Payment strategies

Payment strategies are used to configure parameters that allow users to create requests for Withdrawals or Deposits. Each strategy has one currency and one operation type, so separate payment strategies are created for deposits and withdrawals, as well as for each currency. Existing payment strategies are displayed in the table:

The table displays all fields that were filled in when creating the strategy. Strategies can be filtered by type (All, Deposit, Withdrawal), Payment account, Currency and Payment system.

Any existing strategy in the table can be modified by clicking the Edit button in its row. The Currency, Strategy type, Payment account ID and Payment system cannot be changed after the strategy is created. When you click the Disable button, the strategy will no longer be displayed to clients. The strategy can be enabled again with the Enable button. Automation does not work for requests of a disabled strategy.

The Delete strategy button in the edit sidepage deletes the strategy without additional confirmation. After deletion, a strategy with the same parameters can be created again.

The Save as XLSX button allows you to download a list of all strategies available in the table.

Creating a payment strategy

The Add Strategy button opens a sidebar for creating a new payment strategy. The sidebar contains several blocks to fill:

In the upper block, you need to fill in the following fields:

Name - optional name of the payment strategy.

Description - if the Payment account is associated with a payment connector, then in this field you can specify a custom description for the strategy, which will be displayed to the end user. The description can be set for each language - the language is selected to the right of the Main info heading.

Currency - the currency that will be used by the user for deposits/withdrawals. Only one currency can be assigned to any payment strategy.

Strategy type - deposit or withdrawal.

Payment account ID - the account on which the payment system balance will be reflected. This field is configured with an account where the payment provider has set up integration. Specifying the account in this field allows you to automate the processes of crediting and debiting funds using a specific Payment strategy. The same payment account can be specified in several strategies.

Payment system - indicates through which payment systems deposits/withdrawals of the currency for which the Payment strategy is being created can be carried out.

The following payment systems are available on the platform:

• SEPA
• SWIFT
• CBRF

Please note! A broker can have only one strategy with the same Currency, Strategy type, Payment account ID and Payment system, including disabled strategies.

The Confirm deposit/withdrawal requests with 2FA option allows you to enable 2FA code confirmation for deposits and withdrawals for the strategy.

The Create document on submit block allows you to attach a template from the Documents section, which will be displayed to the client when creating a deposit/withdrawal request:

Note! To attach a document, you must first select its locale (language).

When creating a request, the generated document is saved in the client's request table and in the Deposit and withdrawal requests section of the admin terminal.

When creating a request through a connector, the document is generated without user involvement.

In the Commission field, a fixed commission is set, which will be charged to the user for deposit or withdrawal operations with a specific asset.

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

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 lifetime of the obtained dynamic commission value, after which the user will not be able to complete the Withdrawal request. The user will need to create a new request to obtain a new dynamic commission value.

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

Rounding method - the method used for rounding commissions:

• Round up - rounds toward the greater number. For example: 4.2 ➝ 5
• Round down - rounds toward the lesser number. For example: 4.2 ➝ 4
• Round toward zero - rounds toward zero. For example: 4.9 ➝ 4
• Round away from zero - rounds away from zero. For example: 4.1 ➝ 5
• Round to nearest greater - rounds to the nearest whole number greater than the original. For example: -4.1 ➝ -4
• Round to nearest lesser - rounds to the nearest whole number lesser than the original. For example: -4.1 ➝ -5
• Round to nearest even - for numbers ending in .5, rounds to the nearest even number. For other numbers, the nearest whole number is selected.
• No rounding required - in this case, the netting scale of a specific asset is applied.

When you enable the Cover external fee checkbox, the commission on withdrawals is charged to the broker instead of the client.

In the automation block, you can set up automatic transition of requests through the processing stages. For each stage - Accept, Process and Execution - the block has a separate group of settings:

• Enabled - enables automatic transition at this stage;
• Max amount - if the request amount is equal to or exceeds the limit, the automatic transition is not performed and the request waits for manual processing;
• Max day amount - the automatic transition is performed only if the total amount of the strategy's requests for the current day (UTC) together with the current request is less than the limit.

Please note! The value 0 in the limit fields means no limit. The settings work the same way for deposit and withdrawal strategies.

The sequence of processing a deposit/withdrawal request and assigning statuses is as follows:

1. The client creates a request, which appears in the Deposit and withdrawal requests section with the status New.
2. The broker moves the request to the status Accepted, thereby blocking the client's funds until the request is executed and informing the client that the request has been accepted for processing to carry out necessary checks (e.g., account details and payment amount).
   • This transition occurs automatically if the Enabled toggle is on in the Accept group.
3. After the checks are completed, the broker can move the request to the status Processing and send the payment to an external payment system. The client's status also changes, indicating that the actual payment is expected from the external system at this stage.
4. Upon completion of verification in the external system and confirmation by the broker of the actual receipt of funds in the account, the request is moved to the status Processed.
   • This transition occurs automatically upon receiving payment confirmation from the provider, if the Enabled toggle is on in the Process group.
5. After verifying the actual receipt of the payment on their side, the broker moves the client's request to one of the final statuses - Completed (to create a transaction on the platform and replenish the client's account) or Rejected.
   • If the Enabled toggle is on in the Execution group, status assignment will be skipped, and the transaction will be created after the Processing stage of the request.

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

Policies

In the policies block, you can use the Add policy button to set payment methods that will be available for specified residency and/or citizenship of user profiles:

Important! - To display payment method details to clients, it must be specified in this block. - If no citizenship or residency is specified for a payment method, it will be displayed to all clients who have access to the strategy. - If policies are set but none of them matches the client's profile by residency and citizenship, the strategy is not displayed to this client.

The Payment methods list includes only broker payment methods in the Accepted status whose currency and payment system match those of the strategy. The same payment method can be specified in several strategies - both for deposits and withdrawals.

The policies block is optional. A strategy without policies is available to all clients, and requests can be created under it without selecting a broker payment method. If a deposit strategy has no broker payment method and no connector is linked to the payment account, the client will see a message that there are no account details for the selected currency and payment system when creating a request, but will still be able to submit it.

Payment purpose

Please note! This block is editable only for Deposit strategies.

This block allows to customize the data set that will be displayed in the Payment purpose field of deposit requests made by the client from the trading terminal.

In the text field, you can enter a custom description of the payment purpose and also add a number of fields from certain system sections. When you paste one of the Codes displayed in the list into the text field, the data from the corresponding field will be displayed in the description.

• Account info: Account id adds the client's trading account number from which they made the deposit request to the request;
• Profile details: This block contains fields with data from the client's profile;
• KYC data: This block contains fields created in the KYC section.

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