Multi-Transaction Payment

Overview

What it means

A multi-transaction payment settles one commercial obligation using several blockchain transfers instead of one. This can occur intentionally or when a customer sends only part of the expected amount and completes it later.

How it works

The payment system associates multiple TxIDs or token transfer events with one invoice, verifies each network and asset, calculates the credited amount in consistent units and prevents duplicate counting. It must define whether partial amounts may be combined, within what time window and with what fee or rate assumptions.

Understanding the technical details

The matching engine should accumulate verified credits rather than simply count transactions. Each credit needs its own identity—such as chain, transaction hash and token log index—and the invoice must define permitted combinations. When prices are quoted in fiat but paid in crypto, determine whether all partial payments use the original locked rate or their individual observed rates. Otherwise two customer payments can sum to different obligations in different system components.

Common failures and limitations

One transaction can contain multiple token events, and repeated webhook notifications must not be counted as separate payments. Network changes, late top-ups and small overpayments need explicit allocation rules; avoid mixing unrelated customer deposits.

Related concepts

Crypto Invoice, Crypto Checkout, Crypto Payment Link.

Further reading

OxaPay — Integration documentation.