Paid Up

Free template

Credit card authorization form for payment plans: consent wording, not paper forms

To charge a client's card for a deposit and scheduled instalments, you need their written agreement to the amounts and dates, but you shouldn't hold their card number. Here's the wording to show at checkout and the rules behind it.

SWritten by Sam Ade · Facts checked Nov 17, 2026 · Updated

The short answer

  • Don't collect full card numbers on a paper or PDF form. Once you hold a card number, your inbox, laptop and filing cabinet fall under the PCI Data Security Standard. You may never keep the 3-digit security code at all, and an emailed form breaks the rule against sending card numbers by email.
  • Do get written consent to the plan. Before you store a card and charge it later, Visa expects the cardholder to agree to:
    • the total and each instalment's date, amount and currency;
    • how they'll hear about changes;
    • your cancellation and refund policy;
    • where you're located.
  • Let the processor hold the card. The client types it into a hosted payment form (Stripe, Square and others). You keep a token and the last four digits, never the number.
  • Show the consent wording right where the card is saved, with a checkbox or a clear button, and email a copy. The template below covers a deposit plus scheduled instalments.
  • Send a receipt for each payment, and honour cancellations quickly. Missing receipts and charges after a cancellation are what lose "cancelled recurring transaction" disputes.

The problem with paper and PDF card forms

The classic "credit card authorization form" asks for the card number, expiry date, security code and a signature. The client then emails, faxes or hands it back. It feels official. In practice it makes you the place where a full card number is stored, and the rules for that are strict. These are the PCI DSS requirements that a completed form triggers. Requirement numbers are from PCI DSS v4.0; v4.0.1 was a limited revision.

PCI DSS requirements triggered by a completed card authorization form
What happens with the formPCI DSS requirementWhat it means for you
It asks for the CVV / security code3.3.1.2: the card verification code is not kept after authorizationYou must black out or destroy the code after the first charge. The PCI Council says a customer's permission to keep it "has no validity". Later instalments don't need it anyway.
The client emails or texts it back4.2.2: card numbers sent by end-user messaging are protected with strong cryptographyThe PCI Council's FAQ 1085 says plainly that unencrypted card numbers can't be sent by email, chat or SMS. Your inbox now holds card data.
You save the PDF or a scan3.5.1: card numbers are unreadable wherever they're storedEncryption or tokenization on every laptop, phone and cloud folder it reaches, including backups.
You keep the paper9.4.1 and 9.4.6: media with card data is physically secured, and paper is cross-cut shredded when no longer neededA locked cabinet, a log of who can open it, and shredding.
You show the number to staff3.4.1: card numbers are masked when displayedAt most the first six and last four digits, unless someone has a business need to see the whole number.
You key the number into a terminal each monthYour whole setup moves out of the simplest self-assessment (SAQ A)SAQ A is for merchants that don't store, process or transmit card data on their own systems. A form you keep, scan or email takes you out of it, into a much longer questionnaire.

There is also a plain fraud problem. A completed form carries everything needed to use the card. If it's lost, stolen from an inbox, or seen by the wrong employee, the card is compromised, and so is your relationship with the client. The PCI Council's advice when card data arrives by email is to remove it securely and not reply to the email that contains it.

When paper is still used: some hotels and venues take a form for incidentals or damage. If you must, don't ask for the security code, take the form in person rather than by email, put the number into your processor straight away, then shred the paper. For a payment plan there's no need: the client can save the card themselves on a secure payment page.

What Visa and Mastercard expect before you store a card

A payment plan is what the card networks call an installment arrangement. Visa defines it as a series of transactions for a single purchase of goods or services. It is a "standing instruction" from the cardholder that lets you start later charges yourself: a merchant-initiated transaction on a stored credential. Visa's stored-credential framework says you need a consent agreement with the cardholder before you store the card. For merchant-initiated charges, it lists these contents:

Visa consent agreement contents for stored-credential instalments, and where to put each in your checkout
Visa expects the agreement to includeFor a payment plan, sayWhere it goes
A truncated version of the card"Visa ending 4242"Confirmation email (the payment form shows it on screen)
How the stored card will be used"to charge the payments in your payment plan"Consent wording
Total price and terms of future payments: dates, amounts, currencyThe full schedule, with the total, in US dollarsConsent wording and agreement
How the cardholder will be told about changes"We'll email you before any change"Consent wording
When the consent ends"ends after the last payment on [date]"Consent wording
Cancellation and refund policyA link to your cancellation termsNext to the checkbox
Merchant locationCity and stateConsent wording or footer
Any surcharge or convenience feeThe fee per payment, if you add oneConsent wording (see card fee rules)

