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

# GET /dac/v1/xrp-dt-memo — XRP Destination Tag Memo

> Generate a unique XRP destination tag to route incoming deposits to the correct sub-account when multiple accounts share one on-chain address.

The XRP Ledger uses destination tags — numeric identifiers appended to a shared address — to distinguish individual recipients when multiple accounts share a single on-chain address. If your platform receives XRP deposits, you must include a unique destination tag with each payment instruction so Finrock can credit the correct sub-account. Use this endpoint to generate a new unique destination tag memo for XRP.

## Request

**Method:** `GET`
**URL:** `https://api.finrock.io/dac/v1/xrp-dt-memo`

## Example Request

```bash theme={null}
curl --request GET \
     --url https://api.finrock.io/dac/v1/xrp-dt-memo \
     --header 'accept: application/json'
```

## Response

A `200` response returns a unique destination tag value that you should include in the `address_tag` field when constructing XRP payment instructions for a depositor. A `400` response indicates a problem processing the request.

<ResponseField name="200" type="object">
  Contains the generated XRP destination tag value to use in payment instructions.
</ResponseField>

<ResponseField name="400" type="object">
  Returned when the destination tag cannot be generated.
</ResponseField>

<Warning>
  Every XRP deposit must include the correct destination tag. Deposits sent without a destination tag, or with an incorrect tag, may not be automatically credited and will require manual intervention to reconcile.
</Warning>