#sow - Placing a hold on a card
bleak quiver
Hello again! If you successfully authorize (place a hold) on the funds the capture request will succeed as long as you make it within the allowed timeframe.
Are you looking for some kind of event if the capture is attempted outside that time window?
livid minnow
Yes, we are getting the event as setup_intent succeeded for that ( for successful authorization of the saved payment method) I believe that is what we need to use. Now, after the service delivery we are calling the capture method of the payment_intent and we nee to track if the payment was success or failure. Document listed payment_intent success but not failure. So how to track failure scenarios ?
For connected account
bleak quiver
Hang on, I think we're talking about different things.
livid minnow
🙂 ok
bleak quiver
A Setup Intent sets up a Payment Method for future use, which is very different from the "hold and capture" method you mentioned earlier. Can you give me some request IDs showing what you're doing in the API related to your question so I can be sure we're on the same page?
Specifically I'm interested in the request ID where you're authorizing an amount.
livid minnow
currently i am tesing with stripe CLI , where I am doing this step : https://stripe.com/docs/payments/save-and-reuse?platform=android&ui=payment-sheet#charge-saved-payment-method, in which it is creating a payment Intent. In my case only difference is we are making the payment_intent with capture using the desintation account (for stripe connect)
I want to track if the payment was success or failure. Since it is stripe conntect account, I am not seeing any payment_intent failure event like the one we have for stripe non-connect accounts
I just track in the backend if the final capture was success or not
bleak quiver
Stripe CLI makes API requests, and those API requests have request IDs.
livid minnow
yes, so give few min i will create one and send over to u
bleak quiver
Based on what you've said so far it sounds like you are not placing a hold on funds and authorizing a specific amount to capture later. That is covered here: https://stripe.com/docs/payments/capture-later
Using a Setup Intent sets a Payment Method up for future use, but it doesn't authorize any specific amount or make any guarantees about future transactions succeeding.
If you want to place a hold on funds to guarantee they will be available later you need to use a Payment Intent with capture_method set to manual and then separately confirm (place the hold on the funds) and capture (move the money) the Payment Intent.
If the confirmation of a Payment Intent fails a payment_intent.payment_failed event will be generated regardless of Connect being used or not.
Once I see some request IDs I can provide you with more specific guidance.
livid minnow
You have answered my question 🙂 , "If the confirmation of a Payment Intent fails a payment_intent.payment_failed event will be generated regardless of Connect being used or not." That was exactly I was looking, I thought that since it was against the stripe connected account I need to use webhook listener for connected events. It was confusing that the documentation here https://stripe.com/docs/connect/webhooks shows only few events and one of them was Payment_intent succeeded , so here my concern is, do I need to create two seperate webhook listeners to track both payment_intent failures in non-connect webhook handler and payment_intent succeeded in the connect webhook handler
bleak quiver
That depends on where the Payment Intents live. If the Payment Intents are on your platform account you need an Account webhook endpoint set up on your platform account to get those events. If the Payment Intents live on the connected accounts you need a Connect webhook endpoint to get the events from your connected accounts.
The events shown in the doc you linked to are the ones we recommend you listen to, but you can listen to others if you wish.
I need to get going pretty soon, any final questions before I leave? 🙂
livid minnow
How do we need know if the Payment Intent live in platform or connected account, e.g in our scenario we are using like this, curl https://api.stripe.com/v1/payment_intents
-X "POST"
-d "amount"=1099
-d "currency"="eur"
-d "automatic_payment_methods[enabled]"=true
-d application_fee_amount="123"
-d "transfer_data[destination]"="{{CONNECTED_ACCOUNT_ID}}"
bleak quiver
That Payment Intent is being created on your platform account because you haven't specified the Stripe-Account header.
livid minnow
so for a marketplace scenario, do we need to create payment intent in the connect account ?
we are implementing this option : collect and then transfer scenario
bleak quiver
It depends on the type of connected accounts you're using.
If you're using Standard accounts we recommend direct charges, which means the Payment Intent would live on the connected account.
bleak quiver
If you're using Express or Custom accounts we recommend destination charges where the Payment Intent lives on your platform.
Yeah, so what you're doing is fine.
livid minnow
ok great, so I can track it using the normal webhook events instead of connect webhooks right
bleak quiver
Yep.
livid minnow
thank you so much for your help 🙂
bleak quiver
No problem!
livid minnow
you are awesome. Thanks for your quick help!
bleak quiver
Always happy to help! Have a great weekend!