The same Visa document says you must:

  • keep the agreement for as long as it runs and give it to the card issuer if asked;
  • tell the cardholder about changes to it;
  • send receipts for installments;
  • not charge after the agreed period, after a cancellation, or after a decline response.

That document is from 2017. Visa's current rule book has reworded parts of it, but the core terms haven't gone away.

Mastercard has similar rules for credential-on-file and recurring payments: show the terms when the card is collected, get the cardholder's express agreement, make cancelling easy, and keep the agreement. We couldn't read Mastercard's current rule text directly, so check the detail with your processor. Stripe sums up what both networks need in its own docs. Your terms must cover the customer's agreement to a series of payments, their timing and frequency, and how the amount is set. You must also "keep a record of your customer's written agreement".

Consent wording to copy: deposit plus instalments

Put this next to the card form, above a checkbox or the Pay button, and repeat it in the confirmation email. Fill in your details below to update it (optional; nothing is sent or saved), or replace the blanks by hand.

Payment plan: card authorization

By saving your card, you authorize [business name] to charge it for your payment plan for [booking]:

  • a deposit of $[amount] today, and
  • [number] payments of $[amount], monthly, starting [date],

for a total of $[total] in US dollars, as set out in the payment schedule in your agreement. Each payment is charged on its date; if a charge fails, we'll try again within a few days and email you. This authorization ends when the last payment is made.

We'll email you a reminder before each payment and a receipt after it. If we ever need to change an amount or a date, we'll tell you by email first, and we'll ask for your agreement again before charging more than the total above. You can change your card or pay early at any time from your payment link.

To stop future charges, email [email]. Stopping charges doesn't cancel your booking; our cancellation and refund policy explains what happens if you cancel. [business name], [city, state].

☐ I agree to these payment terms and the booking agreement.

Confirmation email (send right after the card is saved)

Subject: Your payment plan with [business name] is set up

Hi [name], your card ending [4242] is saved for your payment plan. Today we charged your deposit of $[amount]. The remaining [number] payments of $[amount] will be charged on [date list], ending on [last date], for a total of $[total]. We'll email you before each one. Your agreement and cancellation policy are here: [link]. To change your card, pay early or ask a question, reply to this email or use your payment link.

What makes this wording work

  • Every amount and date is fixed. That meets Visa's installment terms. A client who later says "I didn't know I'd be charged" has the schedule in their own inbox.
  • The end is stated. A known end date and total is what separates a payment plan from a subscription. It also keeps you clear of automatic-renewal rules (see below).
  • Cancelling the card and cancelling the booking are separate. This is the line most templates miss, and it's the one that wins disputes.
  • No fees appear unless you charge them. If you add a card surcharge, Visa expects the amount in the agreement, and state law may ban it. See card fees and surcharges.

Debit cards and Regulation E

Many clients pay with a debit card that looks the same as a credit card at checkout. Regulation E, the federal rule for electronic transfers from bank accounts, doesn't cover credit cards. It does cover recurring charges to a debit card. Section 1005.10(b) says those must be authorized by a writing signed or similarly authenticated by the consumer, and the business must give the consumer a copy.

The CFPB's interpretation (comment 10(b)-7) gives a business a defence if a client says a card is credit when it's actually debit. But once you learn it's debit, you must get a written authorization quickly or stop charging. The easier route is to treat every saved card as if it were debit:

  • get the consent online, where an accepted checkbox counts as "similarly authenticated" under the E-Sign Act;
  • email the client a copy.

The wording and email above do both.

Defending a "cancelled recurring" dispute

When a client disputes an instalment, the bank assigns a reason code. Three are common on payment plans:

Common card dispute reasons on payment plans and how to answer them
DisputeCodesClient is sayingWhat wins it
Cancelled recurring transactionVisa 13.2; Mastercard 4841 (Stripe: "subscription canceled")"I cancelled, and you charged me anyway."The signed agreement and cancellation policy. Proof the client didn't cancel, or cancelled for a later date. Your correspondence. Proof the charge was for service before the cancellation took effect.
Card-absent fraudVisa 10.4; Mastercard 4837"I didn't make this payment."3D Secure on the first payment (the liability usually shifts to the bank). The contract. Earlier undisputed payments on the same card. Visa Compelling Evidence 3.0 where it applies.
Services not providedVisa 13.1; Mastercard 4853"The event hasn't happened" or "it was cancelled"The service date, the agreement showing payments fall due before the service, and your cancellation terms.

