#sam_wiser
1 messages · Page 1 of 1 (latest)
Hi 👋
As our docs point out, if you trigger retries and those retries continue to fail then the issuing banks could start flagging legitimate charges as fraud.
Is this a case where the charge has been declined multiple times through your own retry logic and you still want to offer the customer a chance to trigger another retry with the same payment method?
Basically, we have a 3 days, 10 day and 15 day retry logic setup within stripe.
Clients get in touch after say the 10 day fail, and let us know they now have money on the card and want us process the transaction.
We end up having to do this manually via the dashboard, 99.5% of the time, that manual retry goes through and their subscription renews.
I am wanting to remove this human step, as it's starting to add a lot of overhead & support.
We already have a facility for them to update their existing card to a new card if their existing payment method has changed ( e.g new card etc )
Okay so, as our doc points out, we don't recommend charging the same Payment Method more than 4 times. So let's say you go through all your retries and payments fail. Then I think you would be okay to allow a "one off" retry the customer could initiaite. But I would recommend you track the number of failed attemps so, after the 4th, you can prompt them to use a different payment method.
we use stripes built-in subscription retry count, if it hits that 4th retry and it fails it cancels the subscription ( and their related policy within our app).
Will the one-off retry increment that stripe counter ( as I understand, the dashboard retries don't effect that retry count).
Currently, we have been asking clients who know they now have money on the card to just replace their card with the same card, which triggers stripe to try the charge again - but this is a weird work-around.
The manual retry should still increment the faild attempts/retry counter for the subscripiton.
hmm, that is not ideal, as if that charge attempt fails, it could then trigger the auto-cancellation of that subscription. How can I confirm this / is there a way to not increment that count with a one-off retry, like the admin dashboard ?
- You can and should test all of this in Test mode
haha, I am guessing there is no 2.
Well 2. is that dashboard implements some behaviors that we cannot replicate directly with the API