Systems and methods for creating dynamic sessions for mobile application integration
Systems and methods for mobile application integration are described. These may include receiving a payment request a mobile application, sending a payment application detection request, receiving a detection response, and sending a customized user interface to the mobile device. The customized user interfaces are determined by whether an associated payment application is present on the mobile device and whether the mobile device is authenticated with the payment processing platform. These techniques can allow for a better user experience when interacting with the payment processing platform.
1. A system comprising:
a non-transitory memory; and
one or more hardware processors coupled with the non-transitory memory and configured to execute instructions from the non-transitory memory to cause the system to perform operations comprising:
receiving, from a browser object associated with a mobile application of a computing device, a transaction request for processing a transaction during a session associated with the mobile application;
transmitting, to the mobile application, programming code that causes the computing device to retrieve authentication credentials from a web application running on the computing device, the authentication credentials for authenticating a user of the computing device with a service provider associated with the web application, the web application being different from the mobile application;
automatically authenticating the user for a session associated with the transaction request based on the authentication credentials;
processing the transaction for the user based on the authenticating the user; and
in response to authenticating the user based on the authentication credentials retrieved from the web application, causing the browser object to store an authentication session token in a data store of the browser object associated with the mobile application, the authentication session token usable for authenticating the user by the mobile application in a subsequent interaction with the user.
2. The system of claim 1 , wherein the transmitting the programming code is performed in response to determining that the authentication session token is not present in the data store.
3. The system of claim 1 , wherein the authentication credentials indicates that the user is authenticated by a hosting server of the web application.
4. The system of claim 1 , wherein the authentication credentials are retrieved from the web application using an operating system application programming interface (API).
5. The system of claim 4 , wherein the operating system API is a mobile operating system API.
6. The system of claim 4 , wherein the operating system API includes a cookie manager usable to access stored authentication session tokens.
7. The system of claim 1 , wherein the authenticating the user for the session comprises:
validating the authentication credentials with values in a hosting database; and
transmitting the authentication session token to the browser object for storage.
8. The system of claim 1 , wherein the authentication session token is associated with the mobile application.
9. A method comprising:
receiving, from a browser object associated with a mobile application of a computing device, a transaction request for processing a transaction during a session associated with the mobile application;
transmitting, to the mobile application, programming code that causes the computing device to retrieve authentication credentials from a web application running on the computing device;
authenticating a user of the computing device for the session associated with the transaction request based on the authentication credentials, wherein the transaction is processed based on the authenticating the user; and
in response to authenticating the user based on the authentication credentials retrieved from the web application, causing the browser object to store an authentication session token in a data store of the browser object associated with the mobile application, the authentication session token usable for authenticating the user by the mobile application during a subsequent session.
10. The method of claim 9 , further comprising:
providing a customized user interface to the browser object for display.
11. The method of claim 9 , wherein the authenticating the user comprises:
validating the authentication credentials using data stored on a hosting server.
12. The method of claim 9 , wherein the authenticating the user further comprises:
transmitting the authentication session token to the computing device for storage on the browser object.
13. The method of claim 9 , wherein the authentication credentials indicates that the user is authenticated by a hosting server of the web application.
14. The method of claim 9 , wherein the authentication session token is associated with the mobile application.
15. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:
transmitting, to a mobile application of a computing device, programming code that causes the computing device to retrieve authentication credentials from a web application running on the computing device, the authentication credentials being retrieved for a transaction request received by the mobile application during a session between a user of the computing device and the mobile application;
authenticating the user of the computing device for the session associated with the transaction request based on the authentication credentials; and
in response to authenticating the user based on the authentication credentials retrieved from the web application, (i) processing the transaction and (ii) causing the browser object to store an authentication session token in a data store of the browser object associated with the mobile application, the authentication session token usable for authenticating the user by the mobile application in a subsequent interaction with the user.
16. The non-transitory machine-readable medium of claim 15 , wherein the transmitting the programming code is performed in response to determining that the authentication session token is not present in the data store.
17. The non-transitory machine-readable medium of claim 15 , wherein the authentication credentials indicates that the user is authenticated by a hosting server of the web application.
18. The non-transitory machine-readable medium of claim 15 , wherein the authentication credentials are retrieved from the web application using a mobile operating system application programming interface (API).
19. The non-transitory machine-readable medium of claim 15 , wherein the authenticating the user for the session comprises:
validating the authentication credentials with values in a hosting database; and
transmitting the authentication session token to the browser object for storage.
20. The non-transitory machine-readable medium of claim 15 , wherein the authentication session token is associated with the mobile application.