Third-party access to secure hardware

Patent metadata

Field	Value
Publication number	US-10762495-B2
Application number	US-201615395975-A
Country	US
Kind code	B2
Filing date	Dec 30, 2016
Priority date	Dec 30, 2016
Publication date	Sep 1, 2020
Grant date	Sep 1, 2020

Abstract

Integrating third-party applications and native applications allows platform designers to provide greater services than otherwise would be available. This integration can increase security, provide more features, and give users a better experience with devices. Examples of such integration can allow third-party applications to have access to hardware and to provide seamless services to users. Such services can include registering payment accounts, allowing for loyalty programs, and providing additional information and services in native applications to provide a seamless experience.

First claim

We claim:

1. A system comprising:
a third-party payment server configured to receive payment authorization requests from a merchant-acquirer server and to receive user registration requests from one or more user computing devices;
a user computing device comprising a processor and configured to transmit the user registration request to the third-party payment server and including:
a native wallet application stored in a memory of the user computing device;
a third-party payment application integrated with the native wallet application, wherein the third-party payment application is configured to receive a user registration request from the native wallet application;
a normal subsystem; and
a secure subsystem, separate from the normal subsystem, comprising one or more secure elements and a secure operating system, wherein the third-party payment application is integrated with the native wallet application, wherein the third-party payment application can execute within the secure subsystem via the secure operating system,

wherein the one or more secure elements are accessible by the third-party payment application based on the processor being in a secure mode, and wherein the one or more secure elements comprise one or more hardware components,
wherein the native wallet application is configured to receive the user registration request from a user,
wherein the third-party payment application is configured to receive the user registration request from the native wallet application and generate a user interface to register a user,
wherein the native wallet application is configured to:
display the user interface,
receive user registration information via the user interface, and
send the user registration information to the third-party payment application,

wherein the third-party payment application is configured to send the user registration information to the third-party payment server,
wherein, in response to receiving the user registration request, the third-party payment server is configured to associate the user registration request with a user account comprising an account number and an account balance;
wherein the third-party payment server is further configured to generate a payment token corresponding to the account balance and to transmit the payment token to the third-party payment application;
wherein the secure subsystem is configured to receive the payment token from the third-party payment application;
wherein the user computing device is further configured to receive the account balance from the third-party payment application, based on the payment token and via the native wallet application, and to display the account balance on the user interface;
wherein the user computing device is further configured to transmit the payment token to a merchant computing device involving a payment transaction between the user and a merchant associated with the merchant computing device; and
the merchant computing device, in response to receiving the payment token, is configured to transmit a payment authorization request comprising the payment token, through the merchant-acquirer server, to the third-party payment server.

2. The system according to claim 1 , wherein the secure subsystem is further configured to transmit the payment token to the merchant computing device, and the merchant computing device is further configured to transmit the payment token and a payment amount to the third-party payment server.

3. The system according to claim 2 , wherein the third-party payment server is further configured to deduct the payment amount from the account balance associated with the payment token.

4. The system according to claim 3 , wherein the third-party payment server is further configured to transmit a notification of the payment transaction to the third-party payment application.

5. The system according to claim 1 , wherein the user computing device further comprises a native communication application that communicates with the third-party payment application that further communicates with the secure subsystem to effect the payment transaction from the account balance.

6. The system according to claim 1 , wherein the user computing device further comprises a native communication application that communicates with the third-party payment application that further communicates with the secure subsystem to receive a payment comprising an amount, and to add the amount to the account balance.

7. The system according to claim 1 , wherein the third-party payment application further comprises an interface to perform an add-cash request and a cash-out request.

8. The system of claim 7 , wherein the third-party payment application, upon receiving the add-cash request or the cash-out request, is further configured to generate a prompt to download a separate application to complete either the add-cash request or the cash-out request.

9. The system of claim 8 , wherein the separate application is configured to complete the add-cash request or the cash-out request.

10. The system according to claim 1 , further comprising a secure operating system that is separate from a native operating system, and the third-party payment application is integrated with the native wallet application, such that the third-party payment application is supported by the secure operating system.

11. The system according to claim 1 , wherein the third-party payment application integrated with the native wallet application has appropriate permissions to access the secure subsystem.

12. The system according to claim 1 , wherein the third-party payment application integrated with the native wallet application has permissions to operate a thread in a secure mode.

13. The system according to claim 1 , wherein the one or more secure elements comprise a fingerprint reader.

Assignees

• Square Inc

Inventors

• Grassadonia Brian
• Omojola Ayokunle
• Andersen Robert
• Moring Michael
• Perito Daniele

Classifications

• G06Q20/027

  involving a payment switch or gateway · CPC title

• G06Q20/08

  Payment architectures · CPC title

• G06Q20/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 · CPC title

• G06Q20/363 Primary

  with the personal data of a user · CPC title

• G06Q20/326

  Payment applications installed on the mobile devices · CPC title