Payments & POSUACard payments that connect straight to the Checkbox cash register, plus 50+ ready platform connections
monobank's payment acceptance service is the only one of the four payment systems we work with that connects to the Checkbox cash register directly, right from the monobank cabinet — no third party in between. We connect it to your site or CRM, set up two-stage payments where money is held until an order is confirmed, and check the whole flow in a test environment that's open to every bank client, no terminal required.
Before the customer is charged right away, and an out-of-stock item means a manual refund.
After monobank holds the money on the card for up to 9 days and charges it only once the order is confirmed.
Before testing a payment gateway usually means arranging a terminal or a special permission first.
After monobank's test environment is open to every bank client right away, and any test card number, date and CVV work for a trial payment.
Before the refund and the return receipt are handled as two separate manual steps.
After one call cancels the payment, returns the money — fully or partially — and generates the return receipt at the same time if the cash register is connected.
Before a marketplace receives the whole payment and manually works out how much each supplier is owed.
After the split feature automatically divides one payment between several recipients by rules set up in advance.
Before fiscalising a payment usually means connecting a third-party module between the payment system and the cash register.
After monobank connects to Checkbox directly from the monobank cabinet, so the receipt is fiscalised without any extra party involved.
For those who want to check: each point links to the official documentation page it comes from.
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-25The test environment for the acquiring API is open to every bank client without a terminal or a separate permission; any card number, expiry date and CVV can be used for a test payment, with no real money charged.
Source: api.monobank.ua ↗ checked 2026-09-25An 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-25Cancelling 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-25Delivery 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-25monobank advertises over 50 ready no-code connections between its acquiring service and popular website builders and CRM systems.
Source: monobank.ua ↗ checked 2026-09-25An invoice created through the connection expires in 24 hours by default, and a hold (two-stage payment) auto-cancels after 9 days if it isn't finalised. Saving a customer's card for future automatic charges (tokenisation) isn't a self-service option in the cabinet — it requires contacting monobank support directly to enable it.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →
Payments & POSUAThe cash register that sends the receipt to the tax office the moment payment goes through
See scenarios →
Payments & POSUACard, Privat24, Apple Pay and Google Pay — every payment method on one checkout page
See scenarios →
Payments & POSUAPayments with a hold before charging and scheduled recurring charges for subscriptions
See scenarios →
CRMUAUkrainian CRM that pulls orders from your site, marketplaces and chat apps into one pipeline
See scenarios →
CRMUAThe CRM built for order-taking: every lead from every channel lands in one place on its own
See scenarios →
Payments & POSUACard payments that reach the client's order the moment they clear — without card data ever touching your server
See scenarios →Implementation · Development · Integrations →
monobank is a trademark of its owner. CoreviaFlow is not affiliated with it unless stated otherwise. Screenshots are taken from public vendor materials; the source is shown under each one.
