#deaa
1 messages · Page 1 of 1 (latest)
Hello! We have a guide to 3D Secure here:https://stripe.com/docs/payments/3d-secure
Beyond that I'm not sure how I can help, can you provide more information?
i need to recharge old payment method
but maybe was 3ds
i recharge by this code
its working fine if it not 3ds
Ah, gotcha. We have a guide for this here: https://stripe.com/docs/payments/save-and-reuse?platform=web#web-create-payment-intent-off-session
in case payment_method is 3ds how to redirect customer to 3ds authenticaion then back to backend code
Specifically this part:
When a payment attempt fails, the request also fails with a 402 HTTP status code and the status of the PaymentIntent is requires_payment_method. You need to notify your customer to return to your application (e.g., by sending an email or in-app notification) to complete the payment. Check the code of the Error raised by the Stripe API library or check the last_payment_error.decline_code on the PaymentIntent to inspect why the card issuer declined the payment.
If the payment failed due to an authentication_required decline code, use the declined PaymentIntent’s client secret and payment method with confirmCardPayment to allow the customer to authenticate the payment.
nice, but how i will know if the customer complete the authentication?
is there redirect_url and return_url?
@ruby prism you should be using Stripe.js to do all of this for you automatically
when you PaymentIntent is in status: 'requires_action' you need to get the customer back on session client-side in a browser and then you can call confirmCardPayment() which Stripe.js to go through 3DS
is there any easy way like old approach like i used
@ruby prism honestly that approach is way harder. You could make it work but we strongly discourage it overall. What I explained is way easier. Client-side you make one JS call and it's done, we do everything for you
i know, but i have already this way implemented, it will have few work instead of implement new one using stripe .js
yeah no, we don't have a flow like what you describe exactly. You'll have to change a lot of that code anyways, and migrating to a flow similar to yours (but showing an iframe and handling 3DS1/3DS2 differently is way more work and more brittle than my approach
honestly you really need to spend the time shifting your integration entirely and re-build it on PaymentIntent's official flow, it will just save you hundreds of hours down the line
ok, thanks
your approach is better, but as you said , i need a time to integrate to it
you helped me, thanks a lot
have a nice day🙂
Please ask more questions if you need to, we can help you get there quickly 🙂