# Credit Card Authorization Form: Template and Guide (2026)

> What a credit card authorization form is, what it must include, a free template, PCI rules for storing it, and when an online checkout with saved cards is the better option.
- **Author**: Deepak Jangir
- **Published**: 2026-11-08
- **Category**: Payments, Compliance
- **URL**: https://dodopayments.com/blogs/en/credit-card-authorization-form

---

A credit card authorization form is a signed document in which a cardholder gives a business permission to charge their card, either once or on a recurring schedule, without the cardholder being present for each charge. It records who the cardholder is, which card can be charged, how much, how often, and for what. Businesses use it as consent evidence for phone orders, retainers, deposits and recurring billing, and as supporting evidence if a charge is later disputed.

The form is useful, but it is also widely misunderstood. It does not make a charge immune to chargebacks, and the way many businesses store completed forms (a PDF in a shared drive, with the full card number and security code written on it) breaks PCI DSS rules. This guide covers what the form must include, a copy-ready template, how to store it safely, and when a hosted checkout that saves the card is the better tool for the job.

## What Is a Credit Card Authorization Form Used For?

The common thread is a **card-not-present** charge that the customer does not initiate in the moment. If the customer types their card into a checkout page and clicks pay, the checkout itself captures consent. When you charge them later, or someone on your team keys the card in on their behalf, you need a record that they agreed.

Typical situations:

