What should be included in a refund policy?

A useful refund policy tells customers what can be returned or canceled, the conditions that apply, the time window for making a request, how to start the process, and what outcome to expect. It should reflect the business's actual products, services, fulfillment methods, and operating capacity rather than copying generic language that staff cannot follow.

Define which purchases are eligible

Start by identifying the transactions covered by the policy. Explain whether physical goods, custom orders, digital products, appointments, subscriptions, deposits, or completed services are treated differently. If some items are final sale or subject to special conditions, name those categories clearly before purchase.

Use plain language to describe acceptable return condition, packaging or proof-of-purchase expectations, and any exceptions the business actually supports. Avoid broad promises such as “all purchases are refundable” unless that is consistently true. A policy should help a customer predict the result without requiring access to internal procedures.

State the request window and available outcomes

Timing

State when the request period begins and ends. Distinguish a return deadline from a cancellation cutoff when the business offers both.

Resolution

Explain whether an eligible request may result in a refund, exchange, store credit, replacement, rescheduled service, or another stated outcome.

Method

Describe how approved refunds are normally returned and identify any processor-specific limitation only after confirming it with the current provider.

Do not promise a universal posting date. A merchant may initiate a refund promptly while the customer's provider or card issuer controls later processing. If timing varies, say what the business controls, what it does not control, and how the customer can request a transaction reference or status update.

Explain the customer request process

Give customers a usable contact route and list the non-sensitive information needed to locate the purchase, such as an order number, receipt number, purchase date, item, and reason for the request. State who pays for return shipping when relevant, where an authorized return should go, and whether prior authorization is required.

Never ask a customer to email a full card number, security code, password, bank credentials, or secret account information. Staff should locate the original transaction through approved business systems and follow the processor's refund workflow. General forms and ordinary email are not appropriate places to collect payment credentials.

Present the policy before the sale

Placement matters. Square's current dispute-prevention guidance recommends writing out and presenting return, refund, and cancellation policies on receipts or other agreements made at the point of sale, such as a contract or invoice. Its dispute-document guidance also emphasizes evidence that the customer acknowledged the policy before purchase, including a signed document or an online click-to-agree step when appropriate.

A website policy can still be useful, but it should be easy to find from product, service, checkout, and customer-support paths. Keep the wording consistent across the website, checkout, invoice, contract, receipt, and staff script. When the policy changes, preserve the version that applied to each transaction so the business can show what the customer saw at that time.

Keep records that support consistent handling

Record the request date, original transaction, decision, customer communications, returned-item status, refund reference, and completion status. Use reason categories that help the business identify recurring product, fulfillment, or service problems without storing unnecessary sensitive information.

Train staff on who may approve exceptions and how those exceptions are documented. Consistent handling reduces confusion, but a written policy is not a guarantee that every dispute will be resolved for the merchant. Dispute outcomes depend on transaction facts, evidence, provider processes, and applicable rules.

Review business-specific requirements

Refund, return, cancellation, warranty, gift-card, and consumer-notice requirements can vary by product, service, sales channel, and jurisdiction. This page offers operational planning guidance, not legal advice. Have qualified counsel review the policy when the business operates under specialized consumer rules, sells across jurisdictions, takes advance payments, uses recurring billing, or limits remedies.

For related planning, visit the chargebacks and disputes FAQ hub, review the fraud prevention and security hub, and explore the merchant account FAQ hub. These resources help organize questions for a provider or adviser without asserting a specific legal or processing result.

Turn the policy into a repeatable workflow

Map each policy statement to a staff action, customer message, record, and escalation owner. Then test the process using typical return, cancellation, partial-refund, and exception scenarios. Confirm refund capabilities and transaction limits directly with the current payment provider, and obtain legal review where the policy creates or limits customer rights.

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.