Provider verification #
The integration verifies incoming signatures and timestamps using HesabPay’s server-side verification endpoint and the API key for the matching environment. Do not invent a local HMAC formula, derive a signature from the merchant PIN, or disable verification to clear a dashboard warning.
Order evidence #
Verified signatures authenticate a notification; payment processing also needs the matching order/session, transaction reference and amount evidence. Repeated notifications must not pay or fulfill the order twice.
If authentication is unavailable, the receiver can reject the request temporarily. Keep the order pending and review redacted logs. Do not report an authentication failure as a successful payment.
