Book a demo
RFCyber Corp. v. Apple Inc. — Mobile Payment NFC Patent Dispute | PatSnap
Explore in Eureka
Case ID1:23-cv-00661
FiledSep 2021
ClosedJan 2024
Patent Litigation

RFCyber Corp. v. Apple Inc. — Six NFC Patents, Apple Pay, Settled After 874 Days

RFCyber Corp. asserted six mobile payment and NFC patents against Apple’s iPhone X running Apple Pay in the Western District of Texas. The parties resolved their dispute privately and secured a court-ordered dismissal with prejudice, with each side bearing its own attorneys’ fees — a structure that strongly suggests a confidential settlement was reached.

Resolution time
874days
874 days — above median for multi-patent infringement cases in W.D. Texas
Patents asserted
6
US8448855B1 and 5 further NFC/mobile payment patents asserted
Outcome
Case Dismissed
Claims dismissed with prejudice — RFCyber cannot refile the same claims against Apple
Cost ruling
Own costs
Each party bears its own attorneys’ fees, costs, and expenses — no cost award made
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

Six NFC patents, Apple Pay in the crosshairs, quietly resolved in Texas

RFCyber Corp., a patent holding entity asserting a portfolio of NFC and mobile payment technology patents, filed suit against Apple Inc. in the Western District of Texas on September 7, 2021, before Chief Judge Alan D. Albright — a venue long favoured by patent plaintiffs. RFCyber alleged that the iPhone X running Apple Pay infringed six US patents covering secure element-based contactless payment, NFC emulation, and related mobile commerce technologies.

The case closed on January 29, 2024, after the parties jointly announced to the court that they had resolved all claims. RFCyber’s claims against Apple were dismissed with prejudice — permanently extinguishing those specific claims — while Apple’s defences were dismissed without prejudice, preserving Apple’s ability to raise them in future proceedings. Each side was ordered to bear its own legal costs, a standard confidential-settlement cost structure.

At 874 days, the litigation ran longer than many W.D. Texas patent cases that settle early but resolved before any trial or public judgment, suggesting substantive negotiation occurred during discovery or claim construction phases. The public record is silent on any monetary terms, licence grant, or other deal conditions, which is typical when a joint motion to dismiss precedes a private settlement agreement.

Case at a glance
Case no.1:23-cv-00661
DefendantApple, Inc.
CourtTexas Western
JudgeAlan D Albright
FiledSeptember 7, 2021
ClosedJanuary 29, 2024
Duration874 days
OutcomeCase Dismissed
Verdict causeInfringement Action
BasisCase Dismissed
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 / Texas Western District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to dismissal in 874 days

874 days — above median for multi-patent infringement cases in W.D. Texas

Case timeline: Complaint filed May 13 2025, NOV–DEC — 874 days total Horizontal timeline showing the three key events in RFCyber, Corp. v Apple, Inc. from filing to voluntary dismissal. Source: PACER, Texas Western District Court. SEP 7 2021 Complaint filed NOV–DEC 2021 Pre-trial proceedings JAN 29 2024 Dismissed with prejudice 874 DAYS TOTAL
Dismissal terms

What the with-prejudice dismissal means for RFCyber and Apple

Legal mechanism

Dismissed with prejudice — RFCyber’s claims are permanently closed

A dismissal with prejudice is a final adjudication on the merits for procedural purposes. RFCyber cannot refile these six patent infringement claims against Apple in any US court based on the same accused products and same patents. This is the highest-finality outcome short of a trial verdict, and courts grant it here because both parties jointly requested it — a hallmark of a negotiated resolution.

Permanent bar on refiling
Asymmetric dismissal

Apple’s defences dismissed without prejudice — a deliberate asymmetry

The order dismisses RFCyber’s claims with prejudice but Apple’s defences without prejudice. This asymmetry is standard in plaintiff-initiated settlements: Apple retains the theoretical ability to revive its invalidity or non-infringement defences if the settlement breaks down or a related dispute arises. In practice, because RFCyber’s claims are barred, Apple’s defences are moot — but the drafting protects Apple’s position in any hypothetical future dispute involving the same patents.

Apple’s defences preserved
Cost allocation

Each party bears its own costs — a neutral signal

