Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
AutoScribe v. EmerchantPay: Patent Dismissal — Payment Form IP | PatSnap
Patent Litigation

AutoScribe v. EmerchantPay: Voluntary Dismissal After 194 Days

AutoScribe Corp. sued EmerchantPay Corporation in Delaware District Court, asserting two patents covering web payment form and WPF API technology. Before any answer was filed, AutoScribe voluntarily dismissed the action without prejudice, with each party bearing its own fees and costs.

Resolution time
194days
Days from filing to voluntary dismissal — resolved before defendant answered
Patents asserted
2
US12462234B2 and US11620621B2 — Web Payment Form / WPF API technology
Outcome
Voluntary dismissal
Dismissed without prejudice; each party bears its own fees and costs
Cost ruling
Each party pays own
No fee or cost award; each side bears its own litigation expenses
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Payment form patent suit ends before EmerchantPay files any answer

AutoScribe Corp. filed suit against EmerchantPay Corporation on 10 December 2025 in the Delaware District Court before Judge Joshua D. Wolson, asserting infringement of two patents — US12462234B2 and US11620621B2 — directed at web payment form and WPF API technology. The accused product is EmerchantPay's 'Web Payment Form' product, or products otherwise using the 'WPF API'. AutoScribe was represented by Connolly Gallagher LLP; EmerchantPay by Morris James LLP.

On 22 June 2026 — 194 days after filing — AutoScribe filed a Notice of Voluntary Dismissal Without Prejudice pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). The notice states that no answer had been filed at that point, making Rule 41(a)(1)(A)(i) dismissal available as of right. The recorded Basis of Termination is 'Voluntary dismissal'; the docket order states the dismissal is without prejudice, with each party to bear its own fees and costs.

The dismissal occurred before the defendant had filed any responsive pleading, which is notable because it leaves AutoScribe's patent claims formally unresolved on the merits. Whether the dismissal reflects a negotiated resolution, a strategic repositioning, or another commercial consideration is not disclosed in the available public record. The specific terms, if any, beyond the fee-bearing arrangement stated in the notice, are not disclosed in the available record.

See Complete Case & Patent Analysis →
Case at a glance
CourtDelaware District Court
JudgeJoshua D. Wolson
FiledDecember 10, 2025
ClosedJune 22, 2026
Duration194 days
OutcomeVoluntary dismissal
Verdict causeInfringement Action
BasisVoluntary dismissal
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Delaware District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 194 days

Days from filing to voluntary dismissal — resolved before defendant answered

Case timeline: Complaint filed DEC 10 2025 — 194 days total Horizontal timeline showing the three key events in AutoScribe Corp. v EmerchantPay Corporation from filing to resolution. Source: PACER, Delaware District Court. DEC 10 2025 Complaint filed Pre-trial proceedings JUN 22 2026 Voluntary dismissal 194 DAYS TOTAL
Patent at issue

US12462234B2 & US11620621B2 — Web Payment Form and WPF API technology

Publication No.US12462234B2
Application No.US18/176173
Patent details
ProductWeb payment form and WPF API technology for online payment processing
Cited in actionDecember 10, 2025

Publication No.US11620621B2
Application No.US16/535424
Patent details
ProductWeb payment form methods and systems for electronic payment transactions
Cited in actionDecember 10, 2025
Technical brief · sourced from PatSnap patent database
Patent figurePatent figure
Representative claim (1 of 2 independent)
1. A method of processing a payment transaction from a payer to a payee, the method being performed by one or more secure servers, the method comprising: providing, by the one or more secure servers to a merchant server providing a webpage to a payer computing system used by the payer, an application programming interface (API) that: provides financial account registration and token retrieval functions that can be executed to process the payment transaction; provides access to the financial account registration and token retrieval functions to the merchant server; receives, from the merchant server via the API, a…
Technical background
This application is a continuation of U.S. application Ser. No. 16/535,424, filed Aug. 8, 2019, which is a continuation of U.S. application Ser. No. 15/408,185, filed Jan. 17, 2017, now U.S. Pat. No. 10,423,940, which is a continuation of U.S. application Ser. No. 13/679,545, filed Nov. 16, 2012, now U.S. Pat. No. 9,576,279, which claims the benefit of U.S. Provisional Application No. 61/655,482, filed Jun. 5, 2012, and U.S. Provisional Application No. 61/698,574, filed Sep. 8, 2012. The aforementioned patent appli…
Patent family
14 family members across 4 jurisdictions (US, EP, CA, WO)
PatSnap Eureka · FTO Search Agent
Should you run an FTO against US12462234B2 and US11620621B2?

