Skip to main content
Use the generated endpoint pages for the complete query parameters and response schemas.

List orders

Filter and paginate organization-scoped orders.

Get an order

Inspect one order and its available payment-channel identifiers.

​
List and detail behavior

The list operation supports payment-status checks and operational views. Its status filter matches the human-facing displayStatus, while the response also preserves the canonical status. The detail operation can expose additional payment-channel, payment, session, subscription, and account identifiers when they exist. Use merchantReference as your correlation identifier. Treat merchantMetadata, buyer-supplied notes, and URL query parameters as untrusted input; never use them alone to authorize access or set a price.

​
Fulfillment

Fulfill from a verified paid state or a verified order.paid webhook. Make delivery idempotent by the Anyway order ID. Anyway protects paid orders from duplicate payment events and status regression, but your fulfillment handler must also tolerate retries.
A successful API response does not make buyer-controlled metadata trustworthy. Authorization and pricing decisions must come from server-controlled records.