Skip to main content
POST
/
v1
/
sandbox
/
deposits
Create a sandbox deposit
curl --request POST \
  --url https://api.sandbox.daya.co/v1/sandbox/deposits \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '
{
  "funding_account_id": "<string>"
}
'

​
Overview

This sandbox-only endpoint creates a mock deposit for an existing funding account and runs it through the same processing pipeline as a real deposit:
  • Deposit creation
  • Settlement to internal balance, onchain payout, or NGN payout
  • Webhook dispatch
Use this to validate deposit processing and webhook handling before going to production. Create the receive instruction with /v1/funding-accounts, then pass the returned funding account id to this endpoint.
This endpoint is not available in production. Calls in production return 403 Not available in production.
For end-to-end guidance (recommended flow, what to validate, and common flagging scenarios), see Sandbox testing.

​
Authentication

​
X-Api-Key
string
required
Your merchant API key

​
Request Body

​
funding_account_id
string
required
Funding account ID to simulate a deposit for. Daya uses the funding account to decide whether the simulated deposit is NGN or crypto, and where settlement should go.Example: 6b0e8400-e29b-41d4-a716-446655440000

​
Request Examples

curl --request POST \
  --url https://api.sandbox.daya.co/v1/sandbox/deposits \
  --header 'X-Api-Key: YOUR_SANDBOX_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "funding_account_id": "6b0e8400-e29b-41d4-a716-446655440000"
  }'

​
Response

Returns a confirmation message. Use /v1/deposits and webhook events to track the simulated deposit.
  • message: Human-readable status message

​
Error Responses

This endpoint may return:
  • 400: Invalid request
  • 401: Unauthorized
  • 403: Not available in production
  • 404: Funding account not found
  • 500: Internal server error

​
Next Steps

Webhooks Overview

Verify your webhook handling with sandbox events

Sandbox testing

Recommended end-to-end sandbox flow + common flagging scenarios