Payments & POSUACard, Privat24, Apple Pay and Google Pay — every payment method on one checkout page
LiqPay is PrivatBank's payment service: a customer pays by card, Privat24, Apple Pay, Google Pay, QR code or in instalments, all on one checkout page. We connect LiqPay to your site or CRM, set up the option to hold funds on a customer's card until an order is confirmed, and check the whole flow with test keys before real money moves.
Before the card is charged right at checkout, and if the item isn't actually in stock, the money has to be manually refunded.
After LiqPay holds the money on the customer's card, and it's charged only once the order is confirmed.
Before the customer has to open the site and re-enter card details every billing cycle, and misses payments if they forget.
After LiqPay charges the recurring payment on schedule by itself, once the subscription is set up.
Before a marketplace or agency receives the whole payment and then works out by hand how much goes to each supplier.
After LiqPay splits one payment between several recipients automatically, by rules set up in advance.
Before a manager looks up the payment and sends a confirmation by hand.
After LiqPay can send the receipt to the customer's email on its own, right after the payment goes through.
Before testing feels risky because a mistake could charge a real card.
After a separate pair of test keys runs the exact same flow with no real money moving, so we catch problems before go-live.
For those who want to check: each point links to the official documentation page it comes from.
Every request to the LiqPay API is signed: the signature is base64(sha3-256(private_key + data + private_key)), where data is the JSON request itself, base64-encoded.
Source: www.liqpay.ua ↗ checked 2026-09-25LiqPay 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-25The 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-25The 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-25For 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-25Saving a customer's card for future automatic charges without an immediate payment is a private API method — it's available only to merchants holding a PCI DSS certificate of the matching level, not by default to every account. The payment signature algorithm is sha3-256; older examples floating around the internet that use sha1 are outdated.
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 →
↔An invoice in 1С/BAS becomes a LiqPay payment page, and the payment status comes back into the same document
See scenarios →↔
A Shopify order gets a LiqPay payment link or an invoice to email, and a confirmed LiqPay payment finds its order and moves it on, without anyone checking two screens
See scenarios →
Payments & POSUAThe cash register that sends the receipt to the tax office the moment payment goes through
See scenarios →
Payments & POSUAPayments with a hold before charging and scheduled recurring charges for subscriptions
See scenarios →
Payments & POSUACard payments that connect straight to the Checkbox cash register, plus 50+ ready platform connections
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 →
E-commerce platformsUSYour own WordPress store: orders, products and customers flow into CRM, delivery and payments without manual copying
See scenarios →Implementation · Development · Integrations →
LiqPay 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.
