Is an electronic PAC legally valid?

Yes. Electronic signatures that demonstrate intent, capture consent to transact electronically, are attributable to the signer, and are retained in a reproducible record generally satisfy ESIGN and UETA requirements for commercial transactions.

How can a payer revoke authorization?

Include clear cancellation instructions in the PAC. A payer typically revokes by written notice per the stated procedure; allow reasonable processing time and stop future debits once notice is effective.

When is notarization required?

Notarization is not routinely required for ordinary payment authorizations but may be necessary where state law applies special formalities or where the authorization is paired with a power of attorney or real property instrument.

What if account numbers are wrong?

Incorrect routing or account numbers often cause bank returns and fees. Correct errors promptly, reimburse fees where appropriate, and maintain supporting verification records to resolve disputes.

How long should I keep PAC records?

Retain PACs at least as long as relevant tax and industry retention rules require: typically 3 years for tax records, 6 years for HIPAA contexts, and longer where state law or contractual obligations demand it.

How to handle a disputed debit?

Follow your processor’s dispute and chargeback procedures, collect supporting authorization and transaction evidence, and respond within the bank’s specified timeframe to defend a valid debit.

Electronic Signature
Templates
Finance
Payment Authorization PAC

Payment Authorization PAC

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Payment Authorization PAC

Payee (Company) Information

Payee Company Name Payee Contact / Reference Payee Address

Payee Phone

Payee Email

Payer (Account Holder) Information

Full Legal Name Billing Address

Phone

Email

Customer / Account ID (if applicable)

Payment Authorization Details

Authorization Type: One-time debit Recurring debit Variable/Authorized amount

Amount:

Currency:

Start Date:

End Date (if any):

Frequency / Schedule: Number of Payments:

Payment Method

Select method of debit: Bank account (ACH/PAC) Credit / Debit card

Bank Account Details (if applicable)

Account Type Checking Savings

Card Details (if applicable)

Authorization, Terms and Liability

By signing below, Payer authorizes Payee to initiate debit entries to the account indicated above and, if necessary, to initiate adjustments for any entries made in error. This authorization shall remain in full force and effect until Payee has received written notification from Payer of its termination in such time and in such manner as to afford Payee and the financial institution a reasonable opportunity to act on it, which shall be no fewer than five (5) business days prior to the next scheduled debit.

Payer represents and warrants that Payer is an authorized signer on the specified account and that the information provided is true and correct. Payer agrees to indemnify and hold Payee harmless from any loss, damage or expense arising from Payer's breach of this representation. In the event that any debit is returned by the financial institution for any reason, Payee may assess a returned item fee and may re-present the debit to the financial institution.

If the authorization is for variable payments, Payee will provide notice to Payer of the amount and scheduled date of each debit at least ten (10) calendar days prior to the debit unless otherwise agreed in writing. Payer acknowledges that this authorization is not conditioned on the delivery of goods or services.

Governing Law: This Authorization shall be governed by and construed in accordance with the laws of the state or jurisdiction where Payee's principal place of business is located, without regard to conflict of law principles. If any provision is held invalid, the remaining provisions shall remain in full force and effect.

Additional Terms or Special Instructions

Certification

The undersigned certifies that the information contained herein is complete and accurate and that the undersigned is authorized to execute this Payment Authorization on behalf of the Payer named above. The undersigned acknowledges receipt of and agrees to the terms set forth in this Authorization.

Printed Name:

Signature:

Date:

What the Payment Authorization PAC Is and when it’s used

The Payment Authorization PAC is a written authorization form that permits a payer to authorize single or recurring payments to a payee, vendor, or agent. It documents payer identity, payment method (ACH, debit/credit card), payment amount or range, frequency, and an effective date or termination condition. In electronic workflows the form also captures signer intent, consent to electronic transactions, and an audit trail to support enforceability under U.S. electronic-signature law. Use this form to reduce billing disputes, enable automated processing, and create a retained record of payment consent.

Why a clear Payment Authorization PAC matters

A well‑drafted PAC clarifies payment terms, reduces processing delays, and documents consent in a reproducible format that supports electronic signature laws such as ESIGN and UETA. It protects both payer and payee by spelling out amounts, timing, cancellation procedures, and dispute contact points.

