P26 (BSA), which replaced the long-familiar Section 65B of the Indian Evidence Act. The certificate is the formal statement that accompanies the record; pairing it with cryptographic hashes of the saved screenshot file gives a reviewer a concrete, repeatable way to confirm the file is bit-for-bit the same one you preserved. The certificate does not prove that the payment happened — corroboration and the transaction reference do that — but it removes the easy objection that the file was edited after capture. For the statutory detail, see our guide to the Section 63 BSA 2023 electronic evidence certificate. We are describing the framework in general terms; always read the provision as it currently stands and take advice where the stakes warrant it.

Step by Step: Capture, Hash, Certify

A defensible record is mostly about doing a few simple things in the right order, early. 1. Capture the payment record fully. Save the success screenshot, but also open the transaction details inside the app so the reference, timestamp, amount and both handles are visible, and capture that too. Where you can, download the bank statement line that shows the same reference. 2. Preserve the originals. Keep the unedited files; do not crop, annotate or re-save them through a chat app, which can strip data and recompress the image. 3. Hash each file. Run the saved files through a free offline hash tool to compute a cryptographic fingerprint of each. 4. Certify the values. Generate a certificate that records those hashes so the set is locked to a known state. Because the hash changes if even one byte changes, you — or anyone else — can re-verify months later that the file is exactly the one you preserved.

P26 (which replaced Section 65B of the Indian Evidence Act), electronic records generally need an accompanying certificate when produced as evidence. A certificate that records cryptographic hashes of the saved screenshot file lets anyone later confirm the file is bit-for-bit unaltered. It does not prove the payment by itself, but it removes the easy argument that the file was edited after capture.

How do I preserve a UPI screenshot so it can be verified later?
Save the original image and, where possible, the app or bank transaction page and a downloaded statement showing the same reference. Then compute and record a cryptographic hash of each file, for example with a free offline hash tool, and keep a certificate of those values. Because the hash changes if even one byte changes, you can re-verify months later that the file is exactly the one you preserved. You can also confirm an existing certificate at any time with our online certificate verifier.

Conclusion

A UPI screenshot is a starting point, not a finish line. On its own it is an editable image that an opponent can wave away; surrounded by a matching bank record, the transaction reference and a certificate that proves the file is unaltered, it becomes a far steadier piece of proof. The good news is that the hardest part — locking the file to a verifiable state — takes only minutes. Compute and certify the hashes of your saved payment records, fully offline, on a single Windows machine with e-Dex — the free Digital Evidence Integrity Suite. Download it free and preserve your payment proof before you need it. Remember: this is general information, not legal advice.