Commerce banking
Every surface. One platform.
Commerce banking is the category Box by Potter is built for: a bank gives its merchants a complete commerce stack — in-store terminals, compact checkout devices, and every online channel — all settling on the bank’s own rails. The merchant never has to leave the bank to sell.
A traditional bank stops at the account. Box extends the bank all the way to the point of sale, so the same institution that holds a merchant’s money also owns how that merchant takes it.
One platform, every surface
In-store POS
A full catalog on a tablet plus a compact terminal with a customer display — running on the bank’s rails. Tap, insert, or swipe; funds settle T+0.
Online storefront
A website, a single shopping page, an Instagram-shoppable catalog, or payment links — all spun up from the same box the bank already runs. No separate provider, no hand-off.
Checkout anywhere
Payment links with no website needed, settling T+0. The merchant can take a payment from a chat, an invoice, or a social post and the money lands on the bank’s rails.
Settling on the bank’s rails
Every surface above — terminal, storefront, link — clears through the bank that runs the box. There is no third-party processor in the middle: the institution that holds the merchant’s account also captures the transaction, so settlement, risk, and the customer relationship all stay in one place.
A box is a self-hostable instance of the platform that a bank runs for its own merchants. See the introduction for how the engine, console, control plane, and storefront render fit together.
Why it matters
| For the bank | For the merchant |
|---|---|
| Owns the full commerce relationship, not just the account | One provider for in-store and online |
| Captures transaction volume that used to leave for processors | Funds settle T+0 on rails they already trust |
| Ships terminals, storefronts, and links from one platform | Never has to leave the bank to sell |
The merchant never has to leave the bank.