Electronic form automation

1 . A system comprising:

a non-transitory memory storing instructions; and

one or more hardware processors coupled to the non-transitory memory and configured to read the instructions from the non-transitory memory to cause the system to perform operations comprising:

maintaining a plurality of data structures, including an entities table that maps user identifiers to respective ones of a plurality of entities, and an entity attribute table that stores information for respective ones of the plurality of entities;

receiving, from a merchant associated with a merchant website, credentials that authenticate the merchant;

prompting the merchant to enter sample values for a set of data fields included in a particular form associated with the merchant for which field element identifier data is lacking;

mapping the field element identifier data corresponding to the set of data fields based on the sample values;

receiving an indication that a user, different from the merchant, has initiated a transaction at the merchant website;

performing a verification process based on a user identifier obtained from the user;

accessing the entities table using the user identifier to retrieve an entity identifier associated with the user identifier;

determining the mapped field element identifier data associated with the merchant website, wherein the mapped field element identifier data identifies the set of data input fields;

using the entity identifier, retrieving, from the entity attribute table, a plurality of attribute values that correspond to the entity identifier, wherein at least a subset of the plurality of attribute values was obtained from the user during a previous transaction of the user;

generating, using the retrieved plurality of attribute values and the mapped field element identifier data, instructions to populate the set of data input fields with the retrieved plurality of attribute values; and

transmitting, to a remote computing device, the instructions or execution to facilitate the transaction.

2 . The system of claim 1 , wherein retrieving the plurality of attribute values that correspond to the entity identifier further comprises:

selecting, for each of the mapped field element identifier data, an attribute identifier from the entity attribute table; and

utilizing each selected attribute identifier to access a corresponding attribute value of the plurality of attribute values stored in the entity attribute table on behalf of the user.

3 . The system of claim 1 , wherein the user identifier is an email address of the user.

4 . The system of claim 1 , wherein the retrieved plurality of attribute values corresponds to one or more types of the following types of data: a name of the user, a payment instrument information of the user, an address of the user, or a phone number of the user.

5 . The system of claim 1 , wherein prior to determining the entity identifier associated with the user identifier, the operations further comprise:

receiving, from the remote computing device, a global unique identifier (GUID) from which the entity identifier is determined.

6 . The system of claim 1 , wherein subsequent to receiving the indication that the user has initiated the transaction at the merchant website, the operations further comprise:

causing a separate interface to be displayed to the user, wherein the separate interface prompts the user to input the user identifier.

7 . The system of claim 1 , wherein the field element identifier data corresponds to a sequence of checkout web pages associated with the merchant website.

8 . A method comprising:

maintaining a plurality of data structures, including a first data structure that maps user identifiers to respective ones of a plurality of entities, and a second data structure that stores information for respective ones of the plurality of entities;

receiving, from a merchant, credentials that authenticate the merchant;

prompting the merchant to enter a set of sample values corresponding to a respective set of field elements associated with a checkout process for a website of the merchant, the checkout process lacking information about the set of field elements;

pairing, based on the set of sample values, the set of field elements with field element identifier data for the checkout process;

receiving a request initiated by a user that is different from the merchant, the request associated with the checkout process for the website of the merchant;

verifying a user credential obtained from the user;

determining, using the first data structure, an entity identifier based on the user credential;

determining ones of the field element identifier data included within one or more user interfaces associated with the checkout process, wherein the field element identifier data identifies, based on the pairing, a set of text input fields corresponding to transaction information for the checkout process;

retrieving, from the second data structure using the entity identifier, a plurality of attribute values that correspond to the entity identifier;

generating, using at least the retrieved plurality of attribute values and the field element identifier data, instructions to populate the one or more text input fields within the one or more user interfaces with the retrieved plurality of attribute values; and

in response to the request, transmitting, to a remote computing device, the instructions for execution to facilitate the checkout process.

9 . The method of claim 8 , wherein the instructions are executed on the remote computing device using a client application, and wherein the plurality of attribute values corresponding to the entity identifier are updatable using the client application.

10 . The method of claim 8 , wherein the user credential is an email address of the user.

11 . The method of claim 8 , wherein the retrieved plurality of attribute values corresponds to one or more types of the following types of data: a name of the user, a payment instrument information of the user, an address of the user, or a phone number of the user.

12 . The method of claim 8 , further comprising transmitting an error message in response to the user credential not being verified.

13 . The method of claim 8 , wherein retrieving the plurality of attribute values that correspond to the entity identifier further comprises:

identifying, for each of the determined field element identifier data, an attribute identifier within the second data structure; and

accessing, within the second data structure, each of the plurality of attribute values using the attribute identifier selected for each of the determined field element identifier data.

14 . The method of claim 13 , wherein the plurality of attribute values is mapped to the entity identifier associated with the user within the second data structure.

15 . A non-transitory machine readable medium having stored thereon machine readable instructions executable to cause a machine to perform operations comprising:

maintaining a plurality of data structures, including a first data structure that maps user identifiers to respective ones of a plurality of entities, and a second data structure that stores information for respective ones of the plurality of entities;

receiving, from a merchant, credentials that authenticate and associate the merchant with a merchant website;

prompting the merchant to enter a set of sample values corresponding to a respective set of field elements associated with a transaction process for the merchant website, wherein information about the transaction process is lacking;

correlating, based on the set of sample values, the set of field elements with a set of data input fields;

receiving a request associated with a purchase transaction initiated at the merchant website;

verifying a user identifier obtained from a user that is different from the merchant;

using the first data structure to identify an entity identifier associated with the user identifier;

determining, based on the correlating, field element identifier data associated with a sequence of one or more electronic forms displayed on one or more user interfaces associated with the merchant website, wherein the field element identifier data identifies the set of data input fields corresponding to information on the one or more electronic forms;

retrieving, from the second data structure, a plurality of attribute values that correspond to the entity identifier, wherein at least a subset of the plurality of attribute values was obtained from the user during a previous transaction of the user;

generating, using the retrieved plurality of attribute values and the field element identifier data, instructions for causing a sequential combination of steps that include populating the set of data input fields with the retrieved plurality of attribute values; and

transmitting, to a remote computing device, the instructions for execution to facilitate the purchase transaction in response to the request.

16 . The non-transitory machine readable medium of claim 15 , wherein the user identifier is an email address, a phone number, or a username associated with the user.

17 . The non-transitory machine readable medium of claim 15 , wherein subsequent to receiving the request associated with the purchase transaction, the operations further comprise:

causing a pop-up interface to be displayed to the user, wherein the pop-up interface prompts the user to input the user identifier.

18 . The non-transitory machine readable medium of claim 15 , wherein the sequential combination of steps corresponds to a sequence for a checkout process on the merchant website.

19 . The non-transitory machine readable medium of claim 15 , wherein the retrieved plurality of attribute values corresponds to one or more types of the following types of data: a name of the user, a payment instrument information of the user, a shipping address of the user, a billing address of the user, or a phone number of the user.

20 . The non-transitory machine readable medium of claim 15 , wherein prior to determining the entity identifier associated with the user identifier, the operations further comprise:

receiving a global unique identifier (GUID) from which the entity identifier is determined.