#dmitriy2835
1 messages · Page 1 of 1 (latest)
👋 happy to help
would you mind sharing a Payment Intent ID?
pi_xxx
are you still here @timber timber ?
for example this one -> pi_3NTLDVGeiK3Nc9MV0Te5kcG4
this one also -> pi_3NT683GeiK3Nc9MV1Q4MB040
taking a look
I'm not sure you're using this https://stripe.com/docs/payments/run-custom-actions-before-confirmation right?
oh sorry this is a private beta, my bad
you could either contact support https://support.stripe.com/?contact=true and ask whether you're eligible for this beta
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
or you can use capture: 'manual' to achieve what you're looking for
and instead of confirming in the backend after the collection of the payment method, you would capture
Im not sure that understand you
basically it's the "place a hold" approach https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
so when you use confirmPayment on the front-end, this will confirm the Payment without the need to confirm it from the Backend
if you wish to still have a way to control when the payment will be "executed"
one way of doing this is by using capture: 'manual'
but we didn't confirm it on the front-end(it seems like)
ok, let me please with everything one more time so I can get back to you with something fresh. It seems like we didn't confirm it on the front-end but I have to talk with front-end developers
actualy you did
when collecting the Payment Method on the frontend, the confirmPayment is called
which collects and confirms the payment at the same time
hm
oook
I definately have to talk with front-end developer then
beacuse I suppose to confirm it on backend isead of front-end
what is the use-case? why do you need to confirm it on the backend?
this might help me guide you to which approach is best
hard to say
cause we just implemented everything by usng Stripe examples
and one of the examples -> https://stripe.com/docs/payments/accept-a-payment-synchronously?platform=web#create-payment-intent
says that 3DS confirmation has to be on backend
if we can skip it, so evertying could heppen on UI - then cool
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
3DS authentication can only happen on the frontend.
Happy to help!