#civo_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/1217051396394717264
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Can you help me understand the issue exactly? The evt_xxx ID you shared is .requires_action event which is expected for intents where 3DS flow is requested
This represents the intent transitioning to requires_action state, where Stripe.js will facilitate the 3DS flow
In the example you shared, the customer failed auth/3DS so it transitions to requires_payment_method and will need to be re-confirmed again
Ok so in this example it's a customer fault? I was thinking the flow was expecting an action via API to continue..
All we can see is that the bank failed the 3DS auth check
Customer would need to speak to their bank about that
All right
Another question
I read the doc about 3ds2, it has 2 scenario. the first had a manual validation with the customer bank (with OTP or something else), and the second is frictionless mode. The frictionless mode requires additional actions from the api or it is completely transparent to us?
There's no additional action required via the API in either scneario really. The frictionless flows aim to complete auth for the payment without prompting the customer for direct action
Normally it's done via device fingerprinting etc
Glad to hear that
i.e. the customer has made n payments on that card on this device, chances are it is them, opt for frictionless flow