# US 2020/0394644 A1 · Third-party access to secure hardware

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

- Number: US 2020/0394644 A1
- Document ID: US20200394644A1
- Status: Published application
- Kind: A1
- Application number: 17/008,453
- Filed: 2020-08-31
- Published: 2020-12-17
- Earliest claimed: 2016-12-30
- Assignees: Square, Inc.
- Applicants: Square, Inc.
- Inventors: Brian Grassadonia; Ayokunle Omojola; Robert Andersen; Michael Moring; Daniele Perito
- Web page: https://patentgrep.com/patent/US20200394644A1

## CPC

- G06Q 20/363: {with the personal data of a user}
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/08: Payment architectures
- G06Q 20/0855: {involving a third party}
- G06Q 20/326: {Payment applications installed on the mobile devices}
- G06Q 20/386: {using messaging services or messaging apps (using mobile network messaging services for payment, e.g. SMS G06Q20/3255)}
- 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: 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

In one embodiment, a method includes, receiving, by a wallet application executing on a computing device, a user registration request from a user. The computing device includes a secure subsystem with secure elements and a secure operating system. The method includes sending the user registration request to a third-party payment application integrated with the wallet application. The third-party payment application is configured to execute within the secure subsystem based on a processor of the computing device being in a secure mode. The method includes receiving user registration information via a user interface generated based on instructions from the third-party payment application. The method includes providing the received user registration information to the third-party payment application in response to receiving authorization for the user registration request via the secure elements. The method includes receiving user account information for the user from a third-party payment server via the third-party payment application.

## Claims

### Claim at position 1

1-16. (canceled)

### Claim 17

A method comprising:
receiving, by a native wallet application executing on a user computing device, a user registration request from a user, wherein the user computing device comprises a secure subsystem comprising one or more secure elements and a secure operating system, the one or more secure elements comprising one or more hardware components;
sending, by the native wallet application, the user registration request to a third-party payment application integrated with the native wallet application, wherein the third-party payment application is configured to execute within the secure subsystem via the secure operating system and the one or more secure elements are accessible by the third-party payment application based on a processor of the user computing device being in a secure mode;
receiving, by the native wallet application, user registration information via a user interface generated based on instructions from the third-party payment application;
providing, by the native wallet application, the received user registration information to the third-party payment application in response to receiving authorization for the user registration request via the one or more secure elements; and
receiving, by the native wallet application, user account information for the user from a third-party payment server associated with the third-party payment application via the third-party payment application.

### Claim 18 (depends on 17)

The method of claim 17, wherein the user computing device further comprises a normal subsystem separate from the secure subsystem, the normal subsystem comprising a native operating system.

### Claim 19 (depends on 17)

The method of claim 17, further comprising:
displaying, by the native wallet application, the user account information on the user interface in response to receiving authorization for displaying the user account information via the one or more secure elements.

### Claim 20 (depends on 17)

The method of claim 17, wherein the hardware components comprise one or more of a fingerprint reader, retina scanner, camera, and antenna.

### Claim 21 (depends on 17)

The method of claim 17, wherein the native wallet application receives the user account information for the user from the third-party payment server responsive to providing the received user registration information to the third-party payment server via the third-party payment application; and
wherein the third-party payment server is configured to associate the user registration request with a user account.

### Claim 22 (depends on 17)

The method of claim 17, wherein the user computing device further comprises a native communication application that communicates with the third-party payment application and that further communicates with the secure subsystem to facilitate a payment transaction or to receive a payment.

### Claim 23 (depends on 17)

The method of claim 17, further comprising:
receiving, by the native wallet application, a payment request and a program code from a merchant computing device;
transferring, by native wallet application, the payment request and the program code to the third-party payment application integrated with the native wallet application after receiving authorization for the payment request via the one or more secure elements,
wherein, in response to receiving the payment request and the program code, the third-party payment application is configured to:
decode the program code; and
transmit a payment token to the merchant computing device based on the received authorization and the decoded program code.

### Claim 24 (depends on 23)

The method of claim 23, wherein the native wallet application receives the payment request and the program code from the merchant computing device via near-field communication; and
wherein the program code is included in a near-field communication code.

