DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, 18/594,838, was filed on March 4, 2024, and does not claim foreign priority or domestic benefit to any other application.
The effective filing date is after the AIA date of March 16, 2013, and so the application is being examined under the “first inventor to file” provisions of the AIA .
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
Status of the Application
This Final Office Action is in response to Applicant’s communication of Sept. 26, 2025.
Claims 1-4, 6-9, and 11-22 are currently pending, of which claims 1, 2, 6, 11, and 15 are independent.
In the most recent amendment, the claims 1-4, 6, 7, 9, 11-13, 15, 16, 18, 19, 21, and 22 have been amended. Claims 5 and 10 were previously cancelled.
All pending claims have been examined on the merits.
Claim Interpretation
The following is a quotation of 35 U.S.C. § 112(f):
(f) Element in Claim for a Combination. – An element in a claim for a combination may be expressed as a means or step for performing a specified function without the recital of structure, material, or acts in support thereof, and such claim shall be construed to cover the corresponding structure, material, or acts described in the specification and equivalents thereof.
Claims 11-22 in this application are given their broadest reasonable interpretation using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. However, the broadest reasonable interpretation of claim elements (also commonly referred to as claim limitations) in claims 11-22 is limited by the description in the specification, because 35 U.S.C. § 112(f) is invoked.
As explained in MPEP § 2181, subsection I, claim limitations that meet the following three-prong test will be interpreted under 35 U.S.C. § 112(f):
(A) the claim limitation uses the term “means”, “step”, or a term used as a substitute for “means” that is a generic placeholder (also called a nonce term or a non-structural term having no specific structural meaning) for performing the claimed function;
(B) the term “means”, “step”, or the generic placeholder, is modified by functional language, typically, but not always linked by the transition word “for” (e.g., “means for”) or another linking word or phrase, such as “configured to” or “so that”; and
(C) the term “means”, “step”, or the generic placeholder, is not modified by sufficient structure, material, or acts for performing the claimed function.
Use of the word “means” (or “step for”, or a nonce term) in a claim with functional language creates a rebuttable presumption that the claim element is to be treated in accordance with 35 U.S.C. § 112(f). The presumption that 35 U.S.C. § 112(f) is invoked is rebutted when the function is recited with sufficient structure, material, or acts within the claim itself to entirely perform the recited function.
Absence of the word “means” (or “step for”, or a nonce term) in a claim creates a rebuttable presumption that the claim element is not to be treated in accordance with 35 U.S.C. § 112(f). However, the presumption that 35 U.S.C. § 112(f) is not invoked is rebutted when the claim element recites function but fails to recite sufficiently definite structure, material or acts to perform that function.
Claim elements in this application that use the word “means” (or “step for”, or a nonce term) are presumed to invoke 35 U.S.C. § 112(f) except as otherwise indicated in an Office action. Similarly, claim elements that do not use the word “means” (or “step for”, or a nonce term) are presumed not to invoke 35 U.S.C. § 112(f), except as otherwise indicated in an Office action.
This application includes one or more claim limitations that do not use the word “means,” but are nonetheless being interpreted under 35 U.S.C. § 112(f), because the claim limitation(s) uses a generic placeholder (a nonce term) that is coupled with functional language without reciting sufficient structure to perform the recited function and the generic placeholder is not preceded by a structural modifier.
Such claim limitations in independent claims 11 and 15 are: “module” and “engine”. More specifically: “an intelligent routing module” and “a payment staging engine”.
Because these claim limitations are being interpreted under 35 U.S.C. § 112(f), they are being interpreted to cover the corresponding structure described in the specification as performing the claimed function, and equivalents thereof.
More specifically, the claimed feature “an intelligent routing module” is being interpreted according to paragraph [0024] of the specification:
[0024] The intelligent routing module 108 includes at least one processor coupled to at least one memory, where the memory stores instructions that are executed by the processor to perform the operations of the intelligent routing module 108. In at least one aspect, the intelligent routing module 108 determines payment scheduling data for each of the one or more payments. The payment scheduling data includes a determination whether the payment can be made by the requested payment date, and a preferred payment network for the payment based on data regarding the payee and the requested payment date. For example the intelligent routing module 108 can determine if a payment can be made by a requested payment date and determine a preferred payment network to be used for the payment. The intelligent routing module 108 is communicably coupled to the payment staging engine 110.
More specifically, the claimed feature “a payment staging engine” is being interpreted according to paragraph [0030] of the specification:
[0030] The payment staging engine 110 includes at least one processor coupled to at least one memory, where the memory stores instructions that are executed by the processor to perform the operations of the payment staging engine 110. The payment staging engine 110 receives the actionable payments from the intelligent routing module 108. The payment staging engine 110 transmits each payment through the preferred payment network for that payment. Each payment is transmitted by the payment staging engine 110 at the appropriate time such that the payment is received by the payee on the requested payment date. The payment staging engine 110 can transmit any number of payments to any number of payees on the same or different days.
If applicant does not intend to have these limitations interpreted under 35 U.S.C. § 112(f), applicant may: (1) amend the claim limitations to avoid them being interpreted under 35 U.S.C. § 112(f) (e.g., by reciting sufficient structure to perform the claimed function); or (2) present a sufficient showing that the claim limitations recite sufficient structure to perform the claimed function so as to avoid them being interpreted under 35 U.S.C. § 112(f).
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-9, and 11-22 are rejected under 35 U.S.C. §101 because the claimed invention is directed to non-statutory subject matter. The claimed invention is directed to an abstract idea, without “significantly more”.
Based on the flowchart in MPEP § 2106, Step 1 of the Alice/Mayo analysis is: “Is the claim to a process, machine, manufacture or composition of matter?”
In regards to Step 1 of the Alice/Mayo analysis, independent claims 1 and 6 are method claims, and claims 11 and 15 are apparatus claims.
For the sake of compact prosecution, we continue with the Alice/Mayo “abstract idea” analysis.
Step 2A, prong 1 of the Alice/Mayo analysis is: “Does the claim recite a law of nature, a natural phenomenon (product of nature), or an abstract idea?”
In regards to Step 2A, prongs 1 and 2 of the Alice/Mayo analysis, the abstract idea elements recited in independent claims 11 and 15 are shown in italic font. The “additional elements” and “extra solution steps” are shown in italic and underlined font (the independent methods claims 1 and 6 are rejected on the same grounds):
In regards to independent claim 11:
11. (Currently Amended) A system, comprising:
a computer-implemented payment server system of a financial institution, the payment server system comprising:
a payment scheduling system comprising a web-based interface to receive payment data;
an intelligent routing module to schedule a payment based on the payment data, wherein the intelligent routing module is communicably coupled to the payment scheduling system; and
a payment staging engine to perform the scheduled payment, wherein the payment server system is to:
electronically receive, by the web-based interface, from a customer of the financial institution, payment data for a batch of payments to be made by the customer from one or more accounts with the financial institution, wherein the payment data for the batch of payments comprises, for each payment in the batch of payments:
a payee;
a payment amount; and
a requested payment date;
automatically determine, by the intelligent routing module, payment scheduling data for each payment of the batch of payments, wherein the payment scheduling data comprises for each payment of the batch of payments:
a determination whether the payment can be made by the requested payment date;
a preferred payment network for the payment based on data regarding the payee, the requested payment date; and
a scheduled transmission time for the payment based on the requested payment date and the preferred payment network;
electronically transmit, by the intelligent routing module, actionable payments of the batch of payments based on the payment scheduling data to the payment staging engine, wherein the actionable payments comprise payments that can be made by the requested payment date;
maintain, by the payment staging engine, each actionable payment in a pending state prior to the scheduled transmission time for the actionable payment;
for each actionable payment initiate an asset transfer at the scheduled transmission time for the actionable payment, by the payment staging engine via the preferred payment network for the actionable payment such that the payment is received by the payee by the requested payment date; and
electronically transmit, by the intelligent routing module to the web-based interface, non-actionable payments of the batch of payments, wherein non-actionable payments comprise payments that cannot be made by the requested payment date.
In regards to independent claim 15:
15. (Currently Amended) A system, comprising:
a computer-implemented payment server system of a financial institution, the payment server system comprising:
a payment scheduling system comprising a web-based interface to receive payment data;
an intelligent routing module to schedule a payment based on the payment data, wherein the intelligent routing module is communicably coupled to the payment scheduling system; and
a payment staging engine to perform the scheduled payment, wherein the payment server system is to:
electronically receive, by the web-based interface, from a customer of the financial institution, payment data for a batch of payments to be made by the customer from one or more accounts with the financial institution, wherein the payment data for the batch of payments comprises, for each payment of the batch of payments:
a payee;
a payment amount; and
a requested payment date;
automatically determine, by the intelligent routing module, payment scheduling data for each payment of the batch of payments, wherein the payment scheduling data comprises payment of the batch of payments:
a determination whether the payment can be made by the requested payment date;
a preferred payment network for the payment based on data regarding the payee, the requested payment date; and
a scheduled transmission time for the payment based on the requested payment date and the preferred payment network;
electronically transmit, by the intelligent routing module, actionable payments of the batch of payments based on the payment scheduling data to the payment staging engine, wherein the actionable payments comprise payments that can be made by the requested payment date;
maintain, by the payment staging engine, each actionable payment in a pending state prior to the scheduled transmission time for the actionable payment;
for each actionable payment, initiate an asset transfer at the scheduled transmission time for the actionable payment, by the payment staging engine, via the preferred payment network for the actionable payment such that the payment is received by the payee by the requested payment date; and
electronically display, by the web-based interface, in response to receiving the payee and the payment amount, the earliest available payment date to the customer.
More specifically, claims 1-4, 6-9, and 11-22 recite an abstract idea: “Commercial or Legal Interactions (Including Agreements in the form of Contracts; Legal Obligations; Advertising, Marketing, or Sales Activities or Behaviors; Business Relations)”, as discussed in MPEP §2106(a)(2) Parts (I) and (II), and in the 2019 Revised Patent Subject Matter Eligibility Guidance.
The “Commercial or Legal Interactions” elements include:
“wherein the payment data for the batch of payments comprises, for each payment in the batch of payments: a payee; a payment amount; and a requested payment date”.
“automatically determine ... payment scheduling data for each payment of the batch of payments, wherein the payment scheduling data comprises for each payment of the batch of payments: a determination whether the payment can be made by the requested payment date; a preferred payment network for the payment based on data regarding the payee, the requested payment date; and a scheduled transmission time for the payment based on the requested payment date and the preferred payment network”.
“wherein the actionable payments comprise payments that can be made by the requested payment date”.
Moreover, claims 1-4, 6-9, and 11-20 recite “Mathematical Concepts", specifically “Mathematical Relationships”, “Mathematical Formulas or Equations”, and “Mathematical Calculations”, as discussed in MPEP §2106.04(a)(2) Part (IV), and in the 2019 Revised Patent Subject Matter Eligibility Guidance.
The mathematical elements include:
“automatically determine ... payment scheduling data for each payment of the batch of payments, wherein the payment scheduling data comprises for each payment of the batch of payments: a determination whether the payment can be made by the requested payment date; a preferred payment network for the payment based on data regarding the payee, the requested payment date; and a scheduled transmission time for the payment based on the requested payment date and the preferred payment network”.
The “additional elements” include: “a computer-implemented payment server system”, “a payment scheduling system”, “an intelligent routing module”, and “a payment staging engine”.
Moreover, “additional extra-solution elements” include: “receive payment data”, “receive … from a customer of the financial institution that has an account with the financial institution, payment data for one or more payments to be made by the customer from the account”, “transmit … actionable payments of the one or more payments based on the payment scheduling data to the payment staging engine”, “initiate an asset transfer ... from the account of the customer of the financial institution each of the actionable payments via the preferred payment network for the actionable payment”, “transmit … non-actionable payments of the one or more payments”, and “display … the earliest available payment date to the customer”.
Step 2A, prong 2 of the Alice/Mayo analysis is “Does the claim recite additional elements that integrate elements that integrate the judicial exception into a practical application?”
In regards to Step 2A, prong 2 of the Alice/Mayo analysis, this abstract idea is not integrated into a practical application, because:
The claim is directed to an abstract idea with additional generic computer elements. The generically recited computer elements (“a computer-implemented payment server system”, “a payment scheduling system”, “an intelligent routing module”, and “a payment staging engine”) do not add a meaningful limitation to the abstract idea, because they amount to simply implementing the abstract idea on a computer. The claim amounts to adding the words "apply it" (or an equivalent) with the abstract idea, or mere instructions to implement an abstract idea on a computer, or merely uses a computer as a tool to perform an abstract idea.
The extra-solution activities (“receive payment data”, “receive … from a customer of the financial institution that has an account with the financial institution, payment data for one or more payments to be made by the customer from the account”, “transmit … actionable payments of the one or more payments based on the payment scheduling data to the payment staging engine”, “initiate an asset transfer ... from the account of the customer of the financial institution each of the actionable payments via the preferred payment network for the actionable payment”, “transmit … non-actionable payments of the one or more payments”, and “display … the earliest available payment date to the customer”) do not add a meaningful limitation to the method, as they are insignificant extra-solution activity;
The combination of the abstract idea with the additional elements (generically recited computer elements), and/or with the extra-solution activities, does not integrate the abstract idea into a practical application.
Step 2B of the Alice/Mayo analysis is: “Does the claim recite additional elements that amount to significantly more than the judicial exception?”
In regards to Step 2B of the Alice/Mayo analysis, the claims do not include additional elements that are sufficient to amount to significantly more than the abstract idea, because:
When considering the additional elements "alone and in combination" (“a computer-implemented payment server system”, “a payment scheduling system”, “an intelligent routing module”, and “a payment staging engine”), they do not add significantly more (also known as an "inventive concept") to the exception, because they amount to simply implementing the abstract idea on a computer. Instead, they merely add the words "apply it" (or an equivalent) with the abstract idea, or mere instructions to implement an abstract idea on a computer, or merely use a computer as a tool to perform an abstract idea.
In regards to the extra solution activities (“receive payment data”, “receive … from a customer of the financial institution that has an account with the financial institution, payment data for one or more payments to be made by the customer from the account”, “transmit … actionable payments of the one or more payments based on the payment scheduling data to the payment staging engine”, “initiate an asset transfer ... from the account of the customer of the financial institution each of the actionable payments via the preferred payment network for the actionable payment”, “transmit … non-actionable payments of the one or more payments”, and “display … the earliest available payment date to the customer”), these are recognized as such by the court decisions listed in MPEP § 2106.05(d).
More specifically, in regards to the “receive” and “transmit” steps, see the court cases 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 (presenting offers and gathering statistics), OIP Techs., 788 F.3d at 1362-63, 115 USPQ2d at 1092-93; 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).
Moreover, in regards to “apply it”, according to MPEP § 2106.05(f)(2):
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. See Affinity Labs v. DirecTV, 838 F.3d 1253, 1262, 120 USPQ2d 1201, 1207 (Fed. Cir. 2016) (cellular telephone); TLI Communications LLC v. AV Auto, LLC, 823 F.3d 607, 613, 118 USPQ2d 1744, 1748 (Fed. Cir. 2016) (computer server and telephone unit). Similarly, "claiming the improved speed or efficiency inherent with applying the abstract idea on a computer" does not integrate a judicial exception into a practical application or provide an inventive concept. Intellectual Ventures I LLC v. Capital One Bank (USA), 792 F.3d 1363, 1367, 115 USPQ2d 1636, 1639 (Fed. Cir. 2015).
In contrast, a claim that purports to improve computer capabilities or to improve an existing technology may integrate a judicial exception into a practical application or provide significantly more. McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1314-15, 120 USPQ2d 1091, 1101-02 (Fed. Cir. 2016); Enfish, LLC v. Microsoft Corp., 822 F.3d 1327, 1335-36, 118 USPQ2d 1684, 1688-89 (Fed. Cir. 2016). See MPEP §§ 2106.04(d)(1) and 2106.05(a) for a discussion of improvements to the functioning of a computer or to another technology or technical field.
The Examiner holds that the independent claims “use a computer or other machinery in its ordinary capacity for economic or other tasks (e.g., to receive, store, or transmit data)” or “simply add a general purpose computer or computer components after the fact to an abstract idea”.
Independent claims 1 and 2 are rejected on the same grounds as independent claim 11, and independent claim 6 is rejected on the same grounds as independent claim 15.
All dependent claims are also rejected, because they merely further define the abstract idea, except for the following claims, which recite the following features:
In addition, claims 1-4, 6-9, and 11-22 are interpreted as "means plus function" claims. As mandated under 35 USC § 112(f), the Examiner has interpreted these claims according to the Applicant's disclosure. Paragraphs [0020], [0024], and [0030] of the specification describe a general purpose computer, which does not add “significantly more” technologically to the abstract idea.
Response to Amendments
Re: Claim Interpretations - 35 USC § 112(f)
The 35 U.S.C. 112 interpretations have been maintained, because Applicant’s amendments to the claims have not amended the claims to address this issue, and the arguments are a repeat of those submitted on Sept. 26, 2025.
The arguments submitted on Sept. 26, 2025 refer to para. [0067] of the specification as providing a definition of the term “control circuit” (which is not recited in claims 11-22), but fails to discuss the terms “an intelligent routing module” and “a payment staging engine”, which are recited in independent claim 11. Moreover, paragraphs [0024] and [0030] do define these nonce terms of “module” and “engine”, and were cited in the original 35 USC § 112(f) interpretation.
Re: Claim Rejections - 35 USC § 101
The 35 U.S.C. 101 rejections have been amended, as necessitated by Applicant’s amendments to the claims.
Re: Claim Rejections - 35 USC § 103
The 35 U.S.C. 103 rejections have been withdrawn, as necessitated by Applicant’s amendments to the claims.
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 extension fee 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 date of this final action.
Any inquiry concerning this communication or earlier communications should be directed to Examiner Ayal Sharon, whose telephone number is (571) 272-5614, and fax number is (571) 273-1794. The Examiner can normally be reached from Monday to Friday between 9 AM and 6 PM. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, SPE Christine Behncke can be reached at (571) 272-8103 or at christine.behncke@uspto.gov. The fax 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.
Sincerely,
/Ayal I. Sharon/
Examiner, Art Unit 3695
October 22, 2026