Skip to main content
Zentra sends webhook notifications for various events in your account. This page shows common event families and representative payload shapes, not a reviewed schema bundle for every tenant and rail combination.
Treat event names and fields here as implementation guidance. Exact event availability and payload shape can vary by tenant capability, provider path, and rollout phase.

Event Structure

All webhook payloads follow this structure:

Virtual Account Events

virtual_account.created

Triggered when a virtual account is successfully created.

virtual_account.credited

Triggered when a payment is received in a virtual account.

virtual_account.closed

Triggered when a virtual account is closed.

Transfer Events

transfer.pending

Transfer initiated and pending processing.

transfer.processing

Transfer is being processed by the bank.

transfer.completed

Transfer successfully completed.

transfer.failed

Transfer failed to process.

Payment Events

payment.pending

Payment created and awaiting customer action or downstream completion.

payment.successful

Payment completed successfully.

payment.failed

Payment failed.

Card Events

card.created

Card successfully issued.

card.transaction

Transaction made with the card.

card.locked

Card has been locked.

card.unlocked

Card has been unlocked.

KYC Events

kyc.completed

KYC verification completed.

kyc.failed

KYC verification failed.

Customer Events

customer.created

New customer created.

customer.updated

Customer information updated.

Wallet Events

wallet.credited

Wallet credited with funds.

wallet.debited

Wallet debited.

Handling Events

Next Steps

Configure Webhooks

Set up webhook endpoints

Verify Signatures

Secure your webhooks

Handling Guide

Best practices

Test Events

Test in sandbox