Own the surface
Move from a payment endpoint to the place merchants work.
Pair your existing rail with Merchant Console, Website, In person, and Connect under your institution’s name.
Commerce that knows your payment business and works for it.
Move beyond processing into the software merchants use to sell, operate, and grow, without surrendering the rails you already run.
Keep your gateway
Put your name on the merchant experience
License software instead of sharing transaction value
More control over the merchant relationship.
Keep the economics
Use a licence rather than another rate card.
Box charges for software. The processing relationship, commercial terms, and transaction revenue remain yours.
Grow together
Add capability without replacing your core.
Start with one merchant journey and install more packages as the product expands.
Operate locally
Keep data, identity, and providers in your estate.
The platform runs in infrastructure and regions your teams already govern.
Manage merchant commerce without rebuilding your rail.
Your gateway remains the payment implementation.
Box calls the payment port you provide. Credentials and provider-specific behavior remain outside the platform shell.
Merchants sign into your product.
Use your identity, navigation, support routes, and design system across the commerce surfaces you deploy.
Add the next merchant job when it is needed.
Install catalogue, checkout, invoicing, website, till, and operations packages against the same engine.
Connect your approved payment rails
Use one model for the commerce around every transaction
Operate the complete merchant experience in one placeFAQ
Does Box replace our payment gateway?
No. The institution’s payment implementation binds to Box through an explicit port.
Who owns the merchant relationship?
The institution does. The merchant experience can use its brand, identity, support route, and commercial model.
Does Box take a percentage of transactions?
No. Box licenses software and does not participate in transaction revenue.
Can we begin with one capability?
Yes. Packages can be installed incrementally while sharing the same commerce engine.
Where does merchant data live?
Inside the institution-operated deployment and selected region.
Can we use our existing authentication?
Yes. Merchant access binds to the institution authentication boundary.
Can our team build custom surfaces?
Yes. Use the generated API directly or combine custom interfaces with Box components.
Keep your payment business moving with Box.
Contact salesGet product and platform updates.
Box provides institution-operated commerce software. Payment processing, settlement, underwriting, scheme participation, and regulated financial services remain the responsibility of the institution and its approved providers.