1С/BAS ↔ LiqPay integration

An invoice in 1С/BAS becomes a LiqPay payment page, and the payment status comes back into the same document

The invoice is made in 1С/BAS, but the customer pays through LiqPay, and the accountant learns about the payment from the cabinet or a bank statement and marks it by hand. We connect the two so an invoice in 1С/BAS opens a LiqPay payment page with the methods the customer is used to, and every payment result is checked for authenticity and written back into the same 1С/BAS document.

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

What moves between the systems

1С/BAS → LiqPayAn invoice or order posted in 1С/BAS creates a LiqPay payment page, where the customer chooses a card, Privat24, Apple Pay, Google Pay, a QR code or instalments.
1С/BAS → LiqPayWhen a customer wants an invoice by email, the invoice from 1С/BAS is sent through LiqPay to their address, without a manager retyping it.
LiqPay → 1С/BASThe payment result from LiqPay is checked against your private key to confirm it is genuine, then written into the 1С/BAS document, and the order is marked as paid.
1С/BAS → LiqPayFor orders that still need a stock check, the money is only held on the card, and 1С/BAS shows which orders are held and which are already charged.
LiqPay → 1С/BASRecurring charges for subscriptions and memberships arrive in 1С/BAS as payments against the right customer, so the accountant does not enter them every month.

What we connect

We look at your 1С/BAS configuration and which document starts a payment: an invoice, an order or a sales document.
You give us the keys from your LiqPay cabinet, starting with the separate test pair, so nothing is charged or credited while we set up.
We agree which payment methods the customer sees, which orders only hold the money, and which ones are subscriptions with recurring charges.
We set up receiving payment results: each one is checked for authenticity with your private key before it changes anything in 1С/BAS.
We decide how the fiscal receipt is issued: LiqPay reaches the Checkbox cash register through an intermediate module, not directly, so we agree which side prints it.
We run the whole path on the test keys, then switch to live keys and stay on call for the first working days.

Automation scenarios

Payment confirmed by screenshot

Before the customer sends a screenshot, the manager looks for the payment in the LiqPay cabinet and marks the invoice in 1С/BAS by hand.

After the checked payment result arrives in the 1С/BAS document by itself.

Invoices retyped for email

Before the invoice is made in 1С/BAS, then a manager builds a separate payment request and emails it.

After the invoice from 1С/BAS goes to the customer's email through LiqPay with a payment option.

Charged before the stock check

Before the money is charged at once, and if the item turns out to be missing, the manager has to arrange giving it back.

After the money is only held until the order is confirmed in 1С/BAS.

Subscriptions entered by hand

Before every month the accountant copies recurring charges from the LiqPay cabinet into 1С/BAS customer by customer.

After each recurring charge appears in 1С/BAS against the right customer on its own.

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
LiqPay Checkout supports these payment methods: Privat24, Apple Pay, Google Pay, QR-code payment, Mastercard/Visa cards, FacePay24, tokens, self-service payment terminals, instalments and an invoice sent to email.
Source: www.liqpay.ua ↗ checked 2026-09-25
The Checkout API supports different payment types through the action parameter: pay (direct charge), hold (two-stage payment — funds held on the card), subscribe (recurring payment), paydonate (donations), split_rules (splitting one payment between several recipients), apay/gpay (Apple Pay / Google Pay).
Source: www.liqpay.ua ↗ checked 2026-09-25
The payment status is delivered to the server_url as a POST request with data and signature parameters; to confirm the callback is genuine, the receiving server has to recalculate the signature itself using the same algorithm and private key, and compare it with the one received.
Source: www.liqpay.ua ↗ checked 2026-09-25
For testing, LiqPay issues a separate pair of test (sandbox) keys prefixed sandbox_; using them never charges or credits real money.
Source: www.liqpay.ua ↗ checked 2026-09-25

Limits

The limits come from both systems. Saving a customer's card for future automatic charges without an immediate payment is available only to merchants holding a PCI DSS certificate of the matching level, not to every account. LiqPay does not issue fiscal receipts directly: a receipt reaches the Checkbox cash register through the AssetPayments module. Refunds from 1С/BAS are not part of this page: we check how they work for your account before promising them. 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

What does the customer see?

Only the LiqPay payment page with the usual methods: card, Privat24, Apple Pay, Google Pay, QR code or instalments. 1С/BAS stays behind the scenes.

How do we know a payment notice is real?

Every result from LiqPay comes with a signature. We recalculate it with your private key and compare; a notice that does not match changes nothing in 1С/BAS.

Can we test without real money?

Yes. LiqPay gives a separate pair of test keys that never charge or credit real money, so the whole path from 1С/BAS is rehearsed on them first.

Who prints the fiscal receipt?

LiqPay reaches Checkbox through the AssetPayments module. If 1С/BAS is already linked to Checkbox, we pick one route for the receipt so a payment never gets two.