# US 2016/0260084 A1 · Secure mobile remote payments

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

- Number: US 2016/0260084 A1
- Document ID: US20160260084A1
- Status: Published application
- Kind: A1
- Application number: 15/063,212
- Filed: 2016-03-07
- Published: 2016-09-08
- Earliest claimed: 2015-03-06
- Assignees: Mastercard International Incorporated
- Applicants: MasterCard International Incorporated
- Inventors: Jonathan J. Main; Igor Fabyshev; Chintan Oza; Alan Wang
- Web page: https://patentgrep.com/patent/US20160260084A1

## CPC

- G06Q 20/401: {Transaction verification}
- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06Q 20/227: {characterised in that multiple accounts are available, e.g. to the payer}
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3674: {involving authentication}
- G06Q 2220/00: Business processing using cryptography
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- 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

Provided are systems and methods for conducting secure remote transactions between mobile devices and merchants.

## Claims

### Claim 1

A method for processing a checkout transaction, comprising:
receiving, at a server, a request to initiate a checkout transaction;
generating a request token including information identifying the checkout transaction;
receiving a verification token encrypted with a key of the server; and
providing checkout resources to a merchant for use by the merchant to complete the transaction if the verification token is validated by the server.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, at the server, a request to authorize the checkout transaction, the request received prior to providing checkout resources to the merchant.

### Claim 3 (depends on 1)

The method of claim 1, wherein the request to initiate a checkout transaction is received from a merchant server.

### Claim 4 (depends on 3)

The method of claim 3, wherein the merchant server is in communication with a merchant application on a mobile device of a user, where the checkout transaction involves a transaction between the user and a merchant associated with the merchant server and the merchant application.

### Claim 5 (depends on 1)

The method of claim 1, wherein the request to initiate a checkout transaction includes information identifying a merchant application initiating the checkout transaction and information identifying an initial transaction amount.

### Claim 6 (depends on 5)

The method of claim 5, wherein the request to initiate a checkout transaction further includes information identifying at least a first item to be purchased.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
encrypting the request token with a key associated with the server.

### Claim 8 (depends on 1)

The method of claim 1, wherein the verification token is received from a wallet proxy server.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
generating the verification token; and
transmitting the verification token to a wallet server proxy for transmission to a wallet application on a mobile device.

### Claim 10 (depends on 9)

The method of claim 9, wherein the verification token is generated upon receipt of a payment token associated with a payment instrument selected by a user of the mobile device.

### Claim 11 (depends on 10)

The method of claim 10, wherein the checkout resources include information associated with the payment token.

### Claim 12 (depends on 11)

The method of claim 11, wherein the checkout resources further include information identifying a transaction amount.

### Claim 13 (depends on 12)

The method of claim 12, wherein the transaction amount is at least one of: (i) the same as the initial transaction amount, and (ii) an amount different than the initial transaction amount.

### Claim 14

A method for operating a mobile device to conduct a transaction with a merchant, comprising:
transmitting a transaction initiation request message to a merchant server associated with a mobile application of the mobile device;
receiving, from the merchant server, a request token and, based at least in part on the request token, performing a cardholder validation method to validate a user of the mobile device;
transmitting, to a wallet proxy server, a token associated with a payment device to be used in the transaction;
receiving, from a wallet proxy server, an authorize checkout request message;
validating the authorize checkout request message using a key shared with the wallet proxy server; and
transmitting a checkout confirmation to the merchant server.

### Claim 15 (depends on 14)

The method of claim 14, wherein the mobile device does not store actual payment credentials.