USDC / SERVICE PREFLIGHTPRECHECK
Before you send USDC, confirm the asset, direction, both networks, total cost and current terms. Treat privacy language as a claim until a dated source supports it.
01 / DECISION AID
Tick each check when you have a current, attributable answer. The handoff action appears only after every row is reviewed.
Review each line against a current source before you rely on it.
ROUTE EVIDENCE
Choose the observed label closest to the route you need to check. The readout keeps its evidence boundary visible; it does not confirm a current route, direction, pair or fee.
NETWORK FIT
Confirm asset, direction, source network and destination in the current interface before relying on a route.
Verify withCurrent interface; date required
FEE BOUNDARY
Separate service, network and destination-side costs. Record the source and date beside each mutable figure.
Verify withService, network and destination costs; date required
02 / WHAT WE CAN CONFIRM
The rows below show what was observed, what was attributed to a service and what still needs a current check.
READER DECISION GUIDE
Confirm the token contract, direction, both networks, limits, full quote and destination address in the current interface.
Decision guide
USDC, USD Coin, online, service and platform describe the question, not a guaranteed live route.
Treat each visible label as a prompt for verification. It does not prove a current pair, direction, settlement quality, custody standard, trust property or legal suitability.
| Field | What to confirm | Ready when |
|---|---|---|
| Asset | USDC token contract | The contract matches the asset you hold |
| Direction | Deposit asset -> payout asset | The displayed direction matches your task |
| Networks | Source and destination | Both endpoints accept the selected networks |
| Quote | Amount, limits and every fee | The complete current quote is visible |
| Support | Failure and contact path | The process is documented for this route |
Match the token contract, direction, source and destination networks, quote and destination address in the current interface.
Open the current provider flow and record the pair, direction, quote and date before relying on the label.
Decision guide
Seven USDC labels were visible in the dated first-party observation.
On 2026-08-13 the observed labels were ERC20, Arbitrum, AVAX C-Chain, Optimism, Solana, Base and Algorand. The labels identify interface entries only; they do not prove a current pair, direction, availability or fee.
| Observed label | It tells you | It does not establish |
|---|---|---|
| ERC20 / Arbitrum / Optimism / Base | The label appeared in the interface | A live pair, direction or current fee |
| AVAX C-Chain | The label appeared in the interface | Current availability or settlement |
| Solana | The label appeared in the interface | Destination support or address validity |
| Algorand | The label appeared in the interface | Current limits or successful payout |
Observed 2026-08-13. Recheck the exact pair and direction before use.
Use the list as a starting point, then verify the exact route and terms at the point of use.
Recheck the selected pair, direction and current quote on the date of the transaction.
Decision guide
A current USDC minimum is not supplied by the observed route labels.
Do not infer a minimum, maximum or free-use condition from a network selector. Keep service, network and destination-side costs separate when reading a quote.
| Field | Record | Do not infer from |
|---|---|---|
| Minimum | Exact pair and current lower limit | A network selector |
| Maximum | Exact pair and current upper limit | A general service label |
| Service cost | Rate and fixed charge | A low-fee claim |
| Network cost | Source and payout network charges | The asset ticker |
| Total | All costs plus quote time | A single advertised percentage |
Read the exact pair's current minimum and maximum and save the complete fee breakdown with its date.
Check limits and total cost in the current order flow immediately before relying on them.
Decision guide
The dated USDC observation covers a web interface only.
An app listing or mobile wrapper needs its own evidence for version, supported routes, custody and data terms. Do not transfer web availability or privacy wording to an app by assumption.
| Check | Required result | Stop when |
|---|---|---|
| Publisher | The store listing links to the official provider | The publisher cannot be verified |
| Version | Version and update date are current | Only an undated download is available |
| Route | The same pair, direction and networks appear | The app and web flow differ without explanation |
| Funds | Custody and failure handling are documented | The app adds an unexplained funds path |
| Data | App-specific collection and retention terms are available | Only web terms are shown |
Verify the official app listing, current version, supported pair and data terms before using an app.
Compare the app and web route screens on the same date and record any difference.
Decision guide
A USDC route label does not establish trust, legality or privacy performance.
No trusted-provider verdict follows from a route label. Review custody, account requirements, data handling, operational limits and jurisdiction separately, and keep a current source beside every mutable statement.
| Area | What to verify | Evidence needed |
|---|---|---|
| Custody | Who controls funds and for how long | Current workflow and failure terms |
| Identity | Account and identity requirements | Current provider terms |
| Data | Collection, retention and deletion | Current privacy wording |
| Operations | Limits, support and failure handling | Documented current process |
| Jurisdiction | Rules that apply to the user and route | Relevant current legal information |
Stop when the decision depends on a trust or privacy claim that has no attributable current source.
Check the provider's current terms and the rules that apply to the route before acting.
03 / TRUST CHECKS
Privacy language cannot erase custody, sanctions, exchange-screening or jurisdiction risk. If a claim would change your decision, require a fresh primary source.
04 / NEXT STEP
Once every preflight row is checked, the action inside the decision frame becomes available. You can also apply the evidence checklist first.
Reader preflight
