Monticello Enterprises vs. Petco: Browser Payment API Patent Case Consolidated in Texas
What would you like to do next?
Choose your path based on your current needs:
📋 Case Summary
| Case Name | Monticello Enterprises, LLC v. Petco Health & Wellness Company, Inc., et al. |
| Case Number | 6:23-cv-00761 (W.D. Tex.) (Consolidated into Lead Case: 6:23-cv-753-XR) |
| Court | Western District of Texas |
| Duration | Nov 2023 – Apr 2024 162 days (to administrative closure) |
| Outcome | Procedural Consolidation — Litigation Continues |
| Patents at Issue | |
| Accused Products | Petco’s browser payment request API integrations, in-app payment systems, and point-of-sale checkout interfaces. |
Case Overview
The Parties
⚖️ Plaintiff
A patent assertion entity (PAE) asserting IP rights in browser-based and mobile payment technologies. Characterized by coordinated patent assertion strategies.
🛡️ Defendant
One of the largest specialty pet retailers in the United States, operating both physical retail locations and a significant e-commerce platform.
The Patents at Issue
This case involved six U.S. patents covering browser payment interfaces and in-store/in-app purchase APIs. These technologies are foundational to modern e-commerce checkout experiences and were asserted against Petco’s digital payment infrastructure.
- • US11468497B2 — Browser payment request API
- • US11461828B2 — Simplified in-store/in-app purchase flows
- • US11004139B2 — User-interface-driven payment processing
- • US10121186B2 — Browser-based payment systems
- • US10643266B2 — Payment initiation and processing
- • US9824408B2 — Secure transaction methods
Building a similar payment system?
Check if your payment API or e-commerce checkout implementation might infringe these or related patents before deployment.
The Verdict & Legal Analysis
Outcome
Case 6:23-cv-00761 was **administratively closed** on April 19, 2024, pursuant to a consolidation order. No merits determination — no finding of infringement, validity, or damages — was issued in this specific case. The litigation continues under the consolidated lead case number 6:23-cv-753-XR.
Verdict Cause Analysis: Rule 42(a) Consolidation
The basis of termination here is purely procedural: **case consolidation**. Under Federal Rule of Civil Procedure 42(a), when actions share common questions of law or fact, a district court has broad discretionary authority to consolidate them. The Fifth Circuit has confirmed this discretion is “entirely within the district court’s” purview in service of judicial economy (Gentry v. Smith, 487 F.2d 571, 581 (5th Cir. 1973)), a precedent the court explicitly cited.
Monticello’s simultaneous multi-defendant filing created natural consolidation conditions. Courts increasingly exercise Rule 42(a) consolidation in coordinated patent assertion campaigns to eliminate duplicative Markman hearings, claim construction disputes, and scheduling conflicts — reducing judicial burden while preserving plaintiff’s ability to pursue all defendants under one roof.
Legal Significance
For multi-defendant patent campaigns: This case exemplifies a well-documented plaintiff strategy — filing near-simultaneous complaints against multiple defendants asserting the same patent portfolio, then allowing or encouraging consolidation to preserve resources while maintaining litigation pressure across defendants.
Claim construction implications: With six patents in suit covering overlapping technological concepts, consolidated Markman proceedings in the lead case will be particularly consequential. A single adverse claim construction ruling could dispose of multiple asserted patent families simultaneously.
Venue considerations: The Western District of Texas filing reflects continued plaintiff preference for the Waco and San Antonio divisions, notwithstanding In re: Google LLC (Fed. Cir. 2021) and subsequent transfer decisions that have reshaped venue calculus in the district.
Freedom to Operate (FTO) Analysis
This case highlights critical IP risks in browser payment API implementations. Choose your next step:
📋 Understand This Case’s Impact
Learn about the specific risks and implications from this litigation.
- View all 6 asserted patents in this technology space
- See which companies are most active in digital payment IP
- Understand claim construction patterns for payment APIs
🔍 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
Browser payment request APIs & in-app purchases
6 Asserted Patents
Covering core payment API functionality
IPR as Defense Track
Evaluate prior art against these patents
✅ Key Takeaways
Rule 42(a) consolidation is increasingly used to manage coordinated PAE campaigns — anticipate it in multi-defendant filings involving common patent portfolios.
Search related case law →Administrative closure does not mean dismissal; substantive litigation continues under lead case designation, requiring continued vigilance.
Explore precedents →Monitor consolidated docket 6:23-cv-753-XR for claim construction orders covering US9824408B2 through US11468497B2.
Track this case in Eureka →Browser payment API patents represent a growing assertion category warranting portfolio audits for e-commerce companies.
Conduct a portfolio audit →Frequently Asked Questions
Six U.S. patents: US9824408B2, US10121186B2, US10643266B2, US11004139B2, US11461828B2, and US11468497B2, covering browser payment APIs and in-app purchase systems.
The court consolidated this case with related cases under lead docket 6:23-cv-753-XR pursuant to Federal Rule of Civil Procedure 42(a), resulting in administrative closure. Litigation continues in the consolidated proceeding.
It reinforces that browser-based payment technologies remain active assertion targets. E-commerce companies should evaluate IPR options and conduct FTO analyses against this patent family.
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
- PACER – W.D. Tex. Case 6:23-cv-753
- USPTO Patent Public Search – US11468497B2
- W3C Payment Request API technical specification
- Cornell Legal Information Institute — Federal Rule of Civil Procedure 42(a)
- 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.