Who typically completes or signs a Payment Authorization PAC

The PAC is used by organizations and individuals who need recurring or one‑time payment consent recorded formally before collecting funds.

Small businesses and vendors who bill customers on a recurring schedule and need written authorization for ACH or card debits.
Healthcare providers and clinics when obtaining patient authorization to bill insurance balances or recurring patient payments.
Property managers and landlords authorizing recurring rent collection or one‑time move‑in fees from tenant accounts.

Use the PAC whenever you require documented payer consent for automated debits, card charges, or third‑party payment processing.

Stepwise completion process for the Payment Authorization PAC

Follow these steps in order to complete the PAC accurately and ensure it can be processed electronically or by your billing partner.

01

1. Gather payer data: Collect legal name, address, and bank or card details.
02

2. Define payment terms: Enter amount, frequency, start date, and end conditions.
03

3. Add authentication: Include ID check, SMS code, or other authentication as required.
04

4. Sign and retain: Obtain signature and save the signed record with audit trail.

Configuring an online PAC workflow

Map each workflow setting to the PAC fields to automate routing, authentication, and retention.

Field	Configuration
Authentication	Email link or SMS code; use stronger KBA for higher risk
Routing	Send to payer first, then billing team for verification
Retention	Automate PDF export plus audit log storage
Notifications	Set payer and accounts‑receivable alerts on completion

How electronic submission and processing typically flow

A concise electronic workflow reduces manual steps and provides an immutable audit trail for payment authorization.

Upload: Sender uploads PAC template and configures fields.
Request: System sends signer link or secure email invite.
Authenticate: Signer confirms identity by SMS, email, or KBA.
Process: Signed PAC is stored and payment processor debits account.

Technical and platform considerations for eSubmission

Ensure the platform supports required formats, authentication, and retention policies before sending the PAC.

Document formats: PDF, DOCX supported for upload and export
Authentication options: Email link, SMS OTP, or KBA as available
Integrations: Connect to CRM, accounting, or payment gateway

Essential elements to include in a professional Payment Authorization PAC

A complete PAC combines identity data, payment specifics, consent language, and administrative terms so that both parties understand obligations and cancellation rights.

Payer identity

Full legal name and contact details plus an optional government ID reference or account verification step to confirm the person granting authorization.

Payment details

Clear payment method information, including ACH routing/account numbers or card number tokenization, dollar figure or range, frequency, and any caps or limits on charges.

Consent statement

Explicit language stating the payer’s intent to authorize electronic debits and acceptance of any associated fees or processor terms to satisfy ESIGN/UETA criteria.

Cancellation terms

Instructions for revocation, notice period required to stop future charges, and whether revocation affects pending debits or returned items.

Dispute and refunds

Procedure for disputing charges, contact information, time limits to report errors, and any refund policy that applies to unauthorized or erroneous debits.

Recordkeeping and audit trail

Statement noting how signed records will be retained, how copies are supplied to the payer, and what authentication evidence (IP, timestamp) is kept for compliance.

Privacy, security, and compliance notes to include

Encryption: TLS 1.2/1.3

Data at rest: AES‑256

Audit trail: IP, timestamp, actions

HIPAA readiness: BAA available if needed

Authentication: SMS, email, or KBA

Access controls: Role‑based permissions

Common preparation errors with Payment Authorization PACs

Entering an incorrect routing or account number that causes ACH returns and increases bank fees and collection delays.
Using vague payment language such as 'as billed' without caps, which increases dispute risk and complicates refund decisions.
Failing to capture signer intent or a clear consent statement, which can undermine enforceability under electronic signature laws.
Not providing a cancellation mechanism or clear notice period, producing friction when payers request stops or refunds.

Legal and financial consequences of improper authorizations

Returned payments: Bank fees and reversal costs

Disputes: Chargebacks and penalties

Withholding: Backup withholding risk if TIN missing

Contract disputes: Claims for improper authorization

Regulatory risk: FTC or state enforcement exposure

Reputational harm: Customer trust erosion

