LiqPay webhook triggers in n8n: automate everything after the payment
The payment clears. Then what? For most Ukrainian online stores, "then what" is a person. Someone opens the LiqPay dashboard, copies the order number into the CRM, marks the invoice paid in accounting, pings the warehouse, and emails the customer. Multiply that by a few hundred orders a month and you have a salary spent on copy-paste — plus the delays and reconciliation errors that come with it.
The problem isn't LiqPay. LiqPay already knows the moment a payment succeeds. The problem is that nothing downstream hears about it automatically. The payment confirmation sits in one system while your CRM, your accounting, and your fulfillment team wait to be told.
The solution: a signed callback into n8n
The fix is a LiqPay server callback wired into an n8n workflow. LiqPay sends a signed POST request to a URL you control the instant a transaction changes state — success, failure, reversal, or refund. n8n receives that request, verifies it, and routes the event to every system that needs it. No dashboards, no copy-paste, no waiting.
The workflow we deploy
- Catch the callback. Add a Webhook node in n8n and copy its production URL. In your LiqPay integration, set this URL as the
server_urlthat LiqPay calls on every status change. - Verify the signature. LiqPay signs each callback as
base64(sha1(private_key + data + private_key)). The workflow recomputes that signature with a Function node and compares it to the one LiqPay sent. If they don't match, the run stops — keeping a forged "payment succeeded" request from ever reaching your order logic. - Branch on status. A Switch node reads the decoded payload and splits on status — success, reversed, refund, error — so a refund never gets treated like a sale.
- Fan out the success path. On a successful payment the workflow updates the order to "paid" in your CRM or OpenCart over the API, writes the invoice line to Google Sheets or your accounting tool, posts to the warehouse Telegram channel, and sends the customer a branded confirmation email — all in parallel, in under a second.
- Make it reliable. Enable retries on each outbound node and route failures to an error workflow that alerts a manager. Every payment event is logged and every failed delivery is surfaced — not silently dropped.
The business result
Orders move to fulfillment the moment money arrives instead of at the next manual check. Accounting reconciles itself because every paid invoice is written the instant it's paid. Your team stops watching a payment dashboard and starts handling exceptions only. For a store doing a few hundred orders a month, that's hours of manual work removed every week and a measurable cut in reconciliation errors.
LiqPay handles the money. n8n handles everything that has to happen next. The integration is a few hours of engineering against a stack we've shipped for two decades — PHP, Laravel, OpenCart, and the Ukrainian payment and delivery APIs your business runs on.
Want your payments wired straight into fulfillment and accounting? Talk to us at maximorum.com