List available event types
Retrieve the complete list of event types your subscriptions can listen to, along with human-readable descriptions.Response
boolean
true when the request succeeded.object[]
Array of event type descriptors.
Event type reference
Standardized events
These are the recommended event types for new integrations.Legacy events
These event types are preserved for backward compatibility with existing integrations. New integrations should prefer the standardized events above.Webhook payload structure
All events share the same top-level payload structure:data object contains fields specific to the event type. For transaction events, it contains the full transaction record. For wallet events, it contains wallet balance details. For customer events, it contains customer profile fields.
Example payloads
transaction.success
transaction.success
wallet.credit
wallet.credit
customer.created
customer.created
card.linked
card.linked
test.webhook
test.webhook
Signature verification
Every webhook request includes headers you should use to verify that the payload originated from TagPay and has not been tampered with.Headers
Your private key is the same key used for API authentication. You can retrieve it from the TagPay dashboard under API Keys.
Verifying with Node.js
Use thex-webhook-signature header for new integrations. It combines the timestamp with the payload to prevent replay attacks.
verify-webhook.js
Verifying the legacy signature
If you are on the legacy callback URL system, verify using thex-glide-signature header and SHA-512:
verify-legacy-webhook.js
Retry policy
TagPay attempts delivery up to 3 times per event before marking the delivery asfailed.
After all attempts are exhausted, you can manually trigger another delivery using the replay endpoint.
