Payment Verify v2

Client-only check: recipient + reference(s) + expected amount → polls RPC getSignaturesForAddress(recipient, limit 20, commitment finalized) with before-pagination, then getTransaction(jsonParsed, maxSupportedTransactionVersion 0, commitment finalized) per signature. Reference must be a 32-byte non-signer read-only key bound to a transfer instruction (F2); failed txs (meta.err) are skipped (F3). No dependencies, no keys, no backend. Nothing is published.

USDC SPL mint is network-specific (F8): mainnet-beta EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v (6 decimals), devnet test-USDC 4zMMC9sEqfkz6Fv5k9bwb7BG3QkDPz8eeMzmxfUX8b8 (6 decimals). SOL = native lamports (9 decimals).

Recipient address (base58, must decode to 32 bytes) Reference(s) (one or comma-separated several base58 pubkeys; match = ANY of them bound to the transfer ix) Expected amount (0 allowed per spec; SOL max 9 decimals, USDC max 6) Currency RPC endpoint (also selects the USDC mint network)

Press Check payment.

Result PENDING

status: PENDING (not checked yet)

signature: -

slot: - | time: -

expected: - | found: -

commitment: finalized | confirmation: -

CONFIRMED = a reference (32-byte, non-signer, read-only) bound to the transfer instruction and amount matches (last transfer, F9). MISMATCH = reference bound but amount differs. PENDING = not found in scanned signatures (press Search deeper, F4).

Details log

Press Check payment.

Read-only RPC: getSignaturesForAddress + getTransaction (commitment finalized). RPC errors are shown honestly as error: <msg> — no fake CONFIRMED.

This device

links: 0 | verifies: 0 (0/0/0) | last check: never