Patent ID: 12260397

DETAILED DESCRIPTION

The illustrative embodiments recognize and take into account one or more different considerations. For example, the illustrative embodiments recognize and take into account a number of different bank accounts from different banks or brokerage accounts that an employee may have to use in financial transactions. Moreover, the illustrative embodiments recognize and take into account a number of different debit cards from the different banks that the employee may have to use in the financial transactions.

The illustrative embodiments further recognize and take into account a number of different credit cards from different service providers that the employee may have to use in the financial transactions. The illustrative embodiments recognize and take into account a number of statements that the employee may have to read, check, and manage for the number of different bank accounts, brokerage accounts, and credit card service providers.

The illustrative embodiments recognize and take into account that there have been many attempts to consolidate financial transactions. For example, Apple® and Google® have provided payment systems that consolidate at least some transactions. The illustrative embodiments recognize and take into account that the payment systems provided by Apple® and Google® require a vendor to adopt new, sophisticated, and expensive equipment in order to validate purchases. Therefore, only some vendors offer these types of payment systems that consolidate some transactions.

The illustrative embodiments recognize and take into account that a need exists for a system that validates all purchases. The illustrative embodiments recognize and take into account that a system that validates all purchases may use an electronic wallet or a single paycard. Moreover, the illustrative embodiments recognize and take into account that a system that makes purchases using an electronic wallet or single paycard must also route the purchases from the electronic wallet or the single paycard in a manner that allows payment without a requirement for additional equipment at a vendor location. The illustrative embodiments recognize and take into account that such a payment system may allow a user to route the purchases from the electronic wallet or the single paycard to an existing platform and current commercial system.

The illustrative embodiments recognize and take into account that an electronic wallet and single paycard may have a single payment number for transactions. The illustrative embodiments recognize and take into account that a single payment number for transactions may be tied to a payment technology gateway. The payment technology gateway may provide a display for touchscreen input or swiping input. A transaction may be performed using the single payment number by the electronic wallet or the single paycard, and the transaction may be routed to a specific account previously designated by the user. In an illustrative example, a person having the electronic wallet or the single paycard may go to a grocery store and use the electronic wallet or the single paycard at the register to pay for purchases. At the register, the person may display a number of credit cards on the electronic wallet. The person may swipe the image of the card they select to use for the purchases, and the electronic wallet will complete the purchase using the single payment number and route the transaction to a selected card account. Alternatively, the person may use the single paycard to pay for the purchases and the transaction will be routed to a card chosen in advance by the user. Such a choice may be based on a policy defined by the user such as use of a particular card for a particular type of purchase.

The illustrative embodiments recognize and take into account that a payment technology gateway that provides an electronic wallet and single paycard may analyze purchases and make recommendations on how best to use funds available to the user. Furthermore, the illustrative embodiments recognize and take into account that machine intelligence may be employed to analyze the purchases and make recommendations on how best to use the funds available to the user.

The illustrative embodiments recognize and take into account that an electronic wallet, in addition to a number of credit cards, may include identification cards and insurance cards. The electronic wallet may show, responsive to selection of an identification card or an insurance card, additional details and actions related to the respective identification card and insurance card.

The illustrative embodiments recognize and take into account that an electronic wallet containing identification may be used as a scan card for entry to a workplace or a facility requiring identification to enter or otherwise to be granted access. In an illustrative example, the electronic wallet displaying the identification may be used to clock in and clock out of a workplace. The illustrative embodiments recognize and take into account that an electronic wallet containing insurance cards may be used as access cards for multiple family members and be configured for presentation at care facilities and doctor offices. Thus, a method and apparatus that would allow for a payment technology gateway validated by a single payment number would fill a long-felt need in the field of consolidating financial transactions.

The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatuses and methods in an illustrative embodiment. In this regard, each block in the flowcharts or block diagrams may represent at least one of a module, a segment, a function, or a portion of an operation or step. For example, one or more of the blocks may be implemented as program code.

In some alternative implementations of an illustrative embodiment, the function or functions noted in the blocks may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession may be performed substantially concurrently, or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved. Also, other blocks may be added, in addition to the illustrated blocks, in a flowchart or block diagram.

As used herein, the phrase “at least one of,” when used with a list of items, means different combinations of one or more of the listed items may be used and only one of each item in the list may be needed. In other words, “at least one of” means any combination of items and number of items may be used from the list, but not all of the items in the list are required. The item may be a particular object, thing, or a category.

