Pay-If-Paid vs. Pay-When-Paid: The Clause That Can Leave Small Businesses Unpaid

If you sign a pay-if-paid clause, small business owners can end up doing the work, delivering it, and never getting paid, all without the contract being breached. That is the whole point of the clause: it makes the other side’s payment to you conditional on their customer paying them first. A pay-when-paid clause is different and far less dangerous, because it only delays your payment rather than eliminating it. The distinction decides who absorbs the loss when money upstream does not arrive, and it is written into contract language most subcontractors and service providers skim past.

Here is the direct answer to whether you have to worry about one you have already signed: it depends on your state, and the split is real. Some states void these clauses outright as against public policy. Others enforce them if the wording is clear enough. A few will apply another state’s more permissive rules if a choice of law clause in your contract points there. Below is how to tell which situation you are in before you sign, not after the invoice goes unpaid.

What a Pay-If-Paid Clause Actually Does

The difference between the two clauses is the difference between a condition and a schedule.

A pay-if-paid clause creates a condition precedent: the general contractor or client owes you nothing unless and until they are paid by the owner or end customer. If that upstream payment never comes, your right to payment never matures. The risk of the owner going broke, disputing the job, or simply refusing to pay is transferred from the party that chose and contracted with that owner onto you, who never met them.

A pay-when-paid clause is only about timing. It says the contractor will pay you within some period after they receive payment, but if that payment never arrives, they still owe you the money within a reasonable time. Courts generally read pay-when-paid language as a timing mechanism, not a permanent excuse, which is why the law firm Smith, Gambrell & Russell describes pay-when-paid as governing when payment is due while pay-if-paid governs whether it is due at all. That single word, if versus when, is the one your contract turns on.

These clauses are most common in construction contract payment terms, but they now appear in staffing agreements, IT and software subcontracts, marketing retainers with white-label vendors, and any arrangement where the company hiring you is itself getting paid by someone further up the chain. If your customer’s ability to pay you depends on their customer, expect to see one.

The State-by-State Split That Decides Everything

There is no single national rule. The same clause that is airtight in one state is worthless in another, and roughly a dozen states have moved to prohibit or sharply limit these provisions. As of 2026, states including California, Illinois, North Carolina, Wisconsin, and New York bar pay-if-paid clauses by statute or by court decision, with Virginia joining the list through legislation in 2022. The clearest way to see the divide is to compare two neighboring states that landed on opposite sides.

New York voids them. New York’s highest court settled this in 1995 in West-Fair Electric Contractors v. Aetna Casualty & Surety Co., holding that a clause forcing a subcontractor to assume the risk of the owner’s non-payment is void as contrary to public policy. The court grounded that on Lien Law section 34, which makes any agreement waiving the right to enforce a mechanic’s lien unenforceable. Because a pay-if-paid clause could strip a subcontractor of the payment that its lien depends on, New York treats it as an illegal lien waiver. A New York subcontractor who signed one can, in most cases, still collect.

New Jersey enforces them, if they are written clearly. In 2022, a New Jersey appellate court upheld a pay-if-paid clause in JPC Merger Sub v. Tricon Enterprises, holding that these provisions are enforceable so long as the contract contains clear and unequivocal language that owner payment is a condition precedent to the general contractor’s duty to pay the subcontractor. New Jersey has no statute banning the clause and treats sophisticated commercial parties as free to allocate the risk. The court did note one important limit: a contractor cannot rely on the clause if the contractor itself caused the owner’s non-payment.

So a subcontractor doing identical work on two sides of the Hudson River faces opposite outcomes on the same contract language. That is not a technicality. It is the difference between getting paid and eating the loss.

The Choice-of-Law Clause That Undoes Your State’s Protection

Living in a state that bans pay-if-paid clauses does not automatically protect you, because of a second clause that usually sits near the end of the contract. A choice of law clause states which state’s law governs the agreement. If your protective home state is New York but the contract says it is governed by the law of a state that enforces pay-if-paid clauses, a court may apply the more permissive law.

