Learn the difference between a payment transfer, authorization, clearing, and settlement—and how blockchain networks and TSN coordinate final asset ownership.
How Transfers and Settlements Work
When someone sends money, it often appears to happen in one simple step:
Sender pays → recipient receives.
Behind the screen, however, a payment may pass through several separate stages involving authorization, messaging, clearing, funding, reconciliation, and final settlement.
Understanding these stages is important because moving payment information is not always the same as moving the underlying money.
A transfer tells a system that value should move. Settlement is the process that makes the resulting ownership change final.
What Is a Transfer?
A transfer is an instruction to move value from one person, account, wallet, or institution to another.
The instruction normally identifies:
- the sender;
- the recipient;
- the asset or currency;
- the amount;
- the destination;
- the sender’s authorization;
- any required payment conditions.
A transfer may be initiated through:
- a bank application;
- a debit or credit card;
- a mobile-money account;
- a payment service provider;
- a blockchain wallet;
- a payment identity such as a Transfer Identity Number.
Creating the transfer does not necessarily mean that final settlement has already occurred.
What Is Payment Authorization?
Authorization answers the first important question:
Is this sender permitted to initiate this payment?
For a card payment, the issuing bank may check:
- whether the card is valid;
- whether sufficient funds or credit are available;
- whether the transaction appears suspicious;
- whether the payment exceeds any account limits.
For a bank or mobile-money payment, authorization may involve a PIN, password, device confirmation, biometric check, or account signature.
For a blockchain wallet, authorization usually comes from a cryptographic signature created with the wallet’s private key.
Authorization approves the requested action. It does not always complete the final movement of money.
What Is Clearing?
Clearing is the exchange and processing of payment information before final settlement.
The Federal Reserve describes clearing as the exchange of payment information, potentially including activities such as fraud screening. Settlement is the actual debiting and crediting of accounts to transfer the funds.
Clearing may include:
- validating transaction records;
- comparing payment instructions;
- calculating obligations;
- netting several payments together;
- performing fraud and compliance checks;
- determining how much each participant must pay or receive.
For example, instead of settling every card purchase individually, financial institutions may combine many transactions and calculate the final amount owed between them.
What Is Settlement?
Settlement is the stage where the financial system performs the final asset or account ownership update.
It answers:
Who owns the money after the payment completes?
Settlement may involve:
- debiting the sender’s bank;
- crediting the recipient’s bank;
- moving balances between financial institutions;
- updating a mobile-money ledger;
- transferring tokens between blockchain accounts;
- rewriting confidential ownership backed by a reserve.
The BIS defines settlement finality as the point at which the transfer of an asset becomes irrevocable and unconditional.
This means settlement is deeper than displaying a successful payment notification. It is the financial state change that completes the transaction.
Authorization, Clearing, and Settlement Are Different
The complete traditional lifecycle can be represented as:
Payment initiated
→ Authorization
→ Payment message transmitted
→ Clearing and reconciliation
→ Settlement obligation calculated
→ Accounts debited and credited
→ Payment finalized
A payment may be authorized within seconds while the institutions behind it settle later.
That is why a card terminal can display “Approved” even though the merchant may not receive settled funds until a later settlement cycle.
How Traditional Bank Transfers Work
A domestic bank transfer may pass through:
- The sender’s bank.
- A payment or clearing network.
- A central settlement system.
- The recipient’s bank.
- The recipient’s account.
The customer sees one transfer, but the banks must still exchange instructions and settle their financial obligations.
Some systems settle transactions individually in real time. Others calculate net positions and settle them in batches.
The Federal Reserve’s National Settlement Service, for example, enables participants in private clearing arrangements to submit multilateral settlement files and settle through master accounts held at Federal Reserve Banks.
How Cross-Border Transfers Work
Cross-border payments can involve more institutions because the sender and recipient may use different currencies, banking systems, and settlement arrangements.
A simplified cross-border flow may look like:
Sender
→ Sender’s bank
→ Payment message
→ Correspondent or intermediary banks
→ Foreign-exchange conversion
→ Recipient’s bank
→ Recipient
SWIFT is frequently described as a global payment network, but SWIFT itself explains that it does not move the money. It provides secure messaging through which financial institutions exchange payment instructions. The actual transfer occurs through banks, fintech companies, and settlement institutions.
This distinction illustrates the difference between:
Payment messaging
and:
Final settlement
How Mobile-Money Transfers Work
Mobile-money platforms make payments feel immediate because both users often exist within the same controlled ledger.
When one user pays another:
Sender’s mobile-money balance decreases
→ Platform ledger updates
→ Recipient’s balance increases
The platform can provide a simple experience because it controls:
- user identities;
- account balances;
- authorization;
- routing;
- transaction records;
- final ledger updates.
This is one reason mobile money can feel easier than blockchain payments. Users normally send to phone numbers or account identities rather than long wallet addresses.
The challenge is reproducing that experience without requiring one company to centrally control the entire payment system.
How Blockchain Transfers Work
A basic public blockchain transfer can combine authorization and ledger settlement more closely than many traditional systems.
Sender signs transaction
→ Network validates transaction
→ Blockchain state changes
→ Recipient wallet receives the asset
The transaction message and the asset movement can occur within the same blockchain transaction.
However, a blockchain transfer is not automatically a complete payment system.
A raw wallet transfer may still lack:
- human-readable payment identity;
- private routing;
- merchant authorization rules;
- recurring-payment permissions;
- confidential balances;
- protected transaction receipts;
- payment-intent coordination;
- fiat entry and withdrawal;
- dispute or failure management.
Public blockchains provide programmable asset-transfer rails. Additional infrastructure is required to make those rails work like an everyday payment network.
Transfer Does Not Always Mean Complete Settlement
The word “transfer” can describe several different events.
A payment instruction
Please send 100 units to the recipient.
A pending ledger update
The payment has been accepted but is waiting for settlement.
A blockchain token transfer
The on-chain ownership record changed.
A completed real-world payment
The recipient can access and use the intended currency.
These events may occur together, but they are not always identical.
For example, a stablecoin may reach a recipient’s wallet within seconds while conversion into local bank money takes longer.
Stablecoin infrastructure can provide continuous blockchain availability, and providers increasingly describe merchant and network settlement that operates around the clock.
But the full payment journey may still depend on:
- stablecoin issuers;
- liquidity providers;
- foreign-exchange markets;
- local banks;
- compliance providers;
- fiat on-ramps and off-ramps.
Why Modern Payment Networks Separate Intent From Settlement
A payment intent describes what the user wants to happen.
A settlement transaction performs the final ownership change.
Separating these two stages can provide important benefits:
- a third party can pay the blockchain transaction fee;
- the sender does not need to remain online;
- policy conditions can be checked before settlement;
- funding can be verified before delivery;
- replay protection can be applied;
- sender and recipient activity can appear in separate transactions;
- failed transactions can stop before final asset movement.
This separation is central to the Transfer Settlement Network architecture.
How Transfers and Settlements Work in TSN
The Transfer Settlement Network is designed to make blockchain payments feel closer to traditional mobile money.
Native users send through a 10-digit Transfer Identity Number rather than exchanging public wallet addresses.
TSN is the complete payment network. Its architecture includes:
- TIN payment identity;
- ZK-PRU authorization;
- the TSN intent mempool;
- TSN mempool nodes;
- Crankers;
- the on-chain TSN program;
- payment-data PDAs;
- TCAP confidential asset settlement;
- private payment receipts.
The native transaction lifecycle contains two major states.
State One: Intent and Funding
The user first creates a payment intent.
For a native TIN payment, the sender selects:
- the recipient’s TIN;
- the asset;
- the amount;
- the payment purpose;
- the expiry;
- any required conditions.
The user does not submit this intent directly to the on-chain TSN program.
Instead:
User
→ TSN mempool
For a TIN transaction, the user’s encrypted Layer 0 authority is retrieved from the ZK-PRU registry and decrypted on the user’s device.
Layer 0 creates a scoped Layer 1 authorization defining what the network may execute.
The authorization may bind:
- protocol ID;
- purpose ID;
- asset;
- amount;
- destination scope;
- permitted action;
- expiry;
- provider or subscription conditions.
Only the authorization leaves the device. The decrypted Layer 0 material does not.
The payment intent and Layer 1 authorization are then placed in the TSN mempool.
The First Cranker Submission
After the intent is accepted, a Cranker submits the first authorized on-chain transaction.
TSN mempool
→ Cranker
→ TSN program
The Cranker pays the blockchain transaction fee. The user does not call the TSN program directly.
The TSN program creates a payment-data PDA containing the payment’s on-chain state and references.
The PDA may store:
- payment commitment;
- authorization reference;
- asset reference;
- destination commitment;
- nonce;
- expiry;
- current status;
- funding reference.
The TSN program does not escrow the payment assets.
TSN program
= payment state
TCAP
= reserve and confidential ownership state
Public funding moves into the TCAP reserve, while an existing confidential source may instead be referenced for a native TIN payment.
After the payment state and funding state are established, the payment becomes claim-ready.
State Two: Mempool Claim and Settlement
The TSN mempool node observes the funded payment and verifies the Layer 1 authorization.
The node then uses its restricted Layer 2 execution authority.
Layer 2 cannot act independently.
Valid Layer 1 authorization
→ Layer 2 permitted
Invalid or missing Layer 1 authorization
→ Layer 2 blocked
→ no ZK-PRU selection
→ no settlement claim
Within the permitted scope, the TSN node performs the required ZK-PRU selection mathematics and prepares the settlement claim.
A Cranker then submits the second on-chain transaction:
Claim-ready payment
→ Cranker
→ TSN program
→ TCAP
This is the claim-settlement transaction, separate from the earlier intent-and-funding transaction.
TCAP Confidential Asset Settlement
TCAP is the Transfer Confidential Asset Protocol inside TSN.
TCAP verifies the asset side of settlement, including:
- mint and token-program binding;
- payment commitment;
- authorization reference;
- funding state;
- confidential ownership;
- nonce or nullifier;
- replay protection;
- reserve and liability accounting.
After successful validation, TCAP performs the final ownership update.
For a native TIN-to-TIN transfer:
Sender confidential ownership decreases
→ Recipient confidential ownership increases
→ Nonce or nullifier is consumed
→ Reserve-backed accounting remains balanced
The reserve assets may remain in the same TCAP reserve. What changes is the confidential ownership representation.
The TSN payment-data PDA is then marked settled, and private receipts become available to the sender and recipient.
TSN Transaction Lifecycle
The complete native flow can be summarized as:
Sender creates payment intent
→ Layer 0 creates Layer 1 authorization
→ Intent enters TSN mempool
→ Mempool verifies authorization
→ First Cranker submits intent and funding transaction
→ TSN program creates payment-data PDA
→ TCAP funding state is established
→ Payment becomes claim-ready
→ TSN node uses Layer 2 within Layer 1 scope
→ ZK-PRU source or route is selected
→ Second Cranker submits settlement claim
→ TSN program processes settlement state
→ TCAP updates confidential ownership
→ TSN payment PDA is marked settled
→ Private receipts become available
Transfer Network vs Settlement Network
A transfer network mainly helps communicate or route instructions.
A settlement network must also coordinate the final ownership change.
| Function |
Transfer |
Settlement |
| Creates payment instruction |
Yes |
Uses the instruction |
| Identifies sender and recipient |
Usually |
Verifies settlement destination |
| Authorizes payment |
Yes |
Verifies authorization |
| Moves final asset ownership |
Not always |
Yes |
| Handles reserve accounting |
Not necessarily |
Often |
| Produces final transaction state |
Sometimes |
Yes |
A complete payment network needs both.
Why This Difference Matters
A payment can look finished to a user even when financial institutions are still clearing and settling behind the scenes.
Blockchain reduces some of this separation by placing programmable assets and settlement logic on a shared ledger.
But real adoption requires more than faster transfers.
It requires infrastructure for:
- identity;
- authorization;
- funding;
- settlement coordination;
- transaction submission;
- confidential ownership;
- finality;
- receipts.
That is the broader problem a Transfer Settlement Network is designed to solve.
Conclusion
A transfer communicates the instruction to move value.
Settlement makes the ownership change final.
Traditional systems often separate authorization, clearing, and settlement across several institutions and time periods. Blockchain systems can bring asset movement and ledger finality closer together, but a raw blockchain transaction still does not provide the complete experience required for everyday payments.
TSN is designed around that missing infrastructure.
Users create payment intents. The mempool coordinates them. Crankers submit the required on-chain transactions. The TSN program records payment state. TCAP holds reserve assets and finalizes confidential ownership.
The transfer begins with user intent. The payment is complete only when settlement finalizes ownership.
