If you paid for a digital download that never arrived, preserve your records before repeatedly retrying the download. Capture the order, the promised delivery terms, the failed access attempt, and your contact with the seller. Then request a working replacement, restored access, or a refund in writing. If the seller doesn't resolve the issue, use the dispute process for your payment method before its deadline.
For U.S. consumers, the deadline depends on how you paid. A written credit-card billing dispute generally must reach the issuer within 60 days after the statement containing the error was sent. PayPal's published terms generally use a 180-day payment deadline, with a possible shorter deadline tied to delivery or fulfillment. Debit cards, prepaid cards, ACH payments, and wires have different procedures.
This is general consumer information, not legal advice. Your contract, payment method, account type, and state law may affect the result.
Identify the problem before choosing a dispute reason
Payment providers may handle these situations differently, so use the description that matches the facts:
- Non-delivery: You paid but received no working link, license key, file, or account access.
- Defective or incomplete content: The file is corrupted, empty, locked, the wrong version, or unusable as promised.
- Not as described: The product or license differs materially from the seller's description or order confirmation.
- Revoked access: The seller or SaaS provider disabled access after payment. Check whether you paid for a subscription period, a perpetual license, or a limited access term.
- Recurring billing after cancellation: The charge occurred after you canceled or were told that the subscription would end.
- Unauthorized transaction: You didn't make or approve the purchase.
An authorized purchase that failed to download isn't automatically an unauthorized transaction. Likewise, a faulty file isn't the same issue as a copyright takedown.
Preserve evidence that connects the payment to the failure
Keep the original records in one folder and make backup copies. Use filenames such as 2026-03-04-order-confirmation.pdf so the timeline is easy to follow.
| Evidence | What it can show | Limitation |
|---|---|---|
| Receipt, invoice, and card statement | What you bought, the price, merchant, and transaction date | A statement alone doesn't show whether access worked |
| Product page and checkout terms | Promised format, delivery method, license period, and refund terms | Save a PDF or screenshot because the page may change |
| Download link and error message | That the link was broken, expired, blocked, or returned an error | Include the full visible URL and the date and time |
| Account screenshots | A missing library item, disabled account, or revoked access | Show the account identifier without exposing your password |
| Emails and support tickets | Your attempts to resolve the issue and the seller's response | Keep complete threads, not only selected messages |
| The downloaded file | Whether the file opens, contains the expected content, or is the wrong version | Preserve the original before testing or modifying it |
| File hash | Whether two copies are identical or different | A hash doesn't prove who caused the difference |
| Cancellation confirmation | When you ended a subscription and what the seller promised | It may not prove that the cancellation was processed correctly |
Also record the merchant name as it appears on your statement, the order number, purchase date, promised delivery date, and amount. If a marketplace or payment intermediary was involved, record both the seller and the payment descriptor.
How to use a file hash
A hash is a mathematical fingerprint for a particular file. SHA-256 is a common choice. If the seller published an expected SHA-256 value and your file produces a different value, that supports a claim that your copy isn't identical to the advertised file.
You can calculate a hash with built-in tools:
- Windows PowerShell:
Get-FileHash "file.zip" -Algorithm SHA256 - macOS:
shasum -a 256 file.zip - Linux:
sha256sum file.zip
Save the command output with the filename, file size, and date of calculation. Keep the original file unchanged and make a working copy for testing.
A hash is much less useful when there is no trustworthy reference value. It identifies your copy, but it can't establish that the seller supplied a different file, that the file was corrupted during transmission, or that the product was defective. Hashing also can't prove non-delivery because there is no file to hash.
Blockchain timestamps and NFTs have similar limits. They may show that a record or token existed at a certain time, but they don't automatically prove that you received usable content, that a wallet belongs to you, or that the seller owes a refund.
Steps to take after a failed download
1. Preserve the first failure before troubleshooting
Take screenshots of the product page, order status, account page, and error message. Include the device date and time when possible. Save the confirmation email and the terms that applied when you paid.
You can try another browser or device, but document the first failure before doing so. If you download the file more than once, keep the original copies separate and label each attempt.
2. Check what you purchased
Confirm whether the transaction was for:
- A one-time download
- A license key with an activation limit
- A subscription or time-limited access plan
- Content supplied through a marketplace
- A pre-order or delayed release
Look for expiration dates, device limits, regional restrictions, file-format requirements, activation rules, and refund exclusions. A seller's use of the label "digital product" doesn't by itself establish that delivery was complete.
3. Contact the seller in writing
Use the seller's support email or ticket system. State what you paid for, what was promised, what happened, and the remedy you want. A short, factual message is easier to use later as evidence than an angry or lengthy exchange.
Subject: Order [number] - digital content not delivered
I paid [amount] on [date] for [product]. The order promised [download, license, or access]. On [date and time], I tried to use it and received [exact error or result]. I contacted support on [date] and have not received a working resolution.
Please provide a working replacement, restore access, or issue a refund. I have attached the receipt, relevant terms, screenshots, and support history. Please respond by [reasonable date].
Don't send your full card number, password, recovery codes, or private encryption keys. If the seller offers a refund, confirm the amount and refund method in writing.
4. Prepare a focused dispute packet
Put the records in chronological order:
- When and how much you paid
- What the seller promised
- When and how you tried to download or access the content
- The exact failure
- When you contacted the seller
- The seller's response, or lack of response
- The remedy you want
Attach the receipt or statement, applicable terms, screenshots, support messages, and any relevant file or hash output. Highlight the important facts instead of sending dozens of unrelated screenshots.
Keep unedited originals in case the issuer, platform, mediator, or court asks how a screenshot or file was created. Redact full account numbers, passwords, security codes, and unrelated personal information.
Use the payment method's dispute process
A seller's refund policy and a payment dispute are separate. A card issuer or payment platform may investigate even when the seller refuses a voluntary refund, but no provider guarantees a particular result. Check the deadline immediately instead of waiting indefinitely for the seller's response.
Credit-card purchases
For a personal credit-card purchase, a digital product that was never delivered or wasn't delivered as agreed may fit the federal billing-error process. The issuer will decide how to classify and evaluate the dispute.
The FTC's credit-card dispute guidance says to send a written dispute to the issuer's billing-dispute address so that it reaches the issuer within 60 days after the statement containing the error was sent. Use the address listed for billing inquiries or disputes on the statement, not necessarily the address where payments are sent.
Include:
- Your name and account information
- The transaction date and amount
- The merchant name
- The reason you dispute the charge
- The date you contacted the seller
- Copies of the receipt, terms, error messages, and correspondence
Keep a copy of the letter and attachments. The FTC says the issuer generally must acknowledge the complaint within 30 days unless it has already resolved the issue, and resolve the dispute within two billing cycles, with a maximum of 90 days.
The FTC also says you don't have to pay the disputed amount or related finance and other charges during the investigation, but you should continue paying undisputed charges and follow the issuer's instructions. The FTC's guidance on goods and services you never received covers the same 60-day written-dispute period and investigation deadlines.
Don't rely only on a phone call if you want to use this written billing-error procedure. If the issuer says the claim doesn't fit that procedure, ask promptly whether it has another merchant-dispute process and what deadline applies.
PayPal payments
PayPal has its own dispute process and eligibility rules. Its published Purchase Protection terms state that a dispute must generally be opened within 30 days of the date of delivery or fulfillment, when applicable, or within 180 days of the date you sent the payment, whichever is sooner.
Open the case promptly through the applicable PayPal process. Upload a concise evidence packet and explain whether the content was never delivered, couldn't be accessed, or materially differed from the description. If the seller doesn't resolve the dispute, follow the next step in PayPal's Resolution Center before the applicable deadline.
PayPal makes its own decision under its policy. A PayPal result isn't the same as a court ruling or a finding under federal billing-error law.
If you funded the PayPal payment with a credit card, tell both providers about the other dispute. Don't seek duplicate recoveries without following their instructions, because the procedures can affect one another.
Debit cards, prepaid cards, ACH payments, and wires
The federal credit-card billing-error procedure and its 60-day written-notice rule shouldn't automatically be applied to debit cards, prepaid cards, ACH payments, or wire transfers. Contact the bank or payment provider promptly and ask which dispute category and deadline applies.
Select a category that accurately describes the problem, such as merchandise or services not received if the provider offers that option. Use the unauthorized-transaction process only when you didn't authorize the payment.
Bank transfers and wires may be difficult or impossible to reverse after completion, so delay can reduce your options. Keep the confirmation number and ask the provider to explain any required written notice or documentation.
What doesn't prove non-delivery by itself
Some technical or account records can support your timeline without proving the entire dispute:
- A screenshot: It shows what appeared on your screen, but not necessarily the full transaction history.
- A hash mismatch: It shows that two files differ. It doesn't alone prove that the seller acted improperly or that the advertised hash was accurate.
- A seller download log: It may show a request or link click, not that the transfer completed, the file opened, or the file matched the promised version.
- A blockchain record or NFT: It may show a token or timestamp, not delivery of usable content or an entitlement to a refund.
- A DMCA notice: The DMCA addresses copyright takedown procedures. It isn't a general method for recovering money from a seller that failed to deliver.
- A chargeback decision: It is a payment-provider decision under a particular process, not a final legal judgment.
If access was removed because of a copyright complaint, separate the access problem from the payment problem. Ask the seller or platform why access was removed and whether it will restore access or refund the affected purchase. A copyright counter-notice is a specialized step that can involve legal statements; it isn't a routine substitute for a refund request.
If the seller claims you received the download
Ask for an explanation tied to your account and order:
- What date and time was the download recorded?
- Which filename and version were supplied?
- Did the event show a completed transfer or only a link click?
- Was the license activated on your account?
- Why can't you access or open the content now?
You don't need to argue about technical logs. Explain the gap between the seller's record and the result you experienced, then provide your own timestamps, screenshots, and error messages.
When to escalate
Open the payment dispute while its deadline is still available. If a credit-card issuer denies a written billing dispute, ask what evidence it relied on and whether it accepts additional documents or a reconsideration request. Follow the issuer's instructions and keep the denial.
For a larger claim, review the seller's agreement before filing anything. Look for an arbitration clause, required notice period, governing-law provision, small-claims limits, and available remedies. A lawyer or local legal-aid service may help you assess whether further action is practical for the amount involved.
Frequently asked questions
Do I need a hash to win a digital download dispute?
No. A hash is useful for a corrupted or altered file when you have a trustworthy comparison value. For non-delivery, the order record, failed-access proof, and written support history usually matter more. No single type of evidence guarantees the result.
How soon should I contact my credit-card issuer?
As soon as you know there is a problem. For the federal written billing-error process described by the FTC, your written notice must reach the issuer within 60 days after the statement containing the error was sent.
Can I charge back a digital purchase through PayPal?
You can open a PayPal dispute if the transaction fits its current rules. PayPal's published terms generally use a 180-day deadline, with possible shorter limits tied to delivery or fulfillment. Eligibility and the final decision depend on PayPal's policy.
Is the DMCA the right way to request a refund?
Usually not. The DMCA concerns copyright notices and access removal. A failed-download refund should normally begin with the seller and the payment provider's applicable dispute process.
What should I do if the seller has already refunded me?
Tell the payment provider and close or update any duplicate dispute as instructed. Keep confirmation of the refund, and don't accept more than the amount you paid.