Update Payment System sale.paysystem.update
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
pay_systemWho can execute the method: CRM administrator (permission "Allow to modify settings")
This method updates the payment system.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
Identifier of the payment system |
|
|
FIELDS |
Object containing new field values (detailed description provided below) |
FIELDS Parameter
|
Name |
Description |
|
NAME |
Name of the payment system |
|
DESCRIPTION |
Description of the payment system |
|
PERSON_TYPE_ID |
Identifier of the payer type |
|
BX_REST_HANDLER |
Code of the REST handler specified when adding the handler using the sale.paysystem.handler.add method |
|
ACTIVE |
Indicator of the payment system's activity. Possible values:
|
|
LOGOTYPE |
Logo of the payment system (image in Base64 format) |
|
NEW_WINDOW |
Flag for the "Open in new window" setting. Possible values:
|
|
XML_ID |
External identifier of the payment system |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":12,"FIELDS":{"NAME":"New Payment System Name","DESCRIPTION":"New Payment System Description","PERSON_TYPE_ID":1,"BX_REST_HANDLER":"resthandlercode","ACTIVE":"Y","NEW_WINDOW":"N","LOGOTYPE":"/* base64 image */"}}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.paysystem.update
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"ID":12,"FIELDS":{"NAME":"New Payment System Name","DESCRIPTION":"New Payment System Description","PERSON_TYPE_ID":1,"BX_REST_HANDLER":"resthandlercode","ACTIVE":"Y","NEW_WINDOW":"N","LOGOTYPE":"/* base64 image */"},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sale.paysystem.update
try
{
const response = await $b24.callMethod(
'sale.paysystem.update',
{
"ID": 12,
"FIELDS": {
"NAME": "New Payment System Name",
"DESCRIPTION": "New Payment System Description",
"PERSON_TYPE_ID": 1,
"BX_REST_HANDLER": 'resthandlercode',
"ACTIVE": 'Y',
'NEW_WINDOW': 'N',
'LOGOTYPE': '/* base64 image */',
}
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'sale.paysystem.update',
[
'ID' => 12,
'FIELDS' => [
'NAME' => 'New Payment System Name',
'DESCRIPTION' => 'New Payment System Description',
'PERSON_TYPE_ID' => 1,
'BX_REST_HANDLER' => 'resthandlercode',
'ACTIVE' => 'Y',
'NEW_WINDOW' => 'N',
'LOGOTYPE' => '/* base64 image */',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error updating payment system: ' . $e->getMessage();
}
BX24.callMethod('sale.paysystem.update',
{
"ID": 12,
"FIELDS": {
"NAME": "New Payment System Name",
"DESCRIPTION": "New Payment System Description",
"PERSON_TYPE_ID": 1,
"BX_REST_HANDLER": 'resthandlercode',
"ACTIVE": 'Y',
'NEW_WINDOW': 'N',
'LOGOTYPE': '/* base64 image */',
}
},
function(result)
{
if(result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sale.paysystem.update',
[
'ID' => 12,
'FIELDS' => [
'NAME' => 'New Payment System Name',
'DESCRIPTION' => 'New Payment System Description',
'PERSON_TYPE_ID' => 1,
'BX_REST_HANDLER' => 'resthandlercode',
'ACTIVE' => 'Y',
'NEW_WINDOW' => 'N',
'LOGOTYPE' => '/* base64 image */',
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP Status: 200
{
"result": true,
"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 |
Result of the payment system update |
|
time |
Information about the request execution time |
Error Handling
HTTP Status: 400, 403
{
"error": "ERROR_HANDLER_NOT_FOUND",
"error_description": "Handler 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 |
|
|
Access denied. The application is trying to modify a payment system added by another application, or insufficient rights to modify the payment system |
403 |
|
|
The handler specified in the |
400 |
|
|
The payer type specified in the |
400 |
|
|
The payment system with the specified |
400 |
|
|
The |
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
- Get a List of Payment Systems sale.paysystem.list
- Get Payment System Settings sale.paysystem.settings.get
- 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