Reference-Based Payment Matching

Overview

Reference-Based Payment Matching starts with a reference issued or recorded before payment. When a transaction or provider callback arrives, the application resolves that reference to the intended invoice, order, customer, or account.

References can be on-chain, such as a Destination Tag or memo, or off-chain, such as an OxaPay track ID and order ID. Off-chain references still need a trusted link to the verified blockchain transaction.

A good reference is unique within its namespace and difficult to guess when privacy matters. Sequential identifiers can reveal volume or allow users to copy another payer’s reference unless the system validates destination and session ownership.

References should have explicit lifecycle states: issued, active, used, expired, canceled, and manually resolved. Reusing one reference for unrelated payments can create duplicate credit or make reconciliation impossible.

The final matcher should combine reference evidence with Amount-Based Matching, asset, network, address, and transaction state. A reference selects the candidate business record; it does not prove that the economic transfer satisfies every requirement.

References that appear in URLs, QR codes, or public blockchain fields should not contain sensitive customer data. A random opaque identifier can map internally to the business record without revealing email, account number, or order details. Access controls should protect the reverse lookup because the reference alone may be visible to third parties.

The reference service should prevent simultaneous issuance of the same active identifier and should retain consumed references long enough to reject replay. Deleting old references too early can make a late transaction look like an entirely new payment.