Prosecution Insights
Last updated: November 18, 2026
Application No. 18/670,330

SOFTWARE APPLICATION FOR PERFORMING CERTIFICATION TESTING OF PAYMENT TERMINALS

Non-Final OA §101
Filed
May 21, 2024
Priority
Apr 02, 2024 — provisional 63/573,356
Examiner
KANERVO, VIRPI H
Art Unit
3691
Tech Center
3600 — Transportation & Electronic Commerce
Assignee
Capital One Financial Corporation
OA Round
3 (Non-Final)
48%
Grant Probability
Moderate
3-4
OA Rounds
95%
With Interview

Examiner Intelligence

Grants 48% of resolved cases
48%
Career Allowance Rate
271 granted / 569 resolved
-4.4% vs TC avg
Strong +48% interview lift
Without
With
+47.7%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
18 currently pending
Career history
614
Total Applications
across all art units

Office Action

§101
DETAILED ACTION 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 . Status of the Claims Claims 1-4, 6, 8-14, 17-18, and 21-26, are presented for examination. Applicant filed a request for continuous examination (RCE) on 05/18/2026 amending claims 1-4, 6, 8-14, 17-18, 21-22, and 25; and adding new claim 26. In light of Applicant’s amendment, Examiner has withdrawn the previous objections and § 101 rejection. Examiner has, however, established new objection for claim 11; and new § 101 rejection for claims 1-4, 6, 8-14, 17-18, and 21-26, in the instant Office action. Examiner’s Remarks Patent Eligibility under § 101: Applicant argues in pages 14-17 of Applicant’s Remarks: First, Applicant respectfully submits that amended independent claims 1, 11, and 17 do not recite a fundamental economic principle or practice, which is the grouping of abstract ideas identified in the Office Action under Step 2A, Prong One. To the contrary, amended independent claims 1, 11, and 17 each recite a "client device" installed with a specific "software application" for selectively configuring the "client device" into either (i) "a first operating mode in which the client device emulates a physical payment card in accordance with a virtual test card profile" or (ii) "a second operating mode in which the client device configures a physical payment card to operate in accordance with the virtual test card profile." Further, each of the functional elements of amended independent claims 1, 11, and 17 recite functionality that is specific to the operation of the "client device" installed with the claimed "software application," rather than any fundamental economic principle or practice. Second, Applicant respectfully submits that amended independent claims 1, 11, and 17 are patent eligible under Step 2A, Prong Two of the Office's § 101 framework, which provides that a claim is patent eligible under § 101 if it integrates the alleged abstract idea into a practical application. As the M.P.E.P. explains, one way that a claim can integrate an abstract idea into a practical application under Step 2A, Prong Two is by providing an improvement in the functioning of a computer or any other technology or technical field. See M.P.E.P. § 2106.04(d)(1). The M.P.E.P. defines the framework for evaluating whether a claim provides an improvement in the functioning of a computer or any other technology or technical field. . . . [T]he disclosed software technology advantageously integrates multiple different sets of functionality related to certification testing into a single software application - including card emulation functionality, physical-card loading functionality, and test data logging functionality, all of which may be caried out based on a common set of virtual test card profiles that are loaded by the software application. In this way, the disclosed software technology enhances the user experience of individuals that are tasked with carrying out certification testing and improves upon existing software applications that only provide a limited set of functionality related to certification testing - such as software applications that allow for capturing of test data but do not provide card emulation functionality or physical-card loading functionality. Third, even if amended independent claims 1, 11, and 17 were not found to be eligible under Step 2A of the Office's § 101 framework, Applicant respectfully submits that the combination of additional elements recited by amended independent claims 1, 11, and 17, when taken together, supply an inventive concept that amounts to significantly more than any alleged abstract idea that is recited in the claims under Step 2B of the Office's § 101 framework. Examiner respectfully disagrees. First, Applicant’s invention belongs to the group of certain methods of organizing human activity (i.e., fundamental economic principles or practices including mitigating risk). This Is demonstrated by Applicant’s Specification that recites: [0041] As demonstrated by the foregoing discussion, merchant systems play a critical role in the processing of transactions involving payment cards, and as such, it is important to all involved parties (e.g., cardholders, merchants, acquirer banks, issuer banks, etc.) that merchant systems are operating properly. For instance, if a payment terminal such as a contact-based or contactless card reader does not interact properly with other components involved in the end-to-end authorization process for a payment transaction, such as a payment card, a merchant’s computing system, a bank’s computing platform, and/or a payment processor’s computing platform, then this may lead to various problems, including but not limited to processing errors and security issues. [0042] For these and other reasons, payment terminals typically must undergo certification testing before they can be used to initiate the processing of transactions involving payment cards. One example of the type of certification testing that may be performed on payment terminals is EMV Level 3 (L3) testing. In general, certification testing of a payment terminal involves (i) having a tester (e.g., an individual associated with an acquirer bank, a payment processor, a merchant, etc.) initiate test transactions at the payment terminal using test payment cards, (ii) capturing test data related to the test transactions that provides information on the functions that were performed by the payment terminal during the test transactions, including the communications that were sent and received by the payment terminal during processing of the test transactions, and then (iii) performing an analysis of the test data to determine whether the payment terminal operated properly during the test transactions (e.g., whether the payment terminal conforms with the policies and procedures of payment systems). As explained in Applicant’s specification: “it is important to all involved parties (e.g., cardholders, merchants, acquirer banks, issuer banks, etc.) that merchant systems are operating properly . . . if a payment terminal such as a contact-based or contactless card reader does not interact properly with other components involved in the end-to-end authorization process for a payment transaction, such as a payment card, a merchant’s computing system, a bank’s computing platform, and/or a payment processor’s computing platform, then this may lead to various problems, including but not limited to processing errors and security issues.” Second, Applicant’s claim limitations are recited in high level of abstraction lacking details and specifics as to how technological improvement to existing technology is achieved. Third, instant claims do not recite anything besides entirely conventional, generic technology of components of general purpose computing system. Therefore, instant claims 1-4, 6, 8-14, 17-18, and 21-26, are not patent eligible under § 101 in view of the Alice/Mayo Test. Applicant is invited to set up an interview with Examiner to further discuss this matter. Prior Art under § 102 and § 103: Closest prior art reference of record, Walters (US 9,449,320 B1) discloses testing of integrated circuit card payment terminals. Walters, however, fails to disclose – either alone or in combination with other references – the claim limitation found in independent claims 1, 11, and 17, as an ordered combination of steps. Claim Objections Claims 11 is objected to because of the following informalities: Claim 11. A client device comprising: . . . present, via the display of the client device, a graphical user interface (GUI) of the software application that enables selection of an operating mode for the client device from a set of operating-mode options presented via the GUI that includes at least (a) a first operating mode in which the client device emulates a physical payment card to use in testing the one or more payment terminals and (b) a second operating mode in which the client device configures a physical payment card to use in testing the one or more payment terminals; and receive, via the GUI of the software application, a user selection, from the set of operating mode options, of the first operating mode for the client device; and based on the user selection, selectively operate in the first operating mode in which the client device emulates a physical payment card in accordance with a virtual test card profile while selectively operating in the first operating mode, engage in a test transaction with a payment terminal by (i) receiving transaction data for a test transaction from the payment terminal, (ii) generating a cryptogram for the test transaction based at least in part on the transaction data for the test transaction, and (iii) transmitting the cryptogram for the test transaction to the payment terminal. There should be a colon (“:”) after “that includes at least”; there should be no definite article “the” in front of “one or more payment terminals”; there is no need for “and” between all the claim limitations; it appears that “in accordance with a virtual test card profile” and “while selectively operating in the first operating mode” are an end and a begging of two different limitations; there should be “and” between the last two limitations; and there should be a colon (“:”) after “by.” Applicant could amend claim 11 to recite: Claim 11. A client device comprising: . . . present, via the display of the client device, a graphical user interface (GUI) of the software application that enables selection of an operating mode for the client device from a set of operating-mode options presented via the GUI that includes at least: (a) a first operating mode in which the client device emulates a physical payment card to use in testing [[the]] one or more payment terminals and (b) a second operating mode in which the client device configures a physical payment card to use in testing the one or more payment terminals; [[and]] receive, via the GUI of the software application, a user selection, from the set of operating mode options, of the first operating mode for the client device; [[and]] based on the user selection, selectively operate in the first operating mode in which the client device emulates a physical payment card in accordance with a virtual test card profile; and while selectively operating in the first operating mode, engage in a test transaction with a payment terminal by: (i) receiving transaction data for a test transaction from the payment terminal, (ii) generating a cryptogram for the test transaction based at least in part on the transaction data for the test transaction, and (iii) transmitting the cryptogram for the test transaction to the payment terminal. 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-4, 6, 8-14, 17-18, and 21-26, are rejected under 35 USC § 101 because they are directed to non-statutory subject matter. The rationale for this finding is explained below. The Supreme Court in Mayo laid out a framework for determining whether an applicant is seeking to patent a judicial exception itself or a patent-eligible application of the judicial exception. See Alice Corp., 134 S. Ct. at 2355,110 USPQ2d at 1981 (citing Mayo, 566 U.S. 66, 101 USPQ2d 1961). This framework, which is referred to as the Mayo test or the Alice/Mayo test (“the test”), is described in detail in Manual of Patent Examining Procedure (”MPEP”) (see MPEP § 2106(III) for further guidance). The step 1 of the test: It need to be determined whether the claims are directed to a patent eligible (i.e., statutory) subject matter under 35 USC § 101. Step 2A of the test: If the claims are found to be directed to a statutory subject matter, the next step is to determine whether the claims are directed to a judicial exception i.e., law of nature, natural phenomenon, and abstract idea (Prong 1). If the claims are found to be directed to an abstract idea, it needs to be determined whether the claims recite additional elements that integrate the judicial exception into a practical application (Prong 2). Step 2B of the test: If the claims are directed to a judicial exception, the next and final step is to determine whether the claims recite additional elements that amount to significantly more than the judicial exception. Step 1 of the Test: When considering subject matter eligibility under 35 USC § 101, it must be determined whether the claim is directed to one of the four statutory categories of invention, i.e., process, machine, manufacture, or composition of matter. Here, the claimed invention of claims 1-4, 6, 8-14, 17-18, and 21-26, is a system and, thus, one of the statutory categories of invention. Conclusion of Step 1 Analysis: Therefore, claims 1-4, 6, 8-14, 17-18, and 21-26, are statutory under 35 USC § 101 in view of step 1 of the test. Step 2A of the Test: Prong 1: Claims 1-4, 6, 8-14, 17-18, and 21-26, however, recite an abstract idea of performing testing of payment terminals. The creation of performing testing of payment terminals, as recited in the independent claims 1, 11, and 17, belongs to certain methods of organizing human activity (i.e., fundamental economic principles or practices including mitigating risk) that are found by the courts to be abstract ideas. The limitations in independent claims 1, 11, and 17, which set forth or describe the recited abstract idea, are found in the following steps: “based on the user selection, selectively operate in either: (i) a first operating mode in which the client device emulates a physical payment card in accordance with a virtual test card profile by engaging in wireless communication with a payment terminal to facilitate processing of a test transaction, the wireless communication with the payment terminal including generating a cryptogram for the test transaction based at least in part on the transaction data for the test transaction; or (ii) a second operating mode in which the client device configures a physical payment card to operate in accordance with the virtual test card profile by engaging in wireless communication with the physical payment card to wirelessly transfer at least a portion of a virtual test card profile to the physical payment card such that the physical payment card is configured to generate a cryptogram for the test transaction based at least in part on the transaction data for the test transaction” (claim 1); “enable selection of an operating mode for the client device from a set of operating-mode options that includes at least (a) a first operating mode in which the client device emulates a physical payment card to use in testing one or more payment terminals and (b) a second operating mode in which the client device configures a physical payment card to use in testing the one or more payment terminals” (claim 11); “based on the user selection, selectively operate in the first operating mode in which the client device emulates a physical payment card in accordance with a virtual test card profile while selectively operating in the first operating mode, engage in a test transaction with a payment terminal by generating a cryptogram for the test transaction based at least in part on the transaction data for the test transaction” (claim 11); “based on the first user selection, selectively operate in the first operating mode in which the client device emulates a physical payment card in accordance with a first virtual test card profile while operating in the first operating mode, engage in a test transaction with a first payment terminal by generating a cryptogram for the test transaction based at least in part on the transaction data for the test transaction” (claim 17); and “based on the second user selection, selectively operate in the second operating mode in which the client device configures a physical payment card to operate in accordance with a second virtual test card profile by engaging in wireless communication with the physical payment card” (claim 17). Prong 2: In addition to abstract steps recited above in Prong 1, independent claims 1, 11, and 17, recite additional elements: “a display” (claims 1, 11, and 17); “at least one communication interface” (claims 1, 11, and 17); “at least one processor” (claims 1, 11, and 17); “at least one non-transitory computer-readable medium having stored thereon a software application comprising program instructions executed by the at least one processor” (claims 1, 11, and 17); and “a graphical user interface (GUI) of the software application” (claims 1, 11, and 17). These additional elements are recited at a high level of generality (i.e., as a generic processor performing a generic computer functions) such that they amount to no more than mere instructions to apply the exception using generic computer components. Also, the following additional limitation recites insignificant extra solution activity (for example, data gathering): “receive a first user selection, from a set of operating mode options, of a given operating mode of the client device” (claim 1); “the wireless communication with the payment terminal including: receiving test transaction data for the test transaction from the payment terminal, and transmitting the cryptogram for the test transaction to the payment terminal” (claim 1); “wirelessly transferring at least a portion of a virtual test card profile to the physical payment card such that the physical payment card is configured to: receive test transaction data for a test transaction from a payment termina, and transmit the cryptogram for the test transaction to the payment terminal” (claim 1); “receive a user selection, from the set of operating mode options, of the first operating mode for the client device” (claim 11); “engage in a test transaction with a payment terminal by: receiving transaction data for a test transaction from the payment terminal, and transmitting the cryptogram for the test transaction to the payment terminal” (claim 11); “receive a first user selection from a set of operating mode options, of a first operating mode for the client device” (claim 17); “engage in a test transaction with a first payment terminal by: receiving transaction data for a test transaction from the first payment terminal, and transmitting the cryptogram for the test transaction to the first payment terminal” (claim 17); “receive a second user selection, from the set of operating mode options, of a second operating mode for the client device” (claim 17); and “wirelessly transfer at least a portion of the second virtual test card profile to the physical payment card” (claim 17). These additional elements/limitations do not integrate the abstract idea into a practical application because they do not impose a meaningful limit on the judicial exception. The additional elements/limitations of independent claims 1, 11, and 17, here do not render improvements to the functioning of a computer or to any other technology or technical field (see MPEP § 2106.05(a)), nor do they integrate the abstract idea into a practical application under MPEP § 2106.05(b) (particular machine); MPEP § 2106.05(c) (particular transformations); or MPEP § 2106.05(e) (other meaningful limitations). Conclusion of Step 2A Analysis: The limitations in independent claims 1, 11, and 17, which set forth or describe the recited abstract idea are not patent eligible either alone or in combination. The additional elements/limitations in independent claims 1, 11, and 17, are not patent eligible either alone or in combination. Further, the combination of these additional elements/limitations and the limitations which set forth or describe the recited abstract idea is no more than mere instructions to apply the exception using a generic device. Accordingly, even in combination, these additional elements/limitations and the limitations which set forth or describe the recited abstract idea do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea. Therefore, independent claims 1, 11, and 17, are non-statutory under 35 USC § 101 in view of step 2A of the test. Step 2B of the Test: The additional elements of independent claims 1, 11, and 17 (see under Step 2A - Prong 2), are individually well-understood, routine, and conventional elements that amount to no more than implementing the abstract idea with a computerized system. The Applicant’s Specification describes these additional elements in following terms: [0110] Turning now to FIG. 5, a simplified block diagram is provided to illustrate some structural components that may be included in an example computing platform 500 that may be configured to perform some or all of the platform-side functions disclosed herein. At a high level, computing platform 500 may generally comprise any one or more computer systems (e.g., one or more servers) that collectively include one or more processors 502, data storage 504, and one or more communication interfaces 506, all of which may be communicatively linked by a communication link 508 that may take the form of a system bus, a communication network such as a public, private, or hybrid cloud, or some other connection mechanism. Each of these components may take various forms. [0111] For instance, the one or more processors 502 may comprise one or more processor components, such as one or more central processing units (CPUs), graphics processing units (GPUs), application-specific integrated circuits (ASICs), digital signal processors (DSPs), and/or programmable logic devices such as field programmable gate arrays (FPGAs), among other possible types of processing components. In line with the discussion above, it should also be understood that the one or more processors 502 could comprise processing components that are distributed across a plurality of physical computing devices connected via a network, such as a computing cluster of a public, private, or hybrid cloud. [0112] In turn, data storage 504 may comprise one or more non-transitory computer-readable storage mediums, examples of which may include volatile storage mediums such as random-access memory, registers, cache, etc. and non-volatile storage mediums such as read-only memory, a hard-disk drive, a solid-state drive, flash memory, an optical-storage device, etc. In line with the discussion above, it should also be understood that data storage 504 may comprise computer-readable storage mediums that are distributed across a plurality of physical computing devices connected via a network, such as a storage cluster of a public, private, or hybrid cloud that operates according to technologies such as AWS for Elastic Compute Cloud, Simple Storage Service, etc. [0113] As shown in FIG. 5, data storage 504 may be capable of storing both (i) program instructions that are executable by the one or more processors 502 such that the computing platform 500 is configured to perform any of the various functions disclosed herein (including but not limited to any of the server-side functions discussed above), and (ii) data that may be received, derived, or otherwise stored by computing platform 500. This is a description of general-purpose computing system. Further, the additional limitation of “receiving,” “transmitting,” and “transferring” information amount to no more than mere instructions to apply the exception using generic computer component. For the same reason this element is not sufficient to provide an inventive concept. The additional limitations of “receiving,” “transmitting,” and “transferring” information were considered insignificant extra-solution activity in Step 2A – Prong 2. Re-evaluating here in Step 2B, they are also determined to be well-understood, routine, and conventional activity in the field. Similarly to OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015) (sending messages over a network), and buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014) (computer receives and sends information over a network), the additional limitation of independent claims 1, 11, and 17, “receive,” “transmit,” and “transfer” information over a network in a merely generic manner. The courts have recognized “receiving,” “transmitting,” and “transferring” information functions as well-understood, routine and conventional when claimed in a merely generic manner. Therefore, the additional limitations of independent claims 1, 11, and 17, are well-understood, routine, and conventional. Further, taken as combination, the additional elements/limitations add nothing more than what is present when the elements are considered individually. There is no indication that the combination provides any effect regarding the functioning of the computer or any improvement to another technology. Conclusion of Step 2B Analysis: Therefore, independent claims 1, 11, and 17, are non-statutory under 35 USC § 101 in view of step 2B of the test. Dependent Claims: Dependent claims 2-4, 6, 8-10, and 21-25, depend on independent claim 1; dependent claims 12-14 and 26 depend on independent claim 11; and dependent claim 18 depends on independent claim 17. The elements in dependent claims 2-4, 6, 8-10, 12-14, 18-18, and 21-26, which set forth or describe the abstract idea, are: “while selectively operating in the first operating mode, the client device is configured to log test data related to the test transaction between the client device and the payment terminal; and while selectively operating in the second operating mode, the client device is configured to wirelessly retrieve, from the physical payment card, test data related to the test transaction between the physical payment card and the payment terminal” (claim: where “logging” step is further narrowing the recited abstract idea; and “retrieving” step is insignificant extra solution activity); “present, via the GUI of the software application, one or both of (i) the test data logged by the client device while selectively operating in the first operating mode, or (ii) the test data retrieved from the given physical payment card while selectively operating in the second operating mode” (claim 3: further narrowing the recited abstract idea); “transmit, to a remote computing system, one or both of (i) the test data logged by the client device while selectively operating in the first operating mode or (ii) the test data retrieved from the physical payment card while selectively operating in the second operating mode” (claim 4: insignificant extra solution activity); “in the first operating mode, the wireless communication with the payment terminal is carried out over a near field communications (NFC) link between the client device and the payment terminal” (claim 6: insignificant extra solution activity); “in the second operating mode, the wireless communication with the physical payment card is carried out over a near field communications (NFC) link between the client device and the physical payment card” (claim 8: insignificant extra solution activity); “determine an optimal location for positioning the physical payment card relative to the client device when selectively operating in the second operating mode” (claim 9: further narrowing the recited abstract idea); “a respective selectable GUI element for each of the first operating mode and the second operating mode” (claim 10: further narrowing the recited abstract idea); “while selectively operating in the first operating mode, the client device logs test data related to the test transaction between the client device and the payment terminal” (claim 12: further narrowing the recited abstract idea); “present, via the GUI of the software application, the test data logged by the client device while selectively operating in the first operating mode” (claim 13: further narrowing the recited abstract idea); “transmit, to a remote computing system, the test data logged by the client device while selectively operating in the first operating mode” (claim 14: insignificant extra solution activity); “while selectively operating in the first operating mode, the client device is configured to log test data related to the test transaction between the client device and the first payment terminal; and while selectively operating in the second operating mode, the client device is configured to wirelessly retrieve, from the physical payment card, test data related to a test transaction between the physical payment card and the a second payment terminal” (claim 18: where “logging” step is further narrowing the recited abstract idea; and “retrieving” step is insignificant extra solution activity); “transmit, via the at least one communication interface to a remote computing platform, a request for virtual test card profiles; after transmitting the request, receive, via the at least one communication interface from the remote computing system, a set of virtual test card profiles; and store the set of virtual test card profiles” (claim 21: insignificant extra solution activity); “load a set of virtual test card profiles in response to one of (i) a user request to load the set of virtual test card profiles, (ii) a determination that a user is authorized to use to the software application, or (iii) a notification that an updated version of the set of virtual test card profiles is available for loading by the client device” (claim 22: further narrowing the recited abstract idea); “while selectively operating in the first operating mode, the GUI of the software application presents an indication that the client device is emulating the physical payment card” (claim 23: further narrowing the recited abstract idea); “the GUI of the software application comprises a GUI element that (i) indicates whether the client device is operating in either the first operating mode or the second operating mode and (ii) comprises (a) a first selectable element corresponding to the first operating mode that, when selected, causes the client device to being operating in the first operating mode and (b) a second selectable element corresponding to the second operating mode that, when selected, causes the client device to being operating in the second operating mode” (claim 24: further narrowing the recited abstract idea); “the virtual test card profile comprises a data object that represents one or more of a test card type, a test card account number, a test card account holder name, an identifier of an issuer, or an identifier of a payment network” (claim 25: further narrowing the recited abstract idea); and “the user selection is a first selection, the virtual test card profile is a first virtual test card profile, and the payment terminal is a first payment terminal, and wherein the software application further comprises program instructions that, when executed by the at least one processor, cause the client device to: receive, via the GUI of the software application, a second user selection, from the set of operating mode options, of a second operating mode for the client device; and based on the second user selection, selectively operate in the second operating mode in which the client device configures a physical payment card to operate in accordance with a second virtual test card profile by engaging in wireless communication, via the at least one communication interface, with the physical payment card to wirelessly transfer at least a portion of the second virtual test card profile to the physical payment card” (claim 26: further narrowing the recited abstract idea, except where “receiving” step is insignificant extra solution activity). Conclusion of Dependent Claims Analysis: Dependent claims 2-4, 6, 8-10, 12-14, 18-18, and 21-26, do not correct the deficiencies of independent claims 1, 11, and 17, and they are, thus, rejected on the same basis. Conclusion of the 35 USC § 101 Analysis: Therefore, claims 1-4, 6, 8-14, 17-18, and 21-26, are rejected as directed to an abstract idea without “significantly more” under 35 USC § 101. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Kumawat (US 11,410,172 B2) discloses: “A verification computing system for verifying operation of a payment terminal and a payment processing network linking the payment terminal to a payment processor is provided. The verification computing system includes at least one verification computing module including at least one processor. The verification computing module is programmed to receive a test request message corresponding to a test payment card transaction from the payment terminal, identify a void flag included in the test request message, and bypass a settlement process for the test payment card transaction based on the identified void flag. The verification computing module is further configured to determine an operating status of the payment terminal and the payment processing network, generate a test response message based upon the determination, and transmit the test response message to the payment terminal for notifying a user.” Any inquiry concerning this communication or earlier communications from the examiner should be directed to VIRPI H. KANERVO whose telephone number is 571-272-9818. The examiner can normally be reached on Monday – Friday, 10 am – 6 pm. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor Abhishek Vyas can be reached on 571-270-1836. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /VIRPI H KANERVO/Primary Examiner, Art Unit 3691
Read full office action

