DETAILED ACTION
This Final Office Action is in response to the application filed on 08/17/2012, the Amendment & Remark filed on 03/20/2026 and Request for Continued Examination filed on 03/20/2026.
Notice of Pre-AIA or AIA Status
The present application is being examined under the pre-AIA first to invent provisions.
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 03/20/2026 has been entered.
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-13,15-20 and 22-30 are rejected under 35 U.S.C. 101 because the claimed invention is directed to a judicial exception (i.e., a law of nature, a natural phenomenon, or an abstract idea) without significantly more.
As an initial matter, the claims as a whole are to a process and a machine, which falls within one or more statutory categories. (Step 1: YES) The recitation of the claimed invention is then further analyzed as follow, in which the abstract elements are boldfaced.
The claims recite:
providing a processor based enrollment system including a requesting client computer system including an input/output interface that enables wired or wireless connection to a mobile phone and
providing a computer logic stored in a main memory or secondary memory as the controller of the processor based enrollment system and containing instructions directing the enrollment of a customer in an underbanked and unbanked module and a communications interface for enrolling a customer in the underbanked and unbanked module associated with a financial institution by verifying the customer’s information regardless of whether the customer is a deposit or non-deposit customer of said financial institution;
receiving, with a central processing unit as a data receiver, check data and identification data from the requesting client computer system, the data receiver in communication with a third party check verification system, the check verification system applying scanned check data for decisioning;
creating an interface between the third party check verification system and a bill payment system;
providing a server to response to the request client computer system, retrieve the requested page, retrieve check and identification data and transmit the check and identification data over a communications data channel transmit data for the requested page back to the requesting client computer system, display the requested page, launching an application to perform an analysis;
verifying with the check verification system said check data and identification data;
upon verifying said check data, dispensing funds to the customer with a funds dispenser:
loading funds onto a general purpose reloadable prepaid card electronically;
facilitating cash to cash money transfers over the communications data channel; and
facilitating bill payments to a network of billers over the communications data channel;
applying a graphical user interface (GUI) to on the requesting client computer system and to facilitate customer creation and enrollment, the GUI creating a first interface between a third party vendor capable of providing check verification and the underbanked and unbanked module and a second interface between the third party vendor and an individual or business such that the underbanked and unbanked module may execute a single sign on (SSO) and redirect the customer to pages hosted by the third party vendor that facilitate the transfer of funds, a page hosted by a third party vendor wherein a session status is maintained through a PING URL embedded in a third party header, served from the underbanked and unbanked module that the third party vendor incorporates into its design;
providing a communications interface for displaying the check data and identification data on a client display screen;
the server electronically integrated with the general purpose reloadable prepaid card system, a money remittance system and a bill payment system and the general purpose reloadable prepaid card system, a money remittance system and a bill payment system, integrated with each other to allow a customer to use the funds dispensed from the underbanked and unbanked module, load a general purpose reloadable prepaid card with these funds, pay for purchases, pay bills, or obtain a money order.
verifying the name, physical address, social security number, date of birth and government issued photo ID of the customer.
wherein the funds dispensed to the customer comprise cash.
wherein the funds dispensed to the customer are used to facilitate cash to cash money transfers, bill payments and/or money orders.
wherein the funds for the general purpose reloadable prepaid card comprise cash.
loading the general purpose reloadable prepaid card with funds from an existing account at the financial institution associated with the underbanked and unbanked module.
wherein the funds for the general purpose reloadable prepaid card are directly deposited onto the card.
wherein the funds directly deposited onto the general purpose reloadable prepaid card comprise the customer’s wages, tax refunds and/or state disbursements.
wherein the funds are loaded onto the general purpose reloadable prepaid card at the financial institution associated with the underbanked and unbanked module.
wherein the funds are loaded onto the reloadable card at a network location other than the financial institution associated with the underbanked and unbanked module.
using the funds dispensed to the customer to provide a line of credit to the customer based on the customer’s deposit history, at a location other than the financial institution.
using the funds dispensed to the customer to provide a short term loan or pay day advance to the customer.
Based on the limitations above, the claims describe a process that covers facilitating banking activity for unbanked or underbanked customer. Facilitating banking activity for unbanked or underbanked customer is considered to be a commercial interaction, which falls within the “Certain Methods of Organizing Human Activity” grouping of abstract ideas. As such, the claim(s) recite(s) a Judicial Exception. (Step 2A prong one: Yes)
This analysis then evaluates whether the claims as a whole integrates the recited Judicial Exception into a practical application of the exception. In particular, the claims recite the additional element(s) of “processor”, “computer system”, “… system”, “computer logic” and “… module” as a mere tool to perform the … steps of the Judicial Exception, which encompasses no more than Mere Instruction to Apply.
For example, the limitation “providing a processor based enrollment system including a requesting client computer system including an input/output interface that enables wired or wireless connection to a mobile phone and providing a computer logic stored in a main memory or secondary memory as the controller of the processor based enrollment system containing instructions directing the enrollment of a customer in an underbanked and unbanked module and a communications interface for enrolling a customer in the underbanked and unbanked module associated with a financial institution by verifying the customer’s information regardless of whether the customer is a deposit or non-deposit customer of said financial institution”, encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of providing interaction session for enrolling a customer via verification;
the limitation “receiving, with a central processing unit as a data receiver, check data and identification data from the requesting client computer system, the data receiver in communication with a check verification system, the check verification system applying scanned check data for decisioning” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of receiving check data and identification data from the customer client, wherein the check data is scanned;
the limitation “creating an interface between the third party check verification system and a bill payment system” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of facilitating communication between the third party check verifier and bill payment processor;
the limitation “providing a server to response to the request client computer system, retrieve the requested page, retrieve check and identification data and transmit the check and identification data over a communications data channel transmit data for the page back to the requesting client computer system, display the selected page, launching an application to perform an analysis” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of retrieving check and identification data and sending the data over communication channel to make available to the requestor;
the limitation “verifying with the check verification system said check data and identification data;” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of verifying the data;
the limitation “upon verifying said check data, dispensing funds to the customer with a funds dispenser” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of dispensing fund to customer upon verification;
the limitation “loading … a general purpose reloadable prepaid card electronically” language, “loading funds onto a general purpose reloadable prepaid card electronically;” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of loading fund to an account represented by the reloadable prepaid card;
the limitation “facilitating cash to cash money transfers over the communications data channel;” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of facilitating cash to cash money transfer;
the limitation “facilitating bill payments to a network of billers over the communications data channel” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of facilitating bill payment;
the limitation “applying a graphical user interface (GUI) to on the requesting client computer system and to facilitate customer creation and enrollment, the GUI creating a first interface between a third party vendor capable of providing check verification and the underbanked and unbanked module and a second interface between the third party vendor and an individual or business such that the underbanked and unbanked module may execute a single sign on (SSO) and redirect the customer to pages hosted by the third party vendor that facilitate the transfer of funds, a page hosted by a third party vendor wherein a session status is maintained through a PING URL embedded in a third party header, served from the underbanked and unbanked module that the third party vendor incorporates into its design” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of facilitating customer creation and enrollment, while the creation of interface between parties encompasses one or more human agent manually facilitating referrals between parties such that the customer can be authenticated with a single sign on and be redirected to a third party vendor that facilitates transfer of funds.
the limitation “providing a communications interface for displaying the check data and identification data on a client display screen” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of presenting the check data and identification data;
the limitation “verifying the name, physical address, social security number, date of birth and government issued photo ID of the customer” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of verifying the data;
the limitation “using the funds dispensed to the customer to provide a line of credit to the customer based on the customer’s deposit history, at a location other than the financial institution; using the funds dispensed to the customer to provide a short term loan or pay day advance to the customer” encompasses no more than generically invoking generic computing elements to apply the Judicial Exception step of using the fund dispensed for credit purposes.
Other than being generally linked to the steps of the Judicial Exception, the additional elements in the above step(s) is/are recited at a high-level of generality, without technological detail of how the particular steps are performed technologically. The additional element(s) of “memory” and/or “non-transitory storage medium” are generically recited to store data and/or instructions of the Judicial Exception.
The additional element(s) of “communication interfaces”, “a central processing unit as a data receiver” and “an input/output interface that enables wired or wireless connection to a mobile phone” are generically recited to perform communication steps such as receiving and transmitting.
The additional element(s) of “Graphical User Interface” are generically recited to perform input/output steps described only by a result-oriented solution with insufficient detail for how the interface accomplish it.
The additional element(s) of “a Packet Internet or Inter-Network Grouper (PING) Uniform Resource Locator (URL) embedded in a … header” is generically recited to perform the maintaining of a session status described only by a result-oriented solution with insufficient detail for how the interface accomplish it
The examiner further noted generic computer affixes such as “system” and “module” are appended to abstract elements such as “general purpose reloadable prepaid card system”, “a money remittance system” and “a bill payment system”, but found that to be mere instructions to implement the Judicial Exception idea on a computer.
Indeed, the instant claims (1) attempted to cover a solution to an identified problem with no restriction on how the result is accomplished and no description of the mechanism for accomplishing the result; (2) used of a computer or other machinery in its ordinary capacity for economic or other tasks or simply added a general purpose computer or computer components after the fact to the Judicial Exception and (3) generally applied the Judicial Exception to a generic computing environment without limitation indicative of practical application (See MPEP 2106.04(d)I). Thus, the claims are no more than Mere Instruction to Apply the Judicial Exception (See MPEP 2106.05(f)) or adding insignificant extra-solution activity to the judicial exception (See MPEP 2106.05(g)), which do not integrate the cited Judicial Exception into practical application (Step 2A prong two: No) The claims are directed to a Judicial Exception.
The claim does 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 element of using a processor to facilitating banking activities amount to no more than mere instructions to apply the exception using generic computer components. The recited ordered combination of additional elements includes non-meaningfully applying the Judicial Exception to a generic computing environment. Mere instructions to apply an exception using a generic computer component cannot provide an inventive concept. Dependent claim 3, 7- 10, 17-20, 22--30 merely limit the abstract idea but do not recite any additional element beyond the cited abstract idea, thus, do not amount to significantly more. No additional element currently recited in the claims amount the claims to be significantly more than the cited abstract idea. (Step 2B: No)
Therefore, claims 1-13, 15-20 and 22-30 are rejected under 35 U.S.C. 101 as being directed to non-statutory subject matter.
Response to Arguments
Applicant's arguments filed 03/20/2026 have been fully considered but they are not persuasive.
Regarding the applicant’s argument that the claims contain sufficient technological detail of how the steps are to be achieved, the examiner respectfully disagrees. The examiner noted that examples included in Remark page 9-11 only discloses what additional element performs what step, but not how the steps are achieved. As explained in the rejection, the role of the claimed additional elements remain to be nominally invoked to perform the steps of Judicial Exception. For example, the interfaces are nominally recited to perform the communicating step of the Judicial Exception. It should be noted that the technological details, such as specific communication protocol or the sequence of packet exchange, are absent from the disclosure. The disclosure only invoked non-specific interface to desirably perform the communicate, suggesting the technology of interface is not what the applicant sought to patent. Such implication further support the Office Action’s finding that the additional elements are only nominally invoked as Mere Instruction to Apply the Judicial Exception. Thus, the argument is not persuasive.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHO KWONG whose telephone number is (571)270-7955. The examiner can normally be reached 9am - 5pm EST M-F.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, MICHAEL W ANDERSON can be reached at 571-270-0508. 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.
/CHO YIU KWONG/Primary Examiner, Art Unit 3693
Prosecution Insights