Yes. Krokul CRM integrates with WayForPay through the Krokul API and webhooks. A deal invoice becomes a WayForPay invoice with an invoiceUrl link. Krokul receives the WayForPay notice on serviceUrl itself, checks the signature, records the actual payment and replies with a signed accept.
A manager opens an invoice in Krokul and clicks «Payment link». Krokul calls WayForPay with transactionType CREATE_INVOICE and passes the orderReference, amount, currency, the document lines as productName, productPrice and productCount, the contact email and serviceUrl. The invoiceUrl link appears in the «Payments» block of the deal.
After payment, WayForPay sends JSON with transactionStatus, orderReference, amount and merchantSignature to serviceUrl. Krokul checks the HMAC_MD5 signature with the merchant secret key and, for the Approved status, turns the expected payment into an actual one. The payment.received event follows, and full coverage of the invoice triggers invoice.paid.
For every notice, Krokul returns JSON to WayForPay with orderReference, status accept, time and a signature. If WayForPay still sends a notice twice, Krokul finds the orderReference among recorded payments and creates no second one.
A notice with the Declined status keeps the plan open, and an entry about the failed attempt appears in the deal feed. The manager knows that the client tried to pay and can send the link again.
Once a day, Krokul goes through open expected payments with an orderReference and requests CHECK_STATUS. If a payment went through and the notice did not arrive, Krokul records the payment from its actual state.
| WayForPay | Direction | Krokul | When |
|---|---|---|---|
| CREATE_INVOICE: orderReference, amount, currency, productName, productPrice, productCount, clientEmail, serviceUrl | Krokul → WayForPay | Deal invoice and expected payment | A manager creates a payment link |
| invoiceUrl | WayForPay → Krokul | Link in the «Payments» block | In reply to CREATE_INVOICE |
| orderReference | WayForPay ↔ Krokul | External key of the payment | When the invoice is created |
| serviceUrl notice, transactionStatus Approved | WayForPay → Krokul | Actual payment, payment.received event | The client has paid |
| Signed accept reply | Krokul → WayForPay | Confirmation that the notice was received | For every notice |
| transactionStatus Declined | WayForPay → Krokul | Entry about the failed attempt in the feed | The payment did not go through |
| CHECK_STATUS | Krokul → WayForPay | Open expected payments | Once a day |
document.created. Each delivery has the x-crm-signature header, and your handler checks it against your secret.externalRef/api-upsert.payment/api-create with the deal cardUuid.No. serviceUrl points straight to Krokul, which checks the notice signature itself and returns a signed accept reply to WayForPay.
Yes, if the client email is passed in CREATE_INVOICE. Krokul takes it from the deal contact, and without an email the invoiceUrl link still appears on the deal.
WayForPay repeats it until it gets accept. Krokul also reconciles open payments with a CHECK_STATUS request once a day.
Krokul passes each document line as productName, productPrice and productCount, so the client sees on the payment page what the payment is for.
WayForPay repeats the serviceUrl notice until it gets a valid reply, for up to four days. WayForPay emails the invoice to the client only when the invoice contains the client email.
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.
WayForPay is a trademark of its owner. Krokul is not affiliated with WayForPay.