ScreenshotNeo

BlogHow-to

How to Archive a UPI Refund Status Page as Screenshot and PDF in India

Save a UPI refund status, transaction details, and complaint reference as private screenshot and PDF records. Learn what screenshots can—and cannot—prove.

By the ScreenshotNeo team4 October 20267 min read

To archive a UPI refund status, open the UPI or bank app that shows the transaction, capture the status and relevant transaction details, and save the original screenshots. If you need a PDF, use your phone’s built-in image sharing, printing, or document-saving feature where available. Keep the files private and retain any complaint reference. A screenshot records what the app displayed; it is not necessarily a substitute for an official bank statement or accepted evidence in every dispute.

1. Capture the right screens

Use the app or bank account where the payment, refund, or complaint appears. Open transaction history, select the relevant item, and capture the status. If the details do not fit on one screen, take additional screenshots of the transaction detail and complaint reference or status screen.

Before you capture, check that the private evidence copy makes these details legible when they are available:

  • Refund or transaction status and the date and time shown
  • Amount and app or bank identity
  • Transaction ID or 12-digit transaction number/RRN
  • Payer/payee identifiers, if needed to distinguish the transaction
  • Complaint reference number and the latest complaint status

NPCI’s UPI Help guideline depicts transaction-history and transaction-detail screens, including fields such as transaction ID, date, time, amount, and payer/payee identifiers. Its complaint guidance also refers to transaction details and complaint references for status checks. See NPCI UPI Help and NPCI’s complaint guidance.

Do not assume the app has a dedicated “download refund page” control. Export and menu options vary by app and version.

2. Save the screenshots and make a PDF

  1. Keep the originals. Save the screenshots as captured. Avoid cropping, annotating, or overwriting the originals.
  2. Create the PDF if useful. From the image gallery or file-sharing menu, look for the phone’s built-in print, share, or save-as-document option. The exact steps vary by phone, operating system, and app; there is no single verified menu sequence for every device.
  3. Check the result. Open the PDF and confirm that the status, identifiers, date, and complaint reference are readable and that all pages are present.
  4. Name the files clearly. For example, use UPI-refund-status_2026-10-04_appname.pdf and keep the original image files too.
  5. Preserve later updates. Save new status checks and complaint responses as separate dated files rather than replacing the earlier record.

A PDF is a convenient container for captured images. Converting a screenshot to PDF does not make it more authoritative than the original app record or an official bank statement.

3. Keep evidence private and share it carefully

Transaction screens may show UPI IDs, names, account fragments, transaction IDs, and amounts. Store the unedited originals somewhere private. If you need to post an image publicly or send it to someone who does not need all the details, make a separate copy and redact unnecessary identifiers. Keep the original unchanged.

Never share a UPI PIN, OTP, or password as part of an evidence file or support conversation.

4. Know what a screenshot can establish

A screenshot can help document what the app displayed at the time of capture. It does not necessarily prove that money was credited or debited in the account ledger, and each bank or provider sets its own requirements for a dispute.

Google Pay India explicitly says that app screenshots are not valid bank statements. Its guidance says that, in some cases, a bank statement covering the transaction date through the dispute date may be needed for an in-app ticket. Save both the app capture and any official statement the provider requests. Read Google Pay India’s guidance for failed payments.

5. Follow up using the provider’s process

Keep the complaint reference with your files and check subsequent status through the app, bank, or relevant institution. NPCI says its portal can facilitate transaction-status checks in NPCI records and complaint registration with member institutions; the member institution is responsible for resolving the complaint. NPCI advises users to check the final status with the bank or institution using transaction details or the complaint reference. See NPCI’s complaint guidance.

