Monobank is one of the most popular acquirers in Ukraine. The invoice webhook is verified by an ECDSA signature, records a payment on the order, and updates its status.
How it works
Invoice webhook
Monobank posts the invoice status with an x-sign header to the adapter endpoint.
Payment record
A crm_order_payments row is created with amount and status.
Status update
The order moves to "Confirmed" if it was "Pending".
Security
- ECDSA/SHA-256 signature verified against the merchant public key
- The public key is fetched once and cached, refreshed only on failure
- No card data stored (PAN/CVV) — only amount, status and invoice id
- Tied to the order by the invoice reference
Real connection test
In the adapter settings you can verify the merchant token against Monobank before any real payment — the test returns the connected merchant identity without recording a payment.
Setup
- 1
Add the Monobank adapter
Provide the merchant X-Token and copy the webhook URL.
- 2
Set the URL in Monobank
Use the generated endpoint as the invoice webhook URL.
- 3
Test the connection
Run the connection test to confirm the token reaches Monobank.
Frequently asked questions
Is card data stored?
No. We store only the status, amount and invoice id — no PAN/CVV.
How is the right order found?
The invoice reference from the webhook is matched to the order's externalId in the CRM.
Connect Monobank
Payments move the order status automatically.
Start for free