Settings

Each setting is documented in a consistent format: data type, scope, and path within the configuration JSON.

Scope defines where the setting lives in the configuration:

Scope	JSON path
gateways	`.gateways`
integration	`.gateways.integration_alias`

Example configuration structure:

{
  "RUB": {
    "gateways": {
      "pay": {
        "providers": [{ "gateway_alias": "gateway" }]
      },
      "payout": {
        "providers": [{ "gateway_alias": "gateway" }]
      }
    }
  },
  "gateways": {
    "gateway": {
      "api_token": "cf4c559d-40a9-4844-8741-1cd132767da1",
      "class": "brusnikapay",
      "webhook_token": "+MWRinGhkXlYEBtJCp2aC0xKylZBoNJsx+KV/X07KDA=",
      "masked_provider": true,
      "wrapped_to_json_response": true
    },
    "allow_host2host": true
  }
}

enable_change_final_status

boolean scope: integration

Path: .gateways.integration_alias.enable_change_final_status

Allows changing the final status of a payin operation if another callback is received.

enable_change_amount

boolean scope: integration

Path: .gateways.integration_alias.enable_change_amount

Allows changing the amount of a payin operation if another callback is received.

class

string scope: integration

Path: .gateways.integration_alias.class

Unique predefined name of the integration.

masked_provider

boolean scope: integration

Path: .gateways.integration_alias.masked_provider

Hides the provider name from the merchant during the merchant request flow.

Masking does not affect alias in the providers settings:

{
  "gateways": {
    "pay": {
      "providers": [
        {
          "paypal": "gateway"
        }
      ]
    },
    "payout": {
      "providers": [
        {
          "paypal": "gateway"
        }
      ]
    }
  }
  ...

In this case, the merchant receives the alias (paypal) in the initial response.

skip_processing_url

boolean scope: gateways

Path: .gateways.skip_processing_url

Allows the merchant to receive payin requisites without needing to follow the processingUrl.

Randomizer

This set of settings is designed for p2p payment operations and allows iterating over amount variants for the gateway. After receiving a rejection, the system generates amounts within the specified range and tries them one by one in random order — until the first success or until attempts run out. All attempts count as a single operation.

random_range

array[number, number] scope: integration

Path: .gateways.integration_alias.random_range

The range of additional amounts for payin retry attempts — [min, max] in kopecks.

random_retries

number scope: integration

Path: .gateways.integration_alias.random_retries

Maximum number of retry attempts. The actual number of attempts equals min(random_retries, number_of_steps_in_range).

random_step

number scope: integration

Path: .gateways.integration_alias.random_step

Step size between attempts in kopecks. Determines the list of possible amounts within random_range.