Auto lending is one of the DOJ’s most active SCRA enforcement targets, and the violations almost always come down to one missing step: nobody checked military status before ordering the repossession. Santander paid $9.35 million for 760 illegal repossessions. CarMax paid $420,000 plus a civil penalty for 28. The fix costs one database lookup.
This is the operational workflow recovery and collections teams need — where the check belongs in your process, how to interpret the result, and what to keep on file.
The rule: §3952 in plain terms
Under 50 U.S.C. §3952, a creditor may not repossess a vehicle (or other property under an installment contract) during a servicemember’s military service — or enforce the contract — without a court order, if two conditions are met:
- The contract was entered into before the servicemember’s active-duty service began, and
- The servicemember made at least one payment before active-duty service began.
If both are true, the account is protected. Self-help repossession is prohibited; you need a court order, and the court may stay the proceeding or adjust the obligation. Get this wrong and the exposure is not theoretical — wrongful repossession is the single most expensive SCRA fact pattern in auto.
Where the check belongs in your process
The most common failure is checking too late — or not at all — because the repossession order is triggered automatically by delinquency. Build the check in as a hard gate:
No repossession order may be issued until military status has been verified for the relevant dates.
Place the DMDC check at the moment an account becomes repo-eligible, and re-verify immediately before the order goes to the agent or forwarder. Active-duty status can change; a check from 60 days ago is not enough.
The step-by-step workflow
- Trigger. Account hits repo-eligible status (delinquency threshold met, internal approvals cleared).
- Verify military status (DMDC). Screen the borrower against the Defense Manpower Data Center for active-duty status on the relevant dates. Retain the verification certificate.
- Apply §3952. If active duty is confirmed, determine whether the contract and first payment both pre-date service. The rules engine makes this determination and documents the statutory basis.
- Decision gate:
- Protected → No self-help repossession. Place a hold, and pursue a court order if you intend to proceed. Document the hold and the basis.
- Not protected → Proceed under your normal process, with the verification result and reasoning retained in the file.
- Document everything. The verification certificate, the eligibility determination, the decision, and the timestamp — a defense-ready record for every repo decision, protected or not.
- Monitor. Active-duty status and account status change. Re-screen open accounts on a schedule so a borrower who enters service after origination is caught.
Common failure points
- Manual, one-at-a-time lookups that get skipped at volume. The CFPB has found that most eligible accounts never receive protections precisely because manual checks break down at scale. Batch screening removes the human gap.
- Checking once and never again. Status changes; a single origination-time check misses borrowers who deploy later.
- No record of the check. “We usually check” is not a defense. If it isn’t documented, in the DOJ’s eyes it didn’t happen.
- Relying on the borrower to self-identify. The obligation to determine status sits with you, not the servicemember.
Who needs this workflow
This applies to any operation that repossesses or forwards repossessions: auto lenders, buy-here-pay-here dealers, debt collectors and recovery firms, and the towing and disposition vendors that act on their orders. The SK Towing and VMS San Antonio cases show the liability reaches the vendors who dispose of the vehicles, not just the lender who ordered it.
What does your pre-repo verification process actually look like — and could you prove it to an examiner for every repossession in the last three years?
Civrel verifies military status before every repossession decision, applies §3952 automatically, and keeps the audit trail that proves it. Check your repo pipeline exposure or talk to us.
Related training
See these topics covered in depth in our free SCRA training videos. Watch now →
Mario Bailey · Founder & CEO, Civrel
Mario serves in the Air National Guard (Cyber Systems Operations) and spent ten years as a software engineer before founding Civrel. He has been on the receiving end of SCRA compliance — getting his own protections applied took longer than it should have — and built Civrel so institutions can get it right.
Disclaimer: This content is provided for general informational purposes only and does not constitute legal advice. SCRA obligations depend on your institution's specific facts and on applicable federal and state law. Consult qualified counsel before acting on anything you read here.
Ready to automate your SCRA compliance?
See how civrel.io replaces manual processes with continuous, automated monitoring.