# Trade request acceptance mechanics

Unigox is using a cascading multi-vendor auction model to match buyers and sellers instead of a typical marketplace listing model.

When a user wants to sell 50 USDT, they send a trade request. Unigox sorts by the best price for the user and sends a trade request to vendor A, who has the best price for the user. This trade request is exclusive to vendor A for 45 seconds.

If vendor #1 does not accept the trade request, the same trade request is sent to vendor B, who has the next best price for the user.

Now, both vendor #1 and vendor B can accept this trade request.

If vendor B did not accept trade request within 45 seconds, if there is another vendor C that matches user criteria, trade request is sent to vendor C, and now all 3 vendors can accept trade request. See visualization.

| Timeline (mm:ss) | Unigox system                                                                  | Vendor action                   |
| ---------------- | ------------------------------------------------------------------------------ | ------------------------------- |
| 00:00            | Trade request sent to Vendor A (45-second timer)                               | Vendor A ignores                |
| 00:45            | Trade request sent to Vendor B (Vendor A can still accept trade request)       | Vendor B ignores                |
| 01:30            | Trade request sent to Vedor C (Vendors A and B can still accept trade request) |                                 |
| 01:50            | First vendor to accept wins                                                    | Vendor A accepts trade request. |

{% columns fullWidth="true" %}
{% column width="33.33333333333333%" %}

<div data-full-width="true"><figure><img src="/files/beb83JKDSrRhsTtvvNBE" alt=""><figcaption><p>What you initially see as Vendor A</p></figcaption></figure></div>
{% endcolumn %}

{% column width="33.33333333333333%" %}

<figure><img src="/files/PlU7awtYCwEUBJobmRlC" alt=""><figcaption><p>What you see as vendor A when you missed first 45 seconds window and vendor B got trade request as well</p></figcaption></figure>
{% endcolumn %}

{% column %}

<figure><img src="/files/VBi3CFhqR49zeQwy5R2y" alt=""><figcaption><p>What you see as vendor B</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

## Penalty for not accepting trade request

In case you are Vendor A, and if Vendor B or any subsequent vendor accepts trade request, you get 1 penalty point.

3 penalty points total turns your offers inactive until you turn them on again.

This keeps only active vendors on marketplace who are present and ready to process trade requests.

In case you are Vendor C who received trade request and Vendor B or Vendor A accepted trade request, you do not receive a penalty point.


---

# Agent Instructions: 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:

```
GET https://guide.unigox.com/user-guides/trade-as-vendor/trade-request-acceptance-mechanics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
