What Is a Ghost Card? Definition, Use Cases, and How It Differs from Virtual Cards

A ghost card is a commercial credit card number that's tied to a department, cost center, or specific vendor relationship, not to an individual cardholder. There's no plastic in anyone's wallet. The card number lives in your AP system or on file with a supplier, and any authorized purchase against it shows up on a single consolidated bill.

If you've ever set up "the team's travel card" or "the office subscriptions card" and run all the spend through one shared number, you've used a ghost card, even if you didn't call it that. Ghost cards have been a quiet workhorse in corporate finance for decades, and they still fit specific use cases better than newer virtual cards do.

Key Takeaways

• A ghost card is a commercial card number assigned to a department, cost center, or supplier rather than a person. There's no physical card.

• The same card number is reused across many transactions, which centralizes spend and simplifies reconciliation for recurring expenses.

• Ghost cards are sometimes called "lodge cards" (the term used in travel) or "shared cards" (the term used by employees).

• The main risk: a single static number with multiple authorized users is a fraud target. Modern setups pair ghost cards with merchant, dollar, and date-range controls to limit exposure.

• Virtual cards (single-use or short-lived) are usually a better fit for AP vendor payments, while ghost cards still win for repeated low-touch use cases like office subscriptions and team travel.

What Is a Ghost Card?

A ghost card is a commercial card number issued by a card provider that doesn't come with a physical card and isn't tied to one named employee. The same number is reused for every authorized transaction in the use case it's set up for. For example, all travel booked through the corporate travel agency, or all charges from a specific software vendor.

The "ghost" in the name comes from the absence of a physical card. The account exists, the number works, but there's nothing to lose, nothing to mail to a new hire, and nothing to physically present at a register. That's both the appeal (no card distribution to manage) and the risk (one number, multiple hands).

Ghost cards have existed for decades in commercial card programs, especially for travel and entertainment. The newer term you'll see in this space is virtual card. Those are similar in concept (no physical card) but typically structured for single-use or short-lived payments, which makes them safer for AP and one-off vendor invoices.

How does a ghost card work?

A ghost card works the same way a regular commercial card works at the network level, a real Mastercard or Visa account that processes transactions through interchange. What's different is who holds the number and how it's used — instead of being issued to an individual employee, the number is assigned to a department or a specific merchant/vendor relationship.

In practice, the card provider sets up the account, assigns the number, and configures spend controls like merchant category restrictions, daily/monthly limits, and allowed users. Authorized people or systems then use that number for purchases inside the defined scope. Each transaction posts to a single consolidated statement that flows back to AP for reconciliation and payment.

Where the term "ghost card" came from

"Ghost card" originated in commercial card programs as shorthand for an account that exists in the issuer's records but has no physical card associated with it. The term is most common in North America, while in the UK and Europe the same concept is often called a lodge card... usually because the number is "lodged" with a corporate travel agent for booking all employee travel under one account.

Some teams also call them "shared cards" or "departmental cards" informally. They're all variations on the same idea: one card number, many transactions, one consolidated bill.

How Are Ghost Cards Used in Business?

Ghost cards are used in businesses primarily for centralizing spend categories that have many small transactions or many authorized users, where issuing individual cards would create administrative overhead. The use cases cluster around travel, recurring vendor payments, software subscriptions, and shared services.

The common pattern is "lots of transactions, defined scope, low individual transaction size." A ghost card removes the friction of issuing a personal card to everyone who might touch the spend, and it removes the reconciliation pain of chasing receipts from many employees.

Ready to see how Corpay handles these use cases? Request a demo and we'll show you ghost card and virtual card workflows side by side.

The most common ghost card use cases

The most common ghost card use cases fall into four buckets:

• Travel booking. A single account "lodged" with the corporate travel agency that books flights, hotels, and rental cars for all employees. Reconciliation happens against the travel agency's invoice, not individual receipts.

