How to Capture an Indian Bank Net Banking Page for Documentation
Capture a clear record of an Indian bank net banking page while protecting credentials and personal details. Learn what to save and how to preserve it.
To document an Indian bank net banking page, open the bank’s official website directly, verify its domain and secure connection, navigate to only the relevant page, and capture just enough context to explain the record. Keep passwords, PINs, one-time codes, and unrelated financial details out of the image. Save the original securely; if you need to share it, redact a separate copy.
A screenshot can be useful supporting material, but it does not by itself establish that a transaction occurred or satisfy every reporting or legal requirement. Preserve related records, such as a bank statement, transfer receipt, page URL, or other relevant documents. The National Cyber Crime Reporting Portal lists images among possible supporting evidence, without saying that a screenshot alone is sufficient.
1. Start from the bank’s official site
- Use a trusted, updated device and browser. Keep the operating system and browser up to date.
- Type the bank’s known official URL into the address bar, or reach it from the bank’s official home page. Avoid unexpected links in email, SMS, pop-ups, and search ads.
- Before signing in, check that the displayed domain is the bank’s correct domain and that the connection uses HTTPS with a valid security certificate. A padlock alone does not prove that a site is the bank’s; check the domain too.
- Sign in through the bank’s normal process. Do not include your password, PIN, one-time password (OTP), or any other security access code in a screenshot or share them with anyone.
CERT-In advises users to access online banking by typing the URL in the browser address bar and to check the security certificate and HTTPS indicators. Indian Bank gives similar domain and HTTPS checks in its guidance. See CERT-In’s online banking guidance and Indian Bank’s privacy policy.
2. Prepare a minimal, useful record
Open only the account, transaction, or page needed for the record. Before capturing, check what is visible around it. Include enough context to identify what the page shows, while excluding unrelated accounts, balances, addresses, account numbers, and personal details the recipient does not need.
- Keep secrets out: Never capture a password, PIN, OTP, or other access code. If a code or secret is visible, leave that screen without recording it.
- Limit personal data: Show only the information needed to explain the record. Do not assume a recipient needs every identifier or account detail.
- Keep context: Include the relevant page heading, transaction state, and date or reference information if the page displays them and they are needed.
- Capture the page as it appears: Do not alter the original screenshot to add or remove information. If you need to conceal data before sharing, make a separate redacted copy.
These are practical recordkeeping steps, not a screenshot procedure prescribed by the cited official sources.
3. Capture and save the page
- Use your device’s ordinary screenshot function to capture the relevant visible section. The exact shortcut depends on your device and operating system; the official sources cited here do not prescribe one.
- If a page-oriented document is more useful, use the browser’s print or save-to-PDF function. Check the preview for hidden or unrelated content before saving.
- Review the result at normal size. Confirm it is legible, shows the relevant context, and does not expose a credential or unnecessary personal information.
- Save the original image or PDF in a secure location. Use a descriptive filename and keep a note of the date, time, bank, page, and reason for the capture.
For example, a filename such as bank-transfer-status-2026-10-04.png can make a record easier to find. Use the date that applies to your actual capture. Store any note separately if it contains private information.
4. Share a redacted copy when needed
Keep the original unchanged. Make a duplicate for sharing, then redact identifiers that the recipient does not need. Use an editing method that permanently removes the selected content from the shared copy; a translucent highlight or removable layer may leave the underlying text recoverable. Reopen the exported copy and check that the redaction is opaque and cannot be selected or undone.
Share the minimum necessary material through the recipient’s appropriate, trusted channel. Do not send your banking credentials or security codes. If the record relates to a suspected cybercrime, use the relevant reporting channel and provide accurate details rather than relying on a screenshot alone.
5. Preserve related evidence and close the session
If you are documenting an incident or disputed transaction, retain related records where available: a bank statement, online transfer receipt, relevant webpage URL, and other supporting documents. The National Cyber Crime Reporting Portal FAQ lists bank statements, online transfer receipts, URLs, videos, images, and other documents as examples of supporting evidence. It recommends keeping relevant evidence and providing accurate, complete complaint details. It does not say that a screenshot alone proves a transaction or is enough for every proceeding.
When finished, use the bank’s log-off control and close the session. Do not leave a logged-in banking page unattended. CERT-In includes logging off through the banking service’s control among its online banking guidance.
Screenshot or PDF: which should you keep?
| Format | Useful when | Check before saving or sharing |
|---|---|---|
| Screenshot image | You need a fixed visual record of a particular visible page state. | It is readable, has enough context, and contains no unnecessary private information. |
| Print or save to PDF | A page-oriented document is more practical for review or filing. | The print preview includes only relevant content and does not reveal extra pages or details. |
The official sources cited here do not prescribe one format or compare their suitability. Choose based on what the recipient needs, then preserve the original securely.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. For documentation, use it only on a public page that does not require signing in or expose private banking data. Do not send bank credentials, account pages, or other sensitive session information to a screenshot service.
For an appropriate public page, this cURL request saves a WebP screenshot. See the ScreenshotNeo API documentation for options and setup.
curl -G "https://api.screenshotneo.com/v1/shot" \
-d access_key=YOUR_API_KEY \
--data-urlencode url=https://stripe.com \
-o shot.webp
ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server includes tools for AI agents to take screenshots, inspect page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for 1,000 free screenshots a month, with no card required.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| The login page’s domain looks unfamiliar. | You may have followed a misleading link or reached a lookalike site. | Do not enter credentials. Close it and type the bank’s known official address or start from its official home page. Verify the domain and secure connection. |
| The screenshot contains more account information than intended. | The page included other visible details or the capture included too much of the screen. | Keep the original securely. Make a separate copy, redact information the recipient does not need, and inspect the exported copy before sharing. |
| The saved image is difficult to read. | The relevant content may be too small or outside the captured area. | Return to the page, frame the relevant section clearly, and capture again without exposing unrelated information. Keep the clearer original. |
| The PDF includes unrelated content. | The browser’s print layout may include extra sections or pages. | Review print preview, adjust the selected pages or layout if available, and inspect the saved PDF before sharing. |
| You cannot find the saved record later. | The file may have a generic name or be stored in an unexpected location. | Save it in a secure, known location with a descriptive filename and note the capture date, page, and reason. |
| You are unsure whether the screenshot is enough for a complaint. | A screenshot is only one possible supporting item; requirements depend on the situation. | Preserve related records and provide accurate details through the appropriate reporting channel. The National Cyber Crime Reporting Portal gives examples of supporting evidence but does not establish screenshot-only sufficiency. |
Reliability and privacy checklist
- Use a trusted, updated device and browser.
- Navigate to the bank directly and verify its domain and HTTPS connection before signing in.
- Exclude passwords, PINs, OTPs, and unrelated financial details.
- Check that the record is readable and includes the context needed to understand it.
- Keep the original secure; redact a separate copy for sharing.
- Preserve related documents if the record concerns an incident or transaction dispute.
- Log off using the bank’s control and close the session.
Frequently asked questions
Does a screenshot prove that a bank transaction happened?
A screenshot can support a record, but the National Cyber Crime Reporting Portal does not say that an image alone proves a transaction. Keep related records such as a bank statement or transfer receipt where available.
Should I send a screenshot to someone who asks for my OTP?
No. Do not share an OTP, password, PIN, or other security access code. A documentation request does not require you to disclose banking credentials.
Should I edit the original screenshot to hide account details?
Keep the original unchanged and secure. Redact a separate copy, then verify the exported copy no longer reveals the concealed information.
Where do I report suspected cybercrime in India?
The National Cyber Crime Reporting Portal accepts complaints and says they are handled by the selected State or Union Territory police authorities. Follow the portal’s instructions and provide accurate details and relevant supporting records.


