#mclowrider_3dsecure-payment-intents
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/1377677217080934561
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mclowrider_api, 17 minutes ago, 5 messages
Use of test card pm_card_visa keeps triggering 3D Secure sporadically.
Last thread was closed sorry
It just seems to consistently trigger 3DS now
We close threads for inactivity. Can you please provide the current state of your question
Sorry.
Use of test card pm_card_visa keeps triggering 3D Secure sporadically.
โ๏ธ This is my question
Sorry had to drop off briefly earlier.
In what context? What are you testing?
Testing a regular payment
Payment intent gets created but consistently requires action
Is there a payment method that bypasses 3DS?
What front end?
Or are you just making API requests?
Can you share a Payment Intent ID?
What API calls are you making?
Is there a way to share the ids securely. Noticed these threads can be viewed by anyone.
IDs are secure. Only someone with your API keys can use them
pi_3RU8mZBqblN9WokJ0L236fyD
In the creation request, I see the following parameters:
payment_method_options: {
card: {
request_three_d_secure: "any",
},
},
In our API reference we state "Use any to manually request 3DS with a preference for a frictionless flow"
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
That doesn't matter really. It would only come into play when you are making live charges
Because you have requested 3DS
That is not what frictionless means
You requested 3DS, we gave it to you
So I have to go through the UI to complete the paymnet in test mode?
Only if you pass the payment_method_options.card.request_three_d_secure parameter
You are literally telling us to trigger 3DSecure
If you don't want to have that happen, don't ask for it
Ok. Thanks for your help ๐
Sure thing!