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 Claims
This action is in reply to the communication(s) filed on 06 July 2026.
Claims 1, 10 and 18 are amended.
Claim(s) 1-20 is/are currently pending and have been examined.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 06 August 2026 has been entered.
Response to Arguments
Applicant's arguments filed 06 July 2026 have been fully considered but they are not persuasive.
Rejection Under 35 U.S.C. §112
The claims have been amended to address the objection(s)/rejection(s) presented in the prior Office Action. Accordingly, Examiner withdraws the corresponding objection(s)/rejection(s).
Rejection Under 35 U.S.C. §101
Step 2A Prong Two
Applicant argues that the Office did not consider claim elements beyond the alleged judicial exception both individually and in combination. Examiner respectfully disagrees. Several times throughout the office action it is stated “These element(s) in combination do not add anything that is not already present when the steps are considered separately.” Ergo, the claim elements were considered in combination.
Applicant argues across pages 13-15 of the remarks that many cited claim limitations are not merely a statement of payment distribution or other organizing human activity. Examiner respectfully disagrees. Step 2A Prong 1 requires examiners to evaluate whether a claim recites a judicial exception as the applicant cited. The elements which examiner identified in Step 2A Prong 1 are those which describe the noted abstract idea which means that the claim recites an abstract idea. “The mere inclusion of a judicial exception such as a mathematical formula (which is one of the mathematical concepts identified as an abstract idea in MPEP § 2106.04(a)) in a claim means that the claim "recites" a judicial exception under Step 2A Prong One.” See MPEP 2106.04(II)(A)(2). “When performing the analysis at Step 2A Prong One, it is sufficient for the examiner to provide a reasoned rationale that identifies the judicial exception recited in the claim and explains why it is considered a judicial exception (e.g., that the claim limitation(s) falls within one of the abstract idea groupings). Therefore, there is no requirement for the examiner to rely on evidence, such as publications or an affidavit or declaration under 37 CFR 1.104(d)(2), to find that a claim recites a judicial exception. Cf. Affinity Labs of Tex., LLC v. Amazon.com Inc., 838 F.3d 1266, 1271-72, 120 USPQ2d 1210, 1214-15 (Fed. Cir. 2016) (affirming district court decision that identified an abstract idea in the claims without relying on evidence); OIP Techs., Inc. v. Amazon.com, Inc., 788 F.3d 1359, 1362-64, 115 USPQ2d 1090, 1092-94 (Fed. Cir. 2015) (same); Content Extraction & Transmission LLC v. Wells Fargo Bank, N.A., 776 F.3d 1343, 1347, 113 USPQ2d 1354, 1357-58 (Fed. Cir. 2014) (same).” See MPEP 2106.07(a)(III). The omitted element(s) (if any) are elements in addition to the abstract idea (i.e. they are not abstract) which require further analysis under Step 2A Prong 2 in order to determine if they cause the recited abstract idea to be integrated into a practical application. See MPEP 2106.07(a)(II). The omitted element(s) (if any) are later enumerated under Step 2A Prong 2 as additional elements. The claim element recites and/or describes a judicial exception.
Applicant argues across pages 13-15 of the remarks that the claim limitations require specific operations on one or more specific claimed data objects and should therefore be evaluated as an additional element under step 2A Prong Two. Examiner respectfully disagrees. “The Court has held that a claim may not preempt abstract ideas, laws of nature, or natural phenomena, even if the judicial exception is narrow (e.g., a particular mathematical formula such as the Arrhenius equation). See, e.g., Mayo, 566 U.S. at 79-80, 86-87, 101 USPQ2d at 1968-69, 1971 (claims directed to "narrow laws that may have limited applications" held ineligible); Flook, 437 U.S. at 589-90, 198 USPQ at 197 (claims that did not "wholly preempt the mathematical formula" held ineligible).” See MPEP 2106.04(I). Narrowing the judicial exception to the particular use case or context applicant describes does not negate the fact that the claim(s) recites and/or describes a judicial exception. The claim(s) recites and/or describes a judicial exception.
Applicant argues that the specification confirms that these claim limitations address deficiencies in prior systems and are thus integrated into a practical application. Examiner respectfully disagrees. The MPEP clarifies how additional elements can impose meaningful limits on a recited judicial exception:
“Consideration of improvements is relevant to the eligibility analysis regardless of the technology of the claimed invention. That is, the consideration applies equally whether it is a computer-implemented invention, an invention in the life sciences, or any other technology. See, e.g., Rapid Litigation Management v. CellzDirect, Inc., 827 F.3d 1042, 119 USPQ2d 1370 (Fed. Cir. 2016), in which the court noted that a claimed process for preserving hepatocytes could be eligible as an improvement to technology because the claim achieved a new and improved way for preserving hepatocyte cells for later use, even though the claim is based on the discovery of something natural. Notably, the court did not distinguish between the types of technology when determining the invention improved technology. However, it is important to keep in mind that an improvement in the abstract idea itself (e.g. a recited fundamental economic concept) is not an improvement in technology. For example, in Trading Technologies Int’l v. IBG, 921 F.3d 1084, 1093-94, 2019 USPQ2d 138290 (Fed. Cir. 2019), the court determined that the claimed user interface simply provided a trader with more information to facilitate market trades, which improved the business process of market trading but did not improve computers or technology.” (MPEP 2106.05(a)(II))
Drawing attention to the emphasized section, an improvement in the judicial exception itself is not an improvement in technology. In the current case, regardless of whether or not applicant’s invention improves the recited judicial exception, improving a method, algorithm, or process of a judicial exception absent of any technological modification, would be an improvement to the judicial exception (e.g. via the improvement in the efficiency of the judicial exception), but does not improve computers or technology.
Step 2B
Applicant argues across pages 16-19 of the remarks that the Office did not consider the amended claim limitations that require the system to parse, compare, determine, conditionally store or generate an error, authenticate, calculate, and authorize in a particular ordered sequence or ordered combination. Examiner respectfully disagrees. “Although the conclusion of whether a claim is eligible at Step 2B requires that all relevant considerations be evaluated, most of these considerations were already evaluated in Step 2A Prong Two. Thus, in Step 2B, examiners should:
• Carry over their identification of the additional element(s) in the claim from Step 2A Prong Two;
• Carry over their conclusions from Step 2A Prong Two on the considerations discussed in MPEP §§ 2106.05(a) - (c), (e) (f) and (h):
• Re-evaluate any additional element or combination of elements that was considered to be insignificant extra-solution activity per MPEP § 2106.05(g), because if such re-evaluation finds that the element is unconventional or otherwise more than what is well-understood, routine, conventional activity in the field, this finding may indicate that the additional element is no longer considered to be insignificant; and
• Evaluate whether any additional element or combination of elements are other than what is well-understood, routine, conventional activity in the field, or simply append well-understood, routine, conventional activities previously known to the industry, specified at a high level of generality, to the judicial exception, per MPEP § 2106.05(d)” (See MPEP 2106.05(II)).
In both the prior and instant Office Action, the conclusions from Step 2A Prong Two are equally applied in Step 2B which further re-evaluates additional elements which are considered to be insignificant extra-solution activity and evaluates these elements as per MPEP §2106.05(d) to be well-understood, routine, and conventional activity. Said elements which are considered to be insignificant extra-solution activity (if any) are evaluated as well-understood, routine, and conventional as per the evidentiary requirements detailed in MPEP §2106.07(a)(III) utilizing option (B) via citation to one or more of the court decisions discussed in MPEP §2106.05(d)(II). Thus, there are no further elements to evaluate under Step 2B. Most considerations relating to any additional elements were already evaluated in Step 2A Prong Two and thus do not require further re-evaluation in Step 2B.
Applicant argues that the amended claims recite a particular ordered combination amounts to significantly more than the alleged abstract idea in which the system parses a stored recipient file template, compares extracted data fields with stored recipient data, ensures single processing and non-overlap, applies user-specified rules, conditionally stores validated data or generates a validation error, authenticates based on a determination that the data fields match user requirements, and only then calculates and authorizes payment based on the calculated values. Examiner respectfully disagrees. The MPEP clarifies how additional elements can impose meaningful limits on a recited judicial exception:
“Consideration of improvements is relevant to the eligibility analysis regardless of the technology of the claimed invention. That is, the consideration applies equally whether it is a computer-implemented invention, an invention in the life sciences, or any other technology. See, e.g., Rapid Litigation Management v. CellzDirect, Inc., 827 F.3d 1042, 119 USPQ2d 1370 (Fed. Cir. 2016), in which the court noted that a claimed process for preserving hepatocytes could be eligible as an improvement to technology because the claim achieved a new and improved way for preserving hepatocyte cells for later use, even though the claim is based on the discovery of something natural. Notably, the court did not distinguish between the types of technology when determining the invention improved technology. However, it is important to keep in mind that an improvement in the abstract idea itself (e.g. a recited fundamental economic concept) is not an improvement in technology. For example, in Trading Technologies Int’l v. IBG, 921 F.3d 1084, 1093-94, 2019 USPQ2d 138290 (Fed. Cir. 2019), the court determined that the claimed user interface simply provided a trader with more information to facilitate market trades, which improved the business process of market trading but did not improve computers or technology.” (MPEP 2106.05(a)(II))
Drawing attention to the emphasized section, an improvement in the judicial exception itself is not an improvement in technology. In the current case, regardless of whether or not applicant’s invention improves the recited judicial exception, improving a method, algorithm, or process of a judicial exception absent of any technological modification, would be an improvement to the judicial exception (e.g. via the improvement in the efficiency of the judicial exception), but does not improve computers or technology.
Claim Interpretation
Examiner will interpret “eligible recipients” in Claim 5 to be recipients who are eligible for payment distribution (as is supported by the specification at paragraph [0062]).
Examiner will interpret “configuration-based” in Claim 7 to be equivalent to “preconfigured”, “predefined”, or “customizable to specify under which conditions a particular setting is applied” (as is supported by the specification at paragraph [0063]).
Examiner notes that “a payment recipient” recited in Claim 13 is a different recipient from “a recipient” in Claim 10 as noted by the applicant in the remarks dated 05 March 2025.
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.
Step 1 of the 101 Analysis:
Claims 1-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. The claims recites a system, non-transitory computer-readable medium, and method for multi-party payment disbursement. These are a machine, article of manufacture, and process which are within the four categories of statutory subject matter.
Step 2A Prong 1 of the 101 Analysis:
The following limitations and/or similar versions are found in claim(s) 1, 10 and 18:
Claim(s) 1, 10 and 18:
“receive,…, a request to authenticate a recipient file template, wherein the recipient file template contains data fields for a recipient;”
“parse contents of the recipient file template to extract the data fields for the recipient, wherein the recipient file template is one of a plurality of file templates…”
“process, the data fields by comparing the extracted data fields with recipient data…for validation to ensure data in the data fields is processed once for the recipient and there is no overlapping data from at least one of multiple entities within the system or multiple file templates;”
“determine whether, based on user-specified rules, the data fields match user requirements, the data fields including personal identifiable information of the recipient wherein the rules are customized by the user based on information needed to validate and authorize the payment distribution to the recipient;”
“in response to determining that the data fields do not match the user requirements, generate a validation error for the recipient file template;”
“authenticate the recipient file template based on a determination that the data fields match the user requirements;”
“calculate, upon authentication of the recipient file template and based on the data fields, at least one of payment eligibility and payment amount;”
Claim(s) 1:
“authorize, based on at least one of the payment eligibility and the payment amount calculated from the data fields, an automatic payment to a recipient;”
“send the payment to a payment disbursement system…”
Claim(s) 10 and 18:
“authorize, based on at least one of the payment eligibility and the payment amount calculated from the data fields, a payment to a recipient;”
“notify the recipient of a status of the payment, using a payment disbursement system,…”
These limitations, as drafted, are a process that, under its broadest reasonable interpretation, describes Fundamental Economic Principles or Practices or Commercial or Legal Interactions but for the recitation of generic computer components. That is, other than reciting “a database, a memory storing instructions”, “at least one processor configured to execute the instructions to:”, “computer-implemented”, or “A computer-implemented method for automatic payment distribution, comprising:” nothing in the claims’ elements precludes the steps from practically describing Fundamental Economic Principles or Practices or Commercial or Legal Interactions. For example, but for the recited computer language, the limitations in the context of this claim describes Mitigating Risk or could reasonably describe business relations. Mitigating Risk is described when determining appropriate payees for disbursement. Business Relations is described when disbursing payment to recipients. If a claim limitations, under their broadest reasonable interpretation, describes Fundamental Economic Principles or Practices or Commercial or Legal Interactions but for the recitation of generic computer components, then it falls within the “Certain Methods of Organizing Activity” grouping of abstract ideas.
Dependent claim(s) 4, 6, 8, 11, 13, 15-16 and 19-20 are directed to the following:
Claim(s) 4:
“generating a notification if the payment is attempted more than once.”
Claim(s) 6:
“denying authorization of another payment to the recipient;”
Claim(s) 8:
“…sending a notification of at least one of an email, text message, phone call, or system alert, based on the user-specified rules when a payment is sent to a payment disbursement system.”
Claim(S) 11:
“…wherein the operations further comprise determining a user’s authorization or status, wherein the user includes at least one of a read-only user, an upload-only user, a call center agent, or an administrator.”
Claim(s) 13:
“…wherein the operations further comprise a call center agent performing at least one of:… reporting a payment recipient;… reviewing payment history;”
Claim(s) 15:
“validating the payment recipient’s address;”
“confirming financial information with a financial institution.”
Claim(s) 16:
“…wherein the operations further comprise the payment recipient receiving multiple payments.”
Claim(s) 19:
“…wherein the user-specified rules are customized by an employing entity.”
Claim(s) 20:
“…wherein the operations further comprise an administrator changing the user requirements.”
These processes are similar to the abstract idea noted in the independent claims because they further the limitations of the independent claim which are directed to a judicial exception. Accordingly, these claim elements do not serve to confer subject matter eligibility to the claims since they are directed to abstract ideas.
Dependent claim(s) 3-5, 7, 9, 12, 14 and 17 include the following limitations which are not directed to any additional abstract ideas and are also not directed to any additional non-abstract claim elements:
Claim(s) 3:
“…wherein the payment to the recipient further comprises a payment method of at least one of a check, ACH payment, or debit to a bank account.”
Claim(s) 4:
“…wherein the payment method is one of a plurality of payment methods…”
Claim(s) 5:
“…wherein the recipient is selected from a database of eligible recipients.”
Claim(s) 7:
“…wherein the user-specified rules are configuration-based.”
Claim(s) 9:
“…wherein each payment is an encrypted transaction.”
Claim(s) 12:
“…wherein an administrator has full permissions within the user-specified rules including changing the payment recipient’s address, re-issuing check payments, or flagging payments for review.”
Claim(s) 14:
“…wherein the data fields include personal identifiable information.”
Claim(s) 17:
“…wherein the payment amount has a limit based on user-specified rules.”
Rather, these claims offer further descriptive limitations of elements found in the independent claims and addressed above – such as by describing the nature and content of the data that is received/sent. While these descriptive elements may provide further helpful context for the claimed invention these elements do not serve to confer subject matter eligibility to the invention since they merely represent a narrowing of the recited judicial exception. Step 2A prong 2 and Step 2B for these limitations therefore are the same as for the independent claims.
Accordingly, the claims recite an abstract idea.
Step 2A Prong 2 of the 101 Analysis:
This judicial exception is not integrated into a practical application. In particular, the independent claim(s) recite the following additional elements:
Claim 1:
“a database;”
“a memory storing instructions;”
“at least one processor configured to execute the instructions to perform operations comprising:”
Claim(s) 1, 10 and 18:
“…from a user device of a user…”
“…stored in the database;”
“…stored in the database…”
“in response to determining that the data fields match the user requirements, store validated recipient data corresponding to the recipient file template in the database;”
“…wherein the payment disbursement system is configured with a search screen on a graphical user interface, the search screen including a button to customize fields to search for the recipient.
Claim 10:
“A non-transitory computer-readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for automatic payment distribution, comprising:”
The computer components or other machinery (database, memory, non-transitory computer-readable medium and user device) are recited at a high level of generality (i.e. as a generic database, generic memory, and user device) such that it amounts to no more than mere instructions to implement the judicial exception on a computer or by using a computer or other machinery merely as a tool to perform an existing process. These element(s) in combination do not add anything that is not already present when the steps are considered separately. Simply implementing an abstract idea on a computer or using machinery as a tool to perform an existing process is not indicative of integration into a practical application (See MPEP § 2106.05(f).)
The storing step(s) are recited at a high level of generality (i.e., as generally storing) such that they amount to no more than mere data gathering which is adding insignificant extra solution activity. These element(s) in combination do not add anything that is not already present when the steps are considered separately. Simply adding insignificant extra-solution activity is not indicative of integration into a practical application (See MPEP § 2106.05(g).)
The use of a search screen with customizable search via button is implemented at a high level of generality (i.e. as simply using the technology) such that it amounts to no more than generally linking the use of the judicial exception to a particular technological environment or field of use. These element(s) in combination do not add anything that is not already pre-sent when the steps are considered separately. Generally linking the use of the judicial exception to a particular technological environment or field of use is not indicative of integration into a practical application (See MPEP § 2106.05(h).)
Dependent claim(s) 2, 4, 6 and 13 contain the following additional elements:
Claim(s) 2:
“…wherein the operations further comprise logging each authorized payment to a recipient as a transaction.”
Claim(s) 4:
“logging each payment method in a positive pay file;”
Claim(s) 6:
“logging the denied authorization of the another payment to the recipient.”
Claim(s) 13:
“…wherein the operations further comprise a call center agent performing at least one of: searching for a payment recipient;… searching a database;… viewing payment status.”
The computer components or other machinery (database) are recited at a high level of generality (i.e. as a generic database) such that it amounts to no more than mere instructions to implement the judicial exception on a computer or by using a computer or other machinery merely as a tool to perform an existing process. These element(s) in combination do not add anything that is not already present when the steps are considered separately. Simply implementing an abstract idea on a computer or using machinery as a tool to perform an existing process is not indicative of integration into a practical application (See MPEP § 2106.05(f).)
The logging, searching, and viewing step(s) are recited at a high level of generality (i.e., as generally logging, generally searching, and generally viewing) such that they amount to no more than mere data gathering which is adding insignificant extra solution activity. These element(s) in combination do not add anything that is not already present when the steps are considered separately. Simply adding insignificant extra-solution activity is not indicative of integration into a practical application (See MPEP § 2106.05(g).)
Accordingly, these additional elements do not integrate the abstract idea into a practical application because they do not impose any meaningful limits on practicing the abstract idea.
The claims are directed to an abstract idea.
Step 2B of the 101 Analysis:
The user device mentioned above is/are not described in further detail within the applicant’s specification. Therefore examiner must interpret these elements as generic computer components.
The database and non-transitory computer-readable medium mentioned above is/are disclosed in applicant’s specification (See paragraph [0042] of the specification). The components are described as:
“The various components of system 100 may be stored in database 102. Database 102 may be included on a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible or non-transitory computer-readable medium. Database 102 may include one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments. Database 102 may include any suitable databases, ranging from small databases hosted on a work station to large databases distributed among data centers. Database 102 may also include any combination of one or more databases controlled by memory controller devices or software. For example, database 102 may include document management systems, Microsoft SQL™ databases, SharePoint™ databases, Oracle™ databases, Sybase™ databases, other relational databases, or non-relational databases, such as Mongo and others.”
The processor mentioned above is/are disclosed in applicant’s specification (See paragraph [0058] of the specification). The component is described as:
“Processor 220 may take the form of, but is not limited to, a microprocessor, embedded processor, or the like, or may be integrated in a system on a chip (SoC). Furthermore, according to some embodiments, processor 220 may be from the family of processors manufactured by Intel®, AMD®, Qualcomm®, Apple®, NVIDIA®, or the like. The processor 220 may also be based on the ARM architecture, a mobile processor, or a graphics processing unit, etc. The disclosed embodiments are not limited to any type of processor configured in server 210.”
The memory mentioned above is/are disclosed in applicant’s specification (See paragraph [0059] of the specification). The component is described as:
“Memory 230 may include one or more storage devices configured to store instructions used by the processor 220 to perform functions related to server 210. The disclosed embodiments are not limited to particular software programs or devices configured to perform dedicated tasks. For example, the memory230 may store a single program, such as a user-level application, that performs the functions associated with the disclosed embodiments, or may comprise multiple software programs. Additionally, the processor 220 may, in some embodiments, execute one or more programs (or portions thereof) remotely located from server 210. Furthermore, memory230 may include one or more storage devices configured to store data for use by the programs. Memory 230 may include, but is not limited to a hard drive, a solid state drive, a CD-ROM drive, a peripheral storage device (e.g., an external hard drive, a USB drive, etc.), a network drive, a cloud storage device, or any other storage device.”
Therefore applicant’s own specification supports these components as generic computer components.
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed above with respect to integration of the abstract idea into a practical application, the additional elements identified in Step 2A Prong 2 amount to no more than mere instructions to implement the judicial exception on a computer or no more than mere data gathering or data outputting which only adds insignificant extra solution activity to the judicial exception. Accordingly, the Examiner:
• Carries over their identification of the additional element(s) in the claim from Step 2A Prong Two;
• Carries over their conclusions from Step 2A Prong Two on the considerations discussed in MPEP §§ 2106.05(a) - (c), (e) (f) and (h):
• Re-evaluates any additional element or combination of elements that was considered to be insignificant extra-solution activity per MPEP § 2106.05(g), because if such re-evaluation finds that the element is unconventional or otherwise more than what is well-understood, routine, conventional activity in the field, this finding may indicate that the additional element is no longer considered to be insignificant.
These element(s) in combination do not add anything that is not already pre-sent when the steps are considered separately. Adding insignificant extra-solution activity cannot provide an inventive concept when the activities are well-understood routine and conventional. The courts have recognized the following computer functions as well-understood, routine, and conventional functions when they are claimed in a merely generic manner:
(for storing/logging/searching for/viewing various data) Storing and retrieving information in memory, (See MPEP § 2106.05(d)(II)).
(for viewing various data) Receiving or transmitting data over a network, (See MPEP § 2106.05(d)(II)).
The claims are not patent eligible.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Cronin et al. (US 2019/0272597 A1) discloses employee based payroll validation including PII such as employee name.
Connor et al. (US 2023/0058933 A1) discloses filtering rules for validation where they may apply a rule to prepare a retrieved payment for potential duplicate payment matching based on payment amount when the payment destination account is a consumer card or business card (i.e. rules customized based on recipient account information).
Noland et al. (US 2017/0132200 A1) discloses searching data files with a search screen with search fields wherein the search fields are customizable via a button.
John et al. (US 8,078,515 B2) discloses recording user activity and historical records including history of charge-backs and historical record of rejection (i.e. logging the denied authorization).
Franceschi et al. (US 2020/0211012 A1) discloses that an administrator may flag transactions for review and restricting transaction amounts based on a user class.
Joyce et al. (WO 00/16568 A1) discloses a payment system may contain call center agents that can select accounts from a menu (i.e. search for payment recipient and searching a database) and display details of the selected account including payments and payment details (i.e. reviewing payment history and viewing payment status).
Kearns et al. (US 2015/0032604 A1) discloses call center agents making reports of DNR transactions.
Orttung et al. (US 2013/0226798 A1) discloses implementing user defined rules for electronic payment.
Rajendran et al. (US 2021/0295285 A1) discloses removing duplicate entries stored in a database.
Ainslie et al. (WO 2014/052970 A1) discloses how the presence of PII may affect usage policies.
Edlabadkar et al. (“IBM Financial Transaction Manager for Automated Clearing House Services”) discloses operations for an ACH including operations for business rules.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ADAM J HILMANTEL whose telephone number is (571)272-8984. The examiner can normally be reached M-F 8:30AM-5:00PM.
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, Abhishek Vyas can be reached at (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 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.
/ADAM HILMANTEL/Examiner, Art Unit 3691
