# US 2021/0342832 A1 · E-Commerce Security Assurance Network

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

- Number: US 2021/0342832 A1
- Document ID: US20210342832A1
- Status: Published application
- Kind: A1
- Application number: 17/245,957
- Filed: 2021-04-30
- Published: 2021-11-04
- Earliest claimed: 2020-04-30
- Assignees: Bright Lion, Inc.
- Applicants: Bright Lion, Inc.
- Inventors: Lawrence B. LeBel; Brian D. Tawney; Cathi L. Peck; Kurt L. Sussman
- Web page: https://patentgrep.com/patent/US20210342832A1

## CPC

- G06Q 20/401: {Transaction verification}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/04: Payment circuits
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3827: {Use of message hashing}
- G06Q 30/0633: {Managing shopping lists, e.g. compiling or processing purchase lists (shipping orders G06Q10/083; order filling G06Q10/087)}
- 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

## Abstract

This disclosure describes techniques that enable a security assurance network to secure entry of sensitive payment data associated with a merchant transaction. A security assurance webserver is configured to receive order context data associated with the merchant transaction, and selectively establish a secure webpage on the client workstation that overlays a presentation of a merchant webpage. The security assurance webserver may receive encrypted payment data via the secure webpage for transmission to an application server within a security assurance network, and in response, facilitate a processing of the payment data via the application server. In turn, the application server may transmit a payment message indicating whether the payment data was successfully processed.

## Claims

### Claim 1

A security assurance webserver, comprising:
one or more processors;
memory coupled to the one or more processors, the memory including one or more modules that are executable by the one or more processors to:
receive, from an enterprise server, order context data associated with a merchant transaction at a client workstation;
determine whether to establish, at the client workstation, a secure webpage that overlays a presentation of a merchant webpage on the client workstation, the secure webpage to receive payment data associated with the merchant transaction;
in response to establishing the secure webpage, transmit, via a second secure communication connection, the payment data to an application server, the application server to process the payment data; and
transmit via the secure webpage, a payment message indicating whether the payment data was processed.

### Claim 2 (depends on 1)

The security assurance webserver of claim 1, wherein the order context data includes at least a merchant identifier and purchase data associated with the merchant transaction.

### Claim 3 (depends on 1)

The security assurance webserver of claim 1, wherein the one or more modules are further executable by the one or more processors to:
generate a secure webpage configuration data for delivery to the client workstation via the enterprise server, the secure webpage configuration data to initiate a secure communication connection between the client workstation and the security assurance webserver, and
wherein, to establish the secure webpage is based at least in part on delivery of the secure webpage configuration data to the client workstation.

### Claim 4 (depends on 3)

The security assurance webserver of claim 3, wherein the one or more modules are further executable by the one or more processors to:
receive, from the enterprise server, a checkout timer that commenced at a first point-in-time when the merchant transaction was initiated at the client workstation, the checkout timer to expire at a second point-in-time that follows the first point-in-time by a predetermined time interval, and
wherein to determine to establish the secure webpage is based at least in part on delivery of the secure webpage configuration data to the enterprise server prior to an expiration of the checkout timer.

### Claim 5 (depends on 4)

The security assurance webserver of claim 4, wherein to determine not to establish the secure webpage is based at least in part on the expiration of the checkout timer prior to delivery of the secure webpage configuration data to the enterprise server, and
wherein the one or more modules are further executable by the one or more processors to transmit, to the enterprise server, an alert message responsive to the expiration of the checkout timer.

### Claim 6 (depends on 1)

The security assurance webserver of claim 1, wherein the one or more modules are further executable by the one or more processors to:
receive, from the client workstation, a request to initiate a secure communication connection with the client workstation, and
wherein to establish the secure webpage at the client workstation, based at least in part on the request.

### Claim 7 (depends on 1)

The security assurance webserver of claim 1, wherein the one or more modules are further executable by the one or more processors to:
receive the payment data via the secure webpage, the payment data to include a personal account number and sensitive account data.

### Claim 8 (depends on 1)

The security assurance webserver of claim 1, wherein the one or more modules are further executable by the one or more processors to:
receive, from the application server, a processing message indicating whether the payment data was processed, and
wherein, to transmit the payment message via the secure webpage is based at least in part on the processing message.

### Claim 9

A computer-implemented method, comprising:
under control of one or more processors:
receiving, at a security assurance webserver and from an enterprise server, order context data associated with a merchant transaction at a client workstation;
generating, a first secure connection between the client workstation and the security assurance webserver;
determining whether to establish, via the first secure connection, a secure webpage that overlays a presentation of a merchant webpage on the client workstation;
receiving, via the secure webpage, encrypted payment data associated with the merchant transaction;
transmitting, via a second secure connection, the encrypted payment data to an application server; and
receiving, via the second secure connection, a processing message indicating whether the payment data was processed.

