Generic Webhook — Architecture
What is Generic Webhook?
Generic Webhook is HyperVerge's centralised system for delivering event notifications (webhooks) to client servers. When something happens in a KYC flow — a transaction completes, a reviewer makes a decision, a user opens a link — the client's server needs to know. Generic Webhook is the system that sends that notification reliably.
Instead of each product building its own webhook-sending logic, they all plug into this one system. It handles delivery, retries, signing, routing, and logging centrally.
The two important services
| Service | Repo | What it does |
|---|---|---|
| Configuration API | gitlab.com/hvlabs/post-processing/ind/generic-webhook | Internal CRUD API. Stores each client's webhook URL, headers, HMAC secret, and routing rules in DynamoDB. |
| Delivery Service | gitlab.com/hvlabs/post-processing/global/generic-webhook | AWS Lambda triggered by SQS. Reads configs from DynamoDB, signs payloads, and POSTs to client webhook URLs. |
Both services share the same DynamoDB table. The Configuration API writes to it; the Delivery Service reads from it.
See also:
- Flow — How webhooks are delivered end to end.
- Engineering — Codebase structure, Redshift schemas, env vars.
- API Reference — Configuration API request/response specs.