Reloadable Virtual Cards for AI Agents, Explained

Tokenized by default

A virtual card's PAN and CVV never sit in the open. They are tokenized through a VGS vault, and the real values are detokenized just-in-time only at the moment of payment: a checkout call, a browser fill, or an explicit reveal. This keeps sensitive card data out of application logs and out of the agent's reach during normal operation.

Controls enforced at the issuer

The important guarantee is where the controls live. Merchant category, per-merchant, and amount rules are enforced at the issuer, so even if something downstream misbehaves, a disallowed charge is declined at the network rather than merely discouraged in software.

• Merchant category rules — restrict where a card can be used.
• Per-merchant rules — allow or deny specific merchants.
• Amount rules — cap what a single charge can be.

Reloadable, and its own bucket

Cards are reloadable, and a card purchase draws from that card's own bank-held balance. That balance is independent from the wallet funds used for payout rails, which keeps card spending and payout spending cleanly separated.