You went Custom because you wanted control — and you got 80% of it. The last 20% is rails: Stripe still sets the rate card, still owns the Risk API, and still ships settlement on its timeline. multiflow is Connect Custom without the Stripe layer. Same KYC ownership, same custom UX, same token shape for your existing code — but interchange-plus pricing, same-day settlement where banks allow, and a Risk API you can actually override.
On Stripe Connect Custom today
On multiflow after migration
| What you pay for | Stripe Connect Custom | multiflow |
|---|---|---|
| Base processing (negotiated) | IC + 0.6% typical Custom rate | IC + 0.35% + 10¢ |
| Platform fee margin | Capped at 1.5% by Stripe | Uncapped |
| Same-day payout | 1.5% (Debit Push only) | $0.25 flat (RTP/FedNow) |
| ACH seller payout | $2.00 or 0.8% | $0.25 pooled |
| Issuing — per card | $0.10/auth | $0.08/auth |
| Risk Override capability | Not available | Platform-level |
| Multi-acquirer routing | No (single Stripe rail) | Yes — BIN-based |
| Custom contract term | 24-month typical | 12-month |
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 share your current Stripe Custom agreement (NDA'd) so we can benchmark the Custom-tier rate card and match or beat. We also inventory every Connected Account, Capability grant, and Balance element so nothing is missed.
multiflow underwrites you at platform tier. Because you own KYC, we inherit your verification outputs without re-verifying sellers. API keys issued; you wire them into your platform's gateway abstraction. Most Custom platforms already have a gateway-agnostic layer — adding multiflow is one class.
Because Custom platforms hold seller references through acct_*, we ship a seller-ID crosswalk table. Your platform code does a lookup on every outgoing call — acct_1234 on Stripe becomes mf_acct_1234 on multiflow. Buyer vault ports same as Standard migration.
For 24 hours, your platform runs every new charge in shadow mode — the real charge hits Stripe, a duplicate authorization-only hits multiflow and voids immediately. We reconcile rate/success/decline parity. If parity is <99.8%, we debug before go-live.
Gradual-rollout flag flips. 10% of new charges route to multiflow, 90% continue on Stripe. You monitor the success rate, decline patterns, and settlement timing. Any anomaly triggers instant rollback to 0%.
10% → 25% → 50% → 100% over three days. Each step gets a 24-hour observation window. By end of day 8, every new charge is on multiflow.
Pending transfers on Stripe complete normally. Any platform-held Stripe balances drain to your operating bank over 2 business days. multiflow balances begin accruing immediately on its own schedule.
If you run Issuing, card programs migrate to multiflow Issuing with BIN sponsor swap. Physical cards in the wild continue working on Stripe for 60 days while new issuances come from multiflow. Virtual cards cut over instantly.
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 Connect Custom drain window closes.
Everything below is yours under Stripe Connect Custom'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 Connect Custom knows you're leaving.
Capability grants don't 1:1 map. Stripe's card_payments and transfers capabilities translate to multiflow's accept and payout permissions — same semantics, different names. One-time translation on day 3.
Issuing BIN swap. Existing physical cards carry the Stripe-issued BIN and must continue routing through Stripe until they expire naturally (or you do a mass reissue). Virtual cards move instantly.
Risk Override is new behavior. Your team now has authority to override platform-level risk decisions. We ship a governance template (2-person approval, audit log, expiry) so you don't accidentally give engineering unilateral risk control.
Shadow-mode reconciliation catches 90% of issues. We've never had a Custom migration skip the shadow-mode step successfully. If parity is under 99.8%, something is miswired — do not proceed.
Platform Fee accounting. Stripe reports Platform Fees as a separate line on BalanceTransactions. multiflow mirrors this but uses mf_platform_fee as the type. BI mapping required.
Rollback is cleanest for Custom migrations because you already own the KYC. You flip the gradual-rollout flag back to 0% at any point in days 5-8. Buyer checkout returns to Stripe immediately. Any multiflow-settled balances pay out to your operating bank on the existing schedule, then we freeze the account.
Post-day-10 rollback is still possible but you've drained Stripe balances and reissued some cards — budget a 5-day re-migration. No seller impact in either direction because you own the seller relationship at the platform layer.
Custom platforms have already solved the hard problem: seller onboarding, KYC compliance, and platform-owned risk decisioning. The payment rail is a commodity at that point. Migrating off Stripe Connect Custom to multiflow is a rail swap, not a product rebuild. Most of our 10-day timeline is shadow-mode testing and gradual rollout — actual engineering work is typically under 40 hours.
Custom platforms have already solved the hard problem: seller onboarding, KYC compliance, and platform-owned risk decisioning.
From the Stripe Connect Custom migration field notesIf you're deeply invested in Stripe Issuing physical cards (large in-the-wild card base), your rate card already beats IC+0.35%, or your platform revenue is under $10M and the admin overhead of a migration outweighs the savings — stay put. multiflow's breakeven for Custom platforms is roughly $2M GMV/month.
FAQ
Talk to an operator
Human reply within 2 business hours. No chatbot.