Legislative intelligence / 90R
SESSION 2027View project ↗

Business and Commerce Code § 523.052: NOTIFICATION TO CHECK VERIFICATION ENTITIES THAT CUSTOMER IS VICTIM OF IDENTITY THEFT

No bill in the 90th Legislature changes this section yet

Follow this section in Texas Bill Atlas: a bill filed later that changes it shows up as new.

Part of Business and Commerce Code Chapter 523, with every bill that changes it.

Bills are matched to sections automatically from their text and can be missed, for example when a bill changes a whole chapter at once or renumbers sections. No bill listed here does not mean no bill changes this section.

Current law

Sec. 523.052. NOTIFICATION TO CHECK VERIFICATION ENTITIES THAT CUSTOMER IS VICTIM OF IDENTITY THEFT. (a) In this section:

(1) "Check verification entity" means a consumer reporting agency that compiles and maintains, for businesses in this state, files on consumers on a nationwide basis regarding the consumers' check-writing history.

(2) "Financial institution" means a bank, savings association, savings bank, or credit union maintaining an office, branch, or agency office in this state.

(b) A financial institution shall submit the information as required by Subsection (c) if a customer notifies the financial institution that the customer was a victim of an offense under Section 32.51, Penal Code, requests that the financial institution close an account that has been compromised by the alleged offense, and presents to the financial institution:

(1) a copy of a police report of an offense under Section 32.51, Penal Code;

(2) a sworn statement by the person that the person was the victim of an offense under that section; and

(3) written authorization to submit the information required by Subsection (d) to the electronic notification system established under Section 11.309, Finance Code, for secure distribution to check verification entities.

(c) A financial institution that receives the documents required by Subsection (b), not later than the second business day after the date the customer provides the documents to the financial institution, shall submit the information required by Subsection (d) to the electronic notification system established under Section 11.309, Finance Code.

(d) The information submitted by a financial institution under Subsection (c) must include:

(1) the customer's name, address, phone number, date of birth, and driver's license number or government-issued identification number;

(2) the financial institution account number of any account that has been compromised by the alleged offense and has been closed in response to the alleged offense;

(3) the financial institution routing number; and

(4) the number on any check that has been lost, stolen, or compromised.

(e) A check verification entity shall maintain reasonable procedures, in accordance with rules adopted by the finance commission, to prevent the check verification entity from recommending acceptance or approval of a check or similar sight order drawn on an account identified in the notification if:

(1) the check verification entity receives notification through the electronic notification system; or

(2) a customer presents to the check verification entity:

(A) a copy of a police report of an offense under Section 32.51, Penal Code;

(B) a sworn statement by the person that the person was the victim of an offense under that section and that the person has requested that the financial institution close any account that has been compromised by the alleged offense; and

(C) the information described by Subsection (d).

(f) A financial institution or check

The section continues: whole chapter.

Links

Texas Bill Atlas is an independent research tool, not an official state website.

PLEASE READ

Before you use Texas Bill Atlas

An independent, open-source project. This site is not affiliated with, endorsed by, or operated by the Texas Legislature, the Texas Legislative Council, the Secretary of State, or any state agency.

Data may be incomplete, delayed, or wrong. Bill records are copied automatically from the legislature’s public files. Topic, agency, party, influence and last-action tags, and the full-text summaries written by Luna (an AI model), are automated interpretations and can be mistaken.

Not advice. Nothing here is legal, political, or professional advice. The project and its contributors make no warranty of accuracy or completeness and accept no liability for errors, omissions, or decisions made using this site.

Check the official record. Confirm anything that matters on Texas Legislature Online. Spotted a mistake? Report it on GitHub.

TEXAS BILL ATLAS

Privacy Policy

Last updated: November 11, 2026

Texas Bill Atlas is a free, independent, open-source project. We believe you should be able to research legislation without creating an account or providing personal information.

Information we collect

We do not require registration, names, email addresses, or other personal information to use the service.

We do not sell personal information, serve targeted advertising, or intentionally track individual browsing activity.

Analytics and security

We use Cloudflare for website delivery, security, and traffic analytics.

Cloudflare may process technical information such as IP addresses, browser details, request information, and website usage statistics. Cloudflare may also use cookies necessary for security and abuse prevention.

For more information, see Cloudflare's Privacy Policy.

Watchlists and saved preferences

Watchlists and preferences are stored locally in your browser by default.

If you choose to enable watchlist synchronization, we store the selected bill numbers, the member codes of legislators you follow, your saved searches (their names, search words and filters), filters, and hashed access keys on our server. View-only links show the bill numbers only.

No account or personal information is required. Anyone possessing a valid private access link may access the associated watchlist according to that link's permissions.

You can delete a synced watchlist using its edit access key. Inactive synced watchlists are automatically removed after approximately one year.

Technical data

Our servers may temporarily process IP addresses and request information for security, rate limiting, and reliable operation.

We do not use this information to build individual user profiles.

The site also loads certain external resources, including Google Fonts. Those providers may receive ordinary technical request information.

Third-party services

Links to government websites, GitHub, and other external services are governed by their respective privacy policies.

Changes

We may update this policy as the project develops. The current version will be available on this website with its updated date.

Questions

For questions about the project or its privacy practices, visit our GitHub repository.