Reconciling cryptocurrency payments can present several challenges for merchants. Consider the following examples.
- A customer pays an invoice in full, but processing fees reduce the amount credited to the merchant;
- Several transactions are consolidated into a single payout, complicating the reconciliation of individual sales;
- A payment is confirmed on the blockchain, yet the corresponding transaction is missing from the gateway's records.
This guide explains how to reconcile invoices with blockchain transfers, verify gateway records and trace funds through to settlement. It also examines common discrepancies and how merchants can resolve them while maintaining an accurate audit trail.
What is crypto reconciliation?
Reconciliation is the process of comparing financial records from separate systems and investigating differences between them. For cryptocurrency payments, it establishes whether a customer settled an invoice, how much the gateway received, which fees were charged and where the proceeds went.
Payment reconciliation establishes receipt and settlement. Accounting treatment determines how transactions and balances are recognised, measured and presented under the applicable standards.
The four records needed to reconcile a crypto payment
-
Orders and invoices
The invoice is the starting point. It identifies the order, the sum due, the currency of account and the payment deadline. Where the merchant quotes a crypto amount, the record should preserve the token and network offered to the customer, together with the exchange rate and its validity period. -
The gateway transaction report
For crypto transaction reconciliation, the gateway records the payment it detected and how it was processed. Its transaction ID is particularly valuable because it provides a reference for status checks and enquiries. The report should also supply the asset received, gross amount, processing fee and currency credited to the merchant balance, subject to the provider's available fields. -
The blockchain record
Blockchain reconciliation begins with the transaction hash, which leads to the underlying on-chain transfer. Finance or operations staff should examine it on an explorer for the relevant network, confirming the receiving address, asset, amount, timestamp and transaction status. Token contract addresses warrant attention because assets with similar names can exist on the same network. -
Payout records and bank statements
A merchant that retains cryptocurrency should match the gateway withdrawal with the destination wallet's receipt. Where funds are converted to fiat, the reconciliation extends to the conversion statement and the bank statement. The relevant records include payout identifiers, exchange rates, fees, beneficiary details and the final amount deposited.
An example of payment and payout reconciliation
Suppose a retailer raises invoice INV-1042, connected to order ORD-1042, for $250. The customer chooses 250 USDC on Polygon and transfers the full amount.
For this example, assume that the merchant pays the withdrawal network fee separately and records it as an additional expense. The full 742.50 USDC therefore reaches the off-ramp provider; after conversion at the assumed rate and the $2 off-ramp charge, the bank receives $740.50.
To reconcile these payments, the merchant first needs to collect the relevant transaction records. The table below shows what information is required and where to find it.
Reconciliation template for the incoming payment and payout
|
Field |
Example |
Where to find it |
|---|---|---|
|
1. Order ID |
ORD-1042 |
Store or order-management record |
|
2. Invoice and amount due |
INV-1042, $250 or 250 USDC |
Invoice and checkout quote |
|
3. Expected payment destination |
Invoice-linked Polygon address |
Original payment request |
|
4. Gateway transaction ID |
GW-78621 |
Gateway transaction report |
|
5. Gateway status and time |
Confirmed, 5 Nov at 14.03 UTC |
Gateway history or status callback |
|
6. Network, token and contract |
Polygon, USDC, verified contract |
Checkout quote and blockchain explorer |
|
7. Transaction hash |
0x7b3a…9e21 |
Gateway record and explorer |
|
8. Actual amount received |
250.00 USDC |
On-chain token event and gateway report |
|
9. Fee and net currency credited |
2.50 USDC fee; 247.50 USDC credited |
Gateway fee report and merchant balance |
|
10. Settlement batch reference |
BATCH-1105-A, 742.50 USDC |
Merchant's payout allocation schedule |
|
11. Withdrawal and off-ramp reference |
WD-1106-09; $2 external charge |
Gateway withdrawal and conversion provider |
|
12. Bank reference and received amount |
BANKREF-6348; $740.50 |
Bank statement |
⚠️All IDs, dates, amounts and charges above are fictional. The abbreviated transaction hash serves as an illustration. The settlement batch identifier belongs to the merchant's internal schedule.
With these records in hand, the merchant can reconcile the payments and subsequent payout in four steps.
-
Match the invoice to the gateway payment
Begin with ORD-1042 in the store's order register. Find the corresponding gateway record using the order ID or invoice number and preserve GW-78621 as the transaction reference. Check whether the customer sent the requested asset before the payment window closed. A status such as confirmed should be supported by the gateway's own record rather than a customer screenshot. -
Verify the transaction on-chain
Search the full transaction hash on a Polygon explorer. Confirm that a transfer of 250 USDC reached the destination shown in the payment request. Check the token contract and the gateway's confirmation status. If the transaction includes several token events, record the event that belongs to the merchant payment.
-
Calculate the merchant credit
In this example, the payment ledger records 250.00 USDC gross − 2.50 USDC processing fee = 247.50 USDC net. The customer's invoice can be marked paid in full, with the processing fee recorded separately. A business accepting cryptocurrency through automatic conversion should also retain the conversion timestamp, rate and credited asset. -
Trace the withdrawal to the bank
The merchant's settlement schedule connects the 247.50 USDC credit to a second net receipt of 495 USDC. The combined amount is 742.50 USDC. An off-ramp provider converts that amount at the assumed rate, deducts $2 and sends $740.50 to the merchant's bank. The merchant retains both the gateway withdrawal reference and the separate provider's conversion reference.
Want to accept crypto payments on your website?

