Patent Application
20170083914
Historically, a major concern of merchants and issuers of payment devices (such as credit or debit cards and applications associated therewith) in online shopping contexts and other “card not present” transactions is whether the person attempting to use the payment device is an authorized user of the payment device. When a cardholder is not present, it may be difficult for the merchant or other entity to authenticate or verify whether the actual authorized cardholder is indeed authorizing a purchase, as opposed to some attempt of a type of fraudulent activity.
In an effort to reduce the incidence of payment device fraud in online purchase and other “card not present” transactions, a number of systems have been proposed and used to verify that the person using the payment device is an authorized user of payment device. In this regard, one security protocol developed to add a layer of additional security to online credit and debit transactions is the 3-D Secure (3DS) Protocol that couples the financial authorization process of a purchase transaction with an online authentication of the user or account completing the purchase transaction. This protocol was designed to allow a credit card issuer to authenticate their cardholder(s) while the cardholders shop online or in other “card not present” scenarios. However, 3DS and other authentication processes and systems proposed heretofore are typically closed-loop systems that are complex, costly to implement, and primarily directed to authenticating the identity of the cardholder.
Therefore, it is desirable to provide improved methods and systems that support the acquisition and processing of authentication data related to purchase transactions that is operationally stable, efficient, and scalable and includes improved data management functionalities.
Features and advantages of some embodiments of the present invention, and the manner in which the same are accomplished, will become more readily apparent upon consideration of the following detailed description of the invention taken in conjunction with the accompanying drawings, wherein:
In general, and for the purpose of introducing concepts of embodiments of the present disclosure, an authentication security policy relates to a process of verifying cardholder account ownership during a transaction in an online electronic commerce (e-commerce) environment, where that transaction may include a purchase transaction. As used herein, the terms purchase transaction and payment transaction or simply transaction may be used interchangeably unless stated otherwise. In general, the purchase transactions herein refer to card not present or e-commerce transactions. As such, these transactions may be requested by a merchant or other entity to have the cardholder, user, or other entity presenting a payment device for payment or an account thereof verified as an authorized user of the payment device since, for example, a merchant cannot physically verify the user is even in possession of the payment device.
In accordance with some general aspects of the present disclosure, a framework for an authentication process, system, and method will be described that includes efficient and flexible data management functions and mechanisms. The data management functions and mechanisms of the authentication framework or platform herein include, but are not limited to, providing efficient and accurate control and management of a new customer enrollment process and billing aspects of the authentication platform. In some aspects, an authentication framework or platform herein provides mechanism(s) supporting customer enrollment/data management and billing solution(s) that are scalable to future business growth and customers' expectations. In some aspects, the authentication framework or platform herein supports and facilitates the accurate management of data related to aspects of issuer, payment processor, and merchant information in an authentication ecosystem.
payment device system, application, or service collects authentication data from various internal and external entities (e.g., applications, devices, services, etc.) of a business, enterprise, or organization within an authentication ecosystem, including but not limited to a 3DS environment, that can provide authentication services and stores the collected authentication data in a data repository such as a data warehouse, local or distributed storage facility, and a cloud based storage service. The collected authentication data may be used as a basis for business analytics including, for example, business reporting for internal and external customers of an enterprise or other business organization. Analysis based on the collected authentication data may, in some aspects, be utilized for transactional fraud scoring purposes. In some embodiments, data derived from the collected authentication data can be shared and used in combination with transaction data (e.g., purchase authorization data) within a data warehouse to provide a view of an end-to-end transaction lifecycle.
The present disclosure provides, at least in part, processes and systems for reporting an end-to-end or complete view of a transaction including authentication data used in the authorizing and processing of credit and other types of transactions. The authentication data determined, processed, collected, analyzed, and stored herein may be used to provide valuable insight into a business and other entities. Such insights may relate, but not be limited to, transactional patterns, authentication trends and patterns, card issuer authentication success and failure rates, fraud indicators due to multiple failures within certain card ranges or regions, cardholder trends on authentication abandonment, failure rates of certain authentication service providers, and trends on authentication methods used in particular transactions.
A number of methods, systems, and solutions have been proposed to provide a cardholder authentication process. One solution is MasterCard® SecureCode™ promulgated by the assignee of the present patent application that defines and provides a level of security relating to a cardholder authentication process. The MasterCard® SecureCode™ process incorporates aspects of the 3-D Secure™ Protocol Specification Core Functions, Version 1.0.2 effective 17 Apr. 2006. This particular implementation of 3-D Secure™ (also referred to herein as “3DS”) includes support for the SPA (Secure Payment Application) algorithm and Universal Cardholder Authentication Field (UCAF) without changing the 3-D Secure™ specification, messages, or protocol. While some aspects herein may build on, rely on, and leverage various aspects of the 3-D Secure™ specification, the processes and systems herein are not limited to a security authentication protocol or process adhering to that specification or even authentication flows that may fit within the 3DS protocol. Even in some instances herein where some embodiments may be described in the context of a system and process interfacing with at least some aspects of the 3-D Secure™ specification, other or alternative authentication security protocols may be substituted without any loss of generality, including those now known and those that may be developed in the future.
System 100 includes a plurality of entities that must interact with each other by exchanging multiple, specifically formatted messages over secure communication channels (as defined in the 3-D Secure™ specification). Accordingly, the cardholder authentication process of
System 100 includes a cardholder 105 that interacts with a merchant's online presence. Typically, cardholder 105 visits a merchant's Web site using a browser on their device of choice and selects items (e.g., goods and/or services) for purchase. As part of the online ordering process, cardholder 105 checks out and finalizes the purchase transaction by providing payment credentials to the merchant. The payment credentials may include at least a primary account number (PAN) representative of the account to be used as a source of funds in the transaction, an expiration date associated with the PAN, and (billing) address information of the cardholder. The PAN and other information is provided to the merchant's Merchant Server Plug-in (MPI) 110, where the MPI is a software module executed on behalf of the merchant. MPI 110 operates to determine whether payment authentication is available for the PAN received from the cardholder. The MPI formats and sends a Verify Enrollment Request (VEReq) message including the PAN to a Directory Sever (DS) 115, where the DS is a computer server that can determine whether the PAN is within a range of PANs enrolled in the authentication service provided by system 100. The DS may comprise a computer having at least one processor, a memory to store program instructions and data, and a communication interface to interface with other devices.
Upon receiving the VEReq, DS 115 queries an Access Control Server (ACS) 120 device, where the address of the ACS is specified in the VEReq. The address of the ACS may be specified using a Web address URL (uniform resource locator) for the ACS. The specified ACS may be an issuer of the account represented by the PAN. In some embodiments, the ACS may be acting on behalf of the issuer of the PAN and the specified URL points to a Web address other than that of the issuer. ACS 120 may respond to the query by providing an indication of whether authentication is available for the PAN included in the VEReq. If the merchant is a participating acquirer and the merchant is a valid merchant, then ACS 120 may respond with a Verify Enrollment Response (VERes) message that indicates that authentication is available for the PAN included in the VEReq message. ACS 120 uses the PAN from the VEReq to determine whether the cardholder is enrolled in the authentication service.
In some instances, the MPI may store data related the ranges of PANS enrolled in the authentication service and determine whether the PAN is within a range of PANs enrolled in the authentication service provided by system 100.
In some aspects, the VERes may include a flag that authentication is available for the PAN (e.g., a PAN Authentication Available field may be set to “Y” indicating authentication is available). Conversely, ACS 120 may respond with a VERes that indicates that authentication is not available for the PAN (e.g., acquirer BIN and/or PAN not enrolled, ACS unresponsive to query, etc.). In some aspects, the VERes may include a flag that authentication is not available for the PAN (e.g., a PAN Authentication Available field may be set to “N” indicating authentication is not available or “U” indicating authentication is unavailable). In the event the VERes includes a flag, a value in a field thereof, or other mechanism to indicate that authentication is not available for the PAN, the authentication process provided by system 100 may be terminate or aborted.
ACS 120 further sends the VERes including the indication of whether authentication is available to DS 115. DS 115 will then forward the VERes to MPI 110. This may conclude the DS's participation in the authentication of the transaction but the authentication process is far from complete. Upon receipt of the VERes, MPI 110 reads the response to see if authentication is available for the transaction's PAN. If authentication is available, then MPI 110 sends a message including a Payer Authentication Request (PAReq) message to ACS 120 via the cardholder's browser using the ACS URL included in the VERes. The PAReq message requests the issuer ACS to authenticate its cardholder. The PAReq may include cardholder, merchant, and transaction-specific information. The cardholder information may include security information known only to the cardholder and the issuer. It is noted that the PAReq message is not shared with the merchant (or the MPI).
ACS 120 receives the PAReq and may proceed to validate the received message to ensure that it is properly formatted and includes the requisite information, including for example, digital certificates and a proper PAN Authentication Available flag (e.g., “Y”). ACS 120 may further determine whether to provide authentication of the cardholder. ACS 120 may provide an indication of that determination by providing a status for the transaction. Values for the status may include, in accordance with 3-D Secure™, “Y” meaning the customer is fully authenticated, “N” meaning the customer failed or canceled authentication (i.e. transaction denied), “U” meaning the authentication could not be completed (e.g., technical issues such as communication failures, time-outs, etc.), and “A” that provides proof that the authentication was attempted.
A message is sent from ACS 120 to MPI 110 that includes the transaction status as determined by ACS 120. The message may comprise a Payer Authentication Response, PARes message. In the event the transaction status is determined to be “Y”, then the PARes will include an authentication token, AAV, that is sent to MPI 110. The PARes may be digitally signed to offer a level of security regarding the authenticity of the message itself. The PARes is received at MPI 110 through the cardholder's browser. Upon receipt of the PARes, MPI 110 may operate to validate the signature of the PARes and determine whether to authorize the transaction based, at least in part, on the values comprising the VERes.
If the cardholder is authenticated using the authentication process generally described above, then the purchase transaction may proceed to a purchase or payment authorization process and informs the MPI of the AAV value or token. The purchase authorization may be accomplished in a conventional manner after the MPI notifies the merchant payment system of the results of the authentication attempt.
It is again noted that the authentication of the cardholder or account as explained hereinabove with respect to
In some instances, if the authentication was not successful, the merchant may still proceed with a conventional transaction authorization without the authentication token, as an unauthenticated transaction. Liability for the processing of an unauthenticated transaction may in some such instances reside with the merchant. In accordance with some aspects herein, data including an indication of the unsuccessful cardholder authentication, will be documented and maintained.
As noted in conjunction with
In some embodiments, the requested authentication value may comprise a security code that is compatible with a Universal Cardholder Authentication Field (UCAF) data structure that is compatible with an authentication payment environment. It is noted however that an authentication value in some embodiments herein is not limited to the UCAF data structure or an instance thereof. In accordance with some aspects herein, the requested authentication value may be compatible with one or more authentication flows being utilized in a particular transaction and/or use-case.
In some embodiments, the authentication payment environment may comprise a three-domain (3-D) security protocol, although other authentication flows and protocols may be used in some embodiments. In some embodiments and aspects, a process of generating and communicating the API call and the API response in reply thereto and the systems and devices to execute that process are separate and distinct from the security protocol. In some embodiments, aspects of a method and process herein may, in some instances, provide information to and/or receive information from a process and system comprising a security protocol but be distinct therefrom.
In one aspect, the request for an authentication value or token may be for a specific, particular transaction, where the authentication value returned or sent to calling application 205 in reply to the API call provides an authentication value that is valid for and specifically associated with the transaction specified in the API call. In some embodiments, the authentication value or token sent from enterprise server 210 to application 205 may be used by application 205 and/or other applications, systems, devices, and services in one or more processes performed by application 205 and/or the other applications, systems, devices, and services. As an example, the authentication value generated by enterprise server 210 and sent to application 205 in response to the API call from the application may be used as an indicator (i.e., proof) of a verified authentication and further included in a payment transaction authorization request or other process. In some embodiments, the authentication value may be formatted and encoded in a suitable manner (e.g., formatted, encoded, encrypted, etc.) such that a particular authorization request including the authentication value herein need not be altered to accommodate the authentication value and otherwise be processed. Accordingly, some embodiments of
In some embodiments, it is noted that application 205 makes the authentication request using a single API call to enterprise server 210. Conversely, the enterprise server may provide a reply to application 205 using a single API response. In this manner, an authentication value may be obtained in an efficient process by requesting and receiving an authentication value or token using a single API call from an application. In some aspects, this is in contrast to some embodiments of the processes disclosed in reference to, for example,
Referring to
In some aspects, system 300 includes an application server 310 that may receive payer authentication request (PAReq) messages or other message(s) depending on the authentication protocol being used and payer authentication request (PARes) messages or other message(s) depending on the authentication protocol being used associated with transaction from one or more sources. In accordance with some authentication systems and processes, the PAReq or other messages and PARes or other messages may be received from an ACS 305 external to an enterprise environment. In some aspects, the PAReq messages and PARes messages may be received from an issuer ACS of a system configured, at least in part, similar to system 100 of
In some aspects, server 310 may receive PAReq and PARes data associated with transactions from one or more servers internal to an enterprise environment, such as, for example, from servers 315 and 320. Servers 315 and 320 may be one or more devices or systems functioning as, at least in part, an ACS. In some embodiments, ACS 315 is an internal ACS that may be internal to an enterprise environment such as, for example, the security (ACS) server 215 of
In some embodiments, server 320 may include an online authentication service ACS provided by an enterprise, whereas in some embodiments server 320 may include other types of ACS servers that may, at least on occasion, communicate with applications, devices, and/or services external to the enterprise environment. Server 320 may have transaction PAReq and PARes data or other authentication data associated with certain online and other types of transactions. The PAReq and PARes or other authentication data from servers 315 and 320 may be transmitted to application server 310 and then to history server 325.
Other aspects of the authentication process data, namely the verify enrollment request (VEReq) messages and verify enrollment response (VERes) messages or other message(s) depending on the authentication protocol being used may be received from one or more servers 315 (e.g., the internal ACS server) and a directory server (DS) 340. In some aspects, server 315 is the internal ACS that may facilitate the internal generation of an authentication value for a transaction, as discussed with respect to
In some instances, VEReq and VERes or other message(s) may be generated with the assistance and in cooperation with external devices, applications, and services, such as system 100 of
In some aspects, whether the VEReq and VERes data is received from an internal ACS or a DS 340, server 340 may operate to track, store, format, encode, and/or encrypt the received data to insert the VEReq and VERes or other data into a database table, system, and other data structures. In some embodiments, an indication of the source or the type of device that provides the VEReq and VERes or other data is included in the VEReq and VERes data or other message(s) depending on the authentication protocol being used. This source indicator may provide insight into whether the authentication token request associated with a particular transaction was generated by an internal process (e.g.,
The data in both history server 325 (i.e., PAReq and PARes or other data) and DS server 345 (i.e., VEReq and VERes or other data) may be synced and otherwise processed, combined, or aggregated for inclusion in a data warehouse, storage facility, device, or system 330. In some embodiments, data warehouse 330 may comprise a database management system or an instance of a node of a database management system. In some aspects, the combined PAReq/PARes or other data and the VEReq/VERes or other data may comprise a single data record or data structure representation thereof. The combined data record may provide, in addition to other transaction details, an end-to-end view of a transaction flow, including whether authentication was requested by a merchant, whether the authentication was provided by an issuer, whether the authentication was approved or denied, and whether payment authorization for the transaction was requested and whether it was approved or denied.
In some aspects, the data in the data warehouse 330 may be accessed by other systems and devices (not shown) and used to provide insight into the transactions. In some instances, enterprise level analytics may be used to analyze the data to, for example, generate reports, presentations, and dashboards. In some aspects, the data in data warehouse 330 may be used by various organizations of an enterprise to, for example, settle transaction disputes, to manage and respond to issuer or merchant complaints, to manage compliance programs, to manage abandonment rates, etc. In some embodiments, system 300 facilitates and enables the functionality to determine unique patterns in transactions and better ascertain user and merchant practices (e.g, fraud, etc.) than previous methods of transactional data collection.
In some embodiments, the authentication data processed and collected in accordance with some aspects herein may be used in a process, system, and device to score or provide an indication of a risk level of a particular transaction based on, for example, historical authentication patterns and/or historical authentication velocities of an account or identity. In this and other contexts, the historical authentication activity may, at least in part, be compared to a current request to determine whether the authentication data falls outside (within) observed, expected, desired, calculated, or predicted patterns, ranges, and “norms”. In some aspects, the authentication data processed and stored herein may be aggregated in an effort to facilitate analyzing, storing, retrieving, and reporting functions using the data.
As part of an authentication ecosystem or platform 500 herein, on-behalf authentication services 505 may be called by an Access Control Server (ACS) or some other system to provide the actual authentication in an “out of band” method, which can include, for example, a one-time passcode generation and validation service, a mobile application, a biometric validation service, and other types of services, processes, applications, and use-cases. The results of all of these and other requests can also be fed into a data repository within a data warehouse that can be interfaced with other data to provide detailed transactional reporting and analytics.
In some embodiments, an authentication API in accordance with some aspects herein may include one or more data fields. Table 1 below is a tabular listing of some data fields that may be specified for implementing an API that may be used by a web service or application in accordance with some embodiments herein. In some embodiments, the data fields listed in Table 1 may be described in an interface description language (e.g., Web Service Description Language, WSDL) and provided to a developer of a web service or application for use by the developer or other entity to generate a web service or application that may effectively communicate using an appropriately define API.
In some embodiments, the authentication API may require or expect a value to be specified for all of the data fields listed in Table 1. That is, the API call may include a corresponding value for each of the data fields listed in the table. In some other embodiments, some but not necessarily all of the data fields specified in Table 1 may have a corresponding value supplied in the API call. For example, some instances of an authentication API herein may specify a value for a PAN (i.e., payment account number), a merchant name, and an expiry date corresponding to the PAN. These minimal values may be included in the API call and may be sufficient for the request of an authentication value in some embodiments herein. In accordance with some embodiments herein, the data received by or provided to an authentication history server herein contains at least some of the following components:
Table 1 includes an illustrative sample listing of data for some embodiments herein. The listed data may not be holistic or exhaustive. Accordingly, other data such as high level cardholder information and other transactional data may also be stored or received by and/or provided to an authentication history server in some embodiments herein.
In some embodiments, an application operative in accordance with process 300 may include an electronic payment wallet application developed on behalf of an issuer. As part of the development and deployment of the electronic wallet, authentication of the electronic wallet may be assigned or passed to a payment network provider or other entity. At the time of a log-in for the wallet application, there may be some level of authentication that verifies the authenticity or identity of the wallet application with the issuer of the wallet. Accordingly, there may not be a need for a merchant at the time of a purchase involving a customer to authenticate the wallet at a check-out since the wallet application has already been authenticated with the issuer. In some instances, the wallet authentication is done as part of a wallet initiation process.
While the user associated with the wallet application of this example has already been authenticated with the issuer to a level of authentication determined and designed to satisfy the concern(s) of the issuer and/or others (i.e., “pre-authenticated”), the particular authentication may not provide an authentication value or token such as an AAV value that may normally be generated by and/or in accordance with a security protocol. In an effort to obtain an authentication value or token (e.g., a AAV value), the electronic wallet application may request the authentication value via an API call in accordance with the present disclosure. The API call may be presented directly to a service to pull an authentication value therefrom. In some aspects, the API call from the application may obtain the authentication value without the need to satisfy all of the requirements of one or more security protocols since, for example, the issuer or an entity acting on behalf thereof has agreed to processing of the API call given certain conditions are satisfied. In some embodiments, an agreement to accept and process the API calls from an application in accordance with the present disclosure are determined before the API call is received by an enterprise server herein (e.g., before an operation 305 of process 300). In some aspects, the authentication of the electronic wallet in the present example may be said to comprise a pre-authorized authentication.
In some embodiments, a policy governing the authentication of the electronic wallet or other calling application may vary depending on the calling application, the intended use of the authentication value or token by the calling application, and other considerations.
Continuing with the electronic wallet example, in an instance a customer cardholder logs into a merchant's wallet service, the customer registered with the wallet service may be considered to have already been authenticated (i.e., pre-authorized authentication). In this case however, an authentication value or token may be desired for use in a payment authorization request associated with a purchase transaction of the customer. In some embodiments, the payment authorization request will be expected by an issuer (or entity acting on behalf thereof) to include the authentication value or token. In some aspects, the payment authorization may not be processed in the absence of the expected authentication value or token.
In some embodiments, inclusion of the authentication value or token in the payment authorization request may facilitate processing of the payment authorization in accordance with a known, predetermined, or future developed process flow. The absence of the expected authentication value or token in the payment authorization request may trigger the processing of the payment authorization in accordance with an alternative or “exceptions” process flow or a termination of the process flow.
Referring to
Authentication management platform 405 may include or at least have access rights to one or more data storage facilities or repositories 410. In some embodiments, data repository 410 may include a relational database comprising one or more database nodes and manage data for a business enterprise providing, in some instances, data management functions related to authentication services, including but not limited to customer enrollment and customer data management (i.e., also referred to herein as customer enrollment/data management) and billing solution aspects. Repository 410 may house and manage all aspects and types of data in various data structures such as, for example, customer contact data related to customers in one or more different organizations within an organization, department, or other business entities of the enterprise. Authentication management platform 400 may further include back end systems 420 to support the data acquisition, data processing, and data management functions of authentication platform 405. In some embodiments, back end systems may be organized, at least logically, with business organizations of a business enterprise.
System 500 includes an authentication portal 505. Novel authentication portal 505 provides a mechanism for one or more external users (i.e., users external to an enterprise or business organization providing the services or functions of system 500) to communicate with and otherwise have access to authentication information managed by an authentication management platform herein. In some aspects, external users 515 may interface with authentication portal 505 via an external customer main portal 510. In some embodiments, external customer main portal 510 may include, at least in part, an outwardly facing graphical user interface that can be accessed by a computer or processor-enabled device such as a computer, tablet, or smartphone running an applicable application (e.g., “app”). External customer main portal 510 may be, in some embodiments, implemented and/or accessed via a browser, a browser extension, or an application programming interface (API). In some instances, external users 515 may include issuers, acquirers, and authorized third parties (e.g., issuer and acquirer service providers) that are enrolled or potentially enrolled in authentication services and applications of an authentication platform herein. In some embodiments, contact information for external customers 515 may be stored and managed by some implementations of external customer main portal 510.
An electronic data repository (EDR) 520 is included in system 500. EDR 520 may include a data storage facility such as a relational database management system to store, maintain, and manage, for example, historical data related to existing external customers 515 of an authentication platform herein. EDR 520 may include, at least in part, a cloud-based storage service, system, or application. In some embodiments, EDR 520 may be a centralized or a distributed database system comprising one or more database nodes or instances. EDR 520 may operate as a validation point for data being entered into or otherwise obtained by system 500 from external customers 500 in an on-going effort to ensure that such data is consistent with and accurately corresponds to data already known and being managed by an enterprise. In some embodiments, EDR 520 may automatically, based on one or more rules or actionable triggers, updated and validate data herein.
In some aspects, system 500 further includes a decision management platform or service 525. Decision management platform 525 may be a data management device or system (e.g., a relational database system) that stores the external customer information for the external customer 515 issuers, acquirers, and authorized third parties. In some particular embodiments, decision management platform or service 525 may include an authentication database 530. Authentication database 530 may store and maintain records, files, and other data structures representative of customer data including, but not limited to, contracts, notes (e.g., messages, documents, unstructured data, etc.), certification information, credit card ranges, payment device BINs (Bank Identification Numbers), merchant information, and other data.
System 500 may include an authentication database user interface 535 that provides, internal to an enterprise, an interface for internal authentication users 540 to access and otherwise communicate with decision management platform 525. In some aspects, authentication database user interface 535 provides a mechanism for internal authentication users 540 to access authentication information of an authentication platform to provide or at least facilitate customer support functions and business or analyst access to external customer authentication related data (e.g., contact information, billing information, etc.). Access to authentication database via authentication database user interface 535 may be restricted to the internal authentication users depending on a role of the internal authentication user(s).
In some embodiments, a number of different types of data can be provided to databases 610 via internal UI 615, including historical card range information 624, merchant information 626, external user contact information 628, testing and certification data 630, and issuer information 632. Other aspects and types of data related to one or more internal users of an authentication platform herein may be encompassed in some instances and embodiments herein, in addition to or as a substitute to the specific user information shown in
In some aspects, external customer main portal 618 provides similar functionality as the external customer main portal 510 of
Processor 705 communicates with a storage device 730. Storage device 730 may comprise any appropriate information storage device, including combinations of magnetic storage devices (e.g., a hard disk drive), optical storage devices, solid state drives, and/or semiconductor memory devices. In some embodiments, storage device 630 may comprise a database system.
Storage device 730 may store program code or instructions 735 that may provide computer executable instructions for updating and validating customer authentication data and storing the data records thereof further processing, analysis, and reporting purposes, in accordance with processes herein. Processor 705 may perform the instructions of the program instructions 735 to thereby operate in accordance with any of the embodiments described herein. Program code 735 may be stored in a compressed, uncompiled and/or encrypted format. Program code 735 may furthermore include other program elements, such as an operating system, a database management system, and/or device drivers used by the processor 705 to interface with, for example, peripheral devices. Storage device 730 may also include data 740 such as database records or look-up tables, including for example records of merchants, issuers, and acquirers participating in a particular authentication program or service and the addresses of the devices used by those entities to implement the service. Data 740 may be used by system 700, in some aspects, in performing one or more of the processes herein, including individual processes, individual operations of those processes, and combinations of the individual processes and the individual process operations.
All systems and processes discussed herein may be embodied in program instructions stored on one or more non-transitory computer-readable, processor-executable media. Such media may include, for example, a solid state drive, a floppy disk, a CD-ROM, a DVD-ROM, magnetic tape, and solid state Random Access Memory (RAM) or Read Only Memory (ROM) storage units. According to some embodiments, a memory storage unit may be associated with access patterns and may be independent from the device (e.g., magnetic, optoelectronic, semiconductor/solid-state, etc.) Moreover, in-memory technologies may be used such that databases, etc. may be completely operated in RAM memory at a processor. Embodiments are therefore not limited to any specific combination of hardware and software.
Embodiments have been described herein solely for the purpose of illustration. Persons skilled in the art will recognize from this description that embodiments are not limited to those described, but may be practiced with modifications and alterations limited only by the spirit and scope of the appended claims.
