Funding Accounts
Update funding account settlement destination
Rotate the settlement destination for a permanent active funding account
Overview
Rotate the active settlement destination for a permanent active funding account. This operation does not create new payment details.Authentication
Your merchant API key
Unique idempotency key for request deduplication
Path Parameters
Funding account ID.
Request Body
Settlement destination type. Allowed values depend on the funding account rail; see the matrix below.
Required for
NGN_VIRTUAL_ACCOUNT funding accounts when type is ONCHAIN.Required for
NGN_VIRTUAL_ACCOUNT funding accounts when type is ONCHAIN.Required for
NGN_VIRTUAL_ACCOUNT funding accounts when type is ONCHAIN.Allowed settlement destination types
This endpoint only updates permanent active funding accounts. The rail comes from the funding account identified byid; do not send rail in this request.
| Funding account rail | Allowed type values |
|---|---|
NGN_VIRTUAL_ACCOUNT | INTERNAL_BALANCE, ONCHAIN |
CRYPTO_ADDRESS | INTERNAL_BALANCE, NGN_PAYOUT |
NGN_PAYOUT for NGN_VIRTUAL_ACCOUNT funding accounts, and do not send ONCHAIN for CRYPTO_ADDRESS funding accounts.
destination_bank
destination_bank is a nested object. Do not send dotted keys such as destination_bank.account_number.
| Field | Type | Required |
|---|---|---|
account_number | string | Yes, for CRYPTO_ADDRESS funding accounts when type is NGN_PAYOUT. |
bank_code | string | Yes, for CRYPTO_ADDRESS funding accounts when type is NGN_PAYOUT. |
destination_bank, fetch supported banks with GET /v1/banks, then verify the account with POST /v1/banks/resolve. Use the verified bank_code and account_number in this request. Daya returns the resolved account_name in the funding account response.
Destination Shapes
Internal balance (NGN virtual account or crypto address)
NGN virtual account to onchain settlement
Crypto address to NGN payout settlement
Request Example
Update NGN virtual account to onchain settlement