Skip to content
SwipeSeal
Menu

Hotel credit card authorization form, free and printable

Fill in your property, the booking and your cancellation and no-show terms, then print the form for the cardholder. Use it at the front desk, or for a third-party booking where someone else pays for the guest. Card fields print blank, there is no security code box, and the receipt checks your terms against what Visa asks a hotel to disclose.

Dithered print of a front desk with a service bell, a key card, a card terminal and a blank form with a pen

Key figures

Security code boxNone

What a hotel credit card authorization form is

It is the cardholder's signed permission for a hotel to charge their card for a stay: the room, a deposit, a hold for incidentals, or a no-show charge. The common case is a third-party booking, where a parent, an employer or a friend pays for a guest who arrives on their own. The form says who the guest is, which nights, which charges the card covers, and what happens if nobody turns up.

Not a hotel? The general credit card authorization form covers one-time and recurring charges for any business. This page reuses its printed form, so both carry the same blank card block and the same missing security code box.

How to use this generator

  1. 01Pick who is paying: the guest at the desk, or someone else paying for the guest.
  2. 02Fill in your property, the booking and your cancellation and no-show terms. Leave a date or an amount blank to write it in per booking.
  3. 03For a third-party booking, tick what the card covers and choose how the card reaches you. A payment link keeps the number off paper and out of email.
  4. 04Print it, or choose Save as PDF in the print dialog. Copy as text pastes it into Word or Google Docs.
  5. 05The cardholder fills in the card fields and signs. Enter the card with your processor, cut off the card strip and cross-cut shred it.

Front desk or a booking sent in: how the card should reach you

The form is the same paper in both cases. What changes is where the card number travels. At the desk the card is in front of you; for a booking sent in, it can arrive by phone, by email, as a photo or on paper, and each route lands differently under PCI DSS. Pick how the card is reaching you.

How is the card reaching you?

RouteDip or tap it

The card is in front of you, so run it on your terminal and let the form carry the terms, the card brand and the last four digits. Nothing on the paper needs the full number. Visa also tells merchants not to ask for the security code on a card-present transaction.

RuleVisa Rules §5.4.3.1; generator option “Terminal only”

Why an emailed form with a card number is a problem

Third-party forms usually go out by email, and that part is fine: a blank PDF holds no card data. The trouble starts when the filled-in form comes back the same way. Two rules meet in that reply.

  • Req. 4.2.2 “PAN is secured with strong cryptography whenever it is sent via end-user messaging technologies.” Its note also covers card numbers that arrive unasked, over a channel never meant for them.
  • Req. 3.5.1 “PAN is rendered unreadable anywhere it is stored.” An attachment sitting in a mailbox or a download folder is the number stored, in plain view.

The Council's guidance for phone payments says it outright: “Never send CHD over an unencrypted, end-user messaging medium such as chat, social media, SMS (short message service)/text, or e-mail”. A printed copy of that email is then paper with card data too, under Requirement 9.

Safer routes for a third-party booking

  • A payment link from your processor. The cardholder enters the card on the processor's page; you get the payment and the signed terms, never the number. Pick “Payment link” in the generator and the form prints with no card fields.
  • A phone call keyed straight in. Take the card on the phone and type it into your processor's virtual terminal without writing it down. The phone payment options compare ways to take cards by phone without hearing them.
  • The paper form, posted or handed in. Enter the card, then shred the cut-off strip.

Why there is no security code box

Where a security code box might sit, this form prints a warning instead. The card verification code is “the three- or four-digit value printed on the front or back of a payment card”, and PCI DSS says “The card verification code is not stored upon completion of the authorization process.” A signed form you keep on file would store it.

Visa goes further for paper. Among its rules for using card details, a merchant must “Not request a Card Verification Value 2 (CVV2) from the Cardholder on any written form”. And holding a card for later charges does not change the answer: the Council says codes “are not needed for card-on-file or recurring transactions”, and bars keeping them for concierge-style services, “for example, for making restaurant reservations or purchasing theatre tickets.”

Reservations, deposits and holds: what Visa's rules ask

Visa calls a booking secured with a card but no payment a guaranteed reservation. For one, the hotel must disclose:

  • the date and time the stay begins, and where
  • the date and time by which the cardholder must cancel to avoid a penalty
  • the amount the cardholder pays if the reservation is not cancelled in time and not claimed

The receipt above the form checks your terms against that list. Visa's clocks for the same booking, from its rules for guaranteed reservations and its dispute rules:

Written confirmation after a phone bookingWithin 24 hours

