Single-Transaction Multi-Invoice Payment

Overview

What it means and why it matters

A single-transaction multi-invoice payment uses one blockchain transaction to cover several distinct merchant invoices. Whether this is supported depends on the blockchain and provider’s matching model.

How it works in practice

On a UTXO chain, a sender may include several outputs in one transaction, each paying the address associated with an invoice. On some contract-based chains, one transaction can emit multiple transfer events. The processor must associate each specific output or event with its invoice and keep the shared transaction hash.

Technical detail without the jargon

A hash alone does not uniquely identify an individual invoice payment in this situation; use output index or event log index plus chain identity. A transaction with one lump-sum output to a shared address can be ambiguous without a separate allocation reference.

A deeper point to understand

For a UTXO transaction, outputs—not the total sum of all inputs—are the relevant evidence for what reached each merchant destination. For contract tokens, inspect successful transfer logs from the allowed token contract. This difference is essential when one transaction contains unrelated change, fee payments or other movements beside the invoice payments.

Common mistakes and limitations

Do not credit every invoice with the full value of the shared transaction. Aggregating outputs for reporting is legitimate, but the sum of individually credited amounts must not exceed eligible value actually transferred.

What to check in a real payment system

Verify that your data model permits multiple invoice allocations for one transaction hash but never duplicates one output or log event. During batch reviews, reconcile the sum credited to invoices with actual value at the corresponding destinations.

Related concepts

Crypto Invoice, Transaction Hash, Crypto Payment Status.

Further reading

Bitcoin Developer Guide — Payment Processing.