Technical connectivity
Ledgers need compatible messages, token contracts and verifiable finality. Cross-chain gateways connect supported networks; they do not automatically connect every public chain, Swiss ledger or bank system.
Global payments · Connected ledgers
Global stablecoin
interoperability
From a Swiss-franc token to dollars in a US bank account: connecting chains, currency markets and banking networks without confusing token delivery with cash settlement.
Follow the paymentA connected payment, not a single global ledger
Stablecoins are issued on specific networks and against specific legal claims. Global interoperability means coordinating those networks so the payer can use one currency and ledger while the recipient receives another currency, token or bank deposit. Technical connectivity is only one part of that promise.
Liquidity & currency conversion
Moving a CHF token between chains does not turn it into a USD token. Currency conversion needs an executable FX quote, funded liquidity and a destination stablecoin the recipient accepts.
Legal & banking interoperability
Participants must agree on the token claim, redemption rights, compliance checks and settlement finality. A bank-network integration also needs access permissions, operating rules and compatible settlement assets.
The CHF-to-USD payment process
A CHF-to-USD payment could follow the four steps below when the required token integrations, FX liquidity and banking access are in place. The payer starts with CHF stablecoins; the recipient finishes with US dollars.
CHF → USD · End-to-end payment
Four steps, four hand-offs
- 01
Swiss issuer · CCIP / LayerZero gateway
Move CHF across ledgers
CHF stablecoin on a Swiss ledger
CHF stablecoin on a USD-liquidity chain
- 02
Liquidity provider · on-chain venue
Swap CHF into USD
CHF stablecoin
USD stablecoin, e.g. USDC
- 03
Destination gateway · recipient network
Deliver the USD token
USD stablecoin on the liquidity chain
Recipient’s chain or integrated bank network (e.g. Swift ledger)
- 04
Eligible redeemer · issuer / off-ramp · US bank
Redeem into US dollars
USD stablecoin
USD in the recipient’s bank account
Illustrative route, not a confirmed live corridor. Cross-chain movement, currency conversion and bank payout are separate operations; the full payment is not automatically atomic.
01 · Move CHF across ledgers
A gateway such as Chainlink CCIP or LayerZero carries an authenticated instruction to a supported destination chain. Depending on the token design, tokens are burned and minted, or locked and represented on the destination.
Dependency: Both ledgers and the CHF token must support the chosen integration; a messaging protocol alone does not make a token transferable.
02 · Swap CHF into USD
An on-chain swap exchanges the CHF token for a USD stablecoin at a quoted CHF/USD rate. A liquidity pool or market maker supplies the other side of the trade.
Dependency: A funded market must exist. FX spread, fees, slippage and depeg exposure determine how much USD the recipient gets.
03 · Deliver the USD token
The USD token is delivered to the recipient’s supported chain. Alternatively, an explicitly integrated bank network could receive a compatible token or settlement instruction, including a network built around Swift’s shared-ledger initiative.
Dependency: Swift is an illustrative bank-network branch, not a universal stablecoin destination. If the recipient uses the liquidity chain already, no second cross-chain transfer is needed.
04 · Redeem into US dollars
An eligible customer redeems with the USD issuer, or uses an approved off-ramp. The bank pays out dollars through supported US rails such as ACH, Fedwire or a supported instant-payment service.
Dependency: Redemption eligibility, KYC, bank access, cut-off times and payout limits still apply. On-chain delivery is not the same as final bank-account credit.
What each connection actually does
| Connection | Example | Role | Boundary |
|---|---|---|---|
| Cross-chain messaging | Chainlink CCIP; LayerZero | Authenticates messages and coordinates supported cross-chain token transfers. | Does not supply CHF/USD liquidity or grant redemption rights. |
| Token transfer model | Issuer-supported burn/mint; lock/mint bridges | Makes token value available on the destination ledger. | A wrapped token adds bridge and custody risk; not every representation has direct issuer redemption. |
| On-chain FX | Liquidity pool; RFQ market maker | Converts a CHF stablecoin into a USD stablecoin. | Requires actual market depth and a reliable quote; fees and slippage can change the outcome. |
| Bank-network connection | Integrated bank gateway; Swift shared-ledger initiative | Connects approved participants and compatible tokenised value or instructions. | No automatic acceptance of public-chain CHF tokens or USDC; specific integrations must be verified. |
| USD off-ramp | USD issuer; licensed payment provider; US bank | Converts the USD token claim to spendable bank dollars. | Eligibility, compliance, payout windows and bank-rail availability remain separate constraints. |
Where the payment can break
Gateway & representation risk
An invalid message, compromised key or bridge failure can strand or misrepresent value. Use supported issuer integrations, transfer limits, monitoring and explicit pause/recovery procedures.
Liquidity & FX risk
A CHF/USD market can be shallow or unavailable, and either token can depeg. Obtain executable quotes with expiry and slippage limits, and confirm reserve and redemption quality for both tokens.
Compliance & legal finality
A destination wallet or bank may reject a transfer. Check sanctions, counterparty eligibility, travel-rule obligations where applicable and the legal status of each token before execution.
Multi-step execution & bank payout
The swap may succeed while onward delivery or redemption fails. Track each leg, define refunds and exception ownership, and distinguish chain confirmation from issuer redemption and final bank credit.
Sources & further reading
Protocol capabilities are not proof that a particular CHF-to-USD corridor is operational. Confirm network support, issuer approval and bank participation before deployment.
- Chainlink — CCIP documentation
- LayerZero — Omnichain Fungible Token standard
- Swift — cross-network tokenisation experiments
- Circle — USDC and issuer redemption access
- Federal Reserve Financial Services — US payment rails
Educational overview, not legal advice or an endorsement of named providers. Swift’s ledger is an illustrative integration path; this page does not assert a live CHF-stablecoin connection.