One way to take every kind of payment.

In store, online, by link, or on the move, every sale reaches the same order history and settles on the rails your institution chooses.

A payment terminal beside a shop counter

Every channel

Meet customers wherever they are ready to pay.

Payment terminal on a counter

At the counter

Take cards, wallets, and cash from one till, with the order attached from the first tap.

A product page open on a laptop

On your website

Give customers a fast checkout that carries catalogue, stock, and customer details with it.

A payment link displayed on a phone

From any conversation

Send a secure payment link from a message, invoice, or social post and follow its status live.

A contactless payment being made from a phone

While moving

Take a payment from the aisle, table, market stall, or customer’s doorstep without returning to a desk.

Choose the surface

Checkout hardware that fits the work.

Phone accepting a contactless payment

No extra hardware

Tap on phone

Turn a compatible phone into a checkout for temporary counters, deliveries, and queues.

Countertop payment terminal

Portable

Portable terminal

Connect a compatible handheld terminal to take an order, accept payment, and send a receipt.

Point of sale register

Countertop

Counter register

Connect a fixed checkout for busy counters, with a clear payment flow for the customer.

A till screen showing a menu of items

Flexible

Tablet stand

Make a compatible tablet the centre of a complete till that can change with the counter.

Inside your app

Put the till inside the product you already ship.

Embed the commerce libraries or use the optional Box screens. The institution keeps its app, devices, payment component, and release process.

Enrol each device

Bind the device to a merchant and location, then synchronise its catalogue, permissions, and operating rules.

Keep offline work visible

Approved local operations remain queued until connectivity returns, with pending, confirmed, and rejected states kept distinct.

Keep capture outside Box

The institution supplied payment component handles card data and returns only the result needed to update the order.

Account activity showing sales and transfers beside their payment state

One connected record

Keep the payment attached to the work it paid for.

The institution chooses and operates the rails. Box keeps each provider result beside the order, channel, customer, and location that produced it.

  1. Order first

    Products, discounts, staff, and channel form the order before money moves.

  2. Every result stays explicit

    Approved, declined, pending, and uncertain outcomes remain visible without inventing a successful state.

  3. Reconcile in context

    Operations can compare the provider reference with the exact order and merchant involved.

Confidence built in

Every payment is designed to be clear, controlled, and recoverable.

Permissions by role

Give each team member the actions they need without handing over the whole business.

A complete trail

Refunds, voids, discounts, and edits remain tied to the person, order, and payment involved.

Your deployment

Payment configuration stays inside the environment your institution operates and controls.

See how payment credentials stay outside Box

Built for a network

Run one payment foundation across thousands of different businesses.

One

payment contract between the institution and its merchants, not a new platform relationship for every channel.

Every

merchant can receive a configuration shaped to its catalogue, staff, locations, and local payment methods.

Zero

share of transaction value taken by Box. The economics stay with the institution running the rails.

See enterprise deployment

Common questions

Payments with Box.

Does Box process the payment?

No. Box provides the commerce software and connects it to the payment rails selected by the institution operating the deployment.

Can the same setup work online and in person?

Yes. Website checkout, tills, links, and invoices create orders in the same engine and resolve the same configured payment connection.

What happens when an embedded till loses connectivity?

Operations approved for local use remain visibly queued and reconcile with explicit success, conflict, or rejection states when connectivity returns.

Does Box charge a percentage of sales?

No. Box is licensed software and does not take a share of transaction value.

Ready when you are

Take the next payment with Box.