Visa 13.1 — Merchandise/Services Not Received
A student charged back after finishing the course
By Byron Kiriibwa · Updated
When a student finishes a course and then charges back, the dispute usually says they didn't get what they paid for, or that it wasn't as described. The bank decides on your records: that access was set up for their account, that they used it, and what the sales page promised when they bought.
The bank's test
The bank checks:
- Proof the cardholder received it: delivery to their full address, access granted to them and used, or the service performed.
- That delivery happened by the date promised at checkout.
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Product or service as described at sale | What the customer was told they were buying, showing what was promised and when. | A capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description. | Stripe: Product description or Uncategorized fileSquare: Product or service description | Every seller |
| Messages with the customer | Showing the customer acknowledged receipt or asked how to use it. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
| Receipt or invoice | What was bought, the amount, and the date. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Access granted or digital product delivered | The customer was given what they bought — an account, a login, a download link, a license key. | The delivery or welcome email, or the platform record showing when access was granted and to which email. | Stripe: Access activity log or Customer communicationSquare: Online or app access log | Courses, memberships, digital products |
| Access and usage log | Showing when the customer accessed or used what they bought, with dates. | Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export. | Stripe: Access activity logSquare: Online or app access log | Courses, memberships, digital products |
What doesn't help
- Tracking that shows only "label created" or "shipped".
- Tracking that shows only a city or postcode. Visa doesn't accept proof of delivery without the full delivery address.
- Delivery to an address different from the one on the order.
- A link to a tracking page. Banks don't open links; attach the record.
- Access records without dates, or not tied to the customer's account.
Visa's rules for 13.1
- Covers goods, services, and digital products. Show delivery on or before the date promised at checkout. If the order was delayed, show what the customer was told.
- Visa: 13.1 covers goods or services the cardholder didn't receive because the seller was unwilling or unable to provide them. It doesn't apply when the cardholder cancelled before the expected delivery or service date (that is 13.7), to a complaint about quality (13.3), to a payment the cardholder says was fraud, or to goods held by customs in the cardholder's own country. Source: Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.11.2; read 2026-10-29.
- Visa's accepted responses: the cardholder or someone they authorized received the goods or services at the agreed place or by the agreed date; for delivered goods, proof of delivery with the full delivery address (Visa doesn't accept tracking with a partial address); for an online order collected in person, a collection record with the cardholder's acknowledgement (signature, PIN, or collection code); for future services, that the seller didn't cancel and the service is available; a credit or reversal the issuer didn't take into account; the dispute is invalid; the cardholder no longer disputes it.
- The cardholder doesn't have to accept a different date, time, or replacement. If the seller offered one, show whether the cardholder accepted it. Source: Visa Dispute Management Guide for Merchants (October 2026), Condition 13.1.
- From October 2026, when the claim is that it didn't arrive at the agreed place, the issuer must give the full agreed address (street, city, state, postcode, country). Compare it with the address on the delivery proof. Source: Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.11.2.5; read 2026-10-29.
Common mistakes with Visa 13.1, Visa 13.3
- Not addressing a missed delivery date, or what the customer was told about a delay.
- Describing digital delivery in technical terms the bank's reviewer won't follow; say in plain words what the customer got and when.
Should you fight it?
Fight it when your records show the student's own account was given access and worked through the course, and the course matched what the sales page promised. Accept it when any of these is true:
- Tracking shows not delivered, returned to sender, or delivered to a different address.
- Digital access was never set up.
- The service didn't happen, or the promised date passed with no delivery.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Ship with tracking, and with signature on delivery for high-value orders.
- Send an access or delivery email the moment a digital product is available, and log logins and downloads.
- For services, send a written confirmation when the work is delivered or the session happens.
- State delivery timelines at checkout and tell customers about delays in writing.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
A student buys a $497 course on May 2. Your course platform shows they logged in 31 times and completed 9 of 10 modules by June 10. On June 14 they file a dispute saying they never received the course.
The response would attach:
- Exhibit A: the order receipt, with the course name, price and date.
- Exhibit B: the access record showing their account was set up on May 2, at the email they bought with.
- Exhibit C: the progress log: 31 logins and 9 of 10 modules completed, each with a date.
- Exhibit D: the sales page as it read on May 2, showing what the course includes.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Visa reason code 13.1, for $497.00 charged on May 2 for an online course. The customer received the course and used it.
The customer was given access to the course. Their account was created on May 2 at the email address used for the purchase, with full access to all ten modules (Exhibits A and B).
The customer used the course after buying it. Our platform recorded 31 logins between May 2 and June 10, and 9 of the 10 modules completed, each with its date (Exhibit C). The customer received what they paid for.
The course delivered what was described at the time of sale. The sales page on May 2 listed ten modules, and all ten were available to the customer (Exhibit D).
The customer received the course, used most of it, and got what was described. We ask that the dispute be decided in our favor.
Questions people ask
Can a student really charge back after finishing a course?
Yes. Their bank lets them dispute it, usually saying they didn't receive it or it wasn't as described. Your progress records are what answer that.
Is a no-refunds policy enough to win?
Not on its own. The bank looks first at whether the student got access and used it, and whether the course matched the sales page. A policy helps alongside those records.
What if the student only watched a few lessons?
Access set up for their account still shows delivery, but light use is weaker evidence. If the course didn't match what was promised, refunding may be the better choice.
Should we take screenshots of their progress?
Export the platform's dated progress or activity report for their account. Banks don't open links, so attach the record itself.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.