Loan Payment Chargebacks: Winning 'I Didn't Authorize This'
A loan payment chargeback is won with proof of authorization, like signed debit terms and device data. Learn why won disputes still hurt your ratio.
Photo: Pixabay
On this page 6 sections
Key takeaways
- A promissory note shows the borrower owes you money. The issuer wants proof they authorized the specific debit in dispute.
- Records showing loan proceeds went to the borrower's own account are often your strongest answer to an identity-fraud claim.
- Charging after a borrower revokes authorization almost always loses, and each charge after revocation can become a separate dispute.
- Winning representment recovers the payment but generally leaves the dispute in your monitoring count, so prevention moves your ratio more than win rate does.
You win a loan payment chargeback coded as "I didn't authorize this" by proving the borrower agreed to the specific debit in dispute. Issuers want a signed payment authorization that covers the charge, backed by e-signature and device records that tie the agreement to the borrower. Proof that the loan proceeds landed in the borrower's own account makes the case much stronger. If the borrower revoked permission and you kept charging, you will almost always lose. Win or lose, the dispute still counts against your dispute ratio.
That last point is the one that closes lender merchant accounts. Some lenders treat representment as their whole dispute strategy. They find the gap when a monitoring notice arrives in a month when they won most of their cases.
Why Borrowers Dispute Loan Payments They Owe
Debit card repayments come out of checking accounts, and many borrowers keep those balances thin. A borrower who sees a scheduled payment about to overdraw them, or one that already did, often calls the bank. "I don't recognize this charge" is the easiest thing to say on that call, and the bank files it as unauthorized.
That one phrase can cover four different situations, and each calls for a different response:
- True fraud. Someone used a stolen or synthetic identity to take out the loan, and the real cardholder never dealt with you.
- Friendly fraud. The borrower knows about the loan, took the money, and wants this payment back.
- Confusion. The statement shows your legal entity name instead of the brand the borrower knows. Sometimes the payment posted on a date or for an amount the borrower didn't expect.
- Revocation. The borrower told you to stop debiting their card, perhaps in a chat message or through a debt settlement company, and the instruction never reached your billing system.
Federal law also gives debit cardholders protections against unauthorized electronic transfers, and issuers often grant provisional credit while they investigate. So the borrower may have the money back before you see the dispute, which makes filing feel costless to them. How those protections apply to your loan products is a legal question, so confirm it with counsel.
Reason Codes You'll See on a Loan Payment Chargeback
Visa and Mastercard sort disputes into broad families, and lenders mostly deal with three of them.
Fraud and no-authorization disputes are the core of the problem. Nearly every repayment is card-not-present, so an unauthorized loan debit dispute arrives as a card-absent fraud claim even when an agent keyed the card during a phone call.
Processing-error disputes cover duplicate debits and amounts that differ from what the borrower agreed to. They also cover charges processed later than the authorized date.
Consumer disputes include the cancelled recurring transaction. For lenders, that one matters most: the borrower says they cancelled and you charged anyway.
A reason code doesn't always tell the real story. A borrower who revoked authorization may tell the bank "I didn't authorize this," and the issuer may code it as fraud. Read the issuer's narrative and check your own account notes before you build a response. If your records show a revocation request, fraud evidence won't help you.
Response windows are short, and the networks and your processor set them. Find the deadline in your processor's dispute portal on the day the notice arrives, and confirm the exact reason code there. Each code calls for different evidence.
Lender Chargeback Evidence That Proves Authorization
Lenders often misunderstand what the issuer is deciding. Its question is narrow: did this cardholder authorize this transaction on these terms? Whether the borrower owes you money sits outside that question. A promissory note establishes the debt, but it says nothing about consent to a particular card charge. If your loan agreement doesn't name the card and the payment schedule, the issuer has nothing that connects the charge to the cardholder's permission.
Build your response from exhibits that each answer one part of the issuer's question.
| Evidence | What it proves | Where it usually lives |
|---|---|---|
| Signed payment authorization naming the card's last four digits and the payment schedule | The borrower agreed to this debit on these terms | Loan origination system |
| E-signature audit trail with timestamps and device data | The borrower, not someone else, signed | E-sign provider |
| Identity verification results at application | The applicant was the cardholder | Underwriting or KYC vendor |
| Funding record showing proceeds deposited to an account in the borrower's name | The borrower received and kept the loan money | Disbursement records |
| Prior undisputed payments on the same card, ideally from the same device | The borrower has paid this way before without complaint | Payment gateway history |
| Card enrollment records, including CVV and address verification results | The borrower added the card themselves | Gateway and borrower portal logs |
| Pre-debit notices and payment receipts | The borrower was told before and after each debit | Messaging platform |
| Borrower messages acknowledging the loan or the payment | The borrower knew about the charge | CRM, call notes, chat logs |
Against a fraud claim, the funding record does a lot of work. A borrower may say they never authorized the payment. That claim is hard to square with a deposit of the loan principal into their own checking account, followed by months of payments they never questioned.
Package the exhibits behind a short cover letter that tells the loan's story in order, starting at the application and ending with the disputed debit. Highlight where card digits and names match across exhibits. Reviewers spend little time on each case, and a dump of every log you own buries your best facts.
Keyed Phone Payments Need Their Own Paper Trail
When an agent keys a borrower's card into a virtual terminal for phone payments, you lose the device data that online enrollment gives you. Replace it with process:
- Have agents read back the amount and charge date before submitting.
- Log the agent ID on every keyed transaction.
- Send a texted or emailed receipt while the borrower is still on the line.
- Record calls where state law allows it and you have the required consent. Recording-consent rules vary by state, so check with counsel.
For online enrollment, adding 3D Secure authentication when a borrower saves a card gives you stronger evidence on fraud claims. How that authentication carries over to later scheduled debits depends on network rules and your processor's setup. Confirm the details before you rely on it.
When Revoked Authorization Means You Lose
If a borrower revoked authorization and you charged them afterward, expect to lose the dispute. An outstanding balance doesn't change that. Card network rules let cardholders cancel recurring payments, and issuers side with the cardholder when the merchant kept billing. A loan agreement clause saying revocation must be in writing is unlikely to carry much weight with an issuer, so ask counsel what your agreement can enforceably require.
Charging outside what the borrower authorized fails for the same reason. Examples include debiting the full balance after a default when the authorization covered installments, adding a late fee to a scheduled debit, retrying a declined payment more often than you disclosed, or charging a different card on file. Each is a debit the borrower never agreed to.
Federal and state law can add limits of their own. Depending on your loan products, rules may cap how often you can retry failed payments or require notice before certain withdrawals. Treat this as general information and confirm your obligations with a qualified attorney.
So the fix is operational. Treat a revocation from any channel as a revocation, and route chat, email, phone and mail requests to one queue. Scheduled debits should stop the same day. Then confirm the stop to the borrower in writing and offer other ways to pay. You can still pursue the remaining balance through lawful collection channels, but card debits the borrower has refused aren't one of them. If you also pull payments by ACH, revocation handling works the same way there. Our guide to Nacha return rate limits for lenders covers the bank-account side.
Why a Won Dispute Still Counts Against Your Ratio
Network monitoring programs generally count a dispute when it's filed, not when it's resolved. Winning representment gets your money back. It generally doesn't remove the dispute from the count your processor and the networks watch, and some programs also track issuer fraud reports that never become chargebacks. Ask your processor which measures apply to your account.
Here is an illustrative example. Every number is an assumption, not a network or MannyPay figure. Say a lender runs 5,000 debit card repayments in a month, mostly biweekly installments, and borrowers file 40 disputes. The lender wins 28 of them. Its ratio is still calculated on all 40 disputes against 5,000 transactions, because wins don't come off the count.
Now trace where those disputes came from. Five borrowers had revoked authorization, and each was charged successfully on three more biweekly dates before anyone noticed. All five disputed every one of those charges. That's 15 disputes from five people. Had those revocations been honored the same day, the month would have closed with 25 disputes instead of 40. One process fix cut the count by more than a third, with no change to underwriting.
Compare your own figures with the threshold and calculation method in your processor agreement. Some thresholds combine a ratio with a minimum dispute count, and networks revise them. Lenders already operate under close scrutiny, as our piece on why payday lenders get declined for merchant accounts explains. Get your processor's exact numbers in writing.
Preventing Disputes With Clear Descriptors and Notices
A dispute you prevent never touches your ratio. Most prevention comes down to making every debit recognizable and expected.
Match your descriptor to your brand. Borrowers should see the name they know on their statement, along with a customer service phone number. When they can't place a charge, they're likely to call the bank instead of you.
Send notices before and after every debit. A text or email a few days ahead that states the amount and the card being charged gives borrowers time to call you first. A receipt afterward becomes evidence later.
Make rescheduling easy. If a borrower can push a payment back in your portal, they have less reason to ask the bank to reverse it.
Refund clear errors yourself. If you double-charged someone or debited the wrong amount, refund it before the issuer reverses it. A refund doesn't add to your dispute count.
Use the right payment methods for the loan. Card network rules on debt repayment differ by card type. Before you take credit cards for repayments, read whether lenders can accept credit cards for loan payments. Process repayments under your own accurately coded merchant account, never through another business's account.
This week, pull the last quarter's disputes and tag each one by root cause: ignored revocation, unrecognized descriptor, amount mismatch or true fraud. Fix the biggest group first. If your current processor is threatening your account while you work on it, MannyPay sets up high-risk merchant accounts for businesses in scrutinized categories. You can request a free quote, and a MannyPay specialist will review your situation and respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
