> ## Documentation Index
> Fetch the complete documentation index at: https://developers.uqpay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Travel Rule for deposits

> Submit originator information when a deposit arrives flagged with need_travel_rule.

[Stablecoin Account API Publisher Disclaimer](/stablecoin-account/v1.6/guide/stablecoin-account-api-publisher-disclaimer)

Some incoming deposits require the sender's (originator's) Travel Rule information before they can proceed. The [Deposit webhook](/stablecoin-account/v1.6/webhooks/deposit) tells you when: the event's `data` includes `"need_travel_rule": true`. Deposits without the flag need no action.

## When you receive `need_travel_rule: true`

<Steps>
  ### Collect the sender's details

  From the deposit notification, keep the `from_address` and `network` — the submission must match that deposit. Then gather the originator's Travel Rule data from your user: wallet custody type, whether the address belongs to them or a third party, and beneficiary details where required. The field rules are the same `meta_data` schema used for withdrawals — see [Travel Rule compliance](/stablecoin-account/v1.6/guide/travel-rule-compliance) for every field and its conditions.

  ### Submit the deposit sender

  Call [Submit Deposit Sender Travel Rule](/stablecoin-account/v1.6/api-reference/create-deposit-sender) with the deposit's source address and network:

  ```bash theme={null}
  curl -X POST https://api-sandbox.uqpaytech.com/api/v1/ramp/wallet_address/deposit-sender \
    -H "x-auth-token: YOUR_API_TOKEN" \
    -H "x-idempotency-key: $(uuidgen | tr '[:upper:]' '[:lower:]')" \
    -H "Content-Type: application/json" \
    -d '{
      "source_address": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7",
      "network": "TRX",
      "meta_data": {
        "wallet_type": "hosted",
        "address_party": "third_party",
        "beneficiary_information": {
          "entity_type": "individual",
          "first_name": "John",
          "last_name": "Doe",
          "country": "sg",
          "city": "Singapore",
          "vasp_id": "I1QNLP",
          "vasp_name": "Binance"
        }
      }
    }'
  ```

  A successful response returns `data: null` — acceptance is signalled by `code: 200`.

  ### Wait for the deposit to proceed

  Once accepted, the flagged deposit can proceed, and later deposits from the same source address will not be flagged again. Track the order to completion via the [Deposit webhook](/stablecoin-account/v1.6/webhooks/deposit) or [Retrieve Deposit](/stablecoin-account/v1.6/api-reference/retrieve-deposit).
</Steps>

## How deposit-sender entries are stored

Deposit-sender records are kept separately from your withdrawal address book. To review them, call [List Address Book](/stablecoin-account/v1.6/api-reference/list-address-book) with `address_kind=deposit_sender`. Submitting again with the same `source_address` and `network` updates the existing entry rather than creating a duplicate.

## Related

* [Submit Deposit Sender Travel Rule API](/stablecoin-account/v1.6/api-reference/create-deposit-sender)
* [Travel Rule compliance](/stablecoin-account/v1.6/guide/travel-rule-compliance) — the `meta_data` field rules
* [Deposit webhook](/stablecoin-account/v1.6/webhooks/deposit)
* [Receive deposits](/stablecoin-account/v1.6/guide/receive-deposits)