Get Payment System Settings sale.paysystem.settings.get
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect the MCP server so the assistant can utilize the official REST documentation.
Scope:
pay_systemWho can execute the method: CRM administrator (permission "Allow to modify settings")
This method returns the settings of the payment system. The structure of the settings is defined when adding the payment system handler in the method sale.paysystem.handler.add under the CODES key of the SETTINGS parameter.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
Identifier of the payment system for which settings are to be retrieved |
|
|
PERSON_TYPE_ID* |
Identifier of the payer type for which settings are to be retrieved. To get default settings, pass |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":11,"PERSON_TYPE_ID":1}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.paysystem.settings.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":11,"PERSON_TYPE_ID":1,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sale.paysystem.settings.get
try
{
const response = await $b24.callMethod(
'sale.paysystem.settings.get',
{
'ID': 11,
'PERSON_TYPE_ID': 1,
}
);
const result = response.getData().result;
console.dir(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'sale.paysystem.settings.get',
[
'ID' => 11,
'PERSON_TYPE_ID' => 1,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting payment system settings: ' . $e->getMessage();
}
BX24.callMethod('sale.paysystem.settings.get', {
'ID': 11,
'PERSON_TYPE_ID': 1,
},
function(result)
{
if(result.error())
console.error(result.error());
else
{
console.dir(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sale.paysystem.settings.get',
[
'ID' => 11,
'PERSON_TYPE_ID' => 1
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": {
"REST_SERVICE_ID_IFRAME": "snum",
"REST_SERVICE_KEY_IFRAME": "skey",
"PS_WORK_MODE_IFRAME": "REGULAR"
},
"time": {
"start": 1712135335.026931,
"finish": 1712135335.407762,
"duration": 0.3808310031890869,
"processing": 0.0336611270904541,
"date_start": "2024-04-03T11:08:55+02:00",
"date_finish": "2024-04-03T11:08:55+02:00",
"operating_reset_at": 1705765533,
"operating": 3.3076241016387939
}
}
Returned Data
|
Name |
Description |
|
result |
Root element of the response. The keys of the object are the parameter codes specified when adding the handler via sale.paysystem.handler.add in the The values of the object are the parameter values:
|
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400, 403
{
"error": "ERROR_CHECK_FAILURE",
"error_description": "Pay system not found"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Description |
Status |
|
|
Insufficient permissions to read settings |
403 |
|
|
One of the required fields is not specified or the specified payment system is not found (details in the error description) |
400 |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Add REST Handler for Payment System sale.paysystem.handler.add
- Update REST Handler for Payment System sale.paysystem.handler.update
- Get a List of REST Handlers for the Payment System sale.paysystem.handler.list
- Delete the REST handler for the payment system sale.paysystem.handler.delete
- Add Payment System sale.paysystem.add
- Update Payment System sale.paysystem.update
- Get a List of Payment Systems sale.paysystem.list
- Update Payment System Settings sale.paysystem.settings.update
- Delete Payment System sale.paysystem.delete
- Pay for an Order via a Specific Payment System sale.paysystem.pay.payment
- Get Payment System Settings for a Specific Payment sale.paysystem.settings.payment.get