Protection Plans Sold at a Retailer: Who Is the Merchant of Record?
Protection plan merchant of record explained: when a retailer sells your plan, see who charges the card, who refunds returns and who answers chargebacks.

Photo: Pixabay
On this page 6 sections
- The Card Rule Behind the Protection Plan Merchant of Record
- How the Plan Reaches the Register Sets Who Charges the Card
- Remitting Plan Revenue Without Losing Track of Contracts
- Returns: A Worked Example of Who Refunds What
- Chargebacks on a Bundled Plan-and-Product Sale
- Retail Partner Agreement Terms to Settle Before Launch
Key takeaways
- Under Visa's rules, a merchant may submit only its own sales. Only registered models such as payment facilitators and marketplaces can deposit another business's transactions, and a typical retailer is neither one.
- Base the retailer's revenue share on plans that stay active, not on gross plan sales. Back that up with a return feed and a clawback window.
- In a retailer-sold program, the retailer receives every chargeback on the bundled sale. The provider should agree in writing to supply claim files on a short deadline.
- If the provider will be the merchant of record, it needs its own merchant account, an accurate MCC and a descriptor customers recognize before the first retail partner goes live.
When a retailer rings up a protection plan on the same receipt as the product, the retailer is the protection plan merchant of record. Its merchant account charges the card, and later it passes the plan price, minus its revenue share, to the plan provider. When the provider charges the customer through its own checkout, the provider is the merchant of record and pays the retailer a commission instead. That choice decides who refunds the customer, who answers the chargeback when the TV goes back to the store, and whose merchant account carries the risk.
Plan providers and obligors should settle this before they sign a retail partner. (The obligor is the company legally responsible for paying claims.) Remittance, refunds, disputes and the contract language all follow from it.
The Card Rule Behind the Protection Plan Merchant of Record
One network rule drives the whole decision. Visa's Global Acquirer Risk Standards say that, except as permitted for payment facilitators, a merchant "must only submit transactions that directly result from cardholder transactions with the merchant." When a business breaks that rule, Visa's Ecosystem Risk Programs Guide calls it transaction laundering. The guide notes it is also known as factoring and treats it as a form of money laundering.
Many people read that rule too broadly. It doesn't stop a retailer from charging for a protection plan. A retailer can sell a service contract that a provider backs, and when it does, the plan is the retailer's own sale. State service contract laws commonly distinguish the seller from the obligor, so one company can sell the plan while another pays the claims.
What the rule forbids is the in-between arrangement. On paper the provider is the real seller, but the money runs through the retailer's account because that account already exists. Visa permits processing another business's sales only through registered models such as payment facilitators and marketplaces. Its payment facilitator and marketplace guidance requires those platforms' seller agreements to prohibit any transaction that didn't come from an act between the cardholder and the seller. Most retailers are neither a payment facilitator nor a marketplace.
Before launch, answer three questions to find out which model you actually have:
- Who is named as the seller on the service contract the customer receives?
- Whose name appears on the receipt and the card statement descriptor?
- Who sets the plan price and takes the loss when a plan is cancelled?
If all three answers point to the retailer, you have a retailer-sold program. If all three point to the provider, the provider needs its own merchant account and its own checkout. If the answers are split, fix the paperwork or the payment flow before the first plan sells. The rules for sellers under state service contract law vary, so have counsel confirm what the contract must say in each state where plans are sold.
| Retailer-sold (retailer is merchant of record) | Provider-sold (provider is merchant of record) | |
|---|---|---|
| Who charges the card | Retailer, often in one transaction with the product | Provider, in a separate transaction |
| Statement descriptor | Retailer's name | Provider's name |
| Who issues card refunds | Retailer | Provider |
| Who receives chargebacks | Retailer | Provider |
| Revenue share direction | Retailer remits net plan price to provider | Provider pays commission to retailer |
| Processing risk sits with | Retailer's account | Provider's account |
The provider-sold model gives the provider control of the customer record and the cash. It also moves the processing risk onto the provider's own account. Underwriters often treat service contracts as future-delivery sales, because the customer pays today for coverage that runs for years. That's why high-risk merchant accounts for these businesses often come with reserves. Our explainer on why processors hold reserves on multi-year warranty sales covers the reasoning.
How the Plan Reaches the Register Sets Who Charges the Card
Most retail programs use one of four setups, and each one leans toward one of the two models.
Plan SKUs in the retailer's POS. The retailer loads plans as items, usually priced in bands, so each product price range maps to one plan SKU. The cashier adds the SKU and the customer pays once. The retailer is the merchant of record and sends plan sales to the provider by file or API. This is the simplest setup. Its weak spot is data: to register a plan, the provider needs the serial number, purchase date, product price and customer contact details, and a bare SKU sale captures none of them.
An integrated app or plugin. Some POS systems and e-commerce platforms support third-party apps that offer a plan when an eligible product is scanned or added to the cart. Depending on how the app is built, the plan either rides on the retailer's transaction or opens a separate checkout that the provider runs. Ask the app vendor which one you're getting, then run the three questions above against that answer.
A QR code or link at the register. The cashier presents the offer, and the customer scans a code and pays the provider on their own phone. The provider is the merchant of record, and the plan money never touches the retailer's POS.
Post-purchase offers. With the customer's consent, the retailer shares purchase data, and the provider follows up by email or text within the window its program allows. The provider charges the card. Retailers like this option because checkout stays fast. Outbound calls and texts bring telemarketing rules into play. Our guide to auto warranty telemarketing rules under the TSR and TCPA covers the same issues.
Online stores face the same choice. If the shopper adds a plan in the cart and pays through the store's own checkout, the store is the merchant of record. If a pop-up sends the shopper to the provider's checkout, the provider is.
Remitting Plan Revenue Without Losing Track of Contracts
In a retailer-sold program, the retailer holds the provider's money between the sale and the remittance. Agreements usually handle this in one of two ways. With net remittance, the retailer keeps its share and sends the rest along with a sales report. It's simple, but the provider sees only net figures unless the report is detailed. With gross remittance plus commission, the full plan price goes to the provider, which then pays the commission back. The gross figures stay clean, but there are two payments to reconcile each period.
Whichever method you choose, the reconciliation that matters most matches the plans the retailer sold against the plans the provider registered. Suppose a plan rang up at the register but never reached the provider's system. When that customer files a claim, the provider has no record of the contract, the claim is denied, and a card dispute often follows. Write a monthly match into the contract, keyed on transaction ID or serial number, with a deadline for fixing any gaps.
Timing matters too. Every day the retailer holds plan money, the provider is exposed to the retailer's finances. If a retail partner fails while holding weeks of unremitted plan sales, the provider still owes claims on those contracts and may end up chasing the cash. Shorter remittance cycles keep that exposure smaller.
Two more money questions belong in writing. In a retailer-sold model, the retailer pays card processing fees on the plan portion, and those fees come out of its share unless the contract says otherwise. Whether service contracts are subject to sales tax depends on the state, and the seller usually collects it. Our guide to how sales tax on extended warranties varies by state covers the details. Confirm both points with your accountant or tax adviser.
Returns: A Worked Example of Who Refunds What
Returns are where the two models differ most. The numbers below are illustrative assumptions, not market rates or any provider's actual terms.
Assume a $1,000 television sold with a $150 protection plan. The retailer's revenue share is 40% of the plan price, or $60, which leaves $90 for the provider. A few weeks later the customer returns the TV. The return falls inside both the store's return window and the plan's free-look period, which is the window in which a buyer can cancel for a full refund.
Retailer-sold. The retailer refunds the TV and the plan to the card in one transaction. Whether it gets back the processing fees on the original sale depends on its processor agreement, and many processors keep them. If the retailer has already sent the provider its $90, it recovers that amount, normally as a deduction from the next remittance. The provider also has to cancel the plan in its system so a later claim isn't paid by mistake.
Provider-sold. The retailer refunds the TV, but the $150 plan charge sits on the provider's merchant account. Nothing cancels it unless the retailer's return data reaches the provider. If that data never arrives, the customer sees a charge for protecting a TV they no longer own, and they dispute it. The provider can lose the full $150 plus a dispute fee, possibly after it has already paid the retailer its $60 commission. Two things prevent this: a return feed from the retailer to the provider, and a contract clause that claws back the commission on any plan cancelled inside the window.
The example leads to one decision: base the retailer's revenue share on plans that stay active, not on gross plan sales. Cancellations after the free-look period follow state law and the contract terms, which differ by state, so confirm them with counsel. Our article on service contract free-look periods and refund timing covers the timing questions. One workable arrangement has the retailer refund the original card while that's still possible, with the provider paying by check or ACH after that.
Chargebacks on a Bundled Plan-and-Product Sale
In a retailer-sold program, every chargeback on the bundled transaction goes to the retailer, including disputes about the plan. That's true even when the real complaint is about something only the provider controls, such as a claim denied months after the sale. Without the provider's records, the retailer can't build a defense. It needs the contract terms the customer accepted, the registration date and the claim file showing why coverage was denied.
Depending on the network and the reason code, a retailer may be able to accept part of a dispute and contest the rest, refunding the plan portion while defending the product. Ask your processor how partial representment works on its platform before you need it.
Under either model, a few habits lower dispute risk:
- Receipt line: name the plan, its term and the obligor instead of printing a bare SKU code.
- Descriptor: use one customers will recognize. Our guide to warranty billing descriptors customers don't recognize lists the common mistakes.
- Plan terms at the sale: send them by email or printout so the customer knows what's covered before filing a claim.
- Evidence turnaround: the provider should commit in writing to responding quickly, because dispute response deadlines are short.
Disputes over denied claims hurt warranty sellers the most, and they get their own treatment in extended warranty chargebacks over denied claims.
Retail Partner Agreement Terms to Settle Before Launch
Use this as the checklist for the agreement, and have counsel review it against the service contract laws in each state where plans will be sold.
- Merchant of record, stated plainly and matched by the seller named on the service contract, the receipt and the descriptor
- Remittance method and timing, net or gross, with the report format and required fields
- Revenue share base calculated on active plans, with a clawback window for cancellations
- Processing fees and sales tax, stating who pays and who collects
- Registration and return feeds, with deadlines and a monthly reconciliation
- Refund responsibility inside and after the free-look period
- Chargeback allocation, with evidence turnaround times and loss sharing by dispute type
- Run-off terms that keep claims service going for plans already sold after the partnership ends
If you're setting up a retail plan program, compare what your store keeps under Extend, Mulberry and Clyde against the processing responsibilities above.
If the provider will be the merchant of record, its own processing setup has to come first. That means an accurate merchant category code (see which MCC fits a warranty company), a descriptor customers recognize and an acquirer that understands multi-year contracts. To find out how a provider-sold program would be underwritten, request a free quote. A MannyPay specialist will respond within one business day.
Sources
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


