iPhone in-depth Lesson 4: Chargebacks & Refunds [Springfield Scammin’ Series]

[GarySpringfieldScammin’]

Lesson 4: Chargebacks & Refunds
Part 1 of 2 — continued in the first reply below.

Lesson 4: Chargebacks & Refunds​

Introduction​

In the previous lesson a $91.92 purchase travelled from a tap or click through authorisation, clearing, and settlement. That feels like the end. It is not.

A payment can be unwound after settlement, weeks or months later, by a refund, a reversal, or a chargeback. They look similar outside and work very differently inside. This lesson continues the same $91.92 purchase after settlement, tracing each unwind path, the six chargeback stages, the five reason-code categories, and the different rights for credit and debit cards. Claims are tagged Verified, Inferred, Hypothetical, or Unknown where that matters. This is general educational information, not legal advice.

Architecture: Three Ways to Unwind a Payment​

Feature	Refund	Reversal	Chargeback
Started by	Merchant	Merchant or issuer	Cardholder, via issuer
Timing	After settlement	Before settlement	After settlement
Merchant fee	No dispute fee	No dispute fee	Typically $15 to $100
Merchant contest	Merchant decides	Limited	Yes, by representment

A refund is the cleanest unwind. Verified in outline: the merchant issues it through its acquirer, the network routes it to the issuer, and the issuer credits the cardholder. A reversal voids a duplicate, error, or cancellation before settlement; reversals are Inferred to be the cheapest unwind, because no dispute opens and no fee applies. A chargeback is the adversarial unwind: the cardholder asks the issuer to take the money back, and the merchant fights back through representment, where evidence decides it.

The Six Stages of a Chargeback​

1. Dispute. The cardholder contacts the issuer with a reason: fraud, goods not received, goods not as described, duplicate charge, cancelled subscription, or credit never received.
2. Provisional credit. The issuer usually gives a temporary credit while investigating. It is conditional and can be taken away if the merchant wins.
3. Pullback. The issuer sends the chargeback through the network; the acquirer debits the merchant $91.92 plus a fee, typically $15 to $100.
4. Representment. The merchant accepts or fights with evidence: delivery proof, signed receipt, photograph, tracking, accepted terms, or proof a refund was issued.
5. Decision. The issuer or network reviews the evidence. If the merchant wins, the provisional credit is reversed. If the cardholder wins, it becomes permanent.
6. Arbitration. If the merchant disagrees and the amount justifies it, the case can go to network arbitration. The loser pays a fee, so small disputes rarely reach this stage.

No fraud vendor, device fingerprint, or risk score decides the case alone. A chargeback is decided on the reason code and the evidence each side produces. That is Verified in the network rules for representment: evidence wins, not reputation.

Trust Boundary: Who Decides, and What Do They Trust?​

First, the issuer trusts the cardholder account enough to open the case and issue a provisional credit, without verifying the claim first. That is by design: a system demanding proof before opening a case would leave genuine fraud victims waiting while a thief spent their money.

Second, the network trusts the reason code. It is not a free-text complaint, but a category with a defined meaning, burden of proof, and evidence that can defeat it. The wrong reason code can lose a winnable case.

Third, merchant evidence at representment only counts if it matches the reason code. Proof of delivery defeats a not-received claim. It does not defeat a claim that goods were counterfeit, damaged, or not as described.

The chargeback is not a refund with a different name. It is a separate adjudication system, with its own categories, evidence rules, and costs.

Weakness: Who Bears the Loss?​

By default, in online card-not-present fraud, the merchant bears the loss. Verified as the default allocation: the merchant loses the merchandise and the sale, keeps the processing fees already paid, and pays a chargeback fee, typically $15 to $100. One $91.92 fraud chargeback can therefore cost the merchant well over $91.92. The issuer bears the loss only after a liability shift, and both shifts are narrow.

• EMV chip in-store. Since the October 2015 shift, a merchant that swipes a chip card instead of dipping it bears counterfeit fraud; one that uses the chip correctly does not. Chip counterfeit-fraud losses fell by roughly 87 percent afterwards, which is Verified in network reporting.
• Successful 3-D Secure online. If an online transaction passes 3-D Secure, liability for fraud reason codes shifts from merchant to issuer, for fraud codes only.

What does not shift liability? Address Verification Service (AVS) and the card security code (CVV) do not. They are useful signals, but neither moves legal liability. AVS and CVV are evidence, not a liability shift.

The consumer is heavily protected. For credit cards, liability is $0 in practice under network zero-liability policies, with a $50 statutory cap under 15 U.S.C. section 1643. That is Verified. The weakness is structural: a merchant selling digital goods, or goods hard to prove delivered, is disadvantaged in representment, and a false dispute, known as friendly fraud, costs the merchant money even when the merchant wins.

