The short answer
No wallet connection. No personal details. Your selections stay in this tab and reset when the page reloads.
Your pre-transfer checklist
0 of 6 reviewedCheck a statement only when you have an answer. Completion is a reminder, not a safety certification.
Kept only in this page session. No wallet details are requested.
Use two different kinds of source
Use issuer documentation to identify the token. Use the receiving platform's own current instructions to establish acceptance. An issuer listing does not tell you whether a particular service supports that asset.
Compare the exact token and network, not the logo. For a service's conditions, save or note the version you actually read; a search snippet is not the terms you are agreeing to.
Do not continue if the answer is missing
- The domain cannot be independently established.
- The recipient's token or network is ambiguous.
- The total charge or withdrawal conditions are unclear.
- The service asks for a seed phrase or private key.
- You would need to violate applicable law or a service restriction to proceed.
Completion is a prompt to decide, not an approval
The checklist does not inspect a service's backend, test its solvency or predict a transaction outcome. You can finish every visible check and still face contract, custody or operational risks.
An optional partner link is an external commercial path, not the result of this checklist. The destination's terms apply separately.
Already sent USDT or USDC on the wrong network?
- Do not repeat the transfer. Keep the transaction hash, actual chain, token identifier and the original deposit instructions.
- Check the transaction on that chain. Separate a failed or missing chain transaction from a successful transfer that the recipient has not credited.
- Ask the receiving platform through its independently verified contact route whether that specific token/network can be recovered. Recovery is not guaranteed.
- Do not disclose a recovery phrase or pay an unsolicited unlock fee. A person contacting you after a public post has not established that they represent the recipient.
What a route preview can and cannot verify
The network choices on StableMatrix are educational subjects, not a live partner catalogue. The partner link does not transmit a wallet, create a quote or reserve a route. Read the external offer afresh before relying on it.
| Preview item | A useful check | Not established |
|---|---|---|
| Asset and network | Match exact input/output identifiers with issuer documents and receiver instructions. | Live provider acceptance from a ticker alone. |
| Amount and fees | Reconcile gross input, deductions and net output in the same units. | A fixed execution price unless the actual terms bind it. |
| Timing | Identify when each stage starts and which exceptions apply. | Guaranteed processing or withdrawal. |
| Support | Verify the exact domain and its published contact independently. | An official Telegram account from its display name. |
Can transfers be tracked or frozen after an intermediary?
Public chain records and personal attribution are different questions. An intermediary does not erase earlier transfers. Whether a person can be identified requires additional evidence, rather than assuming either perfect traceability or perfect anonymity.
Tether and Circle describe issuer restrictions in their terms. Mixing does not establish an exemption from those controls or force a receiving platform to accept a deposit. The checklist cannot predict a freeze or certify a service's compliance.
A brand-name search is not an official support channel
- Treat a domain, app name, Telegram handle or review title as an unverified lead until the operator relationship is established from an independent source.
- Do not enter credentials, seed phrases or private keys into a result reached from a brand query.
- Do not rely on a legitimacy or scam verdict based only on a title, ranking or logo.
- For a wrong-network issue, use the recipient's authenticated contact route and keep the transaction hash.
Before sending USDT to an unfamiliar service
Identify the exact token, network, operator or contract, and receiving conditions before considering a transfer. StableMatrix has no verified mixing route to recommend; a mixer label is not a substitute for those checks.
Do not use a deposit to test an unverified offer. Never disclose a seed phrase or private key. If the operator, output token or failure process is undocumented, stop rather than treating the missing information as reassurance.
| Question | Evidence needed | Stop when |
|---|---|---|
| Which USDT? | Issuer-listed contract and network. | Only a ticker or logo is supplied. |
| Who controls the route? | Named operator or deployed contract permissions. | A label replaces the custody explanation. |
| What is the output? | Exact token, network and recipient crediting rule. | The result is described only as USDT. |
| What is the privacy claim? | Observer, mechanism, evidence and limitations. | An adjective is treated as a guarantee. |
Verify the route and the support channel
A support statement must name the exact asset, network, accepted contract or mint, minimum amount and confirmation rule. A USDT or USDC logo does not establish these details. StableMatrix does not maintain a live provider catalogue.
Authenticate the hostname and published support channel independently before entering credentials or sharing transaction details. A Telegram handle, search result or copied logo is not proof of an operator relationship. Without that evidence, a branded login or support claim remains unverified.
| Field | Evidence to match | Not established |
|---|---|---|
| Asset and network | Issuer or protocol identifier and receiving network. | Support for every token with the same ticker. |
| Amount and timing | Minimum, confirmation threshold and timing endpoint. | A universal limit or instant credit. |
| Contact | Exact domain and authenticated published channel. | A Telegram handle or copied logo. |
| Failure path | Written refund, review and unsupported-route conditions. | Guaranteed recovery after a mismatch. |
Source notes
Each reference has its own last-check date. That is not its publication date. Follow the live document for current terms and identifiers.
- CircleUSDC contract addressesIssuer-listed mainnet identifiers. A token listing is not a service endorsement. Document date not recorded. Checked: 2026-09-21.
- TetherSupported protocols and integration guidelinesExact issuer-listed asset/network combinations, including discontinued protocols. Document date not recorded. Checked: 2026-09-21.
- CircleUSDC TermsRedemption conditions, blocked addresses, third-party platform boundaries and transfer risks. Document date not recorded. Checked: 2026-09-20.
- Ethereum.orgBlock explorersPublic transaction, block and address data, rather than proof of a person's identity. Document date not recorded. Checked: 2026-09-20.
- TetherToken terms and risk disclosuresIssuer rights, redemption conditions, restrictions, and third-party wrapped-token risks. Document date: 2026-02-26. Checked: 2026-09-20.