The 30-Second Version
A fund hold means the processor decides not to release card revenue that your customers have already paid. That money is sitting in a pool controlled by the processor. It might look like a paused payout dashboard, a reserve percentage deducted from each batch, a lump sum held "for security," or a full account freeze.
Processors are not evil for doing this. They are protecting themselves β specifically, their liability if your customers start disputing charges and you cannot cover refunds. Your job is to prove you are boring enough to not need protecting against.
The rest of this guide breaks down each hold type with the specific mechanics, numbers, and recovery steps Canadian merchants need.
Hold Type 1: Rolling Reserves
A rolling reserve means the processor automatically withholds a fixed percentage of each batch of payouts for a set period β typically 90 to 180 days β then releases it on a rolling basis. This is the most common hold type for legitimate, ongoing businesses that the processor considers elevated risk.
How the numbers work in practice
Say you have a 10% rolling reserve with a 90-day release window and you process $50,000 CAD per month:
- Month 1: you process $50,000. Processor holds $5,000. You receive $45,000 (minus fees).
- Month 2: same. Another $5,000 held. Another $45,000 out.
- Month 3: same. Another $5,000 held.
- Month 4: you now start receiving your Month 1 reserve back β $5,000 β as the 90-day window opens. But you're also depositing a new $5,000 from this month's processing. At steady state, reserves cancel out as long as you keep processing at similar volume.
The trap is when you stop processing or cut volume: the reserve keeps draining from past batches, but you lose the float you'd normally recoup through continued volume. Businesses that slow down, take a break, or shut down find that their held reserve sits for the full window.
Typical reserve rates by category
| Business Type | Typical Reserve % | Release Window | Why |
|---|---|---|---|
| Mainstream retail, restaurants, in-person | 0β5% | 90 days | Low chargeback exposure, goods delivered at point of sale |
| E-commerce with normal fulfillment | 5β10% | 90β120 days | Card-not-present risk, delay between charge and delivery |
| Pre-orders, custom goods, deposits | 10β20% | 90β180 days | Extended dispute window, delivery not immediate |
| Online courses, coaching, digital services | 5β15% | 90β180 days | "I didn't receive what was promised" chargebacks, hard to dispute |
| Events and ticketing | 15β25% | Until event date + 90 days | Mass cancellation risk, chargeback window extends past event |
| Travel and accommodation | 20β30% | Check-in date + 90 days | Worst-case scenario for refund waves |
| High-risk (prohibited categories, established history) | 25β50% or fixed | 180+ days | Processor absorbing known elevated loss rates |
Processors don't advertise these numbers. They're negotiated (or imposed) at underwriting. If you're currently being hit with a reserve and want to challenge the percentage, the path forward is demonstrating your actual chargeback rate, refund rate, and bank liquidity β not arguing philosophy with support.
Hold Type 2: Paused Payouts
A paused payout is a complete stop to funds moving from your processing balance to your bank account. Unlike a rolling reserve, it's not a percentage β it's everything.
What triggers it
Paused payouts are typically triggered by automated risk scoring. The most common triggers in Canada:
- Volume spike over 3Γ your recent baseline. You normally process $8,000/month and suddenly do $30,000 in a week. The system flags it regardless of whether the sales are legitimate.
- Unusual transaction pattern. Lots of same-amount transactions, lots of foreign cards, lots of transactions from the same IP range, or an unusual ratio of card-not-present to card-present volume.
- Chargeback rate crossing Visa/MC thresholds. Visa's formal alert threshold is 0.65%. Their remediation programme kicks in at 0.9%. Above 1% and processors start protecting themselves aggressively. A bad month for a small-volume merchant can hit these thresholds with as few as 5β10 disputes.
- Account not yet verified after a certain volume. Aggregated processors (Stripe, Square, Shopify Payments) have verification thresholds. Process past the threshold without completing KYC and the system can automatically pause payouts.
- Refund rate trending high. If your refunds as a percentage of volume start climbing, automated systems treat it as a signal of future chargebacks, cancellations, or customer service problems.
How long does a paused payout actually last
The honest answer: it varies and support will be vague. The practical ranges Canadian merchants report:
- 3β7 days: typical for a minor verification pause or small volume anomaly where documentation was provided quickly
- 2β4 weeks: typical for a proper risk review where the processor is checking documents, transaction history, refund patterns
- 90β180 days: if the account is terminated and the balance is held against potential disputes
If your pause is sitting at 10+ days with no resolution timeline from support, start treating it as a 30-day scenario for cash flow planning purposes, not a 7-day one.
Hold Type 3: Underwriting Reviews
Aggregated processors do almost no underwriting at signup. That's the convenience of Stripe, Square, and Shopify Payments β you're live in minutes. The trade-off is that underwriting essentially happens reactively: the processor reviews your account after you start processing volume, not before.
What an underwriting review actually looks like
You may receive a request to provide:
- Government-issued photo ID for all beneficial owners over 25% stake
- Canadian business registration or articles of incorporation
- Recent business bank statements (typically last 3 months)
- Supplier invoices or proof of inventory
- Fulfillment records and tracking numbers
- Your website, specifically: refund policy, shipping timeline, return process, contact information
- Explanation of your business model, especially if it involves pre-orders, deposits, subscriptions, or future delivery
The review can be triggered by volume thresholds, a category flag, a complaint, a chargeback spike, or a routine automated sweep. Processors do not generally distinguish between these triggers in the initial notice to you.
What actually determines a good outcome
Risk teams are trying to answer one question: if your customers collectively decided to dispute all their recent charges, does this merchant have the cash and the legitimacy to cover it? The documents that move the needle:
- Bank statements showing an operating balance. If your business bank account regularly holds $10,000β$50,000 CAD, that signals you're not living payment-to-payment through processor deposits. Empty or near-empty statements raise the opposite flag.
- Supplier invoices for tangible goods. Proves you have real inventory to ship, not a drop-shipping or arbitrage setup with thin visibility into fulfillment.
- Tracking export or fulfillment records. Proves orders are actually being shipped and delivered, not just charged.
- Clear, customer-friendly policies on your website. A refund policy that sounds like a legal threat, vague shipping windows, or no working phone/email visible on the site are red flags that say "this merchant creates disputes."
What does not help: long emails about how loyal you've been, screenshots of positive reviews, requests to speak to a supervisor, or legal threats in your first contact. Those delay the review. Evidence accelerates it.
Dedicated merchant accounts avoid the reactive underwriting trap
Providers like Helcim and Moneris issue dedicated merchant accounts after proper upfront underwriting. The onboarding takes longer β days or weeks instead of minutes β but once you're approved, a volume spike or category flag doesn't trigger the same reactive freeze. The risk is priced in at the start. For most Canadian merchants processing more than $20,000 CAD per month, the peace of mind is worth the onboarding friction. Read our underwriting readiness checklist if you're considering making the switch.
Hold Type 4: Verification Delays
Verification delays are the mildest form of hold β and often the most frustrating because they feel arbitrary when your business is entirely legitimate.
Why they happen
Canadian KYC (know your customer) and AML (anti-money laundering) obligations require processors to verify the identity of merchants and beneficial owners. Stripe, Square, and Shopify Payments have automated most of this, but the automation fails in predictable ways:
- Name mismatches between your ID and your business registration
- Recently incorporated companies with thin document trails
- Foreign-born business owners with non-standard name formats
- Sole proprietors operating under a business name with no formal registration
- Business address mismatches (your bank shows a different address than your registration)
- Shared addresses flagged as high-risk (commercial mail services, co-working spaces, certain postal codes)
How to clear a verification hold fast
- Read the exact request carefully. Processors specify which document they need. Submit the exact document format they're asking for, not a substitute.
- File names matter. "stripe-id-john-doe.pdf" is better than "scan001.pdf." Clear names suggest an organized merchant; random filenames suggest someone dumping files.
- No blurry phone photos. A failed document scan wastes a week. Use a scanning app if you don't have a scanner. CamScanner or Adobe Scan work fine and are free.
- Match everything. If your bank account is in the name "Acme Supply Co." but your registration says "Acme Supply Company Inc." β that's a flag. Fix the mismatch or explain it proactively in writing.
- Don't resubmit repeatedly. If you submitted complete documentation, confirm via chat that it was received and wait. Multiple resubmissions can actually slow the queue.
Hold Type 5: Large-Ticket Declines
Large-ticket declines are different from fund holds in that the transaction is declined before it completes, rather than held after the fact. But the effect on cash flow is the same: you made a sale, and you don't have the money.
Why processors decline large individual transactions
Aggregated processors have risk scoring that flags transactions above certain thresholds. The thresholds are not public, but Canadian merchants typically encounter friction starting around:
- $3,000β$5,000 CAD for card-not-present (online) transactions with new customers on accounts that don't have strong transaction history
- $8,000β$15,000 CAD for larger ticket items where no additional verification is set up
The decline isn't always visible to you as a merchant β your customer may just see a generic "card declined" error on checkout. You may never know the transaction was attempted unless the customer contacts you.
What makes a large ticket go through reliably
- 3D Secure (3DS2) authentication. Enabling 3D Secure on high-value transactions shifts fraud liability to the card issuer and dramatically reduces the chance the processor's risk engine intervenes. It adds one extra step for the customer but you gain significant protection and transaction approval.
- Strong transaction history on the account. A Stripe account that has processed $200,000 over 18 months with clean chargeback history has a very different risk profile than one processing its first $6,000 transaction.
- Dedicated merchant accounts for high-ticket items. If your average order value is above $2,000 CAD, an aggregated processor is genuinely the wrong tool. Helcim and Moneris allow you to negotiate transaction limits at onboarding, not after you've been declined on a $10,000 furniture sale.
- Customer verification for high-value orders. Requiring a government-issued ID match or signature delivery on large orders creates evidence that helps in disputes and signals to the processor that you're not exposing them to blind fraud risk.
CAD vs USD amounts β this matters more than you think
Many Canadian merchants using US-founded platforms (Stripe, Square, Shopify Payments) have risk systems calibrated primarily in USD. A $5,000 CAD transaction is roughly $3,600 USD as of mid-2026 β that can fall below or above USD thresholds in ways that feel inconsistent to Canadian merchants. If you're seeing large-ticket friction at specific amounts, the CAD/USD conversion may be part of the explanation.
What to Do Before a Hold Hits
Prevention is the only strategy that's actually cheap. Here's the practical checklist:
Documents to have ready before you need them
- Articles of incorporation or business registration (current, not expired)
- Photo ID for all owners with 25%+ stake
- Last 3 months of business bank statements
- Supplier invoices for your top inventory lines
- A recent tracking export or fulfillment summary
- A single PDF with your current website screenshots: homepage, product pages, checkout, refund policy, contact page
Have these ready in a folder on your desktop. When a verification request lands, a merchant who responds within 24 hours with clean documents is reviewed faster than one who takes a week to assemble paperwork.
Account configuration that reduces risk flags
- Enable 3D Secure for transactions above $500 CAD. Most platforms let you set this threshold. Do it.
- Keep your website policies sharp. Refund policy in plain English, realistic shipping timelines (not "ships in 1β3 weeks" when your lead time is actually 8 weeks), a real email and phone number on the contact page.
- Warn your processor before major volume spikes. Stripe, Square, and Shopify Payments all have support channels. Sending a short note β "we have a product launch next Tuesday, expect 3β5Γ normal daily volume" β creates a paper trail that can prevent an automated pause.
- Set a minimum cash reserve outside your processor. The simplest risk mitigation: keep at least 6β8 weeks of operating expenses in your actual business bank account. If your processor freezes you, your business doesn't stop. In Canada with typical small business expense ratios, $15,000β$30,000 CAD is a reasonable starting target for businesses doing $50,000β$100,000 in monthly revenue.
- Keep chargeback rate below 0.5%. Visa and Mastercard's formal remediation programmes start at 0.65β1%. Most processors get uncomfortable well before that. At 0.5% or below, you're in clean territory. Above 1%, expect reserves or worse.
What to Do After a Hold Hits
First 24 hours
- Read the notice. Is this a verification request, a paused payout, a reserve notice, or a termination? These require different responses.
- Don't panic-email support with an essay. Write one clear, professional message: "I received notice of [hold type]. I'm attaching [specific documents]. Please confirm receipt and expected timeline."
- Pull your last 90 days of data before support asks: total volume, chargeback count and rate, refund rate, top products/services, average order value, any recent spikes and their explanation.
- Stop any campaigns that might add volume. The last thing you need while under review is more unusual transaction patterns.
- Move to cash-flow triage immediately. Assume the worst timeline, not the best. Plan for 30 days without payout access even if support says "a few days."
Cash-flow triage for the hold period
- Protect payroll first. Source deductions, EI, CPP β those are your personal liability as a director, not just a business expense. Do not let payroll slip.
- Contact key suppliers early, before you're late. "We're working through a payment processor issue, revised payment date is X" preserves relationships. Going silent doesn't.
- Stop all discretionary spending. Ad spend, software upgrades, new inventory beyond what's committed. Nothing discretionary until cash flow normalizes.
- Consider Interac-based payment alternatives for ongoing sales. If you have trusted B2B customers, EFT/bank transfers, PAD agreements, or Interac e-Transfer for Business can keep revenue moving without the processor intermediary. Not a permanent solution, but useful in a crunch.
- GST/HST float. If you've been treating the tax component of card revenue as operating cash instead of earmarking it separately, a hold exposes that problem immediately. Separate your tax collections from operating cash, full stop.
Escalation options (limited but real)
You can't call the Financial Consumer Agency of Canada about a fund hold β FCAC covers bank customers, and processors are not banks. But you have some leverage:
- Your provincial consumer protection office if you believe the hold is wrongful under the terms you agreed to. Results are slow but the complaint on file sometimes moves things.
- FINTRAC if you believe the hold involves AML compliance concerns β they regulate the AML side of processors. Not useful for routine holds.
- Small claims court for amounts under your province's limit (typically $25,000 CAD in Ontario, $35,000 in BC). Filing a small claims action doesn't guarantee recovery, but it signals you're serious. Some processors settle rather than contest.
- A lawyer's letter for large amounts. If $50,000+ is frozen and you believe it's wrongful, a formal legal notice from a lawyer is worth the $300β$500 in professional fees. Most processors will respond to a letter when they won't escalate a ticket.
Which Processors Are Lowest-Risk for Holds?
| Processor | Account Model | Hold Risk Level | Best For |
|---|---|---|---|
| Helcim | Dedicated merchant account | Low for normal-risk merchants | Canadian SMBs that want transparent pricing and the fewest surprise freezes. Interchange-plus pricing. Strong hold-avoidance track record for merchants with clean history. |
| Moneris | Dedicated merchant account | Low-medium | Established Canadian merchants with in-person volume. More contract friction upfront, fewer surprise holds later. Better supported if you're doing $30,000+ CAD/month with in-person component. |
| Stripe | Aggregated | High for volume spikes, pre-orders, subscriptions, high-ticket CNP | Developer-built businesses with predictable flat volume and strong technical teams who can manage risk tooling directly. Not great if you can't afford a multi-week freeze. |
| Square | Aggregated | Medium-high | In-person retail and restaurants with fairly stable volume. Weaker fit for high-ticket items or mixed online/in-person behaviour. |
| Shopify Payments | Aggregated via Stripe | High for e-commerce with fulfillment lag | Convenient but carries the same structural risks as Stripe. If you use Shopify heavily, fine as a starter. Consider switching payment rails once you hit $500K+ annual revenue and can't absorb a freeze. |
The CAD-Specific Wrinkles
Interac reduces card-not-present risk
One hold-avoidance strategy that's genuinely Canadian: shift some customer payments to Interac-based bank transfers where you have established customer relationships. Card-not-present chargebacks are one of the biggest sources of holds for e-commerce merchants. Interac direct payment eliminates chargeback exposure entirely for those transactions. Read the Interac Online Payments guide for the details on which processors support it and how the economics work.
Quebec and bilingual compliance
If you sell into Quebec at any scale, your cancellation, refund, and renewal policies need to meet Office quΓ©bΓ©cois de la langue franΓ§aise requirements and Quebec Consumer Protection Act standards. Processors see Quebec-specific disputes as a distinct risk category. A clean bilingual refund policy that meets OPC standards can materially reduce your dispute rate from Quebec customers β and therefore your hold risk.
CRA timing doesn't pause
Monthly GST/HST remitters file by the last day of the following month. Quarterly filers have 30 days after quarter end. Payroll remittances have their own schedule. None of these deadlines extend for processor holds. Late remittances attract 3β10% penalties plus daily compounding interest. Keep CRA obligations funded from a dedicated account that processor holds can't touch.
Seasonal volume is normal β but you need to explain it
Canadian businesses often have sharply seasonal revenue profiles: patio season, ski season, tax season, construction season, holiday retail. A processor risk system trained on global averages may flag a normal Canadian seasonal spike as anomalous. Get ahead of this: contact support before the surge and note the seasonality pattern explicitly. A paper trail saying "our spring volume has been 4Γ winter for the last 3 years" is harder for an automated system to ignore than silence followed by a spike.
Our Take
Fund holds are a structural feature of how aggregated processors work, not a bug or an anomaly. They shift liability to the merchant and let platforms onboard anyone quickly without taking on real underwriting risk at signup. For a startup doing $5,000/month, that tradeoff makes sense. For an established Canadian business with employees, tax obligations, and supplier relationships, a surprise 30-day freeze is a serious operational threat.
- If you're just starting out: Stripe or Shopify Payments is fine. Keep volumes modest, documentation current, and build operating cash reserves as you grow.
- If you're doing $20,000β$50,000 CAD/month: start evaluating Helcim now. The interchange-plus pricing often saves money at this volume anyway, and the hold risk is meaningfully lower.
- If you're doing $100,000+ CAD/month and can't absorb a freeze: you should already have a dedicated merchant account. If you don't, the next freeze will be the reason you finally switch.
- If you've already been hit: follow the 24-hour triage above, build your cash reserves, and fix the setup before the next review cycle hits.