System and method for protecting customer identity from a service or product provider

Abstract

A system and method for customer identity protection from a service or product provider is disclosed. In one embodiment, the method may include receiving, by a trusted third party, a request from a customer for a verified vendor token for a good or service, generating, by the trusted third party, the verified vendor token including a unique identifier, mapping, by the trusted third party, the unique identifier to a customer identifier, receiving, by the trusted third party, the verified vendor token from the vendor, verifying, by the trusted third party, that the verified vendor token is valid, confirming, by the trusted third party, a payment relationship with the vendor, receiving, by the trusted third party, the verified vendor token and an invoice for the good or service from the vendor, and issuing, by the trusted third party, a payment for the good or service to the vendor.

Description

[Technical field]

[0001]

[0001] This application claims priority to and the benefit of U.S. Provisional Application No. 62 / 994,189, filed March 24, 2020, the disclosure of which is incorporated herein by reference in its entirety.

[0002]

[0002] The disclosures of U.S. Patent Application No. 16 / 598,734, U.S. Provisional Patent Application No. 62 / 856,491, U.S. Provisional Patent Application No. 62 / 874,240, and U.S. Provisional Patent Application No. 62 / 944,244 are also incorporated by reference in their entireties herein.

[0003] SUMMARY OF THE DISCLOSURE

[0003] Embodiments generally relate to systems and methods for customer identity protection from a service or product provider. [Background technology]

[0004]

[0004] Many service and product providers use billing processes to extract sensitive personal information from their customers. For example, it is common for providers to collect customer address information even if they are not shipping or provide a service that requires knowing the customer's address. This information may be used intentionally or unintentionally for tracking, monitoring, or monetization purposes, often without the customer's consent or knowledge.

[0005]

[0005] One example of such an association is the collection of addresses and social security numbers of wireless communication customers. To provide wireless service, carriers require proof of user identity and address, as well as financial accounts. Such information is stored by the carrier and associated with the SIM card. Thus, wherever a customer goes with his mobile phone, the SIM is constantly communicating with nearby cellular towers to authenticate and thereby provide the customer with a detailed location. Aggregation and correlation of such data can reveal personal activities, behavior, and interactions with other customers. Summary of the Invention [Problem to be solved by the invention]

[0006] A system and method for customer identity protection from a service or product provider is disclosed. In one embodiment, a method for providing customer identity protection may include (1) receiving, by a trusted third-party computer processor, a request from a customer for a verified vendor token for a good or service; (2) generating, by the trusted third-party computer processor, a verified vendor token including a unique identifier; (3) mapping, by the trusted third-party computer processor, the unique identifier to a customer identifier maintained by the trusted third party; (4) receiving, by the trusted third-party computer processor, a verified vendor token from the vendor that received the verified vendor token from the customer; (5) verifying, by the trusted third-party computer processor, that the verified vendor token is valid; (6) confirming, by the trusted third-party computer processor, a payment relationship with the vendor; (7) receiving, by the trusted third-party computer processor, the verified vendor token and an invoice for the good or service from the vendor; and (8) issuing, by the trusted third-party computer processor, a payment for the good or service to the vendor.

[0007]

[0007] In one embodiment, the method may further include receiving, by the trusted third party computer processor, one or more customer eligibility rules from the vendor, receiving, by the trusted third party computer processor, customer information for the customer, and verifying, by the trusted third party computer processor, that the customer is eligible by comparing the customer eligibility rules to the customer information.

[0008] In one embodiment, the customer eligibility rules include a minimum credit score, a minimum account balance, and / or a minimum age.

[0009] In one embodiment, the trusted third party may be a financial institution.

[0009]

[0010] In one embodiment, the customer may be a customer of a financial institution.

[0011] In one embodiment, the method further includes providing, by the trusted third party computer processor, a vendor-specific payment token to the vendor, where the vendor-specific payment token may be mapped to a financial account of the customer, the trusted third party computer processor receiving the vendor-specific payment token along with the invoice, and the trusted third party computer processor issuing a payment from the financial account to the vendor for the goods or services to the customer.

[0010]

