# Reconcile crypto payments without losing the order context

> Crypto reconciliation connects each business order to its invoice, exact on-chain receipt and any later outgoing adjustment. Keep USD accounting values and received token quantities as separate fields rather than treating one as a substitute for the other.

Publisher: Coinvay | Published: 2026-10-27 | Updated: 2026-10-27 | Category: Merchant operations
Canonical: https://coinvay.com/articles/crypto-payment-reconciliation

Match orders, invoices and exact crypto receipts while keeping refunds, fulfillment exceptions and accounting values distinct.

## Preserve the complete chain of identities

Start with the internal order ID, Coinvay invoice ID, quoted asset, network, destination and exact token amount. Add the verified transaction reference and confirmation state when payment completes. Customer-supplied hashes, screenshots and public wallet activity can help investigation, but they do not establish that a transfer paid the correct order. A useful reconciliation record explains both the business obligation and the blockchain evidence.


## Keep totals meaningful

Suppose an invoice priced at 80.00 USD settles in a particular amount of ETH. The quoted USD price describes the sale, while the exact ETH receipt describes the asset received. Later market movement does not change the historical token quantity. Network fees paid by the sender and a separately authorized refund should not be silently folded into the original receipt amount. Use the current dashboard’s verified-payment records and exports as inputs to your own accounting workflow, not as automatic jurisdiction-specific tax treatment.


## Investigate exceptions explicitly

Create review reasons for wrong networks, unmatched amounts, duplicate claims, late transfers, provider outages and changed orders. Keep testnet receipts outside the live reconciliation dataset; the merchant Sandbox already uses separate records. For outgoing contractor transfers, retain the approval and sending transaction as a distinct expense-side workflow. When a downstream product grant fails, record a fulfillment problem rather than recording a second payment. This separation makes customer support clearer and helps avoid double-counting during retries.


## Practical checklist

- Store the order, invoice and verified transaction identities together in durable records.
- Retain original USD totals and exact crypto quantities without floating-point conversion.
- Use an exception queue for unmatched transfers, refunds and failed fulfillment.

## Questions and answers

### Should every wallet deposit count as a Coinvay sale?

No. A wallet can receive unrelated funds. Count a sale only when the transfer is correctly matched and verified for its invoice.

### Are testnet receipts included in live payment totals?

Sandbox records are separate from live payment analytics and invoice usage. Preserve that distinction when creating your own exports or reports.

## Sources and further reading

- [Coinvay merchant API documentation](https://coinvay.com/docs)

## Related guides

- [Direct Wallet Settlement vs. Platform Balances](https://coinvay.com/articles/direct-wallet-settlement-vs-platform-balances)
- [Wrong Network at Crypto Checkout: Prevention and Support](https://coinvay.com/articles/crypto-checkout-network-mistakes)
- [Crypto Quote Expiry: What Happens When the Timer Runs Out?](https://coinvay.com/articles/crypto-quote-expiry)

Published by Coinvay with AI-assisted drafting. Product claims were checked against the implementation and linked primary sources. Provider facts and pricing can change; verify the current terms before choosing a service. Examples are illustrative, not customer results. No ranking or AI citation is guaranteed.