Legacy Migration Guide

Overview

Older Daya integrations may still use onramp, offramp, payout, and legacy webhook names. Those routes remain available for existing integrations, but new receive-money work should use funding accounts and deposits. This guide shows what to use instead. No removal date has been published for the legacy routes. Daya will share sunset dates before any legacy route is removed.

What Changed

Older integration path	Current path
Create or list NGN onramps with `/v1/onramps`	Create or list funding accounts with `rail: NGN_VIRTUAL_ACCOUNT`
Create or list crypto offramps with `/v1/offramps`	Create or list funding accounts with `rail: CRYPTO_ADDRESS`, `asset`, and `chain`
Reconcile onramp or offramp deposits by legacy receive-flow IDs	Reconcile deposits with `/v1/deposits` and store `funding_account_id`
Track settlement delivery with payout events	Track receive-flow settlement with `deposit.*` events
Send money to a bank recipient through payout-style flows	Create a transfer with `/v1/transfers`
Track old webhook names such as `deposit.settled`	Use current names such as `deposit.completed`

Receive NGN

Use a funding account with rail: NGN_VIRTUAL_ACCOUNT when a customer needs NGN bank details.

{
  "type": "TEMPORARY",
  "rail": "NGN_VIRTUAL_ACCOUNT",
  "customer": {
    "customer_id": "650e8400-e29b-41d4-a716-446655440000"
  },
  "currency": "NGN",
  "amount": 50000,
  "settlement_destination": {
    "type": "INTERNAL_BALANCE"
  }
}

The response includes instructions with the bank account details to show your customer. When money arrives, the deposit response includes funding_account_id. Use these endpoints:

Task	Endpoint
Create NGN payment details	`POST /v1/funding-accounts`
List NGN payment details	`GET /v1/funding-accounts?rail=NGN_VIRTUAL_ACCOUNT`
Reconcile received money	`GET /v1/deposits`

Receive Crypto

Use a funding account with rail: CRYPTO_ADDRESS when a customer needs to send USDC or USDT to Daya.

{
  "type": "TEMPORARY",
  "rail": "CRYPTO_ADDRESS",
  "customer": {
    "customer_id": "650e8400-e29b-41d4-a716-446655440000"
  },
  "asset": "USDC",
  "chain": "BASE",
  "settlement_destination": {
    "type": "NGN_PAYOUT",
    "rate_id": "550e8400-e29b-41d4-a716-446655440000",
    "destination_bank": {
      "account_number": "0690000031",
      "bank_code": "044"
    }
  }
}

The response includes instructions with the wallet address. When crypto lands, the deposit response includes funding_account_id, asset, chain, and tx_hash. Use these endpoints:

Task	Endpoint
Create crypto payment details	`POST /v1/funding-accounts`
List crypto payment details	`GET /v1/funding-accounts?rail=CRYPTO_ADDRESS`
Reconcile received money	`GET /v1/deposits`

Payouts and Transfers

Payouts are legacy read-only records for settlement delivery from older receive-money flows. Do not build new send-money workflows on /v1/payouts. Use:

Goal	Current API
Send NGN or USD to a bank account	`POST /v1/transfers`
Save reusable bank or wallet details	`POST /v1/recipients`
Move collection balance to withdrawal balance	`POST /v1/merchant/balance/transfer`
Send stablecoins on-chain from withdrawal balance	`POST /v1/merchant/balance/withdraw`

If you only need to inspect older payout records, use the legacy List payouts and Get payout routes.

Webhook Names

Use the current webhook names when creating or updating webhook filters.

Older name	Current name
`deposit.flagged`	`deposit.requires_review`
`deposit.settled`	`deposit.completed`
`transfer.flagged`	`transfer.requires_review`
`transfer.settled`	`transfer.completed`
`withdrawal.settled`	`withdrawal.completed`
`virtual_account.created`	`funding_account.active`
`onramp.created`	`funding_account.active`
`onramp.failed`	`funding_account.failed`

Existing endpoints that receive all events may temporarily receive both the current and legacy event name for the same state change. See Legacy Webhooks for the compatibility list.

Migration Checklist

Create new receive instructions with /v1/funding-accounts.
Store funding_account_id from funding account responses and deposit payloads.
Reconcile NGN and crypto payments from /v1/deposits.
Replace payout-based send flows with /v1/transfers or merchant withdrawals.
Update webhook filters and handlers to use current event names.
Keep legacy route support only for existing customers or historical records.

Legacy Routes

The following routes remain documented for older integrations:

Resource	Routes
Onramps	`POST /v1/onramps`, `GET /v1/onramps`, `GET /v1/onramps/{id}`
Offramps	`POST /v1/offramps`, `GET /v1/offramps`, `GET /v1/offramps/{id}`
Payouts	`GET /v1/payouts`, `GET /v1/payouts/{id}`

Legacy receive-flow routes are compatibility routes. Funding accounts, deposits, transfers, and withdrawals are the current integration path.

Getting Started

Core Concepts

Guides

Rates & Chains

Customers

Funding Accounts

Transfers

Deposits

Recipients

Banks

USD Virtual Accounts

USD Virtual Account Deposits

Merchant Balance

Merchant Funding

Webhooks

Legacy API

Overview

What Changed

Receive NGN

Receive Crypto

Payouts and Transfers

Webhook Names

Migration Checklist

Legacy Routes

​Overview

​What Changed

​Receive NGN

​Receive Crypto

​Payouts and Transfers

​Webhook Names

​Migration Checklist

​Legacy Routes

Overview

What Changed

Receive NGN

Receive Crypto

Payouts and Transfers

Webhook Names

Migration Checklist

Legacy Routes