Prosecution Timeline

Show 1 earlier event
Jun 17, 2025
Non-Final Rejection mailed — §101
Oct 14, 2025
Examiner Interview Summary
Oct 14, 2025
Applicant Interview (Telephonic)
Oct 17, 2025
Response Filed
Jan 20, 2026
Final Rejection mailed — §101
May 18, 2026
Request for Continued Examination
May 21, 2026
Response after Non-Final Action
Oct 02, 2026
Non-Final Rejection mailed — §101 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12770129
SYSTEMS AND METHODS FOR PAYMENT MANAGEMENT FOR SUPPORTING MOBILE PAYMENTS
4y 4m to grant Granted Oct 20, 2026
Patent 12711755
ITEM RECOGNITION ENHANCEMENTS
2y 7m to grant Granted Aug 18, 2026
Patent 12711483
GEOFENCED PAYMENTS
1y 10m to grant Granted Aug 18, 2026
Patent 12705621
MULTI-FACTOR AUTHENTICATION USING LOCATION DATA
3y 11m to grant Granted Aug 11, 2026
Patent 12700040
OUTLIER SYSTEM FOR GROUPING OF CHARACTERISTICS
4y 5m to grant Granted Aug 04, 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
48%
Grant Probability
95%
With Interview (+47.7%)
High
PTA Risk
Based on 569 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