Money already moves on chains. It just does not move between them.
A person holding USDC on Base and a product settling on Sui are, in practice, on separate financial systems. Bridging the gap by hand is a five-step errand involving a bridge UI, a swap, a gas token they do not have, and a fifteen-minute wait. Most people simply stop.
CoinVoyage exists to collapse that errand into a single order. You describe where the money should end up. We scan what the payer actually holds, price every route across the liquidity providers worth pricing, chain them together when that pays better, execute each hop, and refund automatically if any step fails. The payer sees one quote and one confirmation.
What we refuse to compromise on
Four decisions that shaped everything else, and that we would rather lose a deal than reverse.
Non-custodial, not nearly non-custodial
Funds go directly from the payer to your wallet. There is no point in the flow where CoinVoyage is holding your money, and so no point where our solvency is your problem.
Route, do not educate
A user should never have to know what a bridge is or why their balance is on the wrong network. That is a routing problem, and routing problems have answers.
Webhooks over optimism
Browser callbacks are for updating an interface. Money moves on signed webhooks with explicit terminal states, because that is what a finance team can actually reconcile against.
Documented before it is announced
Every flow, chain ID, rail, and failure mode is written down in public docs. If something is in preview, it says so on the page.
What is shipped today
Not a roadmap. These are the surfaces you can integrate against right now, documented end to end.
PAYMENTS
PayKit
React providers, a pre-styled PayButton with a full payment modal, and a server-side ApiClient covering orders, quotes, refunds, invoices, fees, and off-ramp flows.
SWAPS
SwapKit
An embeddable cross-chain swap surface covering wallet connection, token selection, quoting, slippage, execution, and status, plus headless quote and execute endpoints.
OPERATIONS
Dashboard
Real-time analytics, transaction search with on-chain metadata, refunds, settlement configuration, fiat withdrawals, custom fees, invoices, and API key management.
PREVIEW
x402 agent payments
Decode a PAYMENT-REQUIRED challenge, choose an acceptable requirement, sign with an agent or server wallet, and retry. Supported chains and payloads are still evolving.
Where it runs
11 networks and 6 fiat currencies today, and a list that grows on a rolling basis.
Live networks
Bitcoin, Zcash, Ethereum, Solana, Sui, Base, Arbitrum, Optimism, Polygon, BNB Smart Chain, Robinhood Chain. Zcash is available through Pay to Address and as a swap destination, transparent addresses only.
In integration
Avalanche, Tron, and additional Ethereum L2s on the chain side. Further APAC currencies are under evaluation on the fiat side.
If your users hold the wrong asset, that is a solvable problem
Read how the routing actually works, or start building against it.