Why Payment Gateway Choice Matters
The payment page is the last step before the money. 70% of cart abandonments happen right here: an inconvenient form, unwanted payment methods, a suspicious-looking page. A well-chosen and configured gateway can increase conversion by 15–30% without any marketing changes.
LiqPay (PrivatBank) and Monobank Acquiring are the two most popular solutions in Ukraine. Let's examine each in detail.
Commission Comparison
| Parameter | LiqPay | Monobank Acquiring |
|---|---|---|
| Ukrainian card fee | 2.75% | from 1.5% |
| EU/US card fee | 3.5% | 2.5% |
| Minimum fee | 2 UAH | none |
| Payout timing | next business day | next business day |
| Connection fee | free | free |
| Monthly fee | none | none |
| Apple Pay / Google Pay | yes | yes |
| Recurring payments | yes (tokenization) | yes (tokenization) |
Commission conclusion: Monobank Acquiring is more cost-effective for most stores — especially if Ukrainian bank cards dominate. But the specific rate depends on turnover and business type — confirm individually.
Integration Methods
LiqPay
Hosted payment page — user redirects to liqpay.ua. Simplest integration, but the user leaves your site.
JavaScript Widget — payment form opens in a popup on your site. Good balance between simplicity and UX.
REST API — full customization. You collect card data yourself, which requires PCI DSS SAQ-D certification.
Ready-made plugins: WooCommerce, OpenCart, Magento, PrestaShop — installation without writing code.
Monobank Acquiring
Hosted page — redirect to pay.mbnk.biz.
API v2 — create an invoice via POST request, receive a payment link. Webhooks for status updates.
SDKs: official PHP SDK, unofficial for Python, Node.js.
Plugins: WooCommerce plugin available, other platforms via API.
Security and PCI DSS
PCI DSS (Payment Card Industry Data Security Standard) is mandatory for everyone processing payment data. Requirement level depends on integration method:
Hosted page / redirect — you never touch card data → PCI DSS SAQ-A (simplest form, ~20 questions)
JavaScript / iframe — card data entered in provider's frame → SAQ-A or SAQ-A EP
Own form + API — card data passes through your server → SAQ-D (~300 questions, annual audit)
Recommendation: for most stores — hosted page or JavaScript widget. Don't collect card data yourself unless you have a dedicated security team.
Additionally: both providers support 3D Secure 2.0 (Verified by Visa, Mastercard SecureCode) — reduces chargebacks and increases fraud protection.
Apple Pay and Google Pay
Both providers support Apple Pay and Google Pay through the Web Payments API.
Apple Pay: site must be on HTTPS, domain verification required (placing a file on the server). LiqPay and Monobank provide detailed instructions.
Google Pay: simpler activation, no domain verification required. Just pass the parameter in the gateway configuration.
Conversion with Apple/Google Pay buttons is typically 20–35% higher than manual card entry — especially on mobile.
Recurring Payments (Subscriptions)
Both providers support card tokenization — saving a token for repeat payments without re-entering card data.
LiqPay: parameter
subscribe: 1on first payment → receiveorder_idfor future chargesMonobank:
saveCardData: true→ receiverecTokenfor future charge requests
Important: the token is stored with the provider, not with you — this reduces your PCI DSS requirements.
Checkout UX: How Not to Kill Conversion
Minimum steps — ideally 1-2 steps from cart to confirmation
Progress bar — show where the user is in the payment process
Apple/Google Pay buttons at the top — don't hide them below the card form
Card field — input mask (1234 5678 9012 3456), automatic card type detection
Error messages — specific, not "Payment Error". "Insufficient funds" → "Check your balance or try another card"
Success page — clear order summary, expected delivery time, "View Order" button
Testing Before Launch
LiqPay test cards:
Successful payment:
4242 4242 4242 4242, CVV: 123, any future dateDeclined:
4000 0000 0000 0002
Monobank sandbox: separate API endpoint with a test token from your personal cabinet. Test cards are provided in the documentation.
Check before launch: successful payment → confirmation email → status change in admin → webhook received → refund processing.
Conclusion: Which to Choose
LiqPay — if you need maximum ready-made plugins, a PrivatBank customer base, or Ukrainian-language support is important
Monobank Acquiring — if lower commission matters more, you have API integration resources, or a large share of Monobank customers
Both simultaneously — let the customer choose. Some stores connect both and show "Pay via LiqPay" and "Pay via Monobank" buttons
Need help connecting a payment gateway to your store? We'll set it up, test it, and document it — contact us.