A valid request URL is required to generate request examples{
"id": "<string>",
"sourceId": "<string>",
"micros": "<string>",
"currency": "<string>",
"status": "pending",
"customerMessage": "<string>",
"updatedAt": "2023-11-07T05:31:56Z",
"caseId": "<string>"
}{
"error": {
"code": "payload_too_large",
"message": "<string>"
}
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}/v1/minute/refunds
Retired on 2026-10-09: unused balance can no longer be refunded online. Every request answers 503 minute_unavailable with retryable: false and a message giving the support address. No refund, reservation or case is created, nothing is sent to the payment provider, and the balance stays available to use. permissions.canRefund on the wallet is always false. Requests made before the retirement stay readable at GET /v1/minute/refunds, and any already approved refund still completes.
Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404.
A valid request URL is required to generate request examples{
"id": "<string>",
"sourceId": "<string>",
"micros": "<string>",
"currency": "<string>",
"status": "pending",
"customerMessage": "<string>",
"updatedAt": "2023-11-07T05:31:56Z",
"caseId": "<string>"
}{
"error": {
"code": "payload_too_large",
"message": "<string>"
}
}{
"error": {
"code": "rate_limited",
"message": "<string>"
}
}Authorizations
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.
Body
Validated operation fields; monetary amounts are server-quoted.
Response
Authoritative durable projection.