One‑off payment
Agree a price, create the order and send a path to payment.
Payment links
The simplest way into a recorded sale.
A link, quote, invoice or QR journey that creates a real order and settles through the payment rails your institution already operates.
Your sale. One small surface.
The services reference begins with the different professionals it serves. This page begins with the different jobs one payment primitive can do.
Quote
Describe the work before converting the accepted amount into an order.
Invoice
Attach terms and a due date to the same underlying commerce record.
Deposit
Connect an advance payment to the appointment or work it belongs to.
QR journey
Open the same payment experience from a physical handoff.
All you need to turn a link into an order.
The object remains inside the same commerce model as every other channel.
Know who bought.
Associate the transaction with a customer record the merchant can use again.
Know what was sold.
Use a catalogue item or a clear one-off description instead of an unexplained transfer reference.
Use existing rails.
Send payment work to the provider implementation supplied by the institution.
Keep the reference.
Preserve the link between the order and the settlement record received from the provider.
Return against the sale.
Keep refund activity attached to the original order rather than separate manual arithmetic.
Count the trade.
Include link-based sales in the same merchant reporting as counter and website orders.
Connected by default
A shortcut for the customer, not the ledger.
The buyer sees a compact experience. Behind it, the sale still has a customer, amount, item, payment reference and status.
Hone the selling workflow.
Move from the primitive to the channels and operating systems around it.
Start with a link. Keep the path to a platform.
The smallest merchant experience can still use the complete commerce record underneath.
Learn about new Box capabilities.
Product changes and practical commerce guidance.