#franco

1 messages · Page 1 of 1 (latest)

nimble prairieBOT
vital axle
#

I didn't think that you had to reauthenticate via 3DS for upgrades/downgrades. Do you have an example of this?

gloomy agate
#

When setting up their plan, they authorize only one charge per month (as per the Indian regulations require). They can't change this as the customer

#

We set the "billing_anchor_date" to "now" when doing a plan change so we can charge overages of the previous plan automatically

#

that's when the payment fails because it needs authentication

vital axle
#

Hmmm, I'll need to dig on this a bit and get back to you.

gloomy agate
#

Appreciate it

#

Do you need my email? I can send it via DM - or will you ping me on this thread?

vital axle
#

Will ping this thread if an answer is forthcoming

#

If I understand correctly, it sounds like we don't recommend doing regular upgrades/downgrades on IN subscriptions. The recommended path is to delete the subscription, create a new one, then reauthenticate.

Does all of that resonate so far?

gloomy agate
#

That is what I had in mind indeed. In that case, I will need to create a new setup intent, right? Is it possible for me to do that without asking the customer to input their CC details again?

#

I just need the SetupIntent to reauthenticate AFAIK

vital axle
#

I believe you can reauthenticate with the existing Payment Method without them having to re-enter their card details. Let me dig up some docs for you

gloomy agate
#

ok so when creating the new subscription, we should grab the payment intent id (from the latest invoice) and take it from there I guess

vital axle
#

For the new Subscription, you could use the same Customer and Payment Method to create a new Setup/Payment Intent and then re-authenticate the Customer's Payment Method by bringing them back on-session and presenting them the 3DS auth portal/window

gloomy agate
#

ah perfect, so i:

  1. cancel the existing subscription, charging for remaining overages
  2. create a setup intent, confirm it to re-authenticate
  3. create the new subcription
vital axle
#

Yup!

gloomy agate
#

alright will try this approach. thanks for the help!

gloomy agate
#

Hey @vital axle 👋 as I'm trying to implement this, it seems the only option I have to confirm the setup intent in the frontend is to create a PaymentElement, therefore asking the customer for their payment info again

#

even if I create the setup intent with a PM attached (which I confirm it is attached from the API calls the SDK makes to retrieve it) - it still shows the payment element (without the payment card prefilled of course)