Last updated · By the Clerk2Officer editorial team · Report a correction
1. Start with the transaction, not the screen
A company uploads a signed borrowing instruction. The bank's platform verifies a certificate and displays a green tick. That is useful technical evidence, but the tick does not answer whether the company could borrow, whether this officer had authority, whether the uploaded document was the agreed version, or whether a statutory formality remains necessary. Electronic transactions require several separate questions to be answered.
The Information Technology Act, 2000 gives electronic records and qualifying signatures legal recognition, regulates certification and addresses specified computer-related wrongs. It works alongside contract, company, banking, evidence, registration and other laws. It does not turn every online instruction into an enforceable obligation. This chapter develops a banker's reasoning sequence: identify the record, establish attribution and authority, preserve integrity, apply the relevant rule, and distinguish operational response from legal findings.
An electronic record can carry text, images, sound and stored or transmitted data. A scanned document, system-generated statement and digitally signed instruction are different evidential objects. Calling all three a digital signature obscures how each was created and what each can prove. Begin by recording the object and the proposition for which it is relied upon.
2. Electronic recognition and contractual validity
Sections 4 and 5 address recognition of electronic records and electronic signatures within their conditions. A requirement for writing can be met through an electronic record that remains accessible for subsequent reference. Signature recognition concerns a qualifying electronic signature in the prescribed manner. It is therefore necessary to distinguish an electronic image of handwriting from a legally recognised authentication method.
Section 10A prevents a contract being denied enforceability solely because electronic means were used in its formation. It does not dispense with offer, acceptance, competence, lawful consideration and other contractual essentials. If the same promise would be unlawful on paper, transmitting it by email does not cure that defect. Similarly, an unauthorised employee cannot create unlimited borrowing authority merely by using the employer's email domain.
Suppose a supplier emails a quotation, the company accepts the stated goods and price, and both preserve the exchange. Electronic formation alone is not a reason to reject the agreement. By contrast, a buyer replying with a changed price may be making a counter-offer. The contractual analysis is the same underlying analysis learned in D01; the medium changes the evidence and process, not the need for agreement.
3. Digital signatures and broader electronic signatures
A digital signature under section 3 uses an asymmetric cryptographic system and a hash function. In simplified teaching terms, the signer uses a private key and verification uses the corresponding public key. A hash represents the document contents; changing the document normally changes that representation. Verification can therefore help connect a signature to a particular record and detect alteration.
This is not the same as encrypting the whole document so that nobody else can read it. Authentication, integrity and confidentiality are distinct objectives. A signed document may remain readable to others. Confidentiality may require separate encryption and access controls. A branch that securely verifies a signature but emails the customer's full data to an unintended recipient has not solved confidentiality.
Section 3A recognises the broader electronic-signature framework for reliable techniques specified through the legal scheme. Digital signatures sit within this wider subject. An OTP may support authentication in a particular process, but the label OTP does not by itself establish every statutory signature requirement, the user's identity beyond dispute or authority for every transaction. Examine the method, its legal basis and the surrounding evidence.
4. Certification is a chain of trust
The Controller of Certifying Authorities has statutory functions involving the certification system. Certifying Authorities operate within the licensing framework and issue certificates through the prescribed processes. A certificate links identity-related information with a public key; it is not a universal assurance that every statement in the signed document is true.
For a banking instruction, examine the certificate identity, validity period, relevant usage and suspension or revocation status, together with the document verification result. Preserve the verification evidence applicable to the transaction time. A certificate that is valid today does not automatically prove its status on an earlier date; a later revocation also requires analysis of timing and cause rather than a mechanical rewrite of all history.
The subscriber must exercise reasonable care to retain control of the private key and prevent disclosure, and notify compromise in accordance with the framework. Shared use of a director's signing token defeats accountable practice. An internal note saying that the assistant always operates the token should prompt investigation of consent, controls and the actual instruction. It is not a substitute for the authorised person's execution.
5. Attribution, acknowledgment and receipt
Section 11 addresses attribution, including records sent by the originator, a person authorised on the originator's behalf, or an information system programmed by or on the originator's behalf to operate automatically. Attribution therefore requires an origin and authority analysis. A copied logo or apparently familiar sender name is weak evidence when account compromise is alleged.
Section 12 deals with acknowledgment of receipt. The agreement between the parties matters, including whether the originator stipulated that the record would bind only upon acknowledgment. A technical delivery acknowledgment, an automated business acceptance and an approval by a competent officer are different events. The system should label them accurately instead of using one status called approved for all three.
Section 13 supplies default rules for dispatch, receipt and deemed business locations, subject to agreement. Entry into a designated computer resource and retrieval from a different resource can matter. Physical server location is not automatically the party's legal place of receipt. In a dispute, preserve the designated address, agreement, timestamps and retrieval history rather than assuming that opening a message always starts every contractual clock.
6. Electronic governance and record retention
The Act enables electronic dealings with government within the applicable framework. It does not confer a general right to insist that every government office accept every document electronically. A filing route, prescribed format, fee and authorised signature method may still be required. Sending an attachment to an officer's private address is not necessarily filing through the notified service.
Section 7 addresses retention conditions, including subsequent accessibility, accurate representation of the original information and preservation of information identifying origin, destination and dispatch or receipt timing where applicable. Retention means more than leaving a file in a downloads folder. A useful bank record can be retrieved, read, connected to its transaction and protected against undocumented alteration.
Imagine a migrated loan file containing only screenshots. The screenshots may preserve some visible content, but they may omit signature-validation data, attachments and routing history. A better migration plan inventories the complete record, preserves relevant metadata, tests retrieval and documents conversion. This is an operational illustration; exact retention periods arise from the applicable banking, tax, company and other requirements, not from a single universal period invented for this lesson.
7. The exclusions must be read with the 2022 amendment
Older notes reproduce a five-entry First Schedule and state that every immovable-property transaction and every power of attorney is outside electronic recognition. That is an unsafe current revision shortcut. The 2022 notification amended the negotiable-instrument and power-of-attorney entries and omitted the former property-conveyance entry. The actual instrument and the amended wording must be identified.
The negotiable-instrument entry includes specified exceptions involving cheques and qualifying demand promissory notes or bills of exchange associated with regulated entities. The power-of-attorney entry also has a specific regulated-entity exception. These are carefully framed exceptions, not a rule that every informal electronic promise or authority letter qualifies. Trusts and wills remain relevant exclusions under the schedule.
Omission of the old property entry does not repeal registration, stamping, execution, attestation or local property-law requirements. A borrower emailing an unsigned sale proposal has not thereby transferred ownership. The proper question is whether electronic form is legally recognised for this document and whether all other applicable requirements have been met. Keep medium, formality and substantive entitlement as separate columns in the file analysis.
8. Civil contravention and criminal offence are different
Section 43 addresses specified unauthorised computer-related conduct, such as access, extraction and damage, within its terms. Section 66 concerns specified section 43 acts committed dishonestly or fraudulently. The additional mental element matters. A system fault, contractual dispute, negligent configuration and deliberate fraudulent extraction should not be classified as the same offence merely because all involve a computer.
Identity-related misuse and computer-enabled personation have their own provisions, including sections 66C and 66D. Apply the actual ingredients to the actor's conduct. For example, using another person's authentication credential and pretending to be that customer may raise different questions from a genuine customer disputing the quality of a service bought online. A failed payment alone proves neither identity theft nor personation.
For bank staff the immediate response is often protective: restrict compromised access through authorised procedures, preserve logs, record customer reports and escalate promptly. Those actions do not require a branch to declare someone guilty. Avoid altering the original evidence while investigating. Record what is known, what the system shows and what remains alleged so that the competent investigative process has reliable material.
9. Penalties: distinguish historical notes from operative amendments
The Jan Vishwas amendments affecting the IT Act commenced on 30 November 2023. A later omnibus law, the Jan Vishwas (Amendment of Provisions) Act, 2026 (Act 8 of 2026, assent 7 April 2026), amends 79 Central Acts and is reported to include the IT Act; its IT Act entries and their commencement date are To be confirmed before relying on any penalty table. They changed several penalty and offence provisions. A study table copied from an old bare Act can therefore be wrong even when its section numbers look familiar. Section 66A is omitted; it should not appear as an available current offence in a banking incident checklist.
Some provisions previously described through imprisonment language now use monetary penalties, while other offences retain criminal treatment. Do not infer that decriminalisation of one provision decriminalised every computer offence. Equally, do not quote an old prison term for a provision whose operative text has changed. Classify the particular section and amendment before learning its consequence.
The 2025 DPDP commencement notification also uses staged commencement. At the preparation date of 8 November 2026, section 44(2), which provides for omission of IT Act section 43A, belongs to the later eighteen-month commencement group. It should not be described as already operative merely because the DPDP Act was enacted in 2023. This contrasts with the separately commenced RTI amendment discussed in D25. Enactment, notification and operative date are different events.
10. Adjudication, appeal and investigation
The Act provides adjudication for specified contraventions and appellate arrangements. Current study should use the post-reorganisation appellate framework involving TDSAT, rather than present the former separate Cyber Appellate Tribunal as the unchanged institution. The relevant order, statutory route and limitation provision must be identified before computing a filing date.
Section 57 ordinarily provides a forty-five-day appeal period from receipt of the relevant Controller or adjudicating-officer order, with a sufficient-cause provision. Section 62 concerns an appeal to the High Court within sixty days of communication on the specified grounds, with a further limited extension for sufficient cause. These are not customer-service complaint response periods, and an extension is not self-granted by the bank.
Section 78 concerns investigation by a police officer not below Inspector. Powers of entry, search and arrest have separate conditions; the investigation-rank rule is not blanket authority for any person to enter any private location or demand every customer database. A branch should establish the requesting authority and lawful scope, cooperate through its designated legal process and preserve records of material supplied.
11. Critical information infrastructure and protected systems
Critical information infrastructure concerns resources whose incapacitation or destruction could have debilitating effects on specified vital interests. A protected system has a statutory notification basis. Banking is important, but it is inaccurate to label every laptop used in a branch a formally notified protected system without checking the applicable notification and scope.
The national critical-information-infrastructure protection role and CERT-In's incident-response functions must be distinguished. Operational reporting requirements come from applicable directions and categories; do not invent a universal period for every minor help-desk ticket. A sound incident record captures discovery, affected systems, likely impact, actions and escalation so that the relevant team can apply the current reporting rule.
Consider a payment outage with no evidence of compromise. Restoration and incident assessment are urgent, but outage alone does not establish cyberterrorism or a criminal attack on a protected system. Conversely, a small financial loss does not make credential theft harmless. Legal classification follows the ingredients and evidence; operational severity considers service disruption and risk as well as money already lost.
12. Electronic cheques and evidence
An electronic cheque and a truncated cheque are distinct concepts under the Negotiable Instruments Act. Truncation generally involves replacing further physical movement with an electronic image through the clearing process; it is not the proposition that every image emailed by a customer becomes a cheque. Use the relevant instrument definitions alongside the electronic-record framework.
Preservation of an image, clearing data and an account debit may support different propositions. An accurate debit entry is evidence of what the system recorded. It does not conclusively resolve forgery, customer authority, alteration, duplicate presentation or entitlement. The evidentiary chain should connect the original capture, processing events, controls and certified output where required.
Electronic evidence now also requires attention to the Bharatiya Sakshya Adhiniyam and applicable transition or savings issues. Avoid presenting an old Evidence Act section reference as the sole unqualified current rule for every proceeding. In examination revision, distinguish the substantive transaction, the IT recognition rule and the procedural evidence requirement; one does not automatically replace the others.
13. Worked case: valid signature, excessive mandate
Riverbend Equipment has an approved borrowing ceiling of ₹40 lakh. An officer whose certificate verifies successfully sends an instruction for ₹65 lakh. The bank's file contains authority limited to ₹40 lakh and no evidence of later enlargement. A checker proposes releasing the full amount because the electronic signature is genuine.
That proposal confuses identity and authority. Even assuming the signature is valid, the supplied mandate does not support the extra ₹25 lakh. The correct next action is to stop the unsupported release and obtain the required current authority and approvals. The arithmetic difference is ₹65 lakh minus ₹40 lakh, but the calculation does not decide whether any separate apparent-authority or ratification issue exists.
Preserve the signed record, verification result and applicable mandate. If the officer later sends an ordinary email saying the board verbally agreed, that assertion alone should not replace the documented authority process. If competent fresh approval is produced, verify its scope, timing and conditions before acting. The adverse outcome to avoid is a technically authentic transaction executed beyond supported authority.
14. Worked case: changed document and incident response
A customer signs version A of a facility instruction. The branch later receives version B with a different beneficiary. Verification against version B fails, while the archived version A verifies. An employee suggests manually marking version B as verified because the amount is unchanged and the customer is familiar.
Do not override the failed verification. A beneficiary alteration changes the transaction even when the amount is identical. Separate possible document corruption, clerical replacement and deliberate substitution; none can be resolved by guessing. Preserve both versions and their metadata, hold the disputed instruction through the authorised process and contact the customer through an independently established channel.
The investigation may ultimately show an innocent attachment error. That possibility does not justify executing the altered instruction first. Conversely, failure of a verification check alone is not a final conviction of fraud. A good response protects funds and evidence while allowing a fair determination. For revision, state the supported action, explain the integrity failure and identify the missing evidence before selecting a legal conclusion. Preserve the distinction between a failed validation and an inaccessible validation service. The former may indicate a document or signature problem; the latter may mean no conclusion is yet available. An offline status should not be recorded as a successful check merely to complete the processing queue.
15. Selected amended consequences for revision
The Jan Vishwas comparative text is especially useful for identifying obsolete punishment notes. Under amended section 67C, intentional or knowing contravention of the specified intermediary retention obligation attracts a penalty up to ₹25 lakh, rather than the earlier imprisonment formulation. Section 72 now has a penalty up to ₹5 lakh, and section 72A a penalty up to ₹25 lakh, within their distinct ingredients. Do not merge the confidentiality-related provisions into one offence.
Amended section 45 provides a residual penalty up to ₹1 lakh, together with compensation subject to different maxima: ₹10 lakh for an intermediary, company or body corporate, and ₹1 lakh for another person. It applies where the relevant contravention has no separately provided penalty. The maximum is not an automatic bill. The proper process, actor, conduct and provision must first be established.
These selected figures illustrate why a penalty table needs a version date. They do not imply that identity theft, personation or every other criminal provision became a civil penalty. A chapter question naming a section should be answered from that section's operative ingredients and consequence, not from the general headline that cyber offences were decriminalised.
Work the numbers
Open the relevant worked calculator. Establish the legal inputs and assumptions first. The model does not decide liability or grant approval.
Chapter practice
This practice is separate from timed mock tests. Answers and explanations appear after you choose an option.
Your reading progress
Sign in to save your progress across devices.