#makspiechota_checkout-subscriptions
1 messages ยท Page 1 of 1 (latest)
๐ 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/1229759385434198097
๐ 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.
- makspiechota_checkout-async-payment-methods, 12 minutes ago, 25 messages
in this doc:
https://docs.stripe.com/billing/subscriptions/overview#subscription-statuses
it says that stripe handles automatically retries
What's the follow-up question?
and the section title says:
Build your own handling for recurring charge failures
but that's the thing I don't want to implement it myself
I want to leverage as much as I can stripe
We do for some payment methods, not for most banking methods (SEPA, BACS, etc)
ok so if I receive payment_intent.failed
then I need to deactivate the user subscription manually (by API)?
as Stripe won't do it?
or I can just look for this past_due parameter together with active
It would never have been 'active' in the first place in the initial payment fails. It'd be in an past_due state
Easiest way is to just test these flows with the test data to get the scenarios you want
You can't blindly listen for .payment_failed events though as they might fire when your customer is on-session on the payment page if 3DS/auth is requested
so what should I listen for then?
For what, specifically?
checkout.session.async_payment_failed
ok, once again, here is the scenario (and you can send me just one doc that will explain it, if exists):
I use builtin stripe checkout, the user selects bancontact and get's redirected to the third party website.
How do I handle if this customer is active or not
ok I started to read what you just sent, this might be what I need
please don't close the thread while I am reading
Well Bancontact isn't an async payment method so the failure would happen on the payment page. The async part is irrelevant
We close threads after ~20-30 minutes of inactivity
so why in my dev env
when I checkout with bancontact
it displays the instruction about payment intents?
I'm not sure what you're referencing
makspiechota_checkout-subscriptions
I guess it's a termninology thing. It's async in that you are redirected to the Bancontact site away from Checkout
But it's not delayed
ok
So as soon as you click 'authorize' there it will be succesful and you'll be redirected to your success URL
so in this case it is enough to listen for checkout_complete event?
Yes, for Bancontact. But you might need to adjust for other PM types if you're offering them
how about ideal?
hi! I'm taking over this thread.
iDeal is not listed here, so no: https://docs.stripe.com/payments/checkout/fulfill-orders#delayed-notification
This step is only required if you plan to use any of the following payment methods: Bacs Direct Debit, Bank transfers, Boleto, Canadian pre-authorized debits, Konbini, OXXO, SEPA Direct Debit, SOFORT, or ACH Direct Debit.
so for ideal I can just wait for checkout_complete event?
similarly to simple card payment?
correct
ok
and what would happen if recurring payment fails?
would it set the subscription to status inactive?
you mean the first subscription payment or one of the recurring payment?
oh sorry I missread your question.
this is covered here: https://docs.stripe.com/billing/subscriptions/webhooks#payment-failures
Hi ๐ I'm jumping in as my teammate needs to step away soon. It's a bit hard for us to say exactly what will happen if a recurring payment fails for your Subscriptions, as those settings are account specific. You can check how you currently have those settings configured for your account in your dashboard here:
https://dashboard.stripe.com/settings/billing/automatic
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
checking
If all retries for a payment fail, cancel the subscription
so it means the subscription goes to status: inactive?
No, it means it will be canceled and have a status of canceled, which is a terminal state for Subscriptions.
oh ok
yeah
that's what I meant basically
that it is different than active
ok so in order to summarize
if I enable bancontact and ideal payment methods, the customer on checkout is taken to third party website, and after fulfilling they are taken back to the success_url and I receive checkout_completed event that payment was successful.
For recurring payments I don't have to care if it succeeded or failed, because in case of the failure the correspoinding subscription record is no longer in status: active state