EP-4740162-A2 - PLATFORM-AGNOSTIC UNIVERSAL TRANSACTION PROFILES

Abstract

Methods and systems are presented for providing a framework for facilitating electronic transactions by dynamically managing and sharing user data with multiple online platforms. As a user accesses one or more online platforms, a connect system that is integrated with the online platforms interacts with the user and obtain, from the user, user data that is usable for completing transactions between the user and the online platforms. The user data is stored in a user profile associated with the user and linked to an identifier of the user. When the user subsequently accesses an online platform, the connect system authenticates the user based on an identifier associated with the user, and share at least a portion of the user data stored in the user profile with the online platform to facilitate a transaction between the user and the online platform.

Inventors

• BASU, ROHIT
• KAKANI, ABHISHEK
• DUNNE, MEGGAN MARIE
• THROENER, ANDREW
• GEORGE, TRINI
• LAROSA, MICHAEL

Assignees

• PayPal, Inc.

Dates

Publication Date

20260513

Application Date

20240730

Claims (20)

1. 1. A system, comprising: a non-transitory memory; and one or more hardware processors coupled with the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: receiving, from a merchant server, an indication of a user accessing a first merchant website associated with a first merchant and displayed on a device; initiating an authentication process for authenticating the user via a first user interface associated with the first merchant website based on a user identifier obtained from the user; accessing, from a profile database, a user profile corresponding to the user based on the user identifier; and in response to authenticating the user, transmitting first data from the user profile to the device, wherein the first data was obtained during a previous user interaction of the user with a second user interface associated with an entity different from the first merchant, and wherein the first data is usable for a transaction between the user and the first merchant website.
2. 2. The system of claim 1 , wherein the transmitting enables a module executed on the device to populate a set of text input fields corresponding to transaction information on the first merchant website using the first data from the user profile.
3. 3. The system of claim 1, wherein the operations further comprise: generating a payment token using the first data associated with the user profile; and transmitting the payment token to the device.
4. 4. The system of claim 3, wherein the operations further comprise: in response to receiving the payment token from the merchant server, processing a payment associated with the transaction based on the payment token.
5. 5. The system of claim 1, wherein the first data was obtained during a second transaction conducted between the user and a second merchant website associated with a second merchant.
6. 6. The system of claim 1 , wherein the first data is associated with a user account of the user with a second merchant website associated with a second merchant.
7. 7. The system of claim 1, wherein the data is associated with a user account of the user with a payment service provider.
8. 8. A method, comprising: receiving, from a server, an indication of a user accessing a first online platform associated with a first entity and displayed on a device; determining that a user profile associated with the user exists in a profile database based on an identifier obtained from the user via a first user interface associated with the first online platform; generating a communication package based on a portion of data associated with the user profile, wherein the portion of the data associated with the user profile was obtained during a previous user interaction of the user with a second user interface associated with a second entity different from the first entity, and wherein the portion of the data is usable for a transaction between the user and the first entity; and in response to authenticating the user, transmitting the communication package to the device.
9. 9. The method of claim 8, wherein the data associated with the user profile was obtained during a plurality of user interactions of the user with a plurality of different entities, and wherein the method further comprises: selecting, from the data of the user profile, the portion of the data for transmitting to the device based on at least one of an identity of the first merchant, a device type of the device, a transaction type, or a location of the user.
10. 10. The method of claim 9, wherein the first portion of the data is selected using a machine learning model configured to predict a preferred portion of data for a given transaction. -An-
11. 11 . The method of claim 8, wherein the communication package is generated prior to authenticating the user, wherein the method further comprises: suspending a transmission of the communication package to the device while the user is being authenticated.
12. 12. The method of claim 8, wherein the indication is associated with a token request, and wherein the operations further comprise: generating a session token for an online session between the user and the first online platform; and transmitting the session token to the device.
13. 13. The method of claim 12, wherein prior to the generating, the method further comprises: encoding the portion of the data associated with the user profile into the session token.
14. 14. The method of claim 8, further comprising: prompting, via the first user interface, the user for the identifier; and querying the profile database based on the identifier.
15. 15. A non-transitory machine-readable medium having stored thereon machine- readable instructions executable to cause a machine to perform operations comprising: in response to detecting a user interaction between a user and a first online platform, prompting, via a first user interface associated with the first online platform, the user for a user identifier; querying a profile database based on the user identifier; in response to determining that a user profile associated with the user exists in the profile database based on the querying, initiating an authentication process for authenticating the user via the first user interface; prior to determining that the user is authenticated based on the authentication process, generating a communication package for transmitting to the device based on a portion of data associated with the user profile, wherein the portion of the data is usable for a transaction between the user and the first online platform; and in response to determining that the user is authenticated based on the authentication process, transmitting the communication package to the device.
16. 16. The non-transitory machine-readable medium of claim 15, wherein the portion of the data associated with the user profile was obtained during a previous user interaction of the user with a second user interface associated with a second online platform.
17. 17. The non-transitory machine-readable medium of claim 15, wherein the operations further comprise: generating a one-time passcode for the authentication process; identifying a user device based on the user identifier; and transmitting the one-time passcode to the user device as a part of the authentication process.
18. 18. The non-transitory machine-readable medium of claim 17, wherein the operations further comprise: prompting, via the first user interface, the user for an authentication code; and authenticating the user based on matching the one-time passcode with the authentication code received via the first user interface.
19. 19. The non-transitory machine-readable medium of claim 15, wherein the operations further comprise: generating a payment token using the portion of the data associated with the user profile; and transmitting the payment token to the device.
20. 20. The non-transitory machine-readable medium of claim 19, wherein the operations further comprise: in response to receiving the payment token from a server, processing a payment associated with the transaction between the user and the first online platform based on the payment token.

