Instalment Payments — PrivatBank, monobank and A-Bank for OpenCart 2.3, 3 and 4

Instalment Payments with PrivatBank, monobank and A-Bank adds a single payment method to OpenCart in which the buyer picks the bank themselves. PrivatBank takes them to its own page and offers 2–25 instalments; monobank does not redirect anywhere — a push notification in the app, a confirmation, and the buyer is already on the thank-you page. The shop receives the full amount from the bank — at once, or in parts over the term with the Privatbank PB programme (“funds over the term”). There are three builds: for OpenCart 4.0.2 – 4.1.x, 3.0.2 – 3.0.5.0 and 2.3.0.x; the functionality is identical, only the package differs.

What it looks like for the shopper

An instalment payment method appears in the list of payment methods, with the banks you enabled named in its title. Next to it, the approximate monthly amount is shown — calculated from the order total including delivery, not from the product price alone. With PrivatBank, after confirming, the shopper lands on the bank’s page, logs into Privat24 and arranges the instalment plan; the result is returned to the shop.

The payment method is only shown when the bank will actually accept it: the currency is hryvnia, and the order total is within the range at least one enabled bank accepts (PrivatBank — 300–50,000 UAH, monobank and A-Bank — from 1 UAH). If the cart falls outside those bounds, the method doesn’t appear at all — the shopper doesn’t waste time on a payment the bank would reject.

monobank: confirmation in the app

With monobank the buyer splits the order into 3–25 payments and confirms the purchase right in the app, without going to the bank’s page. Meanwhile the shop shows a waiting page that carries the order to its final status on its own — the buyer does not have to refresh anything by hand.

The signature of every PrivatBank and monobank notification is verified — a notification with a wrong signature is rejected. On top of that, the module asks the bank for the application state itself: for PrivatBank when the shopper returns to the shop, for monobank and A-Bank while the waiting page is open. A repeated notification duplicates nothing, and an order that has already been paid cannot be sent to the bank a second time.

A-Bank: instalments confirmed in Abank24

The third bank works like monobank: the buyer picks A-Bank, enters their phone number and approves the request in the Abank24 app. The shop waits on its own page and completes the order by itself, and if the number is not an A-Bank customer or the request is declined, the buyer sees a clear reason right away.

A-Bank does not sign its notifications, so the module treats them only as a signal: on each notification it asks the bank for the application status itself and changes the order only based on that answer. A forged “paid” request changes nothing.

The bank programme is yours

In the settings you choose the programme your agreement covers: II — instant instalment, the shopper pays the fee; PP — payment by instalments, the shop pays the fee and receives the amount at once; PB — payment by instalments with funds over the term, the shop pays the fee and receives the amount in parts; IA — promotional instant instalment, the fee is split 50/50 between the shop and the shopper. You also set a default number of payments, and in Pro, an upper limit within which the shopper picks the term themselves at checkout.

Verify first, then set the status

The bank reports the outcome two ways: a notification to your site, and the shopper’s return. The module doesn’t take either on trust — every PrivatBank and monobank notification is verified by its signature (A-Bank notifications carry no signature and only trigger a status request to the bank), and after the shopper returns, the application’s status is additionally requested from the bank. So a forged notification can’t mark an order as paid, and a lost one can’t leave a paid order stuck “awaiting payment”.

Order statuses are configured separately: awaiting payment, paid, amount reserved, declined. A repeated notification doesn’t duplicate anything, and an already-paid order can’t be sent to the bank a second time.

Reserve with confirmation

If a product still needs checking in stock, turn on reserve: the bank holds the amount and only charges it once you move the order to “paid” or click “Charge” in the log. If you don’t confirm, the reserve is released and the shopper pays nothing.

Application log

Every application is stored: the order, the bank’s application number, the amount, the number of payments, the bank’s status and message. From the log you can refresh the status from the bank, charge or cancel the reserve — without going into Privat24.

Test mode

Turn on test mode, and applications go to Privatbank’s official test shop from the documentation. No real funds are taken and no agreement is required, but the whole path — creating the application, the bank page, notifications, statuses — is walked through in full. Handy for checking the integration before you’ve even signed the agreement with the bank.

Why a shop needs this

Privatbank’s “Payment by Instalments” is the most familiar way for a Ukrainian shopper to buy something pricier than they’d planned today. The shop, meanwhile, extends no credit itself: the bank pays the full amount — straight away, or in parts over the term with the PB programme.

The complexity isn’t in the button itself, but in what happens after it: the bank’s notification might not arrive, the shopper might close the tab, and the order still needs to close correctly in any of these scenarios.

How to install

1. Upload the archive via “Extensions → Installer” and install the module.

2. Enter the shop ID and password from your agreement, and choose the programme.

3. Turn on test mode and run an order through the bank’s sandbox.

4. Turn test mode off — you’re ready to accept payments.