Valta Docs

Virtual Cards

Coming 2027. Requires banking partnership.

What are virtual cards?

Each agent can be issued a virtual Visa or Mastercard backed by its Valta USDC wallet. Agents can spend at merchants that do not support crypto or x402 — SaaS subscriptions, API credits, vendor payments.

The card is a payment rail. All spending still passes through the Valta policy engine.

How spend limits work

The card limit equals min(walletBalance, maxPerTransaction). If a purchase would exceed the wallet balance or violate the maxPerTransaction policy, the card is declined before the merchant processes it.

requireApprovalAbove still applies: the card transaction is held and the merchant sees a decline until you approve it via the dashboard or API.

Use cases

  • SaaS subscriptions billed monthly
  • API credits that require card payment
  • Vendor payments through Stripe or PayPal
  • Any merchant that does not accept USDC directly

Audit trail

Every card transaction is logged as a card_payment entry in the agent's audit trail. Standard hash-chain integrity applies — nothing is deleted or modified.

Freeze behaviour

Freezing an agent via valta.agents.freeze(agentId) immediately disables all card activity. Any pending authorisations are declined.