#geoff_subscription-connect
1 messages · Page 1 of 1 (latest)
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1299101747737919489
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi đź‘‹ can you elaborate on what you mean you use the term migration?
Sure. So one of our competitors runs subscriptions through Stripe Billing. Their customers are going to be migrating to our product, Outseta. So basically the Stripe subscriptions that were running through the competitor, will now be running through our software.
It's easy enough for us to ingest the Stripe subscriptions—nothing changes. But we need to make sure application fees from the previous vendor drop off, and we can start charging our own application fees on the transactions going forward.
We are both products in the payment space, so we process subscription / membership payments for our customers.
Sorry, what do you mean nothing changes? If they (your competitor) created Subscriptions for their users/customers in their Stripe account, you won't get access to those.
If the customer connects their existing Stripe account to our software, we won't see the pre-existing subscription data?
The subscriptions would still be setup in their account, no?
I don't know. I don't know how your competitor set up their integration and where they're storing objects.
If the Subscription is to charge the customer, then I would highly doubt that Subscription resides on the customer's Stripe account.
If the Subscriptions are for your customers to charge their customers, then the Subscriptions might be on those Stripe accounts. Depends on what charge structure your competitor used when setting up their Connect integration.
OK, let's back it up and forget application fee question for a minute. We do these migrations all the time.
Is this conversation public by the way?
Yes, all discussions in this server are public. If you'd like to have a private conversation you'll want to reach out to our Support team to open a ticket:
https://support.stripe.com/?contact=true
OK let's here...
ACME co processes subscription payments for their customers using Stripe connect. So does Outseta. Both use Stripe Billing and create subscriptions in Stripe.
A customer of ACME co wants to migrate to Outseta. They already have subscriptions running in their Stripe account, they just want to migrate those subscriptions to run through Outseta rather than ACME co.
Does ACME use Direct Charges (where the Subscription objects would reside on the Connected Account) or Destination Charges (where the Subscription objects would reside on the Platform account)?
Direct
Okay, because if they built their integration using a Destination Charge style flow, the Subscription objects will remain with their Platform.
It's direct. All of their customers (and all of our own customers) have their own Stripe accounts that the subscriptions run through.
Their customers will need to have a Stripe account for any Connect integration, even ones using Destination Charge flows.
But to answer the core question too, no, you can't take the application fee from the Platform currently collecting the application fee. We typically block that behavior. I'd suggest reaching out to our Support team with a clear explanation of your use case to see if there is anything they can offer you in this scenario.
https://support.stripe.com/?contact=true
Typically your newly migrated customers would need to cancel the Subscriptions that exist in their Stripe account on their own or through ACME, then you would create new Subscriptions for your customer's customers.
How can we setup a call with someone on the Stripe Billing team?
I'm not sure that's possible, but if it is going through our Support team is the best path I'm aware of.
Can the Stripe account they created for the ACME Connect integration be connected to our own Connect integration? Is there any means of doing that?
Depends on how the Connected Account was created.
Our OAuth flow exists for allowing the connection of existing accounts to your platform:
https://docs.stripe.com/connect/oauth-standard-accounts
But when we introduced platform controls we stopped recommending this approach and instead typically recommend you create new accounts for your customers. That's because if the platform they're already connected to has full control over the account, then you won't be able to connect that account to your platform. Instead a new account gets created, without a good way for you to know whether you connected to a brand new account or one that existed before. That's what the warning/callout we have near the top of that page is warning you about:
https://docs.stripe.com/connect/oauth-standard-accounts#:~:text=Starting in June 2021%2C Platforms using OAuth with read_write scope won’t be able to connect to Standard accounts that are controlled by another platform
geoff_subscription-connect
OK, that relates to another question I have,
In Stripe our customers see settings for the “Outseta Application” which are different from settings they see within their Stripe account should they wish to use Stripe directly. How is a customer connected to the “Outseta Application?” Is this purely via the Stripe Connect workflow? We ask because our current UI also allows customers to connect to Stripe by inputting their Publishable Key and Secret Key directly (bypassing the Stripe Connect workflow). Looking for clarity on how connection to the "Outseta application" is made.
yes that would be Stripe Connect.
What if someone doesn't use the connect flow within our product to connect to Stripe though—and enter the Publishable Key and Secret Key directly.
Then that's not Stripe Connect. Instead this to us looks like this specific merchant/account making their own API requests