Ghost Cards Explained: How One Shared Card Number Covers Travel, Ad Spend, and Subscriptions

Somewhere in your company, the same corporate card number is saved in a dozen browser autofills, pasted into three ad platforms, and sitting in a former contractor's password manager. Every charge lands on one statement, and nobody can tell you which department spent what. That is the mess ghost cards were invented to clean up — and, set up carelessly, the mess they recreate in a new form.

A ghost card is a corporate card number with no plastic and no named cardholder. Instead of belonging to a person, it belongs to a purpose: one number for travel, one for ad spend, one for the office supply vendor. Used well, it turns a tangled card statement into pre-sorted cost centers. Used badly, it is a shared password with a credit limit. This guide covers both sides: how ghost cards work, the controls that make them safe, and how to reconcile a statement that carries no cardholder's name.

What a ghost card actually is​

A ghost card is a digital-only card number assigned to a department, a vendor, or a spending category rather than to an individual employee. There is no physical card to hand out, lose, or photograph. Every charge made against the number rolls up to a single company statement, usually with its own sub-account or reference so finance can tell the travel number's charges apart from the marketing number's.

You will also hear them called lodge cards or shared cards. "Lodge" is the older term and the more descriptive one: the number is lodged — parked on file — with a specific vendor or travel agency, and authorized people charge against it without ever seeing the full digits. The concept comes from corporate travel, where companies have lodged card numbers with travel management companies for decades so employees could book flights without carrying a company card. Modern spend platforms extended the same idea to ad spend, subscriptions, and department budgets.

The defining features, together, are what make it a ghost card:

• No named cardholder. The account belongs to the company and is identified by purpose, not by person.
• No physical form. The number lives in a vendor's vault, a travel booking tool, or a password manager — never in a wallet.
• Purpose-bound by design. One number, one job. The travel ghost card pays for flights and hotels; it should never successfully buy office furniture.

How ghost cards work in practice​

A typical setup looks like this. Finance asks the card issuer for a new number tied to the company's master account, labels it "Q4 Travel" or "Marketing — Ad Platforms," and sets its controls (more on those below). The number is then lodged where it will be used: with the travel agency, inside the Google Ads and Meta billing settings, or with the handful of people authorized to spend from it.

From there, spending flows without expense reports. An employee books a flight through the company travel tool, and the charge hits the travel ghost card. The ad platforms bill the marketing ghost card every month. Each number produces its own itemized statement or statement section, so reconciliation starts from an already-sorted pile: everything on the travel number is travel, by construction.

That pre-sorting is the whole point. Without ghost cards, the alternatives are passing one corporate card number around the team — no attribution at all — or reimbursing a dozen personal cards through expense reports, which buys attribution at the cost of everyone's time. A ghost card per purpose splits the difference: company money, spent directly, already labeled.

Ghost cards vs. virtual cards vs. purchasing cards​

The terminology overlaps, so it helps to draw the lines:

A virtual card and a ghost card can be the same technology under the hood — both are just numbers. The difference is the policy wrapped around them. A virtual card is typically issued to someone for something and then expires or gets replaced. A ghost card is deliberately long-lived and deliberately shared, which is why its controls and its reconciliation process deserve their own treatment.

Where ghost cards earn their keep​

Corporate travel. This is the original use case and still the strongest. A travel ghost card lodged with your booking tool or agency captures airfare, hotels, and rail in one place, often with traveler names and itinerary references attached to each line. Trip-based accounting becomes possible: every charge carries enough context to post to the right trip and the right general-ledger code.

Ad spend and subscriptions. Marketing teams routinely spread spend across Google, Meta, LinkedIn, design tools, and analytics products. One ghost card number across all of them produces a single statement that is, by definition, the marketing acquisition ledger for the month — no more hunting through five employees' expense reports to total up ad spend.

Department shared spend. Office supplies, software seats, and team meals rarely justify issuing cards to everyone involved. A department ghost card with a monthly cap gives a team purchasing power while keeping the blast radius contained to one number with one budget.

