A transaction hash is a lookup reference, not proof that a particular order was paid. Verification must connect a successful transfer to the quoted asset, network, merchant recipient, exact amount, allowed time window and required confirmation state.
Check more than the explorer headline
An explorer may show a successful transaction that paid another address, used a different token with the same symbol or occurred long before the invoice existed. For token payments, verify the supported contract and transfer evidence rather than just the transaction’s destination field. Native transfers and contract token transfers have different structures. Coinvay uses network-specific verification, including canonical receipt and confirmation checks for supported EVM payments.
Match the payment to the business obligation
For example, a customer buying a 60.00 USD product may paste a genuine USDC hash from a different purchase. Your order system should not accept it because it looks real. Use the saved Coinvay invoice ID and authenticated status, or a correctly signed settlement event, and compare the expected order and amount. Exact quoted integer quantities matter; rounding a small difference away can make matching ambiguous.
Keep uncertainty visible
Pending, failed, mismatched and provider-unavailable states need different customer messages. A missing RPC response does not prove nonpayment, while a mined transaction with insufficient confirmations is not yet the required settled state. Do not let a support agent bypass these distinctions solely because a screenshot looks convincing. Retain the submitted hash and investigation reason while waiting for reliable evidence. In Sandbox, exercise wrong-recipient and wrong-network cases so staff learn that a successful unrelated transaction must still be rejected.
Practical checklist
- Verify the quoted network, asset contract, exact amount and recipient together.
- Check canonical success, timing and the required confirmation state.
- Fulfill from trusted invoice evidence and a durable order mapping, not a customer screenshot.
Common questions
Can a successful transaction still be invalid for my invoice?+
Yes. It may be on another network, use another asset, pay a different recipient or fall outside the quote’s allowed window.
Should I mark an invoice paid while the RPC provider is down?+
No. Preserve an awaiting-verification state and retry or investigate through trusted evidence. Provider unavailability is not proof of settlement.
Sources and further reading
Primary references and Coinvay product documentation. Check the linked pages for current details.
AI-assisted drafting, published by Coinvay. Examples are illustrative. Read our editorial approach.