01
Give merchants a reason to make your product primary.
Website, counter, payment-link, catalogue, customer, and order tools can sit inside the experience the bank already owns.
Build the merchant relationship around the account you already provide.
Bring the sale, the merchant, and the account into one operating picture.
02
Keep the rails and operating controls with the bank.
Payments and settlement connect through bounded implementations chosen by the institution rather than a Box-operated financial service.
03
Understand the activity behind each balance movement.
Products, channels, customers, returns, locations, and order state provide context the account balance alone cannot show.
Yourbrand and merchant experience
Yourinfrastructure, rails, and controls
Onecommerce and settlement record
Choose the operating model that fits the institution.
Review architectureOperate it
Run Box in your environment
Keep the database, infrastructure, access model, and operational controls inside the bank’s estate.
- Self-hosted deployment
- Bank-selected region
- Institution-owned records
Connect it
Bind the providers you choose
Payment, settlement, identity, and messaging implementations connect through explicit ports rather than hidden platform dependencies.
- Provider-neutral interfaces
- Clear service boundaries
- Replaceable integrations
Expand it
Install capabilities in stages
Start with one merchant workflow or segment, then add packages without replacing the operating record already in use.
- Nested licence tiers
- Phased merchant rollout
- One deployment model
The merchant experience
A working day, not another financial dashboard.
Merchants can act on orders, customers, stock, settlement state, and the work due today in one branded console. The bank becomes useful between financial transactions, not only when money moves.
Explore Merchant Console
A licensed deployment
See the institution model in the field.
OlivePay licensed Box, collected the first tranche, and put tills into merchants’ hands under its own operating relationship.
Read the OlivePay storyFAQ
Does Box replace the bank’s core system?
No. Box supplies the commerce layer around the merchant relationship and connects to institution-selected systems through bounded implementations.
Does Box hold deposits or merchant funds?
No. Accounts, deposits, payment processing, and settlement remain with licensed institutions and their providers.
Who owns the merchant data?
The deploying institution controls the database and operating environment. Box does not require merchant records to be stored in a Box-operated tenancy.
Can a bank start with one merchant segment?
Yes. A deployment can begin with a narrow set of packages and workflows, then expand without moving the existing merchant record to another platform.
Can the bank use its own payment providers?
Yes. Payment and settlement services connect through provider-neutral ports implemented by the institution or its chosen partners.