Daya sends merchant webhooks for funding account, deposit, transfer, withdrawal, and customer verification lifecycle changes.Every webhook uses the same envelope:
event tells you what changed, id identifies the webhook event for idempotency, and data is the public API response shape for the resource that changed.
Webhook events are documented here at the event-name level. The data object follows the same public response object returned by the corresponding resource endpoint.
Settlement has started and may be waiting on conversion or delivery
deposit.requires_review
No
Deposit needs review before it can continue
deposit.completed
Yes
Deposit reached its settlement destination
deposit.failed
Yes
Deposit permanently fails
deposit.reversed
Yes
A completed deposit was reversed
Deposit payloads for NGN and crypto receive flows include funding_account_id. When a developer fee is configured, deposit payloads include developer_fee and customer_amount. The developer fee is deducted before the final customer amount is calculated; it is not added as a separate charge. Track the merchant-facing settlement lifecycle with deposit.* events.
Customer verification has been submitted for review
customer.verification.approved
Yes
Customer verification has been approved
customer.verification.rejected
Yes
Customer verification has been rejected
funding_account.* and customer.verification.* events use the same webhook envelope as money movement events. Funding account payloads use the public funding account response shape.
When a customer sends NGN to a funding account’s virtual account, the incoming money is a deposit. The payment detail is the funding account; the money movement is tracked with deposit.* events.
Step
Event
Notes
Funds arrive
deposit.received
Daya records the NGN deposit.
Settlement starts
deposit.processing
Sent when delivery or conversion work begins.
Deposit completes
deposit.completed
Funds have reached the configured settlement destination.