Pay an Invoice on the Recipient’s Chain

Two chains are involved when you pay an invoice across networks: the one holding your funds and the one named by the recipient. You need the payment to arrive as a usable token on that destination chain, not merely to leave your wallet.

A cross-chain payment usually has a source transaction that deposits or transfers funds and a destination step that delivers tokens to the recipient. A bridge coordinates those steps, but the recipient’s invoice determines which network and asset count as payment.

What details should you get from the invoice?

An invoice should tell you which chain to pay on, which token to send, and where to send it. If any of those details are missing, ask the recipient before moving funds.

Check the network name and, where available, its chain identifier. Wallets may list networks with similar names, while a token with the same ticker can have different contract addresses on different chains.

Confirm whether the recipient expects the native asset or a token. “USDC,” for example, can refer to distinct token contracts on different networks; matching the ticker alone does not confirm that you have the requested asset.

• The destination network, including its exact name or chain identifier.
• The token and, if supplied, its contract address on that network.
• The recipient’s wallet address on the destination network.
• The amount due, the accepted fee treatment, and any payment deadline.

Ask whether the invoice amount is the amount the recipient must receive or the amount you should send. A bridge fee or token swap can reduce the delivered amount, so a quote showing estimated output matters when the recipient expects an exact sum.

If a bridge says the token needs approval, that step gives a particular contract permission to spend tokens from your wallet. For the specific approval flow, see steps for missing AcrossBridge token approval; the approval applies on the chain where you hold the token.

How do you move funds to the recipient’s chain?

You move funds by choosing a route from the chain where your balance sits to the chain named on the invoice. A bridge may deliver the same token on the destination chain, or let you choose a different supported token there.

The route’s quote should make clear what you send, what you are expected to receive, and which fees apply. Check the destination token and estimated amount against the invoice before you approve or submit anything.

1. Open a bridge or wallet flow that supports both the source and destination networks, then select those networks explicitly.
2. Choose the source token and amount, and set the recipient’s destination address if the flow allows a separate recipient.
3. Review the quoted destination token, delivered amount, fees, and any minimum or expiry conditions.
4. Check the transaction details in your wallet, approve the token if required, and submit the source transaction.
5. Wait for the route to complete, then verify the destination transaction and the recipient’s balance or payment confirmation.

The source transaction may finish before the recipient has funds on the other chain. Bridge routes differ in how they deliver and settle transfers, so use the status shown by the route and verify arrival on the destination network before treating the invoice as paid.

What should you check before calling it paid?

Confirm that the recipient received the right token at the right address on the right chain. A successful source transaction only proves that the first step was submitted or completed; it does not, by itself, prove that the invoice was paid.

Keep the source transaction hash and the destination transaction hash if the route provides one. The hashes let you trace the transfer on the relevant chain explorers and give the recipient useful details if their payment system has not updated.

There are trade-offs in how you fund the destination. Bridging the same token can avoid an extra swap, while choosing a different destination token may fit the invoice better but adds another conversion and its price impact or fee.

You also need to account for gas, the network fee paid to process a transaction. The source wallet needs enough of its chain’s gas asset to submit the transfer; depending on the route, the destination wallet may also need gas to move or use the received tokens later.

For most invoice payments, follow the recipient’s stated chain and token exactly, and prefer a route that shows a clear destination amount before you commit. If the quote would deliver less than the amount due, adjust the send amount or ask the recipient how fees should be handled.