US 11,080,697 B2Granted

Systems and methods for use in authenticating users in connection with network transactions

AssigneeMastercard International Incorporated

InventorsSowmya Reddy Lakka, Brian Piel, Vincenzo Palomba, Jonathan James Main, David Anthony Roberts

Life of this patent

Estimating the term…

Loading patent…

Abstract

Systems and methods are provided for authenticating users to payment accounts in connection with transactions. An exemplary method includes receiving, by at least one computing device, an authentication request for a transaction associated with a payment account where the authentication request includes a token associated with the payment account and a cryptogram, and mapping the token to a primary account number (PAN) for the payment account. The method also includes validating the cryptogram, generating a directory server nonce (DSN) for the authentication request, and transmitting the DSN and the account number to an access control server (ACS) associated with an issuer of the payment account. The method further includes, in response to an issuer authentication value (IAV), compiling an accountholder authentication value (AAV) including the IAV, the DSN and an amount of the transaction, and transmitting the AAV to one of a merchant and a server.

Claims20

Dependent claims

A system for use in authenticating users to accounts in connection with network transactions, the system comprising:

a payment network, wherein the payment network is separate from a merchant, an acquirer associated with the merchant, and an issuer of a payment account;
a directory server (DS) included in the payment network and coupled in communication with an access control server (ACS) and a digital service server (DSS);
the ACS associated with the issuer and coupled in communication with the DS;
and
the DSS coupled in communication with the DS, wherein the DSS is separate from the merchant, the acquirer, and the issuer;
wherein the DS is configured to:
receive an authentication request for a transaction directed to the merchant from a merchant server plug-in (MPI) associated with the merchant, the transaction involving the payment account, the payment account associated with an account number, and the authentication request including at least one of a token associated with the payment account and the account number;
and
transmit the at least one of the token and the account number to the DSS;
wherein, in response to receiving the at least one of the token and the account number, the DSS is configured to:
generate a directory server nonce (DSN) for the authentication request;
and
transmit the DSN and the account number for the payment account to the DS;
wherein, in response to receiving the DSN and the account number, the DS is configured to transmit the DSN and the account number to the ACS;
wherein, in response to receiving the DSN and the account number, the ACS is configured to:
generate an issuer authentication value (IAV);
and
transmit the IAV to the DS;
wherein, in response to receiving the IAV from the ACS, the DS is configured to:
compile an accountholder authentication value (AAV) as evidence of completed authentication for the transaction, the AAV including the IAV, the DSN, and an amount of the transaction;
and
transmit the AAV to the MPI;
wherein the payment network is configured to:
receive an authorization request for the transaction from the MPI, the authorization request including the AAV;
validate the AAV;
and
based on validation of the AAV, transmit the authorization request to the issuer;
and
wherein the issuer is configured to validate the IAV prior to approving or declining the transaction.

26 more elements

A computer-implemented method for use in authenticating a user to a payment account in connection with a transaction, the method comprising:

receiving, by a directory server (DS), an authentication request for a transaction directed to a merchant and associated with a payment account, the authentication request including a token associated with the payment account and a cryptogram, wherein the DS is included in a payment network, and wherein the payment network is separate from the merchant, an acquirer associated with the merchant, and an issuer of the payment account;
transmitting, by the DS, the token and the cryptogram to a digital service server (DSS), the DSS separate from the merchant, the acquirer, and the issuer;
mapping, by the DSS, the token to a primary account number (PAN) for the payment account;
validating, by the DSS, the cryptogram;
in response to validating the cryptogram, generating, by the DSS, a directory server nonce (DSN) for the authentication request;
transmitting, by the DSS, the DSN and the PAN to the DS;
in response to receiving the DSN and the PAN, transmitting, by the DS, the DSN and the PAN to an access control server (ACS) associated with the issuer of the payment account;
generating, by the ACS, an issuer authentication value (IAV);
transmitting, by the ACS, the IAV to the DS;
in response to receiving the IAV from the ACS, compiling, by the, an accountholder authentication value (AAV) as evidence of completed authentication, the AAV including the IAV, the DSN, and an amount of the transaction;
transmitting, by the DS, the AAV to one of the merchant and a merchant server plug-in (MPJ) associated with the merchant;
receiving, by the payment network, an authorization request for the transaction including the AAV from one of the merchant and the MPI;
validating, by the payment network, the AAV;
based on validating the AAV, transmitting, by the payment network, the authorization request to the issuer of the payment account;
and
validating, by the issuer, the IAV prior to approving or declining the transaction.

13 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/725,893Filed 5 Oct 2017
Published: US 2019/0108515 A111 Apr 2019
Granted: 3 Aug 2021
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

G06Q 20/385
Payment protocols; Details thereof: using an alias or single-use codes
G06Q 20/04
Payment architectures, schemes or protocols: payment circuits
G06Q 20/12
Payment architectures: specially adapted for electronic shopping systems
G06Q 20/38215
Electronic credentials: use of certificates or encrypted proofs of transaction rights