#jogui-payments
bold fractal
looks like the customer's bank rejected the 3D Secure attempt at the protocol level.
they should contact their bank or try with a different card! Unfortunately none of this is exposed to you in the API or elsewhere. But the bank rejected with error code 08 meaning "No Card record" (will grab a link...)
dusk trout
Hey @bold fractal how are you 🙂 If you are curious about the deployment: https://www.wikiloc.com/premium this is the startnig point
Really? Then we cannot improve the use case for this specific situation? It's like, the bank unilateraly decides to decline this action, no 3d secure no nothing?
Can you show me which information of the DTO (event json) shows that this isthe situation, to debug this ones from other possible bugs
bold fractal
Really? Then we cannot improve the use case for this specific situation? It's li...
we tried to do 3D Secure, which involves contacting the bank, and the bank was not able to process it(which can be because they are down, their system is broken, or the cardholder doesn't have 3D Secure set up in their bank's systems(maybe they don't have an SMS number set up or so on). If that happens the payment can't proceed.
As the merchant you show the error and ask the customer to try a different card or contact their bank.
bold fractal
Can you show me which information of the DTO (event json) shows that this isthe ...
I wish I could, but I can't, this information is not in the API, you just see what's in that event you linked, the generic failure.
looking at the internal details it failed for reason 08 in the spec (https://www.emvco.com/wp-content/uploads/awesome-support/ticket_195361/EMVCo_3DS_Spec_210_10171.pdf page 197) (feel free to Google "transStatusReason 08" as there are other references to this protocol-level error) which is something that can only be resolved by the cardholder asking their bank why the attempt failed.
dusk trout
Okay, I will investigate later this case, thank you for the feedback, we are already getting purchases.
bold fractal
one thing that might work is to look at the SetupAttempt object : https://stripe.com/docs/api/setup_attempts/object#setup_attempt_object-payment_method_details-card-three_d_secure-result
you have to retrieve that directly from the API(you can see the ID, it's in the event, setatt_xxx) and it might have more context on why the 3D Secure attempt failed. Here I think it will tell you there was a processing_error
dusk trout
Okay, perfect
I will check this, to create a use case sending an email to the user warniing about the problem or something
The question is, why this same credit card is working in other stores?
bold fractal
I couldn't say!