An online course refund request is easier to evaluate when your records answer four questions: What did you buy? What were you promised? What happened? When did you ask for help?
Start with the seller or course platform when its policy provides a refund route. If you paid with a U.S. credit card and the problem may qualify as a billing error, you may also have a separate issuer dispute process. The FTC's credit card dispute guidance says written notice generally must reach the issuer within 60 days after the first bill showing the error was sent to you.
That deadline applies to a qualifying credit-card billing dispute. It is not a platform refund deadline, and it does not automatically apply to debit cards, ACH payments, prepaid cards, wires, or payment apps. Your payment method, purchase route, platform terms, and the facts of the complaint all matter.
Identify the dispute before collecting evidence
The first route and the most useful records depend on what went wrong.
| Problem | First route | Most useful evidence | Important limit |
|---|---|---|---|
| Refund under a platform policy | Course platform or seller | Receipt, policy, purchase date, refund request | The platform may apply policy exceptions |
| Course not delivered or materially different from the listing | Seller, then the card issuer if eligible | Sales promise, access records, messages, payment record | The issuer decides whether the transaction qualifies for a billing dispute |
| Unauthorized charge | Card issuer or bank fraud department | Statement, account alerts, and records showing you did not authorize the transaction | Do not report an authorized purchase as fraud |
| Subscription renewal | Platform or app store | Cancellation timestamp, renewal notice, and statement | Canceling future service does not automatically reverse an earlier charge |
| Misleading advertising or suspected scam | Seller, payment provider, and possibly the FTC | Saved advertisement, checkout page, payment record, and correspondence | An FTC report is separate from a private refund request |
A platform's refund promise is a company policy. A credit-card billing dispute is a separate issuer investigation under applicable law and the issuer's procedures. Keep those deadlines and standards separate.
Build a dated evidence file
1. Prove what you bought
Keep the order confirmation, invoice, receipt, or subscription email. It should show as much of the following as possible:
- Course or program name
- Seller or platform name
- Purchase date and amount
- Transaction or order number
- Currency
- Renewal date, if it was a subscription
- Payment method and the merchant name or descriptor shown on the statement
A bank or card statement shows that money was charged. It does not, by itself, show what the course promised or whether the service was unavailable, incomplete, or materially different. Pair the payment record with evidence about the specific problem.
2. Preserve the promise made at checkout
Save the sales page, course outline, advertisement, checkout screen, and refund terms that applied when you paid. Look for claims about:
- Course contents or number of lessons
- Live sessions or instructor access
- Certificates, credentials, or institutional recognition
- Job, income, health, or other results
- Trial periods and automatic renewals
- Access duration and downloadable materials
- Refund eligibility and exclusions
Use a full-page print-to-PDF or screenshots that show the relevant wording, page title, and full web address. Record the date and time. Keep the original files instead of saving only a cropped sentence.
The FTC's truth-in-advertising guidance says the same advertising standards apply online and offline, and that the agency pays particular attention to claims that can affect consumers' money. That does not make every disappointing result an unlawful advertisement. Your records should connect a specific representation to a specific shortfall.
For example, "includes six live instructor sessions" is more precise than "best course available." A canceled session, missing recording, or support response can then be compared with the exact promise.
3. Document access and delivery
Save screenshots or other records showing what happened after payment:
- Dashboard enrollment
- Locked or missing lessons
- Incorrect course title or account assignment
- Progress and completion status
- Download history, where relevant
- Canceled or missed live sessions
- Certificate status
- Dates when access stopped or was restored
Record your use honestly. Some platform policies restrict refunds after substantial course consumption or downloads. For example, Udemy's refund policy lists notable consumption or downloading as a possible restriction.
An access screenshot shows what you saw at a particular time. It may not show why the problem occurred or whether the page later changed. Pair it with the receipt, support ticket, and dated messages.
4. Keep the full communication record
Save the original email thread, not only the last reply. Include:
- Your refund or cancellation request
- The platform's response
- Ticket numbers
- Dates and times
- Attachments and links
- Any promise that access, a refund, or a correction would be provided
Do not recreate the history in a new message. A short factual summary can help, but preserve the original correspondence underneath it. Export important emails or save them as PDFs, and keep copies outside the platform account in case access is removed.
5. Create a simple timeline
A chronology often makes the issue easier to review than a large folder of screenshots.
| Date | Event | Supporting record |
|---|---|---|
| May 2 | Purchased the course | Receipt and card statement |
| May 2 | Sales page promised live sessions | Saved sales page |
| May 3 | First attempted access | Dashboard screenshot |
| May 5 | Reported missing content | Email or support ticket |
| May 8 | Requested a refund | Request and delivery record |
| May 10 | Refund denied | Platform response |
Use the actual dates from your records. Distinguish the purchase date from the date the charge appeared on your statement, the date you canceled, and the date you contacted support.
6. Protect sensitive information
Redact passwords, security codes, full card numbers, and unnecessary personal information. Leave enough information for the recipient to match the charge, such as the transaction date, amount, merchant name, and last four digits when appropriate.
Do not send a complete bank statement if one highlighted transaction record is enough. Store the evidence securely and avoid posting it publicly.
Platform policies determine which records matter
Udemy refund evidence
Udemy says eligible courses can be refunded within 30 days of purchase if the request meets its policy guidelines. The policy also lists restrictions that may apply when:
- A notable amount of the course was consumed or downloaded
- The account was reported, banned, or had access disabled for a terms violation
- A third party has already issued a refund
- Udemy lacks information needed to review the request
If an instructor cancels or fails to attend a booked session, Udemy's policy says the session receives a full refund.
For a Udemy request, save the purchase-history record, receipt, course page, current progress, download status, and all support replies. Submit the request through the account or support route shown by Udemy, and keep the submission confirmation. The 30-day platform window is separate from the 60-day written-notice period for a qualifying credit-card billing error.
Coursera refund and accreditation evidence
Coursera's Terms of Use say that Coursera and content providers do not have to have content recognized by an educational institution or accreditation organization.
If your complaint concerns accreditation, institutional credit, or a certificate, save the exact wording used at checkout and identify who made the statement. Keep any communication from a university, employer, licensing body, or course provider that contradicts the marketing.
Coursera products can differ, including individual courses, subscriptions, and programs purchased through another organization or store. Do not assume one universal U.S. refund period. Check the order confirmation, product-specific terms, renewal details, and the route used to pay. A refund period from a different Coursera product or purchase channel may not control your transaction.
The terms also contain dispute-procedure provisions, including language about pursuing disputes individually rather than through a class or representative action. Read the terms that applied to your purchase before choosing an escalation route.
Skillshare subscription evidence
Skillshare says members can cancel before renewal to avoid future subscription charges. Its help page also warns that deleting the mobile app does not cancel the subscription. If the purchase was made through Apple's App Store or Google Play, the Skillshare refund page directs customers to request the refund through the relevant app store.
Save the cancellation confirmation, account screen showing the next billing date, renewal email, and statement entry. For a Skillshare session that has already ended, the same help page says to email support within 48 hours of the scheduled session start and explain why you are requesting a refund.
Skillshare's page describes separate cooling-off information for customers in the European Union and United Kingdom. Those rules are not automatically U.S. rules. A U.S. customer should rely on the terms and purchase route that apply to the account.
How to request a refund from the platform
Send a short, specific written request. If you authorized the purchase, describe the delivery, access, quality, or billing problem accurately instead of calling it fraud.
You can adapt this format:
Subject: Refund request for [course or subscription] - order [number]
I purchased [name] on [date] for [amount]. I am requesting a refund under [the relevant policy or order term]. The listing stated "[short, exact quote]." The problem is [specific missing, unavailable, canceled, or materially different service]. I contacted support on [date], and the response was [brief summary]. Please confirm the decision and any next steps in writing. I have attached the receipt, relevant terms, access records, and correspondence.
Attach only documents that support the points in the message. Ask for a written decision even if you also speak with support by phone. If the company offers credits or an extension instead of money, decide whether that actually solves the problem before accepting it.
If an app store or another organization processed the purchase, check whether that intermediary controls the refund request. Keep the platform's response even when you must submit the request somewhere else.
Using evidence for a U.S. credit-card billing dispute
A card dispute is not a second platform refund form. It is an issuer review of a card transaction.
If you authorized the purchase but the course was not delivered as agreed or was materially different from the deal, describe those facts. If you did not authorize the transaction at all, use the issuer's fraud channel instead.
For a U.S. credit-card dispute:
- Check the first statement showing the charge. Note when that statement was sent. The FTC's billing-error guidance uses that statement as the starting point for the written-notice deadline.
- Contact the merchant promptly. Ask for the promised refund in writing and save the response. Do not let an unresolved support ticket push you past the issuer's deadline.
- Write to the issuer's billing-dispute address. The FTC says the notice should reach the issuer within 60 days after the first bill containing the error was sent. Use the address listed for billing inquiries or disputes on the statement instead of assuming a general customer-service address is sufficient.
- Identify the transaction clearly. Include your name, the account information requested by the issuer, charge date, amount, merchant, and a factual explanation of what was not delivered or was not as agreed.
- Send a focused evidence bundle. Include the statement, receipt, saved promise or terms, timeline, merchant request, and response. Keep copies and proof of delivery.
- Respond to follow-up questions. The FTC guidance says the issuer generally must acknowledge the complaint within 30 days unless it has already resolved it, and resolve the dispute within 90 days.
- Watch for the final decision. A temporary credit, if provided, is not necessarily the final result. Tell the issuer if the merchant later refunds you so the records do not show duplicate recovery.
The federal process described by the FTC applies to qualifying credit-card billing errors. Debit cards, prepaid cards, ACH payments, wires, and payment apps can have different rules, deadlines, and procedures. Contact the provider shown on the transaction record as soon as possible and ask which dispute category and deadline apply.
What makes evidence persuasive
A refund is not guaranteed by any single document. Records are more useful when they are:
- Contemporaneous: created close to the purchase, access problem, cancellation, or complaint
- Complete: includes the surrounding terms and the full message thread
- Identifiable: shows the account, course, order, date, or transaction
- Consistent: the receipt, statement, timeline, and emails tell the same story
- Relevant: each document supports a specific fact
- Unaltered: original files are retained, with edits limited to privacy redaction
Reviews and testimonials can show that other students had similar experiences, but they usually do not prove your order, payment, or communications. A certificate can show completion, but it does not prove that a program had accreditation or that its marketing was accurate. Platform terms show the company's stated policy; they do not necessarily state every right that may apply.
Common mistakes to avoid
- Calling an authorized purchase fraud. Report the delivery, quality, or billing problem accurately.
- Saving only a cropped advertisement. Keep the full page, URL, date, and surrounding qualifications.
- Confusing cancellation with a refund. Cancellation may stop a future renewal without reversing a prior charge.
- Deleting the app and assuming the subscription ended. Use the account or app-store cancellation route and save confirmation.
- Waiting for support indefinitely. Platform deadlines and card-dispute deadlines can run separately.
- Sending altered or excessive evidence. Clear, relevant records are easier to review than hundreds of duplicate images.
- Sharing full financial credentials. A merchant or issuer should not need your password or complete card number.
For suspected deception or a scam, you can file a report through ReportFraud.ftc.gov. Save the report number with your evidence. Keep that report separate from the platform refund request and any payment-provider dispute.
Online course refund evidence checklist
Before submitting a request, confirm that you have:
- [ ] The receipt or order confirmation
- [ ] The first statement showing the charge
- [ ] The sales page, advertisement, checkout language, and refund terms
- [ ] Screenshots or records showing access, missing content, progress, or canceled sessions
- [ ] The full support or email thread
- [ ] A dated timeline
- [ ] Cancellation and renewal records, if a subscription was involved
- [ ] A clear explanation of the remedy requested
- [ ] Proof that a credit-card dispute was sent to the correct address, if applicable
- [ ] Redacted copies that do not expose passwords or full payment details
Before you send anything, write down the purchase date, the date the first statement was sent, and the date you first requested a refund. Then use the route tied to your payment method and attach records that prove the specific shortfall.