#insert_username_here-becs
1 messages · Page 1 of 1 (latest)
heya @elfin veldt , can you share the subscription id for me to take a closer look? it'd look like sub_123
sub_1KbfnrKV2haFIg73JGo2F4y3
If you're looking for the flow for one time payments for BECS, these docs would probably help :
https://stripe.com/docs/payments/au-becs-debit
https://stripe.com/docs/payments/au-becs-debit/accept-a-payment
gimme a couple of minutes to take a look at your subscription
I need to implement both actually. I'm just unsure at which point I can be 100% sure that the payment is successful
usually its when subscription has active status as it was when I implemented card payments. But in this case it goes from active to unpaid/failed state
so, for bank debit payment methods, when starting a subscription, Stripe immediately initiates a debit against the default payment method on file.The subscription’s status is active while payment is pending, then stays active. It moves in to failed state if the payment fails later.
you can be 100% sure that the payment is successful when you receive the payment_intent.succeeded event : https://stripe.com/docs/payments/au-becs-debit/accept-a-payment#web-confirm-success
So if I've understood correctly, even though the payment_intent is in processing state, the subscription can still be in active till the processing completes?
yes, that's right
So my usual flow is to route the customer to the paid invoice after payment is made. But in this case, I reckon most business just route the customer to a success page and then send email later on if the direct debit setup is successful because its delayed notification?
In a live environment, if the debit request processing takes a few seconds, I can still use my existing flow. Would that be the case in live environment or it usually takes some time to go from processing to success/fail in most cases?
BECS Direct Debit is a delayed notification payment method, which means that funds aren’t immediately available. A BECS Direct Debit PaymentIntent typically remains in a processing state for 3 business days after submission to the BECS network. So this would always happen in live environment.
i would actually suggest that you route the customer to a page that displays the PaymentIntent status which would be "Processing". I wouldn't show that the payment is successful because that could be misleading.