# US 2017/0286944 A1 · Secure transfer of payment data

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

- Number: US 2017/0286944 A1
- Document ID: US20170286944A1
- Status: Published application
- Kind: A1
- Application number: 15/513,753
- Filed: 2015-06-02
- Published: 2017-10-05
- Earliest claimed: 2014-09-24
- Assignees: Bpay Group Limited
- Applicants: Bpay Group Limited
- Inventors: Keith Brown
- Web page: https://patentgrep.com/patent/US20170286944A1

## CPC

- G06Q 20/3223: {Realising banking transactions through M-devices}
- G06F 21/606: {by securing the transmission between two devices or processes}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/326: {Payment applications installed on the mobile devices}
- G06Q 20/3829: {involving key management}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4014: {Identity check for transactions}
- G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment
- H04L 63/168: {above the transport layer}
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04W 12/065: Continuous authentication
- H04W 12/068: {using credential vaults, e.g. password manager applications or one time password [OTP] applications}
- H04W 12/069: using certificates or pre-shared keys
- G06Q 2220/00: Business processing using cryptography
- H04L 9/3271: {using challenge-response}
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

This disclosure relates to a payee applications and payment applications installed on a mobile communication device. The device authenticates the payee application with a transaction server and sends transaction data to the transaction server. The device then receives from the transaction server a transaction identifier and sends the transaction identifier to a payment application installed on the mobile communication device to allow the payment application to access the transaction data from the transaction server. In response, the device receives from the payment application a payment confirmation associated with the transaction identifier and sends to the transaction server a request for payment status, the request comprising the transaction identifier. Finally, the device receives response data indicative of the payment status from the transaction server and determines a validity of the payment confirmation based on the response data from the transaction server.

## Claims

### Claim 1

A method as performed by a payee application installed on a mobile communication device to validate a confirmation of a payment, the method comprising:
authenticating the payee application with a transaction server;
sending transaction data to the transaction server;
receiving from the transaction server a transaction identifier;
sending the transaction identifier to a payment application installed on the mobile communication device to allow the payment application to access the transaction data from the transaction server;
receiving from the payment application a payment confirmation associated with the transaction identifier;
sending to the transaction server a request for payment status, the request comprising the transaction identifier;
receiving response data indicative of the payment status from the transaction server; and
determining a validity of the payment confirmation based on the response data from the transaction server.

### Claim 2 (depends on 1)

The method of claim 1, wherein sending the transaction identifier comprises sending the transaction identifier in plain text.

### Claim 3 (depends on 1)

The method of claim 1, wherein the step of sending the transaction data is performed before receiving the transaction identifier and receiving the transaction identifier comprises receiving the transaction identifier associated with the transaction data.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
sending a request for a transaction identifier to the transaction server, wherein
the steps of sending the request for a transaction identifier and receiving the transaction identifier are performed before sending the transaction data, and
sending the transaction data comprises sending the transaction identifier.

### Claim 5 (depends on 1)

The method of claim 1, wherein the steps of sending the transaction data, receiving the transaction identifier, sending a request for payment status and receiving response data comprises using a direct communication channel between the payee application and the transaction server.

### Claim 6 (depends on 5)

The method of claim 5, wherein using the direct communication channel comprises using an encrypted communication channel between the payee application and the transaction server.

### Claim 7 (depends on 6)

The method of claim 6, wherein using an encrypted communication channel comprises using an Secure Socket Layer communication channel.

### Claim 8 (depends on 1)

The method of claim 1, wherein the steps of sending the transaction data, receiving the transaction identifier, sending a request for payment status and receiving response data comprises using an indirect communication channel between the payee application and the transaction server via a payee server.

### Claim 9 (depends on 8)

The method of claim 8, wherein using the indirect communication channel comprises using an encrypted communication channel between the payee application and the payee server.

### Claim 10 (depends on 9)

The method of claim 9, wherein using an encrypted communication channel comprises using an Secure Socket Layer communication channel.

### Claim 11 (depends on 1)

The method of claim 1, wherein sending the transaction identifier to the payment application comprises performing a call of the payment application using the transaction identifier as a parameter value of the call.

### Claim 12 (depends on 11)

The method of claim 11, wherein performing a call to the payment application comprises generating a Uniform Resource Locator comprising the transaction identifier as a parameter.

### Claim 13

(canceled)

### Claim 14 (depends on 1)

A non-transitory computer readable medium with an executable program stored thereon that when executed causes a computer to perform the method of claim 1.

### Claim 15 (depends on 1)

An Application Programming Interface that when installed on a mobile communication device as part of a payee application causes the mobile communication device to perform the method of claim 1.

### Claim 16

