Skip to main content
POST
Error

Authorizations

Authorization
string
header
required

The control surface credential. Send Authorization: Bearer <token>.

Two kinds of token are accepted and they are told apart by shape, not by a separate header. A token beginning pbk_ or puk_ is an org scoped API key, whose public half and secret half are generated together and of which only a hash of the secret is ever stored; anything else is treated as an OAuth 2.1 access token and verified against the authorization server's keys.

Both resolve to the same context: an org, a principal and a set of scopes. Nothing downstream branches on which channel you used, with one deliberate exception, key management, which requires a signed-in person so that a key can never mint another key.

Scopes are enforced when MCP tools are REGISTERED rather than when they are called, so a tool your credential cannot use is absent from tools/list rather than refused mid gesture.

Path Parameters

orderId
string
required

The order id POST /v1/checkout-sessions returned.

Response

What the check found.

What one return from Checkout found.

orderId
string
required

The checkout's order id, as returned by POST /v1/checkout-sessions.

outcome
enum<string>
required

recorded: payment is on file and delivery has started. pending: Stripe has not completed this checkout yet. needs_staff: the payment could not be matched automatically; staff need to review this order. unavailable: this deployment cannot check now.

Available options:
recorded,
pending,
needs_staff,
unavailable