Project and high-turnover spend. Contractors, seasonal staff, and rotating project teams are the worst candidates for named corporate cards and the best candidates for a purpose-bound number. When someone rolls off the project, you revoke their access to the number — or rotate the number — without reissuing anyone else's card.

The controls that make a shared number safe​

A number that several people can spend from is only as safe as its guardrails. Every one of these should be set before the first charge, not after the first surprise:

Merchant category (MCC) restrictions. The card networks assign every merchant a four-digit category code — airlines, hotels, ad services, office supply stores, and so on. Restricting a ghost card to the two or three MCCs its purpose needs means a leaked travel number simply declines at an electronics store or a casino. This is the single highest-value control on a shared number.

Transaction and monthly limits. Cap both the size of any single charge and the total per cycle. A travel card that has never legitimately seen a charge above $2,000 should decline a $9,000 one. Limits turn a compromised number from an open tap into a bounded incident.

A tight authorized-user list. "Shared" should still mean "five named people," not "whoever finds the digits." Keep a written list of who may spend from each number, store the number itself in a password manager rather than email or chat, and treat the list as part of your offboarding checklist.

Real-time alerts and monitoring. A charge notification the moment money moves is worth more than a perfect month-end review. Route alerts to the number's owner so misuse surfaces in minutes, and review the full statement monthly even when nothing looked wrong in real time.

Rotation. A static number shared across people and vendors accumulates exposure over time: every vendor breach, every departing employee, every copied-and-pasted checkout form adds risk. Rotate ghost card numbers on staff changes and on a calendar — annually at minimum for high-traffic numbers — the way you would rotate any shared credential.

Level 3 data: the reconciliation superpower​

Card transactions carry different amounts of detail depending on what the merchant submits. Level 1 is the bare minimum: card number, amount, date. Level 2 adds tax amounts, purchase order numbers, and customer codes. Level 3 adds full line-item detail — item descriptions, quantities, unit prices, product codes, freight, and ship-to postal codes. It is essentially the invoice, traveling with the payment.

For ghost card reconciliation, Level 3 data changes the job completely. Instead of matching a $4,812.40 charge labeled with a cryptic vendor descriptor against a stack of invoices, the statement line itself tells you what was bought, in what quantity, at what unit price. Matching becomes verification rather than detective work. As a bonus, merchants that submit Level 2 and Level 3 data qualify commercial and purchasing cards for lower interchange rates, so the detail literally costs less to process.

Two caveats. First, not every merchant passes Level 3 data — large suppliers, airlines, and hotel chains generally do; small vendors often do not. Second, the detail only helps if your accounting process is built to receive it. When you lodge a ghost card number with a major vendor, ask whether they submit Level 3 data and make sure your card feed or import preserves those fields instead of collapsing each transaction to one line with a memo.

Reconciling a statement with no cardholder's name on it​

Here is the honest difficulty with ghost cards: a traditional card statement tells you who spent the money, and the who is often the fastest route to the why. A ghost card statement tells you only what and where. Reconciliation has to be rebuilt around that fact.

Map each number to its accounts up front. The travel ghost card posts to travel accounts; the marketing ghost card posts to advertising. This sounds obvious, but it only works if the mapping is written down before spending starts and if MCC restrictions actually enforce it. A travel number that also bought software produces the exact unclassified mess you were trying to escape.

Match line items to source documents, not people. With Level 3 data, match quantities and unit prices against purchase orders and invoices. For travel, match each charge to its itinerary reference or traveler name from the booking tool — trip type (domestic, international) often determines the ledger code. Build the habit of attaching the booking confirmation or invoice to the transaction record at import time, while the context is fresh.

Run an exception workflow for orphans. Every cycle will produce charges that match nothing: a fee you have never seen, a descriptor you do not recognize, a duplicate-looking line. Route these to the number's owner with a deadline, not to a shared inbox where they age into write-offs. An orphan older than one cycle should be disputed or accrued, never ignored.

Reconcile on a monthly cadence, per number. Because each ghost card is its own sub-statement, reconcile each one separately and sign off separately. A clean travel number should not wait on a messy marketing number, and a problem in one category should never hold the whole close hostage.

