Consumer complaint received 2026-05-25 00:00:00
Product: Vehicle loan or lease — Loan
Issue: Problem with a company's investigation into an existing problem — Their investigation did not fix an error on your report
Company: CREDIT ACCEPTANCE CORPORATION
State: NC

Complaint narrative:
IMPORTANT NOTE REGARDING CONTACT INFORMATION The phone number currently listed on this CFPB account XXXX is no longer active. My current contact number is XXXX. I attempted to update this number by calling CFPB the day after submitting Complaint XXXX and was told by a representative that it had been updated, however the portal still reflects the old number. Please use XXXX for all correspondence related to this and all prior complaints. Additionally this inactive number XXXX is the same number listed on my Identity Theft Victim Fraud Alert since XX/XX/XXXX, and is the same number Credit Acceptance Corporation claims the electronic signing PIN was delivered to on XX/XX/XXXX when the number was already experiencing documented service instability as evidenced by phone service records submitted with Complaint XXXX. This directly contradicts XXXX 's claim that electronic identity verification was successfully completed. REFERENCE TO PRIOR COMPLAINT This complaint references and supplements closed CFPB Complaint Number XXXX regarding Credit Acceptance Corporation Account XXXX . Since the closure of that complaint the following new violations have occurred and new evidence has been identified. NEW VIOLATION ONE COORDINATED RETALIATORY REPOSSESSION TIED TO NC AG DEADLINE The NC Attorney General Consumer Protection Division issued a formal complaint letter to XXXX XXXX XXXX on XX/XX/XXXX under Case Number XXXX, giving XXXX XXXX 15 days to respond regarding the fraudulent origination of this transaction. That response deadline was XX/XX/XXXX. XXXX initiated repossession proceedings on XX/XX/XXXX charging a {$410.00} repossession cost to the account three days before the AG deadline while that complaint was active. The physical repossession was complete and visible in the XXXX account system by the morning of XX/XX/XXXX the exact same date XXXX XXXX XXXX 's NC AG response deadline. This is documented by two independent timestamped XXXX communications sent on Tuesday XX/XX/XXXX : at XXXX XXXX to one contact stating 'The repossessed that car ' and at XXXX XXXX to a second contact stating 'They repossessed XXXX car apparently. After I made a complaint to the Attorney General. ' These contemporaneous third-party messages are independently timestamped by XXXX XXXX and establish both the repossession date and my real-time recognition of the connection between the AG complaint and the repossession made before any legal strategy was developed. XXXX subsequently issued a Notice of Plan to Sell Property dated XX/XX/XXXX announcing a private sale after XX/XX/XXXX. The complete sequence repossession initiated XX/XX/XXXX, completed XX/XX/XXXX on the exact AG deadline date, sale notice issued XX/XX/XXXX, planned sale after XX/XX/XXXX raises serious concerns that XXXX and XXXX XXXX coordinated the repossession and planned sale to dispose of the vehicle before the NC AG investigation could result in adverse findings or a governmental hold. Credit Acceptance Corporation maintains an active dealer agreement with XXXX XXXX XXXX as documented in the assignment section of the retail installment contract. This potential coordination between parties with a documented contractual business relationship to defeat an active state government consumer protection investigation may constitute a violation of FDCPA Section 1692f prohibiting unfair or unconscionable means to collect a debt, and may also constitute interference with a state consumer protection investigation under NC General Statute 75-1.1. I am requesting the CFPB investigate whether XXXX and XXXX XXXX communicated regarding the NC AG complaint timeline and whether the repossession initiation on XX/XX/XXXX and completion on XX/XX/XXXX were deliberately coordinated with the AG deadline. NEW VIOLATION TWO LEGAL NOTICE ADDRESSED TO WRONG LEGAL NAME On XX/XX/XXXX Credit Acceptance Corporation issued a Notice of Plan to Sell Property addressed to XXXX XXXX XXXX. My legal name is XXXX XXXX XXXX. The name XXXX XXXX XXXX does not match any government-issued identification I hold. XXXX has been on notice of this name discrepancy since my original CFPB complaint yet continues to use the fraudulent name variant in official legal correspondence including notices with legal consequences. NEW VIOLATION THREE FAILURE TO PRODUCE REQUESTED DOCUMENTATION XXXX has not provided any of the eight items of documentation specifically requested in my XX/XX/XXXX rebuttal, which is part of the official record of Complaint XXXX. Those eight items were : the electronic signing audit trail, PIN verification records, IP and device logs, call records, full payment history, itemized fees, complete account ledger including accounting for the {$4000.00} down payment, and explanation of the {$1600.00} interest charge. NEW VIOLATION FOUR CONFLATION OF FCRA AND FDCPA STANDARDS XXXX XXXX XX/XX/XXXX response conflated FCRA credit reporting accuracy standards with FDCPA debt validity requirements. The accuracy of credit reporting does not establish the legitimacy of the underlying debt. XXXX answered my FDCPA debt validity challenge with an FCRA reporting accuracy argument. These are governed by two separate federal statutes and XXXX has never addressed the FDCPA validity challenge. A debt being accurately reported does not mean the debt is valid. NEW VIOLATION FIVE PREDATORY INTEREST CALCULATION I am submitting the complete XXXX transaction history as evidence of predatory interest calculation practices inconsistent with the simple interest terms disclosed in the retail installment contract. The account balance increased by {$1300.00} after 28 months of payments. A single interest charge of {$1600.00} was assessed on XX/XX/XXXX representing approximately six to seven months of simple interest applied at one time. A systematic pattern of payment reversals repeating at least six times between XXXX and XX/XX/XXXX reset interest calculations at higher amounts each cycle preventing any principal reduction. These practices are inconsistent with the disclosed contract terms and represent p otential violations of TILA 15 USC 1638 and Regulation Z 12 CFR 1026.18. NEW VIOLATION SIX FABRICATED PROMISE TO PAY RECORD Following the repossession of the vehicle I contacted Credit Acceptance Corporation to inquire about the condition of the repossessed vehicle and to formally request that the vehicle not be released back to the primary buyer XXXX XXXX XXXX XXXX, who exclusively possessed and used this vehicle throughout the life of the account. A XXXX representative confirmed the vehicle had minor front damage and was driveable. I did not offer, agree to, or promise any payment during that call. I called solely to inquire about the vehicle 's condition and to protect my interests as a named party regarding the disposition of the collateral. The {$800.00} release amount quoted to me during the call was information provided by XXXX not a commitment made by me. XXXX has recorded a promise to pay on my account from that call without my authorization. This is documented in my text message conversations where I described calling to find out the state of the vehicle not to arrange payment. Under FDCPA Section 1692e a debt collector may not use any false, deceptive, or misleading representation in connection with the collection of a debt. Under FDCPA Section 1692f a debt collector may not use unfair or unconscionable means to collect a debt. Creating a promise to pay record from an inquiry call where no such promise was made constitutes both a false representation and an unfair collection practice. I am requesting the CFPB direct XXXX to produce the complete call recording and all account notes from this call and to immediately remove the fabricated promise to pay record from my account. NEW VIOLATION SEVEN FCRA SECTION 623 FAILURE TO NOTE DISPUTED STATUS On XX/XX/XXXX Credit Acceptance Corporation reported the repossession status to XXXX. At the time of that reporting XXXX had an active CFPB complaint on file under Case Number XXXX and had received formal dispute correspondence from me. Under FCRA Section 623 ( a ) ( 3 ) a furnisher who receives notice of a dispute must note the account as disputed when reporting to the credit bureaus. XXXX reported the repossession status on XX/XX/XXXX without noting the account as disputed. My current XXXX credit report shows the XXXX account status as Repossession with no disputed notation visible. This is a standalone FCRA violation separate from all other violations documented in this complaint. CONCURRENT ACTIONS TAKEN I have taken the following concurrent actions which are relevant to this complaint : 1. Formal Regulation Z rescission notice sent to XXXX XXXX XXXX as the original creditor pursuant to TILA 15 USC 1635, citing the failure to provide the required Appendix H8 rescission disclosure and the extended three-year rescission window. Copy sent to XXXX. 2. Formal FDCPA debt validation demand sent to Credit Acceptance Corporation under 15 USC 1692g and Regulation F Appendix B1 demanding cessation of all collection activity including the planned vehicle sale during the validation period. 3. FCRA dispute letters sent to all three credit bureaus XXXX, XXXX, and XXXX disputing the XXXX account as inaccurate and unverifiable on six documented grounds. 4. Updated complaint filed with NC Attorney General Case XXXX notifying them that XXXX initiated repossession proceedings on XX/XX/XXXX and completed the repossession on XX/XX/XXXX the exact date XXXX XXXX XXXX XXXX XXXX response deadline as documented by timestamped XXXX communications at XXXX XXXX and XXXX XXXX on XX/XX/XXXX, and requesting the AG investigate whether XXXX and XXXX XXXX coordinated the repossession timing to defeat the state investigation.

Company public response: Company has responded to the consumer and the CFPB and chooses not to provide a public response
Company response to consumer: Closed with explanation