Finding a transaction without an order reference
Some crypto payments arrive with incomplete order information, making it difficult to determine which invoice they belong to. In these cases, merchants can use the available transaction records to identify the payment and establish its origin.
- Start with the gateway's transaction ID or the blockchain hash. Where neither is available, search recent records by asset, network, receiving address, amount and time.
- Compare the resulting candidates with open invoices and recently expired payment requests. Unique invoice addresses offer stronger evidence than an amount-and-time match involving a shared wallet.
- If the blockchain shows a completed transfer while the gateway report remains incomplete, obtain the full hash, token contract, address and confirmation details.
- Pass these to gateway support with the merchant account reference. Keep the receipt in an exceptions queue while the provider investigates, and document the outcome before assigning the money to an invoice.
How to investigate common reconciliation discrepancies
|
Discrepancy |
What to Check |
Who Resolves It |
|---|---|---|
|
Underpayment |
Amount due, token received, payment deadline and outstanding balance |
Customer support requests the balance; finance approves any adjustment |
|
Payment after invoice expiry |
Original quote, receipt time, applicable exchange rate and order status |
Payments team proposes treatment; finance authorises it |
|
Duplicate payment events |
Gateway ID, callback identifiers, transaction hash and transfer event index |
Engineering removes duplicate posting; finance checks the ledger |
|
Several payments in one payout |
Batch schedule, all net credits, withdrawal reference and bank receipt |
Treasury or finance matches the constituent transactions |
|
Fee-related differences |
Processing schedule, network charges, off-ramp fees and conversion rates |
Finance verifies deductions; provider investigates unexplained entries |
|
Transfer on-chain, absent from gateway |
Network, contract address, receiving address, confirmations and hash |
Gateway support with the integration engineer |
|
Payout awaiting bank receipt |
Withdrawal status, provider reference, beneficiary and bank posting date |
Treasury follows up with the provider and bank |
Maintaining an audit trail of manual decisions
Automated invoice matching resolves routine payments, while exceptions often involve a person deciding how funds should be allocated. An audit trail should identify the underlying evidence and show who approved the treatment, together with the date and reason.
Suppose a customer sends 240 USDC against the 250 USDC invoice. The payment record shows the 240 USDC receipt and an outstanding balance of 10 USDC. If the customer subsequently pays the remaining amount, attach the second gateway ID and transaction hash to the same invoice. If the merchant agrees to waive the shortfall, save the approval and enter the corresponding adjustment in the accounting system.
A complete case file includes the original invoice, gateway IDs, hashes, expected and actual amounts, supporting records, employee responsible and final disposition. Preserve the earlier status and record subsequent changes as separate events. This allows an auditor to follow the sequence from the initial discrepancy to its resolution.
Building a routine for daily and month-end reconciliation
Daily checks should compare the previous day's invoices with gateway receipts, identify duplicate events and verify the status of transfers awaiting confirmation. The exceptions queue should show an owner, age and next action for each unresolved item. Payment records can be grouped by asset and network to expose differences that would disappear in a combined fiat total.
Payout reconciliation should match withdrawals to their constituent net credits. Where assets pass through a conversion provider, retain its statement and the reference carried into the bank deposit. Differences caused by timing should remain visible as outstanding items until the receiving institution records the money.
Month-end checks should confirm opening and closing balances for every asset, reconcile unallocated deposits and review outstanding refunds. Finance should retain dated exports and evidence of the reconciliation review. For digital asset reconciliation, token quantities should be established before the business applies its accounting valuation methodology.
Automation can reduce the manual workload. Persist the order ID when creating a payment request, store gateway IDs alongside on-chain hashes and process status callbacks once per underlying event. Regularly compare the internal ledger with gateway exports so that a failed integration or missing notification surfaces during routine checks.
Reconciliation with 0xProcessing
0xProcessing provides merchant transaction histories, reporting exports and API-based payment status notifications. The platform supports incoming payment tracking and allows businesses to check transaction status through its API. Merchants can use this information alongside their order database and blockchain records to build a consistent payment register.
Its published terms describe processing commissions based on merchant turnover and cryptocurrency withdrawals subject to network charges. Merchants using a separate fiat conversion service should retain that provider's charges and statements as additional reconciliation records.
Frequently asked questions
What does “payment reconciliation” mean?
Payment reconciliation compares the amounts a business expected to receive with the payments recorded by its providers and financial accounts. In cryptocurrency, the process incorporates invoices, gateway credits and blockchain transfers, followed by withdrawals and bank deposits where applicable.
How do you reconcile payments?
Gather the invoices and gateway transaction report, then match each order to a confirmed blockchain transfer. Calculate gross receipts, processing fees and net balances. Finally, connect withdrawals with destination-wallet receipts or bank deposits and investigate outstanding differences.
What is an example of reconciliation?
A customer pays a 250 USDC invoice in full. The gateway records 250 USDC received, charges 2.50 USDC and credits the merchant with 247.50 USDC. The two amounts agree once the documented processing fee is included.
What is the first step in reconciliation?
Establish the original amount due and retrieve the invoice or order ID. Confirm the quoted token, network and expiry time. These details form the reference against which the gateway and blockchain records can be checked.