- **Recurring or retainer billing** for agencies, consultants and B2B services that invoice monthly
- **Phone and mail orders (MOTO)**, where a staff member keys the card into a [virtual terminal](https://dodopayments.com/blogs/virtual-terminal)
- **Deposits and incidentals** in hospitality, rentals and events
- **Usage or overage charges** where the final amount is unknown when the customer signs up
- **Card-on-file arrangements** for repeat customers who do not want to re-enter details

For software companies selling online, most of these needs are better served by a checkout that stores the card as a token and records consent automatically. We cover that trade-off below, and our guide to [card-on-file payments](https://dodopayments.com/blogs/card-on-file-payments) goes deeper on the stored-credential rules.

## What a Credit Card Authorization Form Must Include

A form that is missing key fields is weak evidence. A good one includes:

| Section | Fields | Why it matters |
| --- | --- | --- |
| Business details | Legal business name, address, contact email or phone | Shows the cardholder knew who would charge them |
| Cardholder details | Full name as on card, billing address, email, phone | Supports address verification and identity |
| Card details | Card brand, card number, expiry date | Needed to run the charge (see PCI section) |
| Charge terms | Amount or pricing basis, currency, frequency, start date, end date or "until cancelled" | The core of the consent |
| Description | What the charge is for (plan name, service, order number) | Rebuts "I don't recognize this" disputes |
| Cancellation terms | How and when the customer can cancel | Required disclosure for recurring charges |
| Authorization statement | Plain-language consent paragraph | The legal heart of the form |
| Signature and date | Cardholder signature, printed name, date signed | Proves the consent was given |

Two fields are deliberately absent from that table: the **card security code (CVV)** and a photo of the card. Those are covered in the PCI section, and the short version is that you should not keep either.

## Credit Card Authorization Form Template

Copy the template below into your own document tool and adapt the bracketed fields. Have your legal advisor review it for your jurisdiction and industry.

```text
CREDIT CARD AUTHORIZATION FORM

Business: [Legal business name]
Address: [Business address]
Contact: [Support email / phone]

CARDHOLDER INFORMATION
Name on card: ______________________________
Billing address: ___________________________
City / State / ZIP: ________________________
Country: ___________________________________
Email: _____________________ Phone: ________

CARD INFORMATION
Card type:  [ ] Visa  [ ] Mastercard  [ ] American Express  [ ] Discover
Card number: _______________________________
Expiration (MM/YY): ________
(Do not write the security code on this form.)

CHARGE DETAILS
Description of goods/services: _____________
Amount: [ ] Fixed: $________  [ ] Variable, based on: ____________
Currency: ____
Frequency: [ ] One-time  [ ] Weekly  [ ] Monthly  [ ] Annually  [ ] Other: ______
First charge date: __________
End date: __________  [ ] Until cancelled in writing

CANCELLATION
I may cancel future charges by emailing [support email] at least
[X] days before the next charge date.

AUTHORIZATION
I, ____________________, authorize [Business name] to charge the card
above for the amounts and on the schedule described in this form.
I confirm that I am the cardholder or an authorized user of this card,
that the information above is accurate, and that I will not dispute
charges made in line with this authorization. A copy of this form and
a receipt will be provided for each charge.

Cardholder signature: ______________________   Date: __________
Printed name: ______________________________
```

A few practical notes on the template:

- **"Variable amount" needs a basis.** If you bill usage or overages, describe how the amount is calculated (for example, "$0.02 per API call above 100,000 per month"). Vague terms weaken the form as evidence.
- **Send a copy.** Email the signed form back to the cardholder. Card network rules for stored credentials expect the cardholder to have a record of the agreement.
- **Send receipts.** A receipt for every charge, referencing the agreement, reduces "unrecognized charge" disputes more than the form itself.

## Is a Credit Card Authorization Form Legally Binding?

A signed authorization form is a contract between you and the cardholder, and it is evidence of consent. It is not a guarantee against chargebacks, because the dispute decision belongs to the cardholder's bank under card network rules, not to your contract.

How much the form helps depends on the dispute reason:

| Dispute reason | Does the form help? | Notes |
| --- | --- | --- |
| Unrecognized charge | Yes | Shows the cardholder agreed to this merchant and amount |
| Recurring charge after cancellation | Partly | Helps only if you prove they did not cancel per the stated terms |
| Services not provided | Weakly | You also need delivery or usage evidence |
| Fraud (stolen card) | Rarely | A signature on a PDF is easy to forge and banks know it |

For card-not-present fraud claims, issuers generally weigh authentication data (such as [3D Secure](https://dodopayments.com/blogs/3d-secure-3ds-payment-authentication)), AVS and CVV results, device data and prior undisputed history more heavily than a signed form. That is why a modern checkout often produces stronger evidence than paperwork. Our [chargeback reason codes reference](https://dodopayments.com/blogs/chargeback-reason-codes) shows what evidence each dispute category expects.

## PCI DSS Rules for Storing Authorization Forms

This is where most small businesses go wrong. A completed authorization form contains cardholder data, so how you store it is governed by the Payment Card Industry Data Security Standard. The key rules:

- **Never store the CVV after authorization.** The card verification code is "sensitive authentication data" under PCI DSS. It may not be retained after the authorization is complete, even if encrypted. If your form collects it, you must destroy that portion as soon as the first charge is authorized. The safer design is to never collect it on paper at all. See our explainer on [what CVV is](https://dodopayments.com/blogs/what-is-cvv) for why the rule exists.
- **Protect the card number.** If you keep the full primary account number (PAN), it must be rendered unreadable wherever it is stored (for example, encrypted or truncated) and access must be restricted to staff who need it.
- **No email or chat.** Do not accept completed forms with full card numbers over email, chat or shared drives that are not part of a PCI-compliant environment.
- **Paper counts.** Physical forms must be locked away, access logged, and shredded when no longer needed.
- **Keep scope small.** Every system that touches the full card number is in PCI scope. Each form you store increases your compliance burden.

The cleanest approach is to run the first charge through a provider that tokenizes the card, then keep only the token reference, the last four digits and the signed consent terms. Our [PCI compliance checklist for SaaS](https://dodopayments.com/blogs/pci-compliance-checklist-saas) and guide to [payment tokenization](https://dodopayments.com/blogs/payment-tokenization) explain how tokenization shrinks your PCI scope.

Bank debits follow a different rulebook. If you also pull payments by ACH, the consent and record-keeping requirements come from the Nacha Operating Rules rather than PCI DSS, as covered in our [ACH authorization form guide](https://dodopayments.com/blogs/ach-authorization-form).

## Credit Card Authorization Form vs Online Checkout

For a SaaS or digital product business, the paper form is usually the legacy option. A hosted checkout with saved payment methods gives you the same permission to charge again, with better evidence and less risk:

```mermaid
flowchart LR
    subgraph paper ["Paper / PDF form"]
        A["Customer fills form
with card number"] --> B["Staff keys card
into terminal"]
        B --> C["Form stored with PAN
(PCI scope)"]
    end
    subgraph online ["Hosted checkout"]
        D["Customer pays at checkout
and agrees to terms"] --> E["Card tokenized
+ 3DS where needed"]
        E --> F["Token stored,
future charges via API"]
    end
```

| Factor | Authorization form | Hosted checkout with saved card |
| --- | --- | --- |
| Who enters the card | Your staff | The customer |
| Card data you store | Full PAN on paper or PDF | A token and the last 4 digits |
| Authentication | None | 3D Secure, AVS and CVV checks at first payment |
| Consent record | Signature on a document | Timestamped checkout terms and receipts |
| Fees | Keyed-entry rates are often higher | Standard online rates |
| Dispute evidence | Weak for fraud claims | Stronger, includes authentication results |

With [Dodo Payments](https://dodopayments.com), the customer completes a hosted checkout once, the card is tokenized, and later charges use the saved payment method. The [cards documentation](https://docs.dodopayments.com/features/payment-methods/cards) shows how to charge a saved card for a returning customer without showing checkout again:

```javascript
// Charge a returning customer's saved card (consent captured at first checkout)
const methods = await client.customers.retrievePaymentMethods('cus_123');

const session = await client.checkoutSessions.create({
  product_cart: [{ product_id: 'pdt_retainer_monthly', quantity: 1 }],
  customer: { customer_id: 'cus_123' },
  payment_method_id: methods.items[0].payment_method_id,
  confirm: true,
  // confirm: true requires a billing address; with minimal_address,
  // country and zipcode are enough (pull them from the customer profile)
  minimal_address: true,
  billing_address: { country: 'US', zipcode: '94102' },
  return_url: 'https://yourapp.com/billing/done',
});
```

Because the charge is confirmed without a checkout page, there is no redirect to rely on. Treat the `payment.succeeded` and `payment.failed` [webhooks](https://docs.dodopayments.com/developer-resources/webhooks) as the source of truth for whether the charge went through.

For variable amounts such as overages or retainers that change month to month, [on-demand subscriptions](https://docs.dodopayments.com/developer-resources/ondemand-subscriptions) authorize the payment method once and let your server charge custom amounts later. For fixed schedules, standard [subscriptions](https://docs.dodopayments.com/features/subscription) handle renewals, retries and [dunning](https://dodopayments.com/blogs/dunning-management) automatically, and because Dodo Payments acts as the [merchant of record](https://dodopayments.com/blogs/what-is-a-merchant-of-record), it also handles sales tax and disputes as the legal seller.

## When You Still Need a Signed Authorization Form

Paper or e-signed forms still make sense in a few cases:

- **Enterprise contracts** where procurement wants a signed document alongside the order form, even if the actual card entry happens on a hosted page
- **Phone sales** where the customer cannot or will not complete an online checkout
- **High-value, irregular charges** such as large deposits, where a written description of the charge terms protects both sides
- **Industries with specific requirements** (hospitality and rentals often have their own conventions)

In these cases, a hybrid works well: use the signed form for the **terms** and send the customer a [payment link](https://dodopayments.com/blogs/what-is-a-payment-link) to enter the card themselves. You get the written agreement without ever handling the card number. The [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) covers static payment links that need no code.

## Common Mistakes With Card Authorization Forms

- **Collecting the CVV and keeping it.** This is the most common PCI violation for small businesses.
- **Undefined amounts.** "Charges as needed" is not a meaningful authorization. Write the pricing basis.
- **No cancellation path.** Recurring consent without a clear way to cancel invites [friendly fraud](https://dodopayments.com/blogs/friendly-fraud-prevention) disputes.
- **Forgetting the receipt.** Customers dispute charges they do not recognize. A clear [statement descriptor](https://dodopayments.com/blogs/statement-descriptor) and a receipt for every charge prevent many of these.
- **Treating the form as a chargeback shield.** It is one piece of evidence. Pair it with authentication, delivery proof and communication history.

## FAQ

### What is a credit card authorization form?

It is a document in which a cardholder authorizes a business to charge their card for a specific amount or pricing basis, on a stated schedule, without being present for each charge. It typically includes cardholder and card details, charge terms, cancellation terms and a signature.

### Can I keep the CVV on a credit card authorization form?

No. PCI DSS prohibits storing the card security code after the transaction is authorized, even if encrypted. The safest approach is to leave the CVV off the form entirely and have the customer enter the card themselves through a hosted checkout or payment link.

### Does a signed authorization form prevent chargebacks?

It helps with "unrecognized charge" and some recurring-billing disputes, but it does not prevent chargebacks. For fraud claims, issuers give more weight to authentication results such as 3D Secure, AVS and CVV checks than to a signature on a document.

### Is an e-signature valid on a credit card authorization form?

In most jurisdictions, including the US under the ESIGN Act, electronic signatures are generally valid for this kind of agreement. Keep the audit trail from your e-signature tool along with the signed document.

### Do SaaS companies need credit card authorization forms?

Usually not for self-serve sales. A hosted checkout that tokenizes the card and records the customer's agreement to recurring terms gives you equivalent consent with stronger evidence and much less PCI exposure. Forms remain useful for phone sales and some enterprise deals.

## Conclusion

A credit card authorization form records consent for charges the customer does not initiate in the moment. Include clear charge terms, a cancellation path and a signature, never keep the CVV, and protect any stored card number under PCI DSS. For most online businesses, letting the customer pay once through a tokenized checkout and charging the saved card later is safer and produces better dispute evidence. If you want saved cards, recurring billing, tax and disputes handled in one place, see [Dodo Payments pricing](https://dodopayments.com/pricing).
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)