#Mathieu Ducrot-sepa-test
1 messages ยท Page 1 of 1 (latest)
Hello, apologies I missed this thread for a bit.
I am not seeing other test numbers that do that at the moment.
Will see if there is another way to get to payment_failed quickly
ok i'll keep testing with the other one for now
Also i've got one question about the invoice.payment_failed. What object should i look for from this event to get the reason why did the invoice payment did failed ?
I would retrieve its payment_intent and check the intent's last_payment_error property https://stripe.com/docs/api/payment_intents/object#payment_intent_object-last_payment_error
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Nice this is indeed what i need, thanks.
Can the last_payment_error.message be automatically translated ?
And from all the error codes listed here https://stripe.com/docs/error-codes is there some best practice (or "must implement") feedback error that you advice developer to include on there integration ?
Another thing that i notice between Card error (with 4000000000000341) and SEPA error (with FR8420041010050500013M02607) is that when the SEPA error occur it cancel the subscription instead of just put it in Incomplete status.
Why does it behave this way ?
Looking in to the translation question...
Unsure on why that may happen. Do you have the IDs of the two subscriptions that you saw this for?
you mean about the sepa canceled status question ? here are subscription id you can compare :
- sub_1K2Hg3D9WJsCYyaSlG2AspTh : proper incomplete status with card 4000000000000341 (normal behavior)
- sub_1K2GpnD9WJsCYyaSoHLWd8wc : subscription status being cancel with sepa FR8420041010050500013M02607 (behavior i don't understand)
Exactly, thank you!
catching up here one sec
missed this from bunch of threads, looking nopw
where is the FR8420041010050500013M02607 account from?
ah sorry found it
ok looking now
ok so I think this is expected, with EU banks, there are no retries for those so it just cancels the Subscription
ok so there is some retries mechanism that leads the subscription to get canceled, how do you set them ? from the dashboard or via the API (if yes which ressource please) ?
from the Dashboard
they work for cards, like you can retry failing Subscription Invoice payments up to some number of times
but they don't work with bank debit PaymentMethods
ok my option "Subscription status" under "Manage failed payments for subscriptions" was set to "cancel the subscription" for our use case i think i'll switch to "leave the subscription as-is" and do some more testing to see if it's the correct option
stepping away, a colleague will catch up if you have more qs!
๐
ok thanks, gotta go too for today
i'll contact you guys via dev-help if i need more help bye ๐