PACSEC3 v. Axway: Dismissal Without Prejudice in API Security Patent Case

📄 View Full Report 📥 Export PDF 🔗 Share ⭐ Save

📋 Case Summary

Case NamePACSEC3, LLC v. Axway, Inc.
Case Number1:24-cv-04711 (N.D. Ga.)
CourtU.S. District Court for the Northern District of Georgia
DurationOct 2024 – Feb 2026 1 year 4 months
OutcomeDefendant Win — Dismissal Without Prejudice
Patents at Issue
Accused ProductsAxway Amplify Platform

Case Overview

In a decisive procedural ruling, the U.S. District Court for the Northern District of Georgia dismissed patent infringement claims brought by PACSEC3, LLC against Axway, Inc. — without prejudice — marking the close of Case No. 1:24-cv-04711 on February 3, 2026. The dispute centered on U.S. Patent No. 7,523,497 and alleged infringement by Axway’s Amplify product platform, a widely deployed API management and integration solution.

The Parties

⚖️ Plaintiff

is a patent assertion entity holding IP assets in the cybersecurity and network technology space. The company’s litigation model centers on licensing and enforcement of its patent portfolio against commercial technology providers.

🛡️ Defendant

is a global technology company specializing in API management, data integration, and digital transformation infrastructure. Its Amplify platform serves enterprise clients across financial services, healthcare, and government sectors — representing a commercially significant product line squarely at the center of this dispute.

Patents at Issue

The asserted patent, U.S. Patent No. 7,523,497 (Application No. US 10/841,064), covers technology in the network security and access control domain. While the specific claim language was subject to litigation proceedings, the patent’s technical scope — as reflected in the accused product — relates to secure data transmission and access management architecture relevant to API environments.

🔍

Developing an API Management platform?

Check if your platform design might infringe these or related patents before launch.

Run FTO Check →

The Verdict & Legal Analysis

Outcome

The court granted Axway’s Motion to Dismiss and dismissed the case without prejudice. No damages were awarded. No injunctive relief was granted. The “without prejudice” designation is legally critical: PACSEC3 retains the right to re-file a corrected or amended complaint, subject to applicable statutes of limitations and any conditions the court may impose.

Key Legal Issues

The dismissal arose from an infringement action — meaning PACSEC3’s operative complaint alleged that Axway Amplify directly or indirectly infringed claims of US7523497B2. Axway’s successful Motion to Dismiss (Dkt. 19) suggests the complaint failed to satisfy pleading standards sufficient to survive Rule 12(b)(6) scrutiny. This outcome reinforces the importance of robust claim-charting and detailed technical pleading in patent infringement complaints — particularly when asserting against sophisticated technology defendants represented by experienced IP litigation counsel.

⚠️

Freedom to Operate (FTO) Analysis

This case highlights critical IP risks in API security and pleading standards. Choose your next step:

📋 Understand This Case’s Impact

Learn about the specific risks and implications from this litigation.

  • View all 47 related patents in this technology space
  • See which companies are most active in API security patents
  • Understand claim construction patterns
📊 View Patent Landscape
⚠️
High Risk Area

API Security & Access Control

📋
47 Related Patents

In API management space

Pleading Specificity

Crucial for plaintiffs

✅ Key Takeaways

For Patent Attorneys & Litigators

Dismissals without prejudice at the Rule 12 stage remain an effective early defense strategy in district court patent cases.

Search related case law →

Pleading specificity is non-negotiable — courts require detailed claim-to-product mapping, not conclusory infringement allegations.

Explore precedents →

Monitor PACSEC3’s potential re-filing activity regarding US7523497B2 for precedent development.

Track patent activity →
🔒
Unlock Advanced IP & R&D Strategies
Get actionable insights for product teams on mitigating API security patent risk, including FTO timing guidance and defensive IP strategies.
Pleading Standards Impact FTO for API Products Defensive IP Strategies
Explore Full Analysis in PatSnap Eureka

Frequently Asked Questions

Ready to Strengthen Your Patent Strategy?

Join 18,000+ IP professionals using PatSnap Eureka to conduct prior art searches, draft patents, and analyse competitive landscapes with AI-powered precision.

PatSnap IP Intelligence Team

Patent Research & Competitive Intelligence · PatSnap

This analysis was produced by the PatSnap IP Intelligence Team — a group of patent analysts, IP strategists, and data scientists who work daily with PatSnap’s global patent database of over 2 billion structured data points across patents, litigation records, scientific literature, and regulatory filings.

The team specialises in tracking landmark litigation outcomes, translating complex court rulings into actionable IP strategy, and identifying the competitive intelligence implications for R&D and legal teams. All case analysis is grounded in primary sources: official court records, USPTO filings, and Federal Circuit opinions.

📊 2B+ Patent Data Points 🌍 120+ Countries Covered 🏢 18,000+ Customers Worldwide ⚖️ Global Litigation Database 🔍 Primary Source Verified

References & Resources

  1. USPTO Patent Center – US7523497B2
  2. PACER Case Lookup – 1:24-cv-04711
  3. PTAB IPR Proceedings Database
  4. PatSnap — IP Intelligence Solutions for Law Firms

This article is for informational purposes only and does not constitute legal advice. All case information is drawn from publicly available court records. For platform capabilities, visit PatSnap.

⚖️ Disclaimer: This article is for informational purposes only and does not constitute legal advice. The analysis presented reflects publicly available case information and general legal principles. For specific advice regarding patent litigation, FTO analysis, or IP strategy, please consult a qualified patent attorney.