Is an electronic authorization legally binding?

Yes when it meets the ESIGN four-part test: intent to sign, consent to transact electronically, clear attribution to the signer, and retained reproducible record (15 U.S.C. ch. 96).

Can I store full card numbers?

No. PCI DSS prohibits storing full PANs without strict controls; store tokens or the last four digits and never persist CVV data.

What authentication is recommended?

Use at least email verification plus a secondary factor (SMS OTP or knowledge-based checks) for remote signings to reduce chargeback exposure.

How do I handle revocations?

Provide clear revocation instructions on the authorization and honor timely revocations; document receipt and any follow-up to avoid future disputes.

What should be retained for disputes?

Keep the signed authorization, audit trail (timestamps, IP, auth logs), processor token IDs, and related invoices for the applicable retention period.

Are notarization or witnesses required?

Typically not for routine card authorizations; notarization is uncommon and generally unnecessary unless state law or contract demands it.

Electronic Signature
Templates
Finance
Payment Card Authorization

Payment Card Authorization

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

PAYMENT CARD AUTHORIZATION

Merchant Information

Merchant Name Merchant Address

Merchant Phone

Merchant Email

Cardholder Information

Cardholder Name Billing Address

Cardholder Phone

Cardholder Email

Payment Authorization Details

I authorize the merchant named above to charge the payment card supplied below for the amounts and frequency indicated. This authorization applies to charge(s) described as:

Description of Charge / Invoice Reference

Amount Authorized (per charge)

Currency

Type of authorization: One-time charge Recurring charges

If recurring, frequency

Start Date

End Date (optional)

Payment Card Information

Card Type: Visa MasterCard American Express Discover Other

Card Number Name on Card

Expiration:

/

CVV:

Billing Address (if different)

Terms, Authorization & Certifications

By signing below, the cardholder certifies that the information provided on this form is true and accurate and that the cardholder is an authorized user of the payment card. The cardholder authorizes the merchant to charge the card in accordance with the Payment Authorization Details above. This authorization constitutes express consent to process the charges specified and, for recurring charges, to process future charges in accordance with the stated frequency until the authorization expires or is revoked in writing.

The cardholder agrees to notify the merchant in writing of any changes to the card account information or termination of this authorization at least 7 days prior to the next scheduled charge. Merchant may terminate stored payment privileges upon notice to the cardholder. The merchant will comply with applicable data protection and card network rules in the storage and handling of card data. The cardholder acknowledges that disputes regarding the amount or frequency of an authorized charge must be raised directly with the merchant first.

This authorization is limited to charges described in this form. Any additional or separate authorization must be obtained in writing. The cardholder indemnifies and holds the merchant harmless from any liability arising from charges made in good faith pursuant to this authorization.

Special Instructions or Additional Terms

Authorization to Store Card on File: I authorize the merchant to securely store my card information for the purpose of processing future authorized charges in accordance with this agreement.

Cancellation and Refund Policy: Charges authorized herein are subject to the merchant's refund policy. Refunds, if any, shall be issued to the card on file. The merchant's assessment of refunds, credits or cancellations shall be final except to the extent overridden by applicable card network rules or law.

A copy of this completed and signed authorization will be maintained by the merchant and provided to the cardholder upon request. The cardholder retains the right to revoke this authorization by written notice; revocation does not affect charges already properly incurred prior to receipt of the revocation.

By signing, the cardholder acknowledges receipt of a copy of this Payment Card Authorization and affirms that they are legally authorized to approve charges to the card indicated.

Cardholder Name:

Signature:

Date:

What a Payment Card Authorization Is and when it applies

A Payment Card Authorization is a written or electronic record in which a cardholder gives a merchant permission to charge a payment card for a specified amount, schedule, or transaction type. It records intent, card details (often masked), billing address, and the scope of consent (single charge, recurring payments, estimated amounts). Electronic versions are enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws when they meet intent, consent, attribution, and retention requirements.

Why a clear authorization protects both parties

A properly drafted Payment Card Authorization documents customer consent, reduces chargebacks and disputes, and supports PCI-compliant handling of card data. It creates a tamper-evident record of transaction terms and signer identity for audit and reconciliation purposes.

Who typically completes a Payment Card Authorization

The form is used by organizations that collect card payments without immediate card-present processing.

Subscription and recurring-billing teams who need documented recurring consent and charge schedules.
Property managers and landlords taking security deposits or rent by card to record tenant authorization.
Service providers and merchants taking card-on-file payments for installations, repairs, or invoices.

Use the form whenever a business needs documented cardholder consent for one-time or recurring charges to reduce disputes and demonstrate authorization.

Essential elements to include in a professional authorization

A comprehensive Payment Card Authorization balances clarity for the cardholder with merchant operational needs; include scope, frequency, card handling, and revocation instructions to reduce disputes and support compliance.

Authorization Clause

A clear statement that the cardholder authorizes the merchant to charge the card, including whether charges are one-time or recurring and any maximum amounts permitted.

Card Details

Cardholder name, masked card number (last four digits), expiration date, and billing address; store only permitted elements per PCI DSS rules to limit scope of exposure.

Amount and Schedule

Exact dollar amount or a descriptive range, billing frequency, and start date; include how and when amounts may change and how notice will be given.

