Casino ID Verification, Built Into the Cage
IT Casino Solutions builds casino ID verification into CMS Core, its on-premise casino management system for US cardrooms, so patron identity checks happen inside the cage and compliance workflows — not in a separate tool bolted on afterward. When a patron opens an account, requests a marker, or triggers a reportable transaction, the identity check and the compliance record are the same event in the same system.
Title 31 of the Bank Secrecy Act requires casinos and card clubs to verify and record patron identification in connection with reportable currency transactions. That recordkeeping obligation is a core part of any casino's anti-money-laundering (AML) program, and it's why patron ID verification, marker underwriting, and Title 31 reporting live in the same CMS Core modules rather than three disconnected systems. For specifics on how these requirements apply to your operation, consult your compliance counsel.
What CMS Core Verifies
Patron intake in CMS Core checks identity against the records a compliant cardroom is expected to verify, grouped here by what each check protects against.
Sanctions & Watchlist Screening
OFAC Screening
Checks patrons against the U.S. Treasury's Office of Foreign Assets Control sanctions list as part of casino OFAC screening at intake.
PEP Screening
Flags politically exposed persons (PEPs) so compliance staff can apply the additional due diligence those patrons require.
Identity Documents
Government-Issued ID
Verifies a driver's license, state ID, or other government-issued credential presented at the cage.
Passport
Accepts and verifies passport identification for patrons without a domestic government-issued ID.
SSN
Confirms the Social Security number provided at intake matches the patron on record.
Residence / Address
Confirms a patron's address of record for correspondence, marker collection, and compliance reporting.
Financial Standing
TIN Check
Validates a Taxpayer Identification Number for W-2G and other IRS reporting tied to patron winnings.
Employment History
Records employment information used as part of marker credit review.
Credit
Supports marker and credit underwriting decisions with a patron's credit standing.
Where Verification Happens in the System
Casino ID verification isn't a standalone feature in CMS Core — it's tied into the same modules that handle compliance recordkeeping, cage operations, and patron records.
Compliance & MTL
- Patron ID verification recorded alongside real-time MTL/SAR monitoring
- CTR automation tied to the same patron record
- Audit-ready reporting for regulatory examinations
Player Pay Office (the Cage)
- ID verification at intake for patron bank accounts
- Marker credit underwriting and approval
- Checks and counter-check tracking
- Safe deposit boxes
Player Management
- Patron intake and verification management
- Patron database with a monitored modification log
- Barred patron list management
- Merging and editing patron accounts
On the employee side, CMS Core ties employee records into Back Office HR management, dealer and floor scheduling, and Employee Pay Office imprest tracking — keeping employee data in the same system as patron verification, without a separate background-check product to reconcile.
Why On-Premise Matters for Identity Data
Patron identity documents and Social Security numbers are among the most sensitive data a cardroom holds. CMS Core is 100% on-premise: casino ID verification records stay on servers the operator owns and controls. IT Casino Solutions does not host, store, or maintain persistent access to that operational data.
That deployment model is a deliberate choice for the kind of data casino ID verification produces. See our full breakdown of on-premise vs. cloud casino management systems for how the two models compare on data control, infrastructure, and compliance posture.
Proof Points
IT Casino Solutions has built casino ID verification and compliance workflows for US cardrooms since 2002, backed by patented technology.
Four issued US patents cover CMS Core's dealer coordination, player cage, and multi-transaction log technology, including US 10,109,148, “Casino operations management system with player cage and multi-transaction log.” See the full patent list for details.
Cardrooms running CMS Core
Frequently Asked Questions
What ID verification does a casino management system need?
A casino management system needs to verify and record patron identification for reportable currency transactions under Title 31 of the Bank Secrecy Act. CMS Core, from IT Casino Solutions, builds patron and employee ID verification into the cage, compliance, and player management modules of its on-premise casino management system.
What checks does CMS Core run on patrons?
CMS Core supports OFAC sanctions screening, TIN checks, PEP (politically exposed person) screening, SSN verification, government-issued ID, passport verification, residence/address confirmation, employment history, and credit checks used in marker underwriting.
Does CMS Core store patron ID data in the cloud?
No. CMS Core is 100% on-premise, so patron ID verification records stay on the operator's own servers. IT Casino Solutions does not host, store, or maintain persistent access to that data.
How does ID verification support Title 31 compliance?
Title 31 requires casinos to verify and record patron identification for reportable currency transactions. CMS Core's Compliance & MTL module ties patron ID verification to real-time MTL/SAR monitoring, CTR automation, and audit-ready reporting, so identity checks and compliance recordkeeping happen in one system.
See Casino ID Verification in CMS Core
Talk to our team about how patron and employee ID verification fits into your Title 31 compliance workflow, or contact us with questions about OFAC screening, marker underwriting, or migration from your current system.