#Javier-dynamic-cvc

1 messages · Page 1 of 1 (latest)

sage gazelle
#

Hmmm, that's an interesting problem. I believe once the card is confirmed, you can still create the charge despite the CVC being different. Are you seeing something different?

olive flare
#

I also believe that to be true; however, multiple clients are having this issue, and the bank claims this to be the reason.

The error code in Stripe is not useful, the failed charges have the do_not_honor decline code, which according to the docs means The card was declined for an unknown reason and they need to contact their bank.

sage gazelle
#

yeah, the error messages that banks send back to Stripe are often very unhelpful. Let me check in with a more tenured colleague and see if we know of a solution for this.

olive flare
#

Thank you!

sage gazelle
#

Do you have an example or two of these declines?

olive flare
#

Yes, which ID do you need?

sage gazelle
#

The ID of the Payment Intent or Charge object. A request ID would also be fine.

Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

olive flare
#

charge id 1: ch_3LUxgGIuCVzArKms2E9w8aZP

charge id 2: ch_3LUxgGIuCVzArKms2L903DP9

#

both attempts were on payment intent pi_3LUxgGIuCVzArKms2Y3CHGvp

sage gazelle
#

taking a deeper look now

olive flare
#

I appreciate it

sage gazelle
#

So it looks like there was no successful confirmation on the card attached to that payment intent, which leads me to believe this might be a separate issue. This seems like a standard do_not_honor decline caused by failed confirmation

#

The customer should theoretically be in the checkout flow for the first confirmation at least in order to provide CVC (if requested) so I would expect that (if this were a dynamic CVC issue) we would see the first confirmation attempt pass.

#

Do you have another example where that is the case?

#

I have to leave for now, but @south hollow will be able to assist on any follow-ups

olive flare
#

So, if I understand correctly, the first CVC confirmation appears to have failed?

south hollow
#

Yes that's correct. We are seeing both attempts be declined with DNH — the original and the second attempt

#

Which seems to indicate a normal decline and not a CVC single-use issue

olive flare
#

Thank you, is it possible that you help me check another example?

#

If it's the same issue, I think we can discard this and continue pushing the bank for a solution.

south hollow
#

Sure thing

olive flare
#

Thanks, let me get the ids right away

#

this charge id ch_3LSoV3IuCVzArKms13wkGvcd appears to have the same issue

south hollow
#

Taking a look

#

Okay yes this looks to be the same thing. Slightly different decline as the bank is sending back a transaction_not_allowed but it is very similar in nature here where this is a generic bank decline.

#

The best thing to do in these cases is for the card holder to reach out to the issuer to gather more information from them on why they are declining the payment attempts.

olive flare
#

I understand. Thank you for your help, I'll see what we can find with the bank.