Commerce plane

Visa Intelligent Commerce

Give a verified agent a tokenized Visa credential it can spend without ever holding the card number, then let AxioRank check the mandate before it reaches checkout. Capped, merchant-bound, time-boxed, agent-bound, and funded by a token, not a PAN.

Available in beta. Verified at network authorization time.

commercebeta
payment passkey
···· ···· ···· 1111
agent agent-123not PAN
spend-control mandate
  • capped≤ 200 USD
  • merchantAcme Store
  • expiry2026-12-01
  • agent-boundagent-123
  • fundingnetwork token · not PAN
Visa Intelligent Commerceoutbound · preflight
0
Spend-control terms enforced
0
Raw PAN or token bytes stored
outbound
Governed before checkout
posture
Verification finalized at network time

What it is

Visa's payment rail for agents.

Visa Intelligent Commerce lets a verified agent complete a purchase on the buyer's behalf. Instead of handing the agent a card number, the buyer issues a tokenized Visa credential, a payment passkey or network token, scoped by a spend-control mandate. The agent transacts within that mandate and the real card details never leave Visa.

That mandate is exactly what AxioRank reads. On the outbound path, before the agent reaches a merchant, the gateway confirms the spend is capped, bound to a merchant, time-boxed, bound to the spending agent, and funded by a token rather than a raw card number.

Because the credential is not a signed object, the final agent-to-consumer-to-network binding is asserted at Visa network authorization time. AxioRank reports the mandate posture and never claims a signature it cannot check.

Two sides of Visa's agent program

Visa Intelligent Commerce is the payment credential shown on this page. The Visa Trusted Agent Protocol is the identity and recognition side, an RFC 9421 signature verified at request time. AxioRank governs both, through separate adapters, so a payment credential is never mistaken for an identity proof.

What AxioRank checks

Five terms on every mandate.

A payment credential is only as safe as the mandate around it. AxioRank checks all five terms and raises a named warning when one is missing. A raw card number in the payload is the headline failure.

Capped spend

A maximum amount and currency the agent may not exceed. An uncapped mandate raises vic-uncapped.

Merchant scope

Bound to a specific merchant, so the credential cannot be replayed elsewhere. No binding raises vic-unbound-merchant.

Expiry

A hard expiry timestamp. A mandate that never ends raises vic-no-expiry.

Agent binding

Tied to the agent that is allowed to spend. A missing agent id raises vic-no-agent-binding.

Token, not PAN

Funded by a Visa network token or payment passkey. A raw card number raises vic-raw-pan, the headline leak.

The credential

What the agent presents, and what we keep.

The agent presents a Visa Intelligent Commerce credential. AxioRank resolves it into a normalized card that carries the mandate terms and nothing sensitive. The token reference, raw PAN, and cryptogram are dropped on the way in.

the agent presents
{
  "visaIntelligentCommerce": {
    "credentialType": "payment_passkey",
    "paymentToken": {
      "tokenReference": "VTS-4444-1111",
      "type": "network_token"
    },
    "agentId": "agent-123",
    "merchant": { "id": "merch-42", "name": "Acme Store" },
    "spendControls": {
      "maxAmount": { "value": 200, "currency": "USD" },
      "expiresAt": "2026-12-01T00:00:00Z"
    }
  }
}
what AxioRank keeps
{
  "protocol": "visa-intelligent-commerce",
  "identity": {
    "provider": "Visa Intelligent Commerce",
    "name": "merch-42",
    "signed": false
  },
  "capabilities": [
    {
      "name": "agentic payment (≤ 200 USD)",
      "description": "bound to merchant merch-42"
    }
  ],
  "auth": {
    "schemes": [
      { "type": "payment", "detail": "visa-intelligent-commerce · payment_passkey" }
    ]
  },
  "warnings": []
}

Nothing sensitive is copied

The token reference (VTS-4444-1111), the raw PAN, and the cryptogram never enter the resolved credential. Only the funding type and the mandate terms are kept, so the audit log can prove what was allowed without ever holding a payment secret.

How it runs

From credential to decision.

Visa Intelligent Commerce runs on the outbound path, the moment before an agent pays. Here is the sequence AxioRank governs.

  1. 01

    The agent obtains a VIC credential

    A verified agent is issued a tokenized Visa credential (a payment passkey or VTS network token) scoped by a spend-control mandate.

  2. 02

    AxioRank preflights the mandate

    Before the agent reaches checkout, the gateway inspects the spend-control envelope on the outbound path: capped, merchant-bound, time-boxed, agent-bound, and funded by a token rather than a raw PAN.

  3. 03

    The capability is scored

    The payment capability runs through the risk engine, surfacing a supply_chain.fund_movement signal so a payment is never a silent action.

  4. 04

    Policy returns a decision

    Your policy resolves the call to allow, hold, or deny, with the mandate terms and any vic-* warnings on the record.

  5. 05

    The network finalizes the binding

    The agent-to-consumer-to-network binding is asserted at Visa network authorization time, so AxioRank reports posture rather than a signature verdict.

Why it is still beta

The mandate posture is checked before checkout, but the binding between the agent, the buyer, and the network is finalized at Visa network authorization time. Until that final step is machine-verifiable inline, AxioRank reports posture rather than a cryptographic verdict, the same model as Mastercard Agent Pay.

How AxioRank handles it

Read the specification.

Visa Intelligent Commerce sits in the commerce plane of the agent-interop stack. Read the source, or see how it maps into the wider coverage matrix.

Govern every agent payment.

AxioRank checks the mandate on every agentic purchase, from Visa Intelligent Commerce to AP2 and Lightning, through one engine. See the full coverage matrix, machine-readable.