> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rc.cleverhub.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Simulate Deposit API Reference

> Simulate an inbound deposit into a Treasury Account in the sandbox, so you can verify that your integration receives and credits incoming funds correctly.

The simulate deposit endpoint mimics an inbound bank transfer into one of your [Treasury Accounts](/platform-overview/clever-concepts/treasury-accounts). Use it to confirm that your integration receives the deposit, credits the correct account, and updates the Incoming and Available balances, all without moving real funds.

<Note>
  This is a **sandbox testing endpoint**. It is available on the sandbox base URL (`https://api.cleverhub.co/api`) and has no production equivalent. For the sandbox and production base URLs, see the [v1 introduction](/api/v1/introduction#base-urls).
</Note>

<Tip>
  For AUD Treasury Accounts you can simulate a deposit through the **TestBank** simulator instead of calling this endpoint. See the [deposit flow](/platform-overview/clever-concepts/treasury-accounts#deposit-flow).
</Tip>

***

## Simulate a deposit

<Note>
  `POST /v1/simulate_deposit`
</Note>

Credits a simulated inbound transfer to the Treasury Account matching `account_number`.

### Headers

<ParamField header="app-id" type="string" required>
  A unique identifier assigned to your application. See [where to find `app-id` and `secret-key`](/platform-overview/clever-concepts/treasury-accounts#where-to-find-app-id-and-secret-key).
</ParamField>

<ParamField header="secret-key" type="string" required>
  A secure token associated with your `app-id`.
</ParamField>

### Body parameters

<ParamField body="account_number" type="string" required>
  The Treasury Account number to credit. Find it on the account's **Account Details** tab in the Merchant Portal.
</ParamField>

<ParamField body="amount" type="string" required>
  The deposit amount. For JPY accounts, specify whole yen.
</ParamField>

<ParamField body="remitter_name" type="string">
  The simulated sender's name.
</ParamField>

<ParamField body="remitter_bank_name" type="string">
  The simulated sender's bank name.
</ParamField>

<ParamField body="remitter_branch_name" type="string">
  The simulated sender's branch name.
</ParamField>

<ParamField body="remarks" type="string">
  A free-text note that appears against the transaction.
</ParamField>

<Info>
  For JPY accounts, enter `remitter_name`, `remitter_bank_name`, and `remitter_branch_name` in **half-width katakana**. This matches the Zengin network's own formatting, so the simulated transaction reads the same way a real one would.
</Info>

### Code example

<CodeGroup>
  ```bash cURL theme={null}
  curl --request POST \
    --url https://api.cleverhub.co/api/v1/simulate_deposit \
    --header 'app-id: YOUR_APP_ID' \
    --header 'secret-key: YOUR_SECRET_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
    "account_number": "3451385",
    "amount": "10000",
    "remitter_name": "ﾃｽﾄﾆﾕｳｷﾝﾅ",
    "remitter_bank_name": "ｼﾞ-ｴﾑｵ-ｱｵｿﾞﾗ",
    "remitter_branch_name": "ﾃｽﾄｼﾃﾝ",
    "remarks": "Testing deposit flow"
  }'
  ```
</CodeGroup>

Once the call succeeds, the deposit appears in the Treasury Account's transaction history and the Incoming and Available balances update, exactly as they would for a real inbound transfer.

<Tip>
  A Postman collection can be imported to run this request directly. It uses the environment variable `v1_url` for the base URL, so set that before sending.
</Tip>


## Related topics

- [Clever Connect FAQ](/platform-overview/clever-concepts/faq.md)
- [Treasury Accounts](/platform-overview/clever-concepts/treasury-accounts.md)
- [Multi-Currency Payout API Reference (v2)](/api/v2/payout.md)