A cross-chain stablecoin transfer moves units of a stablecoin from one blockchain to another. What the holder receives on the destination is either the issuer's own token or a third-party copy, and that difference is the whole transfer.
This page explains how a unit moves, what arrives, and how that differs from a payment on one chain. To move a stablecoin across chains, reach out to our team.
What is a cross-chain stablecoin transfer?
A cross-chain stablecoin transfer is the movement of units of an issuer-managed, reserve-backed stablecoin from a source chain to a destination chain. The holder ends the transfer holding the asset on the destination. The source position is gone.
That is a different act from a stablecoin payment. A payment sends units from one address to another on the same ledger. A cross-chain transfer changes which ledger the units sit on. The two are often chained in a product, and they are still two steps.
What the holder receives
Three arrival types. The issuer's own token is the first.
| How the unit moves | What arrives | What happens to supply |
|---|---|---|
| Burn or lock, then mint or unlock | The issuer's own token | Outstanding units unchanged |
| Lock on source, mint a wrapped copy | A third-party representation | Original locked, plus a wrapper |
| Swap through a liquidity pool | A different token pulled from a pool | Depends on inventory on both sides |
The first row is a native transfer. The destination contract is the issuer's. Redemption, controls, and the holder's claim still run to the issuer.
The second row is a bridged copy. The holder now has a claim on the bridge. The ticker can match. The instrument does not.
The third row is a swap. The holder receives a different token from a pool on the destination.
How a canonical transfer works
A messaging layer verifies an instruction on the source chain and executes the matching credit on the destination. The OFT standard does that with debit-and-credit accounting: burn or lock on the source, mint or unlock on the destination.
The valid pairings are lock then mint, burn then mint, and burn then unlock.
Each deployment still holds its own balances. Outstanding units across the mesh stay constant because a send removes units on one side and a receive adds the same amount on the other. An issuer that needs the total reads every deployment and adds units that have been debited but not yet credited. That check lives on stablecoin operations.
PayPal USD is a production case of the issuer's coin arriving on the destination.
How debit and credit stay matched
A transfer has two moments: the source debit and the destination credit. Cross-chain settlement is when both have happened.
An outbound rate limit is checked at debit. An inbound limit is checked at credit. If the credit is retried later, the units stay in flight until the destination accepts them.
FAQ
Is a cross-chain stablecoin transfer the same as a stablecoin payment?
No. A payment moves units between addresses on one chain. A cross-chain transfer moves units from one chain to another.
Does the holder receive the same token on the destination?
Only on a canonical transfer, where the destination contract is the issuer's. A wrapped copy is a different token with a different counterparty.
Does total supply change when units move?
Not under debit-and-credit accounting. Units leave the source and appear on the destination. The issuer still aggregates deployments to read the total.
Can I send a stablecoin to another chain without wrapping?
Yes, where the issuer has deployed its own contract on the destination and uses a standard that credits that contract.
What if the destination credit is retried?
The source has already debited, so the units are in flight until the destination accepts them, for example when a rate-limit window reopens.
Move a stablecoin across chains
A cross-chain stablecoin transfer works when the destination token is the issuer's own contract and the debit on one chain is matched by a credit on the other.
To scope a transfer path or a new chain for an existing stablecoin, reach out to our team, or start at Developers.