For example, without limitation, “at least one of item A, item B, or item C” may include item A, item A and item B, or item B. This example also may include item A, item B, and item C or item B and item C. Of course, any combinations of these items may be present. In some illustrative examples, “at least one of” may be, for example, without limitation, two of item A, one of item B, and ten of item C; four of item B and seven of item C; or other suitable combinations.

Thus, in one illustrative embodiment, one or more technical solutions are present that overcome a technical problem in the area of consolidating financial transactions. A method, computer system, and computer program product for consolidating financial transactions of an employee in a payment technology gateway is provided. The payment technology gateway comprises an electronic wallet linked to a payment technology application and a paycard linked to the payment technology application. The payment technology gateway is configured to be a single gateway through which the employee conducts financial transactions on a number of accounts using the electronic wallet and the paycard. Each financial transaction is validated by the payment technology gateway using a single payment number. Thus, one or more technical solutions may provide a technical effect of processing transactions more efficiently and conveniently for a user.

Moreover, machine intelligence can be used to analyze and make recommendations to an employee in regard to ways to better utilize funds available to the employee. All of a user's transactions can be conducted at a single gateway and thus a user's entire financial transaction history can be used in analyzing and providing recommendations to the user. Moreover, the electronic wallet and paycard may be used as identification for access and for clocking in and clocking out by employees. Therefore, increased speed and accuracy in authenticating employees and tracking employee time for payroll may be achieved. The increased speed and accuracy may be reflected in reduced process time and reduced memory and storage usage. Reduced processor time may be for processor unit2404inFIG.24. Reduced memory and storage may be for memory2406and persistent storage2408inFIG.24.

With reference now to the figures and, in particular, with reference toFIG.1, a diagram of a data processing environment is depicted in accordance with an illustrative embodiment. It should be appreciated thatFIG.1is only provided as an illustration of one implementation and is not intended to imply any limitation with regard to the environments in which the different embodiments may be implemented. Many modifications to the depicted environments may be made.

The computer-readable program instructions may also be loaded onto a computer, a programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, programmable apparatus, or other device to produce a computer-implemented process, such that the instructions which execute on the computer, programmable apparatus, or other device implement the functions and/or acts specified in the flowchart and/or block diagram block or blocks.

FIG.1depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Network data processing system100is a network of computers in which the illustrative embodiments may be implemented. Network data processing system100contains network102, which is the medium used to provide communications links between various devices and computers connected together within network data processing system100. Network102may include connections, such as wire, wireless communication links, or fiber optic cables.

In the depicted example, server computer104and server computer106connect to network102along with storage unit108. In addition, client computers include client computer110, client computer112, and client computer114. Client computer110, client computer112, and client computer114connect to network102. These connections can be wireless or wired connections depending on the implementation. Client computer110, client computer112, and client computer114may be, for example, personal computers or network computers. In the depicted example, server computer104provides information, such as boot files, operating system images, and applications to client computer110, client computer112, and client computer114. Client computer110, client computer112, and client computer114are clients to server computer104in this example. Network data processing system100may include additional server computers, client computers, and other devices not shown.

Program code located in network data processing system100may be stored on a computer-recordable storage medium and downloaded to a data processing system or other device for use. For example, program code may be stored on a computer-recordable storage medium on server computer104and downloaded to client computer110over network102for use on client computer110.

In the depicted example, network data processing system100is the Internet with network102representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers consisting of thousands of commercial, governmental, educational, and other computer systems that route data and messages. Of course, network data processing system100also may be implemented as a number of different types of networks, such as, for example, an intranet, a local area network (LAN), or a wide area network (WAN).FIG.1is intended as an example, and not as an architectural limitation for the different illustrative embodiments.

The illustration of network data processing system100is not meant to limit the manner in which other illustrative embodiments can be implemented. For example, other client computers may be used in addition to or in place of client computer110, client computer112, and client computer114as depicted inFIG.1. For example, client computer110, client computer112, and client computer114may include a tablet computer, a laptop computer, a bus with a vehicle computer, and other suitable types of clients.

