If a digital download never arrives, contains unsafe software, or is materially different from its listing, save the evidence and start the appropriate support or payment process. Contact the seller in writing. Then use the platform or payment provider before its deadline.
Digital download scams often leave a gap between the promise and what you receive. It might be no file, a dead link, copied work, or a program that behaves dangerously. Check the seller, product, delivery path, and payment route before paying.
Thing is, a complaint and a refund request do different jobs. The FTC's ReportFraud service helps investigators spot patterns, but it does not reverse a charge. The steps below are for U.S. consumers.
Digital download scam red flags
A single problem may be a mistake. Several together deserve caution.
- No clear delivery path: The seller promises instant access but provides no order record, download instructions, or working support channel.
- Vague or inflated promises: Claims such as guaranteed income, instant business success, or permanent investment returns are warning signs.
- Missing previews: A course has no sample lesson, an eBook has no sample pages, or music has no reliable preview.
- Pressure to pay quickly: Countdown timers, sudden price increases, and messages urging you to leave the platform can cut short normal checks.
- Copied or mismatched content: The images, reviews, author name, or product description appear to belong to someone else.
- Suspicious software behavior: A file asks you to disable security tools, install an unexpected program, or grant permissions unrelated to its purpose.
- Unclear NFT details: The seller cannot provide a contract address, creator identity, transaction history, or a clear explanation of what the purchase includes.
- No practical remedy: The seller hides refund terms, ignores basic questions, or offers only a social-media account instead of usable support.
Turns out, a polished storefront proves very little. Check each part of the transaction separately.
What to inspect for each type of download
Different products create different risks. Verify what you can before payment, and save the page while it is still available.
| Product | What to check | What to save |
|---|---|---|
| Software, templates, or mods | Publisher identity, download domain, file type, security warnings, and requested permissions | Listing, file name, seller messages, and any security alert |
| eBooks and courses | Author or instructor identity, sample pages, table of contents, promised modules, and licensing claims | Listing screenshots and examples of missing or copied material |
| Music and video | Artist identity, track list, file format, preview, and delivery method | Receipt, listing, and the actual file details |
| NFTs or digital art | Creator account, contract address, token page, transaction record, and stated rights | Wallet address, transaction hash, listing, and messages |
An on-chain transaction can be genuine without proving that the seller created the work or delivered the promised rights. Keep those questions separate.
If a downloaded file may be dangerous
Treat a suspicious file as a security problem, not just a bad purchase. Stop opening it.
If you already ran the file and see pop-ups, unexpected programs, account alerts, or other unusual activity, disconnect the device from the internet if doing so is safe.
Run security checks with trusted software. Change exposed passwords from a clean device, especially if you entered a password on a suspicious page. Contact your bank or payment provider promptly if you submitted card, bank, or account credentials.
Keep the original file and its warning details as evidence, but don't forward it. A suspicious attachment can create another victim.
Preserve evidence before requesting a refund
Collect records before asking for money back. Listings disappear, and support pages can change.
| Record | Why it matters |
|---|---|
| Receipt and payment confirmation | Shows the amount, date, seller, and payment method |
| Listing URL and screenshots | Captures what the seller promised |
| Seller messages and support requests | Shows when you asked for help and how the seller responded |
| Delivery email, broken link, or account screen | Supports a non-delivery or access problem |
| File name and security warning | Explains why the download was unsafe or unusable |
| NFT wallet address and transaction hash | Identifies the blockchain transaction and seller activity |
To be honest, a clear timeline usually helps more than an angry description. Write down what you bought, what arrived, when you contacted the seller, and which remedy you requested. Keep the dates.
Which refund or complaint policy controls the purchase?
One purchase can involve several separate processes. The platform may decide whether its purchase protection applies, PayPal may apply its transaction terms, and a card issuer may use a different dispute process.
An FTC report is separate from all three. Refund rules usually depend on the platform and the payment method, so identify both before choosing a route.
| Situation | First route | Deadline or rule to check |
|---|---|---|
| Etsy digital order | Etsy Help with order and, if eligible, an Etsy case | Etsy's case instructions list conditions including seven days since purchase and 48 hours after the Help with order request. Etsy says refunds processed by Etsy must be within 180 days of the transaction. Eligibility varies by location and order. |
| Gumroad or another direct storefront | Support route in the receipt or account, followed by the original payment service | Do not assume one storefront deadline applies to every seller. Check the receipt and payment terms immediately. |
| Steam game or software application | Steam refund request | Steam's refund policy uses a standard window of two weeks from purchase and under two hours of playtime. Separate rules can apply to pre-purchases, gifts, and some payment methods. |
| PayPal payment | PayPal Resolution Center | PayPal's US Buyer Protection terms state that an Item Not Received dispute must be opened within 180 days of payment. A Significantly Not as Described dispute has a separate deadline of 30 days after delivery or fulfillment, or 180 days after payment, whichever comes first. |
| Credit or debit card payment | Card issuer's dispute process | Ask the issuer about its deadline, evidence requirements, and next steps. Contact it quickly instead of waiting for a platform response. |
Steam's two-week rule is a company policy. It is not a universal U.S. refund period for every digital product. It does not automatically cover a course, eBook, NFT, or key bought elsewhere.
Each process makes its own decision. An FTC report supports enforcement and scam tracking, but it does not guarantee an individual refund.
Steps to request a refund and report the seller
Use these steps in order when possible. Do not let a slow support reply push you past a payment deadline.
-
Stop further loss and save proof. Don't keep retrying a suspicious link or downloading replacement files. Save the listing, receipt, messages, and delivery problem before contacting support.
-
Contact the seller in writing. State the purchase date, the promised product, the actual problem, and the refund or correction you want. Use the platform's messaging system when possible.
-
Open the platform's official process. On Etsy, start with Help with order and follow the case instructions if the order qualifies. On Steam, submit a refund request through Steam and describe the purchase accurately. For Gumroad or another storefront, use the support route shown in the receipt or account instead of a social-media message.
-
Use the payment provider before its deadline. For PayPal, choose the correct dispute category in the Resolution Center and include the listing, payment record, and seller messages. If you paid by card through PayPal, tell the card issuer about the PayPal dispute and ask how it wants you to proceed. Don't assume two separate disputes will be handled the same way.
-
Report the conduct to the FTC. File at ReportFraud.ftc.gov. Include the seller name, listing or website, amount, date, payment method, contact details, and a factual description of what happened. The FTC says these reports help build cases, stop scammers, and alert others to current trends.
How to write a useful complaint
A useful complaint gives the reviewer dates and a concrete failure. Describe what the listing promised, not what you assume the seller intended.
Use this structure:
On [date], I paid [amount] for [product]. The listing promised [specific feature or delivery]. I received [missing, broken, unsafe, or materially different result]. I contacted the seller on [date], and I am requesting [refund or other remedy].
Attach the receipt and screenshots. Keep the wording factual. Don't exaggerate, guess at the seller's motives, or call a file malware unless you have recorded the relevant warning or scan result.
Common questions
Can PayPal refund a digital download?
Possibly, if the transaction and problem fit PayPal's eligibility rules. Open the dispute within the applicable deadline and provide evidence. PayPal decides under its terms; no automatic refund applies to every digital purchase.
Does Steam's 14-day, two-hour rule cover every digital product?
No. Steam describes that standard offer for games and software applications sold through the Steam store. It is not a general rule for eBooks, courses, NFTs, music, or purchases made from another seller.
Should I wait for the FTC before disputing the payment?
No. Use the marketplace, PayPal, or card issuer deadline first. File the FTC report separately.
What should I do if the file contains malware?
Stop opening it. Secure the device and accounts, preserve the relevant evidence, and contact the payment provider. Report the seller to the platform and the FTC. If financial credentials were exposed, contact the bank or card issuer promptly.
Start with the receipt: note the payment date, identify the applicable platform or payment deadline, and open the first eligible dispute. Then file the FTC report separately.