Address-Based Payment Matching

Overview

What it means and why it exists

Address-based payment matching assigns an incoming blockchain transfer to a merchant invoice or customer by using a destination address that is associated with that record.

How it works

The merchant or payment service allocates an address and records its ownership mapping. When a supported network shows a transfer to that address, the monitor checks chain, asset, amount and status, then links the event to the relevant invoice. Distinct per-invoice addresses can reduce ambiguity compared with sharing one static address.

Technical details worth understanding

Address-based matching must account for the possibility of multiple payments to one address, partial transfers and late deposits after an invoice expires. For ERC-20 tokens, the same EVM address can hold many token contracts, so matching still needs contract identity. Reused customer addresses may identify customers without a specific new invoice.

What can go wrong

A matching system that relies only on an address risks crediting wrong-asset transactions or donations against the wrong order. On some chains, memo/tag-based routing or account-creation requirements change the best matching model. Never infer payer identity only from destination or input addresses.

Practical checks

Before enabling address reuse, decide whether one address identifies a customer or a single invoice. A deposit to a shared address may be real but ambiguous, especially with multiple eligible orders. Track both candidate transfers and the explicit order attribution instead of automatically assigning every arrival to the latest open invoice.

Related concepts

Crypto Invoice, Crypto Payment Status, Crypto Checkout.

Further reading

OxaPay — Developer Documentation.