In the illustrative examples, the hardware may take the form of a circuit system, an integrated circuit, an application-specific integrated circuit (ASIC), a programmable logic device, or some other suitable type of hardware configured to perform a number of operations. With a programmable logic device, the device may be configured to perform the number of operations. The device may be reconfigured at a later time or may be permanently configured to perform the number of operations. Programmable logic devices include, for example, a programmable logic array, programmable array logic, a field programmable logic array, a field programmable gate array, and other suitable hardware devices. Additionally, the processes may be implemented in organic components integrated with inorganic components and may be comprised entirely of organic components, excluding a human being. For example, the processes may be implemented as circuits in organic semiconductors.

Turning toFIG.2, a block diagram of a computer system for consolidating financial transactions of an employee in a payment technology gateway is depicted in accordance with an illustrative embodiment. Computer system200comprises data processing system216connected to a number of applications, databases, and devices. The number of applications comprises machine intelligence218, payroll application270, payment technology gateway application230, connections application280, and web page application290. Databases comprise wallet and card database266and enrollee database288. Devices266may comprise non-mobile devices267and mobile devices269.

Data processing system216may be data processing system2400depicted inFIG.24. Machine intelligence218comprises machine learning220, predictive algorithms222, and human algorithms224. Machine intelligence218can be implemented using one or more systems such as an artificial intelligence system, an neural network, a Bayesian network, an expert system, a fuzzy logic system, a genetic algorithm, or other suitable types of systems. Machine intelligence218may work in conjunction with predicting application240, accounting application250, and preferences application244in payment technology gateway application230. Machine intelligence218may be employed to analyze purchases and make recommendations on how best to use funds available to an employee using wallet and card account services262.

Payroll application270comprises payment272, statement preparation274, and coordination with payment technology gateway application276. Payroll application270may be used by an employer to process payroll for employees. In an embodiment, payroll application270may be connected to payment technology gateway application230by coordination with payment technology gateway application276in payroll application270and connection to payroll application242in payment technology gateway application230. In an illustrative embodiment, payments made by payment technology gateway application230may be deducted from payment272and reflected in statement preparation274of payroll application270.

Payment technology gateway application230comprises wallet application232, card application234, identification application236, notification application238, preferences application244, send and redeem application246, connection to payroll application242, accounting application250, displaying application248, predicting application240, team reward application254, and validating application252. Wallet application232may provide an electronic wallet such as electronic wallet604inFIG.6, electronic wallet702inFIG.7, electronic wallet814inFIG.8, electronic wallet902inFIG.9, electronic wallet1002inFIG.10, electronic wallet1102inFIG.11, electronic wallet1202inFIG.12, and electronic wallet1302inFIG.13. Moreover, wallet application232may comprise processes such as process1400inFIG.14, process1500inFIG.15, process1600inFIG.16, and process1700inFIG.17.

Identification application236may provide identification and signing in and signing out capabilities as shown in electronic wallet902inFIG.9and comprise processes such as process1900inFIG.19. Preferences application244may provide preferences as depicted in electronic wallet1002inFIG.10and comprise processes such as process2000inFIG.20. Send and redeem application246may provide a display such as gift display1202and redeem display1239inFIG.12. Send and redeem application246may comprise a process such as process2000inFIG.20. Team reward application250may provide a display such as display1306inFIG.13. Team reward application may comprise a process such as process2100inFIG.21. Accounting application250may provide support for process1500inFIG.15. Displaying application248may provide support for wallet application232inFIGS.6-13. Predicting application240may provide recommendations on spending in conjunction with one or both of accounting application250and machine intelligence218. Validating application252enables the process of step1408inFIG.14and step1804inFIG.18so that each financial transaction is validated by payment technology gateway application230using a single payment number. In an embodiment, the single payment number is a number assigned to a paycard by a financial services provider that issues credit cards and that is selected by the employer to provide the paycard.

Connections application280comprises Internet282, wireless284, and others286. Internet282provides connectivity between payment technology gateway292, data processing system216, and payment technology gateway application230. Web page application290provides payment technology gateway292. Payment technology gateway292may be configured as an interface between an employee and payment technology gateway application230.

Wallet and card data260comprises wallet and card account services262, wallet and card usage history264, wallet and card database266, and payrolls268. Wallet and card database266may further comprise wallet and card database400inFIG.4.

