Select one or more tags, then press “Search Plugins”

Find Plugin with any / all of the selected criteria
Search Plugin

VitaliiHura Checkout For LiqPay Wordpress Plugin - Rating, Reviews, Demo & Download

VitaliiHura Checkout For LiqPay Preview Wordpress Plugin - Rating, Reviews, Demo & Download
No ratings yet
Free
Follow for free plugins, new theme releases and theme news

Plugin Description

A complete LiqPay integration for WooCommerce. Customers pay on the LiqPay page and come back to
your shop; the plugin verifies the notification LiqPay sends, updates the order and records the
transaction details a shop needs for accounting and support.

This plugin is not affiliated with, endorsed by or built by LiqPay or PrivatBank.

What it does

Customers are handed to the LiqPay page and pay there with whatever you have enabled: card, Apple
Pay, Google Pay or Privat24. You can narrow that list per shop or leave the choice to your LiqPay
account. The credit, QR code, cash and invoice methods LiqPay also offers are not available yet.

Refunds work from the WooCommerce order screen, in full or in part. A full refund made inside the
LiqPay account is picked up and recorded against the order; LiqPay does not report a partial refund
made there, so that one has to be recorded by hand. The order screen shows what was charged, what
LiqPay took as commission and how much of it went back.

Marketplaces can split a payment between several recipients through a filter.

Notifications from LiqPay are verified against your private key, deduplicated, and processed under
a per-order database lock, so two notifications arriving at once cannot both change the same
order. A confirmation is refused unless it names the currency and an amount that covers the order,
and a test-mode payment can never settle a live order. Every status LiqPay documents is
recognised, including the ones where the customer still has something to do.

If a notification never arrives, the shop asks LiqPay itself the moment the customer lands back on
the order received page, and an hourly check covers the customers who never came back.
There is also a button on the order screen to do it on demand.

Multilingual shops get per-language fields for everything a customer reads: the payment method
name, its description and the payment purpose. The language switch appears only when the site
actually has more than one language, and an empty translation falls back to the default one. The
language list is read from Polylang, WPML or TranslatePress, and the values are resolved from the
language of the order rather than the language of whoever is looking at the order, so a customer
who bought in English does not find a Ukrainian line on their card statement.

Test mode uses a separate key pair and can be limited to shop managers, so you can try it on a
live shop without customers seeing the method. The gateway works with High-Performance Order
Storage and with both the block based and the classic checkout.

The settings screen opens with whether the connection works, which mode the shop is in and when
LiqPay last called, and there is a button to check the keys without taking a payment. Settings are
grouped by subject with an index beside them, and the screen works on a phone.

Requirements

  • WooCommerce 8.2 or newer.
  • A LiqPay merchant account with a public and private key.
  • Payments in UAH, USD or EUR, and the merchant account has to be enabled for the one you sell in. LiqPay accepts no other currency.

Split payments have to be switched on for your merchant account by LiqPay before they work. The
plugin surfaces the error LiqPay returns when a feature is not available.

Development

The source lives at https://github.com/vitaliihura/vitaliihura-checkout-for-liqpay-pb. Bug reports and
patches are welcome there.

Third-Party Services

This plugin connects your shop to LiqPay, a payment service operated by PrivatBank, so that it can
process payments. Payments cannot be taken without contacting it.

Data is sent to LiqPay only after you enter your own LiqPay API keys and enable the payment
method, and only for orders a customer chooses to pay with this method.

When a customer pays, the plugin sends to https://www.liqpay.ua/api/3/checkout and
https://www.liqpay.ua/api/request: your public key, the order reference, the amount, the
currency, the payment purpose text, the language, and the return and notification addresses of
your site. Depending on the settings you enable, it may additionally send the billing name and
address, and the product names and the order link.

LiqPay sends back, and the plugin stores on the order, a payment status, its own payment
identifiers, the payment method used, a masked card number, the card brand and issuing bank, the
acquirer identifier, the authorisation code, the retrieval reference number and the commission.

Notifications from LiqPay are received at an address on your site and are accepted only when the
signature made with your private key matches.

Wording you can paste into your own privacy policy is added under Tools, Privacy, Policy Guide.
When a customer asks for their data to be removed, the masked card number and the issuing bank are
cleared from the order along with the rest of the personal data WooCommerce removes.

  • Service: https://www.liqpay.ua/
  • Terms of use: https://www.liqpay.ua/en/information/terms
  • Privacy policy: https://privatbank.ua/personal-information
  • API documentation: https://www.liqpay.ua/en/doc

Screenshots

  1. The settings screen: connection state, the name and description customers see, live and sandbox keys.

    The settings screen: connection state, the name and description customers see, live and sandbox keys.

  2. What LiqPay is asked to do: the methods on its page, the payment purpose in every site language, the link lifetime and the reference prefix.

    What LiqPay is asked to do: the methods on its page, the payment purpose in every site language, the link lifetime and the reference prefix.


Reviews & Comments