ClearBox is built for closed-loop, walled-garden environments: music festivals, all-inclusive resorts, amusement parks, stadiums, corporate campuses, university dining, cruise ships, and the food-service networks that operate them. This section covers the merchant side of a ClearBox deployment — onboarding the venue, registering its terminals (including legacy point-of-sale hardware that doesn’t speak blockchain), and getting settled funds to the right account.Documentation Index
Fetch the complete documentation index at: https://docs.clear-box.io/llms.txt
Use this file to discover all available pages before exploring further.
Onboarding overview
The end-to-end flow from intake to first settled transaction.
KYB verification
Verify the business entity through ClearCheck.
Locations & terminals
Add venues and register the terminals at them.
POS integrations
Bridge legacy POS networks (RIST, Square, Toast) into ClearBox.
Settlement & payouts
Configure bank or stablecoin destinations and payout cadence.
Reporting
Reconcile transactions, payouts, and settlement reports.
Why merchants choose ClearBox
A walled-garden operator typically has three problems no single legacy provider solves at once:- Web3-blind terminals. Their existing point-of-sale hardware doesn’t accept digital assets.
- Fragmented payments. Wristbands, tickets, app payments, and card readers all run on different systems.
- Compliance gaps. Accepting stablecoin at scale requires MTL, VASP, and DLT coverage they don’t have.
Who’s involved
| Role | Responsibility |
|---|---|
| Venue operator | The legal business entity (the festival LLC, the campus food-service contractor). Goes through KYB. |
| Locations | The physical or logical sites inside the venue — stages, food halls, dining locations. |
| Terminals | The actual readers — legacy POS, wristband scanners (e.g. RIST), mobile readers, QR kiosks. |
| Settlement account | The bank or stablecoin destination where the operator’s payouts arrive. |