Skip to main content
One order intent can pay several times, until the agent spends the amount or the order intent expires. List the user’s order intents to show the limits that they approved, or to find one that covers a new payment, so that you do not ask the user to approve again.

Prerequisites

  • Approved order intent — follow Approve an Order Intent.
  • Crossmint API key — a client-side key with the order-intents.read scope. In staging, all scopes are included by default.
  • User JWT — use the JWT for the user who owns the order intents.

List the User’s Order Intents

Send a GET request. The response is an array with every order intent of the authenticated user:
Each order intent has a status (active, cancelled, or expired), its rails, and its live amount:
available is the amount that the agent can still spend. Each credential takes its amount from it.

Reuse an Order Intent

An order intent covers a new payment when all of these are true:
  • status is active, and expiresAt is in the future.
  • The currency is the currency of the payment.
  • amount.available is at least the payment amount.
  • The order intent has no merchant, or the same merchant as the payment.
Before you use it, check that one of its rails can pay. See Pay for a Checkout with Agent Checkouts, or Get a Card Number with your own checkout. When no order intent covers the payment, create a new one.

Refresh One Order Intent

To read one order intent again, for example after a payment, send GET /api/unstable/order-intents/{orderIntentId}. It returns the same fields as an item of the list. See Get Order Intent.

Next Steps

Pay for a Checkout

Pay with the order intent in an agent checkout

Cancel Card Access

Cancel an order intent that the user no longer wants

List Order Intents

Review the complete response schema