The Five Reason-Code Categories​

The category decides what evidence matters.

Category	Cardholder claims	Helps cardholder	Helps merchant
Fraud: unauthorised	I did not authorise this	Statement; card still held	3-D Secure proof
Goods not received	I paid but received nothing	Order confirmation	Tracking; signed delivery
Not as described, defective, counterfeit	Item was wrong or damaged	Photographs of item	Accurate listing
Duplicate, wrong amount, cancelled recurring	Charged twice or after cancellation	Both charges; cancellation date	Proof one charge settled
Credit not processed	Refund promised, never issued	Written refund promise	Proof refund issued

Credit vs. Debit: The Same Dispute, Different Rights​

Feature	Credit: Regulation Z / FCBA	Debit: Regulation E
Rule	FCBA, Regulation Z, 12 CFR 1026.13	EFTA, Regulation E, 12 CFR 1005.11
Money at risk	Issuer money	Cardholder money, already gone
Deadline	Acknowledge in 30 days; resolve in two billing cycles, max 90 days	10 business days; extend to 45 days only if credited within 10 days
Provisional credit	Typically issued; consumer need not pay disputed portion	Required within 10 business days if extended to 45 days
Collecting disputed amount	Cannot collect or report it	No equivalent ban
Liability, unauthorised use	$0 in practice; $50 cap, 15 U.S.C. section 1643	$50 within 2 days, up to $500 within 60 days, potentially unlimited after 60 days
Final?	No; reversible if merchant wins	No; reversible if merchant wins

With a credit card, a disputed $91.92 is issuer money while the case runs: the cardholder does not pay it, and the issuer cannot collect or report it. With a debit card, the $91.92 has already left the account, so the cardholder feels the loss at once.

The debit deadlines are therefore the protection. Verified under Regulation E, 12 CFR 1005.11: the bank has 10 business days to investigate, and can extend to 45 days only if it provisionally credits within those 10 days; the outer limit is 90 days for point-of-sale, foreign, or new-account cases. Report within 2 business days and liability is capped at $50; within 60 days, up to $500; after 60 days, potentially unlimited.

The credit deadlines are Verified under the FCBA and Regulation Z, 12 CFR 1026.13: acknowledge within 30 days, resolve within two billing cycles, maximum 90 days, and do not collect or report the disputed amount meanwhile. If the merchant wins, the provisional credit is reversed.
Continued in the first reply below — Part 2 of 2.

 

[GarySpringfieldScammin’]

Part 2 of 2 — continued from the thread above.

Demonstration: Tracing the $91.92 Chargeback​

The buyer files a not-received dispute. The issuer issues a provisional credit of $91.92, then sends the chargeback through the network. The acquirer debits the merchant $91.92 plus a fee, typically $15 to $100. The merchant has a negative sale, a fee, and no goods, because the buyer kept them.

The merchant submits tracking and a delivery photograph showing delivery to the buyer address. That defeats a not-received claim: the provisional credit is reversed, the buyer is charged $91.92 again, and the merchant keeps the sale but also keeps the fee, which is charged for the process, not for losing.

Change one fact: tracking shows delivery to a different city, and the cardholder wins. Change another: the claim is fraud with a successful 3-D Secure record, so liability shifts to the issuer. The chargeback asks a narrow question, on specific evidence, with a deadline.

Evidence: Friendly Fraud and What Counts​

Friendly fraud is a dispute by the genuine cardholder for a transaction the cardholder did authorise, or goods the cardholder did receive: a forgotten purchase, an unrecognised merchant name, or a refund sought without returning the goods. It is called friendly because the fraud is by the cardholder, not a stranger who stole the card.

It is difficult to prove and count precisely, so any single percentage is Inferred at best. What is Verified is the mechanism: friendly fraud costs the merchant the sale, the goods, and a fee, even when the merchant wins, and costs the cardholder nothing to file.

Evidence is the only defence that scales, and it must be contemporaneous and specific. For a merchant: tracking tied to this order, a signature or photograph tied to this delivery, and terms accepted at checkout. For a cardholder: order confirmation, photographs of what arrived, dates of every contact, and any refund promise. The issuer never saw the transaction happen; it sees only the documents each side submits.

What Apple Pay Changes, and What It Does Not​

Apple Pay changes the authorisation, not the dispute system. What it changes: the merchant receives a Device Account Number, a token, instead of the real card number, plus a dynamic cryptogram from the Secure Element, and the cardholder authenticates with Face ID, Touch ID, or a passcode. Tokenisation makes the card number harder to steal, and a stolen token far less useful, because it is tied to the device and the cryptogram changes each time.

What it does not change: the chargeback itself. A dispute on an Apple Pay transaction follows the same six stages, reason codes, and credit versus debit rules. Apple is not a party to the chargeback and does not decide who wins. The token does not defeat a not-received claim or prove the goods were as described.

