Data Processing System and Method for Managing Electronic Split Transactions Using User Profiles

A method for managing a split transaction between two or more users over a network, comprising:

• receiving a request from a first user device to initiate a split transaction session between the first user, a second user, and a third user via digital transaction applications installed on user devices associated with the first user, the second user, and the third user, wherein:
• the first user is associated with a first user device, wherein the first user device has contact information of the second user, the first user device does not have contact information of the third user;
• the second user is associated with a second user device, and
• the third user is associated with a third user device;
• initiating the split transaction session from a digital transaction application installed on the first user device between the first user, the second user, and the third user;
• receiving an Application Programming Interface (API) request from the first user device to retrieve a third user profile of the third user, wherein:
• receiving the API request is a response to the first user device sending the API request to a processor due to the first user device not having the contact information of the third user;
• and
• the third user profile comprises one or more of a name, a phone number, an email address, a Universally Unique Identification (UUID), and a transaction limit associated with the third user;
• determining whether the second user device has the contact information of the third user;
• in response to determining that the second user device has the contact information of the third user:
• sending a second request to the second user device to retrieve the third user profile, wherein in response to receiving the second request from a processor to retrieve the third user profile, the second user device retrieves the third user profile from a profile directory database and sends the third user profile to the processor;
• sending the third user to the first user device;
• in response to determining that the contact information of the third user is missing from the first user device and the second user device:
• determining whether any user devices associated with any other users from a contact list stored in the first user device who are not included in the split transaction session include the contact information of the third user by:
• for each particular contact information of a user who is not included in the split transaction session in the contact list:
• identifying a user device associated with the particular contact information;
• and
• sending a second API request to the identified user device,
• wherein the second API request indicates whether the identified user device stores the contact information of the third user;
• receiving from one or more user devices associated with any of the other users from the contact list who is not included in the split transaction session the third user profile, wherein receiving the third user profile is in response to the one or more user devices retrieving the third user profile from the profile directory database;
• in response to determining that the contact information of the second user is found in the first user device:
• querying the profile directory database to find a second user profile of the second user;
• fetching the second user profile from the profile directory database;
• and
• sending the second user profile to the first user device;
• adding a first user profile of the first user, the second user profile, and the third user profile in the digital transaction application installed on the first user device;
• and
• conducting the split transaction session between the first user, the second user, and the third user.

A computer program comprising executable instructions stored in a non-transitory computer-readable medium that when executed by a processor causes the processor to:

• receive a request from a first user device to initiate a split transaction session between the first user, a second user, and a third user via digital transaction applications installed on user devices associated with the first user, the second user, and the third user, wherein:
• the first user is associated with the first user device, wherein the first user device has contact information of the second user, the first user device does not have contact information of the third user;
• the second user is associated with a second user device, and
• initiate the split transaction session from a digital transaction application installed on the first user device between the first user, the second user, and the third user;
• receive an Application Programming Interface (API) request from the first user device to retrieve a third user profile of the third user, wherein:
• receiving the API request is a response to the first user device sending the API request to the processor due to the first user device not having the contact information of the third user;
• and
• the third user profile comprises one or more of a name, a phone number, an email address, a Universally Unique Identification (UUID), and a transaction limit associated with the third user;
• determine whether the second user device has the contact information of the third user;
• in response to determining that the second user device has the contact information of the third user:
• send a second request to the second user device to retrieve the third user profile, wherein in response to receiving the second request from the processor to retrieve the third user profile, the second user device retrieves the third user profile of-the-third-user from a profile directory database and sends the third user profile of-the-third-user to the processor;
• send the third user profile to the first user device;
• in response to determining that the contact information of the third user is missing from the first user device and the second user device:
• determine whether any user devices associated with any other users from a contact list stored in the first user device who are not included in the split transaction session include the contact information of the third user by:
• for each particular contact information of a user who is not included in the split transaction session in the contact list:
• identify a user device associated with the particular contact information;
• and
• send a second API request to the identified user device, wherein the second API request indicates whether the identified
• user device stores the contact information of the third user;
• receive from one or more user devices associated with any of the other users from the contact list who is not included in the split transaction session the third user profile, wherein receiving the third user profile is in response to the one or more user devices retrieving the third user profile from the profile directory database;
• in response to determining that the contact information of the second user is found in the first user device:
• query the profile directory database to find a second user profile of the second user;
• fetch the second user profile from the profile directory database;
• and
• send the second user profile to the first user device;
• add a first user profile of the first user, the second user profile, and the third user profile in the digital transaction application installed on the first user device;
• and
• conduct the split transaction session between the first user, the second user, and the third user.