> For the complete documentation index, see [llms.txt](https://reference-guide.gitbook.io/crm-version-release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reference-guide.gitbook.io/crm-version-release-notes/v7.59.0-stronger-withdrawal-control-and-visibility.md).

# V7.59.0 – Stronger Withdrawal Control & Visibility

*<mark style="color:$info;">Learn about all the details of all our recent CRM updates here.</mark>*

**Released Date - 15 November 2025**&#x20;

This release introduces new controls and visibility enhancements across the withdrawal workflow. Brokers can automate approval for selected PSP withdrawal requests, receive alerts when clients submit new withdrawal information for review, and reverse previously approved withdrawals when required.&#x20;

Clients also benefit from clearer visibility of withdrawal details within their request history, supporting more accurate reconciliation and a smoother overall withdrawal experience.

### <mark style="color:red;">Key Function Highlights</mark>

1. [**Auto-Approval Controls for Withdrawals**](#id-1-auto-approval-controls-for-withdrawals)**:** Brokers can now enable automatic approval for withdrawal requests processed via Payment Service Providers (PSPs). Available controls include eligible client groups, exclusion of specific clients, approval amount thresholds, and limits on the number of auto-approved withdrawals per client each day. This helps reduce manual processing while maintaining appropriate risk management and operational oversight.
2. [**Post-Approval Rejection with Automatic Refund**](#id-2-post-approval-rejection-with-automatic-refund)**:** Approved withdrawal requests can now be rejected when necessary, such as when payout details are incorrect, transfers are returned by the payment provider, or clients request a cancellation to update the withdrawal destination. Once rejected, the deducted amount is automatically refunded to the client’s trading account, ensuring accurate reconciliation and alignment of CRM records with the actual transaction outcome.
3. [**Back-Office Alerts for "Withdrawal Information" Requests**](#id-3-back-office-alerts-for-withdrawal-information-requests)**:** Brokers will now receive a notification when clients submit new withdrawal information for approval. This includes newly added bank account or wallet details. The enhancement improves operational awareness and supports timely review of payout information in line with internal verification procedures and third-party account restrictions.
4. [**Complete Withdrawal Details in Request History**](#id-4-complete-withdrawal-details-in-request-history)**:** Clients can now view the full withdrawal information submitted with each request directly from their request history, including bank account or wallet details. Previously visible only in "Pending" status, this information now remains accessible across all statuses, making past requests easier to review and improving transparency.

### <mark style="color:red;">1)</mark>   <mark style="color:red;"></mark><mark style="color:red;">**Auto-Approval Controls for Withdrawals**</mark>

You can now enable automatic approval for withdrawal requests processed via Payment Service Providers (PSPs). Available controls include eligible client groups, exclusion of specific clients, approval amount thresholds, and limits on the number of auto-approved withdrawals per client each day. This helps reduce manual processing while maintaining appropriate risk management and operational oversight.

To do so, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Configure Approval Settings

1. Navigate to "**Settings**" > "**Approval Settings**".&#x20;
2. Click the "**Edit**" icon. <br>

   <figure><img src="/files/IYWRI4bLMAaXCAAczVwP" alt=""><figcaption></figcaption></figure>
3. Under the Withdrawal section, select "**Automatic Approval**".&#x20;
4. An important notice will be displayed, advising that when automatic approval is enabled, only one Webhook trigger should be configured for withdrawals. Configuring multiple triggers may result in duplicate Webhook calls and could lead to duplicate payments.<br>

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

{% endstep %}

{% step %}

#### Configure Automatic Approval Criteria

1. Once automatic approval is enabled, you can define the specific conditions under which withdrawal requests will be auto-approved.
2. Define Eligible Client Groups
   1. Select the **client group(s)** eligible for automatic withdrawal approvals.
   2. You may configure different rule sets for different client groups.
   3. Click the "**Add**" button to create a new configuration for another client group.<br>

      <figure><img src="/files/p4qzaeeq0XAvaUiY9nEg" alt=""><figcaption></figcaption></figure>
   4. Each client group can only be configured once and cannot be selected again in another rule set.
   5. Selecting "**All Client Groups**" applies the configuration universally, except for any groups that have their own specific settings.
   6. To remove an existing configuration, click the "**Delete**" icon. <br>

      <figure><img src="/files/GLoh6M41NQQIbgQl89TZ" alt=""><figcaption></figcaption></figure>
3. Exclude Specific Clients
   1. Within each client group configuration, you can specify excluded clients.
   2. Excluded clients will not be eligible for automatic approval, even if they belong to an eligible client group.
   3. Multiple clients can be selected for exclusion.<br>

      <figure><img src="/files/oHYdykqWn6BeZFu1j58l" alt=""><figcaption></figcaption></figure>
4. Set Auto-Approval Amount Thresholds
   1. Define an auto-approval threshold for each currency.
   2. Withdrawal requests with amounts less than or equal to the specified threshold will be automatically approved.
   3. Requests exceeding the threshold will require manual review.
   4. Setting the threshold to 0 disables automatic approval for that currency, meaning all requests will require manual approval.<br>

      <figure><img src="/files/V1XLh22wDf95WAelSxLa" alt=""><figcaption></figcaption></figure>
5. Configure Daily Auto-Approval Limit per User
   1. Specify the maximum number of withdrawal requests that can be automatically approved per client per day.
   2. Once this limit is reached, any subsequent withdrawal requests on the same day will require manual review, regardless of the withdrawal amount.<br>

      <figure><img src="/files/tjOM8ZHenCVT0DHKUYKl" alt=""><figcaption></figcaption></figure>
6. After completing the setup, click the "**Save**" icon to apply the configuration.<br>

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

{% endstep %}

{% step %}

#### Application

1. After configuring automatic withdrawal settings, withdrawal requests submitted via PSP that meet the defined criteria (such as amount within the threshold) will be automatically approved.<br>

   <figure><img src="/files/o5CGj27zGn1FJuOv4cny" alt=""><figcaption></figcaption></figure>
2. Once the daily auto-approval limit per client is reached, any additional withdrawal requests will require manual review.<br>

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

{% endstep %}
{% endstepper %}

### <mark style="color:red;">2)</mark>   <mark style="color:red;"></mark><mark style="color:red;">**Post-Approval Rejection with Automatic Refund**</mark>

Approved withdrawal requests can now be rejected when necessary, such as when payout details are incorrect, transfers are returned by the payment provider, or clients request a cancellation to update the withdrawal destination. Once rejected, the deducted amount is automatically refunded to the client’s trading account, ensuring accurate reconciliation and alignment of CRM records with the actual transaction outcome.

To reject an approved withdrawal request, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Locate the Withdrawal Request

1. Navigate to "**Approval**" > "**Withdrawals**" > "**All**".&#x20;
2. Locate the withdrawal request you wish to reject.
3. Click "**View**" to open the request details.<br>

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

{% endstep %}

{% step %}

#### Reject the Withdrawal Request

1. Click "**Reject**". <br>

   <figure><img src="/files/vjh8IghRAqBR0m7RXUKZ" alt=""><figcaption></figcaption></figure>
2. A confirmation pop-up will appear, informing you that the request status will be changed to "**Rejected**".&#x20;
3. Select whether to refund the deducted amount to the client’s original account (i.e. the account from which the withdrawal was deducted).
4. Click "**Confirm**" to proceed.\
   \
   ![](/files/yAYR52RHzpeM97LooqH1)<br>
5. Once confirmed, the request status will be updated to "**Rejected**" the CRM balance status will be updated to "**Not Withdrawn**", indicating that the deducted amount has been refunded to the client’s account, and the change will be recorded in the audit log for reference.

   <figure><img src="/files/I9eSfJYW5qkuc8KNfZGm" alt=""><figcaption></figcaption></figure>
6. If you choose not to refund the amount to the client’s account, the CRM balance status will remain "**Deducted**". <br>

   <figure><img src="/files/86CtDiJDfz8IYa7uiq2K" alt=""><figcaption></figcaption></figure>

{% endstep %}
{% endstepper %}

### <mark style="color:red;">3)</mark>   <mark style="color:red;"></mark><mark style="color:red;">**Back-Office Alerts for "Withdrawal Information" Requests**</mark>

You will now receive a notification when clients submit new withdrawal information for approval. This includes newly added bank account or wallet details. The enhancement improves operational awareness and supports timely review of payout information in line with internal verification procedures and third-party account restrictions.

{% hint style="info" %}
This feature applies only if "**Withdrawal Information Approval**" is enabled for the client group. When enabled, any new withdrawal information submitted by clients will require approval.
{% endhint %}

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

To configure the notification, follow these steps:&#x20;

{% stepper %}
{% step %}

#### Configure Notification Settings

1. Navigate to "**Settings**" > "**Notification Settings**" > "**Admin Notification**".
2. Locate "**New** **Withdrawal Information**" and click the "**Edit**" icon.<br>

   <figure><img src="/files/OTZAfN24gkApx2sUNRQy" alt=""><figcaption></figcaption></figure>
3. Select the notification recipients:
   1. Choose specific admin accounts, or
   2. Select by role from the dropdown menu.\
      \
      ![](/files/5SkzS5jnuEk6kYI3TIjX)<br>
4. Choose the notification type: Email, Pop-up Notification, or Both
5. Click "**Save**" to apply the settings.\
   \
   ![](/files/lLbTsVqTvm1t6as4Ohns)<br>
   {% endstep %}

{% step %}

#### Application

When a client submits a new Withdrawal Information request, the configured recipients will receive a notification via the selected channels (email and/or pop-up notification).
{% endstep %}
{% endstepper %}

### <mark style="color:red;">**4)   Complete Withdrawal Details in Request History**</mark>

Clients can now view the full withdrawal information submitted with each request directly from their request history, including bank account or wallet details. Previously visible only in "Pending" status, this information now remains accessible across all statuses, making past requests easier to review and improving transparency.

To view the withdrawal details:&#x20;

1. Navigate to "**Funds**" > "**Request History**". <br>

   <figure><img src="/files/NDlAxue2dCnFCMzEP9sC" alt=""><figcaption></figcaption></figure>
2. Under "**Withdrawals**", click the "**Details**" button for the selected request.<br>

   <figure><img src="/files/LT3fFMO4H5yMEnoIv0oT" alt=""><figcaption></figcaption></figure>
3. The full withdrawal details will be displayed.<br>

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


---

# 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://reference-guide.gitbook.io/crm-version-release-notes/v7.59.0-stronger-withdrawal-control-and-visibility.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.