How it works
1
Payment callback
WayForPay posts order fields + merchantSignature.
2
Payment record
A crm_order_payments row is created with amount and transaction status.
3
Status update
The order moves to "Confirmed" after a successful payment.
Signature verification
- Algorithm
- HMAC-MD5 over order fields
- Field
- merchantSignature
- merchantAccount
- required for validation
- Card data
- not stored
Security
- merchantSignature is verified before recording a payment
- The secret key is used only to sign — never returned in the UI
- Tied to the order by orderReference
- Sandbox generation of a signed test payload
Setup
- 1
Add the WayForPay adapter
Provide the secret key and merchantAccount; copy the callback URL.
- 2
Set the service URL
Put the generated endpoint in the merchant settings.
- 3
Validate the sandbox
Generate a signed test payload and confirm the signature.
Frequently asked questions
How is it different from LiqPay?
The signature is HMAC-MD5 over order fields (LiqPay uses base64 SHA1 over data), and a merchantAccount is required.
Can I test without a real payment?
Yes — sandbox validation generates a signed test callback without recording payments.
Connect WayForPay
Payments update the order status automatically.
Start for free