
Own the platform
Run the engine and console in your environment against your database. The merchant relationship, operating model, and records remain yours.
Review the architectureCommerce
Intelligence
Infrastructure
Why institutions choose Box
Keep the brand, records, rails, and merchant relationship.
Start here
By merchant activity
By deployment
See it running
OlivePay licensed Box. The tills are already in the field.
Deploy Box in the environment you choose, keep control of merchant relationships and data, and grow without giving away a share of every sale.
Box Enterprise helps you own your platform and protect merchant relationships so growth stays in your control.

Run the engine and console in your environment against your database. The merchant relationship, operating model, and records remain yours.
Review the architecture
Box is licensed per deployment. It does not take a percentage of merchant sales, so growth in the estate belongs to the institution.
See the commercial model
Orders, products, customers, locations, and settlement outcomes create operating context that a transaction feed alone cannot provide.
Explore InsightsPlan the migration, agree the operating boundary, and keep the deployment current through one coordinated programme.
Map source systems, test critical workflows, reconcile records, and move merchants in controlled cohorts.
Explore migrationAgree the region, infrastructure, identity boundary, provider connections, domains, and approval responsibilities.
Review deployment securityKeep the deployment current with package releases, upgrade guidance, documentation, and support.
Review responsibilities
For an institution launching its first merchant platform with catalogue, orders, payments, websites, tills, invoicing, bookings, and analytics.
Add subscriptions, memberships, loyalty, customer segmentation, campaigns, content, and locations without removing anything merchants already use.
Add staff roles, cross-tenant analytics, device tracking, deployment-level data residency, and named support commitments.
Box runs its own deployment internationally and licenses deployments by market. A licensed institution controls its merchant relationship, commercial terms, payment providers, access policy, and deployment data.
See the first licensed deployment
One-timefor the agreed deployment scope
30–50%of the original licence fee each year
No. Box separates the deployment licence, annual access, and merchant-level Connect usage.
The operating model and region are agreed during scoping. The institution operates the deployment by default, with Box Cloud available when a managed model is selected.
Yes. The tiers are nested, so moving upward adds capability without removing what merchants already use.
The institution does. Box records commerce and provider outcomes but does not replace the institution, processor, acquirer, or settlement system.
Migration uses data mapping, representative testing, controlled cutover, reconciliation, and cohort rollout.
The merchant estate, initial tier, deployment region, integrations, migration scope, support expectations, and target rollout shape.