One narrower effect is Inferred, not Verified: a merchant presenting the Apple Pay authentication record may have stronger fraud representment evidence than one that accepted a typed card number. It is not a liability shift.

Defense: The Six-Step Dispute Checklist​

Use this for your own dispute, on your own accounts, with your own records. Do not file a dispute for someone else, or one you know is false.

Step 1: Identify the charge: merchant name, date, amount, last four digits.
Step 2: Contact the merchant first, in writing. Keep the reply. A refund is faster than a chargeback.
Step 3: Gather evidence first: confirmation, tracking, photographs, messages, cancellation proof, refund promise.
Step 4: File with the issuer in writing if possible. State facts plainly. Let the issuer assign the reason code. Ask for the case number and deadline.
Step 5: Check the provisional credit and deadlines. Credit: confirm you need not pay the disputed portion. Debit: confirm the credit date.
Step 6: Keep everything until the case closes. If the merchant wins, the provisional credit will be reversed.

Hands-On Experiment: Audit Your Own Dispute Trail​

Use only your own devices and accounts. Do not file a test dispute.

1. Pick one past purchase with an emailed receipt. Find the order confirmation, the statement charge, and the delivery record. Is the statement merchant name the same as the store name you remember?
2. Check whether you used credit or debit, and which rights would have applied: the Regulation Z timeline, or the Regulation E timeline.
3. Reconstruct the evidence you would have had if the goods never arrived: tracking, delivery photograph, messages, refund promise. Grade it: strong, partial, or missing.
4. Write two sentences: which card type you used, and whether your evidence would have won a not-received dispute.

Decision Lab: Six Scenarios​

Work each scenario before opening the spoiler.

Scenario 1: The Parcel That Never Arrived​

You order a $91.92 item with a credit card. The merchant shows tracking and a photograph of delivery to your address. You dispute, saying the goods were not received.

Spoiler: Answer

Category: goods not received. Merchant evidence is stronger. Tracking plus a delivery photograph to your address defeats a not-received claim. Expect the merchant to win representment and the provisional credit to be reversed.

Scenario 2: The Subscription That Kept Billing​

You cancel a monthly subscription in writing and receive a confirmation email with a date. The merchant charges you again the next month. You dispute.

Spoiler: Answer

Category: cancelled recurring charge. Your evidence is stronger. The dated cancellation confirmation plus a charge after that date is exactly what this category requires.

Scenario 3: The Card You Never Lost, Used in Another City​

A $91.92 charge appears from a store in a city you have never visited. You still have the card. You file a fraud dispute. The merchant shows a typed card number online, no 3-D Secure, no AVS match.

Spoiler: Answer

Category: fraud, unauthorised. Expect to win, and the merchant to bear the loss. No liability shift occurred: AVS and CVV do not shift liability, and 3-D Secure was not used. Your liability is $0 in practice, with a $50 statutory cap.

Scenario 4: The Same Fraud, But With 3-D Secure​

Same facts as Scenario 3, except the merchant shows a successful 3-D Secure authentication, with a record that the cardholder completed the issuer authentication step.

Spoiler: Answer

Category: fraud, unauthorised, but who pays changes. Successful 3-D Secure shifts liability for fraud codes from merchant to issuer. You still win. The issuer, not the merchant, bears the $91.92 loss.

Scenario 5: The Debit Card Dispute, Reported Late​

You notice an unauthorised $91.92 debit charge but do not report it for 70 days. The bank confirms it was unauthorised. What is your liability?

Spoiler: Answer

Category: fraud under Regulation E, but the debit tiers apply. Within 2 business days, liability is capped at $50. Within 60 days, up to $500. After 60 days, potentially unlimited for later transactions. Debit reporting speed directly controls the cap.

Scenario 6: The Item That Arrived Damaged​

You order an item described as new. It arrives scratched with a cracked case. You photograph it on arrival, contact the merchant, and the merchant refuses a refund. You dispute.

Spoiler: Answer

Category: goods not as described or defective. Your evidence is stronger if photographs are dated, show the damage, and the listing described the item as new without disclosing damage. Expect a genuine contest.

Discussion Prompts​

• Why does the system make the merchant bear online fraud by default? Who can best prevent fraud at the point of sale?
• A provisional credit feels like a refund, but it is reversible. How should a cardholder plan spending during a dispute?
• Friendly fraud costs the merchant even when the merchant wins. What rule change would reduce it without making genuine disputes harder?
• Debit and credit cards look identical at checkout. Should they carry the same dispute rights?
• Apple Pay gives the merchant a token and cryptogram, not the real card number. Does that change fraud dispute evidence enough to matter?

---

Next Lesson​

Next lesson: Lesson 5: Apple Account & iCloud Identity.