Some blockchain networks use shared wallet addresses where multiple users receive funds at the same address. To identify the specific recipient, these networks rely on additional metadata — commonly referred to as a memo, destination tag, or payment ID — attached to each transaction.

Examples of such networks include:

• XRP (destination tag)
• Stellar (memo)
• EOS (memo)

Sumsub Travel Rule supports these networks natively. You can include the memo or tag value when submitting a Travel Rule data exchange transaction, ensuring that the correct end-user is identified on both the originator and beneficiary side.

How to submit Travel Rule transaction with memo or tag

When creating a Travel Rule transaction via the API, use the counterparty.paymentMethod.memo field to pass the memo, tag, or payment ID associated with the counterparty wallet address.

You can submit a Travel Rule transaction using the following methods:

• Submit transaction for existing applicants
• Submit transaction for non-existing applicants

The counterparty.paymentMethod.memo field is optional in general but required for networks where the receiving address is shared among multiple users (for instance, exchanges or custodians). It carries the metadata needed to identify the specific end-user behind a shared wallet address.

Request example

In the following snippet, the counterparty receives funds at a shared XRP address. The destination tag 83927461 identifies the specific user:

"counterparty": {
  "paymentMethod": {
    "type": "crypto",
    "accountId": "rDsbeomae4FXwgQTJp9Rs64Qg9vDiTCdBv",
    "memo": "83927461"
  }
}

The memo value is included in the Travel Rule data exchange and transmitted to the counterparty VASP as part of the standard flow.