Authentication

How the cardholder will be identified at signing (email, SMS OTP, or in-person); stronger authentication reduces dispute risk and supports auditability.

Revocation Terms

Procedures for revoking consent, required notice period, and consequences for revocation, including potential collection actions or service suspension.

Data-handling Notice

Statement describing how card data will be stored, masked, or tokenized, and reference to PCI and applicable privacy practices.

Minimum fields to capture on the authorization

Cardholder name: Full legal name

Card number: Mask except last four

Expiration date: MM/YY format

CVV: Do not store CVV

Billing address: Street, city, state, ZIP

Charge terms: Amount, frequency, start date

Step-by-step: completing a Payment Card Authorization

Follow a consistent sequence to collect consent, authenticate the signer, and store the record securely.

01

Prepare the form: Enter merchant name, purpose, and exact charge terms before sending.
02

Collect card details: Have the cardholder enter or confirm cardholder name and billing address.
03

Authenticate signer: Use email OTP or SMS code to verify identity for remote signing.
04

Retain audit record: Save signed copy, timestamp, IP, and any authentication logs.

How to configure an online authorization workflow

Configure fields, authentication, and retention settings before sending to ensure valid, auditable authorizations.

Setting	Configuration
Auto-mask card numbers	Mask storage and show only last four digits
Conditional fields	Show schedule fields for recurring selections
Signer authentication	Enable SMS or email OTP verification
Save as template	Reuse standard authorization wording

Where to send and how to route completed authorizations

Define a clear routing path so the authorization reaches billing, reconciliation, and the cardholder without delay.

Merchant payments team: Deliver signed authorizations to billing for charge scheduling.
Payment gateway: Send tokenized card data to the payment processor for storage or immediate charging.
Cardholder copy: Provide an emailed receipt and signed record to the cardholder automatically.
Accounting archive: Store the authorization with the transaction record for audit and reconciliation.

Delivery channels and platform considerations

Choose delivery methods that balance convenience with authentication strength and secure recordkeeping.

Email delivery: Send secure links to signer email
Secure link: Protect link with OTP or access code
API integration: Automate capture into billing systems

Typical timelines and processing expectations

Expect specific timing for authorization setup, card updates, disputes, and recurring billing notice; set internal SLAs accordingly.

Authorization setup timeframe:

Complete and store authorization before the first scheduled charge

Recurring charge notice:

Notify cardholder prior to billing when terms change

Card update window:

Request updated card details as soon as payments fail

Dispute submission period:

Cardholders commonly have 60–120 days to dispute charges with issuer

Chargeback processing:

Allow 30–90 days for dispute resolution depending on network rules

Common preparation and processing mistakes to avoid

Using vague charge descriptions that leave cardholders unsure what they authorized, increasing dispute risk.
Storing CVV or full PAN in plain documents, which violates PCI DSS and increases breach liability.
Failing to authenticate remote signers adequately, creating weak evidence when contesting a chargeback.
Not providing a signed copy to the cardholder, which reduces transparency and can prompt customer complaints.

Risks and potential penalties from improper authorizations

Chargeback costs: Monetary loss plus processing fees

PCI fines: Fines from card networks for noncompliance

Consumer disputes: Reputational and refund obligations

Authentication failure: Higher fraud and dispute rates

Legal exposure: Contract dispute or statutory claims

Contract invalidation: Authorization may be unenforceable

Supporting documents and export options to retain

Maintain a consistent set of associated records for each authorization to support audits, reconciliations, and dispute responses.

Signed authorization copy

Retain the signed record with timestamp, signer identity, and authentication log to support dispute defense and internal audits.

Tokenized card record

Store payment token or last four digits rather than full PAN; include processor token ID and linkage to the authorization.

Billing schedule

Attach the payment schedule, revision history, and any notice communications so changes are auditable.

PCI evidence

Keep records showing PCI controls, access logs, and any attestations or breach notifications related to payment handling.

Sample eSignature pricing and capability comparison relevant to authorizations

Compare baseline pricing and core capabilities when selecting an eSignature provider for Payment Card Authorizations; signNow is listed first per comparison requirements.

	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, no credit card required	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

Frequently asked questions about Payment Card Authorizations

Answers to common questions on validity, storage, and dispute handling for payment card authorizations.

Need help? Contact support

Is an electronic authorization legally binding?
Yes when it meets the ESIGN four-part test: intent to sign, consent to transact electronically, clear attribution to the signer, and retained reproducible record (15 U.S.C. ch. 96).
Can I store full card numbers?
No. PCI DSS prohibits storing full PANs without strict controls; store tokens or the last four digits and never persist CVV data.
What authentication is recommended?
Use at least email verification plus a secondary factor (SMS OTP or knowledge-based checks) for remote signings to reduce chargeback exposure.
How do I handle revocations?
Provide clear revocation instructions on the authorization and honor timely revocations; document receipt and any follow-up to avoid future disputes.
What should be retained for disputes?
Keep the signed authorization, audit trail (timestamps, IP, auth logs), processor token IDs, and related invoices for the applicable retention period.
Are notarization or witnesses required?
Typically not for routine card authorizations; notarization is uncommon and generally unnecessary unless state law or contract demands it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now