Register through use.
Collect the business details needed for the product when the merchant has a reason to provide them.
Public sector
Turn everyday trade into a usable record.
Give small businesses software they choose to operate. Registration, transaction history and reporting then become outcomes of useful work—not separate administrative demands.
Let programmes operate on their own terms.
The checking reference presents four ways to use funds. This page mirrors that capability sequence for public-sector commerce programmes.
Record ordinary trade.
Orders, returns and settlement references form an audit trail as the business operates.
Apply local configuration.
Programme rules and tax settings can be represented in the deployment operated by the institution.
Query your own database.
Operational records remain in the environment and jurisdiction chosen by the deploying organisation.
One operating record
Put programme activity under one roof.
The same catalogue and order model supports counter sales, online orders and payment links, reducing the gaps created by separate systems.
Your estate.
No Box-hosted merchant database and no invented promise about where a third-party tenancy stores programme records.
Programme story
Start where usefulness is easiest to prove.
Choose one market, merchant category or district. Measure continued trading rather than registrations alone, then expand from evidence.
Move from a small scheme to a shared platform.
Nested licence tiers add packages without moving the merchant record to a replacement system.
Begin with a narrow workflow.
Start with catalogues, links and simple order records for one defined merchant group.
Add surfaces as demand appears.
Introduce counter, website or booking capabilities against the same deployment.
Keep governance local.
The deploying organisation controls infrastructure access, data policy and operational oversight.
Guidance for programme teams.
Continue with the boundaries most relevant to institutional deployments.
FAQ
Does Box become the system of record for government?
No. Box software runs in infrastructure operated by the deploying organisation. That organisation remains responsible for its records, access controls and policy.
Does Box verify citizens or businesses?
Box can connect to institution-supplied implementations, but it does not claim to operate government registries or make eligibility decisions.
Can a programme begin with one merchant group?
Yes. Package and licence choices can support a narrow deployment before additional capabilities are installed.
Who processes payments?
The institution and its chosen regulated providers remain responsible for payment processing and settlement.
Where does deployment data live?
In the database and infrastructure selected and operated by the deploying organisation.
Build a programme merchants choose to keep using.
Start with the public outcome, the operational boundary and the smallest useful merchant workflow.
Get Box updates.
Product, deployment and programme guidance.