A wrinkle with 13.2: Visa's October 2026 merchant guide lists installment plans among recurring transactions. Elsewhere it says the condition "may also apply" to installments in Europe. Assume a client can use it on a US plan, and keep the evidence ready.

Compelling Evidence 3.0 is Visa's way to beat "friendly fraud" on card-absent fraud claims (10.4). It needs at least two earlier undisputed payments on the same card from 120 to 365 days before the dispute, with matching details such as IP address or device. Long plans often qualify by the third or fourth instalment. Stripe's evidence form for this category asks for the cancellation policy, how it was shown to the client, the service date, the signed contract and your messages with the client.

Worked example. A photographer's client pays a $1,500 deposit and saves a card for four $1,125 instalments before a $6,000 wedding. In month three the couple postpone, email "please stop charging us", and dispute the next instalment as cancelled recurring. If the photographer charged after that email, the dispute is very hard to win, whatever the contract says. Visa's guide tells merchants to stop billing at once on cancellation. The right move: stop the charges, confirm in writing what the contract says is still owed, and ask for payment on a new authorization. The evidence then shows a cancelled authorization was respected and a new one was given.

When a client asks you to stop charging their card

  1. 1

    Stop the next charge straight away

    Visa's framework says no further charges after a cancellation under your policy, and asks for written confirmation with a credit receipt within 3 business days when a refund is due.

  2. 2

    Confirm in writing

    Reply with the date you stopped charges, what has been paid, and what your agreement says about the rest. Keep the tone factual.

  3. 3

    Separate the card from the contract

    "Stop charging my card" might mean "I'll pay another way" or "I'm cancelling the booking". Ask which. If they're cancelling, your cancellation policy decides what's owed or refunded.

  4. 4

    Get a new consent before charging again

    If they want to carry on, get them to save a card again or accept new terms. Don't restart the old schedule quietly.

Auto-renewal laws. The federal Restore Online Shoppers' Confidence Act (15 U.S.C. 8403) and state automatic-renewal laws such as California's apply to "negative option" sales, where the customer's silence counts as agreement to keep paying. Typical examples are subscriptions that renew or run until cancelled. A fixed plan of, say, five instalments for one wedding, with a stated total and end date, most likely isn't one. That's our reading, not settled case law, so check with an attorney if your plan can renew, extend or add charges. The FTC's 2024 "click-to-cancel" rule was vacated by the Eighth Circuit in July 2025, and the FTC reopened the question in 2026; no click-to-cancel rule is in force today. Following its spirit costs little: make stopping charges as easy as starting them.

UK and Europe: one extra step

In the UK and EU, Strong Customer Authentication applies. The client usually completes a bank check (3D Secure) when they first save the card. Later instalments are then flagged as merchant-initiated and, in most cases, go through without another check. Stripe says exemptions "aren't guaranteed", so a bank can still ask the client to authenticate a later payment. Visa's European rules also ask merchants to notify the cardholder before a recurring charge in some cases, such as after a change of date or amount. UK businesses can't add a surcharge to consumer cards at all. Where your payment provider offers it, UK Direct Debit (Bacs) is a cheaper bank route, with its own mandate and guarantee.

How Paid Up handles it

With Paid Up, nobody at your business sees or stores a card number:

  • The client signs your payment plan agreement online, which includes an automatic-payments authorization with the full schedule.
  • They pay the deposit in Stripe's Payment Element, which saves the card on your own Stripe account for later off-session charges.
  • The first card payment requests 3D Secure. Apple Pay is told it's a payment plan, with the amount, frequency and end date.
  • Later payments are charged on their dates. Clients get reminders 7 and 3 days before, and a receipt after each payment.
  • The client can change the card or pay early from their link.
  • If a payment fails, it's retried twice, two days apart, and you're alerted. A lost, stolen or closed card isn't retried, and you're told on the first failure.

Limits: Paid Up doesn't answer disputes for you; you respond with the evidence through Stripe, and the signed agreement and payment history in Paid Up are what you'll attach. See pricing.

Questions people ask

Is a credit card authorization form legally required?

