Verify native USDC contract, decimals and recipient before signing

The USDC symbol does not uniquely identify a token across chains

Wallets can display native USDC, bridged representations and unrelated tokens with similar names or icons. The safe identifier combines the selected blockchain and complete contract address, while the signed action must separately identify the recipient and amount. This is a verification and record-keeping method, not a prediction, payment instruction, legal opinion or promise of an account outcome.

Circle publishes official native USDC contract addresses for supported blockchains. The directory does not authorize a receiving service or guarantee that a route is supported. Users choosing a low-fee USDC route need a contract-and-chain check, not a recommendation based only on a ticker or logo.

Read the authenticated receiving instruction

Read the row from evidence to consequence. The evidence is: The receiving page should state asset, network, address and any current limits or memo requirements. Its limited consequence is: Issuer documentation cannot substitute for receiver acceptance. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Save a metadata-only snapshot of the fresh instruction. File account reference, asset, network, address, memo, minimum, expiry and warning. End the check at the stated boundary—Do not rely on a forwarded screenshot.

Match the blockchain explicitly

Read the row from evidence to consequence. The evidence is: The same hexadecimal address shape appears on many EVM-compatible chains. Its limited consequence is: Address appearance cannot identify the network carrying the token. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Compare wallet chain name and chain identifier with the receiving instruction. File wallet network, chain ID, receiver label, native gas asset and match result. End the check at the stated boundary—Stop on any unresolved network mismatch.

Compare the complete USDC contract

Read the row from evidence to consequence. The evidence is: A copied symbol and icon can be attached to a different token contract. Its limited consequence is: The issuer's full chain-specific contract is stronger evidence than display branding. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Compare every address character with Circle's current directory. File documented contract, wallet contract, selected chain, retrieval date and exact-match result. End the check at the stated boundary—Never accept a token contract supplied only by chat.

Decode decimals and the human amount

Read the row from evidence to consequence. The evidence is: Token transfers encode an integer amount interpreted using the token contract's decimal setting. Its limited consequence is: A raw integer copied without decimals can represent the wrong human-readable amount. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Confirm the wallet's decoded amount and contract metadata before signing. File raw amount, decimals, displayed amount, token contract and wallet warning. End the check at the stated boundary—Cancel if the wallet cannot decode the token action.

Separate approval from transfer

Read the row from evidence to consequence. The evidence is: An approval grants a spender authority while a transfer moves tokens to a recipient. Its limited consequence is: Signing an approval is not evidence that a deposit was paid. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Read the function, spender or recipient and allowance or amount. File function, token contract, spender, allowance, recipient, amount and reason. End the check at the stated boundary—Do not approve an unexplained or unlimited allowance.

Reconcile gas, receipt and account credit

Read the row from evidence to consequence. The evidence is: The chain's native asset pays gas while USDC movement appears in transaction events. Its limited consequence is: A successful receipt and an account credit remain separate records. No adjacent account, payment or legal conclusion is implied.

The practical check is straightforward: Track gas debit, token event and authenticated account status. File hash, gas asset, fee, receipt status, token event, invoice and account credit. End the check at the stated boundary—Do not resend after a delayed service credit.

What the named source establishes and leaves unresolved

Circle's issuer-controlled contract directory supports exact chain-and-contract comparison for native USDC. The verification card combines that identity evidence with decoded wallet fields and receiver instructions.

The directory does not verify a wallet interface, a private receiving address, a bridged representation or SignalBet availability. Current authenticated account instructions are required.

Close the record with a bounded decision

The card includes receiver instruction, chain ID, official contract, decimals, decoded action, recipient or spender, amount, gas, receipt and account state. All mismatches have a stop decision.

SignalBet is 18+ only where lawful. Stable value does not remove gambling or routing risk; set a disposable-money ceiling and never send another transfer to chase a delayed credit.

Use the responsible-play centre, the editorial policy and the guide library for related safeguards.

Read the authenticated receiving instruction: Follow-up review

A useful handoff for Stablecoin payment safety names the open issue, evidence owner and next date beside account reference, asset, network, address, memo, minimum, expiry and warning. Save a metadata-only snapshot of the fresh instruction. Do not rely on a forwarded screenshot. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Match the blockchain explicitly: Follow-up review

A useful handoff for Stablecoin payment safety names the open issue, evidence owner and next date beside wallet network, chain ID, receiver label, native gas asset and match result. Compare wallet chain name and chain identifier with the receiving instruction. Stop on any unresolved network mismatch. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Compare the complete USDC contract: Follow-up review

A useful handoff for Stablecoin payment safety names the open issue, evidence owner and next date beside documented contract, wallet contract, selected chain, retrieval date and exact-match result. Compare every address character with Circle's current directory. Never accept a token contract supplied only by chat. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.

Decode decimals and the human amount: Follow-up review

A useful handoff for Stablecoin payment safety names the open issue, evidence owner and next date beside raw amount, decimals, displayed amount, token contract and wallet warning. Confirm the wallet's decoded amount and contract metadata before signing. Cancel if the wallet cannot decode the token action. The follow-up stores no password, one-time code, recovery code, seed phrase or private key and never treats an unresolved field as permission to continue.