Integrate Orderboost checkout
Build with Orderboost checkout across storefronts, React applications, hosted buyer flows, MCP tools, and agent runtimes.
Start with the path that matches the surface you are building. You can place an existing storefront element, integrate the React Software Development Kit (SDK), or connect an agent through hosted checkout or Model Context Protocol (MCP).
Orderboost hosts its checkout API, account flow, payment services, and persistence. An integration consumes the URLs, App ID, browser capabilities, and credentials issued for that application. It does not clone the Orderboost repository or run Orderboost’s database.
Storefront element
Add a configured Orderboost control to an existing commerce template.
React integration
Render checkout elements and connect them to application state.
Agent integration
Open hosted checkout, pay with MPP, or control checkout through MCP.
Choose by integration surface
Choose the path that matches the code and buyer experience you control:
| Your surface | Start here | Checkout behavior |
|---|---|---|
| Existing commerce theme | Add Orderboost to a storefront | A configured element opens hosted buyer checkout |
| React application | Integrate Orderboost checkout in React | Your code controls placement, state, and lifecycle callbacks |
| Agent runtime | Choose an agent checkout path | The agent opens hosted checkout or controls an approved checkout |
Understand the checkout boundary
The browser and MCP paths share Orderboost’s catalog, quote, checkout, and order state. They use different authorization boundaries:
- Browser checkout: a checkout-scoped browser capability allows a person to enter details and complete payment
- Hosted agent checkout: the agent opens browser checkout and waits with a read-only status capability
- MCP checkout: OAuth allows protected operations, while a purchase grant authorizes one approved completion
- Handoff: a one-time code lets an authenticated agent claim an existing browser checkout without authorizing payment
- Paid HTTP: Tempo MPP can pay an advertised hosted checkout; other MPP or x402 resources require their own advertised endpoint
Read Compare checkout paths before combining browser and agent flows.
Continue with an implementation guide
Authenticate an MCP client
Use native OAuth or the local companion’s browser authorization flow.
Complete an approved checkout
Present buyer review, read the purchase grant, and complete once.
Pay with Tempo MPP
Qualify and pay an advertised hosted checkout with a Tempo wallet.
Understand button flows
Follow Sign In, Buy Now, Cart, Tip, and Page Guard.
Understand agentic checkout
Separate hosted checkout, MCP, human approval, and paid HTTP.
Browse MCP tools
Inspect every tool, authorization boundary, input schema, and output schema.
Browse the HTTP API
Inspect each supported URL-first HTTP operation, request, response, and code sample.
Review the security model
Separate OAuth, checkout access, handoff codes, and purchase grants.