EFT Rails

Pre-authorized debit vs credit card for recurring billing in Canada

A pre-authorized debit collects recurring payments from the customer's bank account under a PAD agreement. For credit card payments, the card issuer approves or declines the transaction when it is made.

Updated November 3, 2026

What EFT Rails does

EFT Rails sends payments by electronic funds transfer (EFT) and Interac e-Transfer. It does not process card payments. EFT Rails sends a debit when you create it, for the amount you set, or on a recurring schedule you set up once through the API. The schedule creates debits about a week before their dates. You hold the pre-authorized debit (PAD) agreement with your customer. The API reference describes the payment requests.

How each one works

A pre-authorized debit (PAD) is drawn under the customer's PAD agreement: a continuing but revocable authority, written or recorded and signed or otherwise authorized, that lets the business debit the customer's account.1

A credit card payment involves the customer, the merchant, the card processor and the bank that issued the card, along with the card network. In some networks, the card processor and the card issuer are the same company.2 The card issuer checks the customer's available funds or credit and approves or declines the payment, with the answer returned to the merchant at the time of payment.3

The comparison

Pre-authorized debit Credit card
Authority The customer gives continuing but revocable authority through a PAD agreement.1 The customer, merchant, card processor, card issuer and card network take part in the payment. The card issuer approves or declines each payment when it is made.4
When the money moves The banks settle an EFT on the business day after its Due Date.5 Approved payments are grouped, usually by business day, and sent to the card processor for settlement. The card issuers send the funds to the processor, which either pays the full amount and takes fees later or takes the fees first.3
What a failure looks like The debit can return with a reason code. A return for non-sufficient funds or funds not cleared can be presented again once, within 30 calendar days, for the same amount.6 The card issuer declines the payment, and the merchant receives that decision at the time of payment.3
How the customer gets money back The customer claims through their own bank when the debit did not follow the agreement, the agreement had been revoked or a required notice was not given. A claim that no agreement existed can be made within 90 calendar days.7 The customer asks the card issuer for a chargeback to reverse a disputed transaction. Each card network sets its own chargeback guidelines, and provincial law may also apply.8

A PAD requires notice before collection and before certain changes. Before the first debit, the business gives the customer a confirmation at least 10 calendar days ahead, unless the customer waives it or shortens the period.9 For debits at set intervals, the business gives pre-notification of the amount and date at least 10 calendar days before a change to a fixed amount or the dates, and before every variable-amount debit after the first.10 See PAD pre-notification and how long an EFT takes.

Card fees depend on the merchant's plan with its card processor. A flat or blended plan applies one rate. Otherwise, fees depend on the card brand, whether the card is premium or standard, and the transaction type.11

When a payment fails

A failed collection produces either a returned debit or a decline at the time of payment. A returned PAD carries a return code naming the reason: 901 for non-sufficient funds (NSF), 902 for account not found, 903 for payment stopped or recalled, 905 for account closed, and 908 for funds not cleared.12

A debit returned for NSF or funds not cleared can be presented again once, within 30 calendar days, for the same amount.13 EFT Rails shows the payment as returned. See handling NSF returns.

For a credit card payment, the card issuer checks the available funds or credit and sends its approval or decline to the merchant at the time of payment.3

Disputes

A customer uses a claim for a PAD and a chargeback for a credit card payment. A PAD customer can claim through their own bank if the debit did not follow the agreement, the agreement had been revoked, or a required notice was not given. The deadline is up to and including 90 calendar days after a personal debit, or 10 business days after a business debit, and the bank reimburses the customer immediately on a best-efforts basis.14 A claim that no agreement existed at all can be made within 90 calendar days.15 See the PAD dispute windows.

A chargeback is a customer's request for their card issuer to reverse a disputed transaction. Each card network sets its own chargeback guidelines, and provincial law may also apply. Merchants must be told the fees charged to them for chargebacks.8

Cancelling

Cancelling a PAD ends the authority for further debits. When a customer cancels, the business must stop issuing new debits within 30 calendar days of the notice and cannot debit again without a new agreement.16

Choosing

A PAD suits a recurring amount from a customer who has signed an agreement. A credit card suits a payment where the customer pays at the time. Many businesses offer both. See setting up pre-authorized debits for the collection process.

Sources (16)
  1. Rule H1, section 5(m) ↩
  2. FCAC, "Parties involved in a card payment transaction" ↩
  3. FCAC, "Card payment transaction steps" ↩
  4. FCAC, "Parties involved in a card payment transaction"; FCAC, "Card payment transaction steps" ↩
  5. Rule F1, Part V, "Settlement" ↩
  6. Standard 007, Appendix I, "List of Return Reason Codes"; Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  7. Rule H1, section 24; Rule H1, section 23 ↩
  8. FCAC, "What rights do consumers have in terms of chargebacks?" ↩
  9. Rule H1, section 16 ↩
  10. Rule H1, section 17 ↩
  11. FCAC, "Card payment transaction fees" ↩
  12. Standard 007, Appendix I, "List of Return Reason Codes" ↩
  13. Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  14. Rule H1, section 24 ↩
  15. Rule H1, section 23 ↩
  16. Rule H1, section 30(a) ↩

Questions

What is the difference between a PAD and a credit card payment?

A PAD draws on the customer's continuing but revocable PAD agreement, which authorizes the business to debit their account.1 A credit card payment involves the customer, merchant, card processor, card issuer and card network.2 The card issuer approves or declines the payment at the time it is made.3

Can a customer dispute a PAD like a credit card chargeback?

A PAD customer claims through their own bank if the debit did not follow the agreement, the agreement had been revoked, or a required notice was missing. The window is up to and including 90 calendar days for a personal debit and 10 business days for a business debit. A claim that no agreement existed can be made within 90 calendar days.4 A card customer instead asks the card issuer for a chargeback, subject to the card network's guidelines and any applicable provincial law.5

What happens when a PAD fails?

The debit can return with a code identifying the reason, including non-sufficient funds, account not found, payment stopped or recalled, account closed, or funds not cleared.6 A return for non-sufficient funds or funds not cleared can be presented again once, within 30 calendar days, for the same amount.7

When does the money arrive?

The banks settle an EFT on the business day after its Due Date.8 Approved card payments are grouped, usually by business day, for settlement through the card processor, and the processor either pays the merchant in full before taking fees or deducts the fees first.3

Can a customer cancel a PAD?

Yes. The business must stop issuing new debits within 30 calendar days of the cancellation notice and cannot debit again without a new agreement.9

Sources (9)
  1. Rule H1, section 5(m) ↩
  2. FCAC, "Parties involved in a card payment transaction" ↩
  3. FCAC, "Card payment transaction steps" ↩
  4. Rule H1, section 24; Rule H1, section 23 ↩
  5. FCAC, "What rights do consumers have in terms of chargebacks?" ↩
  6. Standard 007, Appendix I, "List of Return Reason Codes" ↩
  7. Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  8. Rule F1, Part V, "Settlement" ↩
  9. Rule H1, section 30(a) ↩

Open an account

Open an account