Payment intent + transaction
Compare intent with receipt
The sample values are placeholders. Use a real Arc Testnet hash and intent only if you already have them from a wallet or ArcScan.
Read-only Arc Testnet RPC
Payment Intent Receipt Matcher
Paste a payment intent JSON and an Arc Testnet transaction hash. The matcher fetches the receipt, decodes pinned USDC Transfer logs, and reports whether the onchain transfer matches the expected recipient, token, and amount. It never connects to a wallet, handles private keys, signs, or broadcasts.
No wallet connection
No private keys
No signing
No transaction broadcast
Read-only RPC only
Match evidence
Read-only verdict
Status: not_checked
USDC Transfer logs
Match states
What the matcher reports
matchReceipt succeeded and a USDC Transfer log matches the intent recipient, token, and amount.
mismatchReceipt succeeded but no USDC Transfer log matched the intent.
revertReceipt exists and status is 0x0.
not_foundNo receipt yet for this hash.
unknownRPC unavailable, wrong chain, malformed envelope, or ambiguous status.
Chain5042002 / 0x4cef52
Machine-readable output
Match evidence JSON
Trust boundary
What this does not prove
- A
matchonly means the receipt contains a USDC Transfer with the expected recipient and amount. It does not prove business acceptance, offchain fulfillment, or product settlement. - The matcher relies on the public Arc Testnet RPC and the pinned USDC address. A different token contract will not match even if the call data looks similar.
- The matcher does not estimate gas, simulate calls, submit transactions, or retry failed payments.
- Use the receipt viewer and transaction status playground for earlier/later stages of the payment lifecycle.