Crypto Source-of-Funds Checklist for Lenders and Compliance Teams
A practical operating checklist for crypto source-of-funds reviews, focused on scoping, wallet control, transaction-path clarity, and audit-ready reviewer records.
Most crypto source-of-funds reviews do not fail because the data is unavailable. They fail because the request was vague, the evidence was poorly scoped, or the reviewer could not explain the conclusion afterwards.
That is why a checklist matters. It turns a subjective review into a repeatable control.
What This Checklist Is For
Use this checklist when the task is to understand the origin of funds linked to:
- lending and collateral
- property transactions
- onboarding and enhanced due diligence
- private banking or investment subscriptions
- other regulated reviews where crypto is part of the funding picture
The aim is not to collect everything. The aim is to collect enough verifiable, interpretable evidence to support a defensible decision.
The Four Questions Every Review Should Answer
Before any checklist item, be clear on the outcome you need.
A source-of-funds review should answer:
- What funds are actually in scope?
- Who controlled the relevant wallet or account?
- What was the material transaction path?
- Could another reviewer understand and defend the file later?
If the process cannot answer those questions clearly, it is not ready.
Checklist
1. Define the Review Objective
Record the purpose of the review before requesting evidence.
Confirm:
- transaction or application type
- value or threshold under review
- relevant date range
- whether the concern is source of funds, proof of funds, or both
- whether fiat on-ramp or off-ramp records are needed
This is what prevents vague “send your crypto evidence” requests.
2. Define the Wallet and Account Scope
Identify the wallets, exchange accounts, or bank accounts that actually matter to the review.
Reviewer check:
- in-scope wallets listed
- chain or network listed
- destination of funds identified
- excluded wallets or accounts noted where useful
This avoids unnecessary overcollection.
3. Establish Control Where It Matters
If self-custodied wallets are central to the funding path, the reviewer should know whether control was actually proven.
Reviewer check:
- ownership proof requested where relevant
- proof tied to the correct wallet
- timestamp captured
- any limitations noted if control is inferred rather than proven
Transaction history without control evidence may still be useful, but its evidentiary weight is different.
4. Map the Material Path
The file should describe the relevant path in plain language.
Reviewer check:
- source identified
- material transfers listed
- internal transfers distinguished from third-party transfers
- destination tied to the transaction or application
- unexplained gaps flagged
The point is not to diagram every historical movement. It is to explain the path that matters.
5. Keep the Request Proportionate
Strong review means enough evidence, not maximum disclosure.
Reviewer check:
- only relevant wallets included
- only relevant period included
- unnecessary balances excluded
- counterparty exposure limited where possible
- notes explain why the scope requested was sufficient
This improves both privacy discipline and review quality.
6. Set Rules for Weak Supporting Material
Teams often receive screenshots, PDFs, or manually assembled exports even when they did not ask for them.
Reviewer check:
- policy states whether such material is context only
- reviewer notes explain whether stronger evidence was also received
- material facts are not approved on weak evidence alone
- exceptions require documented rationale
The key is consistency, not moral judgment about the client.
7. Define Escalation Triggers
Not every complex flow is suspicious. But complex flows should not be reviewed without escalation rules.
Reviewer check:
- unclear control of key wallet
- inconsistent amounts across materials
- unexplained late-stage transfers
- missing path into the transaction under review
- repeated resubmissions that alter the story materially
Escalation works best when it is pre-defined rather than improvised.
8. Build the Audit Record
A good review file records how the conclusion was reached.
Reviewer check:
- purpose of review
- scope requested
- evidence types received
- wallets and chains reviewed
- control status
- transaction-path summary
- reviewer conclusion
- escalation notes
- decision date
This is what turns a one-off review into an operational standard.
9. Decide Whether Reverification Is Needed
Some reviews support a one-time decision. Others support ongoing reliance.
Reviewer check:
- evidence expiry or staleness threshold defined
- trigger for refresh documented
- responsibility for refresh assigned
- consequences of missing reverification defined
Without this, strong intake work can still decay into weak ongoing reliance.
What This Checklist Improves
Used properly, this checklist should reduce:
- inconsistent reviewer outcomes
- unnecessary data requests
- unclear escalation decisions
- weak file narratives
- rework after handoff
It also makes client requests easier to draft, because the team knows what it is actually trying to establish.
Where Accredifi Fits
Accredifi supports these workflows by helping teams gather stronger wallet-based evidence without requiring custody.
That includes:
- wallet ownership verification
- scoped transaction-history review
- proof-of-funds records where current holdings matter
- permissioned sharing and reviewable outputs
The goal is to make source-of-funds work cleaner, not simply more digital.
Final Thoughts
The best crypto source-of-funds process is rarely the one that asks for the most material. It is the one that produces the clearest answer with the least unnecessary noise.
A checklist helps teams get there by turning evidence gathering into a disciplined operating habit.
Related Articles
- Source of Funds in Crypto: How to Build a Reviewable Evidence Trail
- Transaction History Verification in Crypto: How to Do It Securely
- What Is Proof of Funds in Crypto? (And What Reviewers Actually Need)
- Crypto Access Requests: How to Share Wallet Data Without Losing Control
- Scheduled Verifications: Continuous Proof for Ongoing Access
Disclaimer: This article is for informational purposes only and does not constitute financial, legal, tax, investment, mortgage, or property advice.