# US 2013/0254112 A1 · System and Method Including Chip-Based Device Processing For Transaction

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

- Number: US 2013/0254112 A1
- Document ID: US20130254112A1
- Status: Published application
- Kind: A1
- Application number: 13/899,523
- Filed: 2013-05-21
- Published: 2013-09-26
- Earliest claimed: 2010-04-09
- Assignees: Visa International Service Association
- Inventors: Ayman Hammad
- Web page: https://patentgrep.com/patent/US20130254112A1

## CPC

- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q 20/00: Payment architectures, schemes or protocols (apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12)
- 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

Present embodiments are directed to a server computer. The server computer establishes a first channel of communication to receive payment device data in a first format (e.g., chip type) and establishes a second channel to receive the payment device data in a second format (e.g., legacy type). The server computer receives an authorization request message in the second format from a merchant and generates a new authorization request message in the first format. The server computer then forwards the new authorization request to the issuer for approval.

## Claims

### Claim at position 1

-20. (canceled)

### Claim 21

A method comprising:
receiving, at a server computer, a first authorization request from a merchant through a communications channel, wherein the first authorization request message includes an identifier of a financial account associated with an issuer, and wherein the first authorization request message is in a first format;
creating, by the server computer, a second authorization request message corresponding to the first authorization request message, wherein the second authorization request message is in a second format that is more secure than the first format, and wherein creating the second authorization request message comprises adding a data element to the first authorization request message; and
forwarding, by the server computer, the second authorization request message to the issuer for approval.

### Claim 22 (depends on 21)

The method of claim 21, wherein the communications channel is a second communications channel, and wherein the method further comprises receiving, at the server computer, account information through a first communications channel between the server computer and a client computer.

### Claim 23 (depends on 22)

The method of claim 22, wherein the data element is determined based upon the received account information.

### Claim 24 (depends on 22)

The method of claim 22, wherein a verification token associated with the client computer previously interacted with a portable device, and wherein the method further comprises:
generating, by the server computer, a verification value associated with the received account information; and
forwarding, by the server computer, the verification value to the client computer through the first communications channel.

### Claim 25 (depends on 24)

The method of claim 24, wherein the portable device is associated with the issuer, and wherein the first authorization request message includes the verification value.

### Claim 26 (depends on 25)

The method of claim 25, wherein determining the data element based upon the received account information comprises identifying, by the server computer, the account information using the verification value.

### Claim 27 (depends on 21)

The method of claim 21 further comprising:
receiving, at the server computer, a first authorization response message from the issuer, wherein the first authorization response message is in the second format that is more secure than the first format;
creating, by the server computer, a second authorization response message corresponding to the first authorization response message, wherein the second authorization response message is in the first format, and wherein creating the second authorization response message comprises removing the data element from the first authorization response message; and
forwarding, by the server computer, the second authorization response message to the merchant through the communications channel.

### Claim 28

A server computer comprising:
a processor; and
a computer readable medium coupled to the processor, wherein the computer readable medium includes code executable by the processor for implementing a method comprising:
receiving a first authorization request from a merchant through a communications channel, wherein the first authorization request message includes an identifier of a financial account associated with an issuer, and wherein the first authorization request message is in a first format;
creating a second authorization request message corresponding to the first authorization request message, wherein the second authorization request message is in a second format that is more secure than the first format, and wherein creating the second authorization request message comprises adding a data element to the first authorization request message; and
forwarding the second authorization request message to the issuer for approval.

### Claim 29 (depends on 28)

The server computer of claim 28, wherein the communications channel is a second communications channel, and wherein the method further comprises receiving account information through a first communications channel between the server computer and a client computer.

### Claim 30 (depends on 29)

The server computer of claim 29, wherein the data element is determined based upon the received account information.

### Claim 31 (depends on 29)

The server computer of claim 29, wherein a verification token associated with the client computer previously interacted with a portable device, and wherein the method further comprises:
generating a verification value associated with the received account information; and
forwarding the verification value to the client computer through the first communications channel.

### Claim 32 (depends on 31)

The server computer of claim 31, wherein the portable device is associated with the issuer, and wherein the first authorization request message includes the verification value.

### Claim 33 (depends on 32)

The server computer of claim 32, wherein determining the data element based upon the received account information comprises identifying the account information using the verification value.

### Claim 34 (depends on 28)

The server computer of claim 28 further comprising:
receiving a first authorization response message from the issuer, wherein the first authorization response message is in the second format that is more secure than the first format;
creating a second authorization response message corresponding to the first authorization response message, wherein the second authorization response message is in the first format, and wherein creating the second authorization response message comprises removing the data element from the first authorization response message; and
forwarding the second authorization response message to the merchant through the communications channel.

### Claim 35

A method comprising:
receiving, at a client computer, account information from a data storage of a portable device;
establishing, by the client computer, a secure communications channel with a remote server computer; and
forwarding, by the client computer, the account information to the server computer, wherein the server computer thereafter:
receives a first authorization request message from a merchant for a transaction, wherein the first authorization request message is received in a first format; and
sends a second authorization request message for the transaction in a second format to an issuer, wherein the second format is more secure than the first format.

### Claim 36 (depends on 35)

The method of claim 35, wherein the server computer creates the second authorization request message by adding a data element to the first authorization request message.

### Claim 37 (depends on 36)

The method of claim 36, wherein the server computer determines the data element based upon the account information.

### Claim 38 (depends on 35)

The method of claim 35 further comprising receiving, at the client computer, a verification value associated with the forwarded account information from the server computer.

### Claim 39 (depends on 35)

The method of claim 35, wherein the client computer uses a verification token to receive the account information from the data storage of the portable device.

### Claim 40 (depends on 39)

The method of claim 39, wherein the verification token is embedded in the client computer.
