What Discover Reason Code UA32 Means
Discover reason code UA32, titled Fraud — Card Not Present, Installment, applies when a cardholder disputes a card-not-present installment transaction as unauthorized. This covers buy-now-pay-later arrangements, installment billing plans, and recurring split-payment structures where the original transaction was CNP and the cardholder claims they did not authorize the installment agreement.
UA32 is particularly significant because if the original installment authorization is successfully disputed, all future installment charges on that agreement are also at risk. Merchants must have clear, documented authorization for the entire installment structure, not just the first payment.
When a cardholder successfully disputes the original UA32 authorization, all future installments in the same series become disputable. Cancel the installment plan immediately upon receiving UA32 to prevent additional chargebacks on subsequent installments. Then focus your representment on the original authorization.
Cross-Network Equivalent Codes
| Network | Code | Title | Notes |
|---|---|---|---|
| Discover | UA32 | Fraud – Card Not Present, Installment | This page |
| Visa | 10.4 | Other Fraud – Card Absent Environment | Visa CNP fraud code |
| Mastercard | 4853 | Cardholder Dispute | Mastercard CNP fraud code |
| Amex | F24 | No Cardmember Authorization | Amex CNP fraud code |
Common Trigger Scenarios
- Unauthorized enrollment in installment plan. A fraudster used stolen card data to enroll in an installment payment plan for high-value goods or services that is subsequently disputed by the legitimate cardholder.
- Friendly fraud on installment agreement. A cardholder who agreed to installment terms later disputes the original transaction, claiming they did not authorize the installment structure.
- Unclear installment authorization during checkout. The installment terms were not clearly disclosed during checkout, and the cardholder claims they authorized a single payment, not a recurring installment series.
- Compromised account used for installment enrollment. An account takeover was used to enroll a stored card in a new installment plan without the legitimate cardholder's knowledge.
Key Deadlines & Timeframes
| Milestone | Timeframe | Notes |
|---|---|---|
| Cardholder Filing Window | 120 days | From the transaction date |
| Merchant Response Window | 30 days | From Discover dispute notification; confirm with your processor for internal deadlines |
| Pre-Arbitration | 30 days | If Discover rejects representment, 30 days to escalate |
Evidence You Will Need
- Signed installment agreement or explicit authorization — Written documentation where the cardholder explicitly agreed to the installment structure, including number of payments, amount per payment, and total obligation
- 3D Secure authentication for original transaction — 3DS authentication record for the transaction where the installment was authorized
- Checkout flow showing installment terms disclosure — Screenshot or recording of the checkout page showing installment terms were clearly displayed and the cardholder agreed to them
- AVS and CVV match records — Authorization response confirming billing address and CVV matched at the time of installment enrollment
- Account and device data — IP address, device fingerprint, and login records showing the account holder enrolled in the installment from a recognized device
Learn Exactly How to Package and Present This Evidence
The Fraud Defense Guide covers the complete evidence format for UA32 representments, how to structure your response letter, and when a dispute is better accepted than contested given your authentication data.
Learn exactly how to package and present this evidence →How Merchants Lose This Dispute
- Unclear installment disclosure at checkout. Burying installment terms in fine print or displaying them ambiguously creates legitimate cardholder confusion and drives friendly fraud disputes.
- No explicit installment authorization record. Processing installment plans without a clear written or electronic authorization for the full series creates an undefendable dispute scenario.
- Continuing to charge installments after dispute received. Continuing to charge future installments after receiving a UA32 dispute generates additional chargebacks on each installment and compounds the financial exposure.
- No 3DS on installment enrollment. 3DS authentication on the enrollment transaction is the primary liability-shifting mechanism. Without it, the merchant bears full fraud liability for the entire installment series.
Get the Step-by-Step Winning Strategy
Our Fraud Defense Guide covers the complete UA32 representment structure and the cross-network approach for equivalent fraud codes across Visa, Mastercard, and Amex.
Get the step-by-step winning strategy →Response Framework Overview
- Cancel all future installments immediately. Stop all pending installments in the series immediately upon receiving UA32 to prevent additional chargebacks.
- Present the installment authorization record. Submit the signed agreement, checkout screenshot with terms, or explicit authorization showing the cardholder agreed to the installment structure.
- Lead with 3DS authentication if available. 3D Secure authentication from the enrollment transaction shifts liability for the entire installment series.
- Submit AVS, CVV, and device data. Show the authentication data from the enrollment transaction: address match, CVV match, device fingerprint, IP address.
Prevention Tips
- Make installment terms explicit and prominent at checkout. Display the number of payments, amount per payment, and total in a clearly visible format before the authorization step. Require affirmative acknowledgment.
- Implement 3DS on installment enrollment. 3DS authentication at enrollment provides the liability shift for the initial transaction and is strong evidence of authorization for the series.
- Use signed installment agreements. For higher-value installment plans, require the customer to sign (electronically or physically) an agreement detailing the full installment structure.
- Send confirmation emails detailing the installment structure. Immediate post-enrollment email confirmation detailing each upcoming installment creates a documented record of the authorized structure.
Frequently Asked Questions
If I win the original UA32 dispute, can the cardholder still dispute future installments?
A successful representment of the original installment authorization strengthens your position on future installments, but each installment is technically a separate transaction that can be individually disputed. Strong documentation of the original authorization is the best prevention for installment series disputes.
Should I cancel the installment plan when I receive UA32?
Yes, immediately. Continuing to charge installments after a fraud dispute generates additional chargebacks on each future installment. Cancel the series, contest the original dispute, and let the network determine liability on the original charge.
What is the difference between UA32 and UA39 (Recurring)?
UA32 is specific to installment transactions — a defined series of payments for a single purchase. UA39 covers recurring subscription transactions — ongoing charges for continuing service. The distinction matters for evidence: installment disputes require documentation of the original purchase authorization; recurring disputes require subscription agreement and cancellation evidence.