No federal law requires a specific form for credit cards. The card networks require the cardholder's agreement before you store a card and charge it later, and you need proof of it if the client disputes a charge. For debit cards, Regulation E requires a signed or similarly authenticated authorization for recurring charges. A clear consent at checkout plus a signed agreement covers both.

Can I keep a client's card number on file in a spreadsheet or on paper?

Not safely. Storing a full card number brings your own systems and filing cabinets into PCI DSS: it must be unreadable wherever it's stored electronically, paper must be locked up and shredded, and the security code may never be kept after the first charge. A payment processor that stores the card for you avoids almost all of that.

Is it legal to email a credit card authorization form?

Emailing a blank form is fine. Getting a completed one back by email isn't: the PCI Security Standards Council says unprotected card numbers must not be sent by email, chat or text. Send the client a secure payment link instead, where they type the card into the processor's form.

Can I keep the CVV to charge later instalments?

No. PCI DSS forbids keeping the card verification code after the payment is authorized, even if encrypted and even if the client agrees. Later instalments don't need it: they're charged as merchant-initiated payments on a stored credential.

Does a signed authorization stop chargebacks?

It doesn't stop a client from filing one, but it's the core of your evidence. For a 'cancelled recurring' dispute, you show the agreement, the cancellation policy the client accepted, and that the service wasn't cancelled under it. For a fraud dispute, 3D Secure on the first payment usually shifts the loss to the bank.

Do automatic renewal laws apply to payment plans?

Probably not to a fixed number of instalments for one service with a set total and end date. Those laws target subscriptions that renew until the customer cancels. The clear disclosure and consent they require is good practice anyway; check with an attorney if your plan can renew or extend.

Sources

  1. PCI SSC FAQ 1085: Can unencrypted PANs be sent over e-mail, instant messaging, SMS, or chat?: no: Requirement 4.2.2 prohibits sending unprotected card numbers by end-user messaging (read Nov 17, 2026)
  2. PCI SSC FAQ: Does PCI DSS allow faxing of payment card numbers?: paper with card data falls under Requirement 9.4; the CVV must be removed before the paper is kept (read Nov 17, 2026)
  3. PCI SSC FAQ 1574: storing card verification codes: a customer's permission to keep the CVV 'has no validity for PCI DSS' (read Nov 17, 2026)
  4. PCI DSS v4.0 Self-Assessment Questionnaire D (Merchants): requirement text: 3.3.1, 3.3.1.2, 3.5.1, 4.2.2, 9.4.1, 9.4.6 (read Nov 17, 2026)
  5. PCI DSS v4.0 Self-Assessment Questionnaire A: eligibility: no account data stored, processed or transmitted on merchant systems (read Nov 17, 2026)
  6. Visa, Improving Authorization Management for Transactions with Stored Credentials (2017): Visa's consent-agreement terms for stored credentials and installments (public copy of Visa's document) (read Nov 17, 2026)
  7. Visa, Dispute Management Guidelines for Visa Merchants (Oct 2026): 13.2 Cancelled Recurring Transaction; 10.4 card-absent fraud; Compelling Evidence 3.0 (read Nov 17, 2026)
  8. Stripe Docs, Save payment details during payment (Compliance): terms must cover the series of payments, timing and how amounts are set; keep the written agreement (read Nov 17, 2026)
  9. Stripe Docs, Customer-initiated and merchant-initiated transactions: agreement before MITs; new agreement if the card brand changes (read Nov 17, 2026)
  10. Stripe Docs, Dispute categories: 'subscription canceled' maps to Visa 13.2 and Mastercard 4841; evidence fields (read Nov 17, 2026)
  11. Stripe Docs, Strong Customer Authentication: authenticate when saving; off-session charges as merchant-initiated with a mandate (read Nov 17, 2026)
  12. Regulation E Official Interpretation, comment 10(b)-7 (CFPB): recurring debit-card charges need a signed or similarly authenticated authorization (read Nov 17, 2026)
  13. 15 U.S.C. 8403, Restore Online Shoppers' Confidence Act (Cornell LII): rules for online negative-option sales (read Nov 17, 2026)

About this page

General information, not legal advice. Card network rules are private contracts that change twice a year, and Visa and Mastercard publish them only in part; where we couldn't read a current rule directly, the page says so. Check your processor's terms, and have an attorney review your wording. Spotted something out of date? Tell us at [email protected] and we'll correct it.

Save the card without ever seeing it.

Clients sign the plan and save their card in Stripe's secure form. Each payment is charged on its date, with a reminder before it and a receipt after. Start on the Free plan.