01 / Configure
Package the right starting point.
Install only the products, orders, payments and reporting capabilities the programme needs. The licensed package set defines what exists.
Mobile money and telcos
Turn wallet users into everyday merchants.
A wallet moves money. Add the catalogue, counter, customers and order history that give merchants a reason to open it every day.
Get a merchant platform running on the network you already operate.
The reference journey moves from setup to enrolment, engagement and reward. Here, that same sequence becomes merchant activation across your wallet and agent network.
02 / Enrol
Let agents activate merchants where they trade.
An existing local network can introduce the service, help configure the first catalogue and keep support close to the merchant.
03 / Engage
Make the wallet useful between transfers.
Stock, orders, customers and daily takings create recurring work inside the same branded experience.
04 / Settle
Keep the sale and its record together.
Your institution remains responsible for payment processing and settlement. Box preserves the order-side record around those existing rails.
Keep merchants engaged with the network.
Use practical operating surfaces, not artificial lock-in, to make the relationship more useful over time.
One catalogue across every channel.
Counter, web, links and social selling read the same products, prices and stock.
Build around the agent network.
Give the people already near merchants a product they can activate and support.
Understand the merchant relationship with first-party operating data.
The deployment runs in your environment, so its commerce records remain inside the estate you control.
See what is being used.
Orders and catalogue activity show how merchants operate without exporting their records to Box.
Follow trade over time.
A consistent order history is more useful than occasional registration or survey data.
Keep residency concrete.
Choose where the deployment and its database run; Box does not become the merchant data host.
Useful for every kind of merchant.
Start with the categories your network already serves.
Market traders
Quick catalogues, cash records and links for repeat customers.
Neighborhood retail
Stock, counter sales and a simple online storefront.
Food businesses
Menus and orders connected across counter and online demand.
Services
Quotes, invoices and payment links without a full shopfront.
Connect the estate
Bind the providers you already use.
Payments, messages and supporting services connect through implementations supplied and operated by your team.
One operating plan
Grow by adding capabilities, not replacing systems.
Nested tiers add packages to the same deployment. A merchant can begin with links and a catalogue, then gain a website or counter surface without moving their history.
Promote the programme through channels you operate.
Use institution-approved messaging implementations to support onboarding and ongoing merchant education.
Make the first useful action clear.
Lead merchants to the catalogue, link or counter workflow included in their tier.
Explain each added capability.
Introduce new surfaces when the merchant has a reason to use them, not as an undifferentiated feature list.
FAQ
Does Box replace the mobile wallet?
No. Box supplies the commerce layer around the wallet and connects to institution-operated payment implementations.
Can agents onboard merchants?
The institution can design an onboarding workflow around its own staff, agents, identity checks and operating policies.
Where does merchant data live?
Inside the database and infrastructure operated for the institution’s deployment.
Can merchants keep selling when connectivity is unreliable?
Availability depends on the licensed surface and implementation. Offline-capable counter workflows must reconcile explicitly when connectivity returns.
Does Box hold wallet balances?
No. Funds and regulated services remain with the institution and its selected providers.
Give the wallet a reason to be opened every morning.
Run the commerce layer in your environment and put your own brand on every surface.
Explore the platform around it.
Continue with the operating surfaces and deployment model.
