> For the complete documentation index, see [llms.txt](https://docs.whales.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whales.market/pre-market/cross-chain-settlement/seller-settlement-flow.md).

# Seller Settlement Flow

### Before Settlement

* The seller owns tokens on the TGE Chain
* The order exists on the Listing Chain
* No tokens have been moved yet

### Initiating Settlement

When the seller clicks the Settle button, the system checks:

* The exact token amount required for this order
* Whether sufficient wrapped tokens already exist on the Listing Chain

<figure><img src="/files/EB5L6SKvPkhuzakcqmiL" alt="" width="381"><figcaption></figcaption></figure>

If the balance is insufficient, a bridge step is required.

### Bridging Tokens

The interface will display:

* The exact amount required to settle the order
* The bridge direction (TGE Chain to Listing Chain)

<figure><img src="/files/kBdgs0Os2Ve1v17wBGz7" alt="" width="369"><figcaption></figcaption></figure>

The seller must:

1. Switch the Network to the TGE Chain

<figure><img src="/files/PhdZOSlvNJZTGWpSDNce" alt="" width="361"><figcaption></figcaption></figure>

2. Approve and sign the bridge transaction

<figure><img src="/files/afyUE3CWhi7DlcD9JrJ2" alt="" width="306"><figcaption></figcaption></figure>

3. Wait for LayerZero confirmation, then click on Settle

**Note: The bridge process may take several minutes depending on LayerZero network conditions.**

<figure><img src="/files/cdiueZwRwmuBvkQ2LDYp" alt="" width="467"><figcaption></figcaption></figure>

### After Bridging

Once the bridge is confirmed:

* Wrapped tokens are minted on the Listing Chain
* Minted amount equals the bridged amount
* Tokens are backed **1:1** by locked assets on the TGE Chain

The original tokens:

* Are locked in a smart contract
* Remain owned by the seller
* Cannot be reused or withdrawn

### Completing Settlement

After sufficient wrapped balance exists:

* The seller click on settle and signs the settlement transaction

<figure><img src="/files/lm8w1E5jTaO4PeOfz61r" alt="" width="316"><figcaption></figcaption></figure>

* Assets are transferred according to contract rules
* Payment is released to the seller
* The order status updates to Settled

***

### FAQs

<details>

<summary>When does a seller need to bridge tokens during settlement?</summary>

A bridge step is required if the system detects an insufficient balance of wrapped tokens on the Listing Chain to fulfill the specific order amount.

</details>

<details>

<summary>What actions must a seller take on the TGE Chain to initiate bridging?</summary>

The seller must switch their network to the TGE Chain, then approve and sign the bridge transaction as displayed in the interface.

</details>

<details>

<summary>How long does the bridging process typically take?</summary>

The bridge process may take several minutes, as it depends on the current network conditions of the LayerZero protocol.

</details>

<details>

<summary>What happens to the seller's original tokens after bridging?</summary>

The original tokens are locked in a smart contract on the TGE Chain; they remain owned by the seller but cannot be reused or withdrawn once the bridge is confirmed.

</details>

<details>

<summary>How is the settlement finalized after bridging is complete?</summary>

Once sufficient wrapped balance exists, the seller clicks "Settle" and signs the transaction to release the payment and update the order status to "Settled".

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.whales.market/pre-market/cross-chain-settlement/seller-settlement-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.