#ditorelo
1 messages · Page 1 of 1 (latest)
Hi 👋
Is this someting you want to force via the API or simply test out so you are familiar with the flow?
I need to test it to make sure our system supports it correctly
For CC I have a bunch of numbers that trigger different SCA states https://stripe.com/docs/payments/3d-secure#three-ds-cards
But I don't have anything like this for Canada or SEPA so I can test it for our development flow
Do you have an example of a Payment Inten that went through this process so I can check the states and transitions?
This is a SEPA one - same issue pi_3NQADcC02mDLKf280vW3nnVI
No 3d secure test details here https://stripe.com/docs/payments/sepa-debit/accept-a-payment
Okay yes I see the requirement for 3DS being requested by the bank. How are you confirming the payment? Are you using Stripe.js?
Yep
Right so Stripe.js should "just handle it". But you want to verify the behavior that your users are experiencing
But all our test account numbers do not include one that triggers 3DS automatically
Ops, maybe I mispoke
We use stripe element to capture this
But we do have some custom processing to send the payment data in the back end using that intent
Hence why I need these details
I'm checking to see if we have any testing resources that match this behavior
Thank you
Looking at the Payment MEthod you passed in that confirm request the underlying payment method type is a card
So using the Test cards for 3Ds would trigger the same behavior as this payment
Here is the request that created this PM: https://dashboard.stripe.com/logs/req_1oswArtdWvBqZD
It looks like it was a cloned Visa
No worries!
Ops, while I have you, I found the Canada PADs one that triggered this
pi_3NP4AZKcLAyOdprh06ovXHQK
pi_3NP4A5KcLAyOdprh06j1vb4U
"The source you provided is not in a chargeable state."
we don't know what to make of this error
And they are set as incomplete
Hi @granite spire I'm taking over. Give me a second to catch up
Thanks for waiting.
https://dashboard.stripe.com/logs/req_XKifK7xYlJ7xpX In this log, I noticed that you passed in a mandate_data to the request. Can you try passing the mandate from the previously suceeded SetupIntent instead? Details in https://stripe.com/docs/payments/acss-debit/set-up-payment?platform=web#reusing-a-payment-method-with-an-existing-authorized-mandate