#marcus.chr

1 messages · Page 1 of 1 (latest)

final patioBOT
coarse mango
#

And this SetupIntent is to save the cloned payment so that it can be reused on the connected account?

#

I actually don't think you need the RN client for the initial setup here. You can create the SetupIntent, provide the PaymentMethod's ID to the payment_method param and pass confirm=true to immediately confirm the intent with that PaymentMethod

haughty dirge
#

Not to be reused, so it can potentially be used later on (once).

coarse mango
#

Is there a specific reason you are trying to use the SetupIntent here then?

haughty dirge
#

The use case is that we only charge the guest if they don't arrive to the restaurant. So the user selects one of his PaymentMethods. Then the server clones that for the restaurant's connected account and creates a SetupIntent.

Then we potentially charge using the SetupIntent. Maybe there is a better way?

coarse mango
#

So SetupIntents are for when you want to save a payment method for future payment. You already have the PM saved on the plaftorm and don't want it saved for future use on the connected account, so I don't think it is necessarily providing value here

#

If you have a payment that you want to make, you will want to use a PaymentIntent. So in this situation it may make more sense to clone the PaymentMethod down and use it with a PaymentIntent when you want to actually take the payment

final patioBOT
haughty dirge
#

I was hoping that I could create a SetupIntent and confirm it with 3D secure when the guest makes the reservation.

So that will minimize the "risk" of 3D secure being asked when the PaymentIntent is created (potentially weeks later).

But maybe there is no difference between a PaymentMethod that has been confirmed and cloned and a confirmed SetupIntent?

bright zephyr
#

👋 stepping in here

#

The PaymentMethod was already set up for future use initially right?

#

Or is this the initial collection that you are talking about?

haughty dirge
#

Yes, the PaymentMethod was set up and confirmed with 3D secure for future. It's saved to the platform account.

#

To be specific, the server creates a SetupIntent and then the app is using initPaymentSheet to confirm it.

bright zephyr
#

Okay then no need to use another SetupIntent

#

If the PaymentMethod was already initially set up, the 3DS exemption will be carried forward after cloning.

#

There is no guarantee that 3DS won't be requested still

#

But there is no benefit of another SetupIntent

haughty dirge
#

That makes sense, actually.. Thanks for amazing and fast support! 💪