Skip to main content
Agentic Payments lets an end user hand a purchase to an AI agent. The user asks for an item in chat. The agent finds it, prices it, and opens the checkout. The user approves the payment on a Reap-hosted page, and no card number ever passes through your application or the agent.
Agentic Payments is not generally available. Product search, quotes, and checkouts are live in the sandbox for enabled projects and appear in the API Reference. Card enrollment, mandates, webhooks, and order verification are on the roadmap. Their reference pages publish when they ship.

Three parties, one flow

The end user

Makes the request in your app or any assistant experience you provide, approves the payment on the hosted page, and remains in control

You

Integrate the agentic endpoints into your application and give the agent product search, quoting, and checkout capabilities

Reap

Executes the real merchant checkout behind the API: live pricing, the hosted approval page, and payment without exposing card credentials

What works today

The purchase surface runs from product discovery to a completed order:
Every purchase requires the user’s approval on the hosted page. The user provides or selects the card there, so the card number never reaches your application or the agent.

Where it is going

The roadmap replaces the per-purchase card step with a one-time setup and standing permissions:
  • Card enrollment that vaults the card once and pays every later purchase with single-use credentials
  • Passkey-approved mandates that cap what the agent can spend at a merchant
  • Standing mandates that cover recurring purchases with one approval
  • Webhook events for the enrollment, mandate, and checkout lifecycle
  • Order verification that matches each order to the card authorization on Reap’s rails

Next steps

How Agentic Payments work

Follow a purchase from product search to the completed order

Set up for purchases

What your project and your customers need before the first purchase