PAD developer guide

Pre-authorized debit (PAD) API for Canada: agreements, recurring debits and returns in one integration

A pre-authorized debit (PAD) API lets your software withdraw payments from a customer's Canadian bank account on a set schedule, once that customer has authorized a PAD agreement under Payments Canada Rule H1. TIB Finance, the Canadian sovereign payment processor, gives you that API ready to use: digital PAD agreements signed online, recurring debits from daily to annual, and every NSF or return sent to your system by webhook.

Updated November 22, 2026 • Registered PSP, Bank of Canada • 1,000+ businesses • $600M+ in annual volume • PCI DSS

Definition

What is a pre-authorized debit (PAD) API?

A pre-authorized debit is a pull payment: your business, the payee, debits the payor's bank account under a standing authorization. A PAD API exposes that process to your code. Your platform saves the customer's bank account, records the authorization, schedules the debits and receives the outcome of each one, with no paper forms and no void cheques.

In Canada, PADs clear through the Automated Funds Transfer (AFT) system, the same rails as EFT, and follow Payments Canada Rule H1. The rule recognizes four categories (personal, business, funds transfer and cash management), and a PAD can be fixed or variable, one-time, at set intervals or sporadic.

Rule H1 was amended, effective July 27, 2026, to remove paper PADs, which will no longer be accepted for clearing as of December 1, 2028. With TIB Finance, your PADs are digital from the first signature.

Rule H1 at a glance

What does Rule H1 require for personal and business PADs?

RequirementPersonal PADBusiness PAD
What it pays forConsumer payments: utilities, insurance, memberships, loans, other consumer goods or servicesGoods or services tied to the payor's business: supplies, franchise fees, leases
PAD agreementWritten or recorded, authorized by the payor, with every Appendix II elementSame
Confirmation10 calendar days before the first debit, or within 5 days after it if the payor waives the delaySame
Pre-notification10 calendar days before a change in amount or date, or a variable-amount debit; can be waivedSame
Reimbursement windowUp to 90 calendar days after the debitUp to 10 business days after the debit
No agreement at all90 calendar days after posting90 calendar days after posting
Cancellation by the payorAny time; PADs stop within 30 calendar days at mostSame
AFT transaction code260 to 272, 323 or 330 to 599700 to 749
RecordsAgreement and audit trail kept 12 months after the last debitSame

Source: Payments Canada, Rule H1, Pre-Authorized Debits, sections 5 and 15 to 31, Appendix II.

The agreement

What must a PAD agreement contain?

Rule H1 defines the payor's PAD agreement as a continuing but revocable authority, written or otherwise recorded, and signed or otherwise authorized by the payor. "Written" includes electronic documents, so an online agreement qualifies. The payor's identity must be verified with commercially reasonable methods. Appendix II lists the mandatory elements:

  • Date and signature or authorization.
  • Authority to debit the account the payor specifies.
  • PAD category: personal, business or funds transfer.
  • Amount and timing: fixed or variable; weekly, monthly, on set dates, on a specified event or sporadic.
  • Cancellation terms: revocable at any time with a notice period of 30 days or less, and a sample cancellation form available from the payor's financial institution or at payments.ca.
  • Payee contact information for questions and recourse.
  • The recourse statement, word for word.

The mandatory recourse statement reads: "You have certain recourse rights if any debit does not comply with this agreement. For example, you have the right to receive reimbursement for any debit that is not authorized or is not consistent with this PAD Agreement. To obtain more information on your recourse rights, contact your financial institution or visit www.payments.ca."

Sporadic PADs need the payor's authorization for each debit, with no waiver possible. A one-time PAD agreement covers a single debit. When a payment service provider collects for the business that sells the goods or services, the agreement must describe that arrangement.

Notice periods

How much notice do you have to give before a PAD?

  • Confirmation: at least 10 calendar days before the first debit, send a copy of the agreement or a summary of its terms. If the payor waives or shortens that delay, send it within 5 calendar days after the first debit.
  • Pre-notification: for PADs at set intervals, give the amount and date at least 10 calendar days before any change in amount or date, and before every variable-amount debit after the first.

No pre-notification is needed for a decrease caused by lower taxes, or for a change the payor requested when the agreement allows it. The parties can also reduce or waive pre-notification in a clause displayed prominently, in bold, highlighted or underlined. For variable amounts, build the 10-day notice into your billing cycle.

Personal or business

What is the difference between a personal PAD and a business PAD?

A business PAD pays for goods or services tied to the payor's commercial activity and carries an AFT transaction code from 700 to 749. A personal PAD covers consumer payments such as mortgage instalments, utility bills, insurance premiums, loans and other consumer goods or services.

