CMS MODULES FOR THE PAYMENT SYSTEM

The project implied development of payment modules to be quickly installed in site engines 1C-Bitrix and WordPress to provide prompt payment integration

Timeline2 months

Development costUndisclosed

FormatFintech · CMS

StatusBitrix / WordPress plugins

Challenge

Official payment modules for WordPress and 1C-Bitrix under NDA

Solution

Shared PHP SDK, CMS hooks, HMAC callbacks and a version matrix

Result

Marketplace release, checkout live in about five minutes

Why we built these modules

An NDA-covered payment aggregator wanted to stop hand-rolling REST integration on every new store for Russia’s two dominant CMS platforms — WordPress and 1C-Bitrix. Partners needed official plugins installed from the admin UI, full transaction lifecycle support and marketplace moderation approval.

Requirements included legacy Bitrix editions, holds, refunds and partial refunds, logging without storing sensitive data inside the CMS and signed callback verification. WordPress had to support WooCommerce and shortcode-only sites; Bitrix had to fit the standard shop checkout and multiple gateways inside one module.

We moved shared logic into an SDK over roughly sixty API endpoints, covered it with PHPUnit tests and built two adapters on native CMS extension points — so API updates touch the layer once instead of two diverging codebases.

Key capabilities

Shared PHP SDK

Request building, JSON, timeouts and retry on 5xx — one business core for WordPress and Bitrix with modular tests against API responses.

Setup wizard

Shop ID and secret key; remaining settings load automatically, with several gateways in one Bitrix module when the merchant uses multiple providers.

Callbacks and PCI

Synchronous post-payment response plus async callbacks with HMAC and IP allowlists; sensitive data never stays in the CMS, step logs for admins.

WordPress plugin

WooCommerce via woocommerce_payment_gateways, shortcodes without WooCommerce, a Payments tab on Settings API, RU/EN localization via GlotPress.

1C-Bitrix module

Registration through onSalePsBeforeSave, checkout payment component, facades for editions 14–23 and pre-D7 order API differences.

Catalog sync and debug

Periodic pull of currencies, methods and statuses from the API; debug mode with request dumps for aggregator support.

How it works

Docker benches with pinned CMS versions and Jenkins CI ran regression on every commit. For Bitrix we stood up twenty-six edition, PHP and MySQL combos — each change was checked on holds, refunds and order expiry; sourcing old distributions became its own engineering task.

The WordPress side moved faster thanks to mature hooks; Bitrix needed include.php, event handlers and compatibility with legacy order APIs before D7. The SDK isolated networking so adapters stay thin.

Before publication we prepared marketplace pages, FAQ and wizard screenshots; passed XSS/nonce review in the Plugin Directory and module structure review in the 1C marketplace. The client registered solutions with install tracking IDs.

How the work went

01SDK, CMS version matrix and CI

02WordPress plugin and WooCommerce

03Bitrix module and 26-bench regression

04Marketplace moderation and release

Technologies

PHPWordPress1C-BitrixWooCommerceREST SDKPHPUnitDockerJenkins CI

Want modules for your payment stack? A project like this starts from 1–3 months at a fixed price, or 0 for development with support from 45,000 ₽ / month.

What we delivered

Both modules passed moderation and live in official catalogs: merchants enter keys and accept payments in under five minutes instead of multi-day manual REST integration, hand-edited checkout flows and developer-led callback wiring.

The SDK and CMS admin logs cut diagnosis time and bad integrations. API support tickets dropped about 40% in the first two months; WordPress and Bitrix 14–23 cover legacy retailers without replatforming or custom checkout rewrites.

An isolated SDK simplified the roadmap for the next engines — the client got enterprise reliability, HMAC callbacks and simple install UX; we got a repeatable Docker matrix, CI and WordPress and Bitrix marketplace publication under NDA, as in other ESK fintech integrations.