Computer system200may use one or more programs such as machine intelligence218, payroll application270, payment technology gateway application230, connections application280, and web page application290in conjunction with wallet and card database266and enrollee database288in order to consolidate financial transactions of an employee in a payment technology gateway such as payment technology gateway292. As a result, computer system200operates as a special purpose computer system for providing an electronic wallet and a single paycard to consolidate financial transactions of an employee in a payment technology gateway. Thus, payment technology application230transforms computer system200into a special purpose computer system as compared to currently available general computer systems that do not have a means to consolidate financial transactions such as computer system200ofFIG.2and as further described inFIGS.3-23.

Moreover, currently used general computer systems do not provide a data processing system such as data processing system216configured by payment technology gateway application230in communication with databases such as wallet and card database266and enrollee database288to provide consolidated financial transactions as further described inFIGS.3-23. Moreover, currently used general computer systems do not provide connectivity between a single electronic wallet and a single paycard with a payment technology gateway such as payment technology gateway292.

Turning toFIG.3, a block diagram of an enrollee database is depicted in accordance with an illustrative embodiment. Enrollee database300may be enrollee database288inFIG.2. Enrollee database300may comprise paycard account310, electronic wallet account314, enrollees320, paycard data330, and electronic wallet data340. Paycard account310may comprise delivery links312. Electronic wallet account314may comprise delivery links316. Enrollees320may comprise contracts322, security324, and legal326. Paycard data330may comprise paycard enrollments332, paycard accounts334, paycard notifications338, and paycard delivery schedules339. Paycard accounts334may further comprise paycard statements336. Electronic wallet data340may comprise electronic wallet enrollments342, electronic wallet accounts344, electronic wallet notifications348, and electronic wallet delivery schedules349. Electronic wallet accounts344may further comprise electronic wallet statements346.

Turning toFIG.4, a block diagram of an electronic wallet and paycard database is depicted in accordance with an illustrative embodiment. Electronic wallet and paycard database400may comprise bank account1402, bank account2404, credit card1406, credit card2408, credit card3410, FSH/HSA account1412, FSH/HSA account414, internet protocol (IP) addresses416, mobile device numbers418, email addresses420, billing data1422, billing data2424, peer-to-peer address1426, peer-to-peer address2428, team address1430, and team address432. In the illustrative example of electronic wallet and paycard database400, a number of credit cards, accounts, and information is shown by way of example. Persons skilled in the art know and take into account that any number of credit cards, accounts, and different types of information may be stored in electronic wallet and paycard database400.

Turning toFIG.5, a block diagram of an interface with a payment technology gateway application is depicted in accordance with an illustrative embodiment. Web page500comprises enrollment502, enter data504, and enter authorizations506. In the illustrative example of web page500, a number of selections are depicted which would lead to additional pages with additions selections and entry icons. Web page500is presented by way of illustrative example. Persons skilled in the art recognize and take into account that web page500may be configured in any number of ways to support computer system200inFIG.2.

Turning toFIG.6, an illustration of a mobile device displaying an electronic wallet is depicted in accordance with an illustrative embodiment. Electronic wallet600comprises mobile device602and a number of cards such as identification cards, credit cards, or insurance cards. In an illustrative example, the number of cards may comprise identification card620, health insurance card622, paycard624, and health insurance identification card626. Electronic wallet display604shows a selected card and a number of partially disclosed cards representing cards pocketed in a wallet, and therefore, referred to as a pocketed card. A card may be selected as an active card by swiping one of the number of partially disclosed cards. In the illustrative example, health identification card626is shown as first pocketed card608, a credit card is shown as second pocketed card610, health insurance card622is shown as third pocketed card612, and identification card620is shown as fourth pocketed card614. Paycard624is shown as an active card above the pocketed cards. Active card606is ready for a transaction. Electronic wallet600may be configured by wallet application232of payment technology gateway230inFIG.2. Electronic wallet600may be implemented by process1400inFIG.14, process1600inFIG.14, and process1700inFIG.17.

