#some1ataplace
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. 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.
- some1ataplace, 22 hours ago, 24 messages
- some1ataplace, 1 day ago, 11 messages
Can you share the Checkout Session ID (cs_xxx)?
cs_test_a1SLuuhojCQ8urv62JJMNBMi0UWO2Cw1jQTft9MkpyPtuPDotxgadBGRcM
req_a1OSeR1H62SmhM
I am not explictly saying in an API way to make a subscription. It seems like it is being done automatically
As if the checkout session will do it no matter what
Thanks for sharing! The behaviour is indeed odd. It's likely because ACH direct debit is processed asynchronously that the the subscription will be created first and have the invoice payment in pending, then update to failure later
Can I suggest writing to Support https://support.stripe.com/contact with the Checkout Session ID, so that they can check with relevant team?
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Unless the workaround is if there is a failure of the ACH then cancel the subscription from checkout. Invoice will be uncollectible webhook?
How do I tell then in that webhook it was an ACH failure?
checkout.session.async_payment_failed will be sent. For example: https://dashboard.stripe.com/test/events/evt_1OEm4SIeTJrsS1reyt4J1uW9
I'd recommend checking the guide here: https://stripe.com/docs/payments/checkout/fulfill-orders#delayed-notification
hmm yea I have that too but it is not sending
oh maybe because on the second round of the webhook getting executed I have to say either
checkout_session.invoice.payment_intent.status
checkout_session.payment_status
Which one is better?
The event was sent and your Webhook endpoint has responded 200
I am running into this scenario https://stripe.com/docs/payments/checkout/fulfill-orders?#delayed-notification
checkout_session.payment_status should be checked
yes but it will be unpaid twice - first round and second round
with
checkout_session.invoice.payment_intent.status
I can at least get canceled. But not sure if that will be every time yet
Would this be okay?
event.type == 'checkout.session.async_payment_failed' and checkout_session.invoice.payment_intent.status == 'canceled'
checkout.session.async_payment_failed event should be sufficient to determine the payment failure on the Checkout Session.
checkout_session.payment_status is mainly used to determine the checkout session status when receiving checkout.session.completed event
okay so maybe i won't need to add either status i guess. I'll give it a try thanks
No problem! Happy to help 😄
i think it worked, even the invoice uncollectible webhook, idk why i didn't include the url to that webhook before
Great to hear that it works!