Stripe Standard is the easiest processor to start on and the hardest to leave — until you know the playbook. In ten business days we port your customer vault, subscriptions, active Connect accounts, and webhook consumers to multiflow while Stripe continues settling in the background. Zero downtime, full data portability, and you keep the Stripe account open for 30 days so nothing in-flight breaks.
On Stripe Standard today
On multiflow after migration
| What you pay for | Stripe Standard | multiflow |
|---|---|---|
| Card-present base rate | 2.7% + 5¢ flat | IC + 0.30% + 10¢ |
| Card-not-present base rate | 2.9% + 30¢ flat | IC + 0.55% + 10¢ |
| International card surcharge | +1.5% | +0.80% |
| Currency conversion | +1.0% | +0.50% |
| Chargeback fee | $15 (non-refundable) | $15 refunded if you win |
| Monthly platform fee | $0 | $0 under $50k, $99 above |
| Volume discount (>$1M/mo) | Negotiable at $1M+ | Tiered from $250k, auto-applies |
| Refund fee policy | Keeps the 30¢ | Returns the fixed fee |
Flat-rate processors optimise for onboarding friction, not P&L. Every line above that reads "flat" on the left and "IC +" or "tiered" on the right is a line where multiflow returns margin that was previously opaque to you.
You sign the multiflow order form and we send the Stripe data-export checklist. While we're opening underwriting, you run stripe customers export, stripe subscriptions export, and the PaymentMethod report — all available in your existing Stripe dashboard, no ticket needed. Snapshot your current webhook consumers and active Connect accounts. Everything goes into a private S3 bucket we provision for you (encrypted, versioned, yours forever).
Our underwriting team pulls 3 months of Stripe statements (you upload the PDFs through the operator portal), runs the KYC checks, and assigns you a parent MID plus one sub-account per brand. If you have 4 brands today, you get 5 IDs by end of day 2: one parent, four sub-accounts. No code written yet — just paperwork.
We PCI-port your Stripe pm_* tokens into multiflow's vault using Stripe's official bulk-migration endpoint (POST /v1/payment_methods/migrate). Tokens stay valid for your existing recurring charges on Stripe while multiflow now holds identical tokens referencing the same network transaction IDs. You wire multiflow as a parallel test-mode gateway in staging and run 20 smoke transactions.
Your smallest-volume brand flips live on multiflow. All new charges for that brand route through multiflow's parent. Existing Stripe subscriptions for that brand continue billing on Stripe — we don't migrate subs yet. This is the "one engine off, one engine on" flight pattern.
One brand per day goes live. For each brand we verify the soft descriptor appears correctly on test charges (Apple Pay, Google Pay, card-on-file, and 3DS-challenged). By end of day 7 every new charge across your portfolio is on multiflow.
Active Stripe subscriptions migrate in batches. We use Stripe's subscriptions.update to cancel at period end on Stripe and create the replacement subscription in multiflow — same card, same billing day, same amount. Customers see one charge per period, not two. This is the step that normally breaks bad migrations; we automate it.
Webhook consumers repoint from stripe.com/webhooks to multiflow.io/webhooks. Stripe account goes to drain mode — no new charges, but active authorizations can still capture, refunds can still process, and disputes can still respond. Stripe stays open for 30 days so any late returns, chargebacks, or refund requests resolve cleanly. Day 40 you close the Stripe account.
Seven days, one operator ceremony per day, zero weekend overtime. Each step is reversible through day 30 — you do not fly one-way until the Stripe Standard drain window closes.
Everything below is yours under Stripe Standard's ToS. Export now, before underwriting opens — it's faster while you're still a customer in good standing.
Once you submit notice-of-migration, some processors throttle export API limits. You want these files in your S3 bucket before anyone at Stripe Standard knows you're leaving.
Network transaction IDs. Stripe's bulk-migration endpoint only preserves NTIDs if you migrate to a partner on the same acquirer network. multiflow is partnered with both Stripe Issuing partners and direct Visa/Mastercard network rails, so NTID preservation works — but you must request it explicitly in the migration ticket. Miss this flag and your first recurring charge on multiflow gets treated as card-not-on-file and may trigger 3DS.
Apple Pay domain verification. You must re-verify every domain on multiflow. Stripe's apple-developer-merchantid-domain-association.txt files are identity-specific; multiflow issues new ones. Budget 10 minutes per domain on day 4.
Radar rules don't port. Stripe's Radar is proprietary. We translate your rules into multiflow's fraud engine during day 2, but any custom-trained ML models stay behind. Expect to re-tune for 2–3 weeks.
Connect Standard accounts. If you're on Stripe Standard because you onboard connected accounts, this migration is Stripe Standard → multiflow Marketplace, not Stripe Standard → multiflow. Talk to us first; different playbook.
Metadata gets renamed. multiflow uses mf_* prefixes for metadata keys. Any downstream system (CRM, BI, tax) consuming Stripe metadata needs a field-map update on day 9.
Rollback is available through day 30 at zero cost. Because Stripe stays in drain mode (not closed) and we preserved your Stripe vault identically, reverting means flipping the webhook endpoint back to Stripe and instructing multiflow to stop accepting new charges. Active subscriptions on multiflow would need to be cancelled and recreated on Stripe, but since we migrated them in the reversible cancel_at_period_end pattern, customers don't see duplicate billing during the unwind.
Rollback window closes day 31 because that's when Stripe auto-disables API keys on drain accounts per their standard policy. After day 31, a return to Stripe requires re-underwriting on Stripe's end — a new account, not the old one.
Three triggers dominate the reasons operators migrate off Stripe Standard. The first is portfolio growth past 3 brands — at that point the cost of manually coordinating descriptors, reserves, and risk decisions across Stripe accounts exceeds the cost of migration. The second is a reserve event: Stripe applies a 180-day rolling reserve with almost no notice, your cash flow breaks, and you realize your entire business runs on one risk committee's temperament. The third is rate — once you're past $500k/mo, Stripe's flat 2.9% + 30¢ is leaving real money on the table compared to interchange-plus.
None of these are Stripe failing. Stripe is excellent for single-brand SaaS at 2.9%. But multi-brand operators at 7-figure scale are no longer Stripe's ICP, and the pricing reflects that.
The second is a reserve event: Stripe applies a 180-day rolling reserve with almost no notice, your cash flow breaks, and you realize your entire business runs on one risk committee's temperament.
From the Stripe Standard migration field notesYour checkout code barely changes. multiflow ships Drop-In Elements that mirror Stripe Elements 1:1 — you swap one script tag, change one API key, and the form looks identical. The webhook payload shape mirrors Stripe's event envelope so existing consumers work with a 2-line change. If you're on Stripe Checkout (the hosted page), we offer a hosted page with the same customization API — you migrate the config JSON and you're done.
Your customer experience is identical. Apple Pay, Google Pay, Link-equivalent (we call it MF Wallet), 3DS challenges, saved cards — all work exactly like Stripe. The only visible change is the soft descriptor, which now reads your brand name instead of "STRIPE *YOURCO".
FAQ
Talk to an operator
Human reply within 2 business hours. No chatbot.