What is KYC and eligibility gates?

Know-your-customer is the identity layer regulated finance requires: who holds what, verified before they hold it. On public chains identity cannot be enforced at the address level, so the gate moves to the edges, issuers allowlist transfers, platforms gate on-ramps, checkouts ask buyers to confirm eligibility.

For tokenized assets the pattern is layered: the issuer's on-chain rules do the hard enforcement (transfers to blocked addresses revert), while the venue carries the disclosure duty, stating plainly who may hold and what rights do not attach.

How KYC and eligibility gates works

Know-your-customer is the identity collection obligation that attaches to regulated money services: verifying who a customer is before providing certain services, typically through document checks, database matches, or increasingly cryptographic methods. It exists to anchor legal accountability to identifiable parties.

The obligation is boundary-dependent. Fiat on-ramps and card processing import full KYC from the banking world because they touch those systems. Pure on-chain settlement between self-held wallets generally sits outside it, because there is no custodian to regulate. Where a platform holds funds or touches fiat, some identity layer is usually unavoidable.

For users the practical arithmetic is friction versus access: KYC'd rails reach bank accounts and cards at the cost of onboarding ceremony, while non-custodial flows skip the ceremony at the cost of staying within on-chain reach. Composing both, as U.CASH checkout does, lets each payment find its natural boundary rather than forcing one model on everything.

KYC and eligibility gates in practice

A merchant takes crypto payments non-custodially with no identity ceremony for the crypto side, while the card leg runs through their own processor account whose KYC happened at that account's opening. Two boundaries, two behaviors, one checkout.

KYC and eligibility gates on U.CASH

U.CASH checkouts present eligibility confirmations for tokenized assets and pre-flight the issuer's transfer gate; the asset pages carry the disclosures so the terms precede the transaction.

Merchants should know which of their rails carry identity obligations and where those obligations sit: on the merchant, the processor, or the ramp. On U.CASH the crypto side is non-custodial and the card side runs through accounts that already cleared their checks, so the composition stays honest without duplicating ceremony. For merchants composing rails deliberately, the boundary map is worth writing down once: which legs touch fiat, which providers' requirements apply, and what each collects. The map rarely changes, and having it converts regulatory questions from research projects into lookups.