> For the complete documentation index, see [llms.txt](https://lara-script.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lara-script.gitbook.io/docs/admin-panel-functionality/general/auto-withdrawals/oasis.md).

# Oasis

**Instructions for adding Oasis auto-payouts in the Lara Script admin panel**

The process of connecting Oasis auto-payouts is simple and takes 5–10 minutes. We present to you a step-by-step guide:

**Step 1: Prepare the data**

* Register an account on Oasis ([oasis-crypto.com](https://oasis-crypto.com))

<figure><img src="/files/b9bcb2b695972f8c9d8a9b19efdbbae2ae84d322" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="/files/f420eacdb348ec85d43c025660fd61f55bf134d1" alt="" width="375"><figcaption></figcaption></figure>

* After logging into your personal account, create an organization in the "Organizations" section

<figure><img src="/files/GlkZ8fXjZayyhIqvCHcv" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/s44dk31ZCiEkckFyipeX" alt=""><figcaption></figcaption></figure>

When filling in the field **Webhook URL** append /notification/oasis to the end of the link so that the link looks approximately like this - <https://demo.lara-script.com/notification/oasis>

* Next you need to create API keys for the organization you created earlier; this must be done in the "Organization API keys" section

<figure><img src="/files/z4XPFm50yhmWE5dly6gz" alt=""><figcaption></figcaption></figure>

When creating an organization API key you must be sure to set permissions for operation types including payout permission if you want to use auto-payouts with these keys

<figure><img src="/files/9z4NGEmeeOEZKhrLxMDx" alt="" width="563"><figcaption></figcaption></figure>

After creating the organization you will have wallets in the Wallets - Main wallets section where you can store funds for future auto-payouts

**Step 2: Go to the section in the admin panel**

* Log in to the Lara Script admin panel.
* Go to "General" > "Auto-payouts" > "Oasis".

<figure><img src="/files/9b7339bb5959e334e17e68e70683bab10f8b0cd2" alt=""><figcaption></figcaption></figure>

**Step 3: Fill in the fields**

Fill out the form in the admin panel. Here’s how to do it step by step:

* **API key:** Here you need to paste the Oasis organization API key (for example, KaxRJdnOla45IidRdR8jJjqO3YvWw3zAl) that you received in step 1 of this guide.
  * Tip: Check the key for errors - it should be unique and contain no spaces.

<figure><img src="/files/fhESZYzu4cx0LwNwlcK2" alt=""><figcaption></figcaption></figure>

* **Organization id:** Here you need to paste the unique Oasis organization ID (for example, oWmGJtHN8dD1TVjfx1gwQbd5fckghZtF) that you also received in step 1 of this guide.

<figure><img src="/files/SdAHEjFeohh4W7ZnS5JY" alt=""><figcaption></figcaption></figure>

**Example of filled fields:**

<figure><img src="/files/IRFZTpgi7LKl1RybT8tW" alt=""><figcaption></figcaption></figure>

**Step 4: Save and test**

* Click "Save" at the bottom of the form.
* In the "Payouts" field (on the create/edit direction page) click "Add row" and select the value "Oasis".

<figure><img src="/files/b009316da831441203766b2c321b12c92b6b72a8" alt=""><figcaption></figcaption></figure>

Set boundary values for the minimum and maximum exchange amount to trigger auto-payments; limits are configured for the "Giving" currency.

* Check the integration: Create a test request and pay it; verify whether statuses update automatically (New request - Awaiting confirmation - Paid - Awaiting confirmation from the auto-payouts module - Completed)
  * If the deposit is for an amount less/greater than specified in the request, that request will receive the status "Under review" and the funds will not be sent automatically. In that case you will need to make such a payment manually by clicking the "Start auto-payout" button and entering the manual payout code which you configure yourself in the section **Administrator settings** - **Confirmation code for manual payout**

<figure><img src="/files/nmftA0Aq71m1Xe3TMlQm" alt="" width="375"><figcaption></figcaption></figure>

**Step 5: USDT payout overspend safeguard**

Sometimes, during an auto payout, a situation may occur where more USDT is spent on the payout than was received in the incoming request (for example, due to a sharp exchange rate jump between networks). To avoid such cases, the Oasis settings include a block **“Payout overspend safeguard”** — a safeguard that checks the deviation before confirming the payout and, if necessary, blocks it.

**Block fields:**

* **Payout overspend safeguard** — \[ON]/\[OFF] switch.
  * **ON** — the safeguard is active: the system will check each payout for deviation and block it if the allowed thresholds are exceeded.
  * **OFF** — the check is disabled; payouts go through without deviation limits (as before).
* **Allowed payout deviation, %** — the maximum allowed excess of the USDT amount spent on the payout over the USDT amount in the request input, as a percentage of the input amount. The default value is **0.1%**.
* **Allowed payout deviation, USDT** — the maximum allowed excess in absolute USDT terms. The default value is **10 USDT**.

Both parameters work simultaneously: the safeguard triggers if the deviation exceeds **at least one** of the two thresholds (percentage **or** absolute value). If the actual deviation falls within both limits, the payout goes through as usual, with no delays.

**What happens when the safeguard triggers:**

* the payout is blocked until manual confirmation — the funds are not sent automatically;
* the request remains in the status **“Paid”** (does not move to “Completed”);
* a notification with conversion and deviation details arrives in Telegram, for example:

```
⚠️ #44798 Oasis auto payout stopped
15 Tether TRC20(USDT) -> 0.01949985 Ethereum ERC20(ETH)
USDT in: 15 | USDT out: 35.64
Deviation: 20.64 USDT (137.6%)
Oasis rate: 1827.3315268523906818
```

> To receive these notifications, the [Telegram notifications plugin](https://lara-script.gitbook.io/docs/admin-panel-functionality/plugins/telegram-notification) must be configured. If the plugin is not configured, the safeguard will still block suspicious payouts, but notifications will not be sent to Telegram.

After the safeguard triggers, the request must be handled manually — just as in the case of a deposit amount mismatch: click the **“Run auto payment”** and enter the manual withdrawal code (configured in the section **Administrator settings** — **Confirmation code for manual withdrawal**) or make the transfer manually and move the request to **Completed**.

**Important**

When sending a payout, the system automatically selects the smaller of the two precision values: the one supported by Oasis and the one specified in the destination settings.

* If Oasis supports 6 decimal places and 8 are specified in the destination, the payout will be sent with 6-digit precision.
* If Oasis supports 6 decimal places and 5 are specified in the destination, the payout will be sent with 5-digit precision.

This eliminates sending errors that could previously occur if the destination precision exceeded what Oasis allowed.