#EAK - CVC Check

1 messages ยท Page 1 of 1 (latest)

wise saffron
#

Hello, if I remember correctly, some banks will approve transactions even with the wrong date/CVC. I think you can further enforce that check with Radar but I forget, looking in to this...

drowsy plume
#

how on earth are banks ok with this... ๐Ÿ˜„

wise saffron
#

There we go, solved it yourself. Nice job!

#

And yes I am still amazed that it works like that

drowsy plume
#

For the banks that do enforce these...we're noticing that payment collection still completes successfully (setupIntent status is succeeded but the subscription then cannot charge the customer. In test mode...Stripe's API kicks us back to the original payment form with an error

#

but in prod, we're allowed to proceed much further along in the process and are actually allowed to fail when creating a subscription..rather than failing at the payment details collection

wise saffron
#

Ah I see, so this is for setting up a card for use later, not when making a payment initially?

drowsy plume
#

Correct - we have a SetupIntent and we collect the payment information and use that to create a subscription with the default payment set to what they just entered.

wise saffron
drowsy plume
#

Let me rephrase - I think the confusion on my side stems from the "test cards" failing at the collection stage (perhaps that's the authorization stage?). In Live mode - we're seeing the collection happen successfully but then we fail when we actually attempt to charge the customer.

#

and they get a clear error back like: "CVC check failed" (if we used the CVC failed test card)

long narwhal
#

๐Ÿ‘‹ @wise saffron had to head out, but i'll hop in and take a look in a few minutes

drowsy plume
#

in Live mode...it just moves forward and we try to charge the customer...which fails..but at this point - it's too late for us to communicate anything back to the customer (as they are no longer on that payment form page)