How to Pay a Vendor on a Different Chain

If a vendor gives you a wallet address on another blockchain, confirm the destination network and exact asset before sending; then compare routes by the amount the vendor will receive. A cross-chain payout has two sides to verify: the payment leaves your wallet, and the right token arrives where the vendor can use it. For the broader treasury decision, see how omnichain handles treasury payouts; this guide focuses on one payment. Omnichain is one service for routing token transfers and swaps across supported chains.

What should you confirm with the vendor?

Ask for the network, token, and receiving address as separate details. “USDC” alone is not enough: tokens with the same ticker can have different contract addresses and may not be accepted by the vendor’s app or exchange.

Confirm that the vendor controls the address on the destination chain and can access the asset there. An address may look identical across EVM networks, but a transfer to the wrong network can still be unusable. If the vendor must spend or forward the funds, check that they can also obtain the chain’s native gas token for transaction fees.

For example, if you owe 250 USDC and the vendor requests USDC on Arbitrum, check that the quote delivers that asset on Arbitrum—not a similarly named bridged token or USDC on another network. Treat the quoted “minimum received” as the amount to compare against the invoice, rather than relying only on the amount leaving your wallet.

How does the cross-chain payment get there?

A route typically combines a source-chain transaction with a transfer mechanism and, when needed, a swap into the destination asset. Think of it like sending a parcel through a carrier: the source transaction is the hand-off receipt, while delivery is confirmed only when the correct package reaches the recipient. Ethereum.org describes common bridge designs such as locking and minting assets, burning and minting, and atomic swaps.

Some routes use intents: you specify the outcome you want, and a relayer may deliver the destination funds before the source-side transaction is fully settled. Across documentation describes this lifecycle as initiation, fill, and settlement. The relayer’s advance can make delivery faster, while the protocol later verifies the fill and settles with the relayer. Other routes wait for source-chain confirmation and then complete the destination transfer.

Costs can include source-chain gas, a route or service charge, and a swap spread; which charges are paid separately or deducted varies by route. Compare the final destination amount and expected time for the same source amount. If the vendor needs an exact invoice amount, leave room for price movement or choose a route whose stated minimum meets the invoice.

What should you check after sending?

Save the source transaction hash and check both sides: the source transaction succeeded, and the destination address received the expected token on the expected chain. A successful source transaction does not by itself prove delivery. If the destination transfer is delayed, check its status before sending again; a second payment can create a duplicate payout while the first route is still completing.

Use a cross-chain service such as Omnichain when you want one service to route the transfer or swap across supported chains. Before confirming any route, match the recipient’s network and token to the destination outcome, then make sure the net amount covers the invoice. For recurring payments, ask the vendor to confirm those details again if their receiving setup changes.

Can the vendor receive the token without native gas?

Usually, a wallet can receive tokens without holding the destination chain’s gas token. But the recipient may need native gas to transfer, swap, or use the funds afterward. If the vendor needs to act on the payment immediately, confirm how they will cover that fee before sending.

What if the source transaction succeeds but the payout is missing?

Keep the transaction hash and check the route’s status using the transaction details. Cross-chain completion can require separate source and destination steps, so wait for the route to resolve or identify a failure before retrying. If the vendor’s address or network was wrong, contact them to agree on the next action rather than sending a second payment to a guessed address.