throbber
Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 1 of 8
`
`
`RFCYBER CORP.,
`
`Plaintiff,
`
`v.
`
`VISA U.S.A. INC.,
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION

`

`Case No. 6:22-cv-00697-ADA

`
`JURY TRIAL DEMANDED


`






`
`PLAINTIFF RFCYBER CORP.’S OPPOSITION TO
`DEFENDANT VISA U.S.A. INC.’S
`MOTION TO DISMISS RFCYBER CORP.’S
`COMPLAINT FOR PATENT INFRINGEMENT (DKT. 7)
`
`Defendant.
`
`
`
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 2 of 8
`
`TABLE OF CONTENTS
`
`Page(s)
`
`BACKGROUND ................................................................................................................ 1
`
`LEGAL STANDARD ......................................................................................................... 1
`
`THE COURT SHOULD GRANT A DISCRETIONARY EXTENSION OF
`TIME FOR SERVICE ........................................................................................................ 2
`
`
`I.
`
`II.
`
`III.
`
`IV.
`
`CONCLUSION ................................................................................................................... 4
`
`
`
`i
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 3 of 8
`
`
`
`Cases
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`DatRec, LLC v. AllegianceMD Software, Inc.,
`No. 21-CV-543-TCK-JFJ, 2022 WL 2758527 (N.D. Okla. July 14, 2022) ..............................3
`
`Henderson v. United States,
`517 U.S. 654 (1996) ...................................................................................................................1
`
`John W. Stone Oil Distrib., LLC v. PBI Bank, Inc.,
`No. 3:09-CV-862-H, 2010 WL 3221800 (W.D. Ky. 2010) .......................................................3
`
`Millan v. USAA GIC,
`546 F.3d 321 (5th Cir. 2008) .....................................................................................................2
`
`Statutes
`
`35 U.S.C. § 286 ................................................................................................................................2
`
`Other Authorities
`
`Fed. R. Civ. P. 4(m) .................................................................................................................1, 2, 3
`
`Fed. R. Civ. P. 12(b)(5)....................................................................................................................2
`
`
`ii
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 4 of 8
`
`Visa U.S.A. Inc. (“Visa” or “Defendant”) was served with the Complaint on October 27,
`
`2022. Defendant waited three weeks after service, until November 17, 2022, to file the instant
`
`motion requesting dismissal of the case due to a mere 31-day delay in service, which Visa does
`
`not even allege was prejudicial. Dismissing the case without prejudice now, months after service
`
`has been effectuated, would merely delay proceedings, unnecessarily increase work, time, and
`
`expenses for the Court and Parties by having to redo service and filings under a new caption, and
`
`would go against the intention of Federal Rule of Civil Procedure 4(m) of promoting efficient
`
`litigation.
`
`I.
`
`BACKGROUND
`
`RFCyber Corp. (“RFCyber” or “Plaintiff”) filed its Complaint against Visa on June 28,
`
`2022. Dkt. 1. On October 27, 2022, Visa was served via its registered agent. Dkt. 6. The short
`
`delay in service was not intentional, but due to a miscommunication by Plaintiff’s counsel. On
`
`November 17, 2022, Visa filed the instant motion to dismiss.
`
`II.
`
`LEGAL STANDARD
`
`Fed. R. Civ. P. 4(m) states that “[i]f a defendant is not served within 90 days after the
`
`complaint is filed, the court—on motion or on its own after notice to the plaintiff—must dismiss
`
`the action without prejudice against that defendant or order that service be made within a specified
`
`time.” Fed. R. Civ. P. 4(m). Courts are not required to dismiss a case merely because service was
`
`outside of the 90-day window. Henderson v. United States, 517 U.S. 654, 661 (1996) (noting that,
`
`under earlier version of Rule 4(m), “the 120–day provision operates not as an outer limit subject
`
`to reduction, but as an irreducible allowance”).
`
`
`
`
`
`
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 5 of 8
`
`III. THE COURT SHOULD GRANT A DISCRETIONARY EXTENSION OF
`TIME FOR SERVICE
`
`Visa moved to dismiss this case under Fed. R. Civ. P. 12(b)(5) for failure to comply with
`
`Fed. R. Civ. P. 4(m), which requires service of the complaint within 90 days of filing. Here, Visa
`
`was served with the Complaint 31 days after the 90-day deadline imposed by Rule 4(m). The
`
`Court should grant a discretionary 31-day extension of time for service for two reasons.
`
`First, if this action is dismissed without prejudice and later refiled, Plaintiff will be
`
`statutorily barred from seeking damages for the period dating back to June 28, 2016, i.e., 6 years
`
`prior to the filing of the Complaint in this case. 35 U.S.C. § 286. The Complaint in this case does
`
`not limit the damages period, and RFCyber seeks to recover for Visa’s infringement up to the 6-
`
`year statutory maximum. The Complaint states that RFCyber “has the right to recover all damages
`
`for past, present, and future infringement of the Patents-in-Suit,” and accuses Visa products which
`
`were launched in 2013 and 2014, such as Visa Token Service and Visa Ready. Dkt. 1, ¶¶ 10, 12;
`
`Exs. 1, 2. A discretionary extension may be warranted “if the applicable statute of limitations
`
`would bar the refiled action.” Millan v. USAA GIC, 546 F.3d 321, 325 (5th Cir. 2008) (quoting
`
`Fed. R. Civ. P. 4(m) advisory committee’s note (1993)). Here, 35 U.S.C. § 286 would bar RFCyber
`
`from seeking damages back to June 28, 2016 in the refiled action. As such, a discretionary
`
`extension is warranted.
`
`Second, Visa has been properly served for some time and was not prejudiced in any way
`
`by the short delay in service. RFCyber’s delay was not intentional, as it was due to a
`
`miscommunication. Immediately upon recognizing the issue, RFCyber properly served Visa. The
`
`31-day delay was not inordinate, and Visa has now been properly served for seven weeks. It would
`
`be markedly inefficient to dismiss this case now, as RFCyber would simply need to immediately
`
`refile the case and serve the complaint again.
`
`2
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 6 of 8
`
`Accordingly, under similar facts, Courts have used their discretion to grant a permissive
`
`extension of time for service and denied motions to dismiss. For example, the court in DatRec,
`
`LLC v. AllegianceMD Software, Inc., No. 21-CV-543-TCK-JFJ, 2022 WL 2758527 (N.D. Okla.
`
`July 14, 2022) addressed a motion to dismiss with nearly identical facts to those here. There, the
`
`defendant was properly served 137 days after filing, and the Court found that there was no good
`
`cause for the delay. Id. at *2. However, like the situation here, the “delay in effecting service was
`
`not inordinate, prejudicial, or intentional.” Id. Under these circumstances, the court granted a
`
`permissive extension of time and denied the motion to dismiss, stating:
`
`Dismissing this case now that Defendant is served and presumably ready to address
`the merits would do nothing to advance the efficient litigation of cases that Rule
`4(m) is intended to promote—to the contrary, it would be inefficiency of the highest
`magnitude to dismiss the case and require the parties and Court administrative staff
`start anew on under a different caption. Id.
`
`The Court should reach the same decision here. Granting Visa’s motion to dismiss now
`
`that it has been properly served for nearly two months would be highly inefficient, contrary to the
`
`intent of Rule 4(m), and it would unnecessarily impose additional work, time, and costs on the
`
`Court administrative staff and the parties. John W. Stone Oil Distrib., LLC v. PBI Bank, Inc., No.
`
`3:09-CV-862-H, 2010 WL 3221800, at *2 (W.D. Ky. 2010) (“All parties agree that Defendant has
`
`now received service of process on both the original complaint and the amended complaint. If the
`
`Court dismisses the claim without prejudice, Plaintiff will be free to re-file tomorrow and will
`
`simply re-effect service of process. . . . In the absence of prejudice to Defendant, the Court will
`
`extend the time limitation for effecting service of process through the time of actual service, which
`
`was effectuated on June 2, 2010.”).
`
`
`
`3
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 7 of 8
`
`IV. CONCLUSION
`
`Based on the above, RFCyber respectfully requests that the Court grant a discretionary
`
`extension of time for service and deny Defendant’s motion to dismiss.
`
`
`Dated: December 15, 2022
`
`
`
`
`
`Respectfully submitted,
`
`
`
`/s/ Richard M. Cowell
`Raymond W. Mort, III
`State Bar No. 00791308
`Email: raymort@austinlaw.com
`THE MORT LAW FIRM, PLLC
`100 Congress Avenue, Suite 2000
`Austin, Texas 78701
`Tel/Fax: 512-865-7950
`
`OF COUNSEL:
`Alfred R. Fabricant (pro hac vice to be filed)
`NY Bar No. 2219392
`Email: ffabricant@fabricantllp.com
`Peter Lambrianakos (pro hac vice to be filed)
`NY Bar No. 2894392
`Email: plambrianakos@fabricantllp.com
`Vincent J. Rubino, III (pro hac vice to be filed)
`NY Bar No. 4557435
`Email: vrubino@fabricantllp.com
`Richard M. Cowell (admitted pro hac vice)
`NY Bar No. 4617759
`Email: rcowell@fabricantllp.com
`FABRICANT LLP
`411 Theodore Fremd Road, Suite 206 South
`Rye, New York 10580
`Telephone: (212) 257-5797
`Facsimile: (212) 257-5796
`
`ATTORNEYS FOR PLAINTIFF
`RFCYBER CORP.
`
`
`
`
`4
`
`

`

`Case 6:22-cv-00697-ADA Document 12 Filed 12/15/22 Page 8 of 8
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that, on December 15, 2022, a true and correct copy of
`
`the above and foregoing document has been served on counsel of record via the Court’s CM/ECF
`
`system per Local Rule CV-5(a)(3).
`
`
`
`/s/ Richard M. Cowell
` Richard M. Cowell
`
`
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket