Online checkout
Place a secure payment flow inside an existing merchant journey.
Embedded components
Build your product vision with checkout.invoicing.commerce.
Add the right merchant capability to the product you already run, without replacing its navigation, identity, or brand.
Plan your integration
Components designed to extend the product you already have.
Product catalogue
Let merchants manage the products every connected surface reads.
Invoices
Create, send, and settle invoices through the same commerce record.
In person selling
Bring a till to compatible phones, tablets, and counter devices.
Merchant operations
Embed focused views from Merchant Console where work already happens.
Custom experiences
Use the API when the interface needs to be entirely your own.
Ship merchant capabilities faster.
Use proven commerce foundations.
Start from packaged domain behavior instead of rebuilding catalogues, orders, refunds, and payment state.
Keep the experience yours.
Use your navigation, design system, identity, and support model around the components you select.
How it works
Choose the capability, bind the services it needs, and place it inside the product your merchants already use.
Select a component.
Install only the packages required for the intended merchant journey.
Bind your services.
Connect identity, payments, messaging, and settlement at explicit ports.
Ship inside your product.
Present the experience beneath your brand with your support route.
Trusted components, available where you need them.
Every component comes from the same package set and reads the same commerce records, so embedded and hosted experiences can operate together.
AUTHCATALOGUECHECKOUTORDERSPAYMENTSREPORTINGCONNECTWEBSITETILL
FAQ
What are embedded components?
Packaged commerce interfaces and workflows that run inside the institution product rather than a separate Box application.
Can we use our existing authentication?
Yes. The deployment is designed to bind to the institution’s auth guard so merchants do not need a separate Box identity.
Can we choose individual capabilities?
Yes. Components are installed by package, so a deployment can include checkout or invoicing without requiring every surface.
Can hosted and embedded surfaces work together?
Yes. They use the same catalogue, customer, order, and payment records in the institution-operated deployment.
Who controls payment providers?
The institution supplies the payment implementation used by the installed components.
Can our developers build custom interfaces?
Yes. Teams can combine embedded components with interfaces built directly against the generated API.
Where does merchant data live?
In the deployment and region operated by the institution.
Ready to add commerce to your product?
Bring the merchant journey you want to improve, the systems it must connect to, and the deployment boundary your team needs to keep.
Plan the integration