Statute of Limitations for Credit Card / Open Account Debt in New York

6 min read

Published March 22, 2026 • By DocketMath Team

Overview

In New York, claims tied to credit card and other “open account” debts are often subject to a statute of limitations (SOL) measured in years. If a creditor (or its debt buyer) files a lawsuit after the SOL expires, the debtor may be able to raise a time-bar defense to prevent the claim from being enforced in court.

For most consumer collection lawsuits in New York involving credit card/open account style debt, the starting point is typically the general civil limitations framework—meaning you usually look to the default SOL rather than a special, claim-specific carve-out.

Note: Based on the jurisdiction data provided here, no claim-type-specific sub-rule was found for credit card or open account debt. The limitation period below reflects the general/default period.

If you want to calculate the deadline for your situation, DocketMath can help you model how different dates affect the outcome—especially where the key date (like the last payment or last account activity) is disputed.

Limitation period

Default SOL period (general rule)

For New York, the general SOL period for the relevant category described in the jurisdiction data is:

  • 5 years

This is the general/default period identified for the jurisdiction data used in this page.

What “5 years” usually means in practice

Your timeline typically turns on a factual date—most commonly one of the following (depending on the evidence the creditor provides):

  • Date of the last payment toward the account
  • Date of the last charge or purchase (account activity)
  • Date the debt became due/accelerated (where terms make that relevant)

Because collection cases often fight over the “last activity” date, the same underlying debt can produce different SOL results depending on which date the plaintiff can substantiate.

How to think about the “key input”

When you use a calculator, you’ll generally provide:

  • Event date (e.g., last payment date or last activity date)
  • Jurisdiction (New York)
  • Optional assumptions (for example, whether you’re modeling “days after” a known date)

Output behavior you should expect:

  • If you move the event date forward, the SOL deadline generally moves forward as well.
  • If the event date is earlier, your deadline moves earlier, making it more likely the claim is time-barred.
  • If your event date is unclear, the calculator can be used to model a range of outcomes.

Pitfall: Using the wrong “last activity” date is the most common reason people get a misleading deadline. Payment posting delays, account reinstatements, or partial payments can all shift what a court may treat as the operative date.

Key exceptions

Even with a stated general period, the SOL landscape can change if certain legal or factual events occur. Below are common categories of “exceptions” or modifications that affect whether the SOL stops running or restarts.

1) Tolling: events that pause the clock

Tolling can occur when the law permits the SOL to be suspended for a period (for example, due to a legal disability or a specific statutory trigger). The exact applicability depends on the circumstances and the statute invoked in the pleadings or filings.

Practical takeaway:

  • If you have documentation showing a relevant legal event during the five-year window (or shortly after), you may need to factor that into the timeline model.

2) Waiver or failure to raise the defense

A SOL defense is typically raised by the defendant (the debtor). If it is not asserted, some courts will treat the defense as waived.

Practical takeaway:

  • Don’t rely solely on the idea that “it’s been more than 5 years.” The timing must also be presented procedurally in the case.

3) Acknowledgment or partial payment

In many SOL regimes, certain actions by the debtor can affect the running of time (commonly described as acknowledgment, reaffirmation, or partial payment impacts). Whether those actions reset the clock depends on the applicable law and the facts.

Practical takeaway:

  • Keep records of payment receipts, account statements, and any correspondence. These can matter both to (a) the event date and (b) whether any exception concept applies.

Warning: This page explains the general/default SOL period and common exception concepts at a high level. It does not examine every procedural wrinkle in a specific lawsuit. If you’re dealing with an active case, review the filed complaint and the dates it alleges before relying on any computed deadline.

4) How the plaintiff’s allegations affect the SOL analysis

Collection complaints often plead:

  • the date of default
  • the date of last payment
  • the account history range
  • the current balance claim

Different pleadings can point to different “event dates.” Your calculator input should align as closely as possible with the date(s) alleged and supported.

Checklist for aligning facts to the calculator:

Statute citation

The general/default SOL period referenced in this New York jurisdiction data is 5 years.

Note: The jurisdiction data provided indicates this as the general/default period and also states that no claim-type-specific sub-rule was found for credit card/open account debt. That is why the page applies the same five-year framework rather than branching into multiple SOL categories.

Use the calculator

DocketMath’s statute-of-limitations tool helps you compute a likely SOL deadline by working from the key dates you provide.

Primary CTA: /tools/statute-of-limitations

Inputs to consider

When using DocketMath, you’ll typically provide:

  • Jurisdiction: New York (US-NY)
  • Event date: choose the best-supported “last activity” date you can document
  • Optional comparison dates: if there’s uncertainty, model more than one date (e.g., “last payment” vs. “last charge”)

Output: what you’ll get

The tool outputs a computed deadline date based on the 5-year general/default period, using your selected event date.

Use the output this way:

  • If the lawsuit filing date (or another relevant filing milestone) is after the calculated deadline, the claim may be time-barred under the SOL framework you modeled.
  • If the filing date is before the deadline, the claim may still be within time (again, based on the dates you entered).

Pitfall: Don’t mix “statement dates” with “transaction dates.” A statement might be generated on one day, but the underlying payment or purchase posts on another—those differences can move the computed deadline.

Practical workflow (quick)

Related reading