#bachir_error
proper krakenBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260540052388319265
đ Have more to share? Add details, code, screenshots, videos, etc. below.
bold thorn
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
void ridge
Hey! req_tOhXh39qDts1My
bold thorn
Maybe it's related to the asynchronous capture:
https://docs.stripe.com/payments/payment-intents/asynchronous-capture
You need to make sure the Charge is succeded before creating a transfer, or retry the operation.
void ridge
We create the transfer in the payment_intent.succeeded webhook, so it should be succeeded ?
We recently added cashapp as payment method, could that be linked ?
bold thorn
We create the transfer in the payment_intent.succeeded webhook, so it should be ...
Refer to this section:
https://docs.stripe.com/payments/payment-intents/asynchronous-capture#listen-webhooks
I invite you to walkthrough the guide I'm sharing with you
void ridge
Since when automatic_async is the default for capture_method ? We upgraded our Stripe lib recently, but we are never passing capture_method explicitly, so this came as a surprise.
bold thorn
it's the default now.
you can override that when creating the PaymentIntent (but it's not recommended if you want to keep getting the best performance)
void ridge
okey great, thanks for the help!
bold thorn
Since when automatic_async is the default for capture_method ?
https://docs.stripe.com/upgrades#2024-04-10:~:text=PaymentIntents,capture guide.
Happy to help!
void ridge
What happens if I need the result of the confirmation synchronously ? I can't use the async capture then ?
We used to have "automatic" as default, would there be cases where automatic confirmation would have returned an error synchronously but not the automatic_async ?
bold thorn
What happens if I need the result of the confirmation synchronously ? I can't us...
You need to set automatic then when creating the PaymentIntent.
would there be cases where automatic confirmation would have returned an error synchronously but not the automatic_async ?
The main benefits of using automatic_async is for performance purposes.
void ridge
What is a valid use case for it ? Usually when people pay we want to tell them right away if the payment has failed or not ?
bold thorn
When using automatic_async, the auth flow is completed so the payment is known failed or not. Just the capture of the funds is async.
void ridge
Tbh I'm still confused : For example If there are insufficient funds on a card, would automatic_async return an error in the API call, or would it be successful, then Stripe would send a payment_intent.payment_failed webhook asycnhronously because it failed to capture the funds ?
proper krakenBOT
bold thorn
If there are insufficient funds on a card, would automatic_async return an error in the API call
Yes it will error.
then Stripe would send a payment_intent.payment_failed webhook asycnhronously because it failed to capture the funds ?
The payment will fail from the beginning.
void ridge
Okey so I can still use it in a synchronous flow then ? Where I need to show an error to the user right away ?