Payments

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 that are already available to the Ramp user who connected it.

Start by connecting Ramp. Then choose the purchase method that fits it.

Optional: Create an agent identity

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.

Ways to purchase

Agent Card checkout

Use an Agent Card 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 with the required memo, receipt, and accounting details.

Stripe MPP purchase

Use Stripe's Machine Payments Protocol (MPP) when a merchant supports a compatible machine-payment challenge or flow. The agent acts on behalf of the connected Ramp user; a standalone agent identity is optional. Existing access and fund spend controls still apply.

Before requesting credentials through Ramp MCP or CLI, the agent asks the customer to confirm the final merchant, all-in amount and currency, purpose, and selected authorized fund. Ramp evaluates that fund and the compatible challenge, then returns a credential for the merchant request. The agent submits the same challenged request and verifies merchant acceptance plus the Ramp payment record.

MPP is for a machine-payment request, not browser Agent Card checkout. It also does not use the separately funded x402 wallet. The MPP purchase skill will be linked here once it is published in the public catalog.

x402 purchase

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.

Purchase confirmation and records

Before purchasing, the agent confirms the merchant, total, and the 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 public skill contains the method-specific confirmation and completion steps.