Shopify Plus stores typically run $10-100M GMV. At that scale, 0.5% is not noise — it's a board-level line item. Shopify Payments' Plus rate card barely improves with volume, and the 0.2% alt-processor penalty still applies to any non-certified gateway. multiflow is a Shopify Plus Certified Payment Gateway: zero penalty, IC+ pricing that compounds at scale, and true multi-brand orchestration for Plus enterprises running multiple store-fronts off a single acquirer relationship.
On Shopify Plus today
On multiflow after migration
| What you pay for | Shopify Plus | multiflow |
|---|---|---|
| Plus online rate | 2.25-2.5% + 30¢ | IC + 0.35% + 10¢ |
| Plus in-person rate | 2.4% + 10¢ | IC + 0.25% + 10¢ |
| Alt-processor penalty | 0.2% | 0% (Certified) |
| International card | +1.0-1.5% | +0.60% |
| Currency conversion | +1.5% | +0.40% |
| Multi-entity billing | Separate Plus org per entity | Native sub-account structure |
| Acquirer routing | Single (Stripe rail) | Multi-acquirer BIN routing |
| Monthly platform fee | Covered by $2k+ Plus | No platform 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.
Plus operators typically run multiple store-fronts under one Plus organization. We inventory every store, note which are on Shopify Payments, identify Recharge/Bold/Seal subscriptions, document Shopify Flow automations that fire on payment events, and catalog Shopify Functions that customize checkout.
Underwriting at enterprise tier typically moves faster because of available financial statements. In parallel, Certified Gateway activation submits to Shopify — Plus has a formal process that takes 48 hours and involves an assigned Shopify Merchant Success Manager.
Customer PaymentMethod fingerprints release through the Shopify-Stripe vault-migration pathway (Plus-only API). Staging Plus store wires multiflow + runs 50 test orders covering cart, Shop Pay Express, Apple Pay, subscription, international, and refund flows.
Highest-volume store flips first to serve as the pilot. Shopify Admin → Settings → Payments → Activate multiflow. Shop Pay, Apple Pay, Google Pay all preserve because of Certified status. 24-hour monitoring window before next store.
One store per day. Subscription apps (Recharge/Bold/Seal) use the gateway-swap flow on Certified Gateways. Next-billing-date preserves. Customer cards re-authorize through ported vault.
Shopify Flow automations referencing Shopify Payments event types need source-field updates (payment-gateway-specific event payloads differ slightly). Shopify Functions that run on checkout (tax calc, shipping, discount) continue working — they operate above the payment layer.
This is the big Plus win: multi-brand portfolios running separate Plus organizations now consolidate reporting through multiflow's parent account. BIN-aware routing rules activate — Visa → Acquirer A, Mastercard → Acquirer B based on interchange-optimal paths per SKU tier.
Webhook consumers repoint. Shopify Merchant Success Manager notified of completed migration. Shopify Payments goes to drain for each store-front (60 days). Enterprise reporting shipped to your CFO.
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 Shopify Plus drain window closes.
Everything below is yours under Shopify Plus'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 Shopify Plus knows you're leaving.
Multi-store-front Plus orgs. Each store-front migrates independently. You pick the order (highest-risk first, or lowest-volume pilot first — both strategies are valid). Don't try to cut all stores in one night.
Shopify Functions on checkout. Any Function that references payment_gateway fields needs a source-map update. Typically 1-2 Functions per Plus store. Budget 30 min each on day 8.
Shopify POS Pro. Preserves with multiflow-compatible card readers. Existing Shopify POS Go devices are tied to Shopify Payments — swap to Clover or PAX loaners.
Shopify Audiences + Collabs. Data-sharing programs depend on Shopify Payments. Migrating off removes access; most Plus operators already don't use Audiences heavily.
B2B catalog pricing. Plus B2B features (custom catalogs, price lists, net-30 terms) work with any Certified Gateway. Net-30 invoicing actually improves because multiflow has better B2B invoice tooling than Shopify Payments.
Shopify Capital eligibility. Enterprise Plus operators rarely use Shopify Capital — not the motivator to stay.
Rollback on a Plus migration is store-by-store. If cohort 1 (the pilot store) underperforms, you can flip that single store back to Shopify Payments within 48 hours without affecting other store-fronts. Once 3+ stores are on multiflow, rollback requires coordinating multiple gateway flips — feasible for 5-7 days post-cutover, expensive after that.
The real lock-in after day 10 is the multi-brand consolidated ledger. Once your CFO has seen consolidated reporting across 4 Plus stores, returning to 4 separate Shopify Payments accounts feels like a regression they won't accept.
Consider a Plus operator at $50M annual GMV blended across 4 store-fronts. Shopify Payments Plus rate: 2.3% effective. multiflow IC+ effective rate: 1.6%. Difference: 0.7% of GMV = $350k/yr in processing costs. Add back the 0.2% alt-processor penalty elimination: +$100k/yr. Total savings: ~$450k/yr. Migration cost: zero (covered under standard underwriting). Payback: day 1. This math compounds linearly with GMV — a $100M Plus operator saves ~$900k/yr.
This math compounds linearly with GMV — a $100M Plus operator saves ~$900k/yr.
From the Shopify Plus migration field notesShopify Plus doesn't elegantly handle multiple distinct brand-owned entities. Either you run one Plus org with multiple store-fronts (shared entity, shared banking, can't run separate brand DBAs cleanly) or multiple Plus orgs at $2k+ per month each (separate entities, but no consolidated reporting). multiflow solves this at the orchestration layer: single contract, one consolidated ledger, per-brand descriptors and sub-accounts, each with its own risk and reserve independently managed. This is the specific pattern multiflow was built for.
FAQ
Talk to an operator
Human reply within 2 business hours. No chatbot.