← Blog

SAAS OPERATIONS

How to Write a Refund Policy for SaaS and Digital Products

Anyway Team

· 7 min read ·

To write a SaaS refund policy, identify the legal seller, define covered products, state refund eligibility and request deadlines, explain subscription cancellation and partial periods, address consumed credits and downloads, describe the request process, preserve mandatory consumer rights, and connect every decision to the original order and product-delivery records.

This guide provides an operating checklist, not legal advice. Consumer rights can vary by buyer location, product type, and delivery method. Have qualified counsel review the final policy for the markets you serve.

The refund policy checklist

  1. Name the legal seller and support contact.

  2. List the products and billing models covered.

  3. State when a refund may be requested.

  4. Explain subscription cancellation separately.

  5. Define treatment of credits, downloads, and usage.

  6. Cover duplicate charges and failed delivery.

  7. Describe the request and review process.

  8. Preserve statutory consumer remedies.

Step 1: Name the seller and support route

The customer needs to know who sold the product and where to request help. Put the support email and required order information in the policy.

If a Merchant of Record is the legal seller, the customer receipt and transaction records should reflect that arrangement. The developer still owns product delivery and first-line product support under the merchant relationship.

Anyway is the Merchant of Record for covered Business sales. Its order records connect the customer, product, payment status, amount, payment method, and order ID. The order ID gives support a focused reference for each request.

Step 2: Separate each product type

A single sentence rarely fits every digital product. Write distinct rules for the offers you sell:

SaaS subscription

Explain renewal, cancellation, the paid-through date, and whether a refund is available for the current or previous period.

One-time software purchase

Explain whether eligibility changes after activation, license delivery, or substantial use, subject to applicable law.

Downloadable product

Explain when delivery begins and what customer consent is collected before immediate download.

Prepaid credit pack

Define whether unused credits are refundable, how consumed credits are measured, and what happens when a technical fault prevents use.

The policy should match the checkout and product behavior. A credit policy is not useful if the app cannot produce a reliable credit ledger.

Step 3: Define refund eligibility

Use specific, reviewable conditions. Examples can include:

  • Duplicate purchase review

  • Delivery or access review after confirmed payment

  • Product-support resolution for a technical issue

  • Product or amount correction

  • Refund right required by applicable consumer law

  • Request approved under a stated satisfaction policy

Avoid vague phrases such as “refunds may be granted at our discretion” without any process. The customer and support agent should be able to reach the same answer from the same facts.

Step 4: State the request deadline

Choose a window that fits the product and local law, then say when the clock starts. It might begin on the purchase date, renewal date, or delivery date depending on the rule.

Do not treat a private deadline as overriding a mandatory legal remedy. A customer may have rights when digital content or a digital service is faulty even after the seller's voluntary satisfaction window has closed.

The European Commission explains that EU consumers can seek repair, a price reduction, termination, or a refund when covered digital content or services are not in conformity. The exact remedy and sequence depend on the applicable rules.

Step 5: Explain subscription cancellation

Cancellation stops future renewal according to the subscription terms. A refund reverses an existing payment. Keep those actions separate in the policy and account interface.

State:

  • How to cancel

  • Whether cancellation takes effect immediately or at period end

  • The date access ends

  • Whether the current period is refundable

  • What happens after a trial

  • How a plan change affects billing

Anyway's current subscription flow schedules cancellation at the end of the paid period. The record can remain active until currentPeriodEnd, with cancelAtPeriodEnd showing the scheduled state.

See how to accept global subscription payments for the event and access model.

Step 6: Address immediate digital delivery

Digital content can be delivered seconds after payment. Consumer law can impose specific information and consent requirements around immediate performance.

UK government guidance says a seller of downloads or streaming content must obtain the consumer's agreement to immediate delivery and acknowledgment that the ordinary 14-day cancellation right will be lost before the download or stream begins. If the seller does not follow those steps, the consumer can retain the cancellation right.

The EU Consumer Rights Directive also covers withdrawal from online digital-content contracts and the consequences of failing to provide required information.

Do not reduce these rules to a universal checkbox sentence. SaaS, downloads, human-performed services, and mixed products can receive different treatment. Review the final checkout language for the countries you target.