Turning toFIG.7, an illustration of an electronic wallet transaction display is depicted in accordance with an illustrative embodiment. Electronic wallet700is depicted with an active card display. Mobile device702is shown on the left as depicted inFIG.6. Mobile device702is shown on the right with a different wallet display. Wallet display701shows active card606inFIG.6along with a number of transactions. In the illustrative example, first transaction710is for $42.89, second transaction712is for $14.36, third transaction714is for $78.64, and fourth transaction716is for $21.93. Wallet display701provides for a selection of recent704, categories706, and statements708. In the illustrative example, a user has selected recent704and recent transactions are displayed comprising first transaction710, second transaction712, third transaction714, and fourth transaction716. Selection of recent704, categories706, and statements708may be made by touching or swiping a selection in wallet display701. Wallet display701may be configured by wallet application232in payment technology gateway230inFIG.2. Wallet display701may be configured by process1800inFIG.18.

Turning toFIG.8, an illustration of a paycard with identification, a paycard, and an electronic wallet are depicted in accordance with an illustrative example. Electronic wallet700is shown with paycard and identification card810. Paycard and identification card810represents a paycard that has passive proximity technology. Paycard and identification card810may be a paycard with contactless smart card technology with an EMV chip. Paycard812represents a paycard with an EMV chip only. Both cards may be pocketed in electronic wallet814for selection as an active card. In the illustrative example, paycard812has been selected as an active card in electronic wallet814. Paycard812and paycard and identification card810may be configured by identification application236in payment technology gateway application230inFIG.2. Paycard812may be configured by card application234in payment technology gateway application230inFIG.2. Electronic wallet814may be configured by wallet application232in payment technology gateway application230inFIG.2.

Turning toFIG.9, an illustration of an application of an electronic wallet with identification for an employee clocking in and clocking out is depicted in accordance with an illustrative embodiment. Electronic wallet employee clock in and clock out system900comprises mobile device902displaying an electronic wallet display with identification card904selected as an active card. When identification card904is selected as an active card, electronic wallet employee clock in and clock out system900displays status906, time908, selector910, history selection914, and duration of last period916. An employee clocks in by touching or swiping selector910which states “clock in”. Immediately after swiping selector910, status906changes from “clocked out” to “clocked in” and selector910now states “clock out”. The foregoing changes are depicted on the right hand view of wallet display902. The electronic wallet display with identification card904may be configured by process1900inFIG.19.

Turning toFIG.10, an illustration of a display screen for selecting preferences is depicted in accordance with an illustrative embodiment. Electronic wallet for selecting preferences1000is shown with mobile device1002, employee picture1004, name and position1006, and a display offering selections of “treat preferences”1008and “goals”1016. First treat preference1010, second treat preference1012, and third treat preference1014are shown. First treat preference1010may be time off. Second treat preference1012may be a coffee drink. Third treat preference1014may be a gift card. First goal1018, second goal1020, and third goal1022are shown. First goal1018may depict sales pipeline success1024. Second goal1020may be “team kudos”1026. Third goal1022may be customer campaigns1028. Electronic wallet1002may be configured to select preferences by preferences application244of payment technology gateway application230inFIG.2. Preferences application244may use process1700inFIG.17. The display screen for selecting preferences inFIG.10is presented by way of illustrative example. Persons skilled in the art recognize and take into account that display screen for selecting preferences may show preferences or less preferences and may show different preferences.

Turning toFIG.11, an illustration of an alert notification is depicted in accordance with an illustrative embodiment. Electronic wallet1100may have wallet display1102overshadowed by alert notification screen1104. Alert notification screen1104may provide instant alerts on ways to save or how to better use accounts in mobile device1102. In the illustrative example, a user may select “yes”1110or “no”1108by touching or swiping alert notification display1104in answer to the query caption “Would you like to use our HSA account for HSA eligible purchases?”1106. Alert notification screen1104may be configured by notification application238inFIG.2. Notification application238may employ process1700inFIG.17.

Turning toFIG.12, an illustration of send and redeem screens in an electronic wallet are depicted in accordance with an illustrative embodiment. Electronic wallet1200has send screen1204in mobile device1202that allows a user to send digital treats or cash and to pay for the digital treat or cash using any card in the electronic wallet. In the illustrative example, a vista gift card has been chosen as a treat with an amount selected from first amount1212, second amount1214, third amount1216, fourth amount1218, fifth amount1220, and sixth amount1222. Once an amount is selected, a payment method may be selected in payment method portion of display1224. In the illustrative example, payment method1226has been selected. The selected treat may be sent by touching or swiping “send treat” control1228. Moreover, using beacon technology, electronic wallet1202may prompt a user and send a notification with a suggestion to redeem digital treats. Redeem treat display1230identifies treat1232and provides an expiration date and information1236regarding treat1232. A recipient may redeem treat1232by touching or swiping “redeem” control1234. Send screen1204and redeem treat display1230may be configured by send and redeem application246in payment technology gateway application230inFIG.2. Send and redeem application246may employ process2000inFIG.20.