• Recurring vendor payments. A card on file with a specific vendor (a software platform, a cloud provider, a marketing service) for monthly or annual billing.

• Team subscriptions. Internal SaaS subscriptions where multiple teams need access but the company doesn't want to issue individual cards.

• Shared services. Utilities, office supplies, courier accounts, or any recurring vendor relationship where the number stays static and the spend is predictable.

Outside those use cases, individually issued cards (physical or virtual) usually fit better because they give you accountability at the user level.

When a finance team should reach for a ghost card

Finance teams should use a ghost card when the spend has many small recurring transactions, a predictable category, and a low need to attribute individual spending to specific employees. The trade-off is always between centralization (simpler admin) and granular attribution (better accountability and forensic trail).

The right test is basically this: If losing the ability to track "which employee made this transaction" doesn't change your control posture, a ghost card is fine. If you need to know who spent what, individually issued virtual cards generated per employee or per project are a better fit.

What's the Difference Between a Ghost Card and a Virtual Card?

The difference between a ghost card and a virtual card is mostly about how the number is structured and how often it changes. A ghost card uses the same static number across many transactions over a long period. A virtual card typically generates a new number per transaction, per vendor, or per short-lived use, making each instance much harder to reuse if it's compromised.

Most modern AP automation programs lean heavily on virtual cards because the per-transaction issuance pairs cleanly with the invoice-to-payment workflow. Ghost cards persist where the workflow is genuinely "many small charges, one account": travel, recurring services, and team subscriptions.

When a ghost card fits better than a virtual card

A ghost card fits better than a virtual card when the spend pattern involves many transactions over time with the same merchant or category, where generating a new card per transaction would create friction without adding much control. Travel agency accounts are the canonical example. Issuing a new virtual card for every employee flight would slow bookings to a crawl and create reconciliation chaos.

Other places ghost cards still win: long-running vendor relationships where the same card-on-file is used for years (think AWS, Salesforce), and shared internal accounts where multiple teams legitimately need the same spend authority.

When a virtual card fits better than a ghost card

A virtual card fits better than a ghost card for AP vendor payments, especially for one-off invoices or vendors you don't have a long-running card-on-file relationship with. Each invoice gets its own short-lived card number, locked to the vendor, the exact dollar amount, and a tight date window. If the number leaks, only that single payment is exposed.

The B2B shift toward virtual cards has been substantial. According to Juniper Research's Virtual Cards Market Research Report 2025, virtual card transactions reached $5.4T globally in 2025 and are expected to grow 164% by 2030, with 76% of that volume coming from B2B spending. The growth is largely AP-driven. Virtual cards solve the static-number fraud risk that ghost cards always carried.

For more on the AP-side virtual card story, see Corpay's ghost in the cloud piece (which despite the name covers virtual cards in detail).

What Are the Benefits and Risks of Ghost Cards?

Ghost cards offer real efficiency benefits, but they come with security trade-offs that have to be managed deliberately. The benefit side gets the marketing attention. The risk side gets the audit attention.

The main benefits

The main benefits of ghost cards are administrative simplicity, consolidated reporting, and easier onboarding for new employees in shared-spend roles. You don't have to issue a physical card to every traveler or every team member who might touch a shared subscription, and the spend rolls up to one statement instead of many.

Specifically, finance teams use ghost cards to:

• Avoid the cost and delay of issuing physical cards to many employees

• Centralize travel spend into a single account for easier reporting

• Maintain card-on-file relationships with key vendors without rotating numbers

• Simplify expense reconciliation for shared categories (subscriptions, office supplies, courier services)

• Capture rebates on a single high-volume account rather than splitting volume across many cards. The corporate credit card program piece covers rebate mechanics in detail.

The risks and how to manage them

The main risk with ghost cards is that a single static number, used by many people across many transactions, is a higher fraud target than a card tied to one user. If the number is compromised through a vendor data breach, an employee mistake, or an internal leak, every charge against it after that point is at risk until the number is rotated.