New York’s own highest court confirmed this in 2006 in Welsbach Electric Corp. v. MasTec North America. The subcontract for a New York project chose Florida law, and the court enforced the pay-if-paid clause under Florida law, holding that New York’s Lien Law policy was not fundamental enough to override the parties’ choice. The lesson is blunt: a boilerplate line naming another state can quietly delete the protection your legislature wrote for you.

There is a partial backstop worth knowing. New York’s Prompt Payment Act, effective in 2003, voids out-of-state choice-of-law provisions in contracts for New York construction projects, which is why Welsbach turned on an older contract. Several other states have similar anti-waiver statutes for local projects. But those protections are narrow, apply mainly to construction, and vary by state, so you cannot assume yours has one. When you do out-of-state work or sign with an out-of-state company, the choice-of-law clause deserves as much attention as the payment clause itself.

How to Read the Clause Before You Sign

You can usually spot the problem in the contract yourself. The clause will sit under a heading like Payment, Progress Payments, or Conditions of Payment. Watch for these signals, from most dangerous to least:

• “Condition precedent.” Language such as “Receipt of payment by the Contractor from the Owner is a condition precedent to any obligation of the Contractor to pay the Subcontractor” is a true pay-if-paid clause. This is the one that can leave you unpaid. The phrase condition precedent is the tell.
• “Shall not be obligated to pay unless and until.” Wording that the party “shall have no obligation to pay unless and until it has received payment” is also pay-if-paid, even without the Latin. It shifts the risk of non-payment onto you.
• “Within X days after receipt of payment.” A clause promising payment “within ten days after the Contractor receives payment from the Owner” is usually pay-when-paid. It sets timing, and most courts still require payment within a reasonable time if the upstream money never arrives.
• The governing-law line. Find the sentence naming which state’s law controls, often labeled Governing Law or Choice of Law. If it names a state other than your own, look up whether that state enforces pay-if-paid clauses.

If you find a true condition-precedent clause, you have real options before signing: strike it, convert it to pay-when-paid, cap the delay to a fixed number of days regardless of the owner, or add a carve-out that the condition does not apply if non-payment results from the contractor’s own default. On the choice-of-law line, ask that the contract be governed by your home state or by a state that bans these clauses. A counterparty who refuses every one of these is telling you something about how they plan to handle a payment problem.

When You Have Already Signed One

If the clause is already in a signed contract and payment has stalled, the analysis moves from drafting to leverage, and both small business contractor payment rights and the dispute-resolution path in your contract come into play. Mechanic’s lien and payment-bond rights often survive a pay-if-paid clause even in states that enforce the clause, because many states protect lien and bond claims separately by statute. Prompt-payment statutes may add interest and, in some states, attorney’s fees. And the clause itself may be attackable if the contractor’s own conduct prevented the owner’s payment.

Most of these disputes are resolved without a courtroom. As covered in our guide on alternative dispute resolution for small business contract disputes, a well-drafted contract usually dictates whether you mediate, arbitrate, or sue, and reading that clause is the first move once a payment fight begins. The broader lesson is the same one that governs protecting a small business’s intellectual property before a competitor forces the issue: the cheapest time to fix a contract is before you sign it, when a single edited sentence costs nothing and prevents a loss you would otherwise absorb in full.

A payment-condition clause is not always a dealbreaker, and on some jobs the risk is genuinely small. But you should know which clause you are signing, whether your state enforces it, and what a choice-of-law line is quietly doing to your protections. If a contract in front of you contains condition-precedent language and you are unsure how your state treats it, a short review before you sign is far less expensive than a collection fight after the work is done. A brief consultation can tell you where you stand and what to change while you still have the leverage to change it.

---

This article is general information, not legal advice. Enforceability of payment clauses is fact-specific and varies by state and contract; consult a licensed attorney about your particular situation.