#morteza_34604-issuing-transactions

1 messages · Page 1 of 1 (latest)

lusty notchBOT
onyx vapor
#

Hi

#

we are developing an expense management app , and using stripe issuing

#

we show transactions that user has made but they appear some 5-6 hours late in the list

#

how can I get issuing transactions immediately after they are made and show their status eg. pending, etc.

#

and second questions is : is it possible to store issuing transactions on our servers, too ?

hybrid onyx
#

👋 happy to help

onyx vapor
#

but when we make a purchase with the issuing card, we don't see that in the transactions result until some hours

hybrid onyx
onyx vapor
#

thanks

#

what about realtime transactions list

#

?

onyx vapor
hybrid onyx
#

I'm not really sure if there's a delay when fetching List APIs

#

I'll ask my colleague

#

@wary cape would you mind taking a look?

wary cape
#

Hi there 👋 do you have an example of a request you made to that endpoint, along with a transaction you expected it to include but didn't see?

onyx vapor
#

no, users reported that to me

#

actually they made a purshase and they said they don't see it in the transaction's list and I checked and didn't see, either

#

but it appeared after 6 hours I guess

#

and the transation time was 6 hours after purchase time

wary cape
#

Sorry, I'm not aware of any sort of delay in that endpoint, and would need a specific example to take a closer look at what could be going on.

onyx vapor
#

so you are saying when making a purchase

#

transaction object must be created immediately ?

wary cape
#

I would think it is, but I haven't looked at Issuing flows a ton so I may be mistaken.

onyx vapor
#

ok how can I make sure then, should I ask support ?

#

After an authorization is approved and is captured, the status on the authorization is set to closed and a Transaction object is created.

#

this is based on docs

#

After an authorization is approved and is captured, the status on the authorization is set to closed and a Transaction object is created. This normally happens within 24 hours;

#

what does this mean. ?

wary cape
#

It means after an authorization is captured, that a Transaction object should be created when the authorization is closed.

onyx vapor
#

so it may have a delay right ?

wary cape
#

A delay when? I would not expect a delay after the capturing of the payment. If the payment hasn't been captured, then it hasn't finished happening and I wouldn't expect there to be anything to show.

onyx vapor
#

After an authorization is approved and is captured, the status on the authorization is set to closed and a Transaction object is created. This normally happens within 24 hours;

#

what is within 24 hours. ?

wary cape
#

I believe that is referring to the part of the process where the party accepting the payment captures it, which is why the last part of that paragraph goes on to explain that some industries may allow businesses to capture payments up to a month after the authorization.

onyx vapor
#

this normally happens refers to capture of authrization I think

wary cape
#

With payments the authorization step (getting the transaction approved by the issuer) and the capture step (the payment is completed and the funds are sent to the party collecting payment), can be separated. As the issuer you don't have the ability to force the capture to happen sooner, that's handled by the party processing the payment.

My read on that paragraph, is that until that capture happens, it is expected for there to not be a Transaction created. As the issuer you don't know exactly when that capture will happen as it's handled by the party processing the payment.

#

morteza_34604-issuing-transactions

onyx vapor
#

ok

#

so I can show authroizations to feel real time

#

for our users

#

right ?

wary cape
#

I would think so. Do you see otherwise in your testing?