> For the complete documentation index, see [llms.txt](https://oneclub-scripts.gitbook.io/oneclub-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oneclub-scripts.gitbook.io/oneclub-scripts-docs/free-script/oneclub-banking/dispatch-integration.md).

# Dispatch Integration

The dispatch system is now handled through **`oneclub_bridge` as a provider layer**, which allows compatibility with multiple dispatch scripts.

<pre class="language-lua"><code class="lang-lua">Dispatch = {
    enabled = true,
<strong>    provider = 'auto' -- 'auto' | 'cd' | 'ps' | 'qs' | 'none'
</strong>},
</code></pre>

#### **Currently supported providers**

* **cd\_dispatch**
* **ps-dispatch**
* **qs-dispatch**

<details>

<summary><strong>How you set your own Dispatch system ?</strong> </summary>

**1. Create a new provider file**

`oneclub_bridge/client/modules/dispatch/providers/my.lua`

**2. Register the provider**

Providers.my = {
\
resource = 'my\_dispatch',
\
send = function(payload)
\
\-- your dispatch event logic
\
end
\
}

**3. Add the file to `fxmanifest.lua` before**

`client/modules/dispatch/index.lua`

**4. Set the provider in configuration**

`Dispatch.provider = 'my'`

</details>