[0012] In one embodiment, the method may further include collecting payment for the invoice from the customer by a trusted third party computer processor.

[0011]

[0013] In one embodiment, the trusted third party computer processor does not receive usage information regarding the goods or services from the vendor.

[0014] According to another embodiment, a system for providing customer identity protection may include a customer electronic device, a vendor system for a vendor of goods or services comprising at least one computer processor, and a trusted third party system for a trusted third party comprising at least one computer processor. The customer electronic device may be configured to request a verified vendor token for the vendor from the trusted third party system, generate a verified vendor token including a unique identifier, map the unique identifier to a customer identifier maintained by the trusted third party system, communicate the verified vendor token to the customer device, receive the verified vendor token from the vendor system that received the verified vendor token from the customer, verify that the verified vendor token is valid, confirm a payment relationship with the vendor system, receive the verified vendor token and an invoice for the goods or services from the vendor system, and issue a payment for the goods or services to the vendor system.

[0012]

[0015] In one embodiment, the trusted third party system may be further configured to receive one or more customer eligibility rules from the vendor system, receive customer information for the customer, and compare the customer eligibility rules to the customer information to verify that the customer is eligible.

[0013]

[0016] In one embodiment, customer eligibility rules may include a minimum credit score, a minimum account balance, and / or a minimum age.

[0017] In one embodiment, the trusted third party may be a financial institution.

[0014]

[0018] In one embodiment, the customer may be a customer of a financial institution.

[0019] In one embodiment, the trusted third party computer processor may be further configured to provide the vendor with a vendor-specific payment token mapped to the customer's financial account, receive the vendor-specific payment token along with the invoice, and issue a payment from the financial account to the vendor for goods or services to the customer.

[0015]

[0020] In one embodiment, the trusted third party computer processor may be further configured to receive payment for the invoice from the customer.

[0021] In one embodiment, the trusted third party computer processor may not receive usage information regarding the goods or services from the vendor.

[0016]

[0022] According to another embodiment, a non-transitory computer readable medium is disclosed having software instructions stored thereon that, when executed by a processor, causes the processor to receive a request from a customer for a verified vendor token for a good or service, generate a verified vendor token including a unique identifier, map the unique identifier to a customer identifier maintained by a trusted third party, receive the verified vendor token from a vendor that received the verified vendor token from the customer, verify that the verified vendor token is valid, confirm a payment relationship with the vendor, receive the verified vendor token and an invoice for the good or service from a vendor system, and issue a payment to the vendor for the good or service.

[0017]

[0023] In one embodiment, the non-transitory computer readable medium further includes software instructions that, when executed by the processor, cause the processor to receive one or more customer eligibility rules from the vendor, receive customer information for the customer, and compare the customer eligibility rules to the customer information to verify that the customer is eligible.

[0018]

[0024] In one embodiment, the customer eligibility rules include a minimum credit score, a minimum account balance, and / or a minimum age.

[0025] In one embodiment, the non-transitory computer readable medium further comprises software instructions that, when executed by the processor, cause the processor to provide a vendor-specific payment token mapped to a customer's financial account to a vendor, receive the vendor-specific payment token with an invoice, and issue a payment from the financial account to the vendor for goods or services to the customer. [Means for solving the problem]

[0019]

[0026] In order to facilitate a more complete understanding of the present invention, reference is made to the accompanying drawings, which should not be construed as limiting the invention, but are intended only to illustrate different aspects and embodiments, in which: [Brief description of the drawings]

[0020] [Figure 1]

[0027] FIG. 1 illustrates a system for customer identity protection from a service or product provider, according to an embodiment. [Diagram 2]

[0028] FIG. 2 illustrates a method for customer identity protection from a service or product provider, according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021]

[0029] SUMMARY OF THE DISCLOSURE Embodiments are directed to systems and methods for customer identity protection from service or product providers.

[0030] In one embodiment, a transaction between a customer and a vendor may be bifurcated into two components: a payment component (e.g., settlement) and a personal component (e.g., name, address, social security number, date of birth, etc.). For example, a particular vendor providing a good or service to a customer may only require a payment component and not a personal component. Examples of such services include wireless telephone service, Internet-based services, etc. By having a trusted third party, such as a financial institution, provide the payment component for the customer, the customer may receive the good or service without having to provide the personal component to the vendor.