Step 7: Describe the request process

Tell the customer what to send:

  • Order ID

  • Account email

  • Product name

  • Purchase or renewal date

  • Reason for the request

  • Screenshot or error detail when relevant

Set an internal response target the team can meet. Keep the request focused on the Anyway order ID, product, purchase date, and relevant support details.

Step 8: Connect the policy to product records

Support needs evidence from the same systems that delivered the product:

  • Policy question: Was payment confirmed?; Record to check: Anyway order status

  • Policy question: Which product was sold?; Record to check: Product ID and payment link

  • Policy question: Who received access?; Record to check: Merchant reference and internal user

  • Policy question: Was a subscription renewed?; Record to check: Subscription and renewal order

  • Policy question: Was cancellation scheduled?; Record to check: cancelAtPeriodEnd and period end

  • Policy question: Were credits consumed?; Record to check: Application credit ledger

  • Policy question: Was the file delivered?; Record to check: Entitlement or signed-download log

Anyway webhooks carry signed order and subscription events. Use webhook-id for idempotency and preserve the Anyway order ID beside the product entitlement.

The SaaS payment webhook guide explains how to build that verified order trail.

A practical SaaS refund policy outline

Use this outline as a drafting structure:

1. Seller and contact information 2. Products covered by the policy 3. Voluntary refund eligibility 4. Request deadline and how it is measured 5. Subscription cancellation and renewal 6. One-time software and downloads 7. Credit packs and consumed usage 8. Purchase corrections and delivery support 9. How to submit a request 10. Review, approval, and payment timing 11. Statutory consumer rights 12. Policy version and effective date
1. Seller and contact information 2. Products covered by the policy 3. Voluntary refund eligibility 4. Request deadline and how it is measured 5. Subscription cancellation and renewal 6. One-time software and downloads 7. Credit packs and consumed usage 8. Purchase corrections and delivery support 9. How to submit a request 10. Review, approval, and payment timing 11. Statutory consumer rights 12. Policy version and effective date
1. Seller and contact information 2. Products covered by the policy 3. Voluntary refund eligibility 4. Request deadline and how it is measured 5. Subscription cancellation and renewal 6. One-time software and downloads 7. Credit packs and consumed usage 8. Purchase corrections and delivery support 9. How to submit a request 10. Review, approval, and payment timing 11. Statutory consumer rights 12. Policy version and effective date

Write plain sentences under each heading. Do not add rules your product cannot measure or your support team cannot apply.

How a clear refund policy reduces disputes

A buyer is more likely to contact support when the path is visible and the likely outcome is understandable. That gives the seller a chance to fix access, explain a renewal, correct a duplicate purchase, or approve a refund before the issue becomes a card dispute.

Keep the policy linked from the pricing page, checkout context, receipt, and customer account. Send subscription terms again after enrollment.

For checkout, delivery, tax, and payout context, see how to sell digital products globally.

Read the SaaS chargeback guide for transaction recognition, fulfillment evidence, and dispute response.

Frequently asked questions

Does a SaaS business have to offer refunds?

The answer depends on the applicable consumer law, product, defect, seller promises, buyer location, and contract. A voluntary policy cannot remove mandatory legal remedies.

Is canceling a subscription the same as getting a refund?

No. Cancellation controls future billing or access according to the subscription terms. A refund reverses an existing payment.

Can a “no refunds” policy override consumer law?

No. Mandatory consumer rights can apply even when a private policy says sales are final. Review the policy and checkout consent for the markets you serve.

What information should a refund request include?

Ask for the order ID, account email, product, purchase date, reason, and relevant support details.

Should unused AI credits be refundable?

Set a clear voluntary rule based on unused balance, expiration, product economics, and applicable law. An auditable credit ledger helps support apply the rule consistently.

Turn the policy into a working process

A refund policy is useful when checkout, support, product access, subscription state, and order records all apply it consistently.

Anyway connects the legal sale, product, order, subscription, signed events, and Finance record. Create an Anyway account and test the purchase, customer-support, delivery, and refund paths before publishing the policy.

Official sources checked