The distinction matters for disputes: 10 business days for a business payor, 90 calendar days for a consumer. A personal PAD wrongly coded as business keeps its 90-day window, so classify each agreement correctly at signup.

Reimbursement rights

What reimbursement rights does the payor have?

Under Rule H1, the payor's financial institution must accept a reimbursement claim when:

  • the PAD was not drawn in accordance with the PAD agreement;
  • the PAD agreement had been revoked;
  • a required confirmation, pre-notification or notice was not given.

Within those windows, the institution reimburses the payor immediately, on a best-efforts basis, and the payee's side must honour the return. With no PAD agreement at all, the window is 90 calendar days after posting for every category.

A debit returned for non-sufficient funds (NSF) or funds not cleared can be re-presented electronically once, for the same amount, within 30 calendar days, with no interest, NSF charges or other fees added. See our guides to NSF and returned payments and EFT return codes.

The TIB Finance PAD API

How does TIB Finance handle PAD agreements, recurring debits and returns?

TIB Finance gives you the full PAD lifecycle through one API and one merchant portal. Your developers ship collections, not banking plumbing.

Digital PAD agreements

Customers sign the PAD agreement online, through the secure Drop-In form or a payment link. If a payment flow requires consent that is missing, the API answers "PPA consent needed" instead of debiting.

Recurring PADs on any schedule

One CreateFreeOperation call schedules a debit daily, weekly, every two weeks, monthly, quarterly, twice a year or yearly, by API or from the merchant portal. Billing a variable amount? Schedule each debit on its own (TransferFrequency Once) after the 10-day pre-notification.

Returns reported by webhook

Each PAD moves through Validation, Transmission, StatusCheck and Payback, and every step reaches your webhook. If an issue occurs (NSF, opposition, closed account), the event arrives with its result code: DescriptionCode 3 (NoFund), 5 (Opposition) or 4 (AccountError), plus an alert email.

Returns can arrive late: a consumer can dispute a PAD up to 90 calendar days after the debit, a business up to 10 business days. Monitor consumer debits for 90 days and business debits for 14 days: call ListExecutedOperations with DateType set to LastModifiedDate and every late NSF or opposition lands in your ledger. After an NSF, you stay in control. You get the webhook and an alert email, the recurring schedule carries on with the next occurrence, and you choose the next move: relaunch the failed debit once with RelaunchMerchantFailedTransfer, within the Rule H1 limit, or send the customer an Interac request for money or a payment link.

Which TIB Finance API calls map to each step?

StepTIB Finance API callWhat it does
Enrol the payorCreateCustomerLinks the customer to your CustomerExternalId
Save the bank accountCreateDirectAccountPaymentMethodSaves institution, transit and account numbers
Collect consentDrop-In with DirectAccountPPA, or CreatePayment with AskForCustomerConsentThe customer authorizes the PAD online
Schedule the debitsCreateFreeOperation, or CreateBill + CreatePaymentOne-time or recurring PAD with CreateFreeOperation; a debit tied to an invoice with CreateBill + CreatePayment
Track every statusWebhooks, ListExecutedOperationsEach step, including late NSFs and oppositions
Relaunch a failureRelaunchMerchantFailedTransferRelaunches it when you decide
Stop the scheduleGetRecuringTransfers, DeleteRecuringTransferCancels future debits
Code

What does a recurring PAD look like in code?

Every call is an encrypted POST to /Data/{method} with a session token valid for 2 hours, and the official SDKs handle the encryption and key exchange for you. Here are the fields for a monthly rent debit of $1,450 on a tenant's bank account (sample values):

// 1. Save the tenant's bank account
POST /Data/CreateDirectAccountPaymentMethod
{
  "SessionToken": "session-guid",
  "CustomerId": "customer-guid",
  "IsCustomerAutomaticPaymentMethod": true,
  "Account": {
    "AccountName": "Tenant chequing",
    "Owner": "Jane Tremblay",
    "BankNumber": "815",
    "InstitutionNumber": "30000",
    "AccountNumber": "1234567"
  },
  "Language": 2
}

// 2. Schedule the PAD: TransferType 3 = FreeCollection, TransferFrequency 4 = Monthly
POST /Data/CreateFreeOperation
{
  "SessionToken": "session-guid",
  "MerchantId": "merchant-guid",
  "CustomerId": "customer-guid",
  "PaymentMethodId": "payment-method-guid",
  "TransferType": 3,
  "TransferFrequency": 4,
  "Amount": 1450.00,
  "TransactionDueDate": "2027-01-01",
  "ReferenceNumber": "LEASE-204",
  "Language": 2,
  "IdempotencyKey": "lease-204-2027-01"
}

