Pre-Authorized Payment_Specific Amount Template

In plain language: Identifies the payee (the business collecting payment) and the payer (the account holder), along with the payer's bank name, account number, and routing or transit number.

Common mistake: Collecting only the last four digits of the account number for privacy — the full account and routing numbers are required for the bank to process the debit, and the authorization is unenforceable without them.

In plain language: States the exact fixed dollar amount the payee is authorized to withdraw each cycle — the defining feature of a specific-amount PAD over a variable-amount authorization.

Common mistake: Writing 'up to $[X]' instead of a single fixed figure. This converts a specific-amount authorization into a variable-amount one, which requires different disclosure language and a distinct form under most banking rules.

In plain language: Defines how often debits occur (weekly, bi-weekly, monthly, annually) and the date on which the first debit will be processed.

Common mistake: Stating only the frequency without a specific start date. An ambiguous start date creates disputes over when the authorization became effective and whether initial debits were properly authorized.

In plain language: Describes the goods, services, or obligation the recurring payment relates to, linking the authorization to the underlying commercial or contractual relationship.

Common mistake: Leaving the purpose field blank or writing 'services.' Regulators and dispute arbitrators use the purpose clause to verify the authorization was given in a specific commercial context — a blank field weakens the payee's position in a reimbursement claim.

In plain language: States whether the authorization runs for a fixed number of payments or indefinitely, and sets out the conditions under which it automatically terminates.

Common mistake: Omitting an automatic termination trigger tied to the underlying contract. If the service agreement ends but the PAD continues, the payee risks processing unauthorized debits and liability for reimbursement plus fees.

In plain language: Sets out the payer's right to cancel the authorization, the required notice period, and the method of delivery for the cancellation notice.

Common mistake: Requiring more than 30 days' cancellation notice. Most banking rules — including Nacha in the US and Payments Canada rules for PADs — cap the permissible notice requirement, and an overly long notice period can be deemed unenforceable.

In plain language: Explains how the payer can dispute an unauthorized or erroneous debit, the timeframe for raising a dispute, and the process for obtaining a reimbursement.

Common mistake: Omitting the dispute and reimbursement clause entirely. Banking networks require payees to include this language; its absence can cause the entire authorization to fail compliance review at the payer's bank.

In plain language: A clause by which the payer waives their right to receive advance notice before each recurring debit, streamlining processing for predictable fixed-amount payments.

Common mistake: Including a pre-notification waiver for variable-amount authorizations. The waiver is appropriate only for truly fixed amounts — if the amount can change, pre-notification is required under most banking scheme rules and the waiver is invalid.

In plain language: States what happens if a debit is returned due to insufficient funds, including any NSF fee the payer agrees to pay and the payee's right to re-present the item.

Common mistake: Authorizing unlimited re-presentment without a cap. Nacha rules limit ACH re-presentment to two additional attempts after the original; exceeding that limit without proper authorization exposes the payee to rule violations and fines.

In plain language: Specifies the jurisdiction whose laws govern the agreement and acknowledges that applicable banking network rules — Nacha, Payments Canada, SEPA, Bacs — take precedence over conflicting contract terms.

Common mistake: Omitting the banking scheme reference and relying solely on contract law. PAD and ACH authorizations operate within a layered regulatory framework; a governing law clause alone does not satisfy the compliance requirements of the payment network.

A pre-authorized payment agreement is a written authorization signed by a bank account holder that permits a payee — such as a business, lender, or service provider — to withdraw funds directly from the account on a recurring schedule without requiring the payer's manual action each time. The specific-amount variant fixes the withdrawal at a set dollar figure per cycle, making it suitable for subscriptions, loan installments, memberships, and fixed-rate service contracts.

A specific-amount authorization fixes the debit at a single, stated dollar figure — for example, $149.00 per month — and typically allows the payer to waive pre-notification since the amount never changes. A variable-amount authorization permits the debit to fluctuate each cycle based on usage, consumption, or a formula, and generally requires the payee to notify the payer of the upcoming amount in advance. Using the wrong form for your billing model can invalidate the authorization under banking network rules.

Yes — a properly executed pre-authorized payment agreement is generally enforceable as a contract between the payee and payer, subject to applicable banking scheme rules and consumer protection laws. The agreement must clearly state the authorized amount, frequency, and cancellation rights, and must be signed by the account holder (or an authorized representative for a business account) before the first debit is processed. Consider consulting a lawyer if the amounts are significant or the payer is located in a different jurisdiction.

Yes. Payers retain the right to cancel a pre-authorized payment authorization at any time under banking scheme rules in most jurisdictions. The cancellation typically requires written notice to the payee within a specified period — often 10 to 30 days — before the next scheduled debit. Cancelling the PAD does not automatically cancel any underlying payment obligation the payer owes under a separate service or credit agreement; those debts remain due by other means.

If the payer's account has insufficient funds on the debit date, the bank returns the item unpaid and both parties typically incur fees. Under Nacha ACH rules, the payee may re-present the debit up to two additional times. The PAD agreement should specify any NSF fee the payer agrees to pay and the number of re-presentment attempts permitted. Repeated NSF returns can result in the payment processor suspending the payee's debit privileges.

Yes. Most banking scheme rules — including Payments Canada Rule H1, Nacha consumer guidelines, and SEPA mandate requirements — require the payee to provide the payer with a copy of the signed authorization at the time of execution. Failing to do so can expose the payee to successful reimbursement claims even where the payer did sign the form.

Best practice — and the requirement under most banking scheme rules — is to retain the signed original for the full duration of the recurring debit series plus at least two years after the final payment. For consumer-facing authorizations in Canada, Payments Canada rules require retention for a minimum of one year after the last PAD item. Retaining the voided cheque alongside the authorization is also standard practice as it corroborates the banking details.

At minimum, a valid authorization must identify the payee and payer, state the exact bank account and routing details, specify the authorized amount and frequency, include a start date, describe the purpose of the payments, set out the payer's cancellation and reimbursement rights, and be signed by the account holder before the first debit. Many banking schemes — particularly in Canada and the EU — impose additional specific content requirements, so check the rules of the applicable payment network.

Yes, with modifications. For personal (consumer) accounts, enhanced disclosure and reimbursement rights apply under most banking scheme consumer protection rules. For business accounts, the signatory must be authorized to bind the business entity, and many banking networks apply a shorter dispute window (typically 10 business days rather than 90 days for consumers). Clearly identify whether the payer is an individual or a business entity in the authorization and tailor the notice periods accordingly.