Granted Patent B1

US 12,339,999 · App. 17/316,369 · Granted Jun 24, 2025

Inventors: Chintan Mehta (San Ramon, CA); Jason Strle (San Francisco, CA)

Assignee: Wells Fargo Bank, N.A.

G06F21/6263G06N5/02G06Q20/24

Abstract

Claims (83)

1. A system comprising:

a data management circuit configured to web-scrape websites of a plurality of experience providers and transmit API requests requesting data corpuses of a plurality of users of the plurality of experience providers;

a user data repository containing data from the web-scrape or the API requests relating to the plurality of users of the plurality of experience providers;

a rules engine configured to apply rules according to a plurality of data sharing preferences of a user;

a first application programming interface (API) configured to:

provide, via a graphical user interface on a user device, a plurality of selectable interaction points associated with configuring the plurality of data sharing preferences;

receive, from the user device associated with the user, user inputs that identify at least one experience provider and at least one data sharing preference of the plurality of data sharing preferences of the user, wherein the user inputs are received in response to selections of the plurality of selectable interaction points; and

configure the rules engine with rules based on the user inputs, wherein the rules comprise a set of logic, wherein the set of logic, based on the user inputs, executes at least one of a modulation or truncation of a first data subset of the data of the user;

a second API configured to:

receive, from a computing system associated with the experience provider, a request for a second data subset of the data of the user, wherein the second data subset of the data comprises at least the first data subset of the data;

transmit the request to the rules engine, wherein the rules engine modulates or truncates the second data subset based on retrieving applicable data of the user from the user data repository, wherein the applicable data of the user is based on the request for the second data subset of the data of the user and the at least one data sharing preference of the user;

receive, from the rules engine, the applicable data of the user; and

provide, to the computing system associated with the experience provider, the applicable data of the user; and

a payments engine configured to:

determine, in real-time after the applicable data of the user is provided using the second API, an amount of funds received from the experience provider and due to the user based on the second API providing the applicable data of the user to the computing system associated with the experience provider; and

credit, paid from the experience provider, an account associated with the user in the amount of the funds due to the user;

wherein the first API facilitates communication between the user device and the system, and wherein the second API facilitates communication between the computing system associated with the experience provider and the system.

2. The system of claim 1 , wherein the second API is further configured to transmit a confirmation message to a third API, the confirmation message confirming that the experience provider received the applicable data of the user.

3. The system of claim 2 , wherein the third API is configured to:

receive, from the second API, the confirmation message;

query the payments engine for the amount of funds due to the user;

receive a currency value for the amount of funds due to the user from the payments engine;

transmit a payment request to the experience provider, the payment request being for an amount equaling the received currency value; and

receive a payment from the experience provider, the payment received in response to the transmitted payment request.

4. The system of claim 1 , wherein providing the applicable data of the user is based on a confirmation presented to the user, the confirmation transmitted by the second API and displayed by the user device.

5. The system of claim 4 , wherein the confirmation is a two-factor authentication (2FA) prompt, the 2FA prompt presented to the user in real-time.

6. The system of claim 1 , wherein the user data repository is further populated with data of the user via voluntary submissions of experience providers.

7. The system of claim 1 , wherein the at least one of the plurality of data sharing preferences of the user includes a selection of advertising categories that the user is willing to view while accessing content associated with the experience provider.

8. The system of claim 7 , wherein the second API is further configured to:

receive an offer from the experience provider associated with advertising revenue with the user for an unselected advertising category;

present, to the user via the user device, the offer associated with advertising revenue with the experience provider;

receive a decision of the user regarding the offer associated with advertising revenue; and

provide the decision of the user to the experience provider.

9. The system of claim 8 , wherein a third API is further configured to:

receive, from the experience provider, a tabulation of funds due to the user according to advertising content displayed by the experience provider correlating the offer associated with advertising revenue with the user;

verify the received tabulation of funds due to the user with the payments engine; and

receive funds equaling the tabulation of funds due to the user from an account associated with the experience provider.

10. The system of claim 9 , wherein the tabulation of funds due is received in real-time for each advertisement displayed by the experience provider.

11. The system of claim 9 , wherein the tabulation of funds due is received at predetermined intervals.

12. A method comprising:

providing, by a first application programming interface (API) of a platform computing system via a graphical user interface on a user device, a plurality of selectable interaction points associated with configuring a plurality of data sharing preferences;

receiving, by the first API and from the user device associated with a user, user inputs that identify at least one experience provider and at least one data sharing preference of the plurality of data sharing preferences of the user, wherein the user inputs are received in response to selections of the plurality of selectable interaction points;

configuring, by the first API, a rules engine of the platform computing system with rules based on the user inputs, wherein the rules engine is configured to apply rules associated with the plurality of data sharing preferences of the user, and wherein the rules comprise a set of logic, wherein the set of logic, based on the user inputs, executes at least one of a modulation or truncation of a first data subset of the data of the user;

receiving, by a second API of the platform computing system and from a computing system associated with the experience provider, a request for a second data subset of the data of the user, wherein the second data subset of the data comprises at least the first data subset of the data;

