> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# Cards overview

> Understand how single-use virtual cards and multi-use ghost cards work for vendor payouts

A virtual card is a card number Payabli issues to a vendor. The vendor uses it to receive a payout as a card payment instead of an ACH transfer or a mailed check. Virtual card payouts earn interchange, which can turn a merchant's accounts payable into a revenue stream. For how that revenue is shared, see [Payables overview](/guides/pay-out-payables-overview).

Payabli supports two types of virtual cards for Pay Out. They differ in how many times the vendor can use the card and how the card is created.

## Single-use virtual cards

A single-use virtual card is tied to a specific payout and can be used only once, for that payment. You create it by passing `vcard` as the payment method when you [authorize a payout](/guides/pay-out-developer-payouts-manage), or a vendor can select a virtual card as the payment method through a vendor link. Single-use virtual cards suit one-off or per-invoice payments where each card matches a single amount.

## Ghost cards

A ghost card is a multi-use virtual card for paying a specific vendor over time, rather than for a single payout. Ghost cards suit recurring or discretionary vendor spend, with configurable spending limits, usage caps, and merchant restrictions. Only one ghost card can exist per vendor per paypoint.

## Choose a card type

Use a single-use virtual card when a payment maps to a specific payout or invoice and shouldn't be reused. Use a ghost card when a vendor needs an ongoing card for repeated or discretionary spend within limits you set.

|                  | Single-use virtual card                                        | Ghost card                              |
| ---------------- | -------------------------------------------------------------- | --------------------------------------- |
| Uses             | Once, for one payout                                           | Multiple, up to configurable limits     |
| Tied to a payout | Yes                                                            | No                                      |
| Created by       | Authorizing a payout with the `vcard` method, or a vendor link | A dedicated create call                 |
| Best for         | One-off or per-invoice payments                                | Recurring or discretionary vendor spend |

## Related resources

See these related resources to help you get the most out of Payabli.

#### Related topics

* **[Manage virtual cards with the API](/guides/pay-out-developer-virtual-cards-manage)** - Retrieve, renew, send, and cancel single-use virtual cards with the API
* **[Manage ghost cards with the API](/guides/pay-out-developer-ghost-cards-manage)** - Create and manage multi-use ghost cards with the API
* **[Understanding payables](/guides/pay-out-payables-overview)** - How virtual card payouts earn interchange and share revenue