AutoScribe Corp. v. Paysafe: Payment Patent Dismissal Analysis
What would you like to do next?
Choose your path based on your current needs:
📋 Case Summary
| Case Name | AutoScribe Corp. v. Paysafe Limited |
| Case Number | 3:24-cv-00104 |
| Court | Texas Southern District Court |
| Duration | Apr 2024 – Jul 2024 104 days |
| Outcome | Plaintiff Dismissal — Without Prejudice |
| Patents at Issue | |
| Accused Products | Paysafe Payment API, Paysafe JS |
Case Overview
The Parties
⚖️ Plaintiff
Patent-holding entity asserting rights in automated data transcription and payment processing technology.
🛡️ Defendant
Global payment processing company offering integrated payment solutions across digital commerce. Defendant group included Paysafe Holdings (US) Corp., Paysafe Merchant Services Corp., and Paysafe Payment Processing Solutions LLC.
Patents at Issue
This case centered on a single patent covering automated data capture and processing technology relevant to payment APIs and JavaScript-based payment tools, which are crucial components in modern fintech infrastructure.
- • US 11,620,621 B2 — Automated data capture and processing technology for payment information.
Developing payment API or JS solutions?
Check if your payment technology might infringe this or related patents before launch.
The Verdict & Legal Analysis
Outcome
On **July 23, 2024**, AutoScribe Corp. filed a notice of voluntary dismissal as to all claims against all four Paysafe defendants. Chief Judge Jeffrey V. Brown entered the formal dismissal order on **July 24, 2024**, specifying: all claims **dismissed without prejudice** to refiling, each party to **bear its own attorneys’ fees and costs**, and dismissal executed pursuant to **Fed. R. Civ. P. 41(a)(1)(A)(i)**. No damages were awarded. No injunctive relief was granted or denied. No merit-based ruling was issued.
Key Legal Issues
Because the dismissal occurred before any substantive judicial ruling, there is no formal legal reasoning from the court regarding patent validity, infringement, or claim construction. The case record does not disclose the specific trigger for AutoScribe’s withdrawal. However, several strategic scenarios commonly drive Rule 41(a)(1)(A)(i) dismissals at this early stage: pre-answer settlement or licensing agreement, claim viability reassessment, or venue/jurisdictional strategy. The “each party bears its own fees” language is standard under Rule 41 at this stage and does not indicate fault or merit attribution to either side.
Freedom to Operate (FTO) Analysis
This case highlights critical IP risks in payment API and JavaScript-based payment processing. Choose your next step:
📋 Understand This Case’s Impact
Learn about the specific risks and implications from this litigation.
- View all related patents in payment processing
- See which companies are most active in fintech patents
- Understand API patent assertion trends
🔍 Check My Product’s Risk
Run a comprehensive FTO analysis for your own technology or product.
- Input your product description or technical features
- AI identifies potentially blocking patents
- Get actionable risk assessment report
High Risk Area
Payment APIs & JavaScript tools
US11620621B2 Active
Unlitigated on the merits
Design-Around Options
Possible for API integration methods
✅ Key Takeaways
Voluntary dismissal under Rule 41(a)(1)(A)(i) before answer preserves plaintiff’s refiling rights and avoids defendant counterclaims entering the record.
Search related case law →Multi-entity defendant groups require coordinated defense strategy from day one.
Explore precedents →Frequently Asked Questions
The case involved **U.S. Patent No. 11,620,621 B2** (Application No. 16/535,424), covering automated data capture and processing technology relevant to payment APIs and JavaScript-based payment tools.
AutoScribe filed a voluntary dismissal under Fed. R. Civ. P. 41(a)(1)(A)(i) on July 23, 2024. The case was dismissed without prejudice, with each party bearing its own fees. No public explanation was provided; common causes include settlement, licensing resolution, or strategic reassessment.
The dismissal leaves US11620621B2 without judicial merit review. The patent remains enforceable and may be asserted again — against Paysafe or others — making FTO analysis essential for fintech product teams.
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.
References
- USPTO Patent Full-Text Database – US11620621B2
- PACER – Case No. 3:24-cv-00104, Texas Southern District Court
- Texas Southern District Court – Chief Judge Jeffrey V. Brown
- 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.