Turning toFIG.13, an illustration of a display for sending treats to team members is depicted in accordance with an illustrative embodiment. Electronic wallet1300is shown with treats display1304in mobile device1302. Team members1306comprises first team member1308, second team member1310, third team member1312, fourth team member1314, and fifth team member1316are shown out of a total of twelve team members. Additional team members may be displayed by swiping the display up to scroll for additional team members. Using treats display1302, a user may find team members and award them gifts or cash from any of the accounts in electronic wallet1300. The user may manage or receive gifts or cash from other electronic account members. Electronic wallet1300may be configured by team reward application250inFIG.2. Team reward application250may employ process2100inFIG.21.

Turning toFIG.14, a flowchart of a process for a computer-implemented method for consolidating financial transactions of an employee in a payment technology gateway is depicted in accordance with an illustrative embodiment. Process1400can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1400can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1400starts. A payment technology gateway having a payment technology application is established by an employer's data processing system (step1402). The employer's data processing system provides an electronic wallet application linked to the payment technology application (step1404). The employer's data processing system provides a paycard linked to the payment technology application (step1406). The payment technology gateway is configured to be a single gateway through which an employee conducts financial transactions on a number of accounts using the electronic wallet and the paycard so that each financial transaction is validated by the payment technology gateway using a single payment number (step1408). Process1400ends thereafter. The payment technology gateway may be payment technology gateway230inFIG.2.

Turning toFIG.15, a flowchart of a process for enabling management of a number of accounts on an electronic wallet is depicted in accordance with an illustrative embodiment. Process1500can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1500can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1500starts. An employer's data processing system provides a wallet display enabling an employee to interface with a payment technology application (step1502). An interface may be with payment technology application230and the interface may be payment technology gateway292inFIG.2. The wallet display enables management of transactions on a number of accounts (step1504). Process1500ends. The number of accounts may include credit card accounts, bank accounts, personal identification, insurance accounts, mortgage accounts, and FSH accounts and HSA accounts. The wallet display may be downloadable to a portable device by one of an internet connection and a wireless connection. The payment technology application may be payment technology gateway application230inFIG.2.

Turning toFIG.16, a flowchart of a process for linking credit cards to an electronic wallet and enabling a selection of an active card on the electronic wallet is depicted in accordance with an illustrative embodiment. Process1600can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1600can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1600starts. Responsive to entry by an employee on a wallet display of a number of credit cards issued to the employee by a number of credit card providers, an electronic wallet is linked to each of the number of credit cards issued to the employee so that a charge incurred using an active card will be passed through to one of the number of credit cards by a payment technology gateway application in accordance with a selection of one of the number of credit cards by the employee as the active card (step1602). The employee is enabled to select the active card by touching or swiping the wallet display on a portable device (step1604). Process1600ends. The portable device may be an electronic wallet such as electronic wallet604inFIG.6.

Turning toFIG.17, a flowchart of a process for previewing balances, viewing accounts, managing settings, alerts, and notifications, and directing reports is depicted in accordance with an illustrative embodiment. Process1700can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1700can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1700starts. An employee, using an electronic wallet application and a wallet display, is enabled to preview a number of balances in a number of accounts (step1702). The employee, using the electronic wallet application and the wallet display, is enabled to create transaction categories (step1704). The employee, using the electronic wallet application and the wallet display, is enabled to view statements and a use history (step1706). The employee, using the electronic wallet application and the wallet display, is enabled to manage notification settings, alerts, and reminders (step1708). The employee, using the electronic wallet application and the wallet display, is enabled to send one or both of gifts and cash to peers (step1710). The employee, using the electronic wallet application and the wallet display, is enabled to direct reports (step1712). Process1700ends. The electronic wallet may be electronic wallet604inFIG.6.

