Lemon Squeezy Refunds and Chargebacks: What the Merchant of Record Actually Handles

A $100 subscription renewal succeeds. The order is paid, the customer gets access, and the transaction looks ordinary. Three weeks later, the customer says they do not recognize the charge and contacts their card provider. At that point, the useful question is not simply whether Lemon Squeezy “handles” chargebacks. It is which part Lemon Squeezy handles — and which part can still reach the seller’s economics.

That distinction is the real consequence of the Merchant of Record model. Lemon Squeezy sits in the payment relationship, takes responsibility for a substantial layer of transaction administration and generally deals with the chargeback process on the seller’s behalf. But its own documentation also makes clear that refund and chargeback amounts can be reflected in the seller’s next payout.

What “handling” a chargeback actually means

A Merchant of Record is the legal entity selling goods or services to the end customer. Lemon Squeezy’s documentation says the Merchant of Record is responsible for handling payments and takes responsibility for purchase-related obligations including sales-tax collection, refunds, chargebacks and PCI compliance. Lemon Squeezy states that it acts in that role for sellers.

That is materially different from merely providing a checkout button. The seller still creates and operates the product, but Lemon Squeezy occupies the payment-side commercial position. Its statement descriptor documentation makes this visible to the customer: purchases appear as LEMSQZY*STORE, with STORE representing the actual store ID.

Four different responsibilities are hidden inside one sentence

The phrase “Lemon Squeezy handles chargebacks” becomes much clearer when it is broken into four separate questions.

Those are not interchangeable responsibilities. A seller can outsource most of the payment-administration burden without outsourcing every financial consequence of a reversed transaction.

The part a “no refunds” policy cannot control

Lemon Squeezy encourages sellers to choose their own refund policies based on their businesses. Sellers can issue full or partial refunds from the Orders area, and the platform’s refund documentation says refunds can be issued at any time.

But Lemon Squeezy also states something that is easy to miss when reading a store’s own “no refunds” language: it reserves the right to issue a refund within 60 days of purchase, at its own discretion, to prevent chargebacks. It also explicitly warns that customers can still initiate chargebacks even if a seller has chosen a no-refunds policy.

I would therefore treat a no-refunds policy as a customer-service policy, not as a guarantee of payment finality. It can define the seller’s normal response to refund requests and set expectations before purchase. It cannot remove the external card-dispute system, and it does not eliminate Lemon Squeezy’s stated MoR-level discretion during that 60-day window.

What happens when an actual chargeback lands

Lemon Squeezy describes a chargeback as a customer asking their credit card provider to cancel a charge on the statement. Its documentation lists examples such as a stolen card, an unrecognized charge, or a customer claiming they did not receive the product and going directly to the card provider instead of requesting a refund.

The key wording is deliberately qualified. Lemon Squeezy says it is generally responsible for handling chargebacks, and that in most cases it will offer a full refund on the seller’s behalf and deduct the refunded amount, minus the platform fee, plus a $15 dispute fee from the next payout.

That is different from saying “Lemon Squeezy absorbs the chargeback loss.” The operational process is handled by the Merchant of Record; the documented settlement mechanics still connect the reversed transaction to the seller’s future payout.

There is also a limit to Lemon Squeezy’s control over the outcome. The company says it provides as much information as it can to the payment provider to make a case on the seller’s behalf, but after that the payment provider decides the outcome. Lemon Squeezy can manage the case; it cannot guarantee that the dispute will be decided in the seller’s favor.

A clean $100 example using Lemon Squeezy’s published fees

Because Lemon Squeezy publishes its fee structure, this example can use a transparent published-fee model instead of a placeholder. The goal is not to claim that every $100 transaction has identical economics, but to isolate the refund and chargeback mechanics under one clearly stated set of assumptions.

Now run the same transaction through three different endings.

The point of this example is not that every $100 Lemon Squeezy dispute costs exactly $109. It does not. International cards, PayPal, non-subscription payments, taxes, volume pricing and other conditions can change the underlying fee. The point is that the platform publishes enough information to model a transparent scenario without inventing a placeholder.

The post-sale dispute window is the useful mental model

The broad idea of “revenue finality” is already relevant to Lemon Squeezy payout planning, so it is more useful here to frame the problem specifically as post-sale dispute exposure.

This matters because the dashboard showing a successful payment answers one question — did the transaction go through? — while a later refund or dispute answers another — did the seller ultimately keep the economic value of that transaction?

I would not use this section to rebuild Lemon Squeezy’s payout calendar. That is a separate subject. If you need the full timing, threshold and payout-cost mechanics, our Lemon Squeezy payout guide covers that in detail. Here, the only relevant point is that refunds and chargebacks can change a future payout after a sale has already been recorded.

Who actually does what?

The Merchant of Record model becomes much easier to understand when the four parties are separated.

This is why “outsourced chargeback handling” and “zero chargeback exposure” are not synonyms. Lemon Squeezy removes a meaningful amount of payment-operations work while the seller still has reasons to prevent disputes upstream.

Refund versus chargeback: the economics are not identical

From a pure cost perspective, that extra $15 makes an avoidable chargeback more expensive than the equivalent straightforward refund under the documented formula. The account-risk dimension makes the difference more important than $15 alone.

Why a proactive refund can sometimes be the better operating decision

There is no universal rule that every dissatisfied customer should be refunded. A merchant may have strong evidence that a product was delivered and used correctly, may be dealing with obvious abuse, or may reasonably enforce a clearly disclosed policy. But the dispute path has an additional cost and an additional risk signal that a normal refund does not have.