[0022]

[0031] In one embodiment, the trusted third party may not receive customer usage information for the goods or services. Thus, the vendor does not have the customer's personal data and the trusted third party does not have the customer's usage. This provides benefits such as protecting user privacy and reducing the work required for the vendor to verify the user and collect payment. If necessary, government agencies can issue subpoenas to the vendor and / or the trusted third party for information.

[0023]

[0032] 1, a system for customer identity protection from a service or product provider, according to one embodiment, is provided. The system 100 may include a vendor system 110, a trusted third party system 120, and a customer 130.

[0024]

[0033] A customer may access the vendor system 110 and / or the trusted third party system 120 using an electronic device 135, which may be any suitable electronic device including a smartphone, a computer (e.g., a tablet, notebook, desktop, workstation, terminal, etc.), a kiosk, a smart device, an Internet of Things ("IoT") device, etc.

[0025]

[0034] Vendor system 110 may be a system for any suitable vendor providing goods or services to customer 130. In one embodiment, the goods or services provided may not require customer 130 to provide at least some of their personal identification information, such as social security number, age, address, etc. Examples may include mobile phone service, streaming entertainment services, etc.

[0026]

[0035] In one embodiment, the vendor may offer goods / services to the customer 130 that may require identity (e.g., this is a real person), age verification (e.g., this is a person old enough to make this purchase), etc. For example, the vendor may offer an adult website. The trusted third party system 120 may provide any additional information while protecting the privacy of the customer 130 from the vendor.

[0027]

[0036] In one embodiment, trusted third party system 120 may be a system for any suitable institution with which customer 130 may have an account, such as a financial institution (e.g., a bank), a financial technology ("fintech") service provider, etc. In another embodiment, trusted third party system 120 may be any suitable institution that may independently verify the identity of a customer.

[0028]

[0037] In one embodiment, the vendor system 110, the trusted third party system 120, and the electronic device 135 may communicate using one or more suitable communications networks.

[0029]

[0038] As shown with reference to FIG. 2, a method for customer identity protection from a service or product provider is provided according to one embodiment.

[0039] In step 205, the customer may register with the vendor to receive goods or services. In one embodiment, the goods or services offered may be goods or services that do not require the customer to provide at least some of their personal identification information, such as social security number, age, address, etc. Examples may include mobile phone service, streaming entertainment services, etc.

[0030]

[0040] In one embodiment, a customer may provide the vendor with the minimum information necessary to provide the product or service, such as a phone number and / or email address. Other information may be provided as needed and / or desired.

[0031]

[0041] For example, if the vendor is a wireless telephone provider, the customer may provide an alternative telephone number. Other information may be provided as needed and / or desired.

[0042] At step 210, the customer may log into an application or website of a trusted third party, such as a bank, fintech, etc. The customer may access the application or website using the customer's mobile electronic device.

[0032]

[0043] In step 215, the customer, or a vendor on behalf of the customer, may request and provide to the vendor a verified vendor token from a trusted third party. In one embodiment, the verified vendor token may include a unique identifier that can identify the customer to the trusted third party.

[0033]

[0044] A trusted third party may map the unique identifier to a customer identifier and maintain it in a database.

[0045] In step 220, the customer may provide or issue a verified vendor token to the vendor.

[0034]

[0046] The verified vendor token may be provided to a trusted third party in step 225. In one embodiment, the vendor and the trusted third party may configure business rules for customer verification, scoring, etc. For example, the vendor may require a particular credit score, minimum account balance, minimum age, etc., and the trusted third party may verify the customer based on these business rules.

[0035]

[0047] In one embodiment, the trusted third party may provide the vendor with additional information about the customer while protecting the customer's privacy. For example, the trusted third party may verify that the customer is a real person (e.g., not a bot), is over a certain age (e.g., not a minor), lives in a particular geographic location (e.g., lives in the United States), etc. This information may be provided to the vendor upon request to fulfill the vendor's requirements for providing goods or services to the customer while maintaining the customer's privacy.