A mobile communication device comprising:
a program memory to store a payee application installed on the mobile communication device and a payment application installed on the mobile communication device;
a first data port to facilitate communication with a transaction server;
a second data port to facilitate communication between the payee application and the payment application; and
a processor to
authenticate the payee application with a transaction server using the first data port;
send transaction data to the transaction server using the first data port;
receive from the transaction server a transaction identifier using the first data port;
send the transaction identifier to the payment application using the second data port to allow the payment application to access the transaction data from the transaction server using the first data port;
receive from the payment application a payment confirmation associated with the transaction identifier using the second data port;
send to the transaction server a request for payment status using the first data port, the request comprising the transaction identifier;
receive response data indicative of the payment status from the transaction server using the first data port; and
determine a validity of the payment confirmation based on the response data from the transaction server.

### Claim 17

(canceled)

### Claim 18

A method as performed by a payment application installed on a mobile communication device to initiate a payment, the method comprising:
receiving a transaction identifier from a payee application installed on the mobile communication device;
authenticating the payment application with a transaction server;
sending to the transaction server a request for transaction data, the request comprising the transaction identifier;
receiving reply data from the transaction server associated with the transaction identifier;
determining a validity of the transaction identifier based on the reply data from the transaction server; and
in response to determining that the transaction identifier is valid
determining the transaction data based on the reply data,
initiating a payment based on the transaction data and associated with the transaction identifier,
receiving a first payment confirmation associated with the transaction identifier, and
sending a second payment confirmation associated with the transaction identifier to the payee application to allow the payee application to request payment status data from the transaction server.

### Claim 19 (depends on 18)

The method of claim 18, wherein sending the payment confirmation comprises sending the payment confirmation in plain text.

### Claim 20 (depends on 18)

The method of claim 18, wherein the steps of
receiving the transaction identifier;
sending the request for transaction data; and
receiving reply data;
comprises using an indirect communication channel between the payment application and the transaction server via a payment server.

### Claim 21 (depends on 18)

A non-transitory computer readable medium with an executable program stored thereon that when executed causes a computer to perform the method of claim 18.

### Claim 22

A mobile communication device comprising:
a program memory to store a payee application installed on the mobile communication device and a payment application stored on the mobile communication device;
a first data port to facilitate communication with a transaction server;
a second data port to facilitate communication between the payee application and the payment application; and
a processor to
receive a transaction identifier from a payee application installed on the mobile communication device using the second data port,
authenticate the payment application with a transaction server using the first data port,
send to the transaction server a request for transaction data, the request comprising the transaction identifier using the first data port,
receive reply data from the transaction server associated with the transaction identifier using the first data port,
determine a validity of the transaction identifier based on the reply data from the transaction server, and
in response to determining that the transaction identifier is valid
determine the transaction data based on the reply data,
initiate a payment based on the transaction data and associated with the transaction identifier using the first data port,
receive a first payment confirmation associated with the transaction identifier using the first data port, and
send using the second data port a second payment confirmation associated with the transaction identifier to the payee application to allow the payee application to request payment status data from the transaction server.

### Claim 23

A method as performed by a transaction server, the method comprising:
authenticating a payee application with the transaction server;
receiving from the payee application first transaction data;
generating a first transaction identifier;
storing the first transaction data associated with the first transaction identifier as a first record of multiple records on a database;
sending the first transaction identifier to the payee application;
authenticating a payment application with the transaction server;
receiving from a payment application a second transaction identifier;
determining a second record of the multiple records that is associated with the second transaction identifier;
determining the second transaction data of the second record;
sending the second transaction data to the payment application;
receiving a payment confirmation associated with a third transaction identifier;
storing in a third record of the multiple records that is associated with the third transaction identifier a first payment status indicative of the payment confirmation;
receiving from the payee application a request for payment status comprising a fourth transaction identifier;
determining a fourth record of the multiple records that is associated with the fourth transaction identifier;
determining whether the fourth record comprises a second payment status that is indicative of a payment confirmation; and
in response to determining that the fourth record comprises a second payment status that is indicative of a payment confirmation sending the second payment status of the fourth record to the payee application.

### Claim 24 (depends on 23)

A non-transitory computer readable medium with an executable program stored thereon that when executed causes a computer to perform the method of any one of claim 23.

### Claim 25

A transaction server comprising:
a communication port to communicate with a payee application and a payment application;
a database to store multiple records of transaction data;
a processor configured to:
authenticate the payee application with the transaction server;
receive from the payee application first transaction data;
generate a first transaction identifier;
store the first transaction data in association with the first transaction identifier as a first record of the multiple records on the database;
send the first transaction identifier to the payee application;
authenticate the payment application with the transaction server;
receive from a payment application a second transaction identifier;
determine a second record of the multiple records that is associated with the second transaction identifier;
determine the second transaction data of the second record;
send the second transaction data to the payment application;
receive a payment confirmation associated with a third transaction identifier;
store in a third record of the multiple records that is associated with the third transaction identifier a first payment status indicative of the payment confirmation;
receive from the payee application a request for payment status comprising a fourth transaction identifier;
determine a fourth record of the multiple records that is associated with the fourth transaction identifier;
determine whether the fourth record comprises a second payment status that is indicative of a payment confirmation;
in response to determining that the fourth record comprises a second payment status that is indicative of a payment confirmation send the second payment status of the fourth record to the payee application.
