Skip to main content
Agentic Payments lets an AI agent complete a purchase for a user without handling the card number of that user. The user stores a card once. Your agent then searches merchant catalogs and prices an order. It opens a checkout against the stored card, and the user approves the charge on a page hosted by Reap. Reap completes the purchase with the merchant and returns the order reference.

​
What Reap handles

You do not need to build any of the following.
  • Card storage, so the card number never reaches your agent or your servers
  • Merchant catalog search, product detail lookup, and live pricing
  • The hosted page where the user enters a new card
  • The hosted page where the user approves each charge
  • Checkout with the merchant, including the order reference that comes back

​
What you build

  • The agent logic that decides what to buy
  • The call sequence described in this section

​
Core resources

Five resources carry the whole flow. How It Works explains each one.
  • An enrollment stores a card. POST /agentic/enrollments returns the enrollment ID, which is the payment handle for every later purchase.
  • A mandate records the charge terms the user approved for one enrollment. Read it with GET /agentic/mandates/:id.
  • Product search finds a product in merchant catalogs and resolves it to a purchasable variant. Start with POST /agentic/products/search.
  • A quote prices an order with the merchant and expires after a short window. Create it with POST /agentic/quotes.
  • A checkout charges the enrollment and completes the order with the merchant. Create it with POST /agentic/checkouts.

​
Use cases

Shopping agent

The user asks the agent to buy Sony WH-1000XM5 headphones for about USD 130. The agent finds them at audiohub.com and quotes USD 138.42 including shipping and tax. The user opens the approval link, checks the order, and pays with their card. The agent reports order 12345 with Friday delivery.

​
Next steps

How It Works

The actors, the resources, and the two phases of a purchase.

Setup

Store a card and confirm it is ready to charge.

One-Time Purchases

Run a single purchase from search to a confirmed order.

Recurring Purchases

Charge the same card on a schedule under approved terms.
Lifecycle and Statuses covers every status value and the operations that change it. The FAQ answers the questions that come up most during an integration.