RFCyber Corp. v. Shell Information Technology International — Dismissed With Prejudice
RFCyber Corp. asserted US8448855B1 against Shell’s mobile payment app and supporting server infrastructure in the Eastern District of Texas. After 362 days of litigation before Judge Rodney Gilstrap, RFCyber voluntarily dismissed all claims with prejudice under Rule 41(a)(1)(A)(i), permanently closing the dispute.
RFCyber’s NFC payment patent claim ends permanently in E.D. Tex.
On 18 July 2024, RFCyber Corp. filed suit against Shell Information Technology International BV in the Eastern District of Texas (Case No. 2:24-cv-00549), asserting infringement of US8448855B1. The accused product was the Shell App along with the hardware and software infrastructure supporting it, including Shell servers. The case was assigned to Judge Rodney Gilstrap, one of the country’s most experienced patent trial judges, and RFCyber was represented by Fabricant LLP and Truelove Law Firm.
On 15 July 2025 — one day short of the case’s first anniversary — RFCyber filed a Notice of Voluntary Dismissal with Prejudice under Federal Rule of Civil Procedure 41(a)(1)(A)(i). Judge Gilstrap accepted and acknowledged the dismissal, confirming all claims in the member case were dismissed with prejudice and denying all outstanding relief requests as moot. A dismissal with prejudice is a final adjudication on the merits; RFCyber is permanently barred from re-asserting these claims against Shell on US8448855B1 in any future action.
The 362-day duration before voluntary dismissal suggests the parties may have reached a private resolution, though no settlement terms appear in the public record. The absence of defendant counsel filings on record is notable and may indicate Shell mounted its defence without formally appearing, or that proceedings were resolved before substantive motion practice crystallised. The precise commercial terms — if any — driving RFCyber’s decision to dismiss with prejudice remain undisclosed.
Filing to Voluntary dismissal in 362 days
362 days — slightly above median for E.D. Tex. patent cases resolved before trial
Dismissed with prejudice: what the Rule 41 filing means for both parties
Rule 41(a)(1)(A)(i): plaintiff-initiated, no court order required
Under FRCP 41(a)(1)(A)(i), a plaintiff may dismiss an action without a court order by filing a notice before the opposing party serves an answer or a motion for summary judgment. Here, RFCyber chose to dismiss with prejudice — a stricter standard than the default — meaning the court’s role was confirmatory. Judge Gilstrap accepted and acknowledged the dismissal rather than granting it, reflecting the self-executing nature of the rule.
Plaintiff-initiated final terminationWith prejudice bars any future claim on this patent against Shell
A voluntary dismissal with prejudice operates as a final judgment on the merits. RFCyber cannot re-file against Shell Information Technology International on US8448855B1 in any U.S. court. This contrasts with a dismissal without prejudice, which preserves the right to re-file. The public record does not disclose whether a settlement, licensing agreement, or other commercial arrangement drove the with-prejudice election — that distinction matters significantly for assessing Shell’s ongoing exposure.
Re-filing permanently barredShell exits without a merits ruling — but faces no further exposure on this claim
Shell Information Technology International achieves dismissal of the infringement claim without the case proceeding to claim construction, summary judgment, or trial. No liability finding was made, and no injunction or damages were awarded. However, because the dismissal is with prejudice, Shell also carries no risk of RFCyber reviving these specific claims. Any undisclosed commercial terms — such as a licence or payment — would not appear on the public docket.
No liability finding; claim extinguishedUS8448855B1 remains valid — other mobile payment operators should monitor
The dismissal does not invalidate US8448855B1. RFCyber’s patent survives fully enforceable against third parties. Companies operating NFC-based mobile payment apps, contactless loyalty platforms, or smart card transaction systems should assess their exposure to this patent, particularly given RFCyber’s history of active enforcement. A with-prejudice dismissal after nearly a full year of litigation is consistent with a confidential licence or settlement that resolved the commercial dispute without public terms.
Patent valid; third-party risk persistsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | RFCyber, Corp. | Company | Mobile payment technology licensor — holder of US8448855B1Search in Eureka ↗ |
| Defendant | Shell Information Technology International, BV | Individual | Shell Information Technology International BV — operator of the Shell App mobile payment platformSearch in Eureka ↗ |
| Plaintiff counsel | Alfred Ross Fabricant | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jacob Daniel Ostling | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Justin Kurt Truelove | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Peter Lambrianakos | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Richard Matthew Cowell | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Vincent J. Rubino , III | Attorney | Counsel for RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP | Law Firm | Representing RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP (NY) | Law Firm | Representing RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Fabricant LLP (Rye) | Law Firm | Representing RFCyber, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Truelove Law Firm | Law Firm | Representing RFCyber, Corp.Search in Eureka ↗ |
| Presiding judge | Judge Rodney Gilstrap | Judge | Texas Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The court’s order confirms a plaintiff-initiated dismissal with prejudice under Rule 41(a)(1)(A)(i), meaning no merits adjudication occurred. Judge Gilstrap’s language — ‘accepts and acknowledges’ — reflects the self-executing nature of the rule: the court had no discretion to deny the dismissal, only to record it. The denial of all pending relief as moot ensures no outstanding motions carry forward. For RFCyber, the with-prejudice election is legally significant: it forecloses any future action against Shell on this patent, suggesting the parties reached a resolution that made continued litigation unnecessary.
US8448855B1 — NFC smart card mobile payment transaction system
US8448855B1, filed under application number US13/400038, sits within the NFC and smart card emulation technology domain. The patent protects methods and systems enabling mobile devices to emulate smart card functionality for payment and transaction processing — technology directly relevant to app-based contactless payment platforms. The ‘855 patent’s B1 designation indicates it issued without any post-issuance reexamination certificate at the time of filing, and it carries the presumption of validity that attaches to all issued U.S. patents.
The strategic importance of US8448855B1 lies in its positioning at the intersection of NFC hardware, secure element management, and server-side transaction authentication — all components present in modern fuel-retail and fleet payment apps like the Shell App. As mobile payment infrastructure becomes standard across retail energy, hospitality, and transit sectors, patents covering the underlying transaction layer carry increasing enforcement value. RFCyber’s decision to target Shell’s app and supporting server infrastructure suggests the asserted claims may read broadly on cloud-assisted NFC payment architectures.
Should your product team run an FTO against US8448855B1?
Any company developing or deploying an NFC-based mobile payment app, contactless loyalty platform, or smart card emulation system for consumer or fleet use should treat US8448855B1 as a priority FTO target. RFCyber’s willingness to litigate against a multinational energy company’s payment infrastructure — and sustain that action for nearly a year — signals this is an actively enforced patent with commercial teeth. The accused product scope (app plus supporting servers) suggests the claims may extend beyond the handset to backend transaction infrastructure.
PatSnap Eureka’s FTO Search Agent can map your product’s technical architecture against the claim set of US8448855B1, identify prosecution history estoppel that may narrow infringement risk, and surface relevant prior art that could support an IPR petition if needed. For product teams building contactless payment or smart card features, an Eureka-powered claim chart and landscape report provides the evidence base your IP counsel needs to advise on design-around options or licensing posture before you receive a demand.
Run a freedom-to-operate analysis on US8448855B1 to assess your product’s exposure
Run FTO in Eureka →Similar NFC and mobile payment patent cases in E.D. Texas
Cases involving NFC smart card and mobile payment patents litigated before Judge Gilstrap and the Eastern District of Texas share procedural and strategic patterns with this RFCyber action.
What this case signals for the mobile payment patent IP landscape
RFCyber’s with-prejudice dismissal after 362 days in E.D. Tex. carries strategic signals for NFC payment operators and patent licensors alike.
E.D. Tex. remains a high-stakes venue for mobile payment patent disputes
Judge Gilstrap’s court continues to attract NFC and mobile payment infringement actions. Filing in this district signals plaintiff’s intent to litigate seriously. Defendants operating payment apps with U.S. exposure should ensure their prior art searches and FTO analyses cover the RFCyber portfolio before receiving a demand letter.
With-prejudice dismissals near trial timelines suggest undisclosed commercial resolution
When a plaintiff dismisses with prejudice after nearly a year of litigation — but before trial — the pattern is consistent with a confidential licence or settlement. For Shell, this resolves the immediate threat. For competitors operating similar payment infrastructure, it raises the question of whether RFCyber is now better resourced to pursue additional targets.
RFCyber v Shell — key questions answered
The dismissal with prejudice means RFCyber is permanently barred from asserting the same claims against Shell Information Technology International on US8448855B1. However, the patent remains fully enforceable against all other parties. RFCyber retains the right to assert US8448855B1 against any other company whose products fall within the claim scope.
The public record does not disclose the reason. A with-prejudice voluntary dismissal after nearly a year of litigation is consistent with a confidential settlement or licence agreement. It may also reflect a strategic reassessment of claim strength following discovery or early motion practice, though no dispositive motions are referenced in the available record.
RFCyber accused the Shell App and the hardware and software infrastructure supporting it, including Shell servers, of infringing US8448855B1. This broad accused product scope — covering both client-side app and backend server components — is typical of NFC payment patent assertions where the claimed invention involves server-assisted transaction authentication.
US8448855B1 is a U.S. patent filed under application number US13/400038 in the NFC and smart card emulation domain. It covers methods and systems enabling mobile devices to perform smart card-style payment and transaction functions, including interactions with backend servers. The patent is held by RFCyber Corp., which has used it in multiple infringement actions.
RFCyber was represented by Fabricant LLP (including its New York and Rye offices) and Truelove Law Firm. Plaintiff counsel included Alfred Ross Fabricant, Jacob Daniel Ostling, Justin Kurt Truelove, Peter Lambrianakos, Richard Matthew Cowell, and Vincent J. Rubino III. No defendant counsel filings appear in the available case record.
PatSnap Eureka searches patents and litigation data to answer instantly.