#pavlos_elpidorou
1 messages · Page 1 of 1 (latest)
hi! well generally future on-session payments all require 3D Secure. Setting it up is mainly for claiming exemptions on off-session payments
The payments are made off-session. automatically via our system each month. For cards that do not required 3D Secure its ok. But for those that require we are having issues charging our clients, resulting in failed payments due to this
it's always possible for the bank to refuse the exemption and require 3D Secure.
https://stripe.com/guides/strong-customer-authentication#exemptions-to-strong-customer-authentication:~:text=Merchant-initiated transactions (including variable subscriptions)
do you have an example of a PaymentIntent pi_xxx where this happened?
yes this is one example
pi_3OX2zmCG5LI7m2080TIY3J7P
In cases that the bank refuses the exemption what is the best practice for this? Send an email to the client with some sort of payment url so he can perform the payment manually?
I see. So there is no way to like authorize the card for future payments when the customer chooses to save their payment method in our system? Each time a payment fails due to 3D Secure the customer needs to manually perform the payment though a link within our app?
there is a way, what you describe as doing above in your initial post is the way
but like in the example pi_xxx you gave, I'm still looking but I don't see that you actually integrated that way, I see no SetupIntent ever used with that pm_xxx , and it was not attached to a Customer object
We have recently made changes to our implementation so i am testing this on the test environment and using test cards that require 3D Secure. Maybe i can give you a pi_xx of the test environment?
sure
anyway if you're using test mode you need to use a specific card to test this, the one that ends in 3155
the other cards don't simulate the off-session payment getting an exemption
here. pi_3OYmMJCG5LI7m2081S2MjkEp i have used a card found here
https://stripe.com/docs/payments/3d-secure#three-ds-cards
to be saved as payment method for the customer and then did then performed a charge on it just like our automated payments in production
hmm ok. trying to find an example in our production data to see how that card was setup
well in the example you have earlier, from what I saw, it never was
seemed to me you just created the PaymentMethod object pm_xxx, didn't set it up or attach to a Customer, and then a few days later did the off-session payment on it
but I might have missed something
but if you do the flow you describe in your initial message, and what it looks like that test mode flow you shared earlier, then that would all be perfect
I see. We will test it and if any issues arise in production i will let you know for further assistance. thanks alot 🙂