Skip to main content

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.

ClearBox abstracts the hardest parts of stablecoin payments — identity, custody, keys, gas, card issuance, and real-time settlement — behind one integration. This page walks the complete lifecycle of a user, from signup to a tap at the register, and points to the guide for each step.

​
The end-to-end flow

A typical ClearBox integration moves a user through four phases. Each phase corresponds to one of the sequence diagrams your team works from.
1

Onboard & verify

The user submits a profile, links their bank through the embedded Quiltt connector, and is verified through ClearCheck (Persona). ClearBox cross-references the profile against the bank metadata before issuing a verified identity.
2

Provision a wallet

ClearBox provisions an invisible, non-custodial smart-contract wallet for the user through Crossmint and associates the wallet address with the user record.
3

Fund & issue a card

The user funds the wallet (for example, a $100 ACH deposit converted to USDC), and ClearBox issues a virtual Visa/Mastercard card derived from the wallet balance. The card can be provisioned into Apple Wallet for tap-to-pay.
4

Transact & settle

The user taps to pay. ClearBox’s mirror ledger validates available balance and authorizes in ~0.2 seconds, tells the point-of-sale the payment is good, and settles the underlying stablecoin on-chain in the background.

​
Phase 1 — Onboarding and identity

The user submits a signup form, ClearBox saves the profile as pending, and the embedded Quiltt Link widget launches so the user can authorize bank access. When the bank links, Quiltt fires an asynchronous webhook with an account token. ClearBox cross-references the profile data against the bank metadata, then sends the verified KYC payload to the identity layer and marks the user ready.

Link a bank with Quiltt

The open-banking connection flow, step by step.

Verify identity (ClearCheck)

How KYC inquiries run through Persona.

​
Phase 2 — Wallet provisioning

Once identity is verified, ClearBox creates an embedded smart-contract wallet for the user through Crossmint and returns a unique wallet address, which ClearBox associates with the user ID. The wallet is non-custodial and abstracts away keys and gas — the user never sees a seed phrase or signs a raw transaction.

Create a wallet

Provision an embedded wallet and store its address.

​
Phase 3 — Funding and card issuance

The user initiates a deposit (for example, “Deposit $100 via bank transfer”). ClearBox creates a bank-transfer authorization, receives a secure processor token, and funds the wallet — triggering an ACH transaction that settles into USDC. With a funded wallet, ClearBox issues a virtual card derived from the balance and, for iOS, retrieves the encrypted Apple PassKit payload needed to provision the card into Apple Wallet.

Fund a wallet (ACH)

Move fiat into the wallet as stablecoin.

Issue a virtual card

Derive a spendable card from the wallet.

​
Phase 4 — Transaction and settlement

When the user taps their phone at a terminal, the network routes an authorization request. ClearBox’s mirror ledger validates that the wallet has sufficient balance and returns an approval before the chain confirms, so the customer walks away while settlement completes asynchronously. ClearBox then burns the equivalent stablecoin from the wallet and records the transaction.

Authorization & settlement flow

How the mirror ledger authorizes faster than the speed of trust.

​
What makes ClearBox different

  • One integration, not ten vendors. ClearBox orchestrates open banking, KYC/AML, wallets, card issuance, and settlement so you don’t integrate each separately.
  • The blockchain is invisible. No gas, no seed phrases, no approval prompts for the end user.
  • Compliant by construction. Genius Act transaction limits, AML, and KYC are built into the product rather than bolted on.
  • Real-time at legacy terminals. The mirror ledger authorizes against existing Web3-blind point-of-sale hardware.
The provider-specific steps below reference the public request/response shapes of Quiltt, Persona, and Crossmint so your developers can follow them directly. Endpoints unique to your ClearBox program are labeled and use https://api.clearbox.example.com as a placeholder base URL.