Product · Virtual card

A virtual card per agent, bound by rules.

Give each agent its own card instead of sharing a corporate one. Decide which merchant categories, merchants, countries and channels it can use, and how much per transaction, hour and day.

AgentWallet is invite-only. Request access and we will follow up.

In short

A virtual card for AI agents is a card issued to one agent with authorization rules attached. AgentWallet evaluates each authorization against the card policy (MCC, merchant, geography, channel, AVS, velocity) and records the decision, so you can see exactly why a charge was approved or declined.

How it works

From issue to authorization.

  1. Provision the card

    Attach a card resource to an agent from the dashboard or API.

  2. Load it

    Reload from the agent balance; load history is kept per card.

  3. Write the policy

    Start from a safe default and add allow or block lists and velocity caps.

  4. Agent pays

    At checkout, the authorization is evaluated against the policy in real time.

  5. Review decisions

    Every approve or decline is listed with its reason.

Capabilities

Card controls you can set

From the published card controls schema.

MCC

Category allow or block

Up to 500 merchant category codes per list.

Merchant

Merchant allow or block

Match by merchant name or acceptor ID, up to 500 entries.

Geography

Country rules

Allow or block by ISO country code.

Channels

Channel toggles

Ecommerce, point of sale, ATM, cashback and cross-border on or off.

Security

AVS match

Require an address verification match.

Velocity

Spend caps

Per transaction, per hour, per day and per merchant per day, plus a default decision.

Use cases

How teams use agent cards

SaaS purchasing

Allow software and data-processing MCCs only, cap at a monthly plan price, block ATM and cashback.

Travel booking

Allow airline and lodging categories in the trip countries, decline everything else by default.

Ad and cloud spend

Allow two named merchants with a per-merchant daily cap.

Prototype agents

Tiny per-transaction cap and ecommerce only while you test.

For developers

Policy, decisions and loads over the API.

The same endpoints power the dashboard card screen.

  • GET/PUT /api/agents/:id/cards/:resourceId/policy
  • GET /api/agents/:id/cards/:resourceId/decisions (paginated)
  • POST /api/agents/:id/cards/:resourceId/reload and GET .../loads
  • Draft a policy in plain English with POST /api/setup/card-policy-chat
# Why was that charge declined?
GET /api/agents/$AGENT_ID/cards/$CARD_ID/decisions?limit=20

# Policy shape (excerpt)
{
  "geography": { "mode": "allow", "countries": ["US","CA"] },
  "security":  { "requireAvsMatch": true },
  "velocity":  { "perHour": 150, "perMerchantPerDay": 300 }
}
Security & controls

Separate cards, separate risk.

Per-agent isolation

Each card belongs to one agent; replacing one does not affect others.

Safe defaults

New policies start from a conservative default configuration.

Vaulted card data

Card material is tokenised through VGS and stored sealed.

Automatic repair

Rejected policy fields are identified and suggested corrections are logged for review.

FAQ

Questions developers ask

What is a virtual card for AI agents?

A card number issued to a single agent, with rules that decide which authorizations are approved.

Which card network is used?

The network depends on the issuing program configured for your account. We confirm it during onboarding.

Can I restrict a card to one merchant?

Yes. Use a merchant allow list with a default decision of DECLINE.

What happens when a charge breaks a rule?

It is declined at authorization and appears in the decision log with the rule that caused it.

Who can use AgentWallet today?

Access is invite-only while we onboard teams. Request access from any page; sign-up is enabled per email or domain once you are approved.

Do you guarantee availability in my country or a specific settlement time?

No. Supported rails, currencies and timing depend on the underlying banking, card and payout partners for your account. We confirm what is available for your account during onboarding rather than promising it upfront.

Issue your first agent card.

Request access to provision cards and write policies for your agents.