Location-based determinations

1. A method comprising:

receiving, by one or more processors, payment information for each of a plurality of users from a plurality of client-side applications associated with the plurality of users;

generating, by the one or more processors, a token for each of the plurality of users from the payment information sent by the plurality of client-side applications, each token configured to be used to complete a transaction through the one or more processors;

comparing, by the one or more processors, a first set of tokens generated from payment information of a first subset of the plurality of users for a first entity with a second set of tokens generated from payment information of a second subset of the plurality of users for a second entity; and

responsive to identifying at least one matching token between the first set of tokens and the second set of tokens, generating, by the one or more processors, a record comprising a list of matching tokens that are included in each of the first set of tokens and the second set of tokens and represent a third subset of the plurality of users that are common to the first entity and second entity.

2. The method of claim 1 , wherein generating the token for each of the plurality of users from the payment information sent by the plurality of client-side applications comprises generating, by the one or more processors, the token using a Hypertext Transfer Protocol (HTTP)-based tokenization application programming interface.

3. The method of claim 1 , comprising:

receiving, by the one or more processors, a first token from a server-side application; and

settling, by the one or more processors, a first transaction based on the first token.

4. The method of claim 1 , wherein a first client-side application of the plurality of client-side applications transmits a first token to a server-side application to complete a transaction comprising registering payment information of the first token with a first merchant website for subsequent use in making a payment for a merchant item.

5. The method of claim 1 , wherein a first client-side application of the plurality of client-side applications executes within a browser executing on a computing device.

6. The method of claim 1 , further comprising:

determining, by the one or more processors, a geographic location of a first user's electronic device using first data, the first user's electronic device executing a first client-side application to complete a first transaction;

performing, by the one or more processors via an Application Programming Interface (API), a location-dependent determination based on the geographic location; and

completing, by the one or more processors via the API, the first transaction using the location-dependent determination based on a first token generated by the one or more processors from payment information of the first user.

7. The method of claim 1 , further comprising:

enforcing, by the one or more processors, a rule that prevents a previously used token from being used for another transaction.

8. The method of claim 1 , comprising:

authorizing, by the one or more processors, a first transaction,

wherein generating a first token for a first user of the plurality of users comprises generating, by the one or more processors, the first token responsive to authorizing the first transaction.

9. The method of claim 8 , wherein authorizing the first transaction comprises:

transmitting, by the one or more processors, data of the first transaction to a first remote computing device; and

receiving, by the one or more processors, authorization for the first transaction from the first remote computing device or a second remote computing device.

10. The method of claim 8 , wherein authorizing the first transaction comprises:

executing, by the one or more processors, a rule using data of a transaction card of the payment information as input; and

determining, by the one or more processors, the first transaction is authorized based on the executing the rule.

11. A system comprising:

one or more processors coupled with a non-transitory memory and configured to:

receive payment information for each of a plurality of users from a plurality of client-side applications associated with the plurality of users;

generate a token for each of the plurality of users from the payment information sent by the plurality of client-side applications, each token configured to be used to complete a transaction through the one or more processors;

compare a first set of tokens generated from payment information of a first subset of the plurality of users for a first entity with a second set of tokens generated from payment information of a second subset of the plurality of users for a second entity; and

responsive to identifying at least one matching token between the first set of tokens and the second set of tokens, generate a record comprising a list of matching tokens that are included in each of the first set of tokens and the second set of tokens and represent a third subset of the plurality of users that are common to the first entity and second entity.

12. The system of claim 11 , wherein the one or more processors are configured to generate the token for each of the plurality of users from the payment information sent by the plurality of client-side applications by generating the token using a Hypertext Transfer Protocol (HTTP)-based tokenization application programming interface.

13. The system of claim 11 , wherein the one or more processors are further configured to:

receive a first token from a server-side application; and

settle a first transaction based on the first token.

14. The system of claim 11 , wherein a first client-side application of the plurality of client-side applications transmits a first token to a server-side application to complete a first transaction comprising purchasing an item from a first merchant website associated with the first client-side application and the server-side application.

15. The system of claim 11 , wherein a first client-side application of the plurality of client-side applications transmits a first token to a server-side application to complete a first transaction comprising registering payment information of the first token with a first merchant website for subsequent use in making a payment for a merchant item.

16. The system of claim 11 , wherein the one or more processors are further configured to:

authorize a first transaction,

wherein the one or more processors are further configured to generate a first token for a first user of the plurality of users by generating the first token responsive to authorizing the first transaction.

17. A non-transitory machine-readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to:

receive payment information for each of a plurality of users from a plurality of client-side applications associated with the plurality of users;

generate a token for each of the plurality of users from the payment information sent by the plurality of client-side applications, each token configured to be used to complete a transaction through the one or more processors;

compare a first set of tokens generated from payment information of a first subset of the plurality of users for a first entity with a second set of tokens generated from payment information of a second subset of the plurality of users for a second entity; and

responsive to identifying at least one matching token between the first set of tokens and the second set of tokens, generate a record comprising a list of matching tokens that are included in each of the first set of tokens and the second set of tokens and represent a third subset of the plurality of users that are common to the first entity and second entity.

18. The non-transitory machine-readable medium of claim 17 , wherein executing the instructions further causes the one or more processors to:

receive a first token from a first server-side application; and

settle a first transaction based on the first token.

19. The non-transitory machine-readable medium of claim 17 , wherein a first client-side application of the plurality of client-side applications transmits a first token to a server-side application to complete a first transaction comprising registering payment information of the first token with a first merchant website for subsequent use in making a payment for a merchant item.

20. The non-transitory machine-readable medium of claim 17 , wherein executing the instructions further causes the one or more processors to:

authorize a first transaction,

wherein executing the instructions causes the one or more processors to generate a first token for a first user of the plurality of users by generating the first token responsive to authorizing the first transaction.