Guides

Payments

Give an agent a Ramp identity, controlled spending power, and a complete purchase record.

Standalone agents are in limited early access. Reach out to the team to get started.

Use business credentials to create roles, agents, and funds. Switch to the agent's credentials only after connecting its runtime; those credentials are what identify the agent when it requests payment credentials and completes the purchase record.

Python examples use the official Ramp SDK. Preview businesses receive a supported version that includes the provisioning resources shown below.

Optional: Create a role

Use one of Ramp's default agent roles: Purchasing, Bill approvals, Data analysis, Expense Completion, or Full Access. Create a custom role only when none of the defaults matches the agent's job.

The API and SDK accept custom roles only; built-in role IDs are not available through those surfaces. The business integration needs users:read and users:write, the person authorizing it must be a role admin, and custom roles must be enabled for the business.

Open Company → Agents, select New agent, and enter the agent's name. On the Role step, choose Purchasing agent, Bill approvals, Data analysis, or Expense completion. Ramp creates or reuses the matching role as part of setup.

1. Create an agent

Create a company-owned identity for the software.

The business integration needs agents:write, the person authorizing it must be a role admin, and standalone agents must be enabled for the business. When supplied, the owner must be an active human with Ramp access in the same business.

Open Company → Agents and select New agent. Enter the agent's name, continue to Role, and choose the role that matches its job. The UI stages the agent until you finish the Wallet step.

2. Assign a fund

Give the agent a budget, merchant rules, approvals, and accounting defaults.

The SDK, API, and CLI examples below show every control supported for a standalone fund. Amounts in fund controls use the currency's smallest unit—for example, 10000 means $100.00 USD. Configure approval chains in Ramp.

On the Wallet step, search for an existing fund and select Add. You can preview its limits, eligibility, policies, and recent activity before assigning it.

To make a new fund, select Create funds and set its name, spend limit, cadence, optional per-transaction limit, and merchant or category rules. The new fund is selected automatically.

Select Create agent when the wallet is ready. Ramp creates the agent, assigns the selected funds, and opens the Credential step. Save the Client ID and show-once Client secret in a secret manager.

3. Connect a runtime

Store the agent's credentials in the system that will operate it.

Add Ramp through the hosted agent's secure connection or secret-storage flow. Store the Client ID and Client secret as credentials, not in the agent's instructions.

Hosted standalone-agent connections are part of the limited preview.

4. Generate card credentials

Request a fresh credential after the fund, merchant, amount, and purpose are approved.

The agent integration needs cards:read_agentic for fund discovery and credential generation.

Ask the connected agent to use a specific fund for a named merchant and maximum amount. Have it confirm the fund and final total before checkout.

The agent should send the credential directly to checkout, not display the PAN or CVV in chat.

The credential is limited to the merchant and requested amount. It expires after the first authorization or 12 hours, whichever comes first.

Agent Card amounts use decimal strings: 100.00 means $100.00 USD. Fund limits above use the currency's smallest unit, where 10000 means $100.00 USD.

5. Complete the purchase record

After the charge posts, add the receipt, memo, and required accounting fields.

Credential generation does not return the posted transaction ID. Find the matching transaction after it posts. If Ramp requires accounting fields, list the available categories and options before editing.

The agent integration needs transactions:read, transactions:write, accounting:read, and receipts:write to finish this step. The examples treat the memo and accounting choices as agent-selected. If the user supplied either value directly, include its field name in user_submitted_fields instead.

Open the transaction in Ramp. Upload the receipt, add a specific memo, confirm the fund, and complete any required accounting or tracking fields.

Finish when Ramp shows no missing items.

More payment methods

ACH, checks, wires, and crypto-native payment methods are in private preview.

Talk to the team to enable the standalone-agent payment flow for your business.