EFT Rails

NSF fees on pre-authorized debits in Canada

A debit returned for NSF can be presented once more, for the original amount only. A returned-payment fee is a separate debit, and your PAD agreement has to provide for it.

Updated November 3, 2026

What EFT Rails does

When a pre-authorized debit (PAD) is returned for non-sufficient funds (NSF), you control both the second attempt and any returned-payment fee. EFT Rails sends a debit when you create it, for the amount you set. It does not present a returned debit again or add a fee on its own.

Create the second attempt and the fee debit as separate debits through the API or in the dashboard. The API reference documents the API. A payment can carry your own reference, which comes back with it. Give both debits the reference of the original payment so you can match them to it in your records.

Try the debit again

The second attempt collects the original payment once more. A debit returned for NSF with return code 901, or for funds not cleared with return code 908, can be presented again once within 30 calendar days after the return. If it is dishonoured a second time, you cannot present it again.1

Keep the second attempt at the original amount. It cannot include your returned-payment fee or any other additional charge.2 Your undertaking to your bank states the same restriction: a re-presentment cannot carry interest, NSF charges or other charges on top of the original amount.3

The process for receiving the return and creating the new debit is covered in Handling NSF returns.

Collect the fee as its own debit

A returned-payment fee is collected through its own PAD, with terms written into the customer's agreement. The fee debit requires the customer's PAD agreement, as does any other PAD.4

The agreement must state the amount, fixed, variable or both, any conditions that apply to the amount, and the timing.5 If an act, event or other criterion triggers the debit, the agreement must describe it unambiguously.6

Write the returned-payment fee into the agreement as an amount and identify the return of a debit as the event that triggers it. Then collect the fee as a separate fee debit. The second attempt remains at the original amount. See PAD agreements for the agreement requirements.

Rule H1 must follow the law, including consumer protection law, so the fee term must also follow the law governing your contract.7 The bank's own NSF charge to the customer is between the customer and their bank.

Tell your customer before the fee debit

For debits at set intervals, a variable-amount debit after the first requires pre-notification of its amount and date at least 10 calendar days before the debit. The same notice period applies when you change a fixed amount or the payment dates.8

See PAD pre-notification for how to provide that notice.

When the agreement says nothing about a fee

A customer can claim back a debit that was taken outside the terms of their PAD agreement. The claim window runs up to and including 90 calendar days after a personal debit and up to and including 10 business days after a business debit. Their bank reimburses them immediately on a best-efforts basis.9

The debit then comes back with return code 916 for a personal debit or return code 919 for a business debit. Both codes mean the debit was not according to the agreement.10

A returned payment shows as returned in EFT Rails. Read more about PAD dispute windows and EFT return codes.

Sources (10)
  1. Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  2. Rule H1, section 22(c); Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  3. Rule H1, Appendix I, paragraph 20 ↩
  4. Rule H1, section 15(a)(i) ↩
  5. Rule H1, section 15(a)(v); Rule H1, Appendix II, "Amount, Timing or Specified Event/Action" ↩
  6. Rule H1, Appendix II, "Amount, Timing or Specified Event/Action" ↩
  7. Rule H1, section 2 ↩
  8. Rule H1, section 17 ↩
  9. Rule H1, section 24 ↩
  10. Standard 007, Appendix I, "List of Return Reason Codes" ↩

Questions

Can I add my NSF fee to the re-presented debit?

No. The second attempt must be for the original amount, without additional charges.1 Your undertaking to your bank also excludes interest, NSF charges and other charges from a re-presentment.2

How do I collect a returned-payment fee by PAD?

Provide for the fee in the customer's PAD agreement, which must support the fee debit.3 State its fixed or variable amount and describe the return of a debit as the event that triggers it.4 Create a separate fee debit, leaving the second attempt at the original amount.

What happens if the agreement does not mention a fee?

The customer can claim back a debit that was not drawn in accordance with their agreement, within 90 calendar days for a personal debit or 10 business days for a business debit. Their bank reimburses them immediately on a best-efforts basis.5 The return uses code 916 for a personal debit or 919 for a business debit.6

How many times can I present a debit returned for NSF?

You can present it again once, within 30 calendar days after the return. The same one-time allowance applies to a debit returned for funds not cleared, and a debit dishonoured a second time cannot be presented again.7

Sources (7)
  1. Rule H1, section 22(c); Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩
  2. Rule H1, Appendix I, paragraph 20 ↩
  3. Rule H1, section 15(a)(i) ↩
  4. Rule H1, Appendix II, "Amount, Timing or Specified Event/Action" ↩
  5. Rule H1, section 24 ↩
  6. Standard 007, Appendix I, "List of Return Reason Codes" ↩
  7. Rule F1, Part III, "Re-presentment and Rejected Returned Transactions" ↩

Open an account

Open an account