bjinwright-charge-migration | Stripe Developers | Page 1

inner plover Jul 28, 2022, 7:49 PM

#

@forest stump what do you call "existing subscribers" exactly? Like are you using our Billing product with Subscriptions? Something else?

forest stump Jul 28, 2022, 7:50 PM

#

Billing product

#

yes that is correct

#

We want to move to international payments our customers and our clients customers via Connect.

inner plover Jul 28, 2022, 7:51 PM

#

So there's nothing to do really

#

they are already on active Subscriptions. Subscriptions create Invoices, Invoices create a PaymentIntent, it's all already handled/existing

forest stump Jul 28, 2022, 7:53 PM

#

ok awesome

inner plover Jul 28, 2022, 7:54 PM

#

Same for legacy card details and such. You likely have card_123 on old Customers and they all work as PaymentMethod without having to change anything

forest stump Jul 28, 2022, 8:00 PM

#

So we use this old modal and it doesn't trigger a 3DS pop up when we use a 3DS test card. So we want to move to Stripe Elements to do so but it was our understanding that we need to change what we are doing on the backend to accomplish this.

#

I just want to make sure that is correct and you're saying that we don't have to do anything with the current subscribers because billing already takes care of that

inner plover Jul 28, 2022, 8:06 PM

#

correct nothing to change for current subscribers. Just change for new ones. Basically move away from this (actively deprecated for years) and maybe use our Checkout product https://stripe.com/docs/payments/checkout

forest stump Jul 28, 2022, 8:07 PM

#

We thought about using Checkout and may still but we thought that Elements would be the better fit because of the success_url and cancel_url redirect and maintaining state

#bjinwright-charge-migration