#syoxiss.
pearl pebble
What's the TS compiler error?
pearl pebble
Hmm, if you're manually handling the 3DS redirect you should be passing return_url on PI creation/confirmation: https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-redirect
Otherwise just send the client_secret from the PI after requires_action back to your front-end and use confirmCardPayment
hard oyster
I can't use the front-end to confirm the pi because I'm creating a direct charge to a merchant in our system. I'm currently creating the customer and adding the card_token using the platform account's publishable key and then cloning it to the connected account of our vendor. Because of this, we can't confirm it on the front-end because we don't have access to their publishable key but still would like to have stripe 3d secure into our system. For additional context, we must use the strip standard account for our vendors
I need to be able to still confirm the payment, and facilitate a stripe 3d secure into our system
pearl pebble
Then the link I shared above will help facilitate manual redirect to the 3DS URL
If you don't pass return_url as described, the expectation is you're using Stripe.js so you get this use_stripe_sdk hash in the response which is largely useless if you're not using Stripe.js
With a return_url you'll get a redirect_to_url you can just send your users to
hard oyster
okay noted. When I return the stripe 3d secure redirect_to_url.url, then my customer successfully does the stripe 3d secure. Do I need to confirm it again on my back-end?
coarse sandalBOT
pearl pebble
In most integrations, no. But would depend on which parameters you're using (specifically confirmation_method)
hard oyster
I'm using automatic
pearl pebble
Then the redirect and 3DS challenge success should transition the PI to succeeded