Source-of-funds review asks what evidence supports the origin of a specific amount, not whether a wallet looks clean. The independent deliverable is a document-to-conclusion table that preserves missing evidence and avoids tactical advice.
What remains visible
ERC20 and TRC20 transfers can both require source context. The documents may look similar, but the transaction record and counterparty ecosystem differ.
What it does not prove
Documentation does not erase public-chain history. It can help explain a transaction, but it does not change what explorers show.
Evaluation checklist
- Define source of funds clearly.
- List documentation types without turning them into tactical advice.
- Link counterparty risk.
- Keep privacy claims secondary to evidence.
Source-of-funds document decision table
Match each record to the narrow conclusion it can support and keep identity, ownership, and transaction purpose separate.
Define the amount and period
State which funds and timeframe the record is meant to explain.
Classify the document
Separate transaction records, account statements, sale records, income records, and counterparty explanations.
Test continuity
Check whether dates, amounts, asset, network, and named parties form a coherent chain without filling gaps.
Filled evidence record
Source-of-funds document decision table snapshot: 2026-08-05. The worked record for source of funds crypto labels every synthetic or non-attributed specimen directly in the table.
| Evidence item | Worked record | Interpretation boundary |
|---|---|---|
| Public transaction record | Can support that a token amount moved between addresses at a time. | Cannot prove lawful origin, beneficial ownership, or economic purpose alone. |
| Platform or account statement | May connect an account-side event to a person or entity within the issuer's stated scope. | Authenticity, completeness, and external accounts may remain unverified. |
| Supporting commercial record | May explain why value was received when dates, parties, and amounts align. | Does not replace network or account evidence for the movement itself. |
Pass or hold criteria
For source of funds crypto, a missing decisive input remains unknown and blocks the affected conclusion; the source-of-funds document decision table never converts it to a silent pass or zero.
| Dimension | Pass condition | Hold or fail condition |
|---|---|---|
| Scope | Specific amount, asset, network, and period | General wallet narrative |
| Continuity | Dates and values reconcile with named gaps | Missing links are silently inferred |
| Conclusion | Limited to supported origin context | Promises exchange acceptance or compliance |
Next evidence layer
Counterparty Risk In USDT Transfers
Counterparty Risk In USDT Transfers adds risk guide context to source of funds crypto. Define regulated and unknown counterparties. Knowing a counterparty type does not prove final risk. It gives context that should be reviewed with wallet history, source documentation, and public-chain visibility.
Exchange Records And USDT Traceability
Exchange Records And USDT Traceability adds visibility guide context to source of funds crypto. Separate public explorer data from platform records. The existence of exchange records does not mean every reviewer has access to them. It means off-chain context can matter.
USDT Mixer Risk Signals
USDT Mixer Risk Signals adds core guide context to source of funds crypto. Check the scope and supporting evidence. Keep the conclusion within the available evidence.
USDT Mixer FAQ
USDT Mixer FAQ adds core guide context to source of funds crypto. Check the scope and supporting evidence. Keep the conclusion within the available evidence.
Source notes
The sources below clarify source of funds crypto terminology and the evidence limits described above. They do not verify private service operations or guarantee an outcome.
Related questions
What if several documents explain only part of the amount?
Record the covered portion and leave the remainder unresolved instead of averaging the gap away.
What if names differ across records?
Treat the mismatch as a follow-up identity or ownership question; do not assume the records belong to the same party.