Skip to main content

​
Overview

New integrations should use the event names documented in Webhook 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 eventLegacy event
deposit.requires_reviewdeposit.flagged
deposit.completeddeposit.settled
transfer.requires_reviewtransfer.flagged
transfer.completedtransfer.settled
withdrawal.completedwithdrawal.settled
funding_account.activevirtual_account.created
funding_account.activeonramp.created
funding_account.failedonramp.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.