[0036]

[0048] In step 230, the vendor may establish billing agreements with the trusted third party. For example, the trusted third party may arrange for the vendor's invoice to be submitted to the trusted third party for settlement using the verified vendor token and provide the vendor with a vendor-specific token.

[0037]

[0049] In one embodiment, the trusted third party can provide a vendor-specific payment token, account number, etc. to the vendor, which the vendor can use to bill the customer for goods or services. The vendor-specific payment token or account number may be specific to the customer. In one embodiment, the vendor-specific payment token may be provided to the vendor's electronic wallet or stored on file on the vendor system.

[0038]

[0050] In step 235, the vendor may provide an account to the customer, and in step 240, may provide goods or services to the customer.

[0051] In step 245, the vendor can bill the trusted third party for the goods or services, and in step 250, the trusted third party can arrange a settlement with the vendor on behalf of the customer. For example, if the trusted third party is a financial institution, a settlement can be arranged with the vendor. If the trusted third party is not a financial institution, a settlement can be arranged with the financial institution.

[0039]

[0052] In step 250, the trusted third party may collect payment for the invoice from the customer.

[0053] In one embodiment, under this configuration, the amount of information the vendor knows about the customer is limited to what it needs to know to properly provide the product or service to the customer. The trusted third party does not know about the product or service the customer is receiving or the customer's use of that product or service.

[0040]

[0054] Vendors may commission a trusted third party to provide payments on their behalf and may trust that the trusted third party has performed appropriate checks on the customer (e.g., know-your-identity procedures, anti-money laundering, etc.).

[0041]

[0055] General aspects of implementation of the system and method of the embodiments are described below.

[0056] An embodiment of the system or a portion of the system may be in the form of a "processing machine," such as, for example, a general purpose computer. As used herein, the term "processing machine" should be understood to include at least one processor that uses at least one memory. The at least one memory stores a set of instructions. The instructions may be stored permanently or temporarily in one or more memories of the processing machine. The processor executes the instructions stored in the one or more memories to process data. The set of instructions may include various instructions to perform a particular task or tasks, such as those described above. Such a set of instructions to perform a particular task may be characterized as a program, a software program, or simply software.

[0042]

[0057] In one embodiment, the processing machine may be a special purpose processor.

[0058] As noted above, a processing machine executes instructions stored in one or more memories to process data. This processing of data may, for example, be in response to commands by one or more users of the processing machine, in response to previous processing, in response to requests by another processing machine, and / or other input.

[0043]

[0059] As mentioned above, the processing machine used to implement the embodiments can be a general-purpose computer. However, the above-mentioned processing machine can utilize any of a wide variety of other technologies. The wide variety of other technologies includes computer systems including special-purpose computers, for example, microcomputers, minicomputers, or mainframes, programmable microprocessors, microcontrollers, peripheral integrated circuit elements, CSICs (customer specific integrated circuits) or ASICs (application specific integrated circuits) or other integrated circuits, logic circuits, digital signal processors, programmable logic devices such as FPGAs, PLDs, PLAs, or PALs, or any other device or configuration of devices capable of implementing the steps of the processes disclosed herein.

[0044]

[0060] The processing machine used to implement the embodiments may utilize any suitable operating system. Thus, the embodiments may include a processing machine running an iOS operating system, an OSX operating system, an Android operating system, a Microsoft Windows operating system, a Unix operating system, a Linux operating system, a Xenix operating system, an IBM AIX operating system, a Hewlett-Packard UX operating system, a Novell Netware operating system, a Sun Microsystems Solaris operating system, an OS / 2 operating system, a BeOS operating system, a Macintosh operating system, an Apache operating system, an OpenStep operating system, or another operating system or platform.

[0045]

[0061] It is understood that in order to implement the method of the embodiments as described above, it is not necessary for the processor and / or memory of the processing machine to be physically located in the same geographical location. That is, each of the processors and memories used by the processing machine may be located in separate geographical locations and communicatively connected in any suitable manner. In addition, it is understood that each of the processors and / or memories may be configured in different physical devices. Thus, it is not necessary for the processor to be a single device in one location and the memory to be another single device in another location. That is, it is contemplated that the processor may be two devices in two different physical locations. The two separate devices may be connected in any suitable manner. In addition, the memory may include two or more portions of the memory in two or more physical locations.

