#vitorleitao_docs

1 messages ¡ Page 1 of 1 (latest)

hexed galleonBOT
#

👋 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/1290594216283734016

📝 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.

forest siren
#

hi! for BACS it would be async_payment_failed yes.

lapis sandal
#

Perfect, thanks for confirming

#

I am wondering if there is a way in test mode to trigger it

#

because in test mode, it always hits the payment_intent.payment_failed and charge.failed, but never the async one

#

is this a limitation of the test mode?

#

I am using the 10-88-00 and 93333335 which is the failure after 3 minutes for debit_not_authorized

#

Also, for SEPA, would it also be async_payment_failed ?

forest siren
#

you probably want the 3 minute failure ones yes

image.png
#

yes same for SEPA

lapis sandal
forest siren
#

I mean did you actually use Checkout for the test?

#

if not, naturally there is no checkout.session.async_payment_failed event

lapis sandal
#

Just to confirm, when you say use checkout, do you mean the checkout ui?

forest siren
#

I mean using api.stripe.com/v1/checkout/sessions to create a Session object, visiting its url in your browser, filling in the hosted Stripe page there with the test numbers, and submitting the payment

lapis sandal
#

In this case no, we will always use the PaymentIntentService with a PayoutMethod from the mandate

I assume in this scenario then, we should rely on the payment_intent.payment_failed ?

#

From the question I assume that the async_payment_failed only happens on checkouts where we redirect to the ui then?

forest siren
#

yes you should use the payment_intent.* events then

#

yes

lapis sandal
#

Perfect, then that makes a whole lot more sense

#

So just to confirm one last time, checkout.session.async_payment_failed will only happen if the payment is done via the stripe ui?

forest siren
#

yes

lapis sandal
#

Perfect, thanks for confirming @forest siren