Abstract: A method for preventing mobile payment is described. The method comprises generating an authorization request, via a payment module, based on sensitive data on a mobile device. The authorization request is transmitted from the payment module to an issuer system. The issuer system sends a neutralization trigger. In response to receiving the neutralization trigger, the payment module is disabled.

Abstract: A method for two factor authentication is described. The method comprises sending an activation code stored on a mobile device to a server for verification. An encrypted secret key generated by the server using the activation code is received. The secret key is decrypted using the activation code stored on the mobile device. The mobile device encrypts the secret key using a predetermined PIN. As a result of a user inputting the predetermined PIN, the secret key is decrypted, the mobile device generates a first token using the secret key and transmits the first token to the server to authenticate the user. After receiving authentication from the server, the information on the mobile device is synced with the server.

Abstract: A method for preventing mobile payment is described. The method comprises receiving an authorization request at an issuer system from a payment module on a mobile device. The authorization request may be based on sensitive data on the mobile device. The issuer system determines whether the mobile device is missing. The issuer system sends a neutralization trigger to the mobile device, and in response to receiving the neutralization trigger, the payment module is disabled.

Abstract: A method for two factor authentication is described. The method comprises a server receiving an activation code for verification from a mobile device. The server generates an encrypted secret key using the activation code The secret key is encrypted and sent to the mobile device. The server receives a first token generated by the mobile device. The server generates a second token using the secret key, determines whether the first token is identical to the second token, and syncs information with the mobile device.

Abstract: Methods of de-tokenizing secure payment tokens are disclosed. A method according to some embodiments includes receiving a request from an issuer to de-tokenize a secure payment token associated with a transaction conducted using a mobile terminal, generating a metric indicative of a risk of de-tokenizing the secure payment token, comparing the metric indicative of the risk of de-tokenizing the secure payment token to a predetermined threshold, and transmitting a response to the request to de-tokenize the secure payment token, wherein the response is based on the comparison of the metric indicative of the risk of de-tokenizing the secure payment token with the predetermined threshold.

Abstract: A method for alternate primary account number generation is described. The method comprises receiving, from a device, an input data string containing sensitive data. The input data string comprises a first portion, a second portion, and a third portion. A plurality of values is generated using the second portion of the input data string, wherein each of the plurality of values are of a predetermined amount of numbers, each of the plurality of values having a corresponding key. A first key is selected, based on the second portion, from the plurality of values. A second key is generated using the first key. An output value is selected, based on the second key, from the plurality of values. An output data string is generated using the first portion, the output value, and the third portion.

Abstract: Methods of de-tokenizing secure payment tokens are disclosed. A method according to some embodiments includes receiving a request from an issuer to de-tokenize a secure payment token associated with a transaction conducted using a mobile terminal, generating a metric indicative of a risk of de-tokenizing the secure payment token, comparing the metric indicative of the risk of de-tokenizing the secure payment token to a predetermined threshold, and transmitting a response to the request to de-tokenize the secure payment token, wherein the response is based on the comparison of the metric indicative of the risk of de-tokenizing the secure payment token with the predetermined threshold.

Abstract: A method for preventing mobile payment is described. The method comprises generating an authorization request, via a payment module, based on sensitive data on a mobile device. The authorization request is transmitted from the payment module to an issuer system. The issuer system sends a neutralization trigger. In response to receiving the neutralization trigger, the payment module is disabled.

Abstract: A method for two factor authentication is described. The method comprises a server receiving an activation code for verification from a mobile device. The server generates an encrypted secret key using the activation code The secret key is encrypted and sent to the mobile device. The server receives a first token generated by the mobile device. The server generates a second token using the secret key, determines whether the first token is identical to the second token, and syncs information with the mobile device.

Abstract: A method for two factor authentication is described. The method comprises sending an activation code stored on a mobile device to a server for verification. An encrypted secret key generated by the server using the activation code is received. The secret key is decrypted using the activation code stored on the mobile device. The mobile device encrypts the secret key using a predetermined PIN. As a result of a user inputting the predetermined PIN, the secret key is decrypted, the mobile device generates a first token using the secret key and transmits the first token to the server to authenticate the user. After receiving authentication from the server, the information on the mobile device is synced with the server.

Abstract: A method for communicating payment status is described. The method comprises receiving an authorization request, via a local merchant terminal, at an issuer system. The authorization request may be generated during a contactless transaction. The authorization request is verified at the issuer system. The issuer system generates a first verification response and a second verification response. The issuer system transmits the first verification response directly to a payment module on a mobile device. The issuer also transmits the second verification response to the local merchant terminal.

Abstract: A method for communicating payment status is described. The method comprises generating an authorization request, via a payment module, on a mobile device. The authorization request may be generated during a contactless transaction. The authorization request is transmitted to an issuer system for verification via a local merchant terminal. The payment module receives a first verification response directly from the issuer system, and determines a transaction status from the first verification response.

Abstract: A method for preventing mobile payment is described. The method comprises receiving an authorization request at an issuer system from a payment module on a mobile device. The authorization request may be based on sensitive data on the mobile device. The issuer system determines whether the mobile device is missing. The issuer system sends a neutralization trigger to the mobile device, and in response to receiving the neutralization trigger, the payment module is disabled.