# US 11,443,325 B2 · Computer system and computer-implemented method for processing an electronic commerce transaction using a network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,443,325 B2
- Document ID: US11443325B2
- Status: Granted
- Kind: B2
- Application number: 16/561,261
- Filed: 2019-09-05
- Published: 2020-03-19
- Granted: 2022-09-13
- Earliest claimed: 2018-09-13
- Assignees: Mastercard International Incorporated
- Applicants: Mastercard International Incorporated
- Inventors: Manu Dharmaiah Kallugudde; Satya Sudipta Padhiary
- Web page: https://patentgrep.com/patent/US11443325B2

## CPC

- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- H04L 63/0838: {using one-time-passwords}
- G06Q 20/3674: {involving authentication}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/425: {using two different networks, one for transaction and one for security confirmation}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L 2463/102: applying security measure for e-commerce
- H04L 2463/121: Timestamp
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A payment network server for processing an electronic commerce (e-commerce) transaction initiated by a customer is described. The server comprises at least a computer processor and a data storage device, where the data storage device comprises instructions operative by the processor to: (i) receive, from a merchant server, an authentication request, the authentication request comprising at least a payment card identifier associated with a payment card; (ii) generate an authentication code associated with the e-commerce transaction for authenticating the customer; (iii) store, in a payment network database, the authentication code as a stored authentication code; (iv) transmit, the authentication code for transmission to the customer and an indication of the payment card to an issuer server; (v) receive, from the merchant server, a customer entered authentication code which was entered by the customer into a merchant website associated with the merchant server; (vi) determine if the customer entered authentication code matches the stored authentication code; if the customer entered authentication code matches the stored authentication code: (vii) generate an authentication indication; (viii) store, in the payment network database, the authentication indication as a stored authentication indication; and (ix) transmit, to the merchant server, an authentication response comprising the authentication indication.

## Claims

### Claim 1

A payment network server for processing an electronic commerce (e-commerce) transaction initiated by a customer, the server comprising at least a computer processor and a data storage device, the data storage device comprising instructions operative by the processor to:
receive, from a merchant server, an authentication request, the authentication request comprising at least a payment card identifier associated with a payment card;
generate an authentication code associated with the e-commerce transaction for authenticating the customer, a portion of the authentication code comprising a unique identifier;
store, in a payment network database, the authentication code as a stored authentication code;
transmit the unique identifier to the merchant server, wherein the merchant server presents the unique identifier to the consumer via a merchant website associated with the merchant server;
transmit the authentication code and an indication of the payment card to an issuer server, wherein the issuer server communicates the authentication code to the customer;
receive, from the merchant server, a customer entered authentication code which was entered by the customer into the merchant website;
determine if the customer entered authentication code matches the stored authentication code; and
if the customer entered authentication code matches the stored authentication code:
generate an authentication indication;
store, in the payment network database, the authentication indication as a stored authentication indication; and
transmit, to the merchant server, an authentication response comprising the authentication indication.

### Claim 2 (depends on 1)

The server of claim 1, wherein the processor is further configured to:
receive, from the merchant server, a transaction request comprising a received authentication indication, the payment card identifier and a payment amount associated with the e-commerce transaction;
determine if the received authentication indication matches the stored authentication indication;
generate an on-behalf service message if the received authentication indication matches the stored authentication indication, the on-behalf service message indicating that the e-commerce transaction has been authenticated;
transmit, to the issuer server, an authorisation request comprising the on-behalf service message, the indication of the payment card and the payment amount;
receive, from the issuer server, an authorisation response indicating if the e-commerce transaction is authorised or refused; and
transmit, to the merchant server, a transaction response indicating whether the e-commerce transaction is approved or refused, the e-commerce transaction is approved if it is authorised.

### Claim 3 (depends on 1)

The server of claim 1, wherein the merchant website is designed using an application programming interface associated with the payment network server.

### Claim 4 (depends on 1)

The server of claim 1, wherein the payment card identifier comprises a payment card number of the payment card.

### Claim 5 (depends on 1)

The server of claim 1, wherein the payment card identifier comprises a token, the processor is further configured to identify, using the payment network database, a payment card number associated with the token, and the indication of the payment card.

### Claim 6 (depends on 1)

The server of claim 1, wherein the authentication code is a one-time password.

