Patent Application
20210042719
With advancements in machine and product development, more and more machines and products are being interconnected via wireless internet channels. Currently the security and efficiency in the field of resource distributions lead to complexity. As such, there is a need for improved resource distribution systems that can provide advanced, efficient, and more secure user communications.
The following presents a simplified summary of one or more embodiments of the invention in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments, nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.
Embodiments of the present invention address these and/or other needs by providing an innovative system, method and computer program product for cardless and paperless resource transfer of allocated resources based on wireless user authentication.
In some embodiments, the invention allows for quicker and more secure resource transfer by eliminating the need for dual messaging and user security breaches. For example, the resource transmittal device will allow users to view resource transfer data from a third party, add or modify a resource transfer input, and verify and authenticate the cardless and paperless resource transfer, all in a single resource transfer message. For example, a user can add a tip or split the bill amongst many users on the portable resource transmittal device. This invention automatically transmits a request for authentication credentials based on smart device signals from the invention and device associated with the user. Subsequently, based on approved authentication by the user, the invention triggers release of user resources to complete the resource transfer. Furthermore, the release of user resources will be wireless, cardless, and paperless, preserving user security, enhancing third party efficiency, and limiting third party dual messaging. Furthermore, the invention may communicate with third party inventory and suppliers to generate an automatic inventory update and order for materials for merchant products based on the completion of one or more steps via the portable resource transmittal device. The invention may also communicate with the third party accounting and back end payroll for efficient resource transfer to individuals associated with the third party.
Embodiments of the invention relate to systems, methods, and computer program products for paperless and cardless third party resource transfer processing, the invention comprising: receiving resource transfer data from a third party resource transfer system, wherein the resource transfer data comprises resource requirements for completion by the user; displaying, on a graphical interface, the resource transfer data to a user; receiving resource transfer input from the user; coordinating the resource transfer input and the resource transfer data into a total resource allocation to a resource distribution account associated with the user; prompting a communicable linkage with a user device associated with the user, wherein the communicable linkage receives authentication credentials from the user device; and transmitting a processed total resource allocation to the third party resource transfer system.
In some embodiments, the invention further comprises performing processing on the third party to conduct one or more transactions across the exchange via a cardless resource transfer, wherein the cardless resource transfer occurs via a communicable link between the third party resource transfer system and the user device.
In some embodiments, the invention further comprising performing processing on the third party resource transfer system to track and total resource transfer data and modify current inventory status, wherein modifying the current inventory status comprises updating product inventory based on the processing.
In some embodiments, receiving the resource transfer data from a third party resource transfer system further comprises an itemized graphical display of resource requirements for completion and selection of resource transfer input by the user associated with user purchases.
In some embodiments, the resource transfer input further comprises an additional resource amount about the resource transfer data that creates a total resource allocation to apply to a resource distribution allocation for user payment to complete a transaction to the third party resource transfer system.
In some embodiments, the resource transfer input further comprises an additional resource amount comprising a portion of the resource transfer data that in combination with other portions creates a total resource allocation, wherein the portion of the resource transfer data is applied to a user payment method to complete a transaction to the third party resource transfer system.
In some embodiments, the invention further comprises fetching authentication credentials, wherein authentication credentials comprise wireless communication between the third party resource transfer system and a user device associated with the user via a communicable link.
In some embodiments, the communicable link further comprises wirelessly transmitting a notification for verification of resource distribution account to the user device.
In some embodiments, the resource transfer input and resource transfer data are totaled and cross-referenced via the third party resource transfer system to ensure correct total resource allocation to the third party resource transfer system.
The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, wherein:
Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to elements throughout. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein.
A “user” as used herein may refer to any customer of a third party or an individual that interacts with the third party. In some embodiments, identities of an individual may include online handles, usernames, aliases, family names, maiden names, nicknames, or the like. For purposes of this invention, the term “user” and “user” may be used interchangeably. Furthermore, as used herein the term “user device” or “mobile device” may refer to mobile phones, personal computing devices, tablet computers, wearable devices, and/or any portable electronic device capable of receiving and/or storing data therein.
“Third party” as used herein may refer to an individual or an organization comprising multiple individuals such as an institution or an association that operates a business, like a bank or restaurant, a non-profit organization, a governmental organization, and the like, which may routinely use various types of applications and devices within its environment to conduct resource transfers with a user.
A “resource transfer system” as used herein may refer to the computing systems, devices, software, applications, communication hardware, and/or other resources used by the third party to perform the functions as described herein. Accordingly, the resource transfer system may comprise desktop computers, laptop computers, servers, mobile smartphones, smart devices, network connections, point of sale terminals, networked terminals, secure keypad, and/or other types of computing systems or devices and/or peripherals along with their associated applications used for resource allocation to the third party. In some embodiments, the resource transfer system may include a portable resource transmittal device, third party resource transfer systems, and/or portable resource transmittal system associated with the portable resource transmittal device.
In the context of example implementations described herein, a “resource requirement,” “resource transfer input,” “total resource allocation,” or “resource distribution account” refers to any transfer of resources to and/or from a user. A resource requirement may refer to a purchase of shares of stock, goods, a return of goods or services, a payment transaction, an itemized or non-itemized receipt depicting the transaction, or other interaction involving a user's account. In the context of a third party, such a financial institution or merchant, a transaction may refer to one or more of: a sale of goods and/or services, initiating an automated teller machine (ATM) or online banking session, an account balance inquiry, a rewards transfer, a user accessing their e-wallet, or any other interaction involving a user and/or the user's device that is detectable by the financial institution. A “user account” is where resources may be extracted from.
Furthermore, “communicable linkage” or “communicable link” may refer to the pathway used for initiating any communication between a user and the financial institution or third party monitoring the user's activities to transfer funds for the purchasing or selling of a product. The pathway may include face-to-face exchanges and electronic exchanges including any transfer of signs, signals, writing, image, sounds, data, or intelligence of any nature transmitted in whole or in part by a wire, radio, network, electromagnetic, or photoelectronic system.
In some embodiments, the invention allows for quicker and safer resource transfer by eliminating the need for dual messaging and user security breaches. For example, the resource transmittal device will allow users to view resource transfer data from a third party, add or modify a resource transfer input, and verify and authenticate the cardless and paperless resource transfer, all in a single resource transfer. For example, a user can add a tip or split the bill amongst many users on the portable resource transmittal device. This invention automatically transmits a request for authentication credentials based on smart device signals from the invention and device associated with the user. Subsequently, based on approved authentication by the user, the invention triggers release of user resources to complete the resource transfer. Furthermore, the release of user resources will be wireless, cardless, and paperless, preserving user security, enhancing third party efficiency, and limiting third party dual messaging. The invention may also communicate with third party inventory and suppliers to generate an automatic inventory update and order for materials for merchant products based on the completion of one or more steps via the portable resource transmittal device.
Furthermore, the invention may also communicate with the third party's back end accounting and payroll system to separate out additional resources added by the user for transfer to individuals associated with the third party, tax the additional resources, and integrate it directly into the individual's pay.
Embodiments of the present invention address the above needs and/or achieve other advantages by providing apparatuses (e.g., a system, computer program product and/or other devices) and methods for cardless and paperless real-time resource transfer between users and third parties.
As illustrated in
The network 201 may be a system specific distributive network receiving and distributing specific network feeds and identifying specific network associated triggers. The network 201 may also be a global area network (GAN), such as the Internet, a wide area network (WAN), a local area network (LAN), or any other type of network or combination of networks. The network 201 may provide for wireline, wireless, or a combination wireline and wireless communication between devices on the network 201.
In some embodiments, the user 202 is a customer of a third party or an individual that interacts with the third party. In some embodiments, the user 202 has a user device, such as a mobile phone, tablet, computer, or the like.
The user device 204 comprises computer-readable instructions 220 and data storage 218 stored in the memory device 216, which in one embodiment includes the computer-readable instructions 220 of a user application 222. In some embodiments, the user application 222 allows a user 202 to send and receive communications with the portable resource transmittal system 206.
As further illustrated in
The processing device 248 is operatively coupled to the communication device 246 and the memory device 250. The processing device 248 uses the communication device 246 to communicate with the network 201 and other devices on the network 201, such as, but not limited to the third party resource transfer system 208, the portable resource transmittal device 207, and the user device 204. As such, the communication device 246 generally comprises a modem, server, or other device for communicating with other devices on the network 201.
As further illustrated in
In one embodiment of the portable resource transmittal system 206 the memory device 250 stores an application 258. In one embodiment of the invention, the application 258 may associate with applications having computer-executable program code that generate and code a tag for implementation onto a product. Furthermore, the portable resource transmittal system 206, using the processing device 248 codes certain communication functions described herein. In one embodiment, the computer-executable program code of an application associated with the application 258 may also instruct the processing device 248 to perform certain logic, data processing, and data storing functions of the application.
The processing device 248 is configured to use the communication device 246 to communicate with and ascertain data from one or more third party resource transfer systems 208. In the embodiment illustrated in
As illustrated in
As illustrated in
Furthermore, the portable resource transmittal device 204 may include a communication mechanism to communicate with the user device and to receive and transmit resources from the user device to the third party.
The processor 410 may include functionality to operate one or more software programs or applications, which may be stored in the memory device 420. For example, the processor 410 may be capable of operating applications such as the activity application 425, a digital wallet application 423, or a web browser application. The activity application 425 may then allow the portable resource transmittal device 204 to transmit and receive data and instructions from the computer terminal 120 (for example, via wireless communication or NFC channels), data and instructions from the processing system 130, web content, such as, for example, location-based content and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like.
The digital wallet application 423 and the financial data module 427, together may include the necessary circuitry to provide token storage and transmission functionality, transmitter device signal encoding and decoding functionality to the portable resource transmittal device 204, for secure transmission of financial and authentication credential tokens via the contactless communication interface 479 from the user device to the third party. Generally, the financial data module 427 may be a chip in the form of an integrated circuit, a microprocessor, a system-on-a-chip, a microcontroller, or the like. Of note, while
The processor 410 may be configured to use the network interface device 470 to communicate with one or more other devices on a network 101 such as, but not limited to the computer terminal 120 and the processing system 130. In this regard, the network interface device 470 may include an antenna 476 operatively coupled to a transmitter 474 and a receiver 472 (together a “transceiver”), modem 478 and a contactless communication interface 479. The processor 410 may be configured to provide signals to and receive signals from the transmitter 474 and receiver 472, respectively. The signals may include signaling information in accordance with the air interface standard of the applicable BLE standard, cellular system of the wireless telephone network and the like, that may be part of the network. In this regard, the portable resource transmittal device 204 may be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the portable resource transmittal device 204 may be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like. For example, the portable resource transmittal device 204 may be configured to operate in accordance with second-generation (2G) wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and/or IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols, and/or the like. The portable resource transmittal device 204 may also be configured to operate in accordance with non-cellular communication mechanisms, such as via a wireless local area network (WLAN) or other communication/data networks. The portable resource transmittal device 204 may also be configured to operate in accordance Bluetooth® low energy, audio frequency, ultrasound frequency, or other communication/data networks.
The network interface device 470 or communication device 470 may also include a user activity interface presented in user output devices 430 in order to allow a user 102 to execute some or all of processes described herein. The application interface may have access to the hardware, for example, the transceiver, and software previously described with respect to the network interface device 470. Furthermore, the application interface may have the ability to connect to and communicate with an external data storage on a separate system within the network 101. As described above, the portable resource transmittal device 204 includes a display device 432 having a user interface that includes user output devices 430 and/or user input devices 440. The user output devices 430 may include a display 432 (e.g., a liquid crystal display (LCD) or the like) and a speaker 434 or other audio device, which are operatively coupled to the processor 410. The user input devices 440, which may allow the portable resource transmittal device 204 to receive data from the user and/or the user device, may include any of a number of devices allowing the portable resource transmittal device 204 to receive data from a user.
The portable resource transmittal device 204 may further include a power source 415. Generally, the power source 415 is a device that supplies electrical energy to an electrical load. In some embodiment, power source 415 may convert a form of energy such as solar energy, chemical energy, mechanical energy, and the like, to electrical energy. Generally, the power source 415 in a portable resource transmittal device 204 may be a battery, such as a lithium battery, a nickel-metal hydride battery, or the like, that is used for powering various circuits, for example, the transceiver circuit, and other devices that are used to operate the portable resource transmittal device 204. Alternatively, the power source 415 may be a power adapter that can connect a power supply from a power outlet to the portable resource transmittal device 204. In such embodiments, a power adapter may be classified as a power source “in” the portable resource transmittal device 204.
The portable resource transmittal device 204 may also include a memory buffer, cache memory or temporary memory device operatively coupled to the processor 410. Typically, one or more applications 425 and 423, are loaded into the temporarily memory during use. As used herein, memory may include any computer readable medium configured to store data, code, or other information. The memory device 420 may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory device 420 may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like.
As illustrated in block 105, the third party may be provided one or more portable resource distribution devices for use at the third party place of business. The portable resource distribution devices may be programmed to include the third party unique identification and be used to complete transactions between users and the third party without requiring dual messaging or physical exchange of payment credentials.
Next, as illustrated in block 106, the process 100 continues by receiving resource transfer data from the third party resource transfer system to await completion by the user. In this way, a user may have completed a transaction with the third party. The user may need to provide a resource distribution to the third party in exchange for the transaction completion. The third party may transmit the required resource transfer request in the form of a resource transfer data request to the system. The system may transmit the resource request to the portable resource transmittal device associated with the third party, based on the unique identifier, for the user to view. The system presents the resource request via the stand alone portable resource transmittal device in a visual format such that the user may visualize the resource request, as illustrated in block 108.
As illustrated in block 110, the process 100 continues by receiving resource transfer input from the user. The user may have a deposit account, such as a transactional account (e.g., a bank account), a savings account, an investment account, a money market account, a time deposit, a dem and deposit, a pre-paid account, a credit account, a non-monetary user profile that includes information associated with the user, or the like. This account information may be stored on a user device. The user may coordinate the user device with the portable resource transmittal device for the transmission of resources from one or more of the user deposit accounts to the portable resource transmittal device. The amount of resources distributed from the user deposit account may be dependent on the resources requested by the third party to complete the transaction. The amount of resources distributed from the user deposit account may also be dependent on the user's resource transfer input. In some embodiments, the user may elect to split the total resource transfer among multiple users, and/or add a tip to the total resource transfer. The user's resource transfer input and the third party's resource transfer data are aggregated into a total resource allocation. The coordination of the user device with the portable resource transmittal device may be based on touch or touchless technology exchange of data.
As illustrated in block 112, the process 100 continues by transmitting a request for authentication credentials from the user via a communicable linkage to a user device. This authentication allows the user, via the user device, to be coordinated with the portable resource transmittal device for secure resource distribution. The system may generate a direct communicable linkage with each of the individual authorized users, if there are multiple users. As such, each communicable linkage may be private, between the system and the individual user and provide a direct portal for account information for the entity and resource transfer via communication between the third party and a financial institution associated with the user. The communicable linkage may be wired or wireless. The communicable linkage will link the third party and user and will present information to the user and third party via a graphical interface on the portable resource transmittal device or user device. The communicable linkage will provide for selective communication to each of the users or third party.
Furthermore, in some embodiments, the system, via the portable device, may link to loyalty accounts associated with the authorized user. The linkage could include recommendations based on user preferences, tie the user to loyalty points, or the like. Furthermore, the loyalty accounts may include processing add on or additional products for utilization based on user preferences and orders.
Next, as illustrated in block 156, the process 150 continues with installation of software on a third party point of transaction device or encoding the portable resource transmittal device for third party resource transfer needs. The portable resource transmittal device typically provides a graphical interface that allows the user to communicate with the portable resource transmittal device and portable resource transmittal system. The portable resource transmittal software to be installed on the third party point of transaction device or encoding of the portable resource transmittal device may provide different functions and different interfaces to the user to perform one or more steps of process flows described herein. The memory can also store any of several pieces of information to implement functions of the portable resource transmittal device and/or other systems described herein. For example, the memory may include such data as user authentication information.
As illustrated in block 158, the third party can test the wireless and/or wired transmittal of resource transfer data from the third party resource transfer system to verify successful transmission of data. As illustrated in block 160, the third party may also verify transmittal completion and test graphical display capabilities.
Further, block 186 illustrates the third party resource transfer system generating a unique transaction identification code to be used by the third party to import resource transfer data to the portable resource transmittal system. As further illustrated in block 188, the process 180 will prompt the third party to enter the unique code into a text field on the portable resource transmittal system and portable resource transmittal device. When the unique code is entered, the system will utilize the communication device to wirelessly communicate with the third party resource transfer system and the processing device to extract resource transfer data from the third party resource transfer system. The resource transfer data will be stored in the portable resource transmittal system via the memory device and data storage.
The process 180 continues with the portable resource transmittal system receiving and storing the resource transfer data, as illustrated in block 190, via processes described herein. The portable resource transmittal system will then transmit the resource transfer data to the portable resource transmittal device using the communication device. The portable resource transmittal device will display via graphical interface the resource transfer data for completion by user.
As illustrated in block 192, the portable resource transmittal device will receive resource transfer input from the user and will coordinate the resource transfer input and resource transfer data into a total resource allocation 192. As used herein, the term “resource transfer input” generally includes user actions such as splitting a bill or adding tip. As used herein, the term “total resource allocation” may refer to totaling a portion of a resource transfer data that has been split and adding tip to it or taking the entire resource transfer data and adding tip to it.
The process 180 continues in block 194 with the portable resource transmittal device transmitting a request for authentication credentials from a user via a communicable linkage to the user device. Authenticating the user may include authenticating the user device associated with the user over a private security network. The authentication credentials may include a username and password, biometric data, secured authentication tokens, or cryptographic keys. As illustrated in block 194, upon user approval and proper user authentication, the portable resource transmittal device will transmit a processed total resource allocation to the third party resource transfer system for completion of the transaction.
As illustrated in block 304, the process 300 continues by displaying, via a graphical interface, the resource transfer data to a user on the portable resource transmittal device. As illustrated in block 306, the portable resource transmittal device will allow the user to split the total resource transfer data, select itemized resources, and/or add resource transfer input. In this way, the user, via the portable resource transmittal device, may modify their portion of the bill by communicating with the third party resource transfer system via the portable resource transmittal device.
As illustrated in block 308, the process 300 continues by aggregating the resource transfer input and the above resource transfer data to create a total resource allocation to apply to a user payment method. The portable resource transmittal device will aggregate the resource transfer input and resource transfer data to create a total resource allocation. As illustrated in block 310, the process 300 continues by cross-referencing the aggregate of the resource transfer input and resource transfer data via the third party resource transfer system to ensure correct total resource allocation. In this way, if there are multiple users who split the bill and added custom tip, the third party resource transfer system will total the portions of the split bill to ensure that the third party is receiving a total resource allocation.
Further, as illustrated in block 312, the process 300 continues by authenticating user credentials and applying the total resource allocation to the user's cardless and paperless payment method on the user device. The third party will typically provide a secure network for communication between user and third party to authenticate users for payment between user and third party resource transfer system. A third party can be understood to include an individual or an organization that owns and/or operates an online system of networked computing devices, systems, and/or peripheral devices on which the system described herein is implemented. Third parties may be a business organization, like restaurants and banks, or government organizations, and the like, which may routinely use various types of applications within its enterprise environment to accomplish its objectives.
Furthermore, when the third party receives the user's processed resource allocation, the third party resource transfer system will subtract out the resource transfer input designated by the user for payment to individuals associated with the third party. The third party resource transfer system will appropriate tax and integrate the designated resource transfer input with the individual's pay.
The process 350 continues in block 356 by allowing a communicable linkage between the third party resource transfer system and the third party inventory tracking system. As such, the system may examine market changes in the inventory and provide the third party with a time frame to purchase inventory and a recommended way (cash, credit, or the like) to purchase the inventory. The system may also track trending data, past orders of the third party, and the like, to predict inventory requirements for the third party.
As illustrated in block 358, the process 350 continues by modifying the current third party inventory status via updating product inventory based on aggregation of third party resources identified on the third party resource transfer system. The process 350 may present inventory purchase recommendations based on analysis of total resource transfer for products of the inventory and recommend price fluctuation for the products of the inventory based on popular demand. The process 350 may notify the third party of diminishing inventory based on resource transfer data and recommend a time frame to purchase inventory.
As illustrated in block 506, the process 500 will continue by prompting the user to verify the total resource allocation to be transferred and communicating to a financial institution to pay to the third party. As such, this communication will still be taking place over a private and secure network. The communication will occur between a user and a third party, which may be a financial institution or account manager associated with the user's financial institution.
As illustrated in block 508, the process 500 continues by completing the transaction with the third party by processing the cardless and paperless transaction to the third party resource transfer system.
As will be appreciated by one of ordinary skill in the art, the present invention may be embodied as an apparatus (including, for example, a system, a machine, a device, a computer program product, and/or the like), as a method (including, for example, a business process, a computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely software embodiment (including firmware, resident software, micro-code, and the like), an entirely hardware embodiment, or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having computer-executable program code portions stored therein. As used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more special-purpose circuits perform the functions by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or having one or more application-specific circuits perform the function. As such, once the software and/or hardware of the claimed invention is implemented the computer device and application-specific circuits associated therewith are deemed specialized computer devices capable of improving technology associated with the in authorization and instant integration of a new credit card to digital wallets.
It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and/or semiconductor system, apparatus, and/or device. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as a propagation signal including computer-executable program code portions embodied therein.
It will also be understood that one or more computer-executable program code portions for carrying out the specialized operations of the present invention may be required on the specialized computer include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F #.
It will further be understood that some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of systems, methods, and/or computer program products. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a special purpose computer for the authorization and instant integration of credit cards to a digital wallet, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s).
It will also be understood that the one or more computer-executable program code portions may be stored in a transitory or non-transitory computer-readable medium (e.g., a memory, and the like) that can direct a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture, including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s).
The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with operator and/or human-implemented steps in order to carry out an embodiment of the present invention.
While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.
