Once a merchant is KYB-active, you model its physical footprint as locations (sites inside the venue) and terminals (the actual readers). Every authorization ClearBox sees can be traced back to a specific terminal at a specific location under a specific merchant.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.
Locations
A location is a physical or logical site under a merchant — a stage, a food court, a campus dining hall, a stadium concourse section. Locations carry an address and a timezone so transaction timestamps and reporting line up with the operator’s view.Add a location
Terminals
A terminal is the actual hardware or software endpoint where a guest taps, scans, or pays. ClearBox supports several terminal types:| Type | Description |
|---|---|
pos_legacy | An existing legacy point-of-sale terminal that doesn’t natively speak blockchain. ClearBox bridges it. |
rist_wristband | A RIST wristband scanner (RFID + ticketing + payment). Common in festivals and resorts. |
mobile_reader | A handheld card reader carried by staff (roving sales). |
qr_kiosk | A QR-code kiosk where a guest scans to pay from their phone. |
Register a terminal
external_id is the ID of the terminal in the merchant’s existing system (RIST, Square, Toast, etc.). ClearBox uses it to match incoming authorizations from that system back to the right terminal.
What you’ve built
You can now trace every settled transaction back to a merchant, a location within that merchant, and a specific terminal at that location. Reporting and reconciliation use this chain.POS integrations
Bridge legacy POS networks (RIST, Square, Toast) into ClearBox.
Settlement & payouts
Configure where settled funds arrive.