// Hospitality & property management

The card number your front desk never has to hear.

Guests, owners, and corporate clients send their cards through a secure Card Vault link. Your team charges a vaulted card when it's time, and nobody in your operation ever sees, types, or stores a card number again.

Free plan · vault up to 5 cards · no sales call required

A hotel front desk agent takes a card number over the phone and writes it on a paper form
The industry's most common card vault — a notepad.
// Sound familiar?

Card-on-file, the way it usually happens

Every one of these is a PCI finding, a lost payment, or a breach waiting for a date.

01

Cards read over the phone

A guest recites their card to the front desk. It gets typed into a terminal, and too often written down first — on a booking sheet, a sticky note, a notebook that lives under the counter.

02

Card numbers sitting in the inbox

Third-party bookings and corporate reservations arrive by email with full card details. Now your mail server is a cardholder data environment.

03

The card that's dead by billing time

A number scribbled down at check-in is expired by the time the incidental or owner invoice runs — and nobody notices until it declines.

04

A PCI questionnaire nobody can honestly finish

Handwritten PANs and emailed card numbers put you in the deepest end of PCI scope — the 250+ question SAQ D — with evidence you'd rather not show an assessor.

// The Card Vault workflow

Send a link. Get a card. Charge it when it's time.

No developer required — the whole workflow runs from the Card Vault console your team signs into.

1

Request

Send a secure card request by email or SMS from the console. The guest or owner opens a Card Vault-hosted page — your systems are never in the middle.

2

Vault

The card goes straight into the vault, encrypted. Your staff see the last four digits and expiry — never the number.

3

Charge

Charge the vaulted card from the virtual terminal — deposits, no-show fees, damages, owner billing — on your schedule.

Card Vault hosted capture form - the secure page a guest uses to submit their card
What your guest sees — a secure Card Vault page, not your website
Card Vault virtual terminal charging a vaulted card
What your team sees — charge the vaulted card, never the number
// Built for multi-property operations

One vault, every property

Segments per property

Each hotel, building, or portfolio gets its own vault segment under one account.

Per-segment staff access

Front desk at Property A never sees Property B's cards. Access follows the org chart.

Expiry warnings

Webhooks and console views flag cards expiring before the next billing run.

Every action logged

Who requested, who charged, who viewed — an audit trail your assessor will like.

Out of PCI's deep end

With card data out of your phones, inboxes, and files, your PCI scope shrinks dramatically.

Your processor stays yours

Card Vault charges through the payment gateway you already have — or any you switch to.

// Pricing

Sized for operations, not enterprises

Start free with 5 cards. A single property typically runs on Basic Vault at $79.99/mo (up to 400 stored cards); groups add a segment per property. Full pricing →

// Get started

Retire the notebook under the counter.

Sign up in minutes. Send your first card request today — free.

Want the technical detail instead? Platform overview · Docs