### Claim 25 (depends on 23)

The method of claim 23, wherein the program code comprises an identifier for an account of the user with the merchant.

### Claim 26 (depends on 23)

The method of claim 23, further comprising:
receiving, by the native wallet application, a status of the payment request from the third-party payment application; and
displaying, by the native wallet application, a notification of the status of the payment request via a user interface generated based on instructions from the third-party payment application.

### Claim 27 (depends on 23)

The method of claim 23, wherein the third-party payment server receives the payment token from the merchant computing device, the method further comprising:
receiving, by the native wallet application, a request for confirmation of the payment request corresponding to the payment token from the third-party payment server via the third-party payment application; and
providing, by the native wallet application, confirmation of the payment request to the third-party payment server via the third-party payment application in response to receiving authorization for the confirmation via the one or more secure elements.

### Claim 28 (depends on 17)

The method of claim 17, wherein the third-party payment application integrated with the native wallet application has permission to operate a thread on the processor in the secure mode via the secure operating system.

### Claim 29

A system comprising:
one or more processors,
a native wallet application stored in a memory of the system and executing on the system via the one or more processors,
a secure subsystem comprising one or more secure elements and a secure operating system, the one or more secure elements comprising one or more hardware components, and
a third-party payment application integrated with the native wallet application, wherein the third-party payment application is configured to execute within the secure subsystem via the secure operating system and the one or more secure elements are accessible by the third-party payment application based on the one or more processors being in a secure mode;
wherein the memory further comprises instructions operable by the one or more processors to cause the native wallet application to perform operations comprising:
receiving a user registration request from a user;
sending the user registration request to the third-party payment application integrated with the native wallet application;
receiving user registration information via a user interface generated based on instructions from the third-party payment application;
providing the received user registration information to the third-party payment application in response to receiving authorization for the user registration request via the one or more secure elements; and
receiving user account information for the user from a third-party payment server associated with the third-party payment application via the third-party payment application.

### Claim 30 (depends on 29)

The system of claim 29, wherein the system further comprises a normal subsystem separate from the secure subsystem, the normal subsystem comprising a native operating system.

### Claim 31 (depends on 29)

The system of claim 29, wherein the instructions are further operable by the one or more processors to cause the native wallet application to perform operations comprising:
displaying the user account information on the user interface in response to receiving authorization for displaying the user account information via the one or more secure elements.

### Claim 32 (depends on 29)

The system of claim 29, wherein the hardware components comprise one or more of a fingerprint reader, retina scanner, camera, and antenna.

### Claim 33

One or more computer-readable non-transitory storage media embodying software that is operable when executed to cause one or more processors of a user computing device to perform operations comprising:
receiving, by a native wallet application executing on the user computing device, a user registration request from a user, wherein the user computing device comprises a secure subsystem comprising one or more secure elements and a secure operating system, the one or more secure elements comprising one or more hardware components;
sending, by the native wallet application, the user registration request to a third-party payment application integrated with the native wallet application, wherein the third-party payment application is configured to execute within the secure subsystem via the secure operating system and the one or more secure elements are accessible by the third-party payment application based on a processor of the user computing device being in a secure mode;
receiving, by the native wallet application, user registration information via a user interface generated based on instructions from the third-party payment application;
providing, by the native wallet application, the received user registration information to the third-party payment application in response to receiving authorization for the user registration request via the one or more secure elements; and
receiving, by the native wallet application, user account information for the user from a third-party payment server associated with the third-party payment application via the third-party payment application.

### Claim 34 (depends on 33)

The computer-readable non-transitory storage media of claim 33, wherein the user computing device further comprises a normal subsystem separate from the secure subsystem, the normal subsystem comprising a native operating system.

### Claim 35 (depends on 33)

The computer-readable non-transitory storage media of claim 33, wherein the software is further operable when executed to cause one or more processors of a user computing device to perform operations comprising:
displaying, by the native wallet application, the user account information on the user interface in response to receiving authorization for displaying the user account information via the one or more secure elements.

### Claim 36 (depends on 33)

The computer-readable non-transitory storage media of claim 33, wherein the hardware components comprise one or more of a fingerprint reader, retina scanner, camera, and antenna.