You manage that risk with a layered approach. The standard controls:

• Merchant category restrictions so the card only works at approved merchant types

• Per-transaction and daily/monthly spend limits that cap exposure on any single attempt

• Authorized-user lists kept tight and reviewed quarterly

• Real-time transaction monitoring with alerts on unusual patterns

• Regular number rotation for higher-risk use cases (annually at minimum)

• Pairing with virtual cards for any use case where ghost-card persistence doesn't add value

The AFP's 2024 Payments Fraud and Control Survey reported that 80% of organizations experienced payment fraud attempts in the prior year, and card fraud was a meaningful contributor. The ghost card isn't unique in that exposure. It just centralizes it, which can be either a control advantage or a risk concentration depending on how you set it up.

How Does Corpay's Commercial Card Platform Support Ghost Card Use Cases?

Corpay's virtual card platform supports both ghost-card and virtual-card use cases under one program, which is increasingly how mid-market and enterprise finance teams want to operate. You get static card numbers for the long-running vendor relationships and travel programs where ghost cards still make sense, plus single-use virtual cards for AP and one-off payments where you want fraud-resistant per-transaction issuance.

What makes the combined approach work: the same controls (merchant categories, spend limits, real-time monitoring), the same reconciliation pipeline, and the same rebate share-back economics across all card types. You don't have to run a ghost-card program in one tool and a virtual-card program in another. The broader card stack, including corporate cards, what is a charge card, and how finance teams use technology for greater spend control, fits the same way.

Want to see the ghost-card-plus-virtual-card workflow live? Request a demo and we'll walk you through both side by side.

Frequently Asked Questions

What does ghost card mean?

Ghost card means a commercial card account that exists in the issuer's records but has no physical card. The number lives in software, in a vendor's records, or with a corporate travel agency, and it's used for transactions inside a defined scope (a department, a category, or a specific vendor relationship).

Are ghost cards safe?

Ghost cards are reasonably safe when paired with merchant category restrictions, spend limits, authorized-user controls, and real-time monitoring. They are inherently more exposed than single-use virtual cards because the same number is reused over time. Most well-run programs pair ghost cards (for persistent use cases) with virtual cards (for one-off payments) to limit the total risk surface.

How do you get a ghost card for business?

You get a ghost card for business by working with a commercial card issuer to set up an account without a physical card, then configuring the controls (allowed merchants, dollar limits, authorized users). Most major issuers, including bank-issued commercial card programs and platforms like Corpay, support ghost card configurations as part of a broader corporate card program. The piece on supplier payments automation covers how card-on-file relationships fit into the broader AP stack.

What is a lodge card?

A lodge card is the UK and European term for a ghost card used specifically in corporate travel. The card number is "lodged" with a travel agency that books all flights, hotels, and rental cars for the company's employees. Functionally it's the same product as a North American ghost card. The name reflects the travel-agent context.

Is a ghost card the same as a corporate card?

A ghost card is a type of commercial card, but it's distinguished by having no physical card and being assigned to a department or vendor rather than an individual. A traditional corporate card is issued to a specific employee with a name on the plastic. Both run on the same card networks (Mastercard, Visa) and use the same underwriting and rebate mechanics.

Can a ghost card be used for travel?

A ghost card can be used for travel. In fact, travel is the original use case. A "lodged" ghost card sits with the corporate travel agency, and every employee booking through that agency uses the same underlying card. This avoids issuing personal travel cards to occasional travelers and centralizes the spend onto one statement for reconciliation.

How do you reconcile spending on a ghost card?

You reconcile ghost card spending by matching the consolidated statement against the source-of-truth records: the travel agency's bookings, the vendor's invoices, or the subscription provider's billing reports. Because there's no individual employee receipt trail, the reconciliation depends on the merchant or service provider sending clean line-item detail. Modern AP automation can pull this data automatically if the merchant supports e-invoicing or detailed statement transmission.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Commercial Cards

Virtual Card