#stripeconnectplatform-migration-subscription
viral mango
@fallen flare There isn't a real way to do this at once and you have to account for edge-cases and such unfortunately, this is quite complex today
fallen flare
Better to code it or do it manually for 200+ people?
viral mango
The most straightforward way is to
1/ Cancel the subscription and pass prorate: true so that it calculates the credit you owe them back and puts it in the customer's credit balance
2/ After that, look at the credit they have, then look at their recent charge and refund it for the right amount. The credit could be higher than the charge amount though so if so you have to basically find the next charge to refund and repeat until you're done
fallen flare
OK got it. Thank you so much!
One more question. On your end, is there an easier way to do this? Maybe a direct upgrade to the new sub and keep the existing customer is that easier?
i.e. what is the cleanest way if we have an existing Customer on a Subscription.
And credit them on the upgrade instead of refunding???
viral mango
Do you mean something like I paid $100 for a monthly subscription on May 1st and now you want to switch me to a $500 monthly subscription that starts immediately (May 5 until June 5, etc.) with credit for how much I paid for the month of May that I won't use?
fallen flare
More like you are on a $29/mo plan and we are going to switch you to $39/mo plan with a $10 off coupon or a $479.64 annual plan with a $120 off coupon (customers choice) to match the pricing of the old subscription to not piss off the customers who are on an app we are sunsetting and we would like to set up a new billing cycle starting today if possible (but can let that go and keep them on the same billing_cycle if we have to and it's easier).
viral mango
Sorry, I really don't get that example and the discount and where it comes from
if the goal of the discount is to cover what they paid already, then why reset the billing cycle?
fallen flare
Extends the customers life. Locks in an annual payment that is non-refundable.
But we can keep the same billing cycle.
Problem is I don't know if they will choose a monthly or annual option since it is really up to the customer.
in the wild these things are complex. 🙂
viral mango
Sorry, I really need more details though I don't get your upgrade flow unfortunately and who pays what when
Can you give a really concrete example of who pays what when, what happens at the upgrade, what they should paid, etc.
you talk about a yearly upgrade but then switch to a $39/month plan which is not a yearly upgrade
fallen flare
We have 1000 customers on an old app on a platform where we have to pay 30% to Apple of our income let's say.
viral mango
let's ignore that
fallen flare
We have a self-hosted version of the new app where we pay 0% to no one.
viral mango
just one concrete example of one customer
fallen flare
We have to migrate a customer on a subscription for $100/mo where we pay 30% so only get $70/mo for that customer. We need to put that existing person on our new self-hosted app for $100/mo on a new plan where we get the whole $100 but best to create a new Customer and a new Subscription for accounting clarity that the person signed up for the new app. We want to refund any amount owed on the original lower-margin sub.
That is the most accurate example.
That is the reason for the refund and the ideal new Customer and new Sub.
viral mango
sure but that is the original question that you then changed completely after we talked
I can't really help with both at the same time.
fallen flare
Choose the latter. That is the most accurate situation.
viral mango
what is the latter?
because you did option 1 option 2 option 1
so the former is the latter 😅
fallen flare
We have to migrate a customer on a subscription for $100/mo where we pay 30% so only get $70/mo for that customer. We need to put that existing person on our new self-hosted app for $100/mo on a new plan where we get the whole $100 but best to create a new Customer and a new Subscription for accounting clarity that the person signed up for the new app. We want to refund any amount owed on the original lower-margin sub.
That is the most accurate example.
That is the reason for the refund and the ideal new Customer and new Sub.
viral mango
Cool, so my original answer should be everything you need in that case right?
fallen flare
The orignal platform is being sunsetted so we need to move everyone to the new self-hosted app.
2/ After that, look at the credit they have, then look at their recent charge and refund it for the right amount. The credit could be higher than the charge amount though so if so you have to basically find the next charge to refund and repeat until you're done
****The above step you suggested needs to be done manually in the dashboard?
viral mango
well no I was talking about writing code to do that since you said you have hundreds of customers
you can definitely do it manually if you prefer!
Does that make sense? Also if you make a new customer don't you need to re-collect card details again?
fallen flare
That is a big issue with have with Stripe's API. You cannot migrate a payment method from Customer A to Customer B. 😦
Or from a "Guest" to Customer A. 😦
Well.
Honestly, if we use a Stripe v1 Checkout form that submits to us, we can strip the source, create a new Customer with that source, put them on a new Sub, look for the old sub, cancel the old sub and refund. But Stripe v2 Checkout I think no.
right? We cannot migrate the payment method to the new Customer.
viral mango
I didn't really follow, you can't migrate whether you use the old Checkout, the new one, or none at all. One a payment method is attached to a customer it can't be moved to another customer
fallen flare
Any way to change that in the future?
"Once a payment method is attached to a customer it can't be moved to another customer"
viral mango
No plan to change that in the future no, it's a foundation of our product design today