Payments in Universal CRM Objects: Overview of Methods
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.
The methods in this section work with payments associated with universal CRM objects. For example, you can create a payment for a deal, mark the receipt of funds, or generate a payment link for the client.
This is necessary to synchronize the status and parameters of payments in the CRM with external payment systems. Bitrix24 stores payment data separately from the main fields of the object but links them through identifiers.
Quick navigation: all methods
Linking Payments to Other Objects
CRM Object. To create and retrieve a list of payments, use the parameter pair entityTypeId and entityId. The first indicates the type of CRM object, while the second refers to a specific element of that type.
Payment Systems. The payment data returns paySystemId and paySystemName. You can access available payment systems using the sale.paysystem.list method.
Payment Line Items. Each payment can contain a set of line items. To manage the composition of the payment, use the methods in the section Line Items in Payment.
Delivery Items. A payment can be linked to delivery items. To work with them, use the methods in the section Deliveries in Payments.
How to Work with Payments in CRM
- Define the CRM object type
entityTypeIdand its identifierentityId. - Create a payment using the crm.item.payment.add method.
- If necessary, add products to the payment using the methods in the section Line Items in Payment or delivery services using the methods in the section Deliveries in Payments.
- Retrieve the list of payments for the object using the crm.item.payment.list method and select the desired payment by
id. - Get the details of a specific payment using the crm.item.payment.get method and update the data if necessary using the crm.item.payment.update method.
- Change the payment status using the crm.item.payment.pay or crm.item.payment.unpay methods.
- If a payment link for the client is needed, use salescenter.payment.getPublicUrl.
- If the payment is no longer needed, delete it using the crm.item.payment.delete method.
Limitations and Features
- For the
crm.item.payment.*methods, a correct pair ofentityTypeIdandentityIdfor the CRM object is required. - The methods crm.item.payment.product.* and crm.item.payment.delivery.* only work with an existing payment by
paymentId. - In list methods, apply
filterandorderin a format compatible with sale.payment.list. - The salescenter.payment.getPublicUrl method works in the
salescenterscope and is used only for generating a public link.
Overview of Methods
Scope:
crm,salescenterWho can execute the methods: depending on the method
Main Payment Methods
|
Method |
Description |
|
Creates a payment for a CRM object |
|
|
Modifies the set of payment fields |
|
|
Returns brief information about the payment |
|
|
Returns a list of payments for a specific CRM object |
|
|
Deletes a payment |
|
|
Changes the payment status to "Paid" |
|
|
Changes the payment status to "Unpaid" |
Public Payment Link
|
Method |
Description |
|
Generates a public payment link |
Line Items in Payment
|
Method |
Description |
|
Adds a line item to the payment |
|
|
Returns a list of line items in the payment |
|
|
Deletes a line item from the payment |
|
|
Changes the quantity of a product in the payment line item |
Deliveries in Payments
|
Method |
Description |
|
Adds a delivery item to the payment |
|
|
Returns a list of delivery items for a specific payment |
|
|
Deletes a delivery item from the payment |
|
|
Reassigns a delivery item to another delivery document |