How to Transfer a Stripe Account When Selling a SaaS
Stripe account transfer process and common pitfalls.
Why Stripe Accounts Are Not Transferable
Stripe’s terms of service prohibit account transfers between unrelated parties. This restriction exists because each Stripe account is tied to a specific legal entity, tax ID, and bank account. Attempting to circumvent this rule by sharing login credentials violates Stripe’s policies and can trigger immediate account termination. Sellers must instead plan for a clean migration that keeps both the original and new accounts compliant until the transaction closes.
Step-by-Step Migration Process
- Verify buyer eligibility: the buyer creates a new Stripe account under their own legal entity and completes full KYC verification before any migration begins.
- Export all customer data: download the full list of customers, payment methods, subscription schedules, and invoice histories via the Stripe API or dashboard exports.
- Re-create subscriptions on the buyer’s account: use the Stripe Billing API to generate identical plans, prices, and trial periods so recurring revenue continues without interruption.
- Migrate payment methods with Stripe Billing migration tokens: obtain limited-scope tokens from the seller’s account and attach them to the buyer’s customers to avoid collecting new card details.
- Update all frontend integrations: replace the seller’s publishable key with the buyer’s key in checkout forms, customer portals, and mobile apps.
- Switch webhook endpoints: redirect all events (invoice.paid, customer.subscription.updated, charge.refunded) to the buyer’s server endpoints before the final cutover date.
- Run parallel testing for 7–14 days: keep both Stripe accounts active while processing a small percentage of traffic on the new account to confirm zero failed payments or webhook drops.
- Close the seller’s account: once 100 % of recurring revenue has moved and the acquisition closes, cancel the original Stripe account and release any remaining reserves.
Valuation and Due-Diligence Implications
Buyers typically apply a 3–4.5× ARR multiple to Stripe-connected SaaS businesses in 2026. During diligence on platforms such as hades.ae, Acquire.com, or Empire Flippers, acquirers request 18–24 months of Stripe payout reports, churn metrics below 2 % monthly, and evidence of PCI-DSS compliance. Any undisclosed chargeback rate above 0.8 % can trigger a 10–20 % escrow holdback in the APA.
Common Pitfalls and How to Avoid Them
- Sharing Stripe login credentials: this is the fastest way to get both accounts shut down; always use the official migration tokens instead.
- Neglecting VAT/GST registration changes: if the seller is EU- or UK-based, the buyer must re-register for tax collection under their own entity before the first post-sale invoice.
- Ignoring subscription proration: mismatched billing cycles during migration can cause double charges; calculate exact proration amounts in the final closing statement.
- Delaying bank-account updates: funds will continue landing in the seller’s account for up to 30 days after key rotation unless the seller proactively closes the account.
How long does a Stripe migration typically take?
Most founders complete the full migration in 3–5 weeks when they follow the eight-step process above and maintain parallel accounts during testing.
Can the seller keep any revenue after closing?
No—once the APA is signed, 100 % of future subscription revenue must flow to the buyer’s new Stripe account; any residual funds received by the seller are held in escrow and wired to the buyer within 10 business days.
What happens to open disputes or chargebacks?
All pre-closing disputes remain the seller’s responsibility and are usually covered by a 15 % escrow reserve released after 90 days, while post-closing disputes are handled exclusively by the buyer’s new Stripe account.
Ready to acquire?
Browse curated digital platforms on hades.ae — every listing is built and owned by our team. View available platforms →