Prosecution Insights
Last updated: November 22, 2026
Application No. 19/278,578

SYSTEMS AND METHODS FOR EXTENDING AUTHENTICATION

Final Rejection §101
Filed
Jul 23, 2025
Priority
Aug 12, 2024 — provisional 63/682,305
Examiner
CHAKRAVARTI, ARUNAVA
Art Unit
3692
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Mastercard International Incorporated
OA Round
2 (Final)
10%
Grant Probability
At Risk
3-4
OA Rounds
2y 9m
Est. Remaining
23%
With Interview

Examiner Intelligence

Grants only 10% of cases
10%
Career Allowance Rate
41 granted / 426 resolved
-42.4% vs TC avg
Moderate +14% lift
Without
With
+13.6%
Interview Lift
resolved cases with interview
Typical timeline
4y 1m
Avg Prosecution
27 currently pending
Career history
472
Total Applications
across all art units

Statute-Specific Performance

§101
44.3%
+4.3% vs TC avg
§103
42.6%
+2.6% vs TC avg
§102
0.7%
-39.3% vs TC avg
§112
10.4%
-29.6% vs TC avg
Black line = Tech Center average estimate • Based on career data from 426 resolved cases

Office Action

§101
DETAILED ACTION Status of Claims 1. This office action is in response to application filed 10/9/2026. 2. Claims 1-5, 7-11, 13, 14, 16, 17 are pending. Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Claim Rejections - 35 USC § 101 35 U.S.C. 101 reads as follows: Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title. Claims 1-5, 7-11, 13, 14, 1617 Claims 1-5, 7-11, 13, 14, 16, 17 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception (i.e., a law of nature, a natural phenomenon, or an abstract idea) without significantly more. Step 1: Claims 1-7 are directed to a method; claims 8-12 are directed to a non-transitory, computer-readable medium; claims 13-17 are directed to a system – each of which is one of the statutory categories of inventions. Step 2A: A claim is eligible at revised Step 2A unless it recites a judicial exception and the exception is not integrated into a practical application of the application. Prong 1: Prong One of Step 2A evaluates whether the claim recites a judicial exception (an abstract idea enumerated in the 2019 PEG, a law of nature, or a natural phenomenon). Groupings of Abstract Ideas: I. MATHEMATICAL CONCEPTS A. Mathematical Relationships B. Mathematical Formulas or Equations C. Mathematical Calculations II. CERTAIN METHODS OF ORGANIZING HUMAN ACTIVITY A. Fundamental Economic Practices or Principles (including hedging, insurance, mitigating risk) B. Commercial or Legal Interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations) C. Managing Personal Behavior or Relationships or Interactions between People (including social activities, teaching, and following rules or instructions) III. MENTAL PROCESSES. Concepts performed in the human mind (including an observation, evaluation, judgment, opinion). See MPEP 2106.04 (a) (2) Abstract Idea Groupings [R-10.2019] The limitations recited in independent clams 1, and 8 – during a checkout session for a website of a first party computing device at a mobile device specific to a user, where the checkout session is associated with a reference session ID: in response to receiving a look-up request from the [first party computing device], confirming a user profile for the user and an existing passkey for the user profile and a mobile device associated with the user; initiating, by a [service provider computing device], a passkey authentication of the user, through a [fast identity online (FIDO) server] at the [mobile device], the service provider computing device being separate from the FIDO server and the first party computing device; receiving, by the [service provider computing device], a proof of authentication for the user from the FIDO server, whereby the proof of authentication is associated with the reference session ID; providing, by the [service provider computing device], the proof of authentication to the first party computing device; receiving, by the [service provider computing device], an instruction to initiate checkout from the first party computing device, the instruction including a session ID; validating, by the [service provider computing device], the proof of authentication based on the session ID being the same as the reference session ID and being received within an expiration interval of the proof of authentication, without a further passkey authentication of the user; compiling, by the [service provider computing device], an authentication payload based on the validated proof of authentication; and returning the authentication payload to the first party computing device, in response to the instruction to initiate checkout. – constitute Fundamental Practices or Principles and/or Commercial/Legal Interactions and hence fall under the abstract idea category Certain Methods of Organizing Human Activity. The limitations recited in independent claim 13 – in response to receiving a look-up request from the first party computing device, confirm a user profile for the user and an existing passkey for the user profile and a mobile device associated with the user; initiate a passkey authentication of the user, through the FIDO server at the mobile device, the service provider computing device being separate from the FIDO server and the first party computing device; wherein the FIDO server is configured, by second executable instructions, to: issue a challenge to the mobile device; verify a signed challenge from the mobile device, based on a public key specific to the mobile device; and in response to the signed challenge being successfully verified, provide a proof of authentication for the user to the service provider computing device; and then wherein the service provider computing device is configured, by the first executable instructions, to: associate the proof of authentication to the reference session ID; provide the proof of authentication to the first party computing device; receive an instruction to initiate checkout from the first party computing device, the instruction including a session ID; validate the proof of authentication based on the session ID being the same as the reference session ID and being received within an expiration interval of the proof of authentication, without a further passkey authentication of the user; compile an authentication payload based on the validated proof of authentication; and return the authentication payload to the first party computing device, in response to the instruction to initiate checkout – also constitute Fundamental Practices or Principles and/or Commercial/Legal Interactions and hence fall under the abstract idea category Certain Methods of Organizing Human Activity. The limitations recited in the dependent claims – (Claims 2, 9) [wherein the service provider computing device is configured to communicate with the first party computing device through one of a software-development kit (SDK) integrated with the website of the first party computing device or an application programming interface (API) accessed by the first party computing device] (Claim 3) wherein the look-up request includes a phone number of the mobile device. (Claims 4, 10) receiving, by the service provider computing device, a request to retrieve the user profile; retrieving one or more enrolled accounts for the user profile; returning, by the service provider computing device, the user profile and the retrieved enrolled accounts to the first party computing device, prior to receiving the instruction to initiate checkout; and wherein the instruction to initiate checkout includes a selection of one of the one or more enrolled accounts. (Claim 5) wherein validating the proof of authentication includes: validating a device ID of the mobile device to the user profile based on historical transaction, through the service provider computing device. (Claim 7) wherein the service provider computing device and the FIDO server are included in a processing network. (Claim 11) in validating the proof of authentication, to: validate a device ID of the mobile device to the user profile based on historical transaction. (Claim 12) in validating the proof of authentication, to: validating an expiration interval for the proof of authentication is not expired. (Claim 14) in validating the proof of authentication, to: validate a device ID of the mobile device to the user profile based on historical transactions, through the service provider computing device. (Claim 16) wherein the proof of authentication is an authentication token. (Claim 17) wherein the service provider computing device and the FIDO server are included in a processing network. – also fall under Certain Methods of Organizing Human Activity. Hence under Prong One of Step 2A, claims 1-5, 7-11, 13, 14, 16, 17 recite a judicial exception. Prong 2: Prong Two of Step 2A evaluates whether the claim recites additional elements that integrate the judicial exception into a practical application of the exception. Limitations the courts have found indicative that an additional element (or combination of elements) may have integrated the exception into a practical application include: An improvement in the functioning of a computer, or an improvement to other technology or technical field, as discussed in MPEP §§ 2106.04(d)(1) and 2106.05(a); Applying or using a judicial exception to effect a particular treatment or prophylaxis for a disease or medical condition, as discussed in MPEP § 2106.04(d)(2); Implementing a judicial exception with, or using a judicial exception in conjunction with, a particular machine or manufacture that is integral to the claim, as discussed in MPEP § 2106.05(b); Effecting a transformation or reduction of a particular article to a different state or thing, as discussed in MPEP § 2106.05(c); and Applying or using the judicial exception in some other meaningful way beyond generally linking the use of the judicial exception to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception, as discussed in MPEP § 2106.05(e). The courts have also identified limitations that did not integrate a judicial exception into a practical application: Merely reciting the words “apply it” (or an equivalent) with the judicial exception, or merely including instructions to implement an abstract idea on a computer, or merely using a computer as a tool to perform an abstract idea, as discussed in MPEP § 2106.05(f); Adding insignificant extra-solution activity to the judicial exception, as discussed in MPEP § 2106.05(g); and Generally linking the use of a judicial exception to a particular technological environment or field of use, as discussed in MPEP § 2106.05(h). Additional elements recited by the claims, beyond the abstract idea, include: first party computing device (102); mobile device (106); fast identity online (FIDO) server (114); service provider computing device (112); SDK integrated with website of first party computing device; API accessed by the first party computing device. Examiner finds that any additional element(s), beyond the judicial exception, has been recited at a high level of generality such that the claim limitations amount to no more than mere instructions to apply the exception using generic components (see MPEP 2106.05(f)) or insignificant data gathering activities (see MPEP 2106.05(g)). The combination of additional elements does not purport to improve the functioning of a computer or effect an improvement in any other technology or technical field. Instead, the additional elements do no more than use the computer as a tool and/or link the use of the judicial exception to a particular technological environment or field of use. The focus of the claims is not on improvement in computers, but on certain independently abstract ideas – during a checkout session for a website of a first party computing device at a mobile device specific to a user, where the checkout session is associated with a reference session ID: in response to receiving a look-up request from the [first party computing device], confirming a user profile for the user and an existing passkey for the user profile and a mobile device associated with the user; initiating, by a [service provider computing device], a passkey authentication of the user, through a [fast identity online (FIDO) server] at the [mobile device], the service provider computing device being separate from the FIDO server and the first party computing device; receiving, by the [service provider computing device], a proof of authentication for the user from the FIDO server, whereby the proof of authentication is associated with the reference session ID; providing, by the [service provider computing device], the proof of authentication to the first party computing device; receiving, by the [service provider computing device], an instruction to initiate checkout from the first party computing device, the instruction including a session ID; validating, by the [service provider computing device], the proof of authentication based on the session ID being the same as the reference session ID and being received within an expiration interval of the proof of authentication, without a further passkey authentication of the user; compiling, by the [service provider computing device], an authentication payload based on the validated proof of authentication; and returning the authentication payload to the first party computing device, in response to the instruction to initiate checkout. – that merely use generic computers as tools. Steps that do no more than spell out what it means to “apply it on a computer” cannot confer patent eligibility. Indeed, nothing in claim 1 improves the functioning of the computer, makes it operate more efficiently, or solves any technological problem. See Trading Techs. Int’l, Inc. v. IBG LLC, 921 F.3d 1378, 1384-85 (Fed. Cir. 2019). Hence, under Prong Two of Step 2A, the additional elements, when considered individually or in combination, do not integrate the judicial exception into a practical application. Hence, the claims are ineligible under Step 2A. Step 2B: In Step 2B, the evaluation consists of whether the claim recites additional elements that amount to an inventive concept (aka “significantly more”) than the recited judicial exception. As discussed in Prong Two, the additional elements in the claims amount to no more than mere instructions to apply the exception using generic components. When considered individually or as an ordered combination, the additional elements fail to transform the abstract idea of – during a checkout session for a website of a first party computing device at a mobile device specific to a user, where the checkout session is associated with a reference session ID: in response to receiving a look-up request from the [first party computing device], confirming a user profile for the user and an existing passkey for the user profile and a mobile device associated with the user; initiating, by a [service provider computing device], a passkey authentication of the user, through a [fast identity online (FIDO) server] at the [mobile device], the service provider computing device being separate from the FIDO server and the first party computing device; receiving, by the [service provider computing device], a proof of authentication for the user from the FIDO server, whereby the proof of authentication is associated with the reference session ID; providing, by the [service provider computing device], the proof of authentication to the first party computing device; receiving, by the [service provider computing device], an instruction to initiate checkout from the first party computing device, the instruction including a session ID; validating, by the [service provider computing device], the proof of authentication based on the session ID being the same as the reference session ID and being received within an expiration interval of the proof of authentication, without a further passkey authentication of the user; compiling, by the [service provider computing device], an authentication payload based on the validated proof of authentication; and returning the authentication payload to the first party computing device, in response to the instruction to initiate checkout. – into significantly more. See MPEP 2106.05(f) Mere Instructions To Apply An Exception [R-10.2019]. (2) Whether the claim invokes computers or other machinery merely as a tool to perform an existing process. Use of a computer or other machinery in its ordinary capacity for economic or other tasks (e.g., to receive, store, or transmit data) or simply adding a general purpose computer or computer components after the fact to an abstract idea (e.g., a fundamental economic practice or mathematical equation) does not integrate a judicial exception into a practical application or provide significantly more. Hence, the claims are ineligible under Step 2B. Therefore, the claim(s) are rejected under 35 U.S.C. 101 as being directed to a judicial exception without significantly more. Response to Arguments Applicant's arguments filed 10/9/2026 have been fully considered but they are not persuasive. 101 Applicant argues that the claims provide technical solution a technical problem in the field of user authentication by extending authentication of the user for the duration of the session, in which the user authenticated, through session ID and validation. The Applicant disputes the rejection of the claims as being directed to Fundamental Economic Practice or any economic function. Examiner respectfully disagrees. The recited steps of independent claim 1 – initiating passkey authentication [at a FIDO server]; receiving proof of authentication [from FIDO server]; providing proof of authentication [to first party computing device]; and validating [by service provider computing device] the proof of authentication based on session ID [received by first party computing device] being the same as reference session ID, within an expiration interval of proof of authentication, without further passkey authentication – constitute risk management exercise(s) that ensure that the user is authentic and the session is the reference checkout session. Similarly, issuing a signed challenge and verifying a signed challenge (claim 13) – also constitutes risk management verification method. The Applicant cannot reasonably deny that the steps mitigating transaction risk by verifying a user or user session is a fundamental economic practice in modern commerce. See MPEP 2106.04(a)(2) II. CERTAIN METHODS OF ORGANIZING HUMAN ACTIVITY A. Fundamental Economic Practices or Principles (“The term “fundamental” is not used in the sense of necessarily being “old” or “well-known.” See, e.g., OIP Techs., Inc. v. Amazon.com, Inc., 788 F.3d 1359, 1364, 115 U.S.P.Q.2d 1090, 1092 (Fed Cir. 2015) (a new method of price optimization was found to be a fundamental economic concept)”). See also Subject Matter Eligibility Examples: Business Methods, December 2016, Page 9 (“fraud prevention by identity verification before proceeding with a banking transaction, which as explained above is a fundamental business practice.”). Examiner also points out that the limitations – receiving [by the service provider computer] an instruction to initiate checkout [from the first party computing device]; compiling [by the service provider computer computing device] an authentication payload based on validate proof of authentication; and returning the authentication payload [to the first party computing device] in response to the instruction to initiate checkout – constitute Commercial/Legal Interactions. The additional elements – first party computing device (102); mobile device (106); fast identity online (FIDO) server (114); service provider computing device (112); SDK integrated with website of first party computing device; API accessed by the first party computing device – are merely invoked as tools to carry out the commercial activity of initiating a checkout from the website of the first party computing device, authenticating the user, and validating the proof of authentication. But for the additional elements, each of the limitations of the independent claims constitute Fundamental Practices or Principles and/or Commercial/Legal Interactions and hence fall under the abstract idea category Certain Methods of Organizing Human Activity. Therefore, the limitations of independent claim 1 collectively fall under the abstract idea grouping Certain Methods of Organizing Human Activity. Examiner also points out that passkeys were introduced in 2022 when Apple, Google, and Microsoft jointly announced support for FIDO-based multi-device credentials, with the FIDO Alliance officially embracing the term “passkey” for all passwordless FIDO credentials by 2023. See NPL What is a Passkey. See also NPL FIDO Deploying Passkeys in the Enterprise by the FIDO Alliance. The claimed invention merely makes use of passkeys as passwordless verification credential for authenticating user during a checkout transaction. Applicant’s invention is not directed to a technical problem. User checkout is a commercial interaction. User authentication and session validation are risk management measures inherent in online commerce. Nor has the application invented new authentication or verification technology. Passkeys are public domain authentication protocol backed by Apple, Google and Microsoft. For the above reasons, the Applicant’s assertion that the claims provide technical solution to a technical problem – is not persuasive. Applicant compares the pending claims to McRO, DDR but the Examiner finds no similarity between the present claims directed to initiate a checkout by validating proof of identification based on reference session ID with improved rules to achieve accurate and realistic lip synchronization and facial expressions in animated characters (McRO) or the use of hybrid web page to merge third party content with host website (DDR). The present claims are also dissimilar from Example 35 which deals with customer verification at an ATM by an unconventional process including the ATM’s provision of a random code, the mobile communication device’s generation of the image having encrypted code data in response to the random code, the ATM’s decryption and analysis of the code data, and the subsequent determination of whether the transaction should proceed based on the analysis of the code data. In contrast, the present claims are primarily directed to a website checkout where the user is authenticated using existing passkey by a FIDO server and the proof of authentication is then used to initiate the checkout. The former is a hypothetical example used by the office to indicate an unconventional authentication protocol. In contrast, the present claims utilize already invented authentication technologies including passkeys and FIDO server to authentication user session. Applicant also compares the claims to Example 35, Finjan, and Uniloc. Examiner finds the analogy unpersuasive. In Finjan, the Court held that claims to a “behavior-based virus scan” were a specific improvement in computer functionality and hence not directed to an abstract idea. 879 F.3d at 1304. The claimed technique of scanning enabled “more flexible and nuanced virus filtering” and detection of potentially dangerous code. Id. This was done by “scanning a downloadable and attaching the results of that scan to the downloadable itself in the form of a ‘security profile.’” Id. At 1303. The security profile included the information about potentially hostile operations produced by a “behavior-based” virus scan, as distinguished from traditional, “code-matching” virus scans that are limited to recognizing the presence of previously-identified viruses, typically by comparing the code in a downloadable to a database of known suspicious code. Id. at 1304. This behavior-based scan was a new type of file that when attached to a downloadable allowed the computer to do more to protect itself than in the past. The instant claims however present no such new type of processing to create a file that improves computer performance. Instead, the pending claims employ known verification technologies for verifying the authenticity of the user and the checkout session may improve the security of the checkout session, but this is not an improvement to the computer. The Uniloc claims covered a method for communication between a primary station and secondary stations (like a Bluetooth mouse, keyboard, or controller). In Uniloc the Federal Circuit found that claim 1 of the ’578 patent “is directed to a particular way of using a conventional application server to nevertheless allow on-demand installation of an application incorporating preferences from two different sources by adding the application manager and configuration manager as additions to each application.” Uniloc, 772 F. App’x at 898. “The two specific added components do not merely fulfill their ordinary roles—their use together on an application server represents a different way of achieving the improvement claimed in the ’578 patent.” In contrast, the method of claim 15 recites no such path or routing of data between computer system architecture components. Unlike Uniloc which is directed to broadcasting messages between a primary station and a secondary station, the pending claims are directed to initiating a checkout. There is no improvement in the present claims that is comparable to reduction in latency arising in the realm of computer networks. Use of passkey based proof of authentication for initiating a checkout is not comparable to reduction of latency between network stations. Hence, this analogy is inapposite. The claim limitations do not recite (i) an improvement to the functionality of a computer or other technology or technical field; (ii) a “particular machine” to apply or use the judicial exception; (iii) a particular transformation of an article to a different thing or state; or (iv) any other meaningful limitation. (See MPEP 2106.05(a)-(c), (e)-(h)). Hence, the additional elements fail to integrate the abstract idea into a practical application. 103 The previous obviousness rejection has been withdrawn based on the amendments and arguments filed 10/9/2026. Conclusion Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Any inquiry concerning this communication or earlier communications from the examiner should be directed to ARUNAVA CHAKRAVARTI whose telephone number is (571)270-1646. The examiner can normally be reached 9 AM - 5 PM ET. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ryan Donlon can be reached at 571-270-3602. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /ARUNAVA CHAKRAVARTI/Primary Examiner, Art Unit 3692
Read full office action

