Separate checkout authority
Distinguish identity, browser checkout access, handoff access, and exact payment approval before combining Orderboost's human and agent flows.
Orderboost separates identity from payment authority. No single browser link, OAuth scope, or handoff code can authorize every checkout action. Model Context Protocol (MCP) clients use these credentials at different stages.
Map each credential to one job
Each credential has a narrow purpose:
| Credential | Grants | Does not grant |
|---|---|---|
| Email verification code | Proof of a new account email | MCP connection or payment |
| Companion connection code | Completion of one local OAuth flow with its secret | Account login or payment |
| MCP OAuth token | Protected agent tools within its resource and scopes | Payment completion by itself |
| Browser capability | Access to one hosted checkout | Agent access or arbitrary item replacement |
| Buyer status capability | Read-only terminal status and order identifier | Full checkout reads or mutation |
| Handoff code | One-time agent claim of an existing checkout | Authentication or payment authority |
| Purchase grant | One exact agent-controlled completion | Approval after any checkout mutation |
| MPP Credential | One exact live advertised payment request | Changed qualification or arbitrary orders |
| x402 payload | One explicitly advertised external paid HTTP flow | Orderboost checkout approval or arbitrary orders |
Bind approval to authoritative state
An exact purchase grant binds the checkout identifier, approved revision, quote hash, merchant, agent OAuth client, amount, currency, tokenized payment reference, approving person, and expiration.
Any mutable checkout update revokes the grant. Orderboost verifies every binding atomically before it authorizes and captures payment.
Keep secrets out of chat
The six-digit companion connection code is safe to paste only because the local companion also holds a high-entropy flow secret. The code appears after fresh account authentication and OAuth consent, expires after 10 minutes, and works once. It is not the email verification code.
Never place bearer tokens, hosted checkout URLs, browser capabilities, payment credentials, handoff codes, or purchase grants in agent instructions or normal chat messages.