Disclosed herein are systems and methods for predicting on-file payment credentials. The methods can include obtaining, from a financial institution, transaction data comprising one or more transactions conducted at one or more merchants. For each respective merchant of the one or more merchants, the methods can include parsing each of the one or more transactions at the respective merchant to create a merchant profile for the respective merchant, the merchant profile comprising merchant behavior data for the respective merchant. The methods can determine a likelihood of a respective associated merchant having the payment credential information on file by calculating a score for the merchant based on the merchant profile. The score can represent that the merchant profile is indicative of the associated merchant having the payment credential information stored on file.

Disclosed is a system and method for implementing a network enabling an interoperable exchange of electronic payment information, which connects two parties to a transaction using established rules, technology, and trust model. Such systems and methods provide a shared set of rules and common APIs, and enable validation of the accuracy of all data exchanged via API. In order to maintain data, the systems and methods described herein enable each participant to only see interactions and information that is relevant and permissioned to such participant, all while maintaining no central data store for the sensitive electronic payment information. Each participant is vetted and authorized by a system administrator as a validated “Credential Service Provider” (“CSP”) and governed by rules created and managed by the administrator. Further, an auditable trail of all transactions is maintained by logging metadata to track events and changes to permissions.

In one embodiment, a payment service system-implemented method of assigning payment card numbers for individual user accounts associated with the payment service system includes receiving payment card numbers activated by a third-party server that are unassigned to accounts registered. The method includes receiving a first transaction authorization request for one of the payment card numbers and denying the request, without notifying the third-party server, based on the number being unregistered with the payment service system. The method includes receiving, via an executable application, a request to register a user account for a payment service system user, and in response, generating a record assigning the payment card number to the user account. The method includes receiving a second transaction authorization request for the payment card number, authorizing the request based on the number being assigned to the user account, and notifying the third-party server, causing user account's balance to be modified.

A system, method and computer-readable medium are provided to enable digital bank endorsement. A digital image of a back side of a check may be placed in a computer memory. Appropriate coordinates for a bank endorsement may be determined. A bank endorsement may be automatically generated. The digital image may then be electronically altered by overlaying, merging, or rendering text of the generated bank endorsement. A modified digital image may be combined with an image of the front side of the check and stored and/or exported to check clearing operations.

A method involves a first participating unit having an electronic coin data set registered in a coin register of a payment system. The method includes: generating a transaction data set relating to the transmission of the electronic coin data set to a second participating unit; encrypting the generated transaction data set using a cryptographic key, wherein the cryptographic key is composed of at least two cryptographic sub-keys of different respective remote entities; and initiating a communication connection to a transaction register of the payment system in order to transmit the encrypted transaction data set to the transaction register.

A system and a method are disclosed for context-based verification flows for digital identity verification. A context-based verification system provides flexible identification procedures for various enterprises that are adapted to the enterprises' services, the enterprises' customers, and these customers' needs. For example, the context-based verification system determines first and second verification flows associated with a first enterprise and a third verification flow associated with a second enterprise. These verification flows include context parameters and verification parameters. The context-based verification system determines context parameters of a request, or “request context parameters,” when a user requests to interact with the first enterprise and determines a verification flow associated with context parameters that substantially match these request context parameters. The context-based verification system may determine that the first verification flow's context parameters substantially match the request context parameters and use the first verification flow's verification parameters to verify the user's identity.

A method to create advertisement and sales trackability is provided. The method includes collecting a consumer data and retrieving, from a publishing server, a media data linking an audience with a content provided by the publishing server, the content including an advertisement for a product, and retrieving a retailer data indicative of a purchase track record of the product. The method also includes identifying one or more attributes of a population segment associated with the consumer data, the media data, and the retailer data, determining an adjustment factor indicative of a statistical data associated with the population segment, and generating, based on the adjustment factor, a measurement scheme to support a decision to modify, improve, or cancel a campaign. A system and a non-transitory, computer-readable medium storing instructions to perform the above method are also provided.

Disclosed is a computer implemented method, system and computer readable medium for performing blockchain-based identity management for a supply chain of a computerised network. In one aspect, the method includes receiving, by a computerised device of a party, an identity issuing transaction initiated by a computerised component or service being in the supply chain, the identity issuing transaction being indicative of a name of the computerised component or service, an identity issuing request message, and a first random number obtained from a distributed database, wherein the identity issuing transaction is initiated by the computerised component or service in response to determining the party is an authoritative party recorded in the blockchain and permitted to issue an identity, invoking a first smart contract, and executing an identity issuance logic of the first smart contract.

A distributed enhanced payment processing system includes a merchant point of sale (POS) terminal system and a remote payment management system. The POS terminal system initiates a transaction that includes receiving a payment amount, a purchaser account identifier, a virtual electronic payment indicator, and a merchant ID via a payment client. Subsequently, the POS terminal system outputs the transaction to the remote payment management system which generates a token for the transaction. The payment management system then provides the purchaser account identifier, a merchant account identifier, and the payment amount to a remote virtual electronic payment (VEP) entity system. Upon receiving a VEP entity system response, the payment management system outputs the response and token to the POS terminal system.

Techniques associated with a dual state merchant-facing device are described herein. A point-of-sale system can comprise multiple devices, such as a customer-facing device and a merchant-facing device that is coupled to the customer-facing device and can operate in a first state or a second state. In at least one example, the merchant-facing device operating in the first state can present a graphical user interface (GUI) on a display. The merchant-facing device can transition from the first state to the second state, the second state enabling the merchant-facing device to perform at least one additional functionality that is not available to the merchant-facing device in the first state, and can update the GUI based at least in part on the at least one additional functionality.