Can You Be Sued for Not Giving a Refund Even If the Customer Never Used the Product?

📑 Table of Contents

• Introduction: The Non-Usage Myth in Software and Digital Commerce
• The Real-World Scenario: The Phantom SaaS Subscription Dispute
• The Law and Regulatory Analysis
• A. Applicable Legislation and Statutory Scope
• B. Judicial Authorities and Contractual Principles
• C. Comparative Legal Framework Table
• D. Liability, Defences, and Legal Uncertainty
• The Takeaway: Actionable Compliance Playbook for Tech Founders

Executive Key Takeaways (TL;DR):

• Non-usage does not automatically equal a legal right to a refund under global consumer protection frameworks like the UK Consumer Rights Act 2015 or EU Consumer Rights Directive.
• Digital service delivery occurs upon access or license grant, meaning failure to log in or provision an account does not invalidate a properly drafted "no-refunds" policy.
• Statutory cooling-off periods apply to digital goods only if the consumer has not given express prior consent and acknowledged that they lose their cancellation right upon digital performance initiation.
• CTOs and founders must align their Terms of Service (ToS) and automated onboarding flows with local statutory disclosure mandates to avoid deceptive trade practice claims and chargeback fraud.

Introduction: The Non-Usage Myth in Software and Digital Commerce

For technical founders, CTOs, and product engineers, nothing triggers more operational friction than the customer who purchases an annual SaaS license, never logs into the dashboard, and demands a full refund six months later under the banner of "I didn't even use it." The core legal question is whether a customer's failure to consume, deploy, or utilize a digital product creates an automatic statutory right to a refund—and whether they can successfully sue your tech company if you refuse.

Under major global legal frameworks including the United Kingdom, European Union, United States, and Nigeria, non-usage is rarely a legal get-out-of-jail-free card. However, your exposure to lawsuits, regulatory fines, and payment processor chargebacks depends entirely on how your Terms of Service (ToS) are drafted, whether statutory cooling-off exemptions were legally triggered during checkout, and how your system logs capture delivery of service.

The Real-World Scenario: The Phantom SaaS Subscription Dispute

Consider a realistic hypothetical scenario involving a London-based B2B SaaS startup providing automated cloud infrastructure monitoring. A mid-sized fintech company purchases an annual enterprise subscription for $12,000. Due to internal engineering delays, the fintech company never integrates the monitoring SDK into their production codebase. Nine months into the subscription term, their new CTO reviews corporate expenses, realizes the software was never deployed or used, and demands an immediate 100% refund.

When the SaaS startup refuses, citing its clear "No Refunds / Final Sale" policy, the fintech company threatens a lawsuit for unjust enrichment and deceptive trade practices, while simultaneously filing a chargeback with their credit card acquirer. What is the legal reality here? Did the SaaS company breach any consumer protection or commercial contract laws by keeping the funds for a service that delivered zero computational utility to the buyer?

The Law and Regulatory Analysis

A. Applicable Legislation and Statutory Scope

Statutory refund rights differ drastically depending on whether the customer is a business (B2B) or a consumer (B2C), and whether the product is physical merchandise, a digital download, or a cloud-based software service (SaaS).

• United Kingdom (Consumer Rights Act 2015): Under Section 42 and Section 47 of the CRA 2015, consumers have rights to a refund for digital content that is faulty, not as described, or not fit for purpose. However, simple non-use does not render digital content "faulty." Furthermore, under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, digital content supplies are exempt from the standard 14-day cooling-off period if performance has begun with the consumer's prior express consent and acknowledgment that they lose their cancellation right.
• European Union (Consumer Rights Directive 2011/83/EU): Implemented heavily across member states, Article 16(m) states that the right of withdrawal does not apply to digital content not supplied on a tangible medium if performance has begun with the consumer's prior express consent. Non-use due to buyer negligence or internal restructuring does not trigger a statutory withdrawal right.
• United States (FTC Act & State Uniform Commercial Code): US federal law governed by the FTC does not mandate a general right to a refund for unused goods or services unless explicitly stated by merchant policy or local state consumer protection laws. However, failure to clearly and conspicuously disclose a "No Refund" policy prior to payment violates Section 5 of the FTC Act (15 U.S.C. § 45) regarding unfair or deceptive acts or practices.
• Nigeria (Federal Competition and Consumer Protection Act - FCCPA 2018): Under Section 120 and Section 124 of the FCCPA, consumers have protections against unfair contract terms and misleading representations. While consumers can cancel services, provisions regarding advance payments for services not rendered depend heavily on whether the supplier was ready, willing, and able to perform. If the platform account was fully provisioned and accessible, the supplier's obligation was fulfilled.

