#ayesha_docs

1 messages ¡ Page 1 of 1 (latest)

fluid hatchBOT
#

👋 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/1237757363734188052

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

twilit coral
#

Hello
Stripe Elements are equipped to handle 3DS automatically when required/prompted.

Can you share more about how you're integrated? Like are you using Stripe Checkout or PaymentElement or Something else?
What guide you're following?

earnest quiver
#

I'm doing like that
$result = \Stripe\Charge::create([
'amount' => $amount * 100,
'currency' => $currency,
'description' => 'Inv-' . $order_id,
'source' => $token,
'capture' => $capture,

                'application_fee_amount' => $charges * 100,
                'metadata' => [
                    "order_id" => $order_id,
                    "business_id" => $business_id,
                    "preauth" => $preauth,
                    "source" => "web",
                ],
            ], ['stripe_account' => $account_id]);
twilit coral
earnest quiver
#

Which PaymentIntents Apis should i use for 3d secure please share the link and also please help to get that should i write the new api or we have to change or add some params in our existing api

twilit coral
earnest quiver
#

Okay but the link you provided does not contain the info for the onsite checkout 3d secure payment could you please check

twilit coral
earnest quiver
twilit coral
#

That document is for when you are trying to manually redirect users to complete 3DS authentication which you don't really need to do if you're using something like PaymentElement

Additionally, that doc is also for PaymentIntents API. So it won't work for you either way.