API ENGINE FOR A SELF-SERVICE DEVICE
In an example embodiment described herein is an application program interface (API) suitable to couple a self service device, such as an automated banking machine, with various banking services. The API acts as a repository or requestor of information from many different sources such as, for example, a financial core, a transaction switch/processor, third party partners such as check guarantee service providers, customer information files stored and maintained by a financial institution or data obtained from other channels such as core banking, Customer Relationship Management (CRM), mobile banking and/or online banking platforms.
1 . An apparatus, comprising:
an application program interface logic coupled with a self service device and a plurality of financial institution data stores;
wherein the application program interface logic is operable to receive transaction requests from the self service device;
wherein the application program interface logic is operable to selectively route a first transaction request to a first financial data store responsive to determining that the first transaction requests corresponds to a first type of transaction; and
wherein the application program interface logic is operable to selectively redirect a second transaction request to a second financial data store responsive to determining that the second transaction requests corresponds to a second type of transaction.
2 . The apparatus set forth in claim 1 , wherein the application program interface logic is operable to receive a response to the second transaction request from the second financial data store; and
wherein the application program interface logic is operable to route the response to the second transaction request to the self service device.
3 . The apparatus set forth in claim 2 , wherein the application program interface logic is operable to receive a response to the first transaction request from the first financial data store; and
wherein the application program interface logic is operable to route the response to the first transaction to the self service device.
4 . The apparatus set forth in claim 1 , wherein the application program interface logic is coupled with a transaction processor; and
wherein the application program interface logic is operable to forward a third transaction request that is to be handled by the transaction processor to the transaction processor.
5 . The apparatus set forth in claim 1 , wherein the application program interface logic comprises a library of application program interface hooks specifying types and formats of data that can be pushed or pulled by the application program interface logic.
6 . The apparatus set forth in claim 5 , wherein the application program interface logic translates the second request to a format that is compatible with the second financial data store.
7 . The apparatus set forth in claim 6 , wherein the application program interface logic translates a response to the second request to a format that is compatible with a screen associated with the second request at the self service device.
8 . The apparatus set forth in claim 1 , wherein the application program interface logic is coupled with a plurality of self service devices; and
wherein the application program interface logic is operable to receive transaction requests from the plurality of self service devices.
9 . The apparatus set forth in claim 7 , wherein the application program interface logic is operable to maintain a plurality of libraries corresponding to the plurality of self service devices.
10 . The apparatus set forth in claim 1 , wherein the application program interface logic is operable to reject a third transaction request responsive to determining that the application program interface logic does not have predefined data indicating how to handle the third transaction request.
11 . Logic encoded in a non-transitory, tangible computer readable medium of execution for execution by a processor, and when executed operable to:
receive transaction requests from a self service device;
determine a type of transaction for the transaction requests;
route a first transaction requests unchanged to a first financial data store responsive to determining that the first transaction requests corresponds to a first type of transaction; and
re-format a second transaction request to a format compatible with a second financial data store and forward the re-formatted, second transaction request to the second data store responsive to determining the second transaction request corresponds to a second type of transaction.
12 . The logic set forth in claim 11 , the logic is further operable to:
receive a response to the second transaction request; and
re-format the response to the second transaction request to a pre-defined format for the self service device and forward the re-formatted response to the second transaction request to the self service device.
13 . The logic set forth in claim 11 , the logic is further operable to:
receive a response to the first transaction request; and
forward the response to the first request unchanged to the self service device.
14 . The logic set forth in claim 11 , wherein the first destination is coupled with a transaction processor; and
wherein the logic is further operable to forward transaction requests for the first type of transaction to the transaction processor.
15 . The logic set forth in claim 11 , wherein the logic comprises a library of application program interface hooks specifying types and formats of data that can be pushed or pulled by the logic.
16 . The logic set forth in claim 11 , wherein the logic is coupled with a plurality of self service devices; and
wherein the logic is further operable to receive a plurality of transaction requests from the plurality of self service devices.
17 . The logic set forth in claim 16 , wherein logic is operable to maintain a plurality of libraries corresponding to the plurality of self service devices coupled with the first interface.
18 . The logic set forth in claim 11 , wherein logic is further operable to reject a third transaction request responsive to determining that the logic does not have predefined data indicating how to handle the third type of transaction.
19 . The logic set forth in claim 10 , wherein logic is further operable to:
send a plurality of requests for the second transaction request to a plurality of financial data stores;
receive responses from the plurality of financial data stores for the second transaction type;
correlate the responses from the plurality of financial data stores for the second transaction type;
format the correlated responses from the plurality of data stores for the second transaction type to a predefined format for the self service device; and
forward the formatted, correlated responses from the plurality of financial data stores for the second transaction type to the self service device.
20 . A method, comprising:
receiving a first transaction request of a first transaction type from a self service device;
receiving a second transaction request of a second transaction type from a self service device;
determining where to route the first transaction request based on the first transaction type;
determining where to route the second transaction request based on the second transaction type;
routing the first transaction requests to a first financial data store responsive to determining the first transaction request corresponds to the first type of transaction; and
forwarding the second transaction request to a second financial data store responsive to determining the second transaction request corresponds to the second type of transaction.
21 . The method of claim 19 , further comprising:
receiving a response to the second transaction request;
determining a pre-defined data format for the response to the second transaction for the self service device;
formatting the response to the second transaction request to the pre-defined format for the self service device; and
forwarding the formatted response to the second transaction request to the self service device.