Transfer Settlement Network · Solana

Private, Identity-first, and Confidential Crypto Payments on Solana

TrustLink Pay is built on the Transfer Settlement Network — a decentralized settlement layer for Solana that turns payment intents into private, cryptographically verifiable execution through Escrow Hold, Cranker execution, and Settlement Proof. Pay anyone using a phone number or 10-digit TIN instead of a wallet address, with private settlement and optional identity trust context.

Identity Layer

TIP

Payment identity and optional trust attestations

Privacy Layer

ZK-PRU

Purpose-bound protected receiving identities for each Transfer Identity

Settlement

TSN

Payment intents, epochs, Crankers, fees, and receipts

Confidential assets

TCAP

Reserve metadata, commitments, nullifiers, and private roots

How a payment works?

Settlement Clock:0.00s
CYCLE #1
01
Alice enters Bob's identity0% • Resolving bob.phone index...
02
Intent enters MempoolAwaiting step
03
Cranker submits on-chainAwaiting step
04
Escrow locks the fundsAwaiting step
05
Private claim pays BobAwaiting step
06
Proof settles at epochAwaiting step
Active Protocol Pipeline: Resolving bob.phone index...
Active
00Blockchain Solution

Why TrustLink Pay Is a Modern Blockchain Solution

A useful blockchain solution should make payments easier for people while preserving the verifiability that makes blockchain settlement valuable. TrustLink Pay does this by combining identity-first payments, stablecoin-native flows, private settlement routing, and developer APIs.

TrustLink Pay is the Web3 payment system users interact with. TSN is the settlement protocol that moves payment work through Crankers, ZK-PRU routes, and programmable blockchain settlement on Solana.

Blockchain Payments Without Wallet Addresses

Users can pay a phone number or TIN while the system resolves identity and settlement routes behind the scenes.

Identity-First Blockchain Solution

The Transfer Identity Protocol connects payment identity, verification context, and ZK-PRU route commitments.

Private Blockchain Settlement

TSN separates sender funding from recipient payout so payments do not look like simple wallet-to-wallet transfers.

Developer-Friendly Payment Protocol

SDKs expose identity resolution, payment authorization, fee transparency, and settlement status for apps building on TrustLink Pay.

01Identity

Pay people, not wallet addresses.

The world already understands how to pay people through identity. Nigeria uses OPay. India uses UPI. Brazil uses Pix. TrustLink brings that identity-first experience to stablecoin payments on Solana.

Instead of copying complex wallet addresses, users pay a phone number or a permanent Transfer Identity with a 10-digit TIN. Each upgraded Transfer Identity receives 30 ZK-PRU handles, so received funds land in private payment routes that are still controlled by the user's wallet proof.

Example TIN

4872-1930-41

A 10-digit identifier that protects your wallet address while enabling seamless payments across the TSN network.

How Transfer Identity Works

Phone-Number Routing

Send payments to any phone number linked to a Transfer Identity. The system resolves the phone to the recipient's TIN and settlement route.

Portable Payment Identity

Your Transfer Identity is not tied to one wallet. Change wallets without changing your public payment identity.

Address Protection

Your actual wallet address stays hidden from recipients. They see only your TIN, Transfer Identity name, or verified display name.

ZK-PRU-Routed Balances

Each upgraded Transfer Identity has 30 ZK-PRU handles. The app shows them as one TIN balance while TSN routes payments into ZK-PRU handles instead of a public owner wallet.

Identity And ZK-PRU Resolution

The Transfer Identity Protocol maintains a secure mapping between human-readable identifiers, TINs, and ZK-PRU settlement routes. When you initiate a payment, the system resolves the recipient's identifier without exposing raw wallet addresses.

Phone number → TIN resolution
TIN → wallet mapping
ZK-PRU route authentication

Identity Lifecycle

Each Transfer Identity can connect multiple identifiers — phone numbers, social handles, and verification credentials — to a single settlement identity. This creates a portable payment identity that works across applications.

Wallet-linked identities
Multi-identifier support
Cross-application portability
02Identity confidence

Trust context belongs with identity.

Transfer Identity provides the payment identity and can carry optional trust context. A TIN is still usable without a verified name or business credential.

TrustLink is designed to accept Solana Attestation Service (SAS) credentials when its credential-provider integration is available. That can let a sender confirm that a displayed legal or business name comes from a trusted issuer without making the credential itself a public payment record.

SAS