Payment technology companies — including PSPs, acquirers, payment gateway operators, and e-commerce platform providers — that offer hosted payment pages, web payment form integrations, or WPF API products should treat this case as a prompt to assess their freedom-to-operate position. AutoScribe's voluntary dismissal without prejudice does not eliminate the risk; it preserves AutoScribe's ability to refile against EmerchantPay or to initiate new actions against other defendants in this space.

Run FTO in Eureka
Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Official verdict

Official order — verbatim text

Plaintiff Autoscribe Corporation (“Plaintiff”) hereby files this Notice of Voluntary Dismissal Without Prejudice pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(i). No answer has been filed in this case. Accordingly, Plaintiff voluntarily dismisses this action against Defendant Emerchantpay Corporation without prejudice, with each party to bear its own fees and costs.
Source: PACER Docket, Case 1:25-cv-01487, Delaware District Court

The dismissal notice invokes Rule 41(a)(1)(A)(i) and confirms no answer had been filed, making the dismissal effective as of right. The notice specifies a without-prejudice posture and a mutual fee-bearing arrangement. No merits determination was made by the court on either patent, meaning the validity and infringement of US12462234B2 and US11620621B2 remain open questions.

PACER case 1:25-cv-01487 · Public docket record Explore in Eureka ↗
Dismissal terms

Voluntarily dismissed: what the Rule 41 exit means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i) dismissal as of right — no court order required

Under Federal Rule of Civil Procedure 41(a)(1)(A)(i), a plaintiff may dismiss an action without a court order at any time before the opposing party serves an answer or a motion for summary judgment. AutoScribe invoked this rule, meaning the dismissal was effective upon filing the notice. No merits ruling was issued; the court made no finding on validity or infringement.

Dismissed before answer filed
Prejudice qualifier

Without prejudice: the distinction matters for future enforcement

A dismissal without prejudice does not bar AutoScribe from refiling claims on the same patents against EmerchantPay in the future, subject to applicable statutes of limitations and any other procedural constraints. A dismissal with prejudice would extinguish those claims permanently. The public record states the dismissal is without prejudice; the specific terms underlying AutoScribe's decision to dismiss — including any agreements between the parties — are not disclosed in the available record.

Claims may be refiled
Defendant outcome

EmerchantPay exits without a merits ruling — but risk is not eliminated

EmerchantPay obtained a termination of this proceeding without having to litigate validity or infringement of either asserted patent. However, because the dismissal is without prejudice, the WPF API and Web Payment Form products remain potentially subject to future assertion of US12462234B2 and US11620621B2. Each party bears its own fees and costs, meaning EmerchantPay received no cost award despite prevailing procedurally.

No merits ruling; exposure persists
Commercial implications

Web payment form IP remains live: what this means for the payments sector

Neither asserted patent was invalidated or adjudicated non-infringed. AutoScribe's patents covering web payment form and WPF API technology remain fully enforceable. Payment processors and gateway providers offering similar hosted payment page or WPF API products should treat this outcome as a signal that the patents remain active enforcement tools. Competitors in this space should consider freedom-to-operate analysis against both patents.

Patents remain enforceable
Legal analysis based on PACER docket records for case 1:25-cv-01487 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffAutoScribe Corp.Company/Search in Eureka ↗
DefendantEmerchantPay CorporationCompany/Search in Eureka ↗
Plaintiff counselAlan Richard SilversteinAttorneyCounsel for AutoScribe Corp.Search in Eureka ↗
Plaintiff counselArthur G. ConnollyAttorneyCounsel for AutoScribe Corp.Search in Eureka ↗
Plaintiff counselJason S. McManisAttorneyCounsel for AutoScribe Corp.Search in Eureka ↗
Plaintiff law firmConnolly Gallagher LLPLaw FirmRepresenting AutoScribe Corp.Search in Eureka ↗
Defendant counselKenneth L. Dorsney.AttorneyCounsel for EmerchantPay CorporationSearch in Eureka ↗
Defendant law firmMorris James LLPLaw FirmRepresenting EmerchantPay CorporationSearch in Eureka ↗
Presiding judgeJudge Joshua D. WolsonJudgeDelaware District CourtSearch in Eureka ↗
R&D signals

R&D signals in the web payment form and checkout API space

Forward-looking patent and innovation intelligence for payment technology teams monitoring AutoScribe's portfolio and WPF API filing trends.

