MAKE THE DOCUMENT WORK FOR YOUR SITUATION
About this credit card authorization form
A card authorization form records permission for defined payments. It should identify the merchant, cardholder, processor-managed payment method, and precise charge scope. A signed form does not process a payment or remove the cardholder’s dispute rights.
When to use it
- A merchant needs a record of consent for a specified one-time charge.
- A customer agrees to recurring payments with clear frequency, limits, and revocation instructions.
- Staff need to reconcile a signed permission record with the secure processor’s customer reference.
What to gather before completing it
- Set up the payment method in an approved secure processor before completing the consent record.
- Record only the last four digits and processor reference in this browser form. Do not add a PAN or CVV to notes.
- Specify the charge purpose, one-time or recurring status, amount or maximum, first charge, frequency, and end date.
- State how the customer can cancel future authorization and how receipts and policy information will be delivered.
- Review the processor’s authorization and retention requirements and the applicable payment-network rules.
Common mistakes to avoid
- Treating one-time consent as permission for indefinite future charges.
- Storing a CVV with the signed authorization.
- Leaving variable charges uncapped or failing to explain what changes the amount.
- Using a consent form as a waiver of chargeback or statutory rights.
After you complete the document
- Provide the cardholder a copy and retain the reference through the approved records process.
- Process only charges within the authorized scope.
- Record changes, cancellations, receipts, and any disputes without storing prohibited authentication data.
What the template includes
The online builder and downloaded documents use the same fields. A selected state can add relevant research prompts. Complete only applicable items; add explanations for exceptions rather than assuming a blank entry resolves them.
Document details4 inputs +
Set the date, jurisdiction, and your internal reference.
- Document date *
- US state *
- County
- Document reference
People & organizations8 inputs +
Use legal names and current contact information.
- Merchant legal name *
- Merchant address *
- Merchant email
- Merchant phone
- Cardholder legal name *
- Cardholder address *
- Cardholder email
- Cardholder phone
Card & processor reference6 inputs +
Use a secure payment processor for full card details. This builder requests only a reference and the last four digits.
- Name on card *
- Card brand
- Card last four digits *
- Payment processor *
- Processor customer / payment-method reference *
- Billing address *
Charge authorization11 inputs +
Define exactly what may be charged, when, and how the authorization ends.
- Purchase / service description *
- Authorization type
- Authorized amount (USD) *
- Maximum variable charge (USD)
- First / one-time charge date *
- Recurring frequency
- Recurring end date
- Variable-charge notice arrangements
- Cancellation / revocation instructions *
- Refund policy reference
- Receipt delivery email
Additional details & signing7 inputs +
Add attachments, exceptions, and the names of authorized signers.
- Attachments / supporting records
- Exceptions / additional terms
- First signer printed name
- First signer title
- Second signer printed name
- Second signer title
- Signing date
Practical tips
- Use a processor-managed payment-method reference instead of a full card number.
- Do not place a CVV in this form, notes, or attachments. PCI rules prohibit retaining verification codes after authorization.
- Separate one-time permission from recurring permission and keep the scope narrow.
Before signing or submitting
Authorization requirements depend on the processor, card-network rules, transaction, and consumer rights. This form does not establish PCI compliance or waive dispute rights.