#monove

1 messages · Page 1 of 1 (latest)

shadow roostBOT
lilac drift
desert inlet
#

nm. testing again

#

"The Payment Element does not support Intents created with confirmation_method=manual"

lilac drift
#

Oh are you using defer intent flow?

desert inlet
#

yes

#

we want to use the card later

#

do we have to use the defer flow if we want setup_future_usage?

lilac drift
#

Can you share the example PaymentIntent IDs?

shadow roostBOT
desert inlet
elfin berry
#

Hi 👋

#

I'm stepping in a @lilac drift needs to go

#

Can you just share the ID

desert inlet
#

ok

elfin berry
#

Dashboard links don't work for us

desert inlet
#

if you meant of the one where i got the error, that form didnt initialize

desert inlet
elfin berry
#

So what's the question here? I see you created and then confirmed this intent successfully

desert inlet
#

have you read this conversation?

#

my initial question: Hi, using PaymentIntent to collect a card for a charge from a Web Payment Element, how can we get the status to be requires_confirmation ie we don't want a hold to be placed just yet, just to make sure that the 3DS has been completed.

#

perhaps theres a javascript function that can attach a card to a payment intent without confirming it?

desert inlet
elfin berry
#

So you want to capture payment method data without confirming the Payment Intent?

#

Why are you using a Payment Intent in that case?

desert inlet
#

because if use the SetupIntent flow, there can end up being two 3DS requests, which would be a poor experience for our custommers

#

we will confirm the PaymentIntent should the store accept the order. We're trying to avoid unnecessary credit card holds. We've received pushback from custommers whos orders were rejected due to time constraints that they dont appreciate the credit card hold

elfin berry
#

Setup Intents optimize cards for 3DS by going through the auth flow if the issuing bank requests it

desert inlet
#

we currently use the Card Element and Charges API and are making the switch to the PaymentIntent flow for our European clients

elfin berry
#

Payment Intents can also require 3DS auth if the issuing bank requests it

desert inlet
#

so 3DS requests can only be made when a hold is being placed?

elfin berry
#

No

#

3DS can be requested at any time

#

by the issuing bank

#

But if you create the Payment Method with a Setup Intent it will perform a 3DS auth if requested and set up the Payment Method to be used in the future for a payment such that it is less likely you will have 3DS again

desert inlet
#

ok bc some of the test cards we used had scenarios where it insisted on 3DS for both the SetupIntent and the PaymentIntent. How realistic is that in the real world (if at all)?

#

that scenario scared us off the SetupIntent flow

elfin berry
#

Did you use a test card that is designed to request 3DS every time?

#

Most often 3DS is requested initially when creating the Payment Intent but once the Payment Method is set up for off-session usage then it isn't required unless the bank suspects fraudulent activity

#

But issuing banks have the right to request any time they want

desert inlet
elfin berry
#

Either

desert inlet
#

i see

elfin berry
#

Given that you don't want to take payment immediately upon getting the payment method information, I think the Setup Intent approach would actually work best for you

desert inlet
#

we do want to take payment immediately but we have a flow where the hold is made once the order is accepted

#

so there's no way of making this work? confirmation_method=manual

#

for PaymentIntent when collecting the payment method using Payment Element

elfin berry
#

You can set confirmation method = manual but the second API call you are making is the /confirm request which will confirm the Payment Intent

#

And you don't want to place a hold on the Payment Intent?

desert inlet
#

i do, just not immediately. can i call handleNextSteps instead of confirm?

#

thats our ideal. and have the server do the confirmation

elfin berry
#

That is intended for situations where the next_steps property is set.

desert inlet
#

so that flow would allow the creation of a payment method without a payment intent? much like the card element does now?

elfin berry
#

We have a deferred intent flow where you can create a payment method without a Payment Intent

#

But the confirmation still occurs client-side

#

Or the server-finalized flow

#

It's a lot of options but you could review each to see which makes the most sense for you