Recurring Purchases

A recurring purchase reuses one enrollment and one mandate across many charges. The user approves the terms once, and each later charge runs inside those terms instead of prompting the user again.

What the mandate controls

Read the mandate with GET /agentic/mandates/:id and check four things.

Term	What it does
`amount`	Sets the ceiling for a charge. The final quote total has to stay at or below it.
`frequency`	Sets the cadence as `WEEKLY`, `MONTHLY`, or `YEARLY`.
`maxCharges`	Caps how many charges the mandate authorizes in total.
`merchantScope`	Limits where the mandate can be used. A `LISTED` scope names the merchant in the `merchant` block.

Response

{
  "id": "<mandate-id>",
  "status": "ACTIVE",
  "enrollmentId": "<enrollment-id>",
  "frequency": "MONTHLY",
  "maxCharges": 12,
  "merchantScope": "LISTED",
  "merchant": {
    "name": "<merchant-name>",
    "url": "https://example.com",
    "country": "US"
  },
  "amount": {
    "amount": 150,
    "currency": "USD"
  }
}

You can charge only while status reads ACTIVE. Lifecycle and Statuses lists every value.

The charge cycle

Each cycle repeats the purchase phase and reuses only the enrollment and the mandate. The ceiling check is the one point where a cycle can stop, so branch on it before you charge.

Read the mandate

Confirm the status is ACTIVE and that charges remain under maxCharges. A paused or canceled mandate cannot authorize the cycle.

Price the order again

Create a fresh quote for the cycle with POST /agentic/quotes and select a shipping option. Merchant prices move, so never reuse a quote or an old total across cycles. The call sequence matches One-Time Purchases.

Compare the total to the ceiling

Check amountBreakdown.finalAmount against the mandate amount before you charge. Hold the cycle and ask the user for new terms when the total sits above the ceiling.

Charge and confirm

Create the checkout with POST /agentic/checkouts against the same enrollment, then read it with GET /agentic/checkouts/:id to capture orderId and finalAmount for that cycle. Branch on nextAction in the checkout response, and send the user to the approval page whenever it holds a value.

Control the schedule

A mandate stays under your control between cycles.

POST /agentic/mandates/:id/pause stops charges and keeps the approved terms
POST /agentic/mandates/:id/resume continues a paused mandate under the same terms
POST /agentic/mandates/:id/cancel ends the mandate

Resuming needs no further approval from the user, because the terms have not changed. Lifecycle and Statuses covers each operation with a request and a response.

Revoking an enrollment stops charges across every mandate that points at the same stored card. Pause or cancel the mandate instead when the card should stay usable.

Getting Started

Program Configuration

Compliance

Accounts

Cards

Transactions

Spend Policies

Virtual Assets

Statements

Agentic Payments

Rewards

Recurring Purchases

What the mandate controls

The charge cycle

Control the schedule

Next steps

Lifecycle and Statuses

FAQ

​What the mandate controls

​The charge cycle

​Control the schedule

​Next steps

Lifecycle and Statuses

FAQ

What the mandate controls

The charge cycle

Control the schedule

Next steps