Skip to main content
POST
Simulate stablecoin deposit
Simulation endpoints are available only outside production. For user-targeted requests, omit user_id when using a valid API key or session cookie; otherwise supply user_id. A supplied ID must match the authenticated user. Invalid credentials are rejected, and both credentials must identify the same user when supplied together. Signed API keys require their normal request-signature headers. Every user is automatically KYB-approved in development and staging; simulated applicant statuses do not change this admission policy.

Headers

X-Api-Key
string | null

Optional API key. Identifies the target user when user_id is omitted; signed keys also require request-signature headers.

Body

application/json

Non-production stablecoin deposit event to create for integration testing.

Non-production stablecoin deposit event to create for integration testing.

amount
string
required
Example:

"100.5"

chain
enum<string>
required

cNGN requires evm and uses Base, in development only.

Available options:
evm,
tron,
solana
symbol
string
required

Token symbol; cNGN credits the NGN wallet after the configured deposit fee.

Example:

"USDT"

blockchain_tx_hash
string | null

Optional transaction hash, preserved exactly in responses, completed details and webhooks. EVM: 0x plus 64 hex characters; TRON: 64 hex; Solana: base58 64-byte signature. Omit to generate a synthetic hash. Retry with the same idempotency key and body.

idempotency_key
string | null
Example:

"sim_crypto_dep_001"

user_id
string<uuid> | null

Required only when no API key or session is supplied. Must match authenticated identity.

Response

Simulated deposit created

data
object
required

Result returned after creating a non-production stablecoin deposit event.

status
enum<string>
required
Available options:
success