Legislative intelligence / 90R
SESSION 2027View project ↗

Business and Commerce Code § 56.054: ENFORCEMENT OF CLAUSE PROHIBITED IF UNCONSCIONABLE

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 56, 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. 56.054. ENFORCEMENT OF CLAUSE PROHIBITED IF UNCONSCIONABLE. (a) A contingent payor or its surety may not enforce a contingent payment clause if the enforcement would be unconscionable. The party asserting that a contingent payment clause is unconscionable has the burden of proving that the clause is unconscionable.

(b) The enforcement of a contingent payment clause is not unconscionable if the contingent payor:

(1) proves that the contingent payor has exercised diligence in ascertaining and communicating in writing to the contingent payee, before the contract in which the contingent payment clause has been asserted becomes enforceable against the contingent payee, the financial viability of the primary obligor and the existence of adequate financial arrangements to pay for the improvements; and

(2) has done the following:

(A) made reasonable efforts to collect the amount owed to the contingent payor; or

(B) made or offered to make, at a reasonable time, an assignment by the contingent payor to the contingent payee of a cause of action against the obligor for the amounts owed to the contingent payee by the contingent payor and offered reasonable cooperation to the contingent payee's collection efforts, if the assigned cause of action is not subject to defenses caused by the contingent payor's action or failure to act.

(c) A cause of action brought on an assignment made under Subsection (b)(2)(B) is enforceable by a contingent payee against an obligor or a primary obligor.

(d) A contingent payor is considered to have exercised diligence for purposes of Subsection (b)(1) under a contract for a private project governed by Chapter 53, Property Code, if the contingent payee receives in writing from the contingent payor:

(1) the name, address, and business telephone number of the primary obligor;

(2) a description, legally sufficient for identification, of the property on which the improvements are being constructed;

(3) the name and address of the surety on any payment bond provided under Subchapter I, Chapter 53, Property Code, to which any notice of claim should be sent;

(4) if a loan has been obtained for the construction of improvements:

(A) a statement, furnished by the primary obligor and supported by reasonable and credible evidence from all applicable lenders, of the amount of the loan;

(B) a summary of the terms of the loan;

(C) a statement of whether there is foreseeable default of the primary obligor; and

(D) the name, address, and business telephone number of the borrowers and lenders; and

(5) a statement, furnished by the primary obligor and supported by reasonable and credible evidence from all applicable banks or other depository institutions, of the amount, source, and location of funds available to pay the balance of the contract amount if there is no loan or the loan is not sufficient to pay for all of the construction of the improvements.

(e) A contingent payor is considered to have exercised diligence for purpo

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.