Send an IdempotencyKey on every call that moves money: repeating a call with the same key and the same values returns the original response instead of debiting twice. Use a new key for each new debit. To change a schedule, cancel it with DeleteRecuringTransfer and create the new one after the required pre-notification. Official SDKs for .NET, Node.js, Python, Java, PHP and JavaScript wrap these calls. See the API documentation, the webhook guide and the API use cases.

How to do it with TIB Finance

How do you launch PAD collections with TIB Finance?

1

Open your account

Create your account online in 30 seconds. The TIB Finance team then configures your webhook endpoints with you.

2

Build in the sandbox

Get your API credentials by email, then simulate successful debits, NSF returns and webhooks before going live.

3

Enrol your payors

Send the Drop-In form or a payment link. Each customer authorizes the digital PAD agreement and saves their bank account.

4

Collect and reconcile

Schedule the debits, receive each status by webhook and match every payment to the right invoice through your own reference numbers.

Multi-tenant platforms

Building a platform? Collect PADs for your own clients

TIB Finance is built for B2B and for multi-tenant payment processing. If you run property management software, a billing platform or a SaaS product, you onboard your own clients, your tenants or sub-merchants, on top of TIB Finance and run their pre-authorized debits under your own offer. TIB Finance is proven and rigorous, and its team works for its clients and its partners. See the partner program or how our team integrates TIB Finance with you.

Trust

Why run your PAD collections through a registered Canadian processor?

TIB Finance is a Canadian sovereign payment processor headquartered in Montréal, Québec (9372-2544 Québec inc.). Since September 28, 2026, it has been registered with the Bank of Canada as a payment service provider under the Retail Payment Activities Act (RPAA). View the official listing or read what PSP registration means for your business.

  • Security: PCI DSS, SOC 1 and SOC 2 Type 2.
  • Scale: more than 1,000 businesses and over $600 million in payment volume a year.
  • One platform: PAD, EFT, Interac, cards and TIB's proprietary instant payment system, from a single API.
FAQ

What do developers ask about PAD APIs in Canada?

What is a pre-authorized debit (PAD) API?

A PAD API lets your software debit a customer's Canadian bank account on a schedule once the customer has signed a PAD agreement. With TIB Finance, one API saves the account, records consent, schedules one-time or recurring debits and reports each result by webhook.

Which rule governs pre-authorized debits in Canada?

Payments Canada Rule H1. It sets the PAD agreement content, the notice periods, the reimbursement windows, cancellation and record keeping.

How many days' notice is required before a PAD?

A confirmation at least 10 calendar days before the first debit, and a pre-notification at least 10 calendar days before any change in amount or date and before every variable-amount debit. The payor can waive or shorten the confirmation delay, and both parties can reduce or waive pre-notification in a prominently displayed clause.

How long can a customer dispute a PAD?

Up to 90 calendar days after the debit for a personal PAD, and up to 10 business days for a business PAD. If no PAD agreement existed, the window is 90 calendar days after posting.

Can a PAD agreement be signed online?

Yes. Rule H1 accepts written or otherwise recorded agreements, and written includes electronic documents. TIB Finance customers sign the PAD agreement online through the Drop-In form or a payment link.

How does TIB Finance report an NSF on a PAD?

The failed debit reaches your webhook with an NSF result code and you get an alert email. You stay in control: relaunch it once with RelaunchMerchantFailedTransfer, or send an Interac request for money or a payment link.

Can I re-present a PAD returned for NSF?

Once. Rule H1 allows one electronic re-presentment, for the same amount, within 30 calendar days of an NSF or funds-not-cleared return, with no interest or fees added.

How do I test PAD collections before going live?

Open a free TIB Finance sandbox and get your API credentials by email. Create customers, sign PAD agreements, schedule recurring collections, simulate an NSF return and receive the matching webhooks.

Is TIB Finance a registered payment service provider?

Yes. TIB Finance has been registered with the Bank of Canada as a payment service provider under the Retail Payment Activities Act since September 28, 2026. It is a Canadian sovereign payment processor based in Montréal.

Talk to our team

Ready to automate your pre-authorized debits? Let's talk.

Tell us how you collect today. A real, bilingual team works with you and stays with you after go-live, from the PAD agreement to reconciliation. TIB Finance sends people, and integration is free for eligible businesses. Developers can start in the free sandbox right away.