Commerce infrastructure, live across 8,400+ merchants.
OlivePay runs Box across websites, payment links and in-person terminals on one licensed deployment.
Summary
OlivePay is a live commerce platform serving more than 8,400 merchants across websites, payment links and in-person terminals. It is not a pilot and it is not a demo: it is the same engine, composed from the same packages, deployed the same way.
Why this matters more than a logo wall
Every package an institution licenses is a package OlivePay is already running against real merchants and real settlement. The software is in production rather than on a roadmap.
The multi-tenant model is proven at merchant scale: tenant scoping, catalogue, orders and payouts hold up across thousands of independent businesses on one deployment.
What it proves
The deployment path works end to end on the same engine an institution would license, rather than on a version prepared for a demonstration. Nothing here was built specially for one customer.
One commerce record, across every selling surface.
Catalogue, orders, customers and settlement remain connected as merchants move between websites, payment links and the counter.
Selling stays connected.
Catalogue, variants, carts, orders, discounts, gift cards, invoicing and bookings use the same underlying records.
Settlement stays legible.
What the merchant sold and what settled are reconciled through the rails the institution operates.
Deployment reaches the counter.
Tills are provisioned against each merchant account and handed over working, one merchant at a time.
We are our own first customer.
When a package regresses, it regresses for us first. The incentive to keep the engine correct is operational, not merely contractual.
“The people maintaining the packages are running a business on them.”
How it runs
The same engine an institution licenses is composed from the same packages and deployed into infrastructure the operator runs.
- 01
A licence names a tier, and the tier resolves to a closed package set.
- 02
Merchants see OlivePay, not Box, across the product and its domains.
- 03
Catalogue, orders, customers and settlement records stay in the operator’s database and region.
- 04
Adding merchants adds rows; adding capability adds packages rather than another platform.
Ask us about the deployment.
Box is early, and every deployment is one we know by name.
Contact sales