Startup Refund, Cancellation and Chargeback Policy Checklist for India: D2C, SaaS, Marketplace and App Founders
A refund policy is not footer text. It is a promise that checkout, customer support, logistics, payment operations and accounting must all deliver in the same way.
Direct answer
A startup refund policy should answer five questions before payment: when a customer may cancel, what qualifies for return or refund, how to request it, when money will be sent, and who resolves a dispute. The operating workflow must match those words.
Use the Department of Consumer Affairs’ official Consumer Protection resources, the Consumer Protection Act, 2019 and the Consumer Protection (E-Commerce) Rules, 2020. Failed payment reversals are distinct from merchant refunds; RBI’s failed-transaction TAT framework applies to authorised payment systems. The Best CS Firm In India policy-design principle is simple: never promise a timeline that finance, logistics and the payment gateway cannot evidence.
First classify the customer journey
| Model | Cancellation point | Evidence that matters |
|---|---|---|
| D2C goods | Before dispatch, after delivery, defect or wrong item | Order, tracking, condition, images, pickup record |
| SaaS subscription | Trial end, renewal, downgrade or termination | Consent, usage, renewal notice, invoice, access logs |
| Marketplace | Seller acceptance, fulfilment and platform dispute | Seller terms, listing, communications, delivery proof |
| Digital content/app | Before or after access/download | Activation, download, consumption and defect logs |
| Services | Before work, after milestone or alleged deficiency | Scope, approvals, timesheets, deliverables, feedback |
Write the policy in nine parts
- Scope: products, services, territories and customer types covered.
- Eligibility: defect, deficiency, wrong item, non-delivery, duplicate payment, change of mind or service failure.
- Exclusions: clearly justified categories such as used, customised or fully consumed products, subject to applicable law.
- Request window: start event, calendar or working days and evidence required.
- Cancellation cut-off: order stage after which fulfilment or committed costs affect the result.
- Return logistics: pickup, shipping cost, condition check and risk of loss.
- Refund method: original payment method, wallet or another lawful agreed route.
- Timeline: internal approval, gateway initiation and expected bank posting separated.
- Escalation: grievance contact, acknowledgement and resolution workflow.
Do not confuse four different events
| Event | Who starts it? | Startup control |
|---|---|---|
| Merchant refund | Startup after an approved request | Eligibility, approval and initiation |
| Cancellation | Customer or startup before completion | Cut-off, costs and communication |
| Failed-payment reversal | Payment-system process | Reconciliation and support; RBI TAT may apply |
| Chargeback | Cardholder through issuer/network | Evidence response, representment and duplicate control |
Checkout disclosure checklist
- Show the policy link before payment, not only after purchase.
- Display total price, mandatory fees, tax, delivery and recurring nature.
- Use an unchecked, clear consent mechanism for recurring billing where required.
- State delivery or service timelines and material limitations.
- Explain cancellation and renewal in simple language.
- Keep a versioned record of the terms accepted for each order.
Build a refund decision matrix
| Reason | Decision owner | Standard evidence |
|---|---|---|
| Defective/wrong goods | Support + quality | Order, photos, inspection and inventory batch |
| Late/non-delivery | Operations | Promised date and carrier scans |
| SaaS technical failure | Product/support | Status logs, ticket and affected period |
| Duplicate debit | Finance/payments | Gateway IDs and settlement report |
| Fraud/unauthorised claim | Risk | Authentication, device, delivery and communications |
| Goodwill request | Authorized manager | Reason and approval limit |
Chargeback operating procedure
- Route every payment-partner notice into one monitored queue.
- Calendar the response deadline and reason code.
- Freeze duplicate merchant refunds while the chargeback status is checked.
- Assemble only relevant, authentic evidence: terms, order, authentication, delivery, usage and communication.
- Respond through the authorised acquirer or gateway channel.
- Reconcile the final debit, fee, tax and customer ledger.
- Feed the reason into fraud, product and support improvements.
Marketplace responsibility map
Do not tell customers to “contact the seller” if the platform has promised support, controlled payment or has its own legal duties. Define who handles seller approval, pickup, quality disputes, refunds, grievance escalation and evidence. Seller contracts should mirror the consumer-facing promise and fund reserves or recoveries where appropriate.
Finance and tax controls
- Link every refund to the original invoice, order and gateway transaction.
- Use credit notes and tax adjustments where applicable.
- Separate initiated, pending, successful, failed and chargeback statuses.
- Reconcile gateway reports, bank credits and the customer ledger.
- Restrict manual bank refunds through maker-checker approval.
- Monitor refund rate, ageing, repeat claimants and product-level reasons.
Common founder mistakes
- Copying a global template that conflicts with Indian consumer rules.
- Using “no refunds” even for defective, deficient or misdescribed supply.
- Starting a refund but giving no reference or realistic posting timeline.
- Refunding manually while a chargeback is already open.
- Letting customer support offer exceptions without authority limits.
- Changing the policy without retaining the version accepted by existing customers.
Founder / Business Takeaway
Run a monthly refund dashboard covering requests, approvals, initiation time, completion time, chargeback rate, ageing and root cause. A fair policy improves trust; a reconciled workflow protects cash and diligence readiness.
Free Weekly Newsletter
Subscribe to BSA startup funding alerts
- Every Sunday, all Indian startup funding alerts in one place
- Monthly funding report on the last day of the month
- Free, concise, founder-focused, and easy to unsubscribe
Get the complete Indian startup funding roundup in your inbox, covering deals, sectors, investor moves, and founder readiness notes from the week.
Built for founders, investors, CFOs, and advisors
No spam. Unsubscribe anytime.
Suggested internal links
FAQ
Is a no-refund policy always valid?
No. Consumer law, defects, deficiencies, misleading descriptions, late delivery, cancellation rights and the specific contract can restrict a blanket policy.
What should the policy disclose?
State eligibility, exclusions, request method, evidence, return logistics, refund destination, timelines and grievance escalation.
How should chargebacks be handled?
Preserve evidence, meet payment-partner deadlines, prevent duplicate refunds, reconcile the outcome and analyse reason codes.