B. Judicial Authorities and Contractual Principles

Courts across common law jurisdictions consistently uphold the principle of freedom of contract, particularly in B2B transactions. In the English landmark case of Cavendish Square Holding BV v Talal El Makdessi [2015] UKSC 67, the Supreme Court emphasized that commercial parties negotiating on equal footing are bound by their agreed risk allocations. If a commercial contract allocates the risk of non-use to the buyer (e.g., "Subscriptions are non-refundable upon purchase, regardless of utilization"), courts will not rewrite the bargain simply because one party failed to extract value from the asset.

In consumer contexts, US courts (e.g., In re Apple Inc. Device Performance Litigation) establish that digital storefronts must maintain transparent disclosures. If a user purchases an app or subscription and clicks "Agree" to terms that waive refund rights upon immediate access, courts routinely enforce the arbitration or liability waiver clauses, provided the clickwrap agreement met standard notice requirements.

C. Comparative Legal Framework Table

D. Liability, Defences, and Legal Uncertainty

To successfully defend against a lawsuit or chargeback for an unused product, a technology company must establish two core evidentiary pillars:

1. Delivery of Consideration: The platform must prove that the service, account credentials, or software license was successfully provisioned and made available to the customer. System access logs, API provisioning timestamps, and welcome emails serve as definitive proof of delivery.
2. Explicit Acceptance of Terms: You must prove the customer had actual or constructive notice of your refund policy before executing payment. Modern clickwrap agreements requiring an affirmative checkbox ("I agree to the Terms of Service and No-Refund Policy") defeat the common law defense of "mistake" or "lack of awareness."

The Takeaway: Actionable Compliance Playbook for Tech Founders

To insulate your startup from costly lawsuits, chargeback abuse, and regulatory inquiries regarding non-use refund demands, execute the following technical and legal safeguards immediately:

• Implement Bulletproof Clickwrap Agreements: Never rely on passive browsewrap agreements. Ensure your checkout flow requires an un-prechecked checkbox explicitly binding users to your Terms of Service and refund policy before payment processing completes.
• Capture Immutable Audit Logs: Configure your database and infrastructure provisioning tools (e.g., AWS CloudWatch, application logs) to record exact timestamps of user account creation, first login, and API key generation. This technical evidence obliterates claims that "we never received the product."
• Draft Explicit SaaS Refund Terms: Include crystal-clear language in your ToS: "All subscription fees are non-refundable. Failure to use, deploy, or access the software does not constitute grounds for a refund, credit, or pro-rata cancellation."
• Comply with Digital Waiver Mandates (EU/UK): If operating in Europe or the UK, insert a mandatory prompt during digital checkout where consumers expressly request immediate performance and acknowledge that they forfeit their 14-day statutory cooling-off right.
• Establish a Standardized Chargeback Response Template: Prepare a legal evidence packet for payment processors (Stripe, PayPal, etc.) containing the customer's IP address, timestamped ToS agreement, system access logs, and communications demonstrating service availability.

Disclaimer: This article is for informational and educational purposes only, does not constitute legal advice, and does not establish an attorney-client relationship. Technology companies and founders should consult with qualified legal counsel licensed in their specific operating jurisdiction before drafting consumer contracts or responding to active legal claims.

Frequently Asked Questions (FAQ)

Can a customer sue me if they bought my software, never logged in, and demanded a refund?

A customer can technically file a lawsuit or initiate a chargeback, but they will rarely succeed if your Terms of Service clearly state that all sales are final and you can prove that the software license or account was successfully provisioned and made available to them.

Does the 14-day EU cooling-off period apply to SaaS subscriptions if the user didn't use the app?

No. Under EU and UK consumer regulations, the right of withdrawal for digital content and services is waived if the consumer gave prior express consent to immediate performance and acknowledged that they would lose their cancellation right once access was granted.

What evidence do I need to defend against a chargeback for an unused digital product?

You need timestamped server logs showing account creation and access availability, IP address records, a copy of the Terms of Service agreed to at checkout, and proof that your refund policy was clearly disclosed prior to payment.

Are B2B software sales treated differently than B2C sales regarding refunds?

Yes. B2B transactions enjoy significantly greater contractual freedom. Courts generally hold commercial entities to the exact terms of their negotiated agreements, making 'buyer's remorse' or internal failure to deploy completely invalid grounds for a refund.

🚀 Build & Scale with SparkleCharge: Ready to architect, scale, or automate your production software platform? Partner with SparkleCharge engineering for high-availability full-stack systems. Schedule an Engineering Consultation or explore our Enterprise Technical Services.