#mattwoberts
1 messages · Page 1 of 1 (latest)
Hi there!
Hi 👋
Can you share a request ID with the decline code you are seeing?
Sure, give me a min...
Ok here's a charge that has this. - "previously_declined_do_not_retry" : ch_2McoKGEHSdXPilfD0fS99bCN
I understand the error - the bank is saying that we shouldn't keep trying that card, so you don't bother trying it again. What I can't understand is that we didn't get this at all until Jan. Do you know if it's linked to smart retries or anything like that (that's about the time we enabled that, previously it was set to manual retries)
This does not appear to be linked to smart retries. In this case it's that we've seen this card before and Stripe has already received a message from the issuing bank that this card should not be charged.
We're trying to work out why we're getting more declines recently - and there are 76 of these in Jan - For the whole previous year - none. I'm scratching my head with it.
Could it be related to radar?
This wasn't related to a radar rule
As I said this was communicated from the issuing bank
It started happening about the same time that we started using customer portal to manage users cards. But I can't see a reason why / how this would be...
Before then we were using our own UI and managing card collection via stripe elements, and using the JS lib. There's nothing different about how that would work behind the scenes?
Shouldn't be. Do you have other examples so I can check to make sure it's the exact same error?
Yup, this one.. ****
ch_2MVAW9EHSdXPilfD1b9FpmYU
ch_2MbSPvEHSdXPilfD0qWkXETn
(both those)
Okay these errors are for the same reason. We are retrying invoice collection but we have received an error from the issuing bank that says we should not retry this card
Ok cool - I guess there's nothing more proactively we can do from our end other than ask the customer for a new card then
Yes and if these are their default payment methods in the Customer record you would want to update that when they provide a new card.
Ok cool, thanks