Invoice ID

Overview

Context and purpose

It can be opaque and globally or tenant-scoped, while the customer-facing invoice number can follow a separate human-readable or legal sequence. The ID should remain immutable across status changes, revisions, payment attempts, and document rendering. When implementing Invoice ID alongside Invoice Number, the invoice should remain distinct from its payment sessions so late transfers, refunds, credits, and exchange-rate changes do not rewrite the original commercial document. A secure ID avoids exposing sequential business volumes or customer information. It can be a UUID, database identifier, provider track ID, or another unique value. The same commercial obligation can have several document versions but one stable root invoice identity, or it can use separate IDs linked through revision relationships. External payment providers generate their own invoice or track identifiers. These should be mapped to the merchant invoice ID rather than replacing it.

How it works

An invoice ID is a stable identifier used to locate one invoice across merchant records, API calls, customer support and payment events. It must be unique within the relevant scope, but need not contain customer-identifying data.

Practical checks and failure points

Never treat knowledge of an invoice ID as authorization to read or modify the invoice; validate tenant ownership.

Related concepts

Invoice Merchant Reference · Invoice Reconciliation