Agent cards

Limits & restrictions

Merchant categories, transaction types, and scopes for Agent Cards.

Agent Card issuance is policy-controlled at the business level. Use it for constrained, one-time purchases where a fresh credential can be generated at checkout time.

Blocked merchant categories

Agent purchases can't run against these Merchant Category Codes (MCCs):

MCCCategory
4816Computer Network / Information Services
5122Drugs, Drug Proprietors and Druggists Sundries
5816Digital Goods: Games
5912Drug Stores and Pharmacies
5966Direct Marketing – Outbound Telemarketing
5967Direct Marketing – Inbound Telemarketing
5968Direct Marketing – Continuity / Subscription
5993Cigar Stores and Stands
6012Member Financial Institution – Merchandise and Services
6051Quasi Cash – Merchant
6211Securities – Brokers and Dealers
7273Dating Services
7995Betting, Lottery, Casino, Off-Track Betting, Wagers

Unsupported transaction types

These flows are not supported today:

  • 3D Secure (3DS). Affects online transactions in the EEA, UK, India, Japan, Australia, and a few others.
  • Merchant-initiated transactions (MIT) / card on file. Affects subscriptions, recurring billing, and metered AI spend.

Required scopes

Agent Card endpoints require the cards:read_agentic scope, and writes need spend_limits:write. If you authenticated without them, ask a Ramp admin to grant access. On the CLI, run ramp update first — older versions surface less-helpful scope errors.

Receipt handling

MCP connections do not currently support passing receipt images or PDFs from chat attachments into Ramp MCP tools. If a purchase workflow requires receipts, handle that step through the CLI, the Ramp dashboard, or another supported upload path.

If a restriction blocks a real workflow, reach out through Ramp support or your Developer API support path.