#sam-uplander_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1310513201409949736
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there, based on the request https://dashboard.stripe.com/test/logs/req_ZyAAxrkN8qtcsQ, you explicilty set request_three_d_secure to any to request 3DS for this payment, is this what you intent to do?
yes
If you look at https://dashboard.stripe.com/test/payments/pi_3QOeaGRqI4bLCDyN1yUPFSuN
you'll see that the PM is set for #DS
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
If that's the case, your customer will most likly be asked for 3DS authentication, which can only be done "on session". Therefore you you should remove off_session: true in your request.
TThe we work with other payment gaetways is that we register a card with a specific gateway including user authentication 0 then we re-use the volted card to issue monthly payments - this has to happen without customer invovlement !!! we issue a payment and an invoice - I followed the API docs but I'm obviously missing something ...
It sounds like you want to reduce the possibility of 3DS request, and yet you set request_three_d_secure to any to manually trigger 3DS.
You should remove request_three_d_secure from your request if you don't want to explicitly request for 3DS.
We have customers inEurope where 3DS2 is a must not optional ... so we need to get 3DS approval when we save the card ....
hi! I'm taking over this thread.
it's ultimately up to the bank to decide if they want to trigger 3DS or not.
so that's something that your integration should handle yes.
but you should follow the advice given below to try to reduce the amont of 3DS customers have to go though, since it can reduce conversions.
Can you point me to a school book example of 3DS2 flow with cards being authenticated and vaulted and then being charged ad hock
???
you mean how to save a card without making a charge, and then trying to charge the card later?
and do you want to change the card on session or off session?
Yes - in principal we can use a small charge when we authenticate the card and then deduce that from the initla payment ...
But in prinicpal yes - we do 3ds autnetication when we register / the card and then use the confirmed payment method to charge later - off session