### Claim 10 (depends on 9)

The computer-implemented method of claim 9, further comprising:
generating a secure webpage configuration data for delivery to the client workstation via the enterprise webserver, the secure webpage configuration data to initiate a secure communication connection between the client workstation and the security assurance webserver, and
wherein, establishing the secure webpage is based at least in part on delivery of the secure webpage configuration data to the client workstation.

### Claim 11 (depends on 10)

The computer-implemented method of claim 10, further comprising:
analyzing the order context data to identify at least a merchant service provider identifier associated with the merchant transaction, and
wherein generating the secure webpage configuration data is based at least in part on the merchant service provider identifier.

### Claim 12 (depends on 10)

The computer-implemented method of claim 10, further comprising:
receiving, from the enterprise webserver, a checkout timer that commenced at a first point-in-time when the merchant transaction was initiated at the client workstation, the checkout timer to expire at a second point-in-time that follows the first point-in-time by a predetermined time interval, and
wherein, determining to establish the secure webpage is based at least in part on delivery of the secure webpage configuration data to the enterprise server prior to an expiration of the checkout timer.

### Claim 13 (depends on 12)

The computer-implemented method of claim 12, wherein determining not to establish the secure webpage is based at least in part on the expiration of the checkout timer prior to delivery of the secure webpage configuration data to the enterprise server, and further comprising:
generating an alert message for delivery to the enterprise server, the alert message indicating that a processing error associated with the merchant transaction has occurred.

### Claim 14 (depends on 9)

The computer-implemented method claim 9, further comprising:
receiving, from the client workstation, a request to initiate a secure communication with the client workstation; and
establishing the secure webpage based at least in part on the request.

### Claim 15 (depends on 9)

The computer-implemented method of claim 9, further comprising:
in response to receiving the processing message, transmitting, via the secure webpage, a payment message indicating whether the payment data was processed, based at least in part on the processing message.

### Claim 16

An enterprise webserver, comprising:
one or more processors;
memory coupled to the one or more processors, the memory including one or more modules that are executable by the one or more processors to:
receive, from a client workstation, a first message associated with a merchant transaction at a merchant website;
generate a server identity data for use in validating an identity of the enterprise webserver;
in response to validating the identity of the enterprise webserver, transmit a secure webpage dataset to the client workstation, the secure webpage dataset including a set of computer-executable instructions that initiate a secure communication connection between the client workstation and a security assurance webserver to establish a secure webpage, the secure webpage to overlay a presentation of the merchant website on the client workstation; and
receive, from the client workstation, a second message indicating a processing status of the merchant transaction, based at least in part on establishing the secure webpage.

### Claim 17 (depends on 16)

The enterprise webserver of claim 16, wherein the one or more modules are further executable by the one or more processors to:
in response to not validating the identity of the enterprise webserver, transmit an alert message to the client workstation indicating that a processing error of the merchant transaction has occurred.

### Claim 18 (depends on 16)

The enterprise webserver of claim 16, wherein the server identity data includes at least a hash of a set of files stored on the enterprise webserver, and wherein the one or more modules are further executable by the one or more processors to:
transmit, to a hashing server, the server identity data for validating the identity of the enterprise webserver; and
receive, from the hash server, a response associated with validating the identity of the enterprise webserver.

### Claim 19 (depends on 16)

The enterprise webserver of claim 16, wherein the one or more modules are further executable by the one or more processors to:
in response to validating the identity of the enterprise webserver, generate an order context data for delivery to the security assurance webserver, based at least in part on the first message, the order context data to include at least a merchant identifier and purchase order context data associated with the merchant transaction; and
receive, from the security assurance webserver, the secure webpage dataset, based at least in part on the order context data.

### Claim 20 (depends on 19)

The enterprise webserver of claim 19, wherein the one or more modules are further executable by the one or more processors to:
generate a checkout timer that commences at a first point-in-time when the merchant transaction is initiated at the client workstation, the checkout timer to expire at a second point-in-time that proceeds the first point-in-time by a predetermined time interval;
transmit the checkout timer to the security assurance webserver;
receive, from the security assurance webserver, an alert message responsive to an expiration of the checkout timer prior to delivery of the secure webpage dataset to the enterprise webserver; and
transmit to the client workstation, a second alert message indicating that a processing error of the merchant transaction has occurred.
