OPay
Verification available
Transaction-status only; not top-ups. Only selected fields are signed. Refunded is encoded as t/f. Quoted or escaped values in signed fields are rejected to prevent ambiguous interpolation.
Signature scheme
- Algorithm
- HMAC-SHA3-512
- Signature
- sha512 (JSON body)
- Signed data
- documented transaction-status fields
- Encoding
- hex
- Timestamp
- Signed field; no freshness guarantee
Configure verification
Create or edit a source, enable Verify signature and search for OPay. The source remains active independently of this switch. Save the provider and its configuration together.
Copy the exact ingress URL from your source when configuring the sender. Save every required field together; saved configuration is encrypted and never returned in source reads.
- OPay secret key (required).
For API clients, signing_secret contains the configured value directly.
Inspect the recorded valid, invalid or not-checked signature result after sending a new event. Changing configuration does not change historical results; replay preserves the original bytes and does not re-sign the webhook.
Capture, delivery and acknowledgement
Verification availability describes the inbound validator. The original incoming query string is not retained or forwarded, and the destination URL or path can differ from the signed request. Acklane does not re-sign deliveries; schemes using that original context may not be verifiable again at the destination.
With async enabled, a failed signature may still be captured and retained, but does not become eligible for signature-on delivery. Replay requires current source eligibility, preserves the event ID and original content, and creates a separate delivery history.
Async capture returns 202 after durable acceptance. A provider that requires HTTP 200 or a special acknowledgement may retry; an implemented validator does not establish compatibility with its acknowledgement rules. No real provider sandbox delivery is certified by this catalog.