Data Recovery Payment Policy: Deposits, No-Data, No-Fee and Disputes
Build a data recovery payment policy that holds up: when to take deposits, how to define no-data, no-fee, bill partial recoveries and win disputes.

Photo: Pixabay
On this page 7 sections
- Evaluation Fees and Tiered Quotes in a Data Recovery Payment Policy
- Define "Data" Before You Promise No Data, No Fee
- Bill Partial Recoveries From a Rate the Customer Already Signed
- Get Written Approval When Teardown Changes the Price
- Your Quote Sets the Terms of Any Dispute
- Proof of Delivery: File Listings and Customer Sign-Off
- Building the Response to a Data Recovery Chargeback
Key takeaways
- A signed "all sales final" clause won't stop a Visa 13.3 dispute. A written definition of success, signed by the customer, is the strongest evidence you can bring to one.
- Visa's 13.1 window can run 120 days from the date the customer expected the service (up to 540 days from the transaction). Put your turnaround estimate and every revised date in writing.
- Visa authorizations last 5 to 10 days and a Mastercard final authorization lasts 7. Charge the final balance as a new transaction the customer approved separately.
- Put the partial-recovery rate and donor-part billing in the signed quote. Then the final bill is simple math the customer already agreed to.
A data recovery payment policy holds up when three things are settled in writing before you charge the full price. The first is what the customer owes if recovery fails. The second is what "recovered" means for this particular job. The third is proof that the customer reviewed the recovered files before paying. Get those right and the terms you set at intake become the evidence a card issuer reads if the customer ever disputes the charge. Skip them and you invite the classic lab chargeback: a customer gets a drive full of data back, then tells their bank it wasn't what they paid for.
This work is hard to bill. The price depends on what you find inside the device, and the result is often partial. Card disputes handle neither situation well, so your quote has to settle both before any money moves.
Evaluation Fees and Tiered Quotes in a Data Recovery Payment Policy
Most jobs start with an evaluation, where you diagnose the failure and work out what recovery will take. Whether you charge for it is your call. Before the customer ships or drops off the drive, tell them in writing whether the evaluation costs anything. If it does, say whether that fee gets credited toward the recovery.
Tiered quotes fit this work because jobs really do fall into levels. Logical recovery is for a drive that spins and reads. Electronic or firmware repair is the next step up. Physical work in a clean room or under a flow hood, such as a head swap on a crashed hard drive, sits at the top. It costs the most because it ties up controlled-environment bench time and often uses parts you can't get back.
Set your prices from your own costs. The table shows what each tier's price has to cover.
| Tier | Typical failure | What the price has to cover |
|---|---|---|
| Evaluation | Any device | Diagnosis time; whether the fee is credited later |
| Logical | Drive reads; deleted files or a damaged file system | Software and bench time |
| Electronic or firmware | Drive won't spin up or isn't detected | Repair time and replacement boards |
| Physical (clean room) | Clicking drive or failed heads | Controlled-environment time and donor parts |
Donor drives cause the most arguments. Physical recoveries often need a matching donor drive for parts, which you buy and usually can't return. If you bill donor parts even when the recovery fails, the quote has to say so in plain words, right next to the no-fee promise.
A data recovery deposit makes sense when you're about to spend money for the customer, such as buying that donor drive. Make the deposit cover that cost, and say whether it's refundable. Collect it when the customer approves a tier, not at intake. Before anyone knows what's wrong, a deposit is payment for work that may never happen. Processors treat that as delivery risk, and tech support businesses already get close attention on that point. Our guide to tech support processing fees, reserves and holds explains how that risk shows up in your pricing.
Define "Data" Before You Promise No Data, No Fee
A no-data, no-fee offer answers the customer's biggest fear: paying a lot and getting nothing back. It protects you only if "data" is defined.
Define it by the customer's priorities, not by byte count. At intake, ask for a short priority list and write it on the work order. A typical list might name a QuickBooks company file and a folder of family photos. Then write the definition of success into the quote: those items recovered in usable condition, meaning the files actually open. A file name showing up in a directory doesn't count. If a drive gives back hundreds of thousands of system files and none of the photos, that customer sees a failure, whatever the raw percentage says.
Next, list what the promise doesn't cover. Donor parts used on the job are the most common exception. Return media (the external drive you ship the data back on) comes next, and some labs also exclude an expedited evaluation fee. Each exception is fair on its own. The complaints come when a "no fee" headline hides its exceptions a page further down. Put each exception next to the promise everywhere the promise appears, from your ads to the signed quote. Underwriters read your ads before they approve an account, as covered in tech support ads that get merchant accounts terminated.
Bill Partial Recoveries From a Rate the Customer Already Signed
Partial results are normal. Damaged platters develop bad sectors, and some files come back with the right names but corrupted contents. Decide in advance what the customer pays for each outcome so the final bill never turns into a negotiation:
- All priority items recovered and verified: full tier price.
- Some priority items recovered, customer accepts the data: the partial rate stated in the quote.
- Some priority items recovered, customer declines the data: disclosed exceptions only.
- No priority items recovered: no recovery fee; disclosed exceptions only.
Worked example (illustrative numbers, not market prices). A bookkeeper brings in a clicking desktop drive. Her priority list has two items: the QuickBooks company file and a folder of client tax PDFs. Assume the lab quotes the physical tier at $1,600, plus a $180 donor drive that the quote says is billed whenever it's used. Also assume the lab's policy sets the partial rate at half the tier price.
After the head swap, the QuickBooks file opens and reconciles. Most of the older PDFs open, but about a third of the recent ones are corrupted. Some priority items came back and some didn't, so this counts as a partial outcome. She accepts the data. Her bill is half of $1,600, or $800, plus the $180 donor drive, for a total of $980.
Without a written partial rate, the lab has two bad options. It can charge the full $1,780 and argue, or it can guess at a discount after the fact. With the rate in writing, the customer sees a number she already agreed to.
Pick whatever partial rate fits your costs. The outcome categories just need to be in the signed quote, and the customer needs to decide whether to accept a partial result before you charge for it. This is general information, not legal advice. Have an attorney in your state review your quote language.
Get Written Approval When Teardown Changes the Price
Often you don't know the real tier until the drive is open. A job quoted as a firmware fault may turn out to need new heads, or a clean room inspection may find platter scoring that lowers the odds of recovery. When that happens, stop and get new approval before you start the more expensive work.
Written approval means a record you could hand to a bank, like an email reply or an e-signature on a revised quote. A phone call is a good way to explain the change, but send the revised quote afterward and wait for a written yes. Show the old price, the new price and the reason for the change. Say whether the no-data, no-fee terms still apply at the new tier.
Card charges need the same discipline, because authorization holds don't last long. Under Visa's framework, a card-present authorization is valid for five days. A card-absent one that the cardholder started, such as a phone or online order, is valid for 10 days, according to Chargebacks911's summary of Visa's authorization rules. Mastercard gives a final authorization 7 days and a pre-authorization 30 days, per the scheme table in Adyen's documentation. A clean room job that sits in a queue for a few weeks will outlast most of those windows.
So don't place a hold at intake and plan to capture it when the job is done. Take the deposit as its own sale. Run the final balance as a new transaction, backed by the customer's written approval of that amount. If you placed a hold you won't use, reverse it. Visa expects merchants to promptly reverse authorizations they won't use, so confirm the exact timing with your processor. The validity periods above are network rules, and your processor and gateway may apply shorter ones, so check what your account allows.
Mail-in labs take most payments as keyed, card-not-present transactions. Those generally cost more than a chip or tap payment at a counter, and the merchant usually carries the fraud liability. A virtual terminal for keyed card payments handles those charges. For safer ways to collect card numbers than having customers read them aloud, see taking cards by phone for tech support. Walk-in customers can pay by chip on a POS set up for repair tickets and check-in.
Your Quote Sets the Terms of Any Dispute
Many lab owners believe a signed "no refunds" or "all sales final" clause blocks a chargeback. It doesn't. Visa doesn't let a merchant's refund policy or "all sales final" terms override the cardholder's right to dispute under condition 13.3, as Chargeback.io's summary of the 13.3 rules explains. What your paperwork can do is give the issuer a clear record to compare against.
Visa's Dispute Management Guidelines for Visa Merchants list two consumer dispute conditions that match typical lab complaints. Condition 13.1 is Merchandise/Services Not Received, and condition 13.3 is Not as Described or Defective Merchandise/Services. Under 13.3, the issuer checks whether the service matched the description on the receipt or other documents, or what you told the customer on a phone order. Your written definition of success is that description. Mastercard runs its own dispute rules with similar categories, and your processor's notice will tell you which code a case arrived under.
Your turnaround estimate matters too. For 13.1, the issuer has 120 calendar days from either the processing date or the last date the cardholder expected the service, capped at 540 days from the transaction, according to Chargebacks911's guide to reason code 13.1. Say you quote a job at roughly two weeks (an illustrative figure), and it slips to six weeks with no written update. The customer now has a fair "not received by the agreed date" claim, and the dispute window keeps sliding forward with each missed date. Every time the estimate changes, send the new date in writing.
When a dispute does arrive, move fast. Visa's response window on the merchant side is 30 days, per Chargebacks911's Visa time-limit guide. Your processor will set its own earlier deadline within that, so ask what it is.
Proof of Delivery: File Listings and Customer Sign-Off
The file listing is your strongest evidence and your best customer service tool. Before final payment, send the customer a listing of what you recovered, including the directory tree with file counts and sizes. Mark each priority item as verified or not, and flag any that came back with errors. A few screenshots of priority files open on your bench add weight.
Ask the customer to confirm in writing that the listing matches what they expect, or to tell you what's missing. You want "that's not all my files" to come up now, before payment. Sometimes the missing files are there under a different path. Other times they were never on that drive and actually lived on another laptop or in a cloud account. Finding that out before the charge costs far less than finding it out in a dispute.
Then take payment and keep a record of how the data reached the customer. A secure download leaves an access log showing when the customer pulled the files. On higher-value jobs, ship return media with signature confirmation, and have walk-in pickups sign a release. Keep the working image for a retention period you state in writing. If the customer calls a week later about a missing folder, the image lets you check the facts instead of guessing.
Building the Response to a Data Recovery Chargeback
Your response has to show that the customer agreed to a defined outcome and received it. Build the packet in this order:
- The signed quote, including the priority list, the definition of success and the expected turnaround.
- Any revised quote, with the customer's written approval.
- The file listing the customer reviewed, plus their written sign-off.
- Proof of delivery: a download log, signed tracking or a pickup release.
- Your messages with the customer, including any offer to re-check the image.
Keep the packet short and clearly labeled. A clear timeline persuades an issuer more than a thick stack of loosely related documents. For more on presentation, see our guide to winning "I was scammed" tech support chargebacks.
Sometimes a refund is the better choice. Suppose a customer says a priority file is corrupted and your verification notes are thin. A partial refund under your own policy, issued before they file a dispute, often costs less than the dispute fee plus the time it takes to fight. It also keeps the case out of your chargeback count, which processors watch closely for tech services. Your refund and cancellation windows should explain how a customer asks for that review.
This week, pull your five most recent physical recoveries and check each one for three things. You're looking for a written definition of success built on the customer's priority list, a turnaround date that was updated in writing whenever it slipped, and a file listing the customer signed off on. Any job missing one of these would be a hard dispute to win. If you're setting up processing for a lab that takes deposits and keyed mail-in payments, MannyPay offers merchant accounts for low- and high-risk businesses, including high-risk merchant accounts. You can request a free processing quote, and a MannyPay specialist will respond within one business day.
Sources
- Visa: Dispute Management Guidelines for Visa Merchants (June 2024)
- Chargebacks911: Visa Reason Code 13.1, Merchandise/Services Not Received
- Chargebacks911: Visa Chargeback Time Limits
- Chargeback.io: Visa 13.3, Not as Described or Defective Merchandise/Services
- Chargebacks911: How Do Credit Card Authorizations Work?
- Adyen Docs: Authorization Adjustment (scheme authorization validity table)
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.


