Merchant of Record chargebacks: who responds, and which records matter?

A Merchant of Record handles the payment-side relationship for the transactions it sells. Your SaaS team still needs to identify the customer, investigate the complaint, and follow the provider's actual case process. Before drafting a response or promising a refund, establish who can take that action and whether your evidence can be submitted.

This matters for both a B2C subscriber disputing a personal plan and a B2B buyer disputing a company workspace. Product support, the person paying, and the party handling the card dispute may sit in different organizations.

Which party sold this transaction?

Start with the receipt and transaction record. The software brand on a customer's screen does not, by itself, identify the seller of the payment.

Keep the seller entity, order and payment IDs, amount, currency, subscription period, customer account, and workspace together. Record the statement descriptor too. If the complaint begins with an unfamiliar charge, first follow the subscription-charge recognition investigation.

A business can sell some subscriptions directly and others through a reseller. The customer's current plan or email address is therefore insufficient to choose the response route. Find the actual purchase. A case for a reseller-sold order will not automatically appear in your separate processor account.

Who handles the chargeback, and can you supply evidence?

The answer depends on the provider and account process. Handling the card-network interaction does not mean every provider gives the software supplier the same controls.

Sources: Polar's terms, sections 6 and 10, Paddle's Billing help, Lemon Squeezy's help, and Dodo's dispute guide. These are scoped descriptions, not a vendor ranking or a universal response procedure.

There is a source conflict worth preserving: Paddle's customer handbook describes requesting seller communications and usage logs, while its Billing help says additional evidence is not accepted. The pages do not resolve that difference. Confirm the instructions for your account before preparing a custom packet.

What belongs in the supplier's investigation?

Keep the relevant product history even when the payment-side provider does not offer an extra upload. Those records can still explain a support commitment, a provisioning failure, or a requested correction. They should answer the actual complaint, rather than merely demonstrate that the account exists.

For a personal subscription, connect the disputed payment to the purchased service and the relevant access or usage period. For a company workspace, also identify the billed organization, affected member, and scope of any support promise. A message about one workspace should not silently become a refund commitment for every subscription owned by the company.

Retain a small investigation record:

• The customer's claim in their own words and the formal dispute reason, if available.
• The historical plan, offer, cancellation request, or support commitment relevant to that claim.
• Source references for meaningful product activity and failures, linked to the account and period.
• Any refund, service credit, or provider adjustment already created, with its current state.
• The person responsible for the next permitted action and the deadline source.

Use the chargeback-evidence guide to select relevant records. A support history that contradicts the proposed response belongs in the investigation too. More account activity does not erase an earlier promise to cancel or refund.

A refund promise meets a balance deduction

Illustrative case. A company buys a reporting workspace through a Merchant of Record. A scheduled export fails. Support tells the billing contact, “We will arrange a refund for the affected month.” The contact also challenges the payment through the card issuer. Finance later sees a supplier-balance deduction and receives a handoff saying “refund completed.”

The deduction alone does not explain what happened. It might relate to the formal dispute or another adjustment. The support message establishes a commitment, not its execution. Sending a separate payment without checking the provider-side state could create an additional, unlinked payment.

The same method applies to a B2C subscriber whose individual plan failed. Keep the scope smaller, but still distinguish the promise, provider action, and customer-facing confirmation. If support and finance disagree about the state, use a named handoff with source records, rather than forwarding another ticket link.

Why the dispute outcome and payout need separate checks

An action on the case and a movement in your supplier balance answer different questions. Link both to the original transaction and keep any fee or later reversal separate. Do not use a payout total as the only evidence that a particular customer received money.

Read the provider's adjustment explanation alongside the case status. Then reconcile the specific amount and currency, any outstanding action, and the customer communication. The refund-versus-chargeback cost guide explains how to separate those money movements without assuming one fee model.

Where Evidenz helps a SaaS supplier

Evidenz is designed for B2B and B2C SaaS teams that need the payment, account, support, and product histories to explain one another. In a Merchant of Record case, its intended value is the supplier-side investigation: which workspace the order covers, what failed, what support promised, and which source supports the explanation.

That focus makes Evidenz a strong fit when the payment dashboard holds the formal case but the missing context lives in the product and helpdesk. The next action still follows the Merchant of Record's permitted process. Organizing a traceable history should make the team's finding clearer; it should not turn an unavailable evidence channel into an assumed submission feature.

Questions that come up during the handoff

Can support promise a refund before the provider acts?

Support should distinguish requesting or arranging a refund from confirming a completed one. Check the team's authority, the applicable provider route, and the exact scope of the promise. Confirm execution only from a verified action record. If the promise has already been made, preserve it and assign someone to check the next step.

Does a Merchant of Record absorb every chargeback loss?

Do not assume that payment-side handling means the supplier carries no financial effect. Inspect the applicable agreement and transaction adjustments. The provider table above describes different workflows; it does not establish a universal allocation of losses or fees.

Should we prepare evidence if no extra upload is available?

Investigate enough to understand and resolve the product complaint, preserve relevant commitments, and answer any permitted provider request. Select attachments only for an available channel and the actual claim. A complete internal finding can be useful without implying that the issuer will receive every record.