The card built for agent checkout

One card.
Every agent task.
Always in your control.

Payrail Card gives AI agents a safe way to complete real checkout—with exact approvals, protected card details, and a verified result for every operation.

Open Payrail Agent → Explore the system →

Private beta · Card provider integration in selection

PAYRAIL CARDAGENT READY
payrail

••••  ••••  ••••  1842

CARDHOLDERPAYRAIL AGENTVALID THRU09/30
APPROVED SCOPEOne checkout · amount boundACTIVE
CARD DATAProtected from model context

Payrail-branded concept · final issuing configuration depends on the selected provider.

01One Payrail Card
02Per-payment approval
03Protected checkout fill
04Verifiable outcomes

A payment instrument agents can use

Cards are the interface.
Policy is the control plane.

Use one Payrail Card across compatible browser checkouts. The agent can prepare and execute the task, while Payrail limits what the card may do for that exact operation.

Card controlsOPERATION / AG-1842
MerchantBound to current checkout✓
AmountExact total + allowed tolerance✓
LifetimeShort-lived operation window✓
Card dataProtected browser handoff✓
OutcomeReconciled before retry✓
Authority stays outside the model

One controlled sequence

From task to paid.

Each transition has one job. A failure stops at its boundary instead of becoming ambiguous spend.

01

The agent prepares the payment

Merchant, total, purpose, and expiry become one bounded operation.

02

You approve the exact boundary

Approval applies to this checkout—not to unlimited future spend.

03

Payrail Card completes checkout

Protected card data reaches the intended fields without appearing in model context.

04

The result is reconciled

The agent verifies the outcome before continuing, retrying, or asking for help.

Use the right surface

One card system.
Three ways in.

Start in the browser, use the compact mini app, or connect an agent directly through MCP.

WEB / 01

Agent workspace

Review approvals, card state, and payment operations in one browser workspace.

Open the app →
EMBEDDED / 02

Mini app

A compact card approval and operation surface for supported embedded environments.

Open mini app →
MCP / 03

Agent tools

Connect a compatible agent while keeping card policy and payment authority at the boundary.

Read the docs →

Built for agent runtimes

A remote tool boundary, not a card number in the prompt.

Point a compatible MCP client at Payrail. The agent gets structured tools; card secrets and final authority stay outside the conversation.

Set up Payrail Agent from https://agent.payrail.one/skill.md Developer documentation →
mcp.jsonREMOTE
{
  "mcpServers": {
    "payrail-agent": {
      "url": "https://mcp.payrail.one/mcp"
    }
  }
}
BOUNDARYAgent tools connectedCARD POLICY ACTIVE

Designed around least authority

The model never becomes the card vault.

Payrail separates what an agent may propose from what a card may execute. Approvals are specific, card details stay protected, and uncertain outcomes must be reconciled before retry.

  • 01 Exact-operation approvals
  • 02 Short-lived protected envelopes
  • 03 No raw card data in model context
  • 04 Idempotent, auditable operations

The card for agentic commerce

Give your agent a way to pay.

Start with the Payrail Agent workspace, or connect your own compatible agent through MCP.

Open Payrail Agent → security@payrail.one