Legal Aspects of Business and TechnologyUnit 95 min read
E-Transactions Act: Digital Contracts, Signatures & Legal Validity
Unit 9 of Legal Aspects of Business and Technology explores Nepal’s Electronic Transactions Act 2063, covering digital contracts, e-signatures, cybersecurity, and legal recognition of electronic records—critical for e-commerce, banking, and online governance.
Core Concepts & Legal Framework
1. Definition & Scope
The Electronic Transactions Act 2063 (2008) governs:
- Electronic transactions (contracts, records, signatures) in digital form.
- Legal recognition of electronic records equal to paper-based documents.
- Cybersecurity and authentication standards for online transactions.
Why it matters: Ensures trust in digital business (e.g., eSewa payments, Daraz orders, online banking).
2. Key Definitions (Visualized)
mindmap
root((Electronic Transactions Act 2063))
Electronic Record
"Data in digital form (emails, PDFs, databases)"
"Legally valid if authenticated (e.g., encrypted emails)"
Electronic Signature
"Digital equivalent of handwritten signature"
Types:
"Simple (password/OTP)"
"Advanced (digital certificates like eSewa PIN)"
"Qualified (high-security, e.g., bank e-signatures)"
Authentication
"Verifying identity (biometrics, OTPs, certificates)"
Cybersecurity
"Protects data integrity/confidentiality (encryption, firewalls)"In the Real World
eSewa (Nepal):
- Uses electronic signatures (OTP + fingerprint) for payments.
- Legal validity: Courts accept eSewa receipts as proof of transactions (Section 5 of the Act).
Nabil Bank’s Online Loans:
- Applicants sign documents digitally via qualified electronic signatures (QES).
- Worked Example: A loan agreement sent via email with a bank-issued digital certificate is legally binding under Section 6.
Daraz’s Order Processing:
- Electronic records (order confirmations, tracking links) replace paper invoices.
- Dispute resolution: Daraz uses Section 10 (Evidence) to validate digital order histories in court.
3. Legal Validity of Electronic Records
Conditions for Validity
| Requirement | Example | Section |
|---|---|---|
| Authentication | OTP, digital certificates | 5 |
| Integrity | Tamper-proof hashing (e.g., blockchain) | 7 |
| Accessibility | Stored in secure servers (e.g., NTC’s digital archives) | 8 |
| Non-repudiation | Logs showing sender/receiver (e.g., WhatsApp payment receipts) | 9 |
4. Electronic Signatures: Types & Use Cases
Comparison Table
| Type | Security Level | Use Case | Nepal Example |
|---|---|---|---|
| Simple Signature | Low | Social media posts | Facebook comments (OTP login) |
| Advanced Signature | Medium | E-commerce orders | Daraz checkout (email + OTP) |
| Qualified Signature | High | Bank loans, legal contracts | Nabil Bank’s digital signatures |
Worked Example: A Pathao driver accepts a ride request via app. The electronic signature (OTP confirmation) is legally valid under Section 6 if:
- The driver’s identity is verified (biometric login).
- The transaction log is stored securely (Pathao’s servers).
5. Cybersecurity & Data Protection
Key Provisions
flowchart TD
A["Electronic Transaction"] --> B{"Is Data Secure?"}
B -->|"Yes"| C["Legally Valid<br/>(Section 11)"]
B -->|"No"| D["Invalid<br/>(Liable for breach)"]
C --> E["Encryption<br/>Firewalls<br/>Audit Logs"]
D --> F["Penalties:<br/>Fines up to Rs. 500,000<br/>(Section 15)"]Real-World Link:
- NTC’s Digital Services: Uses Section 12 (Data Protection) to secure online bill payments.
- Nepal Rastra Bank’s E-Banking Rules: Mandates two-factor authentication for all transactions.
6. Dispute Resolution & Evidence
How Courts Handle Digital Disputes
- Admissibility: Electronic records are presumed valid unless proven otherwise (Section 10).
- Burden of Proof: The party challenging the record must show tampering or fraud.
- Example:
- Case: A user claims a Khalti payment was unauthorized.
- Solution: Khalti provides transaction logs + OTP records (Section 9) to prove the user’s consent.
Exam Tip
How to Score Full Marks
Define Key Terms:
- "Electronic signature" = Digital mark with authentication (Section 4).
- "Qualified signature" = High-security certificate (e.g., bank e-signatures).
Apply to Scenarios:
- Question: "Can a WhatsApp payment receipt be used in court?"
- Answer: Yes, if:
- Sender/receiver IDs are verified (Section 5).
- Transaction log is unaltered (Section 7).
Compare Types:
- Use the signature comparison table to distinguish between simple/advanced/qualified signatures.
Case Studies:
- Relate to Nepali companies (eSewa, Nabil Bank) or global examples (PayPal’s e-signatures).
Common Pitfalls:
- ❌ Saying "digital signatures are always secure" (only qualified signatures are high-security).
- ❌ Ignoring Section 15 penalties for data breaches.
Final Visual Summary
flowchart LR A["Electronic Transaction"] --> B["Valid?"] B -->|"Yes"| C["Legally Binding<br/>(Courts accept)"] B -->|"No"| D["Invalid<br/>(Check Sections 5-9)"] C --> E["Used in:<br/>- eSewa<br/>- Daraz<br/>- Bank Loans"] D --> F["Fix:<br/>- Add authentication<br/>- Use QES"]
Based on the PU BBA (PU) syllabus for Legal Aspects of Business and Technology, unit 9.
Discussion
Loading…