Systems and methods for creating dynamic sessions for mobile application integration

Patent metadata

Field	Value
Publication number	US-11276049-B2
Application number	US-201916731535-A
Country	US
Kind code	B2
Filing date	Dec 31, 2019
Priority date	Dec 31, 2019
Publication date	Mar 15, 2022
Grant date	Mar 15, 2022

Abstract

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.

First claim

What is claimed is:

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, by a service provider server, a payment request for a payment transaction from a browser object associated with a merchant mobile application on a mobile device;
in response to receiving the payment request, sending, by the service provider server, a payment application detection request to the merchant mobile application on the mobile device, wherein the payment application detection request comprises programming code that causes the mobile device, when executing the programming code, to retrieve a token associated with a service provider mobile application different from the merchant mobile application without redirecting a user away from a user interface of the merchant mobile application, wherein the service provider mobile application is associated with the service provider server;
receiving, by the service provider server, a detection response comprising the token from the mobile device;
determining, by the service provider server, whether to authenticate the user with the payment processing platform based on the token included in the detection response; and
in response to authenticating the user based on the token, causing, by the service provider server, a customized user interface to be displayed on the browser object associated with the merchant mobile application.

2. The system in claim 1 , wherein the operations further comprise:
determining that the token comprises credential data associated with a user account with the payment processing platform.

3. The system of claim 1 , wherein the operations further comprise:
receiving an authentication request from the mobile device;
creating an authentication cookie indicating that the browser object is authenticated with the payment processing platform;
transmitting the authentication cookie to the mobile device; and
causing the browser object to store the authentication cookie in a data store on the mobile device, wherein the data store is associated with the mobile application.

4. The system of claim 1 , wherein the operations further comprise:
subsequent to determining that that user is authenticated with the payment processing platform based on the token, receiving a payment completion request from the merchant mobile application on the mobile device; and
sending a payment completion response to the merchant mobile application on the mobile device based on the user being authenticated with the payment processing platform.

5. The system of claim 1 , wherein the programming code, when executed by the mobile device, causes the mobile device to further determine whether the service provider mobile application is present on the mobile device.

6. The system of claim 1 , wherein the operations further comprise generating the customized user interface based on information received in the payment request.

7. The system of claim 6 , wherein the customized user interface is generated further based on one or more user preferences associated with the user.

8. A mobile device 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 mobile device to perform operations comprising:
sending a payment request to a payment processing server from a browser object associated with a merchant mobile application on the mobile device;
receiving, from the payment processing server, a payment application detection request comprising programming code;
based on executing the programing code of the payment application detection request, retrieving a token associated with a service provider mobile application different from the merchant mobile application without redirecting a user away from a user interface of the merchant mobile application, wherein the service provider mobile application is associated with a payment processing platform;

determining whether the user is authenticated with the payment application processing platform based on the token;
in response to determining that the user is authenticated with the payment processing platform, sending detection results to the payment processing server, wherein the detection results indicate that the user is authenticated with the payment mobile application;
receiving a customized user interface from the payment processing server; and
displaying the customized user interface.

9. The mobile device of claim 8 , wherein the operations further comprise:
sending authentication credentials to the payment processing server;
receiving an authentication cookie indicating the browser object is authenticated with the payment processing server; and
storing the authentication cookie in a data store associated with the mobile application.

10. The mobile device of claim 9 , wherein the token comprises authentication credentials associated with a user account with the payment processing platform.

11. The mobile device of claim 8 , wherein the customized user interface comprises receiving an authentication cookie, and wherein the operations further comprise storing the authentication cookie in a data store associated with the merchant mobile application.

12. The mobile device of claim 11 , wherein the operations further comprise:
determining that the authentication cookie has expired;
retrieving authentication credentials from the service provider mobile application;
sending the authentication credentials to the payment processing server;
receiving an updated authentication cookie from the payment processing server; and
storing the updated authentication cookie in the data store.

13. The mobile device of claim 8 , wherein the operations further comprise:
receiving a user input via the browser object, wherein the payment request is based on the user input.

14. The mobile device of claim 8 , wherein the customized user interface is customized based on one or more user preferences associated with the user.

15. The mobile device of claim 8 , wherein the browser object comprises a webview.

16. A method comprising:
receiving, by one or more hardware processors, a payment request for a payment transaction from a browser window associated with a merchant mobile application on a user device;
in response to the payment request, sending, by the one or more hardware processors, a payment application detection request to the merchant mobile application on the user device, wherein the payment application detection request comprises programming code that causes the user device, when executing the programming code, to retrieve a token associated with a service provider mobile application different from the merchant mobile application without redirecting a user away from a user interface of the merchant mobile application, wherein the service provider mobile application is associated with a payment processing platform;
receiving, by the one or more hardware processors, a detection response comprising the token from the mobile device;
determining, by the one or more hardware processors, whether to authenticate the user with the the payment processing platform based on the token included in the detection response; and
in response to authenticating the user based on the token, causing, by the one or more hardware processors, a customized user interface to be displayed on the browser window assoc

Assignees

• Paypal Inc

Inventors

• Annamalai Prasanna
• Annam Harish
• Arumugam Arun
• Shaik Madar Areef Hussain

Classifications

• G06Q20/401

  Transaction verification · CPC title

• H04W12/068

  using credential vaults, e.g. password manager applications or one time password [OTP] applications · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• G06Q20/4014

  Identity check for transactions · CPC title

• G06Q20/385

  using an alias or single-use codes · CPC title