Free cancellation after that confirmationAt least 24 hours

Room held after the agreed arrival timeAt least 24 hours

No-show charge a cardholder can disputeOver one night plus tax

That last line is why the generator's no-show term reads one night's room rate plus tax. A cardholder can dispute a no-show charge “for more than one day's accommodation or rental and applicable taxes”.

Deposits. Before taking an advance payment, Visa asks for the cardholder's agreement to terms that include the description, the total purchase price, and the cancellation and refund policies, “including the date that any cancellation privileges expire without Advance Payment forfeiture”. If you take a deposit, put the stay total in your other terms.

Incidentals holds. When the final amount is not known, Visa lets a merchant send an estimated authorization, and a hold for incidentals at check-in is one. The amount must be “a genuine estimation of what the Cardholder will spend”, the hotel tells the cardholder the amount and that further authorizations may follow, and the estimate leaves out “potential damage, theft, other delayed charges, insurance premiums, or tips.”

Worked example: an employer pays for a visiting consultant

The generator opens on this case. A company books two nights for a consultant and pays for the room only. The consultant settles anything else at check-out. Here is who writes what.

Who fills in each field of a third-party hotel credit card authorization form
FieldFilled in byOn the printed form
Hotel name, address, phone, emailHotelHarbor Lane Inn, 42 Quay Street, Seaview
Guest name, confirmation numberHotelThe guest the employer booked for
Arrival, departure, cancel byHotelThe booking's dates, or blank lines
This card coversHotelRoom and tax
The guest pays at check-outHotelIncidentals, food and drink, parking
Most this card will be chargedHotel or cardholderA cap, or a blank line
Cancellation and no-show termsHotelOne line each; no-show is one night plus tax
Cardholder name, phone, emailCardholderBlank lines
Card number, expiry, billing ZIP and addressCardholderBlank lines on the cut-off strip, or none with a payment link
Security codeNobodyNo box; a printed warning

With the defaults the receipt above the form shows the hotel's location and the no-show charge as stated, and the arrival date and cancel-by time as blank lines, to fill in per booking. Tick incidentals and the hold appears, with a line asking for its amount. Switch the card to “Payment link” and the card fields disappear from the paper altogether.

Where the rules say so

  • Req. 3.3.1.2No card verification code after authorization
  • FAQ 1280No code kept for card-on-file or concierge-style use
  • Req. 3.5.1A stored card number is unreadable
  • Req. 4.2.2A card number sent by email or chat is strongly encrypted
  • Req. 9.4.6Paper destroyed when no longer needed; secure containers until then
  • Phone suppl. 2.3.1A card number written down on a call is storage
  • Visa §5.4.3.1No CVV2 on any written form
  • Visa §5.4.2.5What a guaranteed reservation discloses
  • Visa §5.7.2.4What an incidentals hold may include

PCI DSS v4.0.1 wording from the Council's Prioritized Approach Tool; Visa wording from its April 2026 rules. Read on 2026-10-22. Full list under Sources.

Which questionnaire do your channels point to? Run the SAQ type finder. More card-handling tools and guides sit under Payments & Card Data.

Sources

  1. PCI SSC: Prioritized Approach Tool for PCI DSS v4.0.1 (requirement text for 3.3.1, 3.3.1.2, 3.5.1, 4.2.2, 9.4.1, 9.4.6) (docs-prv.pcisecuritystandards.org), read on 2026-10-22
  2. PCI SSC FAQ 1280: Can card verification codes be stored for card-on-file or recurring transactions? (pcisecuritystandards.org), read on 2026-10-22
  3. PCI SSC FAQ 1069: Does PCI DSS apply to paper with cardholder data? (pcisecuritystandards.org), read on 2026-10-22
  4. PCI SSC Information Supplement: Protecting Telephone-Based Payment Card Data, v3.0 (November 2018), sections 2.3.1, 5.2.1 and 6.2 (docs-prv.pcisecuritystandards.org), read on 2026-10-22
  5. PCI SSC Glossary (card verification code) (pcisecuritystandards.org), read on 2026-10-22
  6. PCI SSC: SAQ Instructions and Guidelines, PCI DSS v4.0.1 r1 (SAQ A eligibility) (docs-prv.pcisecuritystandards.org), read on 2026-10-22
  7. Visa Core Rules and Visa Product and Service Rules, 18 April 2026 (§5.4.2.5, §5.4.3.1, §5.7.2.4, §5.8.8.2, §5.8.11.1, Dispute Condition 13.7) (usa.visa.com), read on 2026-10-22