RamboPay Knowledge Base
Webhook Signature Verification for Payment Events
How merchants can verify payment callbacks before fulfilling orders.
Never trust an unsigned payment callback
Payment webhooks trigger fulfillment, account activation, delivery, or invoice settlement. If a merchant accepts callbacks without verification, a fake request can mark an unpaid order as paid.
RamboPay signing model
Each webhook includes a timestamp and HMAC SHA-256 signature. The merchant recreates the signature with the webhook secret, timestamp, and raw request body. If the signature or timestamp fails validation, the order should stay unpaid.
Operational advice
Store event IDs, reject duplicated paid events, compare amount and currency with the original order, and make fulfillment idempotent. Payment systems should be boring in the best possible way.
FAQ
Does RamboPay delete real order details?
No. Real order details should remain in the merchant system. RamboPay helps control the channel-facing payment summary.
Is this bypassing payment-channel risk controls?
No. The platform supports lawful commercial privacy, not prohibited goods, deceptive descriptions, or disguised transactions.