Yes. Krokul CRM integrates with LiqPay. Krokul builds a LiqPay payment page from a deal with the deal order_id, and the LiqPay callback to server_url turns the expected payment into an actual one after the signature check. The setup runs through the Krokul API and webhooks.
A manager clicks «Payment link» on the deal. Krokul builds a LiqPay checkout with action pay, the amount and currency of the expected payment, a description and an order_id that points to the deal. Krokul signs data with the store private key and gives the client a link to the payment page.
After payment, LiqPay sends the data and signature fields to server_url. Krokul checks the signature, decodes data, finds the deal by order_id and, for the success status, turns the plan into an actual payment. The payment.received event goes to accounting, and full coverage of the invoice triggers invoice.paid.
Krokul stores the LiqPay payment_id as the external key of the payment. A repeated callback with the same payment_id finds the payment already recorded and creates no second one.
A callback with the reversed status means that LiqPay returned the money. Krokul records the refund on the deal, reduces the paid amount and leaves an entry in the feed, so the accountant sees why the payments differ from the invoice.
The failure and error statuses leave the payment open, and an entry about the failed attempt appears in the deal feed. The manager sees that the client tried to pay and can offer another way.
| LiqPay | Direction | Krokul | When |
|---|---|---|---|
| Checkout: action pay, amount, currency, description, order_id, server_url | Krokul → LiqPay | Expected deal payment | A manager creates a payment link |
| Callback to server_url with the success status | LiqPay → Krokul | Actual deal payment, payment.received event | The client has paid |
| payment_id | LiqPay → Krokul | External key of the payment | On the first callback |
| Callback with the reversed status | LiqPay → Krokul | Refund on the deal, entry in the feed | After a refund |
| Callback with the failure or error status | LiqPay → Krokul | Entry about the failed attempt, the plan stays open | The payment did not go through |
payment/api-create with the deal cardUuid and links the LiqPay payment_id to the payment through externalRef/api-set.payment.received and invoice.paid, so accounting learns about the money. Each delivery carries the x-crm-signature header, and your receiver checks it with the secret.Krokul computes base64 of the hash of the string private_key + data + private_key, as the LiqPay documentation describes. Krokul rejects a callback without a valid signature and records nothing.
Krokul stores payment_id as the external key of the payment. A repeated callback with the same payment_id creates no second payment.
An entry in the deal feed with the LiqPay status. The expected payment stays open, and the manager can send a new link.
Refunds and payment cancellations are made in the LiqPay account or through its API, and Krokul gets the result as a callback with the reversed status. Recurring payments and donations (the subscribe and paydonate actions) stay in LiqPay, and Krokul uses the pay action for a deal payment.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
LiqPay is a trademark of its owner. Krokul is not affiliated with LiqPay.