#stephenhuey

1 messages · Page 1 of 1 (latest)

shrewd oysterBOT
red lotus
#

Hello

#

Overall both methods work. There is some potential downside with the SetupIntent approach though. The major downside is it is possible that the SetupIntent is successful (the issuer approves the authorization to save the card) but then the initial Subscription payment is unsuccessful (the issuer then declines the Charge).

#

If they are still going to be on-session you could just prompt them again with a new SetupIntent to create a new Subscription

#

The other potential downside is that the Customer could have to go through 3DS twice

#

It is unlikely, but issuers can force 3DS whenver they want. So possible they force it on both the SetupIntent and the initial Subscription charge.

cerulean grail
#

Good to know! Hmmm, it seems that it's necessary to create the Subscription in order to use PaymentIntent because PaymentIntent needs to know the amount, right?

#

@red lotus -^

#

Or is there some other way to get a client secret intended to be used with a PaymentIntent without first creating the Subscription?

red lotus
#

No you should create the Sub and then pass the latest_invoice.payment_intent.client_secret to your frontend. That is the recommended integration

cerulean grail
#

Ok

#

Thank you @red lotus