Prosecution Timeline

Jul 23, 2025
Application Filed
Jul 14, 2026
Non-Final Rejection mailed — §101
Oct 09, 2026
Response Filed
Nov 10, 2026
Final Rejection mailed — §101 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12784106
SENTIMENT BASED ENHANCEMENT OF INVESTOR RELATIONS COMMUNICATION
2y 10m to grant Granted Nov 03, 2026
Patent 12725159
METHODS AND SYSTEMS FOR IDENTIFYING A RE-ROUTED TRANSACTION
4y 8m to grant Granted Sep 01, 2026
Patent 12646111
SYSTEM AND METHOD FOR EXECUTING SYNCHRONIZED MESSAGES IN MULTIPLE GEOGRAPHICALLY DISTRIBUTED SERVERS
4y 7m to grant Granted Jun 02, 2026
Patent 12561676
SYSTEMS AND METHODS FOR IMPROVING DATA PROCESSING AND MANAGEMENT
10y 10m to grant Granted Feb 24, 2026
Patent 12541747
METHOD AND APPARATUS FOR CONDUCTING SECURE FINANCIAL AND INFORMATIONAL TRANSACTIONS VIA PORTABLE SMART DEVICES
2y 1m to grant Granted Feb 03, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
10%
Grant Probability
23%
With Interview (+13.6%)
4y 1m (~2y 9m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 426 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month