Get Payment System Settings for a Specific Invoice sale.paysystem.settings.invoice.get
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
pay_systemWho can execute the method: a user with permissions to create and edit CRM invoices (legacy version)
This method returns the payment system settings for a specific invoice (legacy version).
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
INVOICE_ID* |
Identifier of the legacy invoice. The service crm.invoice.* is used to retrieve information about invoices. |
|
PAY_SYSTEM_ID |
Identifier of the payment system |
|
BX_REST_HANDLER |
Symbolic identifier of the payment system handler |
You must provide either the PAY_SYSTEM_ID parameter or the BX_REST_HANDLER parameter:
- When providing
PAY_SYSTEM_ID, the payment system with the specified identifier is used. - When providing
BX_REST_HANDLER, the first found payment system with the specified handler is used.
If both parameters are provided, the PAY_SYSTEM_ID parameter takes precedence.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"INVOICE_ID":10,"PAY_SYSTEM_ID":11}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/sale.paysystem.settings.invoice.get
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"INVOICE_ID":10,"PAY_SYSTEM_ID":11,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/sale.paysystem.settings.invoice.get
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type PaySystemSettingsResult = Record<string, string>
try {
const response = await $b24.actions.v2.call.make<PaySystemSettingsResult>({
method: 'sale.paysystem.settings.invoice.get',
params: {
INVOICE_ID: 10,
PAY_SYSTEM_ID: 11,
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Pay system settings:', result)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function getInvoicePaySystemSettings() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v2.call.make({
method: 'sale.paysystem.settings.invoice.get',
params: {
INVOICE_ID: 10,
PAY_SYSTEM_ID: 11,
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Pay system settings:', result)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', getInvoicePaySystemSettings)
</script>
try {
$response = $b24Service
->core
->call(
'sale.paysystem.settings.invoice.get',
[
'INVOICE_ID' => 10,
'PAY_SYSTEM_ID' => 11,
]
);
$result = $response
->getResponseData()
->getResult();
if ($result->error()) {
error_log($result->error());
} else {
echo 'Data: ' . print_r($result->data(), true);
}
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error getting invoice settings: ' . $e->getMessage();
}
BX24.callMethod('sale.paysystem.settings.invoice.get', {
"INVOICE_ID": 10,
"PAY_SYSTEM_ID": 11
},
function(result)
{
if(result.error())
{
console.error(result.error());
}
else
{
console.dir(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'sale.paysystem.settings.invoice.get',
[
'INVOICE_ID' => 10,
'PAY_SYSTEM_ID' => 11
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "sale.paysystem.settings.invoice.get", b24.Params{
"INVOICE_ID": 10,
"PAY_SYSTEM_ID": 11,
}, b24.WithIdempotent())
if err != nil {
return fmt.Errorf("sale.paysystem.settings.invoice.get: %w", err)
}
var item struct {
RestServiceIDIframe string `json:"REST_SERVICE_ID_IFRAME"`
RestServiceKeyIframe string `json:"REST_SERVICE_KEY_IFRAME"`
PsWorkModeIframe string `json:"PS_WORK_MODE_IFRAME"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.RestServiceIDIframe, item.RestServiceKeyIframe)
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 execution time of the request |
Error Handling
HTTP Status: 400, 403
{
"error": "ERROR_CHECK_FAILURE",
"error_description": "Pay system not found"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible Error Codes
|
Code |
Description |
Status |
|
|
Insufficient permissions to retrieve settings |
403 |
|
|
One of the required fields is not specified or the payment system with the specified |
400 |
|
|
The specified invoice was not found |
400 |
Statuses and System Error Codes
HTTP Status: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |