</>
maximorum.com

Integrating LiqPay with WooCommerce: a production guide for Ukrainian online stores

D

Ukrainian online stores lose revenue at checkout when payment options feel unfamiliar. LiqPay — backed by PrivatBank and trusted by millions of Ukrainian cardholders — supports cards, Google Pay, Apple Pay, and instalments in a single checkout flow. Wiring it correctly into WooCommerce is a PHP engineering task, not a plugin install.

What a production-grade integration covers

A bare "pay with LiqPay" button handles the happy path. Production systems need four more components:

  • Signed API requests. Every call to the LiqPay API carries a SHA-1 signature derived from your public_key, private_key, and a Base64-encoded payload. A mismatch returns HTTP 403 before any money moves.
  • Async webhook receiver. LiqPay POSTs payment status updates to your wc-api=liqpay_callback endpoint. Without a working receiver, orders stay pending even after a successful charge — blocking fulfilment and triggering false support tickets.
  • Order state mapping. LiqPay statuses (success, failure, wait_accept, reversed) must map cleanly to WooCommerce order states (processing, failed, on-hold, refunded). Gaps here cause fulfilment errors and accounting discrepancies.
  • Refund API call. When a merchant clicks Refund in WooCommerce, the plugin fires a reverse call to /api/3/refund. Without it, the WooCommerce balance and the LiqPay dashboard diverge immediately.
LiqPay WooCommerce integration — developer workstation with checkout and PHP code

Currency and multi-store considerations

The LiqPay API accepts UAH, USD, and EUR. Store the order currency on post_meta at checkout — not at capture — to prevent rounding errors on multi-currency stores. If you run multiple WooCommerce instances under one domain, each store needs its own LiqPay merchant account and a separate webhook URL.

Development timeline

A clean plugin built to WooCommerce 8.x standards — including sandbox testing, webhook hardening, and a PHPUnit test suite — runs three to five working days. Retrofitting into a heavily customised theme adds one to two days of QA. We scope every project before writing a line of code.

Why this matters for conversion

Payment familiarity is a conversion lever. Stores that surface LiqPay alongside standard card inputs see checkout drop-off fall by 12–18% on mobile, where LiqPay's one-tap pay flow removes the card-entry step entirely. That is revenue recovered without changing your pricing or advertising spend.

Ready to integrate?

MaxiMoruM has shipped payment integrations for Ukrainian e-commerce businesses since 2010 — across WooCommerce, OpenCart, and custom Laravel applications. Contact us at maximorum.com to scope your LiqPay integration project.