mark-reckard_docs

[blissful sequoia]

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[dense thicket]

Hello, yes when cycling our subscriptions themselves will stay in an active state until we hear back from the bank on whether the payment succeeded or failed. There is an unfortunate caveat here that we do pretty much the opposite when you upgrade a subscription and require immediate payment, the subscription goes into a past_due state while we wait to hear back about the payment. I can speak more to that and how to address it if you update your subscriptions like that.

For immediately processed subscription generated payments it seems it takes about an hour between "invoice.created" and "invoice.payment_succeeded"
One quick note on this, the delay there is that the invoice stays in a draft state for an hour where it can still be edited. We auto finalize after an hour, at which point the payment happens immediately, you can also speed this up if you want by calling the invoice finalize API call when you get an invoice.created event.

[elfin island]

Ok yup that makes sense, we use that hour period to add application fees etc. And we don't deal with upgrading subscriptions and requiring immediate payment, so I don't think that will be an issue for us.

So just to be clear, we can expect a longer (4 day) wait time between "invoice.created" and "invoice.payment_succeeded" for BACS payments? Basically my team is just trying to figure out if we need to listen to other events than the ones we currently listen to ('invoice.created', 'invoice.payment_failed', 'invoice.payment_succeeded') for getting updated status information about subscription payments processed through BACS payment methods. I don't see anything relevant in the events docs(https://docs.stripe.com/api/events/types#event_types-invoice.created), but just wanted to confirm

[dense thicket]

Yep, listening to those three events will cover payments succeeding or failing, whether it is immediate or async. You can also listen to payment_intent.processing if you want to get a specific notification from the async payments being initiated. The payment intent in that event will have an invoice field with the ID of the invoice that it is related to

Also one thing to consider is listening to invoice.paid instead of payment_succeeded, they are almost the same event, the one difference is that invoice.paid also triggers when you mark an invoice as paid out of bank (aka outside of Stripe)

[elfin island]

hmm ok interesting re: invoice.paid. I'm not sure if we handle that sort of payment, but thanks for the info. Ok so it sounds like payment_intent.processing might be a nice event to listen to, though I assume that fires whenever any payment_intent starts processing, not just subscription generated ones, so we'll want to scope our handlers. Thanks so much for the info!

[dense thicket]

Correct, that payment intent event would be for any payment intent that is processing an async payment, not just ones firing from Invoices/Subscriptions.