Method of retaining transaction context
Methods of transaction authentication are provided. In one such method, at least one first transaction has been conducted, the or each first transaction generating data including first data comprising authentication data and second data identifying the or each first transaction, wherein a given first transaction is between a merchant and a card holder. A cryptographically signed and/or encrypted token corresponding to the given first transaction and comprising a characteristic of the first transaction has been generated using at least said second data. The cryptographically signed and/or encrypted token has been transmitted to the merchant. The method comprises receiving, from the merchant, data corresponding to a second transaction and in the event that the data corresponding to the second transaction includes the cryptographically signed and/or encrypted token, responsively authenticating the cryptographically signed and/or encrypted token, whereby to determine an authenticated association between the second transaction and a given first transaction.
1. A method of transaction authentication, the method comprising:
receiving, from a merchant in a first transaction, first data comprising authentication data and second data identifying the first transaction and including a characteristic of the first transaction, the characteristic of the first transaction comprising a transaction identifier or a time and date of the first transaction, and data identifying a specific authentication process in which the merchant authenticates a card holder, wherein the first transaction is between the merchant and the card holder, wherein the merchant is unauthorized to store the first data;
responsive to receiving the first data and the second data, generating a cryptographically signed token corresponding to the first transaction by cryptographically signing the second data such that the cryptographically signed token comprises cryptographically signed (1) the characteristic of the first transaction comprising the transaction identifier or the time and date of the first transaction, and (2) data identifying the specific authentication process;
transmitting the cryptographically signed token to the merchant, the merchant thereafter storing the cryptographically signed token;
receiving, from the merchant, data corresponding to a second transaction and the cryptographically signed token, wherein the data corresponding to the second transaction is devoid of the first data and any additional authentication data;
authenticating the cryptographically signed token by cryptographically validating the cryptographically signed token using a public key of a public key certificate, wherein a successful authentication of the cryptographically signed token confers confidence that the first transaction has genuinely occurred and was successfully authenticated since the cryptographically signed token was generated using data identifying the specific authentication process associated with the first transaction, thereby
determining that an authenticated association exists between the second transaction and the first transaction based on the successful authentication of the cryptographically signed token using the public key; and
authorizing the second transaction when the authenticated association exists between the second transaction and the first transaction.
2. The method of claim 1 , further comprising:
transmitting data indicative of a result of the authentication of the cryptographically signed token to a payment card issuer.
3. The method of claim 2 , wherein the second transaction comprises a resubmission of the first transaction.
4. The method of claim 1 , further comprising:
transmitting data indicative of said determined authenticated association to a payment card issuer.
5. The method of claim 1 , wherein the first transaction is an EMV transaction and the authentication data is EMV authentication data.
6. The method of claim 1 , wherein the first transaction is a card-not-present transaction.
7. The method of claim 6 , wherein the authentication data comprises a card security code.
8. The method of claim 1 wherein at least the second transaction is one of a series of recurring transactions, each of the series of recurring transactions occurring in accordance with a pre-determined schedule.
9. The method of claim 1 , wherein the first transaction comprises authorization for a subsequent transaction or transactions including at least the second transaction, and in which at least one of a number, timing, and monetary amount of said subsequent transaction or transactions was unknown when the first transaction was conducted.
10. The method of claim 1 , wherein the characteristic of the first transaction is the transaction identifier.
11. The method of claim 1 , wherein the characteristic of the first transaction is the time and date of the first transaction.
12. The method of claim 1 , wherein the characteristic of the first transaction further includes data regarding channels in which subsequent transactions can occur without further authentication.
13. The method of claim 1 , wherein the first data is received from the merchant via an acquirer bank.
14. The method of claim 13 , wherein the acquirer bank validates details of the first transaction.
15. The method of claim 1 , wherein the characteristic of the first transaction further comprises data identifying the merchant.
16. The method of claim 1 , wherein the authentication process comprises a chip and PIN authentication process.
17. The method of claim 1 , wherein the authentication data comprises a card security code.
18. A non-transitory computer-readable storage medium comprising a set of computer-readable instructions stored thereon, which, when executed by at least one processor cause the at least one processor to perform a method comprising:
receiving, from a merchant in a first transaction, first data comprising authentication data and second data identifying the first transaction and including a characteristic of the first transaction, the characteristic of the first transaction comprising a transaction identifier or a time and date of the first transaction, and data identifying a specific authentication process in which the merchant authenticates a card holder, wherein the first transaction is between the merchant and the card holder, wherein the merchant is unauthorized to store the first data;
responsive to receiving the first data and the second data, generating a cryptographically signed token corresponding to the first transaction by cryptographically signing the second data such that the cryptographically signed token comprises cryptographically signed (1) the characteristic of the first transaction comprising the transaction identifier or the time and date of the first transaction, and (2) data identifying the specific authentication process;
transmitting the cryptographically signed token to the merchant, the merchant thereafter storing the cryptographically signed token;
receiving, from the merchant, data corresponding to a second transaction and the cryptographically signed token, wherein the data corresponding to the second transaction is devoid of the first data and any additional authentication data;
authenticating the cryptographically signed token by cryptographically validating the cryptographically signed token using a public key of a public key certificate, wherein a successful authentication of the cryptographically signed token confers confidence that the first transaction has genuinely occurred and was successfully authenticated since the cryptographically signed token was generated using data identifying the specific authentication process associated with the first transaction, thereby
determining that an authenticated association exists between the second transaction and the first transaction based on a successful authentication of the cryptographically signed token using the public key; and
authorizing the second transaction when the authenticated association exists between the second transaction and the first transaction.
19. Apparatus comprising:
at least one processor; and
at least one memory including computer program instructions
executable by the at least one processor, to perform a method comprising:
receiving, from a merchant in a first transaction, first data comprising authentication data and second data identifying the first transaction and including a characteristic of the first transaction, the characteristic of the first transaction comprising a transaction identifier or a time and date of the first transaction, and data identifying a specific authentication process in which the merchant authenticates a card holder, wherein the first transaction is between the merchant and the card holder, wherein the merchant is unauthorized to store the first data;
responsive to receiving the first data and the second data, generating a cryptographically signed token corresponding to the first transaction by cryptographically signing the second data such that the cryptographically signed token comprises cryptographically signed (1) the first characteristic of the first transaction comprising the transaction identifier or the time and date of the first transaction, and (2) data identifying the specific authentication process;
transmitting the cryptographically signed token to the merchant, the merchant thereafter storing the cryptographically signed token;
receiving, from the merchant, data corresponding to a second transaction and the cryptographically signed token, wherein the data corresponding to the second transaction is devoid of the first data and any additional authentication data;
authenticating the cryptographically signed token by cryptographically validating the cryptographically signed token using a public key of a public key certificate, wherein a successful authentication of the cryptographically signed token confers confidence that the first transaction has genuinely occurred and was successfully authenticated since the cryptographically signed token was generated using data identifying the specific authentication process associated with the first transaction, thereby
determining that an authenticated association exists between the second transaction and the first transaction based on a successful authentication of the cryptographically signed token using the public key; and
authorizing the second transaction based upon the authenticated association exists between the second transaction and the first transaction.