1С/BAS ↔ monobank integration

Orders from 1С/BAS get a monobank payment invoice, and payment status, holds and refunds come back into the same documents

The order lives in 1С/BAS, but the payment is accepted through monobank, and someone has to check the monobank cabinet to see who paid and mark the order by hand. We connect the two so an order in 1С/BAS gets a payment invoice, the payment status is written back into the same document, held payments are confirmed when the order ships, and a return in 1С/BAS starts the refund.

Request an integration System page: 1С/BAS →System page: monobank →

What moves between the systems

1С/BAS → monobankAn order or invoice posted in 1С/BAS creates a monobank payment invoice, and the payment link is saved in the document so the manager can send it to the customer.
monobank → 1С/BASEvery change of the payment status in monobank, such as paid, failed or expired, is written into the same 1С/BAS document, and a paid order is marked as paid without anyone opening the cabinet.
monobank → 1С/BASStatus notices from monobank may arrive out of order, so 1С/BAS keeps the latest one by its time and a late intermediate notice never overwrites a finished payment.
1С/BAS → monobankFor orders that need confirmation, the money is only held on the customer's card; shipping the order in 1С/BAS confirms the charge, and cancelling it releases the hold.
1С/BAS → monobankA return registered in 1С/BAS starts a full or partial refund in monobank, and the list of returned items goes along for the return receipt when the cash register is connected.

What we connect

We look at your 1С/BAS configuration and which document starts a payment: an order, an invoice or a sales document.
You give us access to the monobank business cabinet, and we start in the monobank test environment, which is open to every bank client, so no real money moves while we set things up.
We agree which statuses mean the order is paid, what happens to an invoice the customer did not pay in time, and who is told about a failed payment.
We set up holds: which orders only hold the money, which 1С/BAS document confirms the charge, and a reminder before monobank cancels an unconfirmed hold on its own.
We set up refunds from 1С/BAS returns and agree with you who issues the return receipt, so the same return does not get two receipts.
We run test payments, holds and refunds end to end, then switch to live payments and stay on call for the first working days.

Automation scenarios

Who paid is checked by hand

Before the manager opens the monobank cabinet several times a day, finds the payment and marks the order in 1С/BAS, and the warehouse waits for that mark.

After the payment status arrives in the 1С/BAS document by itself, and the warehouse sees paid orders right away.

A held payment silently disappears

Before the money was held on the card, the order shipped, but nobody confirmed the charge, and monobank cancelled the hold.

After shipping in 1С/BAS confirms the charge, and an unconfirmed hold is flagged before it expires.

Refunds made outside accounting

Before the refund is made in the monobank cabinet, the return in 1С/BAS is entered later or forgotten, and the stock and the money do not match.

After the return in 1С/BAS starts the refund, and both sides describe the same items.

Expired payment links

Before the customer opens an old payment link, it no longer works, and the manager learns about it only from a complaint.

After the expired status is visible in the 1С/BAS document, and the manager sends a new link before the customer asks.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
On every status change of an invoice, the acquiring backend makes up to 3 POST-request attempts to the connected notification address until it gets an HTTP 200 OK response; the request is signed by the ECDSA standard and passed in the X-Sign header.
Source: api.monobank.ua ↗ checked 2026-09-25
An invoice created through the connection is valid for 24 hours by default; for hold payments (two-stage payment) the automatic cancellation window is 9 days if the hold isn't finalised.
Source: api.monobank.ua ↗ checked 2026-09-25
Cancelling a payment supports a partial refund through the amount parameter, and the same request can include a list of items for the return receipt if fiscalisation is enabled for the merchant.
Source: api.monobank.ua ↗ checked 2026-09-25
Delivery order isn't guaranteed for status notifications — for example, a success notification can arrive before the corresponding processing notification; the notification with the latest modifiedDate field should be treated as current.
Source: api.monobank.ua ↗ checked 2026-09-25

Limits

The limits come from both systems. By default a monobank payment invoice is valid for 24 hours, and a hold that is not confirmed is cancelled by monobank after 9 days, so these windows are built into the order process. Status notices can arrive out of order, which we handle by keeping the latest one. Saving a customer's card for future automatic charges is not a self-service option: it is enabled through monobank support. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Do we still need the monobank cabinet?

For everyday payments, no: invoices, statuses, holds and refunds go through 1С/BAS. The cabinet stays for settings, reports and anything we do not automate.

Who issues the fiscal receipt for an online payment?

monobank can be linked to the Checkbox cash register right in its cabinet. If you already have 1С/BAS linked to Checkbox, we choose one side to issue the receipt, so a payment never gets two.

Can we test without real money?

Yes. monobank opens a test environment to every bank client, where any card details work and nothing is charged, so the whole path from 1С/BAS is rehearsed there first.

What if a status notice does not arrive?

monobank repeats the notice several times until it is received. If an order still stays without a status, it is flagged in 1С/BAS for the manager to check, instead of hanging silently.