[0046]

[0062] To further explain, the processes as described above are performed by various components and various memories. However, it is understood that the processes performed by two separate components as described above may be performed by a single component according to further embodiments. Furthermore, the processes performed by one separate component as described above may be performed by two separate components.

[0047]

[0063] Similarly, memory storage performed by two separate memory portions as described above may be performed by a single memory portion according to further embodiments. Furthermore, memory storage performed by one separate memory portion as described above may be performed by two memory portions.

[0048]

[0064] Further, various technologies may be used to provide communication between the various processors and / or memories, and to enable the processors and / or memories to communicate with any other entity, i.e., to obtain further instructions or to access and use a remote memory store. Such technologies used to provide such communication may include, for example, a network, the Internet, an intranet, an extranet, a LAN, Ethernet, wireless communication via a cell tower or satellite, or any client-server system that provides communication. Such communication technologies may use any suitable protocol, such as, for example, TCP / IP, UDP, or OSI.

[0049]

[0065] As mentioned above, a set of instructions may be used in the processing of the embodiments. The set of instructions may be in the form of a program or software. The software may be in the form of, for example, system software or application software. The software may also be in the form of, for example, a collection of separate programs, a program module within a larger program, or a portion of a program module. The software used may also include modular programming in the form of object-oriented programming. The software tells the processing machine what to do with the data being processed.

[0050]

[0066] It is further understood that the instructions or sets of instructions used in implementing and operating the embodiments may be in any suitable form that allows a processing machine to read the instructions. For example, the instructions forming the program may be in the form of a suitable programming language that is converted into machine code or object code to allow one or more processors to read the instructions. That is, written lines of programming code or source code in a particular programming language are converted into machine code using a compiler, assembler, or interpreter. The machine code is, for example, binary coded machine instructions that are specific to a particular type of processing machine, i.e., a particular type of computer. The computer understands the machine code.

[0051]

[0067] Any suitable programming language may be used in accordance with various embodiments. By way of example, programming languages ​​used may include, for example, assembly language, Ada, APL, Basic, C, C++, COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX, Visual Basic, and / or JavaScript. Furthermore, it is not necessary that a single type of instruction or a single programming language be utilized in connection with the operation of the systems and methods. Rather, any number of different programming languages ​​may be utilized as needed and / or desired.

[0052]

[0068] Similarly, the instructions and / or data used in implementing the embodiments may utilize any compression or encryption technique or algorithm, as may be desired. An encryption module may be used to encrypt the data. Additionally, files or other data may be decrypted using, for example, an appropriate decryption module.

[0053]

[0069] As mentioned above, the embodiments can be embodied in the form of a processing machine, including, for example, a computer or computer system including at least one memory, by way of example. It should be understood that the set of instructions, i.e., software, that enables the computer operating system to perform the above-mentioned operations, may be included in any of a wide variety of one or more media, as desired. Furthermore, the data processed by the set of instructions may also be included in any of a wide variety of one or more media. That is, the particular medium within the processing machine utilized to hold the set of instructions and / or data used in the embodiments, i.e., memory, may take, for example, any of a variety of physical forms or transmission media. By way of example, the medium may be in the form of paper, transparencies, compact discs, DVDs, integrated circuits, hard disks, floppy disks, optical disks, magnetic tape, RAM, ROM, PROM, EPROM, wires, cables, fibers, communication channels, satellite transmissions, memory cards, SIM cards, or other remote transmissions, as well as any other medium or source of data that can be read by a processor.

[0054]

[0070] Furthermore, the memory or memories used in a processing machine implementing an embodiment may be in any of a wide variety of forms that allow the memory to hold instructions, data, or other information, as desired. Thus, the memory may be in the form of a database for holding data. The database may use any desired file organization, such as, for example, a flat file organization or a relational database organization.

[0055]

