Third-party access to secure hardware
AssigneeSquare, Inc.
InventorsBrian Grassadonia, Ayokunle Omojola, Robert Andersen, Michael Moring, Daniele Perito
Life of this patent
Estimating the term…
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.
Claims13
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.
Dependencies are inferred from the claim text.