> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/oss-dapps/backoffice/step-3-creating-an-escrow.md).

# Step 3: Creating an Escrow

{% embed url="<https://youtu.be/p7DZWAfewwc>" %}

**1. Navigate to the Escrows Section**

* Click on **"Escrows"** in the **sidebar**.
* This will take you to the **"Initiated Escrows"** tab.

<figure><img src="https://content.gitbook.com/content/T9oAW5k4YIU200ZnbO0x/blobs/QZttyg5yj8koXzAhnwJD/image.png" alt=""><figcaption></figcaption></figure>

* **Escrow tabs** are organized by **role** (Approver, Service Provider, Dispute Resolver, etc.).
  * If you don’t see any escrows, it means your wallet **hasn't been assigned a role yet**.

📌 **Tip:** If you want to understand roles in escrows, refer to the [Roles in Escrow Design section.](/trustless-work/v2-en/introduction/technology-overview/roles-in-trustless-work.md)

***

**2. Click "Create Escrow"**

* This starts the **Escrow Initialization Flow**.

<figure><img src="https://content.gitbook.com/content/T9oAW5k4YIU200ZnbO0x/blobs/n7cJjq79Axwq2pnhvMSW/image.png" alt=""><figcaption></figcaption></figure>

***

**3. Fill in Escrow Details**

To configure an escrow, you need to **define roles** and **key parameters**:

✅ **Title** → Name your escrow.\
✅ **Description** → A summary of the contract.\
✅ **Approver** → Who approves milestone completion.\
✅ **Service Provider** → The person/entity delivering the service/product.\
✅ **Engagement** → A unique ID (e.g., invoice, contract, project ID).\
✅ **Platform Address** → The platform receiving fees and modifying milestones.\
✅ **Amount** → The total amount locked in escrow.\
✅ **Release Signer** → The entity that releases funds.\
✅ **Dispute Resolver** → Handles disputes if needed.\
✅ **Milestones** → Conditions that must be completed & approved.

🔹 *Make sure you **know the wallet addresses** that will play each role before proceeding!*

➡️ **Click "Initialize Escrow" once all details are set.**

<figure><img src="https://content.gitbook.com/content/T9oAW5k4YIU200ZnbO0x/blobs/sZnhwZWpiXis5WSZ1cBC/image.png" alt=""><figcaption></figcaption></figure>

***

**4. Sign the Transaction**

* Your **wallet (Freighter, Albedo, etc.)** will prompt you to confirm and sign the transaction.
* This **deploys the escrow contract** on **Stellar Testnet**.
* Once signed, the escrow is now **active**.

<figure><img src="https://content.gitbook.com/content/T9oAW5k4YIU200ZnbO0x/blobs/LVyjR9i9j3IJt5d2FPyX/image.png" alt=""><figcaption></figcaption></figure>

***

**5. Escrow Successfully Initialized!**

* You will receive a **confirmation pop-up** with:
  * The **Escrow ID**.
  * A link to view the escrow on **Stellar Explorer**.

✅ Your escrow will now be **visible in the "Initiated Escrows" tab**!\
If you used the **same wallet for all roles**, it will appear across **all tabs**.

<figure><img src="https://content.gitbook.com/content/T9oAW5k4YIU200ZnbO0x/blobs/AfS5ohsSYbWqNrVdvAuZ/image.png" alt=""><figcaption></figcaption></figure>

#### **🚀 Next Steps:**

🔹 **Try creating another escrow with multiple addresses** by opening a **Testnet wallet in incognito mode!**\
🔹 **Proceed to the Funding Phase** – Learn how to deposit funds into your escrow.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlesswork.com/trustless-work/v2-en/oss-dapps/backoffice/step-3-creating-an-escrow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.