Paid for an online course and never got working access? Were you locked out after enrolling, or charged again after canceling a subscription? On a U.S. credit card, those facts may support a billing dispute. They don't guarantee a refund, though. The issuer will consider the payment method, reason for the dispute, timing, and evidence.
Two dates are easy to confuse: the purchase date and the statement date. The key federal deadline is generally 60 days after the first statement containing the error was sent, not 60 days after you bought the course. The Federal Trade Commission's guidance on credit-card billing errors says to dispute the error in writing.
Start by finding that statement and saving a copy. Then preserve the course offer, access records, cancellation records, and your messages to the seller. Don't wait for a support thread to run past the deadline.
An issuer may call its process a billing dispute. The seller or payment processor may call the resulting reversal a chargeback. The terms refer to related parts of the process, but a chargeback isn't an automatic refund for a course you didn't finish or didn't like.
The evidence that makes a dispute understandable
Build the file around four questions:
- What did the seller promise?
- What did you pay for?
- What happened after payment?
- What did you do to fix the problem?
A short, dated packet is more useful than a folder full of unlabeled screenshots.
| Record | What it should show |
|---|---|
| Statement and receipt | Transaction date, amount, merchant descriptor, currency, and order or invoice number |
| Sales page and checkout terms | Course description, syllabus, access period, delivery promise, subscription terms, and refund terms shown before purchase |
| Enrollment and access records | Confirmation email, welcome message, login instructions, activation notice, error messages, disabled lessons, missing modules, or account lockouts |
| Cancellation records | Cancellation date, confirmation email or account screen, the billing-cycle terms, and statements showing later charges |
| Misrepresentation evidence | The specific advertisement or checkout promise and a clear comparison with the feature, module, or service that was actually missing |
| Seller communications | Refund requests, support tickets, chat transcripts, the seller's response, or evidence that it did not respond |
| Unauthorized-transaction records | Account alerts and the date you notified the issuer. Use this category only when you truly didn't authorize the purchase |
| Refund records | Any merchant credit or refund confirmation, so the issuer can avoid giving credit twice |
Put dates next to access attempts and support messages. A screenshot showing that an account existed is not necessarily proof that the promised course was available or usable.
Redact your full card number, passwords, security codes, and unrelated personal information. The issuer needs enough information to identify the transaction, not your complete payment credentials.
Which course problems may support a dispute?
The applicable reason can depend on the issuer and card-network process. The distinction is usually between a specific failure and ordinary buyer's remorse.
| Problem | Evidence to emphasize | Limit |
|---|---|---|
| You never received the promised access | Receipt, missing enrollment email, failed login records, and unanswered support requests | A seller's confirmation alone may not prove that usable access was provided |
| Your account was blocked or important content was unavailable | Error messages, screenshots, dates of failed access, and support replies | Say whether the problem affected the whole course or only one feature |
| You canceled a recurring plan but were charged again | Cancellation confirmation, cancellation date, billing-cycle terms, and the later statement | The seller's processing terms and the timing of cancellation matter |
| The course materially differed from its offer | Saved sales copy, checkout terms, syllabus, and a specific comparison with what was delivered | Low completion, nonuse, disappointment, or a change of mind usually doesn't establish non-delivery |
| You didn't authorize the transaction | Account alerts, the issuer's fraud report, and relevant account-security information | Don't describe a purchase you made as fraud just because you regret it |
| You simply didn't use or finish the course | Purchase record and the refund policy | Nonuse by itself generally doesn't show that the seller failed to provide the service |
A "no refunds" term may make a voluntary refund request more difficult, but it doesn't answer every billing question. It doesn't turn an authorized purchase into an unauthorized one, and it doesn't by itself settle whether the promised access or service was provided. At the same time, a dispute shouldn't be used to bypass a valid cancellation requirement when the course was delivered as promised.
Nothing in an evidence packet guarantees a result. Payment method, dispute reason, documentation, issuer review, and the seller's response can all affect the outcome.
The U.S. credit-card deadline
For a U.S. credit-card billing error, the FTC says you must dispute the charge in writing within 60 days after the first statement with the error was sent. Write down the statement date and keep proof that the dispute was submitted.
The FTC also says that:
- The issuer must acknowledge the dispute in writing within 30 days, unless it has already resolved the problem.
- The issuer must resolve the dispute within two billing cycles, but no later than 90 days after receiving your letter.
- During the investigation, you don't have to pay the disputed amount or related finance and other charges. Continue paying amounts that aren't part of the dispute and follow the issuer's instructions.
These protections concern credit-card billing errors. They aren't a universal deadline or procedure for debit cards, prepaid cards, bank transfers, buy now, pay later accounts, or digital wallets. If you used another payment method, contact that provider promptly and check its dispute process.
The deadline also isn't a reason to wait indefinitely for the seller. Ask for a refund when practical, but contact the issuer before the applicable deadline expires if the problem remains unresolved.
A practical submission sequence
1. Confirm the payment method and statement date
Check where the charge appeared. A credit-card statement is treated differently from a debit-card account, bank transfer, or wallet balance. Note the transaction date and amount, then identify the first statement that showed the disputed charge and its sent date.
2. Ask the seller for a specific remedy
Describe the problem in plain terms. You might say that access was never activated, that a cancellation was completed before the later recurring charge, or that a promised module was missing.
Ask for the remedy you want: access, cancellation, or a refund. Keep the request factual and save the reply. A seller's written response can clarify what happened, but it shouldn't delay an issuer dispute beyond the 60-day period.
3. Make a one-page timeline
Put the events in order:
- Purchase date and amount
- Date access was promised or activated
- Date the problem appeared
- Dates you contacted the seller
- Cancellation date, if relevant
- Seller's response or failure to respond
- Date the charge appeared on the statement
Match each event with its supporting record. This gives the issuer a way to follow the dispute without guessing which screenshot matters.
4. Send the written dispute to the issuer
Follow the billing-dispute instructions on your statement, card, or issuer's website. State the transaction details, the date the first statement with the error was sent, the exact problem, and the steps you took with the seller. Attach copies of relevant records, keep the originals, and save proof of submission.
A focused explanation could read:
I dispute the $[amount] charge from [merchant] dated [transaction date]. The first statement showing this charge was sent on [statement date]. I paid for [course or subscription], but [specific problem]. I contacted the seller on [dates] and requested [refund, access, or cancellation]. Attached are the receipt, advertised terms, access or cancellation records, and our correspondence. Please investigate this billing error and tell me if additional information is required.
Use a secure issuer channel. Don't put your full card number in an ordinary email or attachment unless the issuer specifically requests it through a secure process.
5. Track the investigation
Keep the case number, submission date, uploaded files, letters, and follow-up questions together. Respond by the deadline in the issuer's notice.
If the issuer denies the dispute, ask for the reason and whether it accepts additional evidence or a reconsideration request. Address the missing point rather than sending the same disorganized file again. For example, if the issuer says the course was delivered, show the specific access failure or mismatch. If it says the recurring charge was authorized, provide the cancellation date and confirmation.
Why the FTC shipping rule usually isn't the answer
The FTC's business guide to the Mail, Internet, or Telephone Order Merchandise Rule focuses on shipment representations for merchandise and refunds required when an order can't be shipped as promised.
It isn't a blanket rule guaranteeing a refund for every digital-course complaint. A course usually raises a different factual question: whether the promised access or service was made available, whether it worked for the promised period, and whether it matched the offer. The seller's terms, payment processor's rules, and issuer's investigation may all matter.
A login being created is relevant, but it doesn't automatically prove that the service was fully delivered. The access records should show what you could actually use and when.
Mistakes that can weaken the file
- Waiting too long for the seller: Support conversations can use up the 60-day credit-card period.
- Using the wrong dispute reason: A purchase you authorized but regretted isn't the same as an unauthorized transaction.
- Describing only disappointment: Identify the missing access, feature, module, or term and attach the promise that was made.
- Ignoring partial access: If you used part of the course, acknowledge that and identify the exact service that was unavailable or materially different.
- Disputing more than necessary: If only one recurring installment or one specific service is at issue, say so clearly.
- Relying on the no-refund term alone: It may affect a voluntary refund request, but it doesn't settle every billing-error issue.
- Keeping the refund and the chargeback quiet: Tell the issuer if the seller credits you so the account isn't credited twice.
- Sending sensitive information: Course passwords, security codes, and full card details don't belong in an ordinary evidence packet.
If the issuer denies the dispute
Read the denial and compare it with your timeline. Ask which evidence was insufficient, whether the issuer treated the matter as non-delivery, cancellation, misrepresentation, or an authorized purchase, and whether there is a deadline for a focused response.
If the problem was an unauthorized charge, secure the course account and contact the issuer's fraud department separately. If the seller later issues a refund, keep the confirmation and notify the issuer.
If the 60-day period is close to expiring, submit the written dispute now using the issuer's stated procedure and continue the seller conversation in parallel.