How Pre-Authorized Debit (PAD) Works
Pre-Authorized Debit operates as a "pull" payment: the payee initiates the transaction rather than waiting for the payer to push funds. This distinction makes PAD ideal for subscription billing, insurance premiums, and utility payments where collection reliability matters more than immediacy. In Canada, the process flows through the Automated Clearing Settlement System (ACSS), governed by Payments Canada Rule H1.
Create the PAD Agreement
Before any funds can move, you must obtain a signed PAD agreement (also called a mandate) from the payer. This document must include the payment amount or method of calculation, frequency, start date, and the payer's right to cancel or dispute. Digital acceptance is valid — a checkbox during checkout or an e-signed form both satisfy Payments Canada requirements, provided the mandate is stored and producible on request.
Store the Mandate Securely
The signed mandate must be retained for a minimum of three years after the final debit under the agreement. If a dispute arises, you must produce proof of authorization within the timeframe set by your financial institution. Store mandate data encrypted, link it to each individual transaction record, and log the IP address and timestamp of digital acceptances.
Validate the Bank Account
Before submitting your first debit, verify that the account details — institution number, transit number, and account number — are correct using a bank account verification service or a micro-deposit challenge. Invalid account details are the leading cause of avoidable PAD returns and can trigger processor return-rate penalties if they occur at scale.
Submit the Debit File
On or before the debit date, your payment processor submits a debit file to the ACSS in CPA-005 format. Files must be received before the processor's submission cutoff — typically early afternoon on banking days. Most processors accept same-day submissions for next-day processing if volumes and merchant risk profiles permit. Confirm cutoff times contractually before planning your billing run schedule.
Settlement and Return Monitoring
The ACSS routes the debit instruction to the payer's bank. Standard settlement completes in 2–3 business days (T+2 or T+3). Funds appear in the payee's account after settlement, though some processors offer provisional credit earlier for low-risk merchants. Monitor return reports daily during the settlement window — NSF returns and account-closed returns arrive asynchronously and require immediate action to avoid cascading disputes.
Why Pre-Authorized Debit (PAD) Matters
For businesses that rely on recurring payments, PAD is one of the most cost-effective and reliable payment rails available in Canada. It eliminates card expiry risk, reduces involuntary churn, and gives finance teams predictable cash flow that card-based billing cannot match. The economics are compelling enough that high-volume billers routinely prioritize PAD over cards for their core revenue flows.
PAD transaction fees typically range from $0.25–$1.50 per transaction, compared to 1.5–3.5% of transaction value for credit cards. On a $500 monthly subscription, that difference represents a cost saving of 60–80% per payment — material at any volume above a few hundred customers. PAD also shows superior authorization rates: industry data shows PAD return rates average just 1–3% for well-managed merchant programs, while card-not-present decline rates frequently exceed 10–15% due to fraud filters, issuer risk scoring, and expired credentials. For SaaS companies and insurers processing thousands of monthly debits, even a one-percentage-point improvement in success rates translates directly to recovered revenue without a single sales motion.
Adoption is accelerating across the Canadian market. Payments Canada reports that the volume of electronic funds transfers — which includes PAD — has grown at a compound annual rate of approximately 6% over the past five years as businesses migrate away from paper cheques and manual wire transfers. The shift is driven by cost pressure, audit trail requirements, and the availability of API-connected payment processors that make PAD integration as straightforward as a card gateway.
PAD is Canada-specific
Pre-Authorized Debit rules are set by Payments Canada. If you operate in the US, the equivalent mechanism is ACH debit. In Europe, look at SEPA Direct Debit, which operates under a similar mandate framework but with different dispute windows and clearing timelines.
Pre-Authorized Debit (PAD) vs. Direct Debit
PAD and direct debit describe the same fundamental mechanic — a creditor pulling funds from a debtor's bank account — but the terminology, regulatory frameworks, and operational details vary significantly by region. The table below compares the most important dimensions for merchants evaluating multi-country bank debit strategies.
| Dimension | PAD (Canada) | SEPA Direct Debit (Europe) | BACS Direct Debit (UK) |
|---|---|---|---|
| Governing body | Payments Canada | European Payments Council | Pay.UK |
| Clearing network | ACSS | SEPA Clearing | BACS |
| Settlement time | T+2 to T+3 | T+1 to T+3 (CORE) | T+3 (standard) |
| Personal dispute window | 90 days | 8 weeks (unauthorized) | 13 months (unauthorized) |
| Business dispute window | 10 business days | No separate B2B window (SDD B2B: 0 days post-settlement) | Not separately defined |
| Mandate held by | Payee (merchant) | Payee (merchant) | Payee or bank (DDI) |
| Pre-notification required | Yes (per agreement terms) | Yes (minimum 14 days, reducible by agreement) | Yes (minimum 10 days, reducible) |
| Maximum transaction limit | None (processor-set) | None (scheme-level) | None (scheme-level) |
The most consequential operational difference for international merchants is the dispute window. Canada's 90-day personal PAD window is shorter than the UK's 13-month window but longer than SEPA CORE's 8-week window for authorized transactions. These differences directly affect how you structure refund reserves and reconciliation workflows across regions.
For merchants comparing PAD to a SEPA mandate, note that SEPA uses two distinct schemes — CORE for consumers and B2B for businesses — with separate mandate flows and liability models, while Canada's PAD consolidates both under Rule H1 with differentiated dispute windows and a unified mandate format.
Types of Pre-Authorized Debit (PAD)
PAD is not a monolithic product — it comes in variants that carry different risk profiles and compliance obligations. Choosing the wrong type for your billing relationship can expose you to unexpected disputes or mandate compliance failures.
Personal PAD applies when the payer is an individual consumer. The 90-day dispute window governs, meaning the payer can request a reversal from their bank for up to 90 days after the debit date if the amount or timing was not authorized as agreed in the mandate. Merchants processing personal PAD volume should maintain dispute reserves calibrated to their average debit size and volume, and should invest in strong mandate documentation to defend legitimate charges.
Business PAD applies when the payer is a corporation, partnership, or other non-individual entity. An authorized officer of the business must sign the mandate. The dispute window shortens to 10 business days, giving merchants significantly more settlement certainty. Business PAD is the preferred option for B2B SaaS, fleet management, professional services, and enterprise software billing, where the shorter contestability window reduces working capital pressure.
Recurring PAD covers pre-scheduled debits at fixed or variable amounts on a defined cadence — weekly, monthly, quarterly, or annually. The original mandate must specify the frequency and the method by which the amount is determined. Material changes to amount or frequency require a new mandate or advance written notice to the payer.
Sporadic (One-Time) PAD covers individual, non-recurring debits authorized for a specific transaction. These are common in e-commerce checkout flows where a customer authorizes a single bank debit at the point of purchase rather than setting up ongoing billing. One-time PADs still require a compliant mandate for each transaction.
Best Practices
PAD is low-cost but operationally demanding. The mandate lifecycle, return management, and compliance requirements create failure points that card processing does not have. The guidance below addresses the most common issues by role.
For Merchants
- Obtain compliant mandates before the first debit. A PAD submitted without a valid, complete mandate is returnable at any time — there is no settlement finality without proof of authorization. Use a mandate template reviewed by Canadian payments counsel and audit it annually against Payments Canada rule updates.
- Send pre-debit notifications. Notify customers of the upcoming debit amount and date at least 10 days in advance, or the shorter period specified in your agreement — but never fewer than 3 days. Pre-notification reduces disputes significantly and is a Payments Canada compliance requirement, not a courtesy.
- Track return reasons by code. ACSS return codes tell you whether a return was NSF, account closed, payment stopped, or authorization revoked. NSF returns may warrant a retry strategy after 5 business days; "authorization revoked" returns require immediate mandate cancellation and billing suspension.
- Offer a prominent cancellation path. Payments Canada requires your mandate to clearly explain how to cancel. Make it easy with a dedicated email address or self-serve web form — a frictionless cancellation process reduces chargebacks and regulatory complaints.
For Developers
- Integrate bank account verification (BAV) at mandate capture. Use instant bank verification via open banking connections or micro-deposit verification before storing account details. This reduces invalid account returns by 40–60% in practice and protects your processor return-rate standing.
- Build idempotent debit submission. Network timeouts during file submission can cause duplicate debits if retried naively. Assign a unique reference to each debit, persist submission state, and check status before retrying — never submit a file twice without confirming the first submission failed.
- Expose mandate status as a first-class entity in your data model. Track mandate state — active, paused, cancelled, expired — separately from payment status. A cancelled mandate must hard-block future debit submissions even if a payment is already scheduled in the queue.
- Handle ACSS return codes programmatically. Map each return code to a defined action: NSF triggers a configurable retry after 5 business days (maximum 2 retries per billing cycle); account closed suspends billing and notifies the merchant; payment stopped flags the account for manual review before any retry.
Common Mistakes
1. Collecting incomplete mandate information. Mandates that omit the debit amount, calculation method, frequency, or cancellation terms are non-compliant under Payments Canada Rule H1. If a payer disputes a debit and you cannot produce a complete, signed mandate, you will lose automatically regardless of the merits of the charge.
2. Skipping pre-debit notifications. Many merchants treat pre-notification as optional because the dispute risk feels abstract until it materializes. It is a Payments Canada requirement, and failing to send it gives payers grounds to dispute otherwise legitimate debits within the personal PAD window. Automate notifications as part of your billing run, not as an afterthought.
3. Submitting debits after mandate cancellation. When a customer cancels their PAD agreement, any subsequent debit is unauthorized and must be reversed on demand. Without a system that hard-stops all scheduled debits immediately upon a cancellation event, you face regulatory complaints, bank relationship damage, and potential fines.
4. Ignoring return rate thresholds. Payment processors set return rate limits — typically 1–3% of submitted volume. Exceeding these limits triggers increased fees, volume caps, or account termination. Return rates should be monitored weekly and investigated immediately when they spike above baseline.
5. Using a vague mandate for variable-amount charges. If your billing amounts fluctuate significantly — for example, usage-based billing where the monthly charge ranges from $10 to $10,000 — a generic "variable amount" mandate may not satisfy the "reasonable notice" standard if the actual charge surprises the payer. Add amount-range disclosures and consider sending individual pre-debit notices for charges above a defined threshold.
Pre-Authorized Debit (PAD) and Tagada
Tagada is a payment orchestration platform that connects merchants to multiple PAD processors through a single API, removing the operational burden of managing direct processor relationships. Rather than integrating one Canadian payment processor and inheriting its specific return-rate limits, settlement timelines, and file format requirements, merchants using Tagada can route PAD transactions across providers — automatically failing over to a secondary processor if the primary rejects a file submission or exceeds capacity during high-volume billing runs.
PAD orchestration with Tagada
Tagada normalizes ACSS return codes across all connected processors into a unified webhook schema, so your engineering team writes return-handling logic once rather than once per processor integration. Mandate records, pre-debit notification logs, and return histories are stored centrally, making compliance audits significantly faster. Connect your first PAD processor in minutes via the Tagada dashboard — no custom CPA-005 file handling required on your end.
For merchants expanding from Canada into the US or Europe, Tagada's orchestration layer also handles the transition to bank transfer rails in other regions, applying the same mandate lifecycle management and return-code normalization across ACH, SEPA, and BACS payment schemes. This means a single integration supports your full international bank debit strategy as your business scales beyond Canada.