Third-party access to secure hardware

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.

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.

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.