That changes the decision for borderline cases. If a customer is genuinely confused about a renewal, cannot recognize the charge, or has a support problem that can be resolved without a bank dispute, the seller has something concrete to weigh: the amount at stake, the strength of the evidence, the support time involved, the customer history, the likelihood of escalation and the documented chargeback cost.

When I model a refund and a chargeback side by side, the important question is not “who presses the refund button?” It is whether the problem can be resolved before it becomes a formal dispute that adds a fee and contributes to chargeback history.

Too many chargebacks become a different kind of problem

An isolated dispute is mostly a transaction-level event. A pattern of disputes becomes an account-level event. Lemon Squeezy’s documentation states that if a store has too many chargebacks, its team may intervene and suspend the account.

What the public page does not provide is an exact threshold — no published percentage, monthly count or fixed formula is given on the reviewed refunds-and-chargebacks page. That means it would be misleading to import a threshold from Stripe, Visa, Mastercard or a third-party blog and present it as Lemon Squeezy’s own suspension rule.

The practical implication is simpler: a founder should monitor chargebacks as a pattern, not just as individual $15 fees. The absence of a published numeric cutoff makes prevention and support discipline more important, not less.

Not every dispute starts with obvious fraud

Lemon Squeezy says chargebacks can happen for a variety of reasons, typically fraud, and gives concrete examples. One is a stolen card. Another is a customer who simply does not recognize the charge. A third is a customer who believes the product was not received and contacts the card provider rather than asking the seller for a refund.

That middle case is especially relevant to the statement descriptor. Lemon Squeezy documents that customers see LEMSQZY*STORE, not a product name, on their bank statement. A seller therefore should not assume that making the product title descriptive will make the bank line item self-explanatory.

The better prevention strategy is to make the store identity recognizable across checkout, receipt emails, renewal messages and support. If a customer sees LEMSQZY* followed by a store identifier months after the original purchase, the seller wants the rest of the customer communication to make that relationship easy to reconstruct.

What the seller still owns

Lemon Squeezy can operate the payment and dispute infrastructure, but it cannot run the product experience for the merchant. The upstream causes of disputes are still largely under the seller’s control.

• Product accuracy: describe what the customer receives without overselling access, features or outcomes.
• Renewal clarity: make recurring billing terms understandable before the customer forgets the original purchase context.
• Reachable support: give customers a realistic path to resolve a billing or access problem before they reach for the dispute button.
• Cancellation usability: avoid making a legitimate cancellation needlessly difficult or ambiguous.
• Store identity: keep branding and receipt communication consistent enough that a LEMSQZY*STORE descriptor can be recognized later.
• Internal refund notes: track why refunds happen in your own support or analytics workflow, even if you are not relying on a platform-provided “reason code” feature.
• Delivery/access evidence: keep appropriate records that can help explain whether a digital product or account was delivered and used.
• Dispute trend monitoring: watch frequency and recurring causes rather than treating each chargeback as an isolated surprise.

None of those responsibilities contradict the value of Merchant of Record. They define its boundary. Lemon Squeezy removes a hard payments layer; it does not replace the seller’s product, support or customer communication.

What I would check before the first chargeback happens

If I were setting up a new Lemon Squeezy store, I would want the dispute mechanics understood before the first complaint arrives, not after. My short operating checklist would look like this:

• Know where full and partial refund controls are located in Orders.
• Understand that seller-defined refund policy and Lemon Squeezy’s 60-day discretionary authority are separate concepts.
• Know the current published chargeback fee before forecasting net revenue.
• Make subscription renewal language visible and understandable.
• Keep billing-related support accessible enough to intercept genuine confusion.
• Make store branding consistent across checkout, receipts and support so customers can connect the purchase with the statement descriptor.
• Track why customers ask for refunds internally and look for repeat causes.
• Keep appropriate proof of access, delivery or account activity where that evidence exists.
• Review chargebacks as a store-level trend, because Lemon Squeezy explicitly warns that too many can trigger intervention.

The actual trade-off of Merchant of Record

Lemon Squeezy’s Merchant-of-Record model is valuable precisely because a small software or digital-product business does not have to operate the entire payments-compliance and dispute stack independently. Lemon Squeezy takes responsibility for the MoR layer, generally handles chargebacks, processes refunds and deals with the payment-provider side of a dispute.

The trade-off is that the Merchant of Record also needs authority over the transaction. Lemon Squeezy can issue some refunds at its own discretion within the documented 60-day window, and the platform’s published rules allow refund and chargeback adjustments to flow through a future payout. That is not a contradiction. It is part of the same operating model.

The phrase “Lemon Squeezy handles chargebacks” is therefore accurate only when the word handles is understood properly. It means the seller does not have to run the external dispute process themselves. It does not mean a successfully completed checkout becomes economically irreversible or that Lemon Squeezy guarantees the seller will retain the value of every disputed transaction.

For a founder, that is a reasonable trade: substantially less payments administration in exchange for accepting the MoR’s dispute rules and payout-adjustment mechanics. The most useful preparation is not trying to eliminate every refund. It is knowing where the operational responsibility moved, where the economic exposure remained, and what customer-experience problems can be fixed before a bank ever becomes involved.

For pricing, fee stack, subscriptions, licensing and the broader platform assessment, return to our Lemon Squeezy rating and review.