Description

PLATFORM-AGNOSTIC UNIVERSAL TRANSACTION PROFILES BACKGROUND [0001] The present specification generally relates to management of user identities and data, and more specifically, to dynamically sharing user data with different platforms based on user authentication according to various embodiments of the disclosure. Related Art [0002] Many transaction services (e.g., purchasing of items, bill payments, registration services, etc.) are now available online, allowing users to conduct these transactions anywhere via a computing device. However, due to the different transaction services being offered by different separate entities (e.g., different merchants, different utility companies, different government agencies, etc.), users are required to conduct the transactions via different online platforms or portals (e.g., different websites, etc.). As a result, users may be required to provide the same information (e.g., user data, funding instrument data, shipping data, etc.) to the online platforms each time the users desire to conduct an online transaction. Providing information via a computing device can be cumbersome, especially when the data input mechanism is far from ideal (e.g., a small touch screen from a mobile device such as a mobile phone or a smart watch, etc.). Furthermore, having to repetitively provide potentially sensitive information (e.g., funding instrument information, personal identifiable information, etc.) via the computer device and over a network can be prone to data security problems, such as identity theft, unauthorized usages of funding instruments, etc. [0003] In the past, some of the online platforms have attempted to mitigate such problems by storing user data on their respective servers (e.g., data vaults). For example, a user can register an account with each of the online platforms, and may access the user data stored on the respective servers after successfully performing an authentication process (e.g., providing a correct user name and password pair, etc.). However, such an arrangement is also problematic, as multiple copies of the user data (which can be as many as the number of online platforms that the user interacts with) are now stored on different servers on the Internet, which can also lead to data security problems when any one of these servers are attacked. When the user data is updated, the user will also have to manually update the copies stored on each of the online platforms. Thus, there is a need for providing a framework for securely managing user identities and data across different online platforms. BRIEF DESCRIPTION OF THE FIGURES [0004] FIG. 1 is a block diagram illustrating an electronic transaction system according to an embodiment of the present disclosure; [0005] FIG. 2 is a block diagram illustrating a computing environment in which a connect system may operate according to an embodiment of the present disclosure; [0006] FIG. 3 illustrates an example user interface flow for generating a user profile for a user according to an embodiment of the present disclosure; [0007] FIG. 4 illustrates an example user interface flow for sharing user data from a user profile of a user according to an embodiment of the present disclosure; [0008] FIG. 5 illustrates another example user interface flow for generating a user profile for a user according to an embodiment of the present disclosure; [0009] FIG. 6 is a flowchart showing a process of generating a user profile based on user data obtained from a user according to an embodiment of the present disclosure; [00010] FIG. 7 is a flowchart showing a process of generating a user profile based on user data obtained from a merchant server according to an embodiment of the present disclosure; [00011] FIG. 8 is a flowchart showing a process of generating a user profile based on user data obtained from a payment processing server according to an embodiment of the present disclosure; [00012] FIG. 9 is a flowchart showing a process of sharing user data from a user profile associated with a user with an online platform according to an embodiment of the present disclosure; and [00013] FIG. 10 is a block diagram of a system for implementing a device according to an embodiment of the present disclosure. [00014] Embodiments of the present disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures, wherein showings therein are for purposes of illustrating embodiments of the present disclosure and not for purposes of limiting the same. DET AILED DESCRIPTION [00015] The present disclosure describes methods and systems for facilitating electronic transactions across multiple online platforms by dynamically managing and sharing user data. As discussed above, conducting electronic transactions with various online platforms can lead to many problems, including t