Timing considerations and related tax or reporting deadlines

Payment authorizations affect reporting obligations and tax forms; maintain records to meet deadlines for information returns and related tax reporting.

Provide W-9 on request:

Offer a completed W-9 when requested by payers to avoid backup withholding; no fixed IRS deadline for payer request.

1099 reporting cycle:

Collect and retain payer/payee records to meet Jan 31 recipient distribution deadlines and IRS filing deadlines for 1099 series.

Record retention:

Keep payment authorization records long enough to substantiate tax reporting and audits as required by IRS rules.

Bank dispute windows:

Electronic funds disputes often must be reported within 60 to 120 days depending on payment rail and bank policies.

Cancellation timing:

Allow sufficient lead time in your PAC for a revocation to stop future automated debits before the next scheduled charge.

Key processing milestones after PAC submission

Tracking milestones helps coordinate verification, processing, and dispute windows from submission to completed payment.

01

Submission

Payer completes PAC and submits signed authorization for verification.

02

Verification

Payment method and identity are validated before scheduling the first debit.

03

First debit

Initial payment is processed on the effective date; monitor for returns.

04

Ongoing posting

Recurring charges post per schedule; maintain records of each transaction.

eSignature vendor comparison for Payment Authorization PAC workflows

Comparison of typical vendor starting prices and feature availability relevant to payment authorization workflows. Confirm vendor plans and integrations before purchase.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Real-world examples of payment authorization workflows

Practical examples show how organizations capture consent, speed collections, and maintain compliance when using electronic PACs.

Optica Ventures — recurring rent

The property manager digitized tenant authorizations to automate monthly rent debits.

Reduced manual posting and errors.
The electronic authorizations provided a clear audit trail and faster reconciliation, improving cash flow while reducing tenant disputes.

Fertility Centers — patient billing

A clinic captured patient payment consent for installment billing of services.

Secured payment tokens and a signed PAC.
This approach maintained HIPAA safeguards, allowed tokenized charges without storing card numbers, and improved collection timing for multi‑visit care plans.

Practical tips for accurate and efficient PAC completion

Adopt these practices to minimize errors, reduce disputes, and ensure authorizations remain enforceable and auditable.

Use precise payment language

State exact amounts or an explicit calculation method, frequency, and any upper limits. Clear terms reduce interpretation disputes and limit chargebacks.

Verify payer identity

Authenticate payers by matching name, address, and a secondary factor such as SMS OTP or bank micro‑deposits to reduce fraud and returned items.

Record consent evidence

Retain a signed PDF plus an immutable audit trail showing signer IP, timestamp, and authentication method to support enforceability under ESIGN or UETA.

Test integrations end-to-end

Before wide deployment, validate link behavior, payment gateway tokenization, and notification rules to avoid failed transactions and customer confusion.

Frequently asked questions about Payment Authorization PACs

Answers to common questions about signature validity, revocation, notarization, and recordkeeping for payment authorizations.

Need help? Contact support

Is an electronic PAC legally valid?
Yes. Electronic signatures that demonstrate intent, capture consent to transact electronically, are attributable to the signer, and are retained in a reproducible record generally satisfy ESIGN and UETA requirements for commercial transactions.
How can a payer revoke authorization?
Include clear cancellation instructions in the PAC. A payer typically revokes by written notice per the stated procedure; allow reasonable processing time and stop future debits once notice is effective.
When is notarization required?
Notarization is not routinely required for ordinary payment authorizations but may be necessary where state law applies special formalities or where the authorization is paired with a power of attorney or real property instrument.
What if account numbers are wrong?
Incorrect routing or account numbers often cause bank returns and fees. Correct errors promptly, reimburse fees where appropriate, and maintain supporting verification records to resolve disputes.
How long should I keep PAC records?
Retain PACs at least as long as relevant tax and industry retention rules require: typically 3 years for tax records, 6 years for HIPAA contexts, and longer where state law or contractual obligations demand it.
How to handle a disputed debit?
Follow your processor’s dispute and chargeback procedures, collect supporting authorization and transaction evidence, and respond within the bank’s specified timeframe to defend a valid debit.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now