Skip to main content

Overview

Rotate the active settlement destination for a permanent active funding account. This operation does not create new payment details.

Authentication

string
required
Your merchant API key
string
required
Unique idempotency key for request deduplication

Path Parameters

string
required
Funding account ID.

Request Body

string
required
Settlement destination type. Allowed values depend on the funding account rail; see the matrix below.
string
Required for NGN_VIRTUAL_ACCOUNT funding accounts when type is ONCHAIN.
string
Required for NGN_VIRTUAL_ACCOUNT funding accounts when type is ONCHAIN.
string
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 by id; do not send rail in this request. Do not send NGN_PAYOUT for NGN_VIRTUAL_ACCOUNT funding accounts, and do not send ONCHAIN for CRYPTO_ADDRESS funding accounts. NGN_BALANCE credits the merchant’s NGN withdrawal balance and is valid only for NGN virtual accounts. CUSTOMER_NGN_BALANCE credits the funding account customer’s NGN balance; for crypto accounts it supports USDC and USDT only.

destination_bank

destination_bank is a nested object. Do not send dotted keys such as destination_bank.account_number. Before sending 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.
rate_id is rejected for permanent funding accounts.

Destination Shapes

Internal balance (NGN virtual account or crypto address)
Customer NGN balance
NGN virtual account to onchain settlement
Crypto address to NGN payout settlement

Request Example

Update NGN virtual account to onchain settlement

Response

Returns the funding account object with the new active settlement destination.