### Claim 7 (depends on 1)

The server of claim 1, wherein the authentication code is valid for a predetermined authentication code time period.

### Claim 8 (depends on 1)

The server of claim 1, wherein the authentication indication is valid for a predetermined authentication indication time period.

### Claim 9 (depends on 8)

The server of claim 8, wherein the predetermined authentication indication time period is determined by the issuer server.

### Claim 10 (depends on 1)

The server of claim 1, wherein the authentication indication is an accountholder authorisation value (AAV) or a cardholder authentication verification value (CAVV).

### Claim 11

A computerised method for processing an e-commerce transaction initiated by a customer, the method comprising:
receiving, from a merchant server, an authentication request, the authentication request comprising at least a payment card identifier;
generating an authentication code associated with the e-commerce transaction for authenticating the customer, a portion of the authentication code comprising a unique identifier;
storing, in a payment network database, the authentication code as a stored authentication code;
transmitting the unique identifier to the merchant server, wherein the merchant server presents the unique identifier to the consumer via a merchant website associated with the merchant server;
transmitting the authentication code and an indication of the payment card to an issuer server, wherein the issuer server communicates the authentication code to the customer;
receiving, from the merchant server, a customer entered authentication code which was entered by the customer into a merchant website associated with the merchant server;
determining if the customer entered authentication code matches the stored authentication code; and
if the customer entered authentication code matches the stored authentication code:
generating an authentication indication;
storing, in the payment network database, the authentication indication as a stored authentication indication; and
transmitting, to the merchant server, an authentication response comprising the authentication indication.

### Claim 12 (depends on 11)

The method of claim 11 further comprising:
receiving, from the merchant server, a transaction request comprising a received authentication indication, the payment card identifier and a payment amount associated with the e-commerce transaction;
determining if the received authentication indication matches the stored authentication indication;
generating an on-behalf service message if the received authentication indication matches the stored authentication indication, the on-behalf service message indicating that the e-commerce transaction has been authenticated;
transmitting, to the issuer server, an authorisation request comprising the on-behalf service message, the indication of the payment card and the payment amount;
receiving, from the issuer server, an authorisation response indicating if the e-commerce transaction is authorised or refused; and
transmitting, to the merchant server, a transaction response indicating whether the e-commerce transaction is approved or refused, the e-commerce transaction is approved if it is authorised.

### Claim 13 (depends on 11)

The method of claim 11, wherein the merchant web site is designed using an application programming interface associated with the payment network server.

### Claim 14 (depends on 11)

The method of claim 11, wherein the payment card identifier comprises a payment card number associated with the payment card.

### Claim 15 (depends on 11)

The method of claim 11, wherein the payment card identifier is in the form of a token, the method further comprises identifying, using the payment network database, a payment card number associated with the token, and the indication of the payment card.

### Claim 16 (depends on 11)

The method of claim 11, wherein the authentication code is a one-time password.

### Claim 17 (depends on 11)

The method of claim 11, wherein the authentication code is valid for a predetermined authentication code time period.

### Claim 18 (depends on 11)

The method of claim 11, wherein the authentication indication is valid for a predetermined authentication indication time period.

### Claim 19 (depends on 18)

The method of claim 18, wherein the predetermined authentication indication time period is determined by the issuer server.

### Claim 20

A non-transitory computer-readable medium having stored thereon program instructions for causing at least one processor to:
receive, from a merchant server, an authentication request, the authentication request comprising at least a payment card identifier;
generate an authentication code associated with the e-commerce transaction for authenticating the customer, a portion of the authentication code comprising a unique identifier;
store, in a payment network database, the authentication code as a stored authentication code;
transmit the unique identifier to the merchant server, wherein the merchant server presents the unique identifier to the consumer via a merchant website associated with the merchant server;
transmit the authentication code and an indication of the payment card to an issuer server, wherein the issuer server communicates the authentication code to the customer;
receive, from the merchant server, a customer entered authentication code which was entered by the customer into a merchant website associated with the merchant server;
determine if the customer entered authentication code matches the stored authentication code; and
if the customer entered authentication code matches the stored authentication code:
generate an authentication indication;
store, in the payment network database, the authentication indication as a stored authentication indication; and
transmit, to the merchant server, an authentication response comprising the authentication indication.