Abstract:
A transaction is conducted between a merchant site and a customer's electronic device using a payment processor. The merchant site is associated with a client-side application and a server-side application. The client-side application executes on the customer's electronic device. The client-side application electronically sends payment information retrieved from the customer's electronic device to the payment processor. The client-side application does not send the payment information to the server-side application. The payment processor creates a token from the payment information sent by the client-side application. The token functions as a proxy for the payment information. The payment processor electronically sends the token to the client-side application. The client-side application electronically sends the token to the server-side application for use by the server-side application in conducting the transaction. The payment information can thus be used by the server-side application via the token without the server-side application being exposed to the payment information.
Abstract:
A transaction is conducted between a merchant site and a customer's electronic device using a payment processor. The merchant site is associated with a client-side application and a server-side application. The client-side application executes on the customer's electronic device. The client-side application electronically sends payment information retrieved from the customer's electronic device to the payment processor. The client-side application does not send the payment information to the server-side application. The payment processor creates a token from the payment information sent by the client-side application. The token functions as a proxy for the payment information. The payment processor electronically sends the token to the client-side application. The client-side application electronically sends the token to the server-side application for use by the server-side application in conducting the transaction. The payment information can thus be used by the server-side application via the token without the server-side application being exposed to the payment information.
Abstract:
A method and apparatus for providing a document-integrated software integration validation by a service provider system are described. The method includes detecting an application program interface (API) call generated by a user system in a test transaction, the API call comprising a test identifier (ID) and a user system ID, the test ID identifying an API integration test scenario and the user system ID identifying the user system. The method also includes tracking a sequence of API calls and responses. Furthermore, the method includes receiving login credentials from the user system. The method also includes verifying the received login credentials with previously established login credentials associated with the user system ID. Additionally, the method includes determining whether the sequence of API calls and responses is performed correctly for the test transaction and serving the interactive integration guide to the user system indicating a result for the API integration test scenario.
Abstract:
A method and apparatus for performing privacy preserving fraud detection in network based transactions are described. The method may include receiving a fraud detection message during a transaction between a user system and a merchant system, the message having a set of cryptographically transformed universal resource locator (URL) components generated from a URL of a web page of the merchant system on which the transaction is to occur. The method may also include generating one or more secure and anonymous fraud detection features, each fraud detection feature comprising a select subset of the cryptographically transformed URL components. The method may also include performing fraud detection for the web page using the one or more secure and anonymous fraud detection features to determine a likelihood that fraud is occurring in the transaction.
Abstract:
Described herein are systems and methods to use modeling techniques to identify gradual changes in various metrics identified as a result of analyzing an aggregated transaction dataset. In one method, a computer model dynamically slice the data using an attribute, calculates an entropy value for using a rolling time window, and uses the entropy value to identify anomalous behavior. The model may use information gain to determine whether to further segmented the data slice into smaller data slices. The model may iteratively slice and analyze the data until a data slice corresponding to the root cause is determined. The model may then traverse the hierarchy of data slices and combine the data slices until an optimized combined data slice. The model may train a machine learning component, such as a booted tree algorithm, to optimize its traversal of the hierarchy of data slices.
Abstract:
A method and apparatus for updating data router nodes in a distributed storage system are described. The method can include querying, by a first database agent of a database node, a cache data store for health status metrics of the cache data store. The method can also include storing, by the first database agent of the database node, the health status metrics in a data repository. Furthermore, the method can include obtaining, by a second database agent of a router node, the health status metrics from the data repository, and updating, by the second database agent of the router node, a database topology file based on the health status metrics.
Abstract:
Systems and methods are provided for filtering and/or creating Points-of-Interest (POIs). In one embodiment, a list of POIs is obtained and then filtered based on crowd data related to the list of POIs to provide a filtered list of POIs. In another embodiment, one or more crowd-sourced POIs are created based on one or more crowds relevant to a corresponding bounding region for POI creation.
Abstract:
In an example embodiment, interactions among services in a service proxy are recorded in an interaction log. A service graph manager then parses the interaction log. The service graph manager reads each interaction and then processes the interaction to determine if it violates the rules. If so, the service graph manager reports the violation to the software developer and also recommends an action to remedy the violation. In an example embodiment, this recommendation takes the form of an indication of which files to modify to allow the service interaction (e.g., which rule(s) to modify to ensure that the service interaction is not a violation). The software developer can then approve the proposed action, which can then be automatically implemented to ensure that once the service is sent to a quality assurance environment there will be no rules violation from the corresponding interaction(s).
Abstract:
Embodiments of the invention include a method of performing a payment transaction comprising receiving transaction data by a PIN pad terminal from a point-of-sale terminal, and receiving tender from a customer, by the PIN pad terminal. Tender data and the transaction data are sent to a service gateway, by the PIN pad terminal. The service gateway collects metadata from the tender data and the transaction data. The tender data is sent by the PIN pad terminal to the point-of-sale terminal, which sends the tender data and the transaction data to a merchant gateway for approval or denial of the tender data. The tender data sent to the POS may be encrypted. The service gateway may provide customer and merchant analytics based on the metadata, as well as perform security/fraud checks, BIN management, PIN pad management. Systems are also disclosed.
Abstract:
A method and apparatus for using cryptographically signed secure identifiers to detect fraud during network based transactions are described. The method may include receiving a transaction from a user device, the transaction comprising a secure identifier purported to be associated with the user device, and the transaction further comprising transaction data. The method may also include extracting a first identifier and a second identifier from the secure identifier purported to be associated with the user device, and then regenerating a true second identifier using the first identifier. Furthermore, when it is determined that the true second identifier matches the second identifier extracted from the secure identifier purported to be associated with the user device, the method may include determining that the secure identifier is valid, and processing the transaction based at least in part on the determination that the secure identifier is valid.