Solana Attestation Service

Future credential-provider integration

Zero

Personal Data Exposed

Trust context is separate from payment settlement

Future SAS attestation categories

Government Identity

A future trusted credential category for legal-name confirmation

Business Identity

A future credential category for verified business context

Proof Of Personhood

A future credential category for privacy-preserving human verification

Reusable Attestations

Attestation evidence associated with a Transfer Identity

Identity links

Link supported identity channels to your TIN for additional payment context. WhatsApp uses encrypted phone-number linking. X Business credentials are part of the planned attestation path.

WhatsAppActive
X BusinessSoon

Attestation design

When SAS credential providers are available, TrustLink can use their attestations as trust evidence for a Transfer Identity. The payment identity remains separate from the settlement layer.

Trust evidence is associated with identity
TINs remain usable without attestations
Settlement does not depend on credential exposure
03Settlement

Why TSN exists.

Direct wallet-to-wallet transfers are insufficient for everyday payments. They expose addresses, lack payment intent clarity, and offer no recourse for disputes.

TSN (Transfer Settlement Network) coordinates settlement through identity-first flows, Crankers, and verifiable settlement receipts trails.

TSN Coordinates Settlement

1

Payment Intent

Sender creates intent with fee transparency

2

Escrow Hold

Funds secured in protocol-controlled vault

3

Cranker Execution

Operator executes payout transaction

4

Settlement Proof

Verifiable off-chain evidence recorded

Security & Privacy

Intent authorization

Payment intents are signed and coordinated before settlement

Cranker Verification

Multi-signature settlement authorization

Off-Chain Proof Trail

Verifiable settlement evidence off-chain

Gasless Payments

Senders don't need SOL for transaction fees. Crankers — network operators — sponsor transaction execution in exchange for a fee included in the transfer amount.

Gasless by Design

Sender and recipient fees are shown before authorization

Fee Distribution

TSN

Settlement execution

Fees are coordinated by TSN according to the active network policy

TSN

Cranker Operators

Operators earn rewards for valid settlement work

TSN

Protocol policy

Exact fee allocation is versioned by TSN governance

Transparent Fee Breakdown

TSN separates network fees, settlement fees, and infrastructure costs instead of combining everything into a single unclear transaction cost.

Transfer amount

The amount to be sent

Solana network fee

Current chain transaction fee

Sender fee

Covers sender-side TSN execution and network sponsorship

Recipient fee

Deducted from the recipient payout and split by TSN policy

Recipient readiness

Status of the recipient identity

04For Developers

TSN SDK — Production-ready APIs.

TSN SDK provides developer APIs for Transfer Identity resolution, verification, and payment settlement on Solana. Build applications that consume Transfer Identity and TSN without rebuilding payment flows from scratch.

Identity APIs

Resolve TINs and phone numbers to settlement identities

Identity APIs

Resolve payment identity and its available trust context

Settlement APIs

Create payment intents and manage escrow workflows

Escrow Infrastructure

Protocol-controlled vault management for secure settlement

TSN SDK Integration

const recipient = await tsn.identity.resolve({
    identifier: "4872193041",
    type: "tin"
  });

const quote = await tsn.payments.quote({
    recipientTIN: recipient.tin,
    amount: 100_000_000,
    mint: USDC_MINT
  });

constintent = await tsn.payments.createIntent({
    quoteId: quote.id,
    senderWallet: wallet.publicKey
  });
05Roadmap

Current Capabilities

TIN Identity Registry

10-digit payment identities with wallet abstraction

Phone-Number Routing

Encrypted phone-number resolution and payment routing

WhatsApp Verification

Encrypted verification linking through WhatsApp

Gasless Payment Flow

Cranker-sponsored transaction execution

Escrow-Backed Settlement

Funds secured in protocol-controlled accounts

Settlement Intent Creation

Payment intent lifecycle management on TSN

Upcoming Capabilities

X Business Verification

Business identity credentials linked to Transfer Identity

SAS Credential Providers

Government, merchant, and proof-of-personhood attestations when provider integration is available

Multi-Cranker Network

Decentralized settlement operators under integration testing

Additional SPL Assets

Support for broader Solana token ecosystems

Analytics Dashboard

Transaction monitoring and settlement analytics tooling

Ready to Experience Identity-First Payments?

TrustLink Pay brings gasless, identity-first payments to Solana. Pay using phone numbers or TINs while keeping your wallet address private.