#bachir-migration
static hound
We can't use their plan ID because we use the Price API
They're backwards compatible
i.e. you can use plan_xxx in places you can use price_xxx: https://stripe.com/docs/billing/migration/migrating-prices
manic stone
-
Ah I got confused by this answer from the support yesterday #988830555770613850 message
-
So by passing the plan ID as the priceID when creating subscriptions on our side, I do not need to worry about double-charges or anything else ?
static hound
Ah I got confused by this answer from the support yesterday
Which part? My colleague started you can use Plans on your new account
So by passing the plan ID as the priceID when creating subscriptions on our side, I do not need to worry about double-charges or anything else ?
Nope, those fields/objects are interoperable
What they meant was you can't create a Plan on your new account with the same ID as the old account
i.e. specifying plan_123 when creating it, so the UUIDs will differ
manic stone
Which part? My colleague started you can use Plans on your new account
Alright I got it, it didn't mean we could not use the planID as the priceID when creating subscriptions, I misunderstood.
Nope, those fields/objects are interoperable
Okey cool then, thanks a lot for your help
static hound
np!