#monove
wanton oasis
vague zenith
Hello! Most Stripe Elements integrations handle 3D Secure. Did you specifically build an integration that does not handle next actions?
vague zenith
Did you use this guide? https://stripe.com/docs/payments/without-card-authentication
acoustic tartan
is that for saving cards for future use? we are having many customers in the UK complaining that the current Stripe Elements form we have declines 3DS cards
vague zenith
I'm trying to understand what you built so I can help you migrate to handling 3D Secure.
Can you link me to the guide/tutorial/etc. you used to build your current integration?
acoustic tartan
vague zenith
That's the Stripe.js API reference for the Card Element, which doesn't help me understand what you built or how you built it.
acoustic tartan
ok pls hold
vague zenith
When you try the test card 4000002760003184 on your integration in test mode, what happens?
acoustic tartan
we get a token but we cant attach that token to a customer account
vague zenith
Why not? Are you seeing an error?
acoustic tartan
"error": {
"charge": "ch_3NRIE9FVvfxwXzwr02qHRri8",
"code": "authentication_required",
"decline_code": "authentication_required",
"doc_url": "https://stripe.com/docs/error-codes/authentication-required",
"message": "Your card was declined. This transaction requires authentication.",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_G397gbO7S7O00u?t=1688750033",
"type": "card_error"
}
}
the request payload was:
"customer": "cus_Npiv79oOjHDFwo",
"amount": "100",
"source": "card_1NRIE8FVvfxwXzwrOcjIsQgW",
"currency": "USD",
"capture": "false"
}```sorry, this is for a hold
sorry, pls hold
we can attach the cards, but payments are failing. how do we fix that
vague zenith
Oh, okay, so you have a legacy integration that's creating Charges directly?
acoustic tartan
correct
vague zenith
Gotcha. In that case this is the guide you need: https://stripe.com/docs/payments/payment-intents/migration
acoustic tartan
that guide is for using already stored cards for payments?
vague zenith
No, I don't think we have a guide for that specifically. When you collect payment details do you collect a payment at that time, or only store them with no payment until later?
acoustic tartan
the latter
vague zenith
In that case you'll need to move to Setup Intents: https://stripe.com/docs/payments/setup-intents
acoustic tartan
This is for a food ordering app. For https://stripe.com/docs/api/setup_intents/object#setup_intent_object-usage, the customer is initiating usage of their card as part of the checkout process, so its not like we're doing a monthly bill. would we do off_session anyways?
vague zenith
No, in that case they would be on session.
acoustic tartan
so what would we need client side (if anything) to make it still work without requiring authentication? or will it just work
vague zenith
It's possible a later transaction might require authentication. You can use Stripe.js to handle things if so.
acoustic tartan
can you show me where
vague zenith
For example, you can use stripe.handleNextAction: https://stripe.com/docs/js/payment_intents/handle_next_action
acoustic tartan
might a bank decline a card if it was set to off_session?
vague zenith
A bank might decline for any reason.
For the scenario where you want to collect payment info and then let people use it later while they're on session the steps are to create a Setup Intent to collect the payment info and attach the resulting Payment Method to a Customer, then later you create Payment Intents that specify that Customer and the Payment Method attached to it. At any point authentication might be required (for either the Setup Intent or the later Payment Intents) so you need to be ready to handle that if required.
acoustic tartan
what if the customer stores the card at a location they frequent. would calling in an order and using the credit card on file be considered off_session considering the customer ordering the food has no screen in front of them?
vague zenith
Yes, that would be off session.