HookLens Docs

Feature

Signatures Verified Automatically

Providers use vastly different security models. For example, Paystack uses HMAC SHA512, while Flutterwave uses a custom verification hash header. HookLens abstracts this complexity entirely.

Pluggable Signature Verification

The architecture dictates a strict Strategy Pattern for verification. Every provider plugin implements a standard interface. The ingestion route dynamically invokes the correct strategy based on the endpoint configuration.

interface SignatureVerifier {
  providerName: string;
  verify(payload: string, headers: Record<string, string>, secret: string): boolean;
}

Implementation Targets

  • Paystack: Computes HMAC SHA512 of the raw payload using the secret key and compares it to the x-paystack-signature header.
  • Flutterwave: Compares the verif-hash header directly against the developer configured secret hash.
  • Monnify: Computes HMAC SHA512 of the payload and compares it to the monnify-signature header.