title: Agentic Payments
source_url: /developer-api/v1/agent-payments
summary: Connect Ramp as the current user, then let your agent purchase on your behalf. No separate agent identity is required. The agent can use the cards, funds, and permissions already available to the Ramp user who connected it.

content:
Connect Ramp as the current user, then let your agent purchase on your behalf. No separate agent identity is required. The agent can use the cards, funds, and permissions already available to the Ramp user who connected it.

An agent purchase flow that uses Agent Cards, Stripe MPP, or x402 and completes the associated Ramp record.

Choose one of these recommended ways to connect your agent to Ramp:
Use the Ramp connector in a supported agent client, such as ChatGPT or Claude. See Ramp MCP for supported clients.
Connect directly to Ramp MCP when your agent supports MCP. Custom MCP clients and third-party gateways may need Ramp approval before they can connect.
Use Ramp CLI when your agent has terminal access.

Use the Ramp connector in a supported agent client, such as ChatGPT or Claude. See Ramp MCP for supported clients.

Connect directly to Ramp MCP when your agent supports MCP. Custom MCP clients and third-party gateways may need Ramp approval before they can connect.

Use Ramp CLI when your agent has terminal access.

Each path acts with the signed-in user's existing Ramp permissions.

Agent Cards and Stripe MPP use eligible Ramp funds available to that user. x402 uses a separately funded Ramp x402 wallet.

Most agents can purchase on behalf of the connected Ramp user without a standalone identity. If your business needs a separately managed identity for a shared or background workflow, see Optional: Create an agent identity. Standalone agent identities are in limited early access.

If a standalone agent will purchase, assign its role the relevant Payments capabilities before it can make a purchase. Add the agent to one or more funds and configure the desired limits.

Ways to purchase

Use Agent Cards when the agent needs card credentials for a browser checkout. The agent selects from the funds available to the connected user and follows the fund's spend limit, merchant rules, approval policies, and accounting defaults.

Use the Agent Card purchase skill to confirm eligibility, request a checkout credential, complete the purchase, and finish the Ramp transaction record.

Use Stripe MPP when the merchant supports a machine-to-machine purchase flow. MPP uses the connected user's eligible Ramp funding and the controls that apply to that purchase. The skill confirms the purchase outcome and records the completed purchase in Ramp.

Use the MPP purchase skill.

Use x402 when a seller returns a compatible 402 Payment Required challenge. x402 purchases draw from a separately funded x402 wallet, rather than a user's card or fund. Its wallet balance and x402-specific setup apply; do not assume that card or fund controls apply identically to this method. If the wallet is not ready, set up and fund the x402 wallet first.

Use the x402 payment skill for an already funded wallet to send the payment and confirm the seller accepted it.

Before purchasing, the agent confirms the merchant, total, and Ramp funding source available to the connected user. Afterward, it confirms that the merchant accepted payment and completes any required Ramp record, such as a receipt, memo, or accounting fields. Each purchase skill includes the method-specific confirmation and completion steps.

Virtual Cards - choose a browser or backend card-detail delivery flow.

Ramp MCP - connect an agent to Ramp.

Ramp CLI - connect and operate Ramp from the command line.