[0071] The systems and methods utilize various "user interfaces" to allow a user to interface with one or more processing machines used to implement the embodiments. As used herein, a user interface includes any hardware, software, or combination of hardware and software used by a processing machine that allows a user to interact with the processing machine. A user interface may be in the form of, for example, a dialog screen. A user interface may further include any of a mouse, a touch screen, a keyboard, a keypad, a voice reader, a voice recognizer, a dialog screen, a menu box, a list, a check box, a toggle switch, a push button, or any other device that allows a user to receive information regarding the operation of the processing machine as the other device processes a set of instructions and / or provides information to the processing machine. Thus, a user interface is any device that provides communication between a user and a processing machine. Information provided by a user to a processing machine through a user interface may be in the form of, for example, a command, a selection of data, or some other input.

[0056]

[0072] As discussed above, a user interface is utilized by a processing machine that executes a set of instructions, such that the processing machine processes data for a user. A user interface is generally used by a processing machine to interact with a user to convey information or receive information from the user. However, it should be understood that, according to some embodiments of the systems and methods, it is not necessary for a human user to actually interact with a user interface used by a processing machine. Rather, it is also contemplated that the user interface may interact, i.e., convey and receive information, with another processing machine rather than a human user. Thus, the other processing machine may be considered a user. Furthermore, it is contemplated that the user interface utilized in the systems and methods may interact partially with another processing machine or machines and partially with a human user.

[0057]

[0073] Those skilled in the art will readily appreciate that the embodiments are susceptible to a wide range of utility and applications. Numerous embodiments and adaptations of the invention other than those described herein, as well as numerous variations, modifications, and equivalents, will be apparent from, or reasonably suggested by, the foregoing description of the invention without departing from the spirit or scope thereof.

[0058]

[0074] Thus, while the embodiments have been described in detail herein with reference to exemplary embodiments, it should be understood that the disclosure is merely illustrative and exemplary of the invention, and is made to provide an enabling disclosure of the invention. Thus, the foregoing disclosure is not intended to be construed as limiting the invention or otherwise excluding any other such embodiments, adaptations, variations, modifications, or equivalents.

Claims

1. 1. A method for providing customer identity protection, comprising: receiving, by a trusted third party computer processor of a trusted third party, customer information for a customer from a customer electronic device, the customer information including personally identifiable information; receiving, by the trusted third party computer processor, a request from the customer electronic device for a verified vendor token for a vendor of goods or services; generating, by the trusted third party computer processor, the verified vendor token for the vendor, the verified vendor token including a unique identifier for the customer and not including a payment component and the personally identifiable information; mapping, by the trusted third party computer processor, the unique identifier for the customer to the customer information that has been received by the trusted third party; providing, by the trusted third party computer processor, the verified vendor token to the customer electronic device; providing, by the customer electronic device, the verified vendor token to a vendor electronic device in lieu of the personally identifiable information for the customer, wherein the customer remains anonymous to the vendor; receiving, by the trusted third party computer processor, from the vendor electronic device a request to verify customer entitlement for the customer associated with the verified vendor token for the customer to receive the goods or services, wherein the vendor electronic device does not have access to the personally identifiable information for the customer; verifying, by the trusted third party computer processor, that the customer meets the customer eligibility to receive the product or service by applying customer eligibility rules to the customer information mapped to the verified vendor token; providing, by the trusted third party computer processor, a vendor-specific payment token to a vendor's electronic wallet, the vendor-specific payment token being mapped to a financial account for the customer and not including the personal identification information for the customer and an identifier for the financial account, the vendor providing the product or service in response to the provision; receiving, by the trusted third party computer processor, from the vendor, the vendor-specific payment token and an invoice for the goods or services; and effecting, by the trusted third party computer processor, payment for the goods or services from the financial account of the customer to the vendor.

2. The method of claim 1 , further comprising the step of receiving, by the trusted third party computer processor, the customer eligibility rules from the vendor electronic device.

3. The method of claim 1 , wherein the customer eligibility rules include a minimum credit score, a minimum account balance, or a minimum age.

4. The method of claim 1 , wherein the trusted third party is a financial institution.

5. The method of claim 4 , wherein the customer is a customer of the financial institution.

