BLIPS PARVIA
Parvia connects bank-specific, non-bearer tokenized deposits through a Bitcoin-anchored Lightning execution network. Where suitable liquidity is available, banks can execute direct cross-border payments between tokenized-deposit domains—without a chain of intermediary correspondent banks or mandatory stablecoin on- and off-ramps.
The same network is designed for atomic interoperability with supported stablecoins, BTC, wholesale CBDCs, and tokenized collateral.
Keep deposits bank-specific. Make payments interoperable.
Parvia extends the payment capability of commercial-bank money to an open execution network without turning bank deposits into freely circulating bearer instruments.
Monetary foundation
Each tokenized deposit remains a contract-based liability of its issuing bank, recorded on that bank’s balance sheet and held within authorized institutional relationships.
Structural value 01
Where the same Liquidity Provider operates through both Settlement Access Gateway arrangements, Parvia creates a direct TD-to-TD corridor between the two bank deposit domains. The route removes the chain of intermediary correspondent banks and avoids mandatory stablecoin conversion where direct liquidity is available.
Direct bank-to-bank deposit interaction—without a correspondent chain.
Structural value 02
When a direct TD-to-TD route is unavailable—or another settlement asset is preferred—supported channels carrying stablecoins, BTC, wholesale CBDCs, or tokenized collateral can form one atomic cross-asset payment path.
Different assets. One atomic execution path.
Parvia does not make bank deposits freely transferable. It makes bank-specific deposits interoperable.
Each bank retains its own Core Ledger, deposit liabilities, customers, and bank-controlled Issuer Node. A bank-specific channel connects that Issuer Node to an authorized SAG Node, which links the deposit domain to other banks and supported asset nodes across the Parvia network.
Bank liabilities remain issuer-specific. SAG Nodes make their payment capability interoperable.
Open full-size architectureParvia separates legal issuance, network execution, and liquidity provision.
Legal issuance + execution node
01The bank remains the legal deposit issuer and operates the authoritative Core Ledger. Its bank-controlled Issuer Node executes authorized tokenized-deposit activity on the Parvia network.
Authorized access + execution node
02The Settlement Access Gateway Operator provides authorized access to a specific bank deposit domain. Its SAG Node maintains the bank-specific channel and connects that domain to other supported network nodes.
Financial role · not a node
03Liquidity Providers publish executable quotes and commit funded or credit-supported positions through SAG account or omnibus arrangements. They perform the FX and liquidity function of next-generation correspondent banking, but they are not Parvia network nodes.
Coordination layer + execution nodes
04The Parvia Layer coordinates institutional access, addressing, pre-validation, quoting, route selection, atomic execution, and settlement confirmation across Issuer Nodes, SAG Nodes, and supported asset nodes.
Supported asset nodes may include:
Banks issue deposits. Liquidity Providers price and fund the route. Nodes execute the payment path.
Parvia supports a direct TD-to-TD corridor and an atomic cross-asset route between bank-specific deposit domains.
Two execution models: a direct TD-to-TD corridor supported by the same Liquidity Provider, or an atomic cross-asset route connecting different Liquidity Providers through supported asset channels.
Open full-size execution-path diagramPath 01
The same Liquidity Provider operates through both SAG arrangements.
It receives the source bank’s tokenized-deposit position and delivers the destination bank’s tokenized-deposit position under one quote and one atomic execution—without mandatory stablecoin conversion or a chain of intermediary correspondent banks.
Path 02
Different Liquidity Providers operate through their respective SAG arrangements.
Supported channels carrying stablecoins, BTC, wholesale CBDCs, or tokenized collateral connect the two bank domains in one atomic payment path, while each bank-issued deposit remains within its authorized domain.
BLIPS Parvia
Connect bank-issued deposits directly—and enable atomic interoperability across supported money and asset networks.