Invoice Destination Tag

Overview

What it means and why it matters

An invoice destination tag is an additional identifier required on some networks or custodial receiving systems to attribute deposits sent to a shared address. Some networks call a similar field a memo.

How it works in practice

The invoice presents both a receiving address and a destination tag. The payer includes the tag when sending funds. The recipient uses it to distinguish which customer should receive credit even though many deposits reach the same blockchain address. The exact field and supported format are network-specific.

Technical detail without the jargon

Not every blockchain transaction or wallet supports a destination tag. A wrong or missing tag may leave the transferred funds under the recipient’s custody but unmatched to the customer. Check whether the selected asset and network require a tag before showing payment instructions.

A deeper point to understand

The correct tag format depends on the network and custodian; a numeric destination tag cannot be assumed interchangeable with a free-form text memo. For some deposits, omitting a tag may still transfer value successfully on-chain. The operational loss is attribution, not necessarily blockchain execution, so recovery terms should say exactly which problem occurred.

Common mistakes and limitations

A generic QR code containing only an address can be insufficient. Do not fabricate a tag for networks that use different memo conventions, and never promise that a missing tag is always recoverable.

What to check in a real payment system

For networks that require tags or memos, display them prominently alongside the address and test QR interoperability. Explain missing-tag recovery policies in advance. Do not reuse a reference in a way that creates simultaneous ambiguous deposits across customer accounts.

Related concepts

Crypto Invoice, Transaction Hash, Crypto Payment Status.

Further reading

Bitcoin Developer Guide — Payment Processing.