Cyprus · Financial documentation guide
Cryptocurrency Source of Funds Documentation in Cyprus
For a financial review in Cyprus, build a trail that explains both the acquisition of crypto and its route to the funds now being reviewed. Cross-border account movements need an explanation as well as transaction hashes.
Create your crypto statementExplain the full transfer trail for a Cyprus review
A current balance answers a holdings question. Source-of-funds evidence explains the particular money being used, including acquisition, transfers, sale and any bank payment. A public address alone does not identify the customer behind an exchange account or establish the reason for a transfer.
If your trail crosses an overseas exchange, a self-custody address and a Cyprus bank account, identify the account holder and provider’s legal entity at each stage. Preserve trade exports and bank references as well as hashes. Check provider status using current official information; an older national registration entry should not be treated as proof of current MiCA authorisation.
Individuals can attach purchase records and a concise explanation of their own-address transfers. Businesses can add contracts, invoices and the purpose of receipts. For receipts described as earnings, gifts or other acquisitions, retain the supporting evidence for that explanation: the blockchain report cannot independently establish it.
Before preparing documents
- Identify the people or entities associated with each account in the trail.
- Match cross-border bank references, exchange records and on-chain hashes.
- Disclose unsupported networks, missing records and transfers whose purpose is uncertain.
Cyprus, MiCA and document acceptance
CySEC publishes information on crypto-asset entities under MiCAR. The Cyprus-specific EU supervisory authorities’ consumer factsheet points readers to both CySEC and the Central Bank of Cyprus when checking providers. A provider’s authorisation and the evidence needed for your own financial review are separate questions.
MiCA sets EU rules for specified crypto-assets and services. It does not make a third-party wallet statement a compliance certificate. Confirm the recipient’s evidence requirements before paying for documentation.
How CryptoBankStatement can support preparation
The existing generator produces PDF and CSV reports for a supported public address and selected period. Reports reconstruct transaction history with opening and closing balances, historical fiat estimates where available, transaction hashes and verification records. Fiat estimates are not a guaranteed sale price; missing pricing and reported check limitations need to be considered by the reviewer.
On-Chain Statement organises public activity without a wallet signature. Where offered for an eligible wallet, Verified Statement adds wallet-control proof and identity verification through Stripe Identity. An integrity checksum checks document data; it does not establish that the funds are legally yours or that a bank will accept them.
You can prepare a file without purchasing a report: retain original records, write the timeline and use public explorer references. See the free evidence pack and methodology to decide what a statement would add.
Supported assets and evidence limits
Statements cover BTC on Bitcoin mainnet, ETH, USDC or USDT on Ethereum mainnet, or official Circle USDC on Base Mainnet. One statement is one network. Keep separate records for exchange-internal activity and other assets.
| Network | Included | Not included |
|---|---|---|
| Bitcoin mainnet | One public BTC address per statement | XPUB aggregation and exchange-internal records |
| Ethereum mainnet | ETH, ERC-20 USDC, or ERC-20 USDT | Other tokens, NFTs, and private account records |
| Base mainnet | Official Circle USDC | Base ETH, Base USDT, bridged USDbC, and other tokens |
1. Confirm scope
Ask the receiving reviewer which address, asset, date range, currency, and supporting records they require.
2. Keep original records
Retain bank and exchange exports. The wallet report documents only the supported public-chain part of the trail.
3. Explain limitations
Label transfers between your own accounts and disclose unsupported networks, missing periods, estimates, and other gaps.
Important limitations
This is a document-organisation tool, not a bank statement, regulated attestation, audit opinion, ownership certificate, source-of-wealth determination, or guarantee of acceptance. Public activity can be independently reproduced; legal identity and lawful source require separate evidence.
Common questions
Does a transfer from an exchange prove lawful origin in Cyprus?
No. It shows a step in the trail, rather than the underlying acquisition or lawful source. Keep purchase, income or other acquisition records and ask the receiving reviewer what further evidence they need.
What does a blockchain statement establish for a review in Cyprus?
It organises supported public-address activity, opening and closing balances and transaction evidence for a selected period. Historical fiat values are estimates. Reconciliation and integrity checks have a technical scope; they do not establish legal identity, lawful origin or regulatory compliance.
What is the difference between wallet-control and identity verification?
A supported wallet signature demonstrates control of an address for the verification challenge. Verified Statement combines wallet-control proof with Stripe Identity through the existing workflow, subject to wallet eligibility. Bitcoin signing is disabled by default and restricted to supported addresses when enabled. Neither step proves the legal origin of crypto or replaces a recipient’s own checks.
Is this a MiCA, AML or KYC certificate for Cyprus?
No. CryptoBankStatement does not provide regulatory certification or guarantee compliance with MiCA, AML or KYC obligations. It is not a government-issued certificate or an endorsement by CySEC. Banks, lenders and other recipients decide independently whether the documents are sufficient.
Related documentation
Prepare the supported on-chain part of your file
Confirm scope with your reviewer, then use the existing statement generator.
Create your crypto statement