#morteza_issuing-pending

1 messages · Page 1 of 1 (latest)

south fernBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1438150404855828491

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

signal obsidian
#

by the way this transaction is for Tap to Pay app we have developed with React NAtive Terminal

slim acorn
#

👋
The event Id you've shred is for charge.succeeded and it doesn't mean necessary that the amount was capture

#

this hilights that the payment was authorized successfully

#

You may want to check the event charge.captured if you want to monitor the captured amount

#

You have this event for instance: evt_3SScUdLmjdnG8GX01uqG0LJU

signal obsidian
#

wwhat about reading the field amount_captured ?

south fernBOT
signal obsidian
#

should we read that field or charge.amount ?

#

should we check payment_intent_succede to make sure the payment was successful. ?

#

in Tap to Pay case which one is better to be checked ?

#

Card payments are synchronous as I know but why this one is in Pending mode then ?

slim acorn
#

If you want to monitor the amount captured, then listen to the even charge.captured

slim acorn
signal obsidian
#

well, to check if entered amount in the frontend is the same as the one sent to stripe

signal obsidian
#

why payment method is card_present which is synch but it's actually in pending mode and amount is not captured yet!!

slim acorn
signal obsidian
#

what about actaul capture ? when that happens ? I check the issues card used and its transaction is still in pending mode!!

slim acorn
#

It happened after 1 sec almost

#

Check this event creation date evt_3SScUdLmjdnG8GX01uqG0LJU

#

The status transition was automatically for this PaymentIntent pi_3SScUdLmjdnG8GX011mCO9AD, payment authenticated then funds captured

#

sequencially

signal obsidian
#

no I mean I have also developed an app for stripe issuing cards, and the card used for this payment has the transaction in pending state!

slim acorn
#

Can you share a concrete example ?

#

Maybe a PaymentIntent Id ?

signal obsidian
#

I should find transaction id for issuing card

#

please wait untill I find the transaction id, thanks

#

actually the issung card transaction has a capture and pending type and I get its pending start from issuing authorization!!!

#

so I'm gonna share the issuing authorization id

slim acorn
#

Not sure I understand you here, sorry.

south fernBOT
signal obsidian
#

I guess no one knows about stripe issuing in this group

livid bison
#

Hey there, just stepping in for my teammate who had to step away. Do you have those specific examples we can look at?

signal obsidian
#

I need to find the issuing transaction and related authorization.

#

I found

#

iauth_1SSf12PxqJiGKRXD6t6XOdia

#

here is the issuing authorization id

#

@south fern

livid bison
#

ok, thanks. I see this was approved. What questions do you have about it?

signal obsidian
#

why its status is pending, I mean for the authorization object

#

When the authorisation is captured, a transaction is created and the status of the authorisation is set to closed.

this is from the doc

livid bison
#

It doesnt look like this is captured yet, so its pending

signal obsidian
#

ok my question now is , if card payment is synchronous, why this is in pemding state ? we is's almost immediately captured

livid bison
#

What perspective are you asking from, issuing side or payment side?

#

This issuing auth is pending because it hasn't been captured, presumably because on the payment side it was an auth/hold only. The authorization response is synchronous, yes, but may not be captured immediately (or ever).

signal obsidian
#

if it never happens, then why charge.succeded event is sent to the webhooks?

#

actually based on the doc, if amount is not captured yet, it can also be in pending state as well

livid bison
#

Are you also conducting the payment side of this?

#

If so, can you share the payment ID (or that charge.succeeded event id, i can use that).

signal obsidian
#

evt_3SScUdLmjdnG8GX01D6L3dUW

#

this the one I shared at the beginning

#

this payment was made with issuing card and I also shared the authorization id for that issuing card's authorization

livid bison
#

That event corresponds to pi_3SScUdLmjdnG8GX011mCO9AD

#

This does not look like the same payment for the issuing auth you provided, as the network transaction ids don't match

#

Are you sure you haven't mixed up multiple intents & authorizations in testing?

signal obsidian
#

maybe yeah

#

iauth_1SSesRPxqJiGKRXDzI7mw7UC
iauth_1SSeq7PxqJiGKRXDp3Tt3uve
iauth_1SScUpPxqJiGKRXDwcFyK3hS
iauth_1SSbnxPxqJiGKRXDAMXwYwU6
iauth_1SSK8VPxqJiGKRXDzr5Et7kb
iauth_1SSK3aPxqJiGKRXDt8ibVkZu

must be one of these

south fernBOT
livid bison
#

Ah its iauth_1SScUpPxqJiGKRXDwcFyK3hS

signal obsidian
#

it's in pending state

#

and we have received charge.succeded for that

fair palm
#

Sorry for the delay

#

I'm taking over and @livid bison had to step away. I'm looking at this

#

I'm asking a colleague if they know why the authorization is still pending

signal obsidian
#

thanks

fair palm
#

Ok so my colleague who's a bit more familiar with Issuing clarified the behavior here. Let me explain

#

An Issuing authorization is captured when Stripe does the settlement (which is done in batches). So while the payment intent already succeeded, the transaction hasn't been settled from the issuing side of things, and that happens later with a delay.

south fernBOT
errant shoal
#

morteza_issuing-pending

signal obsidian
#

thank you,