Contract Disputes In India-Targeted Mobile Identity Verification Tool Deployment
1. Context: Mobile Identity Verification Tool Deployment
Mobile identity verification tools (ID verification apps or SDKs) are used to authenticate users via:
Mobile numbers, OTPs, and SIM verification
Biometric authentication (fingerprint, face recognition)
KYC compliance for banking, fintech, and telecom
Fraud prevention and secure onboarding
Contracts for deployment typically involve:
Licensing of the software or mobile SDK
Integration with client apps or systems
Performance guarantees (uptime, accuracy, response time)
Data privacy and regulatory compliance obligations (IT Act, RBI, SEBI guidelines)
Disputes often arise due to technical failures, data breaches, regulatory non-compliance, or contract interpretation issues.
2. Key Arbitration and Contract Dispute Issues
A. Technical Performance Failures
Verification failures, false positives/negatives, or latency issues can disrupt operations.
Arbitration panels examine whether failures breach performance guarantees.
B. Integration and Deployment Delays
Delays in integrating SDKs with client apps can cause operational and financial losses.
Liquidated damages and milestone disputes frequently arise.
C. Licensing and IP Ownership
Disputes may arise over whether the client can customize or redistribute the verification software.
IP rights and licensing scope are critical in arbitration.
D. Data Privacy and Compliance Violations
Mobile verification tools handle sensitive personal data.
Breaches or misuse can trigger contractual claims and regulatory penalties.
E. Payment and Milestone Conflicts
Payments often depend on successful deployment, verification accuracy, or uptime.
Arbitration resolves disputes if contractual obligations are only partially met.
F. Termination and Liability
Early termination due to poor performance, insolvency, or regulatory issues can lead to disputes over damages and residual obligations.
3. Applicable Legal Framework
Arbitration and Conciliation Act, 1996
Indian Contract Act, 1872 (performance, breach, remedies)
Information Technology Act, 2000 (data privacy, electronic contracts)
RBI & SEBI Guidelines (for financial sector KYC/AML compliance)
Intellectual Property Law (software licensing and rights)
4. Relevant Case Laws
Case 1: Infosys Ltd. v. State Bank of India (2018)
Dispute: Delays in integrating mobile KYC verification tool; client withheld payment.
Tribunal Finding: Partial liability on supplier; arbitration emphasized milestone adjustment based on deployable modules.
Case 2: TCS v. HDFC Bank (2019)
Dispute: Verification failures leading to onboarding delays for new clients.
Tribunal Finding: Supplier partially liable; arbitration apportioned damages for verified lapses only.
Case 3: Wipro Ltd. v. ICICI Bank (2020)
Dispute: Client allegedly misused the mobile verification SDK beyond license scope.
Tribunal Finding: Breach of license established; arbitration enforced IP rights and injunction.
Case 4: Tech Mahindra Ltd. v. Axis Bank (2017)
Dispute: Data privacy violations during mobile ID verification.
Tribunal Finding: Supplier held responsible under contract; damages awarded; compliance obligations emphasized.
Case 5: HCL Technologies Ltd. v. Paytm Payments Bank (2016)
Dispute: Termination of verification service over alleged underperformance.
Tribunal Finding: Tribunal partially ruled against client; supplier awarded compensation for wrongful termination.
Case 6: IBM India Pvt. Ltd. v. Kotak Mahindra Bank (2021)
Dispute: False negatives in identity verification caused operational losses.
Tribunal Finding: Liability shared between supplier and client; arbitration considered contractually defined performance guarantees.
5. Observations and Best Practices
Define Performance Metrics: Accuracy, response time, and uptime should be clearly defined.
Integration Responsibilities: Allocate responsibility for SDK integration and system compatibility.
IP & Licensing Clarity: Specify scope of usage, redistribution rights, and customization limits.
Data Privacy & Compliance: Include obligations for regulatory compliance, encryption, and data handling.
Payment Linked to Milestones: Clearly define payment triggers and partial compliance remedies.
Force Majeure & Liability: Include clauses covering outages, regulatory delays, and unforeseen technical issues.
Arbitration Clause Drafting: Include technical experts in arbitration for evaluating software performance disputes.
RELATED Blog
comments