Systems and methods for populating online applications using third party platforms

1. A system, comprising:

a communication interface configured to transmit a web-based form to a device of a user and receive an input selecting a third-party system to provide data to populate one or more fields of the web-based form; and

an application server, that, in conjunction with the communication interface, is configured to:

transmit, responsive to receiving the input via the communication interface, a call, using an application programming interface (API), to the selected third-party system;

request a set of data from the selected third-party system via the API;

receive the set of data via the API; and

transmit the received set of data to the device thereby causing the device to auto-populate the one or more fields and display the auto-populated one or more fields on a user interface of the device,

wherein:

the auto-populated one or more fields comprise a password associated with an account, the user, or both, and

displaying the auto-populated one or more fields on the user interface of the device comprises displaying a tokenized version of the password.

2. The system of claim 1 , wherein the application server is further configured to:

encrypt a first portion of the received set of data; and

cause the device to auto-populate the one or more fields with the encrypted first portion of the received set of data.

3. The system of claim 2 , wherein the application server is further configured to:

decrypt a second portion of the received set of data; and

cause the device to auto-populate the one or more fields with the decrypted second portion of the received set of data.

4. The system of claim 3 , wherein the first portion of the received set of data comprises a password, and the second portion of the received set of data comprises a username.

5. The system of claim 1 , wherein the web-based form comprises an account login screen.

6. The system of claim 1 , wherein the web-based form comprises a user input object configured to enable display of an untokenized version of the password.

7. The system of claim 6 , wherein:

the communication interface is further configured to:

receive a selection of the user input object; and

the application server is further configured to:

responsive to receiving the selection via the communication interface:

de-tokenize the tokenized version of the password; and

cause the device to display the untokenized version of the password.

8. A system, comprising:

a mobile application running on a first device and configured to cause the first device to display a first graphical user interface (GUI) comprising a first unpopulated field and receive input, via the first device, requesting to auto-populate the first unpopulated field using third-party system data associated with the first unpopulated field; and

an application server in communication with the mobile application and configured to:

transmit an application programming interface (API) call for the third-party system data associated with the first unpopulated field to a third-party system;

responsive to transmitting the API call, receive the third-party system data associated with the first unpopulated field; and

cause the mobile application to auto-populate the first unpopulated field with the received third-party system data,

wherein:

the received third-party system data comprises a password associated with an account, a user of the first device, or both, and

causing the mobile application to auto-populate the first unpopulated field comprises causing the mobile application to auto-populate the first unpopulated field with a tokenized version of the password.

9. The system of claim 8 , wherein the application server is further configured to encrypt a first portion of the received third-party system data, and wherein causing the mobile application to auto-populate the first unpopulated field comprises causing the mobile application to auto-populate the first unpopulated field with the encrypted first portion of the received third-party system data.

10. The system of claim 9 , wherein the application server is further configured to decrypt a second portion of the received third-party system data, and wherein causing the mobile application to auto-populate the first unpopulated field comprises causing the mobile application to auto-populate the first unpopulated field with the decrypted second portion of the received third-party system data.

11. The system of claim 10 , wherein the first portion of the received third-party system data comprises a password, and the second portion of the received third-party system data comprises a username.

12. The system of claim 8 , wherein the first GUI comprises a login screen.

13. The system of claim 8 , wherein the first GUI comprises a user input object configured to enable display of an untokenized version of the password.

14. The system of claim 13 , wherein:

the mobile application is further configured to:

receive a selection of the user input object; and

the application server is further configured to:

responsive to receiving the selection via the mobile application:

de-tokenize the tokenized version of the password; and

cause the first device to display the untokenized version of the password.

15. A system, comprising:

an application running on a first device and configured to cause the first device to display a first graphical user interface (GUI) comprising one or more unpopulated fields and receive input, via the first device, requesting to auto-populate the one or more unpopulated fields using third-party system data associated with the one or more unpopulated fields; and

a server in communication with the application and configured to:

transmit an application programming interface (API) call for the third-party system data associated with the one or more unpopulated fields to a third-party system;

receive the third-party system data associated with the one or more unpopulated fields; and

cause the application to auto-populate the one or more unpopulated fields with the received third-party system data,

wherein:

the received third-party system data comprises identification information associated with an account, a user of the first device, or both, and

causing the application to auto-populate the one or more unpopulated fields comprises causing the application to auto-populate the one or more unpopulated fields with a tokenized version of the identification information.

16. The system of claim 15 , wherein the server is further configured to encrypt a first portion of the received third-party system data and to decrypt a second portion of the received third-party system data.

17. The system of claim 16 , wherein causing the application to auto-populate the one or more unpopulated fields comprises causing the application to auto-populate the one or more unpopulated fields with the encrypted first portion and the decrypted second portion of the received third-party system data.

18. The system of claim 16 , wherein the first portion of the received third-party system data comprises a password, and the second portion of the received third-party system data comprises a username.

19. The system of claim 15 , wherein the application is further configured to cause the first device to receive additional input comprising a security code associated with a user of the first device.

20. The system of claim 19 , wherein causing the first device to receive the input requesting to auto-populate the one or more unpopulated fields using third-party system data is responsive to the first device receiving the security code.