Payment-to-Order Reconciliation

Overview

What it means

Payment-to-order reconciliation verifies that incoming payment records correspond to the correct commercial orders and that each order has received exactly the credit to which it is entitled.

How it works

Systems match payment-provider invoice IDs, merchant order IDs, blockchain references, asset, network, amount and status. They handle one-to-many cases such as several transfers paying one order and many-to-one provider batches with explicit allocation records. Exceptions flag missing, duplicate, partial and unexpected payments.

Understanding the technical details

An effective reconciliation report includes orders without payments, payments without orders and orders with too many payments. It does not merely count successful transactions. Build deterministic joins using merchant ID, order ID, provider invoice ID and on-chain event ID, with explicit manual rules for exceptions. For an order paid in installments, preserve every component transfer and the rate policy used. Test against replayed webhooks and duplicate screenshots because those are common sources of false paid status. Keep a daily snapshot of unresolved exceptions and their ages; a zero-difference total can still hide two offsetting errors. Review a sample of matched pairs rather than trusting totals alone.

Common failures and limitations

Never match purely on amount and minute: two unrelated orders can have identical values. A duplicated webhook can falsely inflate totals. A successful chain transfer does not always correspond to a valid order after expiration.

Related concepts

Crypto Checkout, Crypto Refund, Merchant Crypto Payment.

Further reading

OxaPay — Developer documentation.