jasoncui

[mighty sequoia]

Hi there

[wide oak]

hey!

[mighty sequoia]

So yes when the SetupIntent is confirmed we will run a card validation with the issuer.

That doesn't mean that the renewal payment can't still be declined by the issuer though

[wide oak]

Ok got it. I guess I'm just confused what the card validation checks for?

ie if the invoice is failing later due to incorrect card information, it seems like that should be validated initially

vs a separate error like insufficient funds

[mighty sequoia]

Yeah incorrect card number is a really weird decline for the issuer to return later on. But really those decline messages are pretty broad. That said, do you have an example I can look at to double check?

[wide oak]

yeah let me find one

@mighty sequoia ok found an example -- cus_Mpg4cNSRaVvupH

actually sorry this one failed due to insufficient funds

let me find another

ok this one

cus_Mrm3o23FsdBYAL

[mighty sequoia]

Thanks let me take a look

[wide oak]

pi_3MD8GuEfPdhRGZ3T023FzAjl failed due to incorrect details, but they were able to attach pm_1M82cHEfPdhRGZ3Tsy6IcON3 correctly

thanks

[mighty sequoia]

Hmm yeah everything looks fine.

My guess is this is just the issuer being strange to be honest

And sending back an error code that doesn't really make sense here

The best thing to have happen is to have your customer reach out to the issuer about this if you want to chase that specific decline further

But nothing is wrong with your integration

The card was setup correctly

[wide oak]

hmmmm ok

thanks for looking into it

is it worth reattempting the charge if we receive that specific error?

[mighty sequoia]

You could, but most likely you will get same response. Best thing to do is to bring your customer back on-session and collect a new PaymentMethod

[wide oak]

ok sounds good

thanks!