6. The method of claim 1 , further comprising the step of receiving, by the trusted third party computer processor, a payment for the invoice from the customer.

7. The method of claim 1 , wherein the trusted third party computer processor does not receive usage information regarding the goods or services from the vendor.

8. 1. A system for providing customer identity protection, comprising: a customer electronic device for the customer; a vendor electronic device for a vendor of goods or services, the vendor electronic device including at least one computer processor; a trusted third party system for a trusted third party, the trusted third party system including at least one computer processor; the trusted third party system is configured to receive customer information for the customer from the customer electronic device, the customer information including personally identifiable information; the customer electronic device is configured to request a verified vendor token for the vendor from the trusted third party system; the trusted third party system is configured to generate the verified vendor token for the vendor, the verified vendor token including a unique identifier for the customer and not including a payment component and the personally identifiable information; the trusted third party system configured to map the unique identifier for the customer to the customer information that has been received by the trusted third party system; the trusted third party system configured to communicate the verified vendor token to the customer electronic device; the customer electronic device is configured to communicate the verified vendor token to the vendor electronic device in lieu of the personally identifiable information for the customer, such that the vendor electronic device does not have access to the personally identifiable information for the customer and the customer remains anonymous to the vendor; the trusted third party system is configured to receive, from the vendor electronic device, a request to verify a customer entitlement for the customer associated with the verified vendor token; the trusted third party system is configured to verify that the customer meets the customer eligibility rules by applying customer eligibility rules to the customer information mapped to the verified vendor token; the trusted third party system is configured to provide a vendor-specific payment token to a vendor's electronic wallet; the vendor-specific payment token is mapped to a financial account for the customer and does not include the personal identifying information for the customer and an identifier for the financial account; the vendor electronic device provides the product or service in response to the offer; the trusted third party system receives the vendor-specific payment token and an invoice for the goods or services from the vendor electronic device; The trusted third party system is configured to effect payment for the goods or services from the customer's financial account to the vendor electronic device.

9. The system of claim 8 , wherein the trusted third party system is configured to receive the customer eligibility rules from the vendor electronic device.

10. The system of claim 8 , wherein the customer eligibility rules include a minimum credit score, a minimum account balance, or a minimum age.

11. The system of claim 8 , wherein the trusted third party is a financial institution.

12. The system of claim 11 , wherein the customer is a customer of the financial institution.

13. 10. The system of claim 9, wherein the trusted third party system is further configured to receive a payment for the invoice from the customer.

14. The system of claim 9 , wherein the trusted third party system does not receive usage information regarding the goods or services from the vendor.

15. A non-transitory computer-readable medium having software instructions stored thereon, the software instructions, when executed by a processor, causing the processor to: receiving customer information for the customer from the customer electronic device, the customer information including personally identifiable information; receiving a request from the customer electronic device for a verified vendor token for a vendor of goods or services; generating a verified vendor token for the vendor, the verified vendor token including a unique identifier for the customer and not including a payment component for the customer and the personally identifiable information; Mapping the unique identifier for the customer to the customer information; providing the verified vendor token to the customer electronic device, wherein the customer remains anonymous to the vendor; receiving a request from the vendor electronic device to verify customer eligibility for the customer associated with the verified vendor token, the vendor receiving the verified vendor token from the customer electronic device in lieu of the personally identifiable information for the customer; verifying that the customer meets the customer qualifications by applying customer qualification rules to the customer information mapped to the verified vendor token; Providing a vendor-specific payment token to the vendor's electronic wallet; the vendor-specific payment token is mapped to a financial account for the customer and does not include the personal identifying information for the customer and an identifier for the financial account; receiving from the vendor a vendor-specific payment token and an invoice for the goods or services; A non-transitory computer readable medium for effecting payment for the goods or services from the financial account of the customer to the vendor.

16. and further software instructions which, when executed by the processor, cause the processor to: receiving the customer eligibility rules from the vendor; 16. The non-transitory computer-readable medium of claim 15.

17. 16. The non-transitory computer-readable medium of claim 15, wherein the customer eligibility rules include a minimum credit score, a minimum account balance, or a minimum age.

Images