In a plain-text ledger, the natural shape is one liability sub-account per ghost card number, so the statement balance and the ledger balance can be compared directly:

2026-01-01 open Liabilities:Ghost-Card:Travel USD
2026-01-01 open Liabilities:Ghost-Card:Marketing USD
2026-01-01 open Expenses:Travel:Airfare USD
2026-01-01 open Expenses:Marketing:Advertising USD
 
2026-10-12 * "United Airlines" "SFO-JFK R. Alvarez conf KX7Q2P" ^trip-q4-roadshow
  trip-type: "domestic"
  Expenses:Travel:Airfare  486.20 USD
  Liabilities:Ghost-Card:Travel  -486.20 USD
 
2026-10-15 * "Google Ads" "October search campaigns" ^mktg-october
  Expenses:Marketing:Advertising  1,203.55 USD
  Liabilities:Ghost-Card:Marketing  -1,203.55 USD
 
2026-10-31 * "Ghost card statement autopay — October"
  Liabilities:Ghost-Card:Travel  486.20 USD
  Liabilities:Ghost-Card:Marketing  1,203.55 USD
  Assets:Checking  -1,689.75 USD

The tags (^trip-q4-roadshow) and metadata (trip-type) carry the attribution the statement lacks: the link to the itinerary, the campaign, the purchase order. When the November statement arrives, the balance of Liabilities:Ghost-Card:Travel should equal the travel number's statement balance to the cent — that comparison is the reconciliation, and the per-number accounts make it a one-line check instead of a forensic exercise. If your bookkeeping lives in conventional software rather than a text ledger, the same structure applies: one card sub-account per ghost number, mapped once to its expense accounts. The general ledger documentation covers account organization in more depth.

Risks and honest downsides​

Ghost cards are not free safety; they concentrate risk in new places.

A shared number has a shared blast radius. When one person's card is compromised, one person's spending is exposed. When a ghost card number leaks — through a vendor breach, a forwarded email, or a departed employee who kept the digits — every charge on that number is exposed until you rotate it. The mitigations are the controls above, applied consistently, not trust in any single one of them.

Offboarding has a new step. Removing someone from payroll does not remove a card number from their memory or their password manager. Every departure of an authorized user should trigger a decision: rotate the number now, or document why the risk is acceptable. Former employees attempting to reuse a department's ghost card is one of the most commonly reported misuse patterns.

Disputes get harder without a cardholder. "I did not authorize this" is straightforward when one person holds the card. On a shared number, the first question — who made this charge? — may have no clean answer, which slows both internal investigation and the issuer dispute process. Real-time alerts and per-transaction context shrink this window but do not close it.

Acceptance is uneven. Lodged numbers work smoothly with travel agencies, major vendors, and online billing portals. They work poorly anywhere a physical card, a named cardholder, or 3-D Secure verification is expected. Pilot each new vendor before migrating real spend onto the number.

Numbers proliferate. The discipline of "one number, one job" decays into forty numbers with overlapping jobs unless someone owns the inventory. Keep a registry — every ghost card number, its purpose, its owner, its limits, its authorized users — and review it quarterly. Retire numbers whose purpose ended; a dormant number with an active limit is pure risk.

Setting up your first ghost card​

Start with exactly one, on your most painful shared-spend category. Travel and ad spend are the usual candidates because the attribution problem is worst there.

1. Pick the category with the most unattributable charges on last month's statement.
2. Ask your issuer for a lodge or shared number on your master account with MCC restrictions and transaction limits set from day one.
3. Name it, map it, and document it: purpose, owner, authorized users, ledger accounts, and the rotation trigger.
4. Lodge the number with the vendor or booking tool directly. Never send it through email or chat to "make setup easier."
5. Reconcile the first statement end to end — import, match, exceptions, sign-off — before creating a second number. The first cycle calibrates your controls; the second number inherits them.

Pull last month's card statement and highlight every charge you cannot attribute to a person and a purpose in ten seconds. That highlighted list is your first ghost card's job description — and once the number exists, go highlight the list again in thirty days and confirm it shrank.