Source of Funds in Crypto: How to Prove Origin of Funds Without Screenshots or Custody

If you hold assets in self-custody, one of the hardest compliance requests to satisfy is source of funds (SoF).

You're not just being asked how much you hold. You're being asked to show where the funds came from.

In traditional finance, this often means bank statements, accountant letters, and manual document reviews. In crypto, many users are still pushed toward screenshots, CSV exports, and exchange statements that don't actually prove control or integrity.

That approach creates risk for everyone.

The better model is verifiable source-of-funds evidence: cryptographic proof of wallet ownership combined with timestamped on-chain transaction data and scoped disclosure.

What "Source of Funds" Means in Crypto

Source of funds is not the same thing as proof of funds.

Proof of Funds (PoF) asks: Do you currently control assets of a certain value?
Source of Funds (SoF) asks: Where did the funds used for this transaction or application come from?
Source of Wealth (SoW) asks: How was your overall wealth accumulated over time?

These are related, but they solve different compliance questions.

For example:

A lender may require proof of funds to confirm collateral value today.
A property seller's solicitor may require source of funds for a deposit.
A private bank may require source of wealth during onboarding.

Crypto users often get asked for all three, sometimes using the wrong labels. That's one reason the process becomes confusing and inconsistent.

Why Source-of-Funds Checks Are Difficult for Self-Custody Users

Self-custody gives users control, but it also removes the familiar paper trail institutions expect.

There may be no single bank statement showing:

fiat on-ramp deposits
transfers between wallets
stablecoin conversions
custody changes across platforms
current control of the destination wallet

As a result, users are often asked to send:

wallet screenshots
exchange screenshots
exported CSV files
manually annotated transaction histories

The problem is that these materials are easy to tamper with, hard to verify independently, and poorly scoped for privacy.

They also fail a basic compliance requirement: a reviewer still cannot reliably prove that the person submitting the file controls the wallet in question.

What Good Crypto Source-of-Funds Evidence Should Include

A credible source-of-funds workflow should combine four elements:

1. Proof of Wallet Ownership

The user signs a one-time message from the relevant wallet. This establishes cryptographic control without exposing private keys or moving funds.

Without this step, a transaction history is just a list of public addresses and hashes.

2. Relevant Transaction History (Not Everything)

Source-of-funds checks should be scoped to the transaction or application.

That may include:

the inbound transfer that funded a purchase
a series of transfers showing movement from an exchange to self-custody
stablecoin conversion records before a payment
a defined lookback period (for example, 90 days or 6 months)

The goal is evidence, not surveillance.

3. Timestamped, Verifiable Records

A screenshot can show a balance, but it cannot prove integrity.

A better record is timestamped and tamper-resistant, so a lender, underwriter, or compliance officer can verify:

what data was included
when it was captured
which wallet it relates to
whether the user proved control

4. Clear Context for the Reviewer

Compliance teams do not just need raw blockchain data. They need a usable explanation of what they are looking at.

A strong SoF package should make it easy to understand:

the purpose of the funds (deposit, collateral, investment, settlement)
the relevant wallets and chains
the transaction path that matters
any excluded data (and why)

This reduces back-and-forth and avoids unnecessary resubmission requests.

Why Screenshots and PDFs Fail Source-of-Funds Reviews

Screenshots and PDFs are still common because they're easy to request, not because they're good evidence.

They fail source-of-funds reviews for the same reasons they fail proof-of-funds:

No ownership proof: a screenshot does not prove the sender controls the wallet.
No integrity guarantee: images and PDFs can be edited.
No machine verification: compliance teams cannot reliably automate checks.
Poor auditability: reviewers cannot independently reproduce the evidence later.
Excess disclosure: users often overshare unrelated balances and transactions.

For institutions, this creates operational risk.
For users, it creates privacy risk.

A Better Workflow: Verifiable SoF Without Custody

A modern source-of-funds process does not require custody, seed phrases, or manual screenshots.

It can follow a simple pattern:

Request is defined
The institution specifies the wallets, time range, and evidence needed for the SoF check.
User proves control
The user signs a one-time message from the relevant wallet(s).
Transaction data is scoped
Only the relevant transaction history is included for the request.
Evidence is sealed and timestamped
The resulting verification is generated in a tamper-resistant format.
Reviewer verifies independently
The compliance or underwriting team reviews a verifiable record instead of screenshots.

This is how source-of-funds checks become faster, more defensible, and more respectful of user privacy.

How Accredifi Supports Source-of-Funds Verification

Accredifi enables non-custodial verification workflows that are directly relevant to source-of-funds checks:

Wallet ownership verification via message signing
Verifiable proof-of-funds and balance checks
Transaction history verification with scoped disclosure
Access requests for permissioned, time-limited data sharing
API and webhook support for institutional workflows

That means lenders, law firms, compliance teams, and onboarding platforms can move away from ad hoc screenshots and toward structured, verifiable evidence.

Users keep custody. Institutions get stronger assurance.

Source of Funds, Source of Wealth, and What Comes Next

As crypto assets move into mainstream lending, property transactions, and regulated onboarding, source-of-funds checks will become more common, not less.

The important shift is not whether checks happen. It's how they happen.

Legacy workflows rely on trust, paper, and manual interpretation.
Modern workflows can rely on cryptographic proof, selective disclosure, and verifiable records.

That's the direction compliance is moving:

from screenshots to verification
from blanket disclosure to scoped evidence
from custody assumptions to user-controlled proof

For crypto holders, that means fewer compromises.
For institutions, it means better evidence and lower review risk.

Disclaimer: This article is for informational purposes only and does not constitute financial or legal advice.