The court ordered that all attorneys’ fees, costs of court, and expenses be borne by each party incurring them. In US patent litigation, courts can award fees under 35 U.S.C. § 285 in ‘exceptional cases.’ The absence of any fee award to either side suggests neither party was found to have litigated in bad faith, and the mutual cost-bearing arrangement is a common term in confidential patent settlements to avoid further dispute.

No § 285 fee award
Settlement inference

Joint motion structure strongly suggests a confidential licence deal

When parties jointly move to dismiss with prejudice and bear their own costs, the standard inference is that a private settlement — typically including a licence, lump-sum payment, or cross-licence — was reached but not disclosed. The public record contains no financial terms. Given RFCyber’s patent portfolio breadth across six NFC-related patents and Apple Pay’s commercial scale, the underlying deal, if any, would carry significant economic weight, though its existence cannot be confirmed from court filings alone.

Confidential terms likely
Legal analysis based on PACER docket records for case 1:23-cv-00661 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffRFCyber, Corp.CompanyNFC/mobile payment patent holding entity — asserting 6 patents incl. US8448855B1Search in Eureka ↗
DefendantApple, Inc.CompanyApple Inc. — consumer electronics and services company, developer of Apple PaySearch in Eureka ↗
Plaintiff counselAlfred R. FabricantAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselEnrique W. IturraldeAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselJacob OstlingAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselJustine Minseon ParkAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselPeter LambrianakosAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselRaymond W. Mort , IIIAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselRichard M. CowellAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Plaintiff counselVincent J. Rubino , IIIAttorneyCounsel for RFCyber, Corp.Search in Eureka ↗
Defendant counselBenjamin YaghoubianAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselCatherine HuangAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselChris M. KatsantonisAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselErin P. GibsonAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselJessica HannahAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselJohn Michael GuaragnaAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselMark D. FowlerAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselMichael G. StrappAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselPaul R. SteadmanAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselPeter MaggioreAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselSean C. CunninghamAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselStephanie LimAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Defendant counselZachary LoneyAttorneyCounsel for Apple, Inc.Search in Eureka ↗
Presiding judgeJudge Alan D AlbrightChief JudgeTexas Western District Court — Chief JudgeSearch in Eureka ↗
Official verdict

Stipulation of dismissal — official text

“On this day, Plaintiff RFCyber Corp. (“RFCyber”) and Defendant Apple Inc. (“Apple”) announced to the Court that they have resolved RFCyber’s claims for relief against Apple asserted in this case. RFCyber and Apple have therefore requested that the Court dismiss RFCyber’s claims for relief against Apple with prejudice and Apple’s defenses against RFCyber without prejudice, and with all attorneys’ fees, costs, and expenses taxed against the party incurring the same. The Court, having considered this request, is of the opinion that their request for dismissal should be granted. IT IS THEREFORE ORDERED that RFCyber’s claims for relief against Apple are dismissed with prejudice and Apple’s defenses against RFCyber are dismissed without prejudice. IT IS FURTHER ORDERED that all attorneys’ fees, costs of court, and expenses shall be borne by each party incurring the same”
Source: PACER Docket, Case 1:23-cv-00661, Texas Western District Court · Filed January 29, 2024

The order’s asymmetric structure — RFCyber’s claims dismissed with prejudice, Apple’s defences without — reflects a jointly negotiated exit rather than a court-imposed outcome. The ‘having resolved’ language confirms the parties reached private terms before approaching the court. The mutual cost-bearing clause is consistent with a settlement in which no party formally prevailed, and forecloses any § 285 fee dispute. No findings of fact were made on infringement, validity, or claim scope for any of the six asserted patents.

PACER case 1:23-cv-00661 · Public docket record Explore in Eureka ↗
Patent at issue

US8448855B1 and 5 co-asserted NFC mobile payment patents

Publication No.US8448855B1
Application No.US13/400038
Patent details
AssigneeRFCyber, Corp.
ProductUS8448855B1 — NFC secure element mobile payment system
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

Publication No.US8118218B2
Application No.US11/534653
Patent details
AssigneeRFCyber, Corp.
ProductUS8118218B2 — NFC contactless transaction processing
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

Publication No.US10600046B2
Application No.US14/728349
Patent details
AssigneeRFCyber, Corp.
ProductUS10600046B2 — mobile payment emulation method
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

Publication No.US9240009B2
Application No.US13/350835
Patent details
AssigneeRFCyber, Corp.
ProductUS9240009B2 — NFC-based commerce and provisioning
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