Timelines depend on the provider and the case. For the specific failed-payment scenarios covered by its India help page, Google Pay says a transaction in progress can take up to three working days to resolve and describes a failed debit as being credited back within three working days. That is provider-specific guidance, not a UPI-wide refund guarantee. Google Pay says users can raise an in-app ticket if the money has not been credited after three working days. If money was debited and a merchant says it did not receive the payment or refund, its guidance directs users to contact their bank about a chargeback. If unresolved, it points to NPCI’s dispute redressal portal. Check the provider’s current instructions.

For an unauthorised or fraudulent transaction, contact your bank promptly. NPCI’s complaint guidance directs users to raise unauthorised transactions with their bank. Do not treat a suspected fraud case as an ordinary refund delay.

6. Or skip the browser setup

A UPI app or bank app that requires your signed-in phone session may not be accessible to a website screenshot API. Use the app’s own screens for those records. If the refund status is on a public web page you are authorized to capture, ScreenshotNeo can return an image or PDF with one GET request. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/refund-status -o refund-status.webp
import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/refund-status"},
    timeout=90,
)
r.raise_for_status()
with open("refund-status.webp", "wb") as f:
    f.write(r.content)
const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/refund-status'
});
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('refund-status.webp', res);

Replace the example URL with a public page you are authorized to capture. The API can return PNG, JPEG, WebP, or PDF; consult the docs for output and capture options. ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000. Learn more at ScreenshotNeo.

Sign up for 1,000 free screenshots a month, with no card required.

Troubleshooting

Problem Likely cause What to do
The transaction ID or status is cut off The app splits details across screens or the content does not fit in one capture. Capture the transaction details and complaint page separately. Check each image before filing it.
The app has no PDF or export button Export controls differ by app, device, and operating-system version. Keep the original screenshots and check the phone’s gallery or share menu for a print or save-as-document option. Do not rely on a universal menu path.
The institution asks for a bank statement A screenshot records the app display but may not meet the institution’s statement requirement. Provide the official statement for the requested date range in addition to the screenshot. Google Pay India says app screenshots are not valid bank statements.
The refund is still pending Processing time depends on the provider and transaction circumstances. Save the current status and reference number, follow the provider’s stated timeline, and raise or check a complaint through its official channel. Do not treat Google Pay’s scenario-specific three-working-day guidance as a universal deadline.
A screenshot shows sensitive information Transaction detail screens can include personal and payment identifiers. Keep the original private. Make a separate redacted copy for public sharing, and never include a PIN, OTP, or password.
A web capture shows a blank page or bot check The public page may require interaction, block automated access, or fail to load. For account-specific UPI records, capture from the signed-in app. For a public URL, check that the page is reachable and authorized for capture; with ScreenshotNeo, blank pages, bot checks, and failed loads are not billed.

Performance, reliability, and cost

  • Capture promptly: save the status when it is visible, then preserve later updates separately. An app screen may change as the case progresses.
  • Keep originals: retain the image files alongside any assembled PDF so you can refer back to the original captures.
  • Check legibility: zoom into the saved files before sending them; a PDF that is too small or blurry may not expose the reference details.
  • Use official records when requested: neither a screenshot nor a PDF conversion guarantees acceptance by a bank or provider.
  • API billing: if capturing a public page with ScreenshotNeo, its stated billing policy excludes bot checks, blank pages, timeouts, failed loads, and cache hits. Check the response’s X-Page-Verdict and X-Billed headers. Free usage is 1,000 shots per month; paid tiers begin at $5 for 3,000. See the docs for configuration.

FAQ

Can I archive a refund status without a PDF?

Yes. Keep the original screenshots. A PDF is optional when an image record meets your storage or submission needs.

Does a screenshot prove that a refund reached my bank account?

It records what the app displayed. Check the account ledger or obtain an official statement to confirm a credit, and follow the bank or provider’s evidence requirements.

Should I delete the earlier screenshot when the status changes?

No. Keep dated captures as separate records so the sequence of status updates remains clear.

What if I suspect an unauthorised payment?

Contact your bank promptly and follow its fraud-reporting process. This is different from following up on an ordinary pending refund.