Systems and methods for associating a proxy card with an electronic wallet are disclosed. A computer implemented method may include receiving an authentication information of a proxy card, and associating the proxy card with an electronic wallet, wherein associating the proxy card with the electronic wallet allows secure access to the electronic wallet when the proxy card is presented at a point of sale. A system may include a proxy card comprising authentication information, and an electronic wallet associated with the proxy card, wherein the association of the electronic wallet with the proxy card allows secure access to the electronic wallet when the proxy card is presented at a point of sale. A wallet redemption card may comprise a rewriteable magnetic stripe, a smart chip, a wireless communicator operably connected to the smart chip, and an interface operably connected between the rewriteable magnetic stripe and the smart chip.

Systems, methods, articles of manufacture, and computer-readable media. A web browser of a device may receive selection of a uniform resource locator (URL). An operating system may download an application from an application server based on the URL. The application may identify a plurality of applications installed on the device and select a first institution corresponding to a first application. The application may receive a cryptogram from a contactless card associated with the first institution and transmit the cryptogram to an authentication server. The application may receive an authentication result specifying the authentication server decrypted the cryptogram. The web browser may receive, based on the decryption of the cryptogram, an account number, an expiration date associated with the account number, and a card verification value (CVV) associated with the account number. The web browser may provide the account number, expiration date, and CVV to a server associated with the application.

A method for detecting fraudulent transactions may include receiving transaction data for a plurality of transactions, assigning a unique identifier to each transaction, sorting the plurality of transactions into a first plurality of groups of transactions by a first sorting parameter, assigning the unique identifier of a first transaction within each group to all other transactions within the respective group, sorting the plurality of transactions into a second plurality of groups of transactions by a second sorting parameter, assigning the unique identifier of a second transaction within each group to all other transactions within the respective group, determining whether each group of transactions is a sequence of fraudulent transactions, and upon determining that a group of transactions is a sequence of fraudulent transactions, marking each transaction among the determined group of transactions as potentially fraudulent.

Secure authentication and delayed transaction processing for booking management systems is provided. Third-party services partner with booking management systems to aggregate and list offerings of the third-party services in a digestible display on a one-stop platform. A booking management system can manage the authentication of payment card information on behalf of any number of such third-party services. The booking management system can maintain and process authentication information associated with traveler payment cards, and provide virtual payment information to the third-party services for payment following chargeable events. The third-party services may later initiate a transactions using the virtual payment information, without being required to perform authentication processing on the traveler payment card information maintained by the booking management system.

A computerized method electronically signs and authenticates documents using cards with associated private keys. A hash of a document is obtained from a user by a cloud point of sale (POS) server and a document signing request to sign the obtained hash with a card is received. The document signing request is received via the presentation of the card. The server causes the obtained hash to be signed using the private key of the card and an associated signature ID is generated. The signed hash and generated signature ID are stored, and the generated signature ID is provided to the user for use in future authentication of the document. Later, a document authentication request is received that includes the generated signature ID and a hash of a target document to be authenticated. The signed hash is decrypted and compared to the hash of the target document to determine its authenticity.

Embodiments of the invention are directed to systems and methods of providing secure remote transaction (SRT) transactions. In some embodiments, a resource provider is able to embed a checkout element into a webpage that it hosts. The checkout element enables interaction between a user that has accessed the webpage and an initiator application server located remotely in order to complete a transaction while preventing the resource provider from gaining access to sensitive information. In some embodiments, the user's information may be determined by an initiator server and populated into the checkout element.

A method of providing a secure service at a computing node is described. The secure service is for a requesting party external to the computing node. The following steps take place at the computing node. A service request is received from the requesting party. This service request comprises a request to generate a credential. The credential is then generated, and service-related information is obtained. The credential and the service-related information are encrypted using an encryption process to form an encrypted message part. A service-identifying clear message part is also created, and a message is sent comprising the clear message part and the encrypted message part to the requesting party. Methods of using such a message to validate the credential, and of using such a message to confirm the integrity of service-related information held in the message, are also described, as is computing apparatus adapted to carry out one or more of these methods.

A method and apparatus for processing a transaction between a merchant and a customer of the merchant are described. The method may include generating, at an ingress server, an initial transaction message by generating a deterministic identifier for a card used in the transaction from card data received for the transaction and encrypting the received card data. The method may also include providing the initial transaction message from the ingress server to a payment server. Furthermore, the method may include updating, by the payment server in response to an authorization of the transaction determined based at least in part on the deterministic identifier for the card, the initial transaction message with authorization data, and providing the updated initial transaction message from the payment server to an egress server. The method may also include communicating a final transaction message to an authorization system for processing the transaction between the merchant and the customer based on the card data.

In various embodiments, a system and method for providing simplified checkout are provided. In example embodiments, an identifier that corresponds to a payment account of a user is received at a payment provider system. Account information from the payment account of the user is retrieved from a payment data storage of the payment provider system. The account information is used in a payment transaction involving a merchant system. A payment interface having transaction fields populated with the account information retrieved from the payment account of the user is presented to the user while the user maintains a presence on a webpage of a merchant system.

Methods are provided for authenticating an initiator of a transaction during processing of the transaction. Methods may include initiating a transaction, including transaction details, at a transaction initiation node. Methods may include transmitting the transaction to a processing entity. Methods may include identifying that the transaction is above a threshold of anomalous transactions based on historic transactions associated with the transaction details. Methods may include transmitting an authorization request from the processing entity to a payment card linked to the transaction details. Methods may include receiving the authorization request at the payment card. Methods may include approving and/or denying the authorization request at the payment card. Approving and/or denying the request may include input of a signature and/or biometric. Methods may include transmitting the approval and/or denial from the payment card to the processing entity. The processing entity may transmit the approval and/or denial to the transaction initiation node.