Publication No.US11018724B2
Application No.US13/782948
Patent details
AssigneeRFCyber, Corp.
ProductUS11018724B2 — host card emulation for mobile payments
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

Publication No.US9189787B1
Application No.US13/903420
Patent details
AssigneeRFCyber, Corp.
ProductUS9189787B1 — secure NFC payment architecture
Publication typeB2 — grant (with prior publication)
Cited in actionSeptember 7, 2021

RFCyber’s six asserted patents span a family of inventions covering NFC-based mobile payment systems, secure element provisioning, contactless transaction emulation, and related mobile commerce infrastructure. The earliest application, US8118218B2 (application US11/534653), dates to technology conceived in the mid-2000s — predating the mass commercialisation of tap-to-pay services. The patents collectively address how a mobile device authenticates, emulates a payment card, and transacts securely over short-range wireless links, the core technical stack underlying Apple Pay.

For the contactless payment industry, this portfolio represents a meaningful prior-art and claim-scope risk. The patents span both hardware-bound secure element approaches and software-layer emulation — meaning they potentially cover a wide range of implementation architectures. Any OEM, payment network, or transit operator deploying NFC payment acceptance should assess claim overlap with this family, particularly given that no court has ever publicly construed the key claim terms, leaving scope uncertainty intact.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO analysis against RFCyber’s NFC payment patent portfolio?

If your product or platform involves NFC-based mobile payments, contactless card emulation, secure element provisioning, or tap-to-pay infrastructure, RFCyber’s six-patent portfolio is a direct FTO concern. The fact that these patents survived nearly 2.5 years of litigation against Apple — without public invalidation — suggests they present real claim scope. Android OEM handset makers, payment processors, transit card operators, and fintech platforms deploying host card emulation are especially exposed.

PatSnap Eureka’s FTO Search Agent allows you to map your product’s technical architecture against the independent claims of each RFCyber patent, flag overlap risk, and monitor for continuation filings or new assertions in the same family. Given the absence of any public Markman ruling in this case, Eureka’s claim-parsing tools can help you build your own internal claim construction baseline and track any post-grant proceedings that may narrow or confirm claim scope.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US8448855B1 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar NFC and mobile payment patent infringement cases in US courts

PatSnap Eureka tracks related litigation across truck body equipment, vehicle accessories, and comparable infringement actions in the Georgia district system.

🔍
Access 40+ similar cases in PatSnap Eureka
RFCyber, Corp. patent enforcement history, Texas Western case history, RFCyber, Corp.’s full IP portfolio, and comparable case analysis
RFCyber v. Google LLCNFC Tech v. HTC AmericaSmartflash v. Apple (W.D. Tex.)Joao Control v. Apple Pay NFC
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the NFC and mobile payments IP landscape

Six asserted patents, a high-profile defendant, and a quiet exit. Here is what the RFCyber–Apple outcome means for IP strategy in contactless payments.

NFC payment patent portfolios remain a credible enforcement threat

RFCyber sustained litigation against one of the most resource-rich defendants in US patent law for nearly 2.5 years without a public invalidation of any asserted patent. That survival alone signals that the underlying NFC and secure element patent claims carry sufficient claim scope to resist early dispositive challenges — a warning for any company deploying contactless payment technology.

W.D. Texas remains a strategic forum for NPE payment patent cases

Chief Judge Albright’s docket continues to attract high-value NPE filings in fintech and mobile technology. Companies in the Apple Pay, Google Wallet, and tap-to-pay ecosystem should monitor new filings in this court as early indicators of enforcement campaigns targeting NFC infrastructure patents — especially those covering secure element emulation and host card emulation architectures.

🔒
Full strategic analysis in PatSnap Eureka
Includes sector IP trends, Judge Treadwell’s case history, and FTO risk assessment for the truck equipment space
Portfolio assertion risk scoreComparable NFC NPE verdictsApple Pay claim overlap map
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

RFCyber v Apple — key questions answered

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

Run your own NFC patent freedom-to-operate analysis

PatSnap Eureka’s FTO Search Agent maps your product architecture against active NFC and mobile payment patents — including RFCyber’s portfolio. Set up claim monitoring to catch continuation filings before they become litigation risk.

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

Help us improve this page

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