#deepa_ach-retries

1 messages ¡ Page 1 of 1 (latest)

boreal bladeBOT
#

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

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

stark karma
#

Hi there!

cinder sonnet
#

hello

stark karma
#

the scenario where a payment fails and the 2 retries also fail to see what is returned back

Could you clarify what you mean by this? Do you mean what the webhook events for the payment failures would look like, or something else?

cinder sonnet
#

yeah basically it seems like enabling retries for ach means retries will trigger if the account has insufficient funds and wondering what the error that's returned is once all those retries are exhausted and still fail

#

or just also like how to test this scenario of exhausting retries

stark karma
#

just doing some testing on my end

boreal bladeBOT
lime plume
#

deepa_ach-retries

#

@cinder sonnet just to be sure we are talking about the same thing, you are looking at payment retries for Subscriptions right? Or something else?

cinder sonnet
#

yeah

lime plume
#

Then it'd work the same as card payments really. After all retry attempts have been exhausted then we will do whatever is the action you configured in your settings. The default is to cancel the Subscription

cinder sonnet
#

okay and then what would the payment intent status be? just failed ?

lime plume
#

It should be requires_payment_method at that point but it shouldn't really matter since at that point the underlying Subscription would be canceled and that's what you would use to reconcile its status with the data in your database

You can use https://docs.stripe.com/billing/testing/test-clocks to simulate time advancing and go through the various retries and look up the related objects

cinder sonnet
#

what is the status then in the scenario that the first attempt to pull funds fails before the retries? for the payment intent but then the subscription is still active

lime plume
#

likely requires_confirmation but the best way to know would be to try this end to end and confirm. I don't know of the top of my head sorry and I do not think the status really matters in this specific flow

cinder sonnet
#

is there a way to know how many retries have happened / are left?

lime plume