transmitting, by the second API and to the rules engine, the request for data of the user, wherein the rules engine modulates or truncates the second data subset based on retrieving applicable data of the user from a user data repository, wherein the applicable data of the user is based on the request for the second data subset of the data of the user and the at least one data sharing preference of the user, and wherein the user data repository contains data from web-scraping websites of a plurality of experience providers or from transmitted API requests requesting data corpuses of a plurality of users from the plurality of experience providers;

receiving, by the second API and from the rules engine, the applicable data of the user;

providing, by the second API and to the computing system associated with the experience provider, the applicable data of the user;

determining, in real-time after the applicable data of the user is provided using the second API by a payments engine of the platform computing system, an amount of funds received from the experience provider and due to the user based on the second API providing the applicable data of the user to the computing system associated with the experience provider; and

crediting, by the payments engine paid from the experience provider, an account associated with the user in the amount of the funds due to the user;

wherein the first API facilitates communication between the user device and the platform computing system, and wherein the second API facilitates communication between the computing system associated with the experience provider and the platform computing system.

13. The method of claim 12 , further comprising transmitting, by the second API to a third API of the platform computing system, a confirmation message confirming that the experience provider received the applicable data of the user.

14. The method of claim 13 , further comprising:

receiving, by the third API and from the second API, the confirmation message;

querying, by the third API, the payments engine for the amount of funds due to the user;

receiving, by the third API, a currency value for the amount of funds due to the user from the payments engine;

transmitting, by the third API, a payment request to the experience provider, the payment request being for an amount equaling the received currency value; and

receiving, by the third API, a payment from the experience provider, the payment received in response to the transmitted payment request.

15. The method of claim 12 , wherein providing the applicable data of the user is based on a confirmation presented to the user, the confirmation transmitted by the second API and displayed by the user device.

16. The method of claim 15 , wherein the confirmation is a two-factor authentication (2FA) prompt, the 2FA prompt presented to the user in real-time.

17. The method of claim 12 , wherein the user data repository is further populated with data of the user via voluntary submissions of experience providers.

18. The method of claim 12 , wherein the at least one of the plurality of data sharing preferences of the user includes a selection of advertising categories that the user is willing to view while accessing content associated with the experience provider.

19. The method of claim 18 , further comprising:

receiving, by the second API, an offer from the experience provider associated with advertising revenue with the user for an unselected advertising category;

presenting, by the second API, to the user and via the user device, the offer associated with advertising revenue with the experience provider;

receiving, by the second API, a decision of the user regarding the offer associated with advertising revenue; and

providing, by the second API, the decision of the user to the experience provider.

20. The method of claim 19 , further comprising:

receiving, by a third API of the platform computing system and from the experience provider, a tabulation of funds due to the user according to advertising content displayed by the experience provider and correlates to the offer associated with advertising revenue with the user;

verifying, by the third API, the received tabulation of funds due to the user with the payments engine; and

receiving, by the third API, funds equaling the tabulation of funds due to the user from an account associated with the experience provider.

21. The method of claim 20 , wherein the tabulation of funds due is received in real-time for each advertisement displayed by the experience provider.

22. The method of claim 20 , wherein the tabulation of funds due is received at predetermined intervals.

23. A non-transitory computer readable medium containing program instructions, which when executed by a processor of a computing system, cause the computing system to:

provide, by a first application programming interface (API) via a graphical user interface on a user device, a plurality of selectable interaction points associated with configuring a plurality of data sharing preferences;

receive, by the first API and from the user device associated with a user, user inputs that identify at least one experience provider and at least one data sharing preference of the plurality of data sharing preferences of the user, wherein the user inputs are received in response to selections of the plurality of selectable interaction points;

configure, by the first API, a rules engine with rules based on the user inputs, wherein the rules engine is configured to apply rules associated with the plurality of data sharing preferences of the user, and wherein the rules comprise a set of logic, wherein the set of logic, based on the user inputs, executes at least one of a modulation or truncation of a first data subset of the data of the user;

receive, by a second API and from a computing system associated with the experience provider, a request for a second data subset of the data of the user, wherein the second data subset of the data comprises at least the first data subset of the data;

transmit, by the second API and to the rules engine, the request for data of the user, wherein the rules engine modulates or truncates the second data subset based on retrieving applicable data of the user from a user data repository, wherein the applicable data of the user is based on the request for the second data subset of the data of the user and the at least one data sharing preference of the user, and wherein the user data repository contains data from web-scraping websites of a plurality of experience providers or from transmitted API requests requesting data corpuses of a plurality of users from the plurality of experience providers;

receive, by the second API and from the rules engine, the applicable data of the user;

provide, by the second API and to the computing system associated with the experience provider, the applicable data of the user;

determine, in real-time after the applicable data of the user is provided using the second API by a payments engine, an amount of funds received from the experience provider and due to the user based on the second API providing the applicable data of the user to the computing system associated with the experience provider; and

credit, by the payments engine paid from the experience provider, an account associated with the user in the amount of the funds due to the user;

wherein the first API facilitates communication between the user device and the processor of the computing system, and wherein the second API facilitates communication between the computing system associated with the experience provider and the processor of the computing system.

Assignments (3)

References Cited (65)

Cited By (1)

US 12,712,855