When an operator should move off Square (and when to stay)
- Square is excellent under $250k/year on a single brand with sub-1% chargeback ratio in a clean MCC. It is wrong almost everywhere else.
- The 6 leave-now signals: portfolio model, chargeback ratio > 0.65%, restricted-vertical drift, multi-brand reconciliation pain, payout cap friction, or any account closure history.
- Migration order matters: gateway swap first, then descriptor remap, then tokenization re-vault, then DNS/Apple Pay last. Done wrong it costs 5–10% of monthly revenue.
On this page
Square is the second most-asked-about platform we hear from operators (after Stripe). The conversation is always the same: "we love how easy Square is, but [reason X] is killing us — should we leave?" The honest answer depends on which X. This is the framework.
The 4 conditions where staying on Square is right
1. Single brand, under $250k/year, clean vertical
Square's flat 2.6% + $0.10 (in-person) / 2.9% + $0.30 (CNP) is competitive at low volume. Below $20k/month, an interchange-plus plan is usually marginally better but the operational lift to switch isn't worth the savings. Stay on Square.
2. Brick-and-mortar with Square hardware investment
If you've got Square Register, Square for Restaurants, Square KDS, or Square Online — the lock-in is real. Migrating means hardware replacement, staff retraining, integration rebuilds. Below 5% effective rate savings, the migration cost exceeds the gain.
3. Sub-1% chargeback ratio in a Square-supported vertical
Square has gotten more aggressive on chargeback monitoring (matched to 0.9% threshold). If you're comfortably under, in a vertical Square supports (most retail, food, services, simple ecommerce), the platform stability is fine. Stay.
4. Cash-flow-sensitive business under $50k/month
Square's instant deposit is genuinely useful at low volume. Most acquirers run T+2 settlement; Square offers next-day standard and instant for 1.5%. If your AR / AP cycles depend on cash velocity, that's real value.
The 6 conditions where leaving saves the business
1. You're running a portfolio (3+ brands)
Square treats each brand as a separate Square account with its own onboarding, dashboard, payout, and risk file. The reconciliation pain is identical to running multiple Stripe accounts — and Square is more aggressive about closing accounts when one brand's pattern triggers a review. See multi-brand reconciliation for the architecture.
2. Chargeback ratio above 0.65%
Square's soft trigger is 0.65% by industry intel (their public threshold is 1%, but reviews start much earlier). Above 0.65% with no dispute playbook in place, expect a review email within 60 days. Above 0.9%, expect a freeze.
3. Vertical drift into restricted territory
Square's prohibited list expanded in 2024–2025. Currently restricted or scrutinized: peptides, kratom, SARMs, nootropic stacks, CBD (ancillary OK, retail flagged), some supplement categories (anything making structure/function claims), credit repair, debt consolidation, MLM. If your product mix has drifted toward any of these, Square will close — usually with no warning. The Square nutra closure walkthrough covers the pattern.
4. You hit Square's sustained-volume reserve
Square applies rolling reserves on accounts that scale fast or carry chargeback risk. Common pattern: 30% of daily volume held for 90 days, with a $50k cap that quietly grows. Operators with $300k/month run into $90k+ permanently held. That's working capital you can recover by moving to a transparent acquirer.
5. Multi-brand reconciliation has become a part-time job
If your CFO or bookkeeper is spending more than 4 hours/week reconciling Square dashboards across brands, the implicit labor cost has crossed the migration threshold. A consolidated parent merchant account with per-brand descriptors is usually 80% less reconciliation work.
6. Any prior account closure
If Square (or a sibling Block product like CashApp Business) has closed any account associated with your principal, EIN, bank, or device, you're on the watch list. Continuing to process there is a freeze waiting to happen. Migrate now, before they pull volume mid-month.
The migration order (do not skip steps)
Migrating off Square wrong costs 5–10% of monthly revenue from broken integrations + lost payment methods + customer confusion. Order matters:
Step 1: stand up the new gateway in parallel
Don't cut over yet. Open the new merchant account, get keys, test in sandbox + production with $1 charges. The new gateway should be live and processing before any traffic moves.
Step 2: update billing descriptors
Customer support tickets spike when the descriptor on the bank statement changes. Update billing descriptors on the new gateway to match the old descriptor exactly when possible. If the new acquirer requires its own descriptor, send a customer email 7 days before cutover explaining the change.
Step 3: re-vault tokens
Square's card-on-file tokens don't transfer. For subscription and saved-card customers, you have three options: (a) require re-entry on next charge (40–60% drop-off), (b) use the network token via account updater service to re-tokenize at the new gateway (best path, requires both sides supporting it), (c) accept the loss.
Step 4: route 10% of traffic to the new gateway
Split testing for a week catches integration bugs before they hit the whole customer base. Compare authorization rates, decline reasons, AVS match rates side by side. New gateway should match Square within 1–2 percentage points on auth rate; if it doesn't, fix before scaling.
Step 5: cut over Apple Pay and Google Pay last
Apple Pay merchant ID is tied to your domain registration, not your gateway. You'll need to register the new merchant ID via your new gateway, then have customers re-add the card or accept a brief Apple Pay outage. Schedule for low-traffic window. See Apple Pay portfolio strategy.
Step 6: leave Square account open for 90 days
Don't close immediately. You'll need access to Square's dashboard for chargeback rebuttals on transactions that processed there, refund processing, and tax reporting. Close after 90 days of zero activity.
Common destinations and their fit
- Stripe Standard: good fit for clean ecommerce single-brand operators leaving Square. Same-class platform; better developer experience; same freeze risk on growth.
- Authorize.net + acquirer: the "boring stable" path. Gateway is 30 years old, runs through any acquirer. Best fit for portfolio operators going to parent MID structure.
- NMI: like Authorize.net but more modern API. Better for high-risk verticals with niche acquirer routing.
- Adyen: only fits at $5M+/year. Below that, the integration cost dominates the savings.
- multiflow: consolidates portfolio brands behind one parent acquirer with descriptor-level branding. Right fit for the "Square killed our portfolio reconciliation" case. See multiflow vs Square comparison.
Migration timing
Don't migrate during peak revenue weeks. Best timing: low-traffic month, mid-month, after the prior month's reconciliation is closed. Worst timing: December for retail, January for fitness, March for tax-prep operators. Build a 14–21 day migration window with the parallel-traffic period accounting for half of it.
Square is fine. Square is also wrong for any portfolio operator past 3 brands, any vertical that has drifted high-risk, and any operator who's already had one account paused. The migration is annoying but routine. The cost of not migrating compounds — usually as a freeze that costs 30–60 days of cash flow when it lands.