Skip to main content
Quick Pay is the direct payment-session path, suited to integrations that want to create a payment session and track its status with a small number of APIs.

When to use Quick Pay

Use Quick Pay when your integration only needs a small number of APIs to create and query a direct payment session. Use UCP Pay when you need product and fulfillment state, and use Browser Pay when the Agent needs to operate a merchant web page.

Payment flow

  1. Create an Agent Payment Session with the payment amount, currency, and checkout context your integration requires.
  2. When user action is required, give the returned next_action to the user or Agent unchanged.
  3. Keep querying the session until it reaches a terminal state.
  4. Treat the actual merchant or payment system result as authoritative before reporting success to the user.

Sequence diagram

Use Create Agent Payment Session to start and Get Agent Payment Session to read the current state. Save the session identifier together with the original payment context; do not create a second session when the result is unknown.

Code examples

MCP

Let the Agent call the Quick Pay tools through MCP. The platform injects the user’s authorization into the MCP connection and hands user confirmation, next_action, and Operation recovery to controlled Agent tools.
Do not give the MCP token or payment credentials to the model. When recovering, reuse the same Operation and the original payment facts; do not create a duplicate payment session.

RESTful API

The server can call the Agent Payment Session API directly, save the session ID and original payment context, and query status using the same session:
If the Agent needs to use the RESTful API, wrap the create and query functions as controlled tools. The server validates user identity, amount, currency, and idempotency; the model must never obtain platformToken.