Overview
The Daya API is built around a set of core concepts that work together to handle fiat-crypto conversion, cross-border transfers, and merchant balance management.Resource Model
Public webhooks follow the resource a merchant creates or reconciles, not the internal provider engine Daya uses to execute it.| Merchant-facing concept | Public resource | Rails / implementation detail | Webhook family |
|---|---|---|---|
| Onramp | Funding account | NGN_VIRTUAL_ACCOUNT. Created through /v1/funding-accounts. | funding_account.* for provisioning, deposit.* when money lands |
| Offramp | Funding account | CRYPTO_ADDRESS. Created through /v1/funding-accounts with asset and chain. | funding_account.* for provisioning, deposit.* when crypto lands |
| Inbound NGN or crypto | Deposit | NGN bank transfer or crypto deposit received through a funding account. | deposit.* |
| Inbound USD to a bank account | USD account deposit | ACH or wire payment received into a USD virtual account. | deposit.* |
| Internal balance to NGN/USD bank | Transfer | Merchant-created bank send through /v1/transfers. | transfer.* |
| Stablecoin or crypto wallet send | Withdrawal | Merchant withdrawal from withdrawal balance to an on-chain address. | withdrawal.* |
Use
/v1/transfers and transfer.* webhooks for merchant-initiated bank sends. Use deposit.* webhooks to track incoming money and settlement into Daya.Funding Accounts
How customers receive funds into Daya
Deposits
Inbound NGN and crypto received through funding accounts
Onramps
Collect NGN from customers
Offramps
Collect stablecoins from customers
Transfers
Send NGN or USD to bank recipients (ACH, wire, SWIFT)
USD Virtual Accounts
USD virtual accounts for tier-2-verified customers
Merchant Balance
Dual-balance model with collection and withdrawal balances
Rates
Firm FX quotes with buy/sell sides and defined validity windows