Patent portfolio

AutoScribe's patent footprint in payment form technology

AutoScribe holds at least two granted US patents (US12462234B2 and US11620621B2) covering web payment form and WPF API methods. Understanding the full breadth and prosecution history of this portfolio — including any continuation or divisional applications — is critical for payment technology firms assessing enforcement exposure before AutoScribe initiates a new action.

Portfolio depth analysis
Technology landscape

Filing trends in hosted payment page and WPF API patents

Hosted payment pages and API-driven checkout flows are an active filing area as PSPs and payment gateways compete on integration simplicity and security. Tracking patent filing trends in this space — particularly claims covering form tokenisation, iframe-based payment capture, and API authentication — helps R&D teams identify crowded claim areas and white space for differentiated development.

WPF API filing trends
Competitor IP posture

EmerchantPay's patent position in payment gateway technology

EmerchantPay operates as a payment gateway and acquiring processor. Understanding whether EmerchantPay holds its own patents in payment form or API integration technology — or relies entirely on third-party IP — informs its defensive posture in future disputes and signals where it may be vulnerable to assertion campaigns by other patent holders in the checkout technology space.

Defensive IP exposure
White space

Adjacent R&D opportunities near web payment form claim scope

The claim scope of the AutoScribe patents centres on web payment form and WPF API integration. Adjacent R&D areas — including server-side payment orchestration, multi-PSP routing logic, and embedded finance checkout flows — may represent lower-encumbrance innovation space for engineering teams seeking to differentiate without entering the core claim territory of existing granted patents.

Innovation white space
Related litigation

Similar patent cases: web payment form and WPF API infringement actions

Explore comparable patent infringement cases involving web payment form, payment gateway, and checkout API technology filed in Delaware District Court and related venues.

🔍
Access 40+ similar cases in PatSnap Eureka
AutoScribe Corp. patent enforcement history, Delaware District Court case history, AutoScribe Corp.'s full IP portfolio, and comparable case analysis
Payment gateway patent suitsWPF API infringement actionsAutoScribe prior filingsPre-answer Rule 41 dismissals
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the payments IP enforcement landscape

A pre-answer voluntary dismissal without prejudice keeps AutoScribe's patent portfolio fully live against EmerchantPay and the broader payments market.

Both asserted patents remain fully enforceable after dismissal

No court made any finding on validity or infringement of US12462234B2 or US11620621B2. Payment technology companies operating hosted payment pages or WPF API integrations should not treat this dismissal as clearing the IP landscape — AutoScribe retains the right to refile against EmerchantPay or assert these patents against other defendants.

Pre-answer dismissal suggests the commercial dynamic shifted quickly

Voluntarily dismissing before the defendant answers — within 194 days — typically suggests a shift in plaintiff's strategic calculus. Whether that reflects a commercial arrangement, a portfolio decision, or a jurisdictional reassessment, the public record is silent. Competitors should monitor AutoScribe's docket activity for any new filings asserting the same patents.

🔒
Full strategic analysis in PatSnap Eureka
Unlock deeper analysis on AutoScribe's payment-form patent enforcement strategy and FTO risk for WPF API providers in Delaware District Court.
Portfolio enforcement trendsWPF API FTO risk mapLikely next defendants
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

AutoScribe v EmerchantPay — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Don't let live payment form patents catch your product team off-guard

US12462234B2 and US11620621B2 remain enforceable after this dismissal. Run a structured FTO through PatSnap Eureka to map your WPF API and hosted checkout products against AutoScribe's claim scope before the next enforcement action begins.

Disclaimer

This page is compiled from public court dockets and third-party patent and litigation data via PatSnap Eureka, and is provided for general informational purposes only. The information shown — including party names, patent and application numbers, dates, case status, outcomes, and any analysis — may be incomplete, may not reflect the most recent filings or legal status, and may contain errors or omissions. Verify all details against official court records (for example, PACER) and the relevant patent office before relying on them.

Nothing on this page constitutes legal advice or a legal opinion on the validity, infringement, enforceability, or scope of any patent or case, and no attorney‑client relationship is created by its use. Any description of an outcome (such as a dismissal, settlement, or consent judgment) is a general summary, not a legal determination. All patents, trademarks, and company or law‑firm names are the property of their respective owners. PatSnap makes no warranty as to the accuracy or completeness of this content and disclaims, to the fullest extent permitted by law, all liability for reliance on it. For advice on a specific matter, consult qualified legal counsel.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.