All templates

Credit Card Authorisation Form Template

Prepare limited card-payment permission without collecting card credentials.

Build the Payment Authority

Client and permission

Include the work covered and any GST or agreed charges.

Charging limits
Charging basis

Up to $999,999.99. Include GST and agreed charges.

Schedule

Processor and cancellation

Use the processor’s reference. Never enter card credentials.

State how and when future charges stop after cancellation.

Use the practice’s established enquiry or cancellation channel.

Permission terms only. Keep card credentials in the processor’s channel. Entries stay in this tab and clear when you leave.

Card-payment permission

Enter permission terms

11 permission fields still need an entry.

    Specify the Payment Permission

    A credit card authorisation form records a client’s permission for defined card payments. Enter the practice, cardholder and purpose, then set the charging basis and schedule. Download the unsigned draft for your approved signing process.

    An invoice states what the client owes. A card authority records permission to use a payment method. A bank-account direct-debit request has different payment details and terms. A completed transaction has its own processor record.

    Choose a fixed amount or the invoiced amount up to a per-charge cap. Include any applicable GST and agreed charges within that cap. A recurring arrangement also needs an end date and a total cap.

    The fictional one-off example authorises up to $825.00 for agreed annual accounts, including GST. Selecting recurring payments requires the last charge date and total cap before another draft can be prepared.

    For example, monthly invoice charges capped at $275.00 each and $1,100.00 overall allow four full-cap payments. A fifth full-cap payment would exceed the authority. Lower invoices still count towards the same total cap.

    Write the cancellation terms and contact route before seeking consent. Settle the timing and notice your processor requires. The draft requires fresh consent for changes outside its recorded terms.

    Keep Card Credentials Out of the Form

    Use the payment-method reference created through your processor’s approved collection channel. This credit card form has no fields for a full card number, expiry date or card security code. Keep those details out of every text field.

    The PCI Security Standards Council’s guidance on card verification codes prohibits retaining them after authorisation, even with the customer’s permission. A signed card authority cannot override that rule.

    An offline credit card details form creates collection and storage responsibilities when it contains card data. This permission draft avoids those fields. It does not establish PCI DSS compliance for the practice’s wider payment arrangements.

    The payment-method reference links the draft to a method held elsewhere. Enter the processor’s record reference, without a secret API credential or payment link containing access credentials. This tool neither creates nor verifies that reference.

    Retain and Cancel the Authority

    Download draft creates an editable text file on your device. Review the charging limits and cancellation terms with the cardholder. Complete the signature and signing date through your practice’s approved signing process.

    Keep the signed version with its consent evidence and the relevant processor reference. Record the version accepted, who agreed and the signing record. A typed cardholder name in this tool is not proof of consent.

    Processor requirements still apply. For example, Stripe’s guidance on saving payment methods requires consent for the intended use, with the anticipated timing and frequency and the method used to determine payment amounts. Keep a record of that agreement.

    When permission changes or ends, record the request and its effective time, then stop the affected future charges in the processor. Retain the original consent and cancellation record under your practice’s approved retention policy.

    Entries stay in this tab without uploads or browser storage. Clear entries removes the working details. Leaving or restoring this page clears them too. Downloaded files remain where you save them.

    When the client cancels, record receipt and the effective cancellation, stop future charges under the authority and confirm the change through the agreed contact route. Handle any outstanding invoice separately.

    Entries remain in this tab without uploads or browser storage. Clear entries and leaving the page remove working details. Downloaded copies remain where you save them. The tool does not charge, tokenise or verify a card.