Payment strategies

Payment Strategies are used to configure parameters that allow users to create Withdrawal or Deposit requests. Existing payment strategies are displayed in the table:

The table displays all the fields that were filled in when creating the strategy.

Any existing strategy in the table can be modified by clicking the Edit button in the row containing it. Clicking the Disable button will disable the strategy's display to clients.

Creating payment strategy

The Add strategy button allows you to open a sidepage to create a new payment strategy. The sidepage contains several blocks to fill in:

In the upper block, the next fields should be filled:

Name - optional name of the payment strategy.

Currency, which will be used by the user for depositing/withdrawing funds. Only one currency can be assigned to any payment strategy.

Strategy type - deposit or withdrawal.

Payment account ID, which will display the balance of the payment system. This field is used to configure the account on which the integration with the payment service provider is configured. Specifying the account in this field allows you to automate the processes of crediting and debiting funds using a specific Payment Strategy.

The Commission field sets a fixed commission that will be charged to the user when making a deposit or withdrawal with a specific asset.

The Commission percent field allows you to charge a percentage of the commission instead of a fixed value.

Please note! In some cases, in addition to the fixed commission, a dynamic commission is added, which depends on the payment system.

Commission TTL The maximum duration of the dynamic commission value received, after expiry of which the user will not be able to complete the Withdrawal request. The user will need to generate a new request in order to receive a new value of Amount dynamic commission.

Netting scale - allows you to set the number to which the commission will be rounded.

Rounding mode - a mode that is used to round commissions:

• Round ceiling - rounds towards a larger number. For example: 4,2 ➝ 5
• Round floor - rounds toward a smaller number. For example: 4,2 ➝ 4
• Round down - rounds down toward zero. For example: 4.9 ➝ 4
• Round up - rounds upward - rounds away from zero. For example: 4.1 ➝ 5
• Round half up - rounds to the nearest modulo integer larger than the original number. For example: -4.1 ➝ -4
• Round half down - rounds to the nearest modulo integer smaller than the original number. For example: -4.1 ➝ -5
• Round half even - for a number ending in .5, rounds to the nearest even number. For other numbers, the nearest integer to which the rounding is performed is selected.
• Round unnecessary - in this case the netting scale of the specific asset is applied.

When the Cover external fee checkbox is enabled, the withdrawal fee is charged to the broker instead of the client.

Payment system indicates through which payment systems the deposit/withdrawal of the currency for which the Payment strategy is created can be made.

Several payment systems are available in the platform:

• SEPA
• SWIFT
• CBRF

In the automation block, the withdrawal limit for one payment (Max amount) and the daily withdrawal limit (Max day amount) for some stages of payment processing could be specified:

For payment strategies that involve automatization by a payment provider, you should specify an account that is integrated with the Payment provider.

The process for processing a deposit/withdrawal request and assigning it a status is as follows:

1. The client creates a request; the request appears in the Deposit and withdrawal requests section with the New status.
2. The broker changes the request to the Accepted status, thereby blocking the client's funds until the request is fulfilled and informing the client that the request has been accepted for processing for the necessary checks (e.g., payment details and amount).
   • This status is automatically activated when the Accept checkbox is checked.
3. After verification, the broker can change the request to the Processing status and forward the payment to the external payment system. The client's status also changes, indicating that the external system is currently awaiting actual payment.
4. Once confirmation in the external system is complete and the broker confirms that the funds have actually been credited to the account, the request is changed to the Processed status.
   • This status is automatically activated upon receipt of payment confirmation from the provider if the Process checkbox is checked.
5. After verifying the payment's actual receipt, the broker assigns the client's request to one of the final statuses: Executed (to create a transaction in the platform and fund the client's account) or Rejected.
   • If the Executed checkbox is checked, the status assignment will be skipped, and the transaction will be created after the Processing stage of the request is finished.

When any of the automation settings are enabled, the system automatically moves the payment to the next status if the previous statuses have already been completed.

More detailed status descriptions are provided in the Deposit and withdrawal requests section.

In the policies block, you can set the payment methods that will be available for the specified residencies and/or citizenships of user profiles:

Important! - For payment method details to be displayed to clients, it must be specified in the block. - If citizenship or residency is not specified for the payment method, it will be displayed to all clients who have access to the strategy.

To save changes and create a payment strategy, you must click the Create button.