Turning toFIG.18, a flowchart of a process for using a card interface to link a number of cards to a paycard is depicted in accordance with an illustrative embodiment. Process1800can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1800can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1800starts. A card interface is provided for data entry by an employee (step1802). Responsive to entry by the employee on the card interface of a number of credit cards issued to the employee by a number of credit card providers, a paycard is linked to each of the number of credit cards issued to the employee so that a charge incurred using the paycard will be passed through to one of the number of credit cards by a payment technology application in accordance with a pre-designated policy selected by the employee (step1804). Process1800ends thereafter. The card interface may be one of a computer card interface or a mobile device interface. The paycard may include an EMV chip. The paycard may be paycard810or paycard812inFIG.8.

Turning toFIG.19, a flowchart of a process for enabling an electronic wallet as an identification card is depicted in accordance with an illustrative embodiment. Process1900can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process1900can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process1900starts. An identification application linked to a payment technology application, an electronic wallet, and a paycard is provided (step1902). The paycard is provided with one of passive proximity technology and contactless smart card technology (step1904). The electronic wallet is provided with a matrix barcode for scanning (step1906). The paycard and the electronic wallet are configured to clock an employee in and out at work (step1908). Process1900ends. The electronic wallet and the identification application are configured to display a history of the employee clocking in and out (step1910). The paycard may be paycard810or paycard812inFIG.8.

Turning toFIG.20, a flowchart of a process for providing preferences on an electronic wallet is depicted in accordance with an illustrative embodiment. Process2000can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process2000can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process2000starts. A preferences application linked to a payment technology application, an electronic wallet, and a paycard is provided (step2002). The preferences application is configured for a selection of treat preferences, entry of goals by an employee, the entry of goals directed to team members, display of goal progress, and direction of reports (step2004). A notification application linked to the payment technology application and the electronic wallet is provided (step2006). The electronic wallet is configured to display instant alerts on ways to save or how to better use one or more of a number of accounts in the electronic wallet (step2008). A send and redeem application linked to the payment technology application and the electronic wallet is provided (step2010). The electronic wallet is configured to send and receive digital treats, to send and receive cash, to pay for a first digital treat, and to receive a second digital treat using any card in the electronic wallet (step2012). The electronic wallet is configured with beacon technology to prompt and send notifications regarding a suggestion to redeem a digital treat. Process2000ends. Process2000may be coded in send and redeem application246inFIG.2.

Turning toFIG.21, a flowchart of a process for providing a team reward application on an electronic wallet is depicted in accordance with an illustrative embodiment. Process2100can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process2100can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process2100starts. A team reward application linked to a payment technology application and an electronic wallet is provided (step2102). Responsive to one or more inputs by an employee on a display of the electronic wallet, a team member is found, and the team member is awarded a gift or cash from any of a number of accounts in the electronic wallet (step2104). A team reward application is configured to manage gifts or cash sent from another electronic wallet to the employee (step2106). Process2100ends. Process2100may be coded in team reward application254inFIG.2.

Turning toFIG.22, a flowchart of a process for providing peer-to-peer payments between employees enrolled in a payment technology gateway is depicted in accordance with an illustrative embodiment. Process2200can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process2200can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process2200starts. A payment technology application provides a mechanism for peer-to-peer payments between employees enrolled in the payment technology gateway, wherein the mechanism employs one of an electronic wallet and a paycard (step2202). Process2200ends. Peer-to-peer payments may be enabled by accounting250in payment and technology gateway230.

Turning toFIG.23, a flowchart of a process for analyzing purchases made by an employee using an electronic wallet and a paycard is depicted in accordance with an illustrative embodiment. Process2300can be implemented in software, hardware, or a combination of the two. When software is used, the software comprises program code that can be loaded from a storage device and run by a processor unit in a computer system such as computer system200inFIG.2. Computer system200may reside in a network data processing system such as network data processing system100inFIG.1. For example, computer system200may reside on one or more of server computer104, server computer106, client computer110, client computer112, and client computer114connected by network102inFIG.1. Moreover, process2300can be implemented by data processing system2400inFIG.24and a processing unit such as processor unit2404inFIG.24.

Process2300starts. A consolidated financial transaction service is configured to analyze purchases made by an employee using an electronic wallet and a paycard and to make recommendations on how the employee may best use available funds (step2302). Process2300ends.

Turning now toFIG.24, an illustration of a block diagram of a data processing system is depicted in accordance with an illustrative embodiment. Data processing system2400may be used to implement one or more computers and computer system112inFIG.1. In this illustrative example, data processing system2400includes communications framework2402, which provides communications between processor unit2404, memory2406, persistent storage2408, communications unit2410, input/output unit2412, and display2414. In this example, communications framework2402may take the form of a bus system.

