Аккаунт в General iT
Войдите или создайте аккаунт для управления услугами в панели.
MODULE FOR 1C-BITRIX
Pavel Shulaev
This module integrates the CloudPayments payment gateway with 1C-Bitrix websites. It supports bank cards (Mir, Visa, MasterCard), Apple Pay, and Google Pay, enabling transactions in any currency and from any country. The solution operates both alongside the 'Online Store' module and independently on service pages, landing pages, booking forms, or Bitrix24 CRM forms.
This module integrates the CloudPayments payment gateway with 1C-Bitrix websites. It supports bank cards (Mir, Visa, MasterCard), Apple Pay, and Google Pay, enabling transactions in any currency and from any country. The solution operates both alongside the 'Online Store' module and independently on service pages, landing pages, booking forms, or Bitrix24 CRM forms.
The module enables payment collection without the 'Online Store' module. The payment button can be placed on any website page. Payment parameters such as amount, description, and transaction ID are configured directly within the component settings. This makes it suitable for Bitrix editions without an online store and for websites with non-standard sales models.
Payments can be processed directly within Bitrix24 CRM forms. The form collects data and immediately initiates the payment without redirecting to an intermediate page or requiring manual invoice generation. This is ideal for service bookings, reservations, and collecting prepayments.
The module supports generating invoices and sending payment links directly from the order card.
A manager opens an order, clicks one button, and sends the customer a payment link via e-mail, SMS, or Viber—either individually or through two channels simultaneously. When a new invoice is created, the previous one is automatically cancelled, preventing payment via an outdated link even if the customer found the old message.
Two-stage payment confirmation from the admin panel
In a two-stage scheme, funds are first blocked on the card and then charged after confirmation. The hold can be released via a button in the order card without accessing the CloudPayments personal account. Order statuses for authorized and confirmed payments are configured separately.
Built-in events for custom logic
JS events allow integration of analytics and e-commerce counters with actual payment steps. PHP events enable modification of the invoice composition, payment description, or intervention in bank response processing. All changes are made without editing the module code, ensuring that system updates do not overwrite custom modifications.
Failure notifications
The module monitors non-standard payment situations, such as unremoved holds, failed refunds, or rejected bank notifications. When such events occur, the system alerts the administrator via a free error notification module. Alerts are sent via email, SMS, or messengers. Urgent and non-critical events are configured separately, while similar errors are grouped.
A specific warning is issued if Check notifications are disabled in the CloudPayments account; without this feature, the store loses the ability to reconcile amounts and is unprotected against duplicate payments for a single order.
Support is provided directly by the module author rather than a general queue. The author analyzes non-standard scenarios, conflicts with other modules, and custom receipt logic. Necessary adjustments are made upon request, a capability not inherent in vendor-supplied modules.
Features:
Automatic payment flag setting
Orders are marked as paid based on bank notifications. The status to which an order is transitioned after payment is configurable. If the flag is not set automatically, check the "Process Automation" tab in the "Online Store" module and other third-party modules involved in order processing.
Refunds via standard Bitrix tools
Refunds are processed from the order card, with funds returned to the buyer's card. The order status after a refund is configurable.
54-FZ Compliant Receipts
Receipts are generated via CloudPayments online cash registers. The receipt structure can be modified via a PHP event, for example, by rearranging items or specifying a proprietary tax system.
Single and Two-Stage Payments
Both payment schemes are configured at the payment system level, with distinct order statuses assigned to each.
Payment Status Monitoring
The current payment status is visible in the admin panel without requiring a transition to the bank's personal account.
Multicurrency Support and Order Number Handling
Payments are accepted in any currency. Alphanumeric order numbers (e.g., 6B7R1 or 8CB2A59X8X) are processed correctly, addressing a common limitation in other integrations.
Interface and Behavior Configuration
The button linking to the payment gateway is customizable. Automatic redirection to payment upon order completion or from the buyer's personal account can be enabled (this may not function in custom order forms). Payment descriptions are generated using templates with placeholders.
English Localization
The module is fully translated into English.
You can verify the module's functionality on the demo site. Visit demo.rover-it.me, add a product to the cart, and at checkout select the payment method «CloudPayments (popup widget)» or «CloudPayments (payment by link)».
Use the following card details for testing:
Card number: 4242 4242 4242 4242
Expiration date: any valid date
CVC: any value
Cardholder name: any name
The demo site operates in test mode, so no real funds will be charged.
Detailed installation and configuration instructions are available on the «Installation» tab.
If “CloudPayments Internet Acquiring Payment Acceptance” is required, General iT can help with installation, configuration and a technical check after integration.
UPDATE HISTORY
Sending payment links from the order card. The manager creates an invoice with one click and sends the payment link to the customer via e-mail, SMS, or Viber — separately or using two methods at once.
Payment confirmation for the two-stage scheme. Releasing held funds directly from the order without navigating to the CloudPayments personal account.
Protection against duplicate payments. When a new invoice is created, the previous one is automatically cancelled — the old link cannot be used for payment.
Failure notifications. Messages about issues with funds and receipts via the free rover.notifier module, with separate settings for urgent and non-critical events. We also separately warn if Check notifications are disabled in the CloudPayments account — without them, the store remains without amount verification and protection against duplicate payments.
Installation is now cleaner. Order statuses already defined on the site are not offered for re-creation; the module installs and uninstalls correctly without the "Online Store" module, and you can immediately proceed to settings after installation.
Discovered vulnerabilities have been fixed, security has been enhanced
Enhanced protection for processing notifications from the CloudPayments payment system: the authenticity of each request is now verified during payment, confirmation, refund, and cancellation.
Identified security vulnerabilities in the module have been fixed.
Fixed an error that prevented disabling the automatic opening of the payment widget in settings.
Fixed the "Link already sent" error that occurred when refreshing the payment page.
Improved compatibility with PHP 8.2.
Updated the module icon.
— New VAT values added: 22% and 122/22
— Translation to English completed
— New languages added for the payment widget component: Italian and Uzbek
— Fixed installation errors
— Logging added. It can be enabled in the module settings
— English language support expanded
— Minimum PHP version increased to 7.4
— Added the ability to select the field to be used as the order identifier with CloudPayments
— added the ability to specify the place of payment when printing receipts
— for the components "CloudPayments Payment Form (by Order ID)" and "CloudPayments Payment Form (by Payment ID)", added the ability to manually set the text before the payment button, as well as automatic widget opening
— added 2 components for payment:
CloudPayments Payment Form (by Payment ID). A payment must be created and its identifier or object passed to the form components.
CloudPayments Payment Form (by Order ID). The payment is searched among the order payments. If the payment is not found, automatic creation can be configured.
The components are available in the visual editor at "Rover Components" > "CloudPayments Internet Acquiring Payment Acceptance", and can be placed anywhere on the site. They work only with the "Online Store" module.
— added support for Italian and Uzbek languages
— refactoring
— improved compatibility with PHP 8
— if VAT = 0, then "no VAT" will be displayed in the receipt
— fixed errors when working with CRM forms in Bitrix24
— restored receipt sending when paying by link
— other minor fixes and improvements
— Automation of refunds and payment cancellations upon payment deletion, order cancellation, and order status transition to the corresponding status is DISABLED, as this is a potentially dangerous operation. Cancellation/refund is now available only from the administrative section of the order and the CloudPayments account
— administrative-reference section updated
— added sending of an advance receipt upon fund freezing (two-stage payment)
— added sending of a refund receipt upon refunding funds to the customer
— fixed an error where a receipt was sometimes not sent during payment (one-stage payment)
— other found errors fixed
— fixed errors related to the expired demo mode
— other found errors fixed
— added the ability to pay via a link. After clicking the "Pay" button on the website, the user is redirected to the CloudPayments website to complete the payment, after which they are returned to the store.
— for all payment methods, settings have been added: "Link to Offer", "Send email with payment link", "Send SMS with payment link", and "Send Viber message with payment link".
— for the widget, settings have been added: "Display "Retry Payment" button on failed payment" and "Require user email address in the widget".
— JavaScript events have been added to the standard template for payments via the widget on the website: onRoverCloudPaymentsSuccess - action on successful payment, onRoverCloudPaymentsFail - action on failed payment, and onRoverCloudPaymentsComplete - always called, can be used for Google Analytics, Facebook, etc. See the module course for more details.
— PHP events onBeforePrepareRoverCPPayFormParams and onAfterPrepareRoverCPPayFormParams have been added, allowing modification of the payment button initialization parameters.
— the onAfterBuildReceipt event has been added, allowing modification of the receipt content.
— the standard template now includes a notification that a two-stage payment method is being used.
— fixed currency display with HTML tags.
— added sending of an updated receipt upon confirmation of two-stage payment
— restored transmission of the calculation item indicator in the receipt
— for delivery in the receipt, the calculation item indicator is set to "service"
— fixed payment confirmation upon setting the corresponding order status
— refactoring
— added the ability to change the payment description. Placeholders are available
— added the option "Automatically confirm payment in CloudPayments when the payment flag is set in the store", enabled by default
— expanded the list of supported currencies
— fixed automatic opening of the widget in the detailed order card
— redesigned the administrative part
— fixed found errors
— fixed encoding errors
— added a component for CloudPayments payment; now payments can be accepted on any Bitrix edition!
— added the ability to change the text next to the payment button. HTML tags are supported
— added the onNotification event, triggered when working with the payment component
— restored the ability to select skins
— the test mode setting has been removed from the payment system settings. Test mode is now enabled only from the CloudPayments side
— other minor improvements, fixes, and refactoring.
— added the beforeHandlerRunAction and afterHandlerRunAction events before and after notification processing
— added logging to the file /bitrix/php_interface/include/sale_payment/rovercloudpayments/rovercloudpayments.log. It can be enabled with the PHP command Bitrix\Main\Config\Option::set('rover.cloudpayments', 'log-enabled', 'Y');
— fixed minor errors
USER EXPERIENCE
How does this solution work in a real project? Share your experience and help others choose.
There are no reviews of this solution on git.ru yet. Tell us what worked well and what could be improved.
Verified purchaseAdd a key if you wish. A verified review gets a badge, priority placement and more rating weight.
Open to every clientJust sign in to your account. A key is optional; all reviews are moderated.
YOUR PROJECT INFRASTRUCTURE
FROM THE SAME DEVELOPER
Pavel Shulaev
The module integrates T-Bank (formerly Tinkoff Bank) e-commerce acquiring with 1C-Bitrix of any edition, from 'First Site' to 'Enterprise'. It automatically creates the payment system, supports migration from the official module, maintains an operations log, and sends error notifications via the rover.notifier module.
Starting with version 2.0.0, the module supports extension without modifying source code. The list of GeoIP services and their execution order are assembled via the onBuildServiceList event. You can connect custom services from other modules by registering an event handler and returning the full class name of your service. The module provides an API for location determination by IP address.
The Administrative Part Builder is a framework for rapid and flexible configuration of the administration interface for Bitrix modules. The tool fully handles the rendering of the graphical interface and the management of options.
MORE FOR YOUR WEBSITE
SDEK integration module for 1C-Bitrix. SDEK is one of Russia's largest logistics companies, providing courier delivery and operating a network of pickup points. The module connects the online store with the SDEK personal account, offering the following capabilities: Providing customers with delivery options: courier, pickup point, or postmat.
The module automatically determines the visitor's location based on their IP address and offers city selection in a stylish popup window. It is available in all platform editions. Key features include automatic location detection by IP address, domain, or website, along with automatic redirection to specific domains and subdomains, including external resources.
The SMSBiz module is designed for sending SMS notifications in online stores and corporate portals built on the 1C-Bitrix platform. Installation and use do not require programming skills and take only a few minutes. The solution is based on the SMSInt service, which has been operating in the market for over 15 years.
BEFORE YOU ORDER