#AndyZ-webhook
1 messages · Page 1 of 1 (latest)
Hi! Every time a Stripe invoice is paid, the invoice.paid event will be fired. https://stripe.com/docs/api/events/types#event_types-invoice.paid
So this is a legit short-cut not having to deal with the "async" events mentioned here: https://stripe.com/docs/payments/dashboard-payment-methods#delayed-notifications ?
respectively the "payment failed" can also be dealt with using event the "invoice.payment_failed"? (https://stripe.com/docs/api/events/types#event_types-invoice.paid)
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I am trying to figure out what are the actual changes we need to do, when we want to start accepting SEPA payments. We have already handlers for the events used with credit card payments. After reading https://stripe.com/docs/payments/dashboard-payment-methods#delayed-notifications I am a bit discombobulated whether these 2 "async" webhook events are really necessary. Or why are they recommended?
I possible, I would like to keep our implementation as simple as possible and deal with async success/failed the same way as from credit, card. So we don't have to extend our switch-case statement to handle more events...
Got it! As mentioned in the link you shared:
When receiving payments with a delayed notification payment method, funds aren’t immediately available. It can take multiple days for funds to process so you should delay order fulfillment until the funds are available in your account.
SEPA is a delayed notification payment method, so you'll need to be careful to only fulfil your orders when you actually received the payment. For that you should use webhooks, and there are a few possible options. For exampleinvoice.paid(assuming your are using invoices) orpayment_intent.succeededorcheckout.session.async_payment_succeeded.