A bank statement may be relevant when a platform specifically requests financial-source evidence, but it is not automatically suitable for every request. Confirm the required period, fields and file type before preparing anything.
Check the request before choosing a statement
Confirm whether the platform asks for a statement, a transaction record, proof of income or another document. These records answer different questions. If a date range or transaction is specified, make sure the file covers it.
Do not assume that a screenshot from a banking app is equivalent to an official statement. Follow the exact file format and source instructions shown in the account.
Completeness and readability
If a statement is requested, check that the issuer and relevant dates are visible and that the required account-holder or transaction details can be read. A cropped page or a low-resolution screenshot may omit context needed for review.
Do not edit transaction values, dates, balances or names. If the statement contains sensitive fields and you want to redact them, first ask whether redaction is allowed and which fields must remain visible.
- Required date range is included.
- Issuer and relevant account-holder details are visible if required.
- Relevant transaction or income details are readable.
- Pages are complete and not altered.
Unsure how this applies to your situation?
Ask on Telegram using general wording only. Do not send documents, credentials, banking details, wallet access or uncensored screenshots.
Never send identity documents, passwords, 2FA codes, banking details, private keys, seed phrases or account access.
Avoid exposing unnecessary financial information
Only upload through the official platform process. Do not send statements to Telegram helpers, account sellers or third parties claiming they can speed up a review.
If you are unsure which statement is appropriate, ask official support to clarify the requirement rather than sharing several documents with an unofficial contact.
Before you act: safety checklist
Confirm a bank statement is the requested category.
Use a genuine file issued by the bank.
Check date range, issuer and required fields.
Do not edit amounts or transactions.
Confirm redaction rules before masking information.
Official sources and research methodology →
Frequently asked questions
Can I upload a screenshot instead of a statement?
Only if the current official request permits it. Do not assume screenshots and issued statements are interchangeable.
Can I redact transactions?
Confirm the platform’s rules first. Redaction can hide information needed for review and cause rejection.
Can a third party check my statement on Telegram?
Do not send financial statements to unofficial contacts. Use the official upload process.
Get general guidance before making a risky decision
Talk to us on Telegram about documents, pending reviews, rejection wording or account-safety boundaries. Guidance cannot access an account or guarantee an outcome.
Never send identity documents, passwords, 2FA codes, banking details, private keys, seed phrases or account access.
Related guides
Stake Source of Funds Verification: A Safe, Practical Guide
Understand what a source-of-funds request can mean, how to read the request, and how to prepare legitimate evidence without exposing more personal data than necessary.
Stake Source of Income Verification: Documents and Common Questions
Learn how source-of-income requests differ from identity and address checks, which evidence categories may be relevant, and what to clarify with official support.
Stake Proof of Income: Common Document Types and Safe Preparation
Understand common proof-of-income categories, how to check a request and how to avoid fabricated or unsuitable financial records.
Stake Proof of Address: Rejections, Document Quality and Safer Resubmission
A detailed guide to Stake proof of address issues, address verification, rejected documents, name and address consistency and safer resubmission.
KYC Readiness Checklist
A practical checklist for ownership, document clarity, privacy and unsafe shortcuts to avoid.
For pre-submission checks.