How to Capture a Screenshot of an Indian Insurance Portal After OTP Sign-In

To capture an Indian insurance portal after OTP sign-in, complete the insurer’s normal sign-in flow, wait until the authenticated page or confirmation you need is visible, and use your device’s built-in screenshot controls. Review the saved image and remove sensitive information before sharing it beyond the intended recipient.

The OTP belongs in the portal’s verification step; avoid including the OTP entry screen or code in your evidence. Portals differ in their sign-in fields and OTP delivery channels. For example, IRDAI’s Bima Bharosa login shows an OTP sent to the registered email address and an OTP validation form. That example does not establish how every insurer’s portal works. IRDAI Bima Bharosa

1. Sign in and reach the page you need

1. Open the insurer’s official website or app. Check the address before entering credentials.
2. Follow the portal’s normal username, password, and OTP prompts. Enter the OTP only in the portal’s own verification step.
3. Wait for the authenticated page, policy detail, claim status, or confirmation to finish loading.
4. Position the page so the necessary context is visible: for example, the portal name, relevant status, and date if shown. Do not include unrelated policy details just to fill the frame.
5. Take the screenshot using the instructions for your device below.

IRDAI’s insurance repository FAQ describes online accounts for accessing electronic policies, another example of policy information being available through authenticated online services. The insurer and service determine the exact page and workflow. IRDAI insurance repository FAQ and information

2. Capture the page with your device

Windows 10 and 11

1. With the authenticated page visible, press Windows logo key + Shift + S.
2. Choose a capture mode in Snipping Tool, such as a rectangular region, and select the part of the screen you need.
3. Open the resulting snip to review, edit, and save it.

Snipping Tool includes a quick redaction feature for detected email addresses and phone numbers. Detection may miss sensitive details, so inspect the final saved image yourself. Microsoft: Use Snipping Tool to capture screenshots

Mac

• Press Shift + Command + 3 to capture the full screen.
• Press Shift + Command + 4 and drag to select a region.
• Press Shift + Command + 5 to open the Screenshot app and choose from its capture controls.

Shortcuts and controls can vary by macOS version and configuration. See Apple’s screenshot instructions for Mac.

iPhone

• Face ID model: Quickly press and release the side button and volume-up button together.
• Touch ID model with a side button: Quickly press and release the side button and Home button together.

For a long page in Safari, Apple documents a Full Page option after taking a screenshot. It can be saved as an image or PDF. Availability and the displayed controls depend on the device and app. See Apple’s screenshot instructions for iPhone.

3. Check the screenshot before sharing

1. Open the saved file and inspect it at full size. Make sure the needed status and portal context are legible.
2. Crop away browser tabs, unrelated policy information, and other screen content that the recipient does not need.
3. Check for OTPs, passwords, full identity or policy numbers, email addresses, phone numbers, and personal details belonging to other people.
4. If you redact, save a separate redacted copy and reopen that copy to confirm the information is no longer visible. A drawn-over area or crop can be incomplete; verify the actual exported file.
5. Send the least detailed version that still supports the request, and use the recipient’s approved submission channel.

These are privacy-conscious handling steps, not a claim that a particular insurer or law requires a specific screenshot format. IRDAI’s 2017 Aadhaar e-KYC clarification concerns UIDAI-based client identification and authentication specifically; it says access to client details from UIDAI for that purpose is voluntary and consent-based. It should not be read as a description of every portal OTP login. IRDAI circular on Aadhaar-based e-KYC, 31 August 2017

4. If you need a browser-generated capture

A device screenshot is usually sufficient for a single visible screen. A browser-based capture can help when you need a consistent viewport or a long page, but an authenticated insurance page requires care: credentials and session cookies grant access to personal information.

Do not paste an OTP, password, session cookie, or private portal URL into an untrusted service. Use a browser tool only if its handling of authenticated pages fits your organization’s policies and the portal’s terms. ScreenshotNeo is a website screenshot API and MCP server for developers. Its API takes a URL in a GET request, but a URL alone does not supply a portal’s authenticated browser session. Do not send portal credentials or session cookies to an API unless you have verified that this is appropriate for the account and data involved. ScreenshotNeo details are at ScreenshotNeo.

Or skip the browser setup

For a page you are authorized to capture and can access through a URL without transferring sensitive sign-in material, ScreenshotNeo can return an image or PDF from one API request. Its clean-shot steps accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Only clean shots are billed: bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools for screenshots, page information, and PDF capture.

For an authenticated insurance portal, use this only when you have a safe, authorized way to provide access; the sample below captures a public page and does not sign in to an insurer.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

See the ScreenshotNeo API documentation for request options and response details. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000, and every feature is on every plan. Sign up for 1,000 free screenshots a month, with no card.

Troubleshooting

What happens	Likely cause	What to do
The OTP does not arrive	The portal may use the registered contact channel, delivery may be delayed, or the account details may need updating.	Use the portal’s resend option if available, check the registered email or phone, and contact the insurer through its official support route. Never share the OTP with someone claiming to help.
The page still shows a spinner or an old status	The authenticated page has not finished loading or the session expired.	Wait for the page to settle. If needed, use the portal’s normal refresh or sign-in flow, then capture the result that actually appears.
The screenshot omits part of a long page	A standard screen capture only records the visible screen or selected area.	Capture multiple clearly framed sections, or use the supported full-page feature in Safari on iPhone when available. Keep enough context to show how sections relate.
The capture shortcut does nothing	The shortcut may differ by operating-system version, keyboard, or device model.	Use the operating system’s Screenshot or Snipping Tool app and check the manufacturer’s current instructions for the device.
Screenshot capture is blocked in managed Chrome	An organization administrator may have enabled screenshot prevention with Chrome Enterprise Premium.	Do not try to evade the restriction. Ask the organization or portal for its approved evidence-submission method. Google documents this as a managed configuration, not a universal behavior of ordinary Chrome installations. Chrome Enterprise policies
A redaction tool leaves details visible	Automatic detection may not recognize every sensitive value, or the edit may not have been saved into the exported copy.	Open the final file and inspect each sensitive area. If necessary, create a new copy with a solid opaque redaction and verify it again.

Performance, reliability, and cost

For one screenshot, the built-in device control is the simplest route and needs no screenshot service. A full-page capture can take longer to review and may include information below the initially visible area, so inspect the whole output. If the portal is slow, wait for the relevant result instead of relying on a capture of an incomplete page. Save a local copy before sharing so you can check what was actually sent.

ScreenshotNeo is useful for developer workflows that capture accessible web pages repeatedly, but it does not remove the need to protect authenticated account access. Its free allowance is 1,000 shots per month without a card. Paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. A direct device screenshot avoids per-shot API usage for this one-off task.

FAQ

Should I include the OTP in the screenshot?

No. Capture the authenticated result after sign-in and keep the OTP out of the image.

Does every Indian insurance portal send OTPs to email?

No. The channel and form vary. Bima Bharosa is an official example of registered-email OTP validation, not a template for every insurer.

Can I use a screenshot as proof of a policy or claim status?

It can document what appeared on screen, but ask the recipient whether they require a portal download, statement, or other official record.

Can ScreenshotNeo sign in to my insurer’s portal?

The API example captures a URL; it does not perform the insurer’s OTP flow. Do not transmit account secrets or session data unless you have confirmed that doing so is authorized and appropriate.