> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daya.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Legacy Webhooks

> Webhook event names kept temporarily for older integrations

## Overview

New integrations should use the event names documented in [Webhook Events](/api-reference/webhooks/events).

Some older integrations may still receive previous event names during the migration window. These names are delivered only for compatibility and are not accepted when creating or updating `event_types`.

If your endpoint receives all events, you may see both the current event and its legacy counterpart for the same resource transition.

## Event Name Mapping

| Current event              | Legacy event              |
| -------------------------- | ------------------------- |
| `deposit.requires_review`  | `deposit.flagged`         |
| `deposit.completed`        | `deposit.settled`         |
| `transfer.requires_review` | `transfer.flagged`        |
| `transfer.completed`       | `transfer.settled`        |
| `withdrawal.completed`     | `withdrawal.settled`      |
| `funding_account.active`   | `virtual_account.created` |
| `funding_account.active`   | `onramp.created`          |
| `funding_account.failed`   | `onramp.failed`           |

The funding account aliases apply to NGN receive instructions that older integrations knew as onramps or virtual accounts. Crypto funding accounts do not emit onramp aliases.

## Migration Guidance

Use the current event names in webhook filters and application logic. Keep handling legacy names only if you already receive them in production.

When you no longer need the legacy names, update your webhook handler to process only the current event names.

For route-level migration steps, see the [Legacy Migration Guide](/legacy/migration-guide).