Everyone prices the 2.9% on the payments that go through. Nobody prices the payments that don't — the expired cards, the soft declines, the stack of add-on fees riding on top of the headline rate. A recurring setup has two costs: the fee stack and the failure rate. This guide handles both, in setup order.
The full fee stack (map it before you commit)
| Layer | What it costs | Notes |
|---|---|---|
| Base processing | e.g. 2.9% + C$0.30 per successful charge (Stripe Canada, checked 2026-10-11) | The headline rate — only the first layer |
| Billing platform | e.g. 0.7% of billing volume (Stripe Billing) | Charged on top of processing, every month |
| Invoicing | e.g. 0.4% per paid invoice | Applies if you invoice on top of billing |
| Fraud screening | e.g. $0.02 per screened transaction | Small per unit, real at volume |
| Disputes | e.g. $15 per dispute, non-refundable | Plus the original processing fee, which isn't returned on refunds |
Per-invoice tools show the same compounding from the other direction: on a $500/month retainer, PayPal Invoicing at ~3.49% + 49¢ costs ~$17.94/month ($215/year), Square Invoices at ~3.3% + 30¢ costs ~$16.80/month — per client, every month, for as long as they stay. Tools that let you connect your own gateway let you negotiate the rate instead of accepting the tool's.
The 8-step setup procedure
- Price the whole stack on your expected volume (table above) — not just the headline processing rate. If the add-ons exceed ~20% of base processing, question each one.
- Store cards as tokens, never numbers. Use your processor's vault or network tokenization. Raw card storage drags the full weight of PCI DSS onto you.
- Enable the account updater on day one: Visa Account Updater and Mastercard ABU. This single switch typically cuts overall failures by ~25% in the first billing cycle — expired and reissued cards update silently.
- Turn on network tokenization alongside it, so underlying card renewals propagate without customer action.
- Build the dunning sequence before launch: Day 0 — retry plus an email with a payment-update link; Day 3 — second retry plus SMS; Day 7 — final retry with a clear cancellation warning. Cap retries at 3 spread across 7 days.
- Separate soft declines from hard declines in your retry logic. Insufficient funds gets retried in a few days; expired or stolen cards trigger the update flow, never another retry — repeated retries on hard declines raise chargeback risk.
- Offer a backup payment method at signup and a one-click update portal in every dunning message. Friction here is churn.
- Set the failure-rate dashboard: under 2% of monthly charges failing is healthy; over 4% means missing updater coverage or weak retry logic — fix the setup, not the customers.
What success looks like: updater and tokenization on, dunning firing automatically, failure rate under 2%, and no customer ever discovering their card expired via a cancellation email.
The worked math: a $10,000 MRR stack
The setup: $10,000/month recurring, ~300 transactions.
Base processing at 2.9% + $0.30: ~$387. Billing platform at 0.7%: $70. Screening at $0.02 × 300: $6. Total before disputes: ~$463/month — the add-ons are roughly 19% on top of base processing.
The verdict: the stack is the price, not the headline rate. And every failed payment the updater + dunning recovers is revenue at nearly zero marginal cost — which is why setup order matters more than vendor choice.
Operators feel this in the margins. One service-business owner, quoted on the cost of absorbing card fees before adding a surcharge to recurring agreements, put it plainly: the 1.5% they used to eat “was real money… roughly 1.5 points straight to the bottom line — in a margin this thin, that's meaningful.” The same logic applies to the failure side: every recovered renewal drops straight to the bottom line, which is why the updater switch and the dunning sequence belong in the launch checklist, not the optimization backlog.
FAQ
What is a good failed-payment rate for subscriptions?
Under 2% of monthly recurring charges is healthy. Above 4% signals missing card-updater coverage or weak retry logic — fix the setup.
Should I retry a failed payment immediately?
Retry soft declines (insufficient funds, temporary bank issues) on a spaced schedule; never blindly retry hard declines (expired, stolen, closed accounts) — route those to the update flow.
What does the account updater actually do?
Visa Account Updater and Mastercard ABU automatically refresh stored card details when cards are reissued or replaced — the renewal charge goes through without the customer doing anything. It's the fastest single change that lowers failure rates.