#monove

1 messages · Page 1 of 1 (latest)

lusty stagBOT
frigid iris
#

Hello 👋

#

You will need to create the SetupIntent on the platform account though. And then clone it before you create a PaymentIntent on the connected account for a direct charge

lavish gyro
#

but that triggers up to 2 SCA verifications

#

one for the setupIntent and another for the PaymentIntent

#

we're looking to reduce it to a single

#

ie a customer should be able to use a credit card and store it for later all in a single authentication

#

this is for a POS where customers will be sent a url where they enter their payment method information and possibly choose to save the payment method for later use after this order

frigid iris
#

Do you use on_behalf_of when creating a SetupIntent?

lavish gyro
#

we're currently trying to scope out what the flow should be and what are the coding requirements, so no

frigid iris
#

I think that's what's causing the second SCA. Typically you'd not see a second 3DS attempt on the cloned payment method if the initial setup used on_behalf_of parameter pointing to a connected account that enforces SCA.

lavish gyro
#

does on_behalf_of store it to the connected account or to our platform?

frigid iris
#

the platform account

lavish gyro
#

oh nice

frigid iris
#

On_behalf_of only changes the merchant of record to the connected account. I'd recommend trying it out in test mode, it should allow you to test the expected behaviour.