Specify Source Tag in XRP transactions

Today, we are excited to announce the release of XRP Source Tag Support in Palisade, extending our comprehensive XRP transaction capabilities by enabling you to specify source tags for all XRP Ledger transaction types.

This new feature completes our XRP tagging functionality, allowing you to identify and track the origination of XRP transactions alongside the existing destination tag support, providing enhanced traceability and operational control for your XRP Ledger operations.

📘

Source tags are optional 32-bit unsigned integers (0 to 4,294,967,295) that help identify transaction originators

Why

In institutional and high-volume XRP operations, tracking transaction flow requires both source and destination identification. While destination tags help identify transaction recipients, source tags provide essential origination tracking—critical for compliance, auditing, and operational transparency in enterprise environments.

What are XRP Source Tags?

Source tags are optional 32-bit unsigned integer identifiers that can be attached to XRP Ledger transactions to indicate the originator or source of the operation. They provide a standardized way to track where transactions originate from within your organization's wallet infrastructure.

Key Features

• Universal XRP Support: Source tags available on all supported XRP transaction types
• Complete Transaction Coverage: Works with Payment, TrustSet, OfferCreate, OfferCancel, AccountSet, SignerListSet, and AMM operations
• XRP Specification Compliant: Follows official XRP Ledger protocol standards
• Type-Safe Implementation: Proper validation and conversion across the platform
• Enhanced Traceability: Combine with destination tags for complete transaction flow tracking

Supported Transaction Types

Source Tag Support Available on:

• Payment Transactions: Transfer transactions with source identification
• TrustSet Operations: Trust line management with origination tracking
• Offer Management: OfferCreate and OfferCancel with source attribution
• Account Configuration: AccountSet operations with source tracking
• Multi-Signature: SignerListSet operations with origination control
• AMM Operations: AMMCreate, AMMDeposit, and AMMWithdraw with source tags

API Examples

Create a Payment Transaction with Source Tag:

POST /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/transfer
Content-Type: application/json
{
  "destination_address": "rPT1Sjq2YGrBMTttX4GZHjKu9dyfzbpAYe",
  "symbol": "XRP",
  "qty": "100",
  "config": {
    "source_tag": "1337",
    "destination_tag": "418"
  }
}

Create an XRP Offer with Source Tag:

POST /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/xrp/offers
Content-Type: application/json
{
  "taker_gets": {
    "asset": "XRP",
    "value": "1000"
  },
  "taker_pays": {
    "asset": "USD",
    "issuer": "rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq",
    "value": "100"
  },
  "source_tag": "2025"
}

TrustSet Operation with Source Tag:

POST /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/xrp/trustset
Content-Type: application/json
{
  "limit_amount": {
    "asset": "USD",
    "issuer": "rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq",
    "value": "10000"
  },
  "source_tag": 1001
}

AMM Operations with Source Tag:

POST /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/xrp/amm/create
Content-Type: application/json
{
  "amount": {
    "asset": "USD",
    "issuer": "rhub8VRN55s94qWKDv6jmDy1pUykJzF3wq",
    "value": "1000"
  },
  "amount2": {
    "asset": "XRP",
    "value": "1000"
  },
  "trading_fee": 500,
  "source_tag": "3001"
}

Implementation Details

Type Safety: Source tags are validated as 32-bit unsigned integers throughout the system, ensuring compliance with XRP Ledger specifications.

Frontend Integration: Source tag fields are available in the customer UI transaction forms with proper validation and helper text.

Backend Processing: Both Go-based transaction service and Java-based XRP orchestrator handle source tags consistently across all transaction types.

How to Get Started

1. Update Your Integration: Include the optional source_tag field in your XRP transaction requests
2. Define Source Tag Strategy: Establish organizational conventions for source tag usage (e.g., wallet groups, departments, or processes)
3. Enhanced Monitoring: Use source tags alongside destination tags for complete transaction flow tracking
4. Compliance Integration: Leverage source tags for audit trails and regulatory reporting

API Endpoints

Source tag support is available through all existing XRP transaction endpoints:

• Transfer transactions: /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/transfer
• XRP-specific operations: /v2/vaults/{vault_id}/wallets/{wallet_id}/transactions/xrp/*

For complete API documentation, visit our developer documentation.

Best Practices

• Consistent Numbering: Use systematic source tag numbering schemes for easier tracking
• Documentation: Document your source tag conventions for operational clarity
• Combined Usage: Leverage both source and destination tags for comprehensive transaction traceability
• Validation: Ensure source tag values fall within the valid range (0 to 4,294,967,295)
• Audit Integration: Include source tags in your compliance and audit reporting workflows