Processor unit2404serves to execute instructions for software that may be loaded into memory2406. Processor unit2404may be a number of processors, a multi-processor core, or some other type of processor, depending on the particular implementation. Memory2406and persistent storage2418are examples of storage devices2416. A storage device is any piece of hardware that is capable of storing information, such as, for example, without limitation, at least one of data, program code in functional form, or other suitable information either on a temporary basis, a permanent basis, or both on a temporary basis and a permanent basis. Storage devices2416may also be referred to as computer-readable storage devices in these illustrative examples. Memory2406, in these examples, may be, for example, a random access memory or any other suitable volatile or non-volatile storage device. Persistent storage2408may take various forms, depending on the particular implementation.

For example, persistent storage2408may contain one or more components or devices. For example, persistent storage2408may be a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage2408also may be removable. For example, a removable hard drive may be used for persistent storage2408. Communications unit2410, in these illustrative examples, provides for communications with other data processing systems or devices. In these illustrative examples, communications unit2410is a network interface card.

Input/output unit2412allows for input and output of data with other devices that may be connected to data processing system2400. For example, input/output unit2412may provide a connection for user input through at least of a keyboard, a mouse, or some other suitable input device. Further, input/output unit2412may send output to a printer. Display2412provides a mechanism to display information to a user.

Instructions for at least one of the operating system, applications, or programs may be located in storage devices2416, which are in communication with processor unit2404through communications framework2402. The processes of the different embodiments may be performed by processor unit2404using computer-implemented instructions, which may be located in a memory, such as memory2406.

These instructions are referred to as program code, computer-usable program code, or computer-readable program code that may be read and executed by a processor in processor unit2404. The program code in the different embodiments may be embodied on different physical or computer-readable storage media, such as memory2406or persistent storage2408.

Program code2418is located in a functional form on computer-readable media2420that is selectively removable and may be loaded onto or transferred to data processing system2400for execution by processor unit2404. Program code2418and computer-readable media2420form computer program product2422in these illustrative examples. In one example, computer-readable media2420may be computer-readable storage media2424or computer-readable signal media2426.

In these illustrative examples, computer-readable storage media2424is a physical or tangible storage device used to store program code2418rather than a medium that propagates or transmits program code2418. Alternatively, program code2418may be transferred to data processing system2400using computer-readable signal media2426.

Computer-readable signal media2426may be, for example, a propagated data signal containing program code2418. For example, computer-readable signal media2426may be at least one of an electromagnetic signal, an optical signal, or any other suitable type of signal. These signals may be transmitted over at least one of communications links, such as wireless communications links, optical fiber cable, coaxial cable, a wire, or any other suitable type of communications link.

The different components illustrated for data processing system2400are not meant to provide architectural limitations to the manner in which different embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system including components in addition to or in place of those illustrated for data processing system2400. Other components shown inFIG.24can be varied from the illustrative examples shown. The different embodiments may be implemented using any hardware device or system capable of running program code2418.

The flowcharts and block diagrams in the different depicted embodiments illustrate the architecture, functionality, and operation of some possible implementations of apparatuses and methods in an illustrative embodiment. In this regard, each block in the flowcharts or block diagrams may represent at least one of a module, a segment, a function, or a portion of an operation or step. For example, one or more of the blocks may be implemented as program code.

In some alternative implementations of an illustrative embodiment, the function or functions noted in the blocks may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession may be performed substantially concurrently, or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved. Also, other blocks may be added in addition to the illustrated blocks in a flowchart or block diagram.

The description of the different illustrative embodiments has been presented for purposes of illustration and description and is not intended to be exhaustive or limited to the embodiments in the form disclosed. The different illustrative examples describe components that perform actions or operations. In an illustrative embodiment, a component may be configured to perform the action or operation described. For example, the component may have a configuration or design for a structure that provides the component an ability to perform the action or operation that is described in the illustrative examples as being performed by the component.

Many modifications and variations will be apparent to those of ordinary skill in the art. Further, different illustrative embodiments may provide different features as compared to other desirable embodiments. The embodiment or embodiments selected are chosen and described in order to best explain the principles of the embodiments, the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.