De bridge First Token Transfer and Receipt Checks

De bridge transfers begin with a compatible source wallet and a confirmed destination address, and finish with verified token receipt. Select the sending network, input token, destination network, and output token before reviewing the quote. Confirm the recipient and available gas, authorize the required spending if prompted, and submit the transfer once. Then match its order record to the destination transaction. Source confirmation alone does not establish delivery.

A first transfer is complete when its destination record confirms delivery of the requested token to the intended recipient.

Source Wallet and Destination Readiness

The source wallet must hold the selected input asset on the sending network and support signing the required transaction. A balance displayed on another network cannot fund that transaction. Check the connected account, network, and spendable balance together. On the receiving side, confirm that the destination address belongs to the intended recipient and works with the selected network. Matching token symbols do not establish matching token identities; inspect the selected asset details on each side.

Cancellation access also matters before submission. A deBridge Liquidity Network (DLN) order specifies a destination authority that can request cancellation while the order remains unfulfilled. For manual cancellation, confirm that you control this authority through a compatible wallet. Approved integrations with automatic cancellation enabled instead assign a deBridge-controlled authority. Confirm which arrangement applies before submitting; automatic cancellation is restricted to eligible market orders and does not apply to limit orders. The recipient and cancellation authority have different functions, even when they use the same address. An address that can receive tokens does not automatically give you the signing access needed for recovery.

Order Terms Before Any Signature

The quote describes what leaves the source account and what the recipient should receive on the destination network. An order records those transfer requirements on-chain. A solver supplies the requested destination assets when fulfilling it. If the selected route includes a swap before order creation, distinguish the token initially spent from the token committed to the order. These terms determine whether the route fits the transfer, and they remain editable before you authorize an on-chain action.

A Transfer Amount That Leaves Gas Available

The first transfer amount must fit both the token balance and the native currency needed for source transactions. An ERC-20 balance does not pay native network gas. When the input itself is native currency, committing the entire balance can leave insufficient funds for fees. Review the wallet’s transaction estimate alongside the transfer quote, including any separate approval transaction.

View image file

A smaller transfer limits the amount committed, but it still needs an executable quote. Operating expenses can make an input too small to produce a viable output. Route availability, liquidity, and costs can change while you review the transfer. Refresh an old estimate and inspect the revised total input and destination amount before signing. A previously displayed quote does not reserve those conditions.

Approval and Submission as Separate Commitments

The wallet prompt identifies the action being authorized. Token spending permission and order creation have different effects, even when they appear consecutively.

ERC-20 Spending Permission

The Approved Contract

An ERC-20 approval allows a specified contract to spend tokens within its allowance. Check the selected token and requested spender against the transaction being prepared. The spender may be a routing contract, so it is not necessarily the recipient address. Approval alone does not create the cross-chain order or deliver the output.

The Approved Amount

The allowance must cover the input required by the prepared transaction, including operating expenses when the quote adds them to that input. A refreshed estimate can require another approval if its total input exceeds the existing allowance. A larger allowance permits more spending by that contract; it does not increase the amount requested by this particular order.

Source Order Creation

The transfer transaction submits the order to the source network. Review its amount, destination details, and native currency requirement before confirming. Successful order creation locks the order’s input under the protocol’s fulfillment and cancellation rules. Treat submission as a commitment: rejecting an unsigned request remains simpler than recovering an order already created on-chain.

An approval already confirmed on-chain remains a separate action. Abandoning the transfer does not erase that permission or recover the approval’s gas cost.

Receipt Checks on Both Networks

The source transaction establishes whether the order was created successfully. Keep its transaction hash and order identifier so later checks refer to the same transfer. A pending source transaction has not yet established successful creation. A successful approval receipt establishes permission only. When inspecting the transfer record, confirm the source account and order details rather than treating every successful wallet transaction as a completed bridge.

For a plain DLN token transfer, destination fulfillment delivers the requested output to the order’s specified recipient. Inspect the linked destination transaction for the receiving network, recipient, token identity, and amount. The subsequent unlock process settles the solver’s claim on the source funds. That settlement can follow delivery. A wallet display that has not refreshed is not enough to overturn a confirmed destination record.

Available Actions at Each Commitment Point

The available action depends on what has already reached the blockchain. Use the existing transaction and order records to identify that boundary before signing again.

View image file

Missing Routes and Failed Source Transactions

An unavailable quote means there is no executable route offered for the selected inputs at that moment. Stop before approval or submission and reassess the selection. After a submission error, inspect the source transaction before trying again: a stalled interface does not prove on-chain failure. A reverted EVM transaction can consume gas without creating an order. Correct the identified balance, allowance, or transaction problem and obtain a fresh quote; do not duplicate a transaction whose outcome remains unresolved.

Cancellation Before Another Attempt

An unfulfilled order requires a different response from a failed source transaction because its input is already committed. A fulfilled DLN order cannot be cancelled. To cancel an eligible order manually, use its page in the deBridge Explorer and connect the designated destination authority on the destination network. Review that transaction’s required native currency and the permitted source refund address. A cancellation request still needs on-chain acceptance; the order may fulfill before that happens.

View image file

Accepted cancellation prevents later fulfillment and starts the cross-chain return of the locked input. If a swap occurred before order creation, the refund can be in the asset committed to the order rather than the token initially spent. A cancellation-in-progress status does not establish that the source refund has arrived. Inspect the refund record and the actual returned token balance before preparing a replacement transfer. That replacement needs its own quote and permissions. If manual cancellation is required but you cannot sign as the designated authority, or if the refund remains unresolved, stop rather than assuming another transfer will repair the first.

De bridge FAQs