Mock Stablecoin Deposits

The sandbox environment provides an endpoint to simulate incoming stablecoin deposits for testing. This allows you to test the full deposit flow without sending real on-chain transactions.

📘

This mock deposit endpoint is sandbox-only and returns HTTP 200 with no body on success. Completion is notified via webhook as PAYMENT_IN_COMPLETED.


Stablecoin Deposit

Simulates an incoming stablecoin deposit arriving at your Caliza wallet. You provide the beneficiary, wallet address, amount, and network directly.

Endpoint: POST /v1/transactions/sandbox/crypto-deposit

curl -X POST "https://api.sandbox.caliza.com/core-api/v1/transactions/sandbox/crypto-deposit" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer {{ACCESS_TOKEN}}" \
  -d '{
    "beneficiaryId": "{{BENEFICIARY_ID}}",
    "walletAddress": "{{WALLET_ADDRESS}}",
    "amount": 100.0,
    "network": "TRON",
    "currency": "USDC"
  }'
FieldTypeRequiredDescription
beneficiaryIdstringYesThe beneficiary ID to credit the deposit to
walletAddressstringYesThe destination wallet address
amountnumberYesThe deposit amount
networkstringYesThe blockchain network. One of: ETH, TRON
currencystringYesThe stablecoin currency. One of: USDC, USDT
fromAddressstringNoThe on-chain origin of the deposit (random when omitted). Use it to complete a microtransfer ownership proof
travelRuleobjectNoSimulates the sender VASP's Travel Rule message for the deposit — see Testing Travel Rule in Sandbox

travelRule object

FieldTypeRequiredDescription
withMessagebooleanNotrue (default) simulates a VASP-originated deposit whose Travel Rule message arrives; false simulates a self-hosted origin with no message
originatorNamestringNoThe sender name declared in the message (defaults to a test value)
beneficiaryNamestringNoThe recipient name declared in the message — defaults to the account's registered name; a divergent value fails the beneficiary name check

Did this page help you?