BSA Sec 63 Compliant
HashPaper Logo
Statutory Framework

The New Standard for Digital Evidence.

In July 2024, the Bharatiya Sakshya Adhiniyam (BSA) fundamentally altered how electronic records are treated in Indian courts. HashPaper is engineered to automate compliance with the strict cryptographic requirements of Section 63.

The Paradigm Shift

From Human Trust to Mathematical Proof

For decades, proving the authenticity of a digital file relied on subjective human testimony. The new law recognizes that binary data can easily be tampered with, shifting the burden of proof to deterministic cryptography.

Legacy System IEA Sec 65B

Affidavit-Based Verification

  • Relied entirely on written affidavits from the person who controlled the computer.
  • Highly vulnerable to tampering, as dates and metadata could be easily modified.
  • Treated as secondary evidence, often requiring prolonged cross-examination.
Current Law BSA Sec 63

Cryptographic Primary Evidence

  • Mandates technical Hash parameters (SHA-256) to prove a file is unaltered.
  • Electronic records now qualify as self-authenticating primary evidence.
  • Requires specific technical schedules (Part A & Part B) formatted precisely for court admissibility.

Technical Requirements

Decoding the Legal Schedules

Section 63 establishes that digital records must be accompanied by a formal certificate split into distinct technical schedules. If these schedules are missing or incorrectly formatted, the evidence can be dismissed.

Part A: Basic Parameters

Details the human elements of the record. It requires the identity of the person producing the record, the date and time of generation, and a description of the device or platform used to generate the output.

Part B: Cryptographic Schedule

The core mathematical proof. It requires the precise Hash Value (e.g., a 64-character SHA-256 string) calculated from the exact digital file. Because hash functions are strictly one-way, changing even a single comma in the original document changes the hash entirely, proving the document has not been altered since the certificate was generated.

sys // sec63_compiler ACTIVE

// HashPaper Output Mapping

[ PART A MAP ]

Timestamp: Locked to IST Server Protocol

Platform: HashPaper Registry Engine

Owner Identity: User Defined Input

[ PART B MAP ]

Algorithm: SHA-256

Digest Output:

e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

> Document fully compliant with BSA schedules.

How HashPaper Ensures Compliance

We abstract the legal complexities away. By using our platform, you automatically generate documents formatted precisely for the Indian legal system.

1

Automated Math

Our engine instantly calculates the exact SHA-256 hash required for Part B. You don't need to understand cryptography; you just paste your text.

2

Immutable Anchoring

The hash and timestamp are permanently anchored to our public ledger. Opposing counsel cannot claim the document was created after the fact.

3

Court-Ready PDF

HashPaper exports a clean, highly legible PDF document. The formatting strictly aligns with what judges and courts expect to see under the BSA.

Mint a Compliant Certificate →