Pre-Authorized Debits for Multi-Tenant Platforms: Mandates, Returns and Fees per Tenant
Table of Contents
- How does a multi-tenant platform collect PAD for its clients?
- Where do PAD agreements live when you collect for many tenants?
- How do you schedule recurring PADs for each tenant?
- How are PAD returns routed to the right tenant?
- How do you set NSF fees and limits per tenant?
- What do VoPay and Zum Rails offer for PAD?
- How fast can your platform launch PAD with TIB Finance?
- Common Questions
A multi-tenant platform collects pre-authorized debits (PAD) for its clients by setting up each tenant, meaning each client of the platform, with its own merchant and bank account, and by keeping that tenant's payers and their PAD agreements underneath it. With TIB Finance, one integration schedules every debit, settles each PAD in 1 to 2 business days and reports every step to your webhook with the tenant's MerchantId, up to a Payback event when a payment comes back. Fees and limits, such as the NSF fee, are set for each tenant.
TIB Finance is built for B2B and for multi-tenant payment processing. Property management software, lending platforms, billing platforms and SaaS products build their own platform on top of TIB Finance, with their own clients as tenants and sub-merchants.
In short: one TIB Finance client for your platform, one service per tenant, one merchant per bank account. Agreements and payers sit under the tenant's merchant, and every webhook event carries the MerchantId.
Launching PAD for your tenants? Talk to our team: we set it up with you.
How does a multi-tenant platform collect PAD for its clients?
With a hierarchy built for it. In TIB Finance, your platform is the client. Each of your tenants is a service, created through the API with CreateSubClient, with its own name, language and currency (CAD or USD). Each service holds its own merchants, its payer customers and their payment methods. A merchant is one destination bank account, so every PAD lands in the bank account of the merchant it belongs to.
| On your platform | In TIB Finance | What it holds for PAD |
|---|---|---|
| Your company | Client | Your integration and the services of all your tenants |
| Each tenant (a property manager, a lender, a software customer) | Service | Its own name, language and currency, its fee settings and its limits |
| Each bank account of a tenant (a building, a loan portfolio) | Merchant | One destination bank account and the MerchantName payers see |
| Each payer (a resident, a borrower, a subscriber) | Customer | The payer's details and preferred language, English or French |
| Each payer's bank account | Payment method | The saved bank account each debit draws on |
Each merchant can also carry its ID from your ERP or CRM (ExternalSystemId), which GetMerchantsByExternalId finds again. Read the multi-tenant payment processing overview, the multi-tenant payment architecture guide and the sub-merchant onboarding API guide.
Where do PAD agreements live when you collect for many tenants?
Under each tenant, with the payer who signed them. The payer is a customer of the tenant, saves a bank account and authorizes 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. Payers recognize who is collecting, because MerchantName is the name shown on bills and payment pages, and payment pages can carry your colors and logo.
The agreement itself follows Payments Canada Rule H1. Our guide to PAD rules in Canada covers it in full: seven mandatory elements, a confirmation at least 10 calendar days before the first PAD, 10 calendar days' pre-notification before variable amounts and changes, and records kept at least 12 months after the last PAD. One clause matters for platforms: when a payment service provider is the payee, the agreement must describe its arrangement with the business that supplies the goods or services.
For the legal side of recurring billing, read recurring payments in Canada and the law and our pre-authorized debits guide.
How do you schedule recurring PADs for each tenant?
From your software, on the tenant's merchant. 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 after the 10-day pre-notification. Each debit carries the MerchantId of the tenant's merchant and your own reference number, and settles in 1 to 2 business days (T+1 to T+2).
Any schedule
One-time or recurring, from daily to yearly.
Idempotent calls
Send an IdempotencyKey on every call that moves money: the same key and values return the original response instead of debiting twice.
Your references
Tie each debit to your reference number, and each merchant to your ERP or CRM through its ExternalSystemId.
Stop on request
GetRecuringTransfers and DeleteRecuringTransfer cancel future debits when a payer revokes the agreement.
TIB Finance also runs EFT, Interac and credit cards, plus instant payments in seconds, 24/7/365, on its own system. The allowed payment methods are set per service, so each tenant gets the methods you enable for it. See payment methods, the PAD API and recurring payments.
How are PAD returns routed to the right tenant?
By the MerchantId on every webhook. Each TransactionEvent reports one of four steps, Validation, Transmission, StatusCheck and Payback: a successful PAD reaches your webhook at the first three, and Payback arrives when a payment comes back. Each TransactionEvent carries its target, its direction (Collect, for a PAD), its step, its status, a DescriptionCode, the amount, the MerchantId and the MerchantName, so your system posts each event to the right tenant's ledger.
A return can come back after a debit succeeds. TIB Finance validates each payment during a validation period: 3 months for personal accounts and 2 weeks for business accounts. If an issue occurs in that period, such as an NSF, an opposition or a closed account, you receive a Payback webhook event. NSFs, account errors and oppositions return a result code, plus an alert email.
After an NSF, you stay in control: 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 payer an Interac request for money or a payment link. For a report per tenant, ListExecutedOperations filters by ServiceId and MerchantId. Rule H1 sets the windows your tenants plan around:
- Personal PAD: the payor can claim a refund up to 90 calendar days after the debit.
- Business PAD: the payor can claim a refund up to 10 business days after the debit.
- NSF retry: re-present the debit once, for the same amount, within 30 calendar days, with no added fees.
Codes and fixes are in our guides to NSF and returned payments and EFT return codes. The full event format is in the webhook documentation.
How do you set NSF fees and limits per tenant?
In each tenant's service settings. Every service carries its own fee grid and its own rules, so each tenant runs on its own terms from the same integration:
| Set per service (tenant) | What it covers |
|---|---|
| Transaction fees | Credit card, debit and instant transfer, each with a mode, a percentage and a fixed amount |
| Return and failure fees | NSF fee, NSF file fee, stop-payment fee, card failure fee and Interac return fee |
| Other fees | Credit and debit convenience fees, cancellation fees, and Interac deposit and collection fees |
| Limits | Collection and deposit limits, per operation and per day, plus limits per bank account |
| Risk settings | An NSF cushion and the merchant deposit delay |
| Payment methods | The methods allowed for collection and for deposit |
Your platform can also charge its own fee on payments: see payment revenue for software platforms.
Picture a property management platform: each landlord is a service, each building a merchant with its own bank account, each resident a customer with a PAD agreement for monthly rent. One landlord sets a lower collection limit, another enables Interac for late payers, and every NSF comes back with the building's MerchantId. Read more on payments for property management software and payments for lending platforms.
What do VoPay and Zum Rails offer for PAD?
Both offer PAD, and both do things well: VoPay publishes a guide to collecting PAD payments compliantly under Rule H1 and offers a no-code collection product, and Zūm Rails publishes when it sends EFT transactions and asks each user for PAD consent when creating a payment profile. Here is what each one states, in its own words.
| Provider | What it publishes about PAD | Source (verified November 22, 2026) |
|---|---|---|
| VoPay | Under Rule H1, "a customer can dispute any PAD transaction and demand a refund from their bank for up to 90 days after the debit if they claim the authorization was not properly obtained"; eLinx eCollect provides "a compliant, no-code path from customer onboarding to automated recurring collections" | VoPay PAD compliance article (April 21, 2026) |
| VoPay | eLinx lets businesses manage "collecting bank details, obtaining debit authority, and handling recurring payments in one integrated solution"; its Payments-as-a-Service solution lets businesses "monetize transactions through multiple different partnership models" | VoPay pre-authorized debit page |
| Zūm Rails | An EFT "takes up to 3 days to complete"; transactions are sent Monday to Friday at 2:55am, 1:58pm and 5:58pm, and responses are processed Tuesday to Saturday at 8:00am; "a user is always asked to agree and consent the information shared (PAD) when creating a payment profile" | Zūm Rails EFT documentation |
| TIB Finance | PAD agreements signed online; PAD in 1 to 2 business days; every webhook event, from Validation to Payback, carries the MerchantId; NSF fee, limits and allowed methods set per tenant | PAD API |
Where your processor is based matters as well. TIB Finance is a sovereign Canadian payment processor, founded in 2018, with its headquarters in Montreal and a team that serves you in English and in French. In September 2024, Zūm Rails announced a U.S. headquarters in Miami, announced that its CEO "will permanently relocate to Miami from Canada", and said it was preparing for at least 50% of its overall revenue to originate stateside within the next 18 months, adding that it would simultaneously continue scaling its work in Canada (verified November 22, 2026). For 2028, the U.S. is expected to contribute more than 60% of its revenue, according to its CEO (Mergermarket, July 2026, verified November 22, 2026).
In January 2026, VoPay announced its global headquarters in Qatar (verified November 22, 2026), and its website has no French version: vopay.com/fr-ca/ leads to an error page (verified November 22, 2026). TIB Finance serves your tenants and their payers in English and in French.
Go deeper with TIB Finance vs Zum Rails, TIB Finance vs VoPay and what a sovereign Canadian payment processor means.
How fast can your platform launch PAD with TIB Finance?
Fast, because TIB Finance sends people. Our integration team works inside your processes until payments run on their own, and integration is free for eligible businesses. The team also configures your webhook endpoints with you. See business integration.
TIB Finance is proven and solid. It is registered as a payment service provider with the Bank of Canada under the RPAA (see registered PSP in Canada) and PCI DSS Level 1 compliant. It serves more than 1,000 businesses, processes over $600 million a year and handles more than 200,000 transactions every month. A real, bilingual team supports every client and every partner. Plans from $25/month, with pricing adapted to your volume and your business model: talk to our team. Developers can open the free sandbox to test every payment flow end to end, with credentials sent by email.
Building a platform or advising clients? Become a TIB Finance partner: a $250 gift card on your first mandate and up to 60% commissions.
Common Questions
Can a platform collect pre-authorized debits for its clients in Canada?
Yes. With TIB Finance, each client of your platform is a service, each of its bank accounts a merchant, and its payers customers underneath it. Your software schedules the PADs, and each one settles in 1 to 2 business days into that merchant's bank account.
Who signs the PAD agreement on a multi-tenant platform?
The payer, online, through the secure Drop-In form or a payment link. The agreement follows Payments Canada Rule H1 and stays with the payer under the tenant. If consent is missing, the API answers "PPA consent needed" instead of debiting.
How long does a PAD take to settle with TIB Finance?
1 to 2 business days (T+1 to T+2), into the bank account of the tenant's merchant. For payments in seconds, 24/7/365, TIB Finance runs instant payments on its own system.
How does my platform know which tenant a PAD return belongs to?
Every TransactionEvent webhook carries the MerchantId and MerchantName, along with its step (Validation, Transmission, StatusCheck or Payback), its status and a DescriptionCode. Your system posts each event to the right tenant.
How long after a debit can a PAD come back?
TIB Finance validates each payment for 3 months on personal accounts and 2 weeks on business accounts, and an NSF, an opposition or a closed account in that period triggers a Payback webhook event.
Can each tenant have its own NSF fee?
Yes. Fees are set per service, and each tenant is a service, so each one gets its own NSF fee, NSF file fee and stop-payment fee. Limits and allowed payment methods are set per service too.
How much does TIB Finance cost?
Plans from $25/month, with pricing adapted to your volume and your business model. Talk to our team for a proposal built around your platform.
Let's map PAD for your tenants
Tell our team how your platform collects today, and we will map your tenants, their bank accounts and their PAD agreements onto TIB Finance with you.
Talk to our team Become a partner Open the sandbox