VA - XLM and XRP: Deposit not Detected

When receiving deposits from the blockchain to a deposit address linked to a Virtual Account, XLM and XRP require a matching "message" and a "destinationTag," respectively, to identify which Virtual Account the deposit should be credited to.

This is due to a limitation in XRP and XLM, where a single deposit address is used. Because of this, the Virtual Account ledger must identify the correct deposit based on the required identifier.

Required Identifiers for Deposits

For Virtual Accounts, deposits to XLM and XRP addresses require the following fields:

• XLM – message
• XRP – destinationTag

These identifiers ensure that funds are correctly assigned to the respective Virtual Account.

📘

Note

• The intended message and destinationTag fields for XLM and XRP are provided when Generating a deposit address for a Virtual Account.
• Find the XLM and XRP Account Creation Guide with a deposit address in this article.

How It Works

For XRP and XLM, only a single blockchain address is generated per currency. The differentiation occurs through the "message" (XLM) or "destinationTag" (XRP) assigned to the Virtual Account. This ensures deposits are routed correctly within the Virtual Account system.

Troubleshooting

If a deposit is not detected:

• Verify the sender included the correct message (XLM) or destinationTag (XRP).
• Confirm that the deposit was sent to the correct address.
• Check if the transaction was successfully confirmed on the blockchain.
• Ensure the Virtual Account is active and not frozen.

Important Information

• Transactions sent with an incorrect or missing message or destinationTag cannot be credited to the Virtual Account ledger.
• All blockchain transactions are final and cannot be reversed.