Skip to main content
In plain English: TIN is a portable 10-digit payment identity. A sender can pay a TIN without knowing the recipient’s wallet address. TIN resolves to routing metadata and the TCAP relationship, not to a private key. The root wallet is the TIN authority.

​
What TIN is (and is not)

TIN is not a username, bank account number, or legal identity. Any name, business, phone, or verification context is optional enrichment and is not payment authorization.

​
Registrar program

Status: Live on Devnet.
The TIN Registrar exposes deterministic PDA helpers rather than a large instruction surface:

​
Resolution flow

  1. Sender supplies a 10-digit TIN.
  2. TIN service resolves the active public routing metadata.
  3. TSN SDK resolves the GPRU / TCAP relationship commitment and policy.
  4. Recipient route is bound into the signed plan commitment.
  5. If local private derivation is required, the owning wallet gives a fresh approval on that device.
Resolution must not return plaintext seeds, child private keys, or an unrestricted wallet-to-person mapping. Registrars apply non-enumeration, rate limiting, revocation, and state-version checks.

​
Record classes

​
Ownership and recovery

The root wallet is the TIN authority. It can approve access from any device. Encrypted TIN material is never sent in plaintext to a backend, Node, Receiver, or Cranker. Older device-bound envelopes require a one-time upgrade from a device that can already unlock them; new and upgraded TINs use the wallet-owned envelope model.

TSN

Settlement coordination and epoch treasury.

GPRU

Non-custodial authorization and routing.

TCAP

Private balance accounting.

Architecture

End-to-end sequence diagram.