Prosecution Insights
Last updated: November 18, 2026
Application No. 19/203,910

COMPUTING SYSTEMS AND METHODS FOR PROTECTING APPLICATION PROGRAMMING INTERFACES WITH TWO-FACTOR AUTHENTICATION

Non-Final OA §DP
Filed
May 09, 2025
Priority
Jan 09, 2023 — continuation of 12/301,720
Examiner
CHOUDHURY, AZIZUL Q
Art Unit
2455
Tech Center
2400 — Computer Networks
Assignee
Capital One Financial Corporation
OA Round
1 (Non-Final)
77%
Grant Probability
Favorable
1-2
OA Rounds
90%
With Interview

Examiner Intelligence

Grants 77% — above average
77%
Career Allowance Rate
532 granted / 688 resolved
+19.3% vs TC avg
Moderate +13% lift
Without
With
+12.7%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
8 currently pending
Career history
708
Total Applications
across all art units

Office Action

§DP
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 . Detailed Action This office action is in response to the listing of claims filed on July 16, 2025. Claims 1-20 are currently pending. Double Patenting The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969). A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b). The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13. The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer. Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-17 of U.S. Patent No. 12,531,844. Although the claims at issue are not identical, they are not patentably distinct from each other because both sets of claims are substantially similar in their claimed approach to providing API protection using 2FA. These similarities are illustrated in the table below comparing an independent claim along with related dependent claims of the present application against a patented independent claim. Present Application Claims 1 & 6 & 7 & 8 Patent 12,531,844 Claim 1 Claim 1: A computing platform comprising: at least one network interface; at least one processor; at least one non-transitory computer-readable medium; and program instructions stored on the at least one non-transitory computer-readable medium that, when executed the at least one processor such, cause the computing platform to: cause a first end-user device associated with an application programming interface (API) provider to display a first interface for registering an API that exposes resources of the API provider and is to be protected using two-factor authentication, wherein the first interface presents a set of two or more authentication-factor options corresponding to different levels of security that are available for use as a second authentication factor of the two-factor authentication for the API; Claim 7: wherein the set of two or more authentication- factor options corresponding to the different levels of security includes two or more of (i) a first authentication-factor option comprising a JSON (JavaScript Object Notation) Web Token (JWT) that is to be signed by a shared secret, (ii) a second authentication-factor option comprising a JWT that is to be signed by a private key from a public-private key pair, and (iii) a third authentication- factor option that comprises a hash of a shared secret. A computing platform comprising: at least one network interface; at least one processor; at least one non-transitory computer-readable medium; and program instructions stored on the at least one non-transitory computer-readable medium that are executable by the at least one processor such that the computing platform is configured to: cause a first end-user device associated with an application programming interface (API) provider to display a first interface for registering an API that exposes resources of the API provider and is to be protected using two-factor authentication, wherein the first interface presents a set of options for two or more types of authentication factors that are available for use as a second authentication factor of the two-factor authentication for the API, and wherein the set of options for the two or more types of authentication factors includes two or more of (i) a first type of authentication factor comprising a JSON (JavaScript Object Notation) Web Token (JWT) that is to be signed by a shared secret, (ii) a second type of authentication factor comprising a JWT that is to be signed by a private key from a public-private key pair, and (iii) a third type of authentication factor that comprises a hash of a shared secret; Claim 1: receive, from the first end-user device associated with the API provider, registration information for the API that includes an indication of a given authentication-factor option that is selected by the API provider from the set of two or more authentication-factor options for use as the second authentication factor of the two-factor authentication for the API; receive, from the first end-user device associated with the API provider, registration information for the API that includes an indication of the API provider's selection of a given type of authentication factor that is to be used as the second authentication factor of the two-factor authentication for the API, wherein the given type of authentication factor comprises one of the first type of authentication factor, the second type of authentication factor, or the third type of authentication factor; Claim 1: cause a second end-user device associated with an API consumer to display a second interface for registering a client application that is to access resources exposed by the API; cause a second end-user device associated with an API consumer to display a second interface for registering a client application that is to access resources exposed by the API; Claim 1: receive, from the second end-user device associated with the API consumer, registration information for the client application; receive, from the second end-user device associated with the API consumer, registration information for the client application; Claim 1: register first-factor credential information for the client application that is to be utilized to perform a first-factor authentication of the client application when the client application requests access to the API, wherein registering the first-factor credential information involves (i) obtaining the first-factor credential information for the client application, (ii) presenting the first-factor credential information for the client application via the second interface, and (iii) storing the first-factor credential information for the client application; register first-factor credential information for the client application that is to be utilized to perform a first-factor authentication of the client application when the client application requests access to the API, wherein registering the first-factor credential information involves (i) obtaining the first-factor credential information for the client application, (ii) presenting the first-factor credential information for the client application via the second interface, and (iii) storing the first-factor credential information for the client application; Claim 1: and register second-factor credential information for the client application that is to be utilized to perform a second-factor authentication of the client application when the client application requests access to the API, wherein the second-factor credential information is of a type that corresponds to the given authentication-factor option that is selected by the API provider for use as the second authentication factor of the two-factor authentication for the API. Claim 6: wherein the second-factor credential information is vaultless. Claim 8: wherein the given authentication-factor option that is selected by the API provider comprises a JSON (JavaScript Object Notation) Web Token (JWT) that is to be signed by a shared secret, and wherein the program instructions that, when executed by the at least one processor, cause the computing platform to register the second-factor credential information for the client application comprise program instructions that, when executed by the at least one processor, cause the computing platform to: obtain a first shared secret for the client application that is to be utilized by the client application to generate a JWT that is signed by the first shared secret; present the first shared secret for the client application via the second interface; and after presenting the first shared secret for the client application, discard the first shared secret rather than storing the first shared secret for future use during two-factor authentication of the client application. and register vaultless second-factor credential information for the client application that is to be utilized to perform a second-factor authentication of the client application when the client application requests access to the API, wherein the vaultless second-factor credential information is of a type that corresponds to the API provider's selection of the given type of authentication factor that is to be used as the second authentication factor of the two-factor authentication for the API, and wherein registering the vaultless second-factor credential information involves: if the given type of authentication factor comprises the first type of authentication factor, (i) obtaining a first shared secret for the client application that is to be utilized by the client application to generate a JWT that is signed by the first shared secret, (ii) presenting the first shared secret for the client application via the second interface, and (iii) after presenting the first shared secret for the client application, discarding the first shared secret rather than storing the first shared secret for future use during two-factor authentication of the client application; if the given type of authentication factor comprises the second type of authentication factor, obtaining and storing a public key for the client application without obtaining or storing a corresponding private key for the client application that is to be utilized by the client application to generate a JWT that is signed by the private key; or if the given type of authentication factor comprises the third type of authentication factor, (i) obtaining a second shared secret for the client application that is to be utilized by the client application to generate a hash of the second shared secret for the client application, (ii) presenting the second shared secret for the client application via the second interface, and (iii) after presenting the second shared secret for the client application, discarding the second shared secret rather than storing the second shared secret for future use during two-factor authentication of the client application. While both sets of claims are substantially similar in their claimed approach to protecting APIs with 2FA authentication, the present invention’s independent claims do not explicitly cite the second-factor credential being vaultless, or various support for JSON and JWT. However, the dependent claims do support such features, including at least dependent claims 6-8. By supporting vaultless second-factor credentials, JSON, and JWT, API can be better protected (for instance by storing credentials in a decentralized manner). Therefore it would have been obvious to one skilled in the art, before the effective filing date to have incorporated the dependent claims’ features of vaultless credentials, JSON, and JWT to provide stronger API protections. Claims 2-20 are similarly rejected for being substantially similar to patented claims 2-17. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to AZIZUL Q CHOUDHURY whose telephone number is (571)272-3909. The examiner can normally be reached M-F. 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, EMMANUEL MOISE can be reached at (571) 272-3865. 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. /AZIZUL CHOUDHURY/Primary Examiner, Art Unit 2455
Read full office action

Prosecution Timeline

May 09, 2025
Application Filed
Sep 17, 2026
Non-Final Rejection mailed — §DP (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12792423
Role-Based Storage Service Management
2y 11m to grant Granted Nov 10, 2026
Patent 12771529
AUTHENTICATION TUNNELING MECHANISMS FOR REMOTE CONNECTIONS
3y 0m to grant Granted Oct 20, 2026
Patent 12763979
HEADERS CLIENT FOR DETERMINING THE BEST CHAIN
3y 2m to grant Granted Oct 13, 2026
Patent 12756684
ADDRESSING TEST METHODS AND APPARATUSES, STORAGE MEDIA, AND ELECTRONIC DEVICES
1y 10m to grant Granted Oct 06, 2026
Patent 12744769
DATA AUTHENTICATION IN DISTRIBUTED NETWORKS
2y 10m to grant Granted Sep 22, 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

1-2
Expected OA Rounds
77%
Grant Probability
90%
With Interview (+12.7%)
Low
PTA Risk
Based on 688 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