Skip to main content

Ripple (XRP)

Ripple uses integer destination tags for deposit identification at shared addresses.

Destination Tags​

Destination tags work like memos — they allow multiple customers to deposit to a shared address. The tag identifies which customer the deposit belongs to.

How It Works​

  1. Create a Ripple address in your vault
  2. Assign a unique destination tag for each customer via the Memos API
  3. Share the address + tag with the customer
  4. Incoming deposits include the tag in the webhook payload — match it to the customer

Create a Destination Tag​

curl -X POST \
     -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "addressId": "hN8qR2tVwX4yZ6aBcDeF3g",
       "memo": "123456",
       "name": "Customer 123456 Deposits"
     }' \
     https://api.carabaas.com/api/v1/memos

Sending with Destination Tag​

curl -X POST \
     -H "Authorization: Bearer $TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "orderId": "a5b6c7d8-e9f0-4a1b-2c3d-4e5f6a7b8c9d",
       "vaultId": "kR7mNpX2wQvL9sYhBjD4eT",
       "destination": "rRecipientAddress...",
       "network": "ripple-mainnet",
       "asset": "c144",
       "amount": "100.00",
       "options": {
         "memo": "123456"
       }
     }' \
     https://api.carabaas.com/api/v1/transactions
warning

Many exchanges require a destination tag for XRP deposits. Sending without the correct tag may result in lost funds.

See Also​