#khoi
vivid dust
celest junco
i ran into this issue several times: where customer is able to save a card to vault successfully with zip code and cvc. However, at charge times, I got a decline saying incorrect zip code or incorrect cvc
is there any false positive in these two checks? and how i guarantee that incorrect cvc/zip code can be checked up front at Vault layer
ashen berry
What do you mean by "vault" exactly? Just the act of saving payment methods for future usage?
celest junco
right
ashen berry
Got it. So those checks are usually done when saving a card. See: https://support.stripe.com/questions/check-if-a-card-is-valid-without-a-charge. Notice the following caveat though:
To prevent card testing, Stripe is sometimes required to not check cvc and zip checks on card validations, so they may appear as “unavailable”. Those checks will be available on the charge object once an actual payment is made. Stripe uses machine learning to predict when card testing is likely. These checks also may be unavailable as a cost-optimization if Stripe’s machine learning predicts the card is valid and that performing these checks will not increase the probability of a successful payment.
Those there's not a way to force it really
celest junco
oh
what's the recommended work around here?
because we run auctions, i just want to make sure the payment method saved is the working paymen tmethod
ashen berry
Are you currently using SetupIntents to save card details? https://stripe.com/docs/payments/save-and-reuse
celest junco
yes we are
ashen berry
Got it. Yeah that's the best way to ensure a card will be charged successfully later, but there is that caveat I linked earlier. That's unavoidable unfortunately
celest junco
ah i literraly just ran into this right now with a customer
do you know how others work around this issue? just disable cvc/zip check altogether?
or maybe disable for returning customers
we are just starting out so these small transactions really add up :/
formal swallow
Hi there! Give me a min to catch up, my teammate has to run
Was this customer's card saved with a SetupIntent?
celest junco
ya
this is the customer if it helps https://dashboard.stripe.com/customers/cus_MW4XsTWPldWuRk
formal swallow
Got it, thanks for sharing the ID
The only path forward in this case is to listen for those failed payment events (payment_intent.payment_failed in this case) and bring the customer back on session to use a new card
Even if a card has successfully been set up with a SetupIntent, it's possible that a charge with that card may be declined or fail