POS Integrations

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.

The walled-garden venues ClearBox serves already run on their own POS infrastructure: RIST wristbands at festivals, Square at small merchants, Toast at restaurants, and bespoke campus systems. ClearBox is designed to bridge these networks rather than replace them — a venue keeps its existing hardware and ClearBox plugs in behind it as the settlement layer.

​

How the bridge works

A legacy POS sees a ClearBox-issued card the same way it sees any Visa or Mastercard card: it sends an authorization request to the card network, which routes to ClearBox. ClearBox’s mirror ledger authorizes against the cardholder’s wallet and responds in real time. The POS gets a normal fiat-style approval and proceeds with the sale. For environments where the cardholder isn’t using a card at all (RIST wristbands, QR kiosks), ClearBox accepts authorization events directly from the POS network through the integration patterns below.

​

RIST

RIST provides the unified payments layer inside many of the venues ClearBox targets, including Compass Group sites. The integration runs in two directions:

• Terminals registered to ClearBox carry the RIST scanner’s ID as external_id (see Locations & terminals).
• Authorization events from RIST are forwarded to ClearBox via a server-to-server webhook, and ClearBox returns an authorize/decline within the network’s window.

​

Configuration

In the Dashboard, under Merchants → → Integrations → RIST, paste the merchant’s RIST API credentials. ClearBox then handles the bidirectional bridge — no code changes on the RIST side.

​

Square

Square’s integration uses Square’s webhooks. After the merchant connects their Square account to ClearBox via OAuth, ClearBox subscribes to payment.created and payment.updated events and reconciles them against ClearBox-issued cards. For card-present transactions on Square hardware, the cardholder’s ClearBox card is accepted as a normal card — the bridge happens at authorization time on the network rather than through Square’s API.

​

Toast

Toast integrates through Toast’s third-party API. Once the merchant authorizes the ClearBox app inside Toast, ClearBox subscribes to order and payment events and reconciles them the same way as Square.

​

Bespoke or unsupported POS

For systems without a public API, ClearBox supports two fallbacks:

• Generic webhook receiver. Your POS posts authorization events to a ClearBox webhook URL in a documented JSON shape, and ClearBox responds with authorize/decline.
• Card-only mode. The POS treats the ClearBox card as a regular Visa/Mastercard. The bridge runs entirely on the card network, no POS integration needed.

The card-only mode is the simplest and works at any terminal that accepts contactless cards — which is the point of building on the existing network rails.

​

Reporting and reconciliation

Every authorization, regardless of POS, lands as a transaction in ClearBox with the originating terminal_id. See Reporting for daily settlement reports that reconcile ClearBox transactions against the merchant’s POS records.