WO2025076365A1 - System and method for verifying the purchase of an electronic stored value account - Google Patents

Abstract

A stored value account processing system for receiving a purchase verification for a form of electronic stored value account. The system verifying purchaser information and delivering a secure link to a recipient. The system verifying recipient information and enabling access to the electronic stored value account to the recipient.

Description

SYSTEM AND METHOD FOR VERIFYING THE PURCHASE OF AN ELECTRONIC STORED VALUE ACCOUNT

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to US Provisional Application No. 63/543,031, filed October 6, 2023, which is expressly incorporated by reference herein.

BACKGROUND

[0002] The present disclosure generally relates to electronic stored value accounts and, more particularly, to a system and method for verifying the purchase of a form of electronic stored value account.

[0003] The purchase of electronic stored value account has greatly increased in recent years. With the increased volume of electronic stored value accounts issued, there is also increased fraud since it is easier and faster to drain funds from an electronic stored value in comparison to standard purchasing practices. This is especially true if there is inconsistent biller/purchaser risk assessment on the order placement and minimal control mechanisms on the recipient electronic stored value account access. There is a need to reduce accessibility without control factors to stored value and be able to void issued electronic stored value accounts at an increasing frequency and with decreased reaction time because the speed with which fraudsters act necessitates quicker ways to secure and prevent drainage. Voiding an electronic stored value account is no longer an exception, but a new norm.

SUMMARY

[0004] The present disclosure includes one or more of the features recited in the appended claims and/or the following features which, alone or in any combination, may comprise patentable subject matter.

[0005] In a first aspect of the disclosed embodiments, a method is performed by a processor computer device having a processor and executable instructions stored on a non-transitory computer readable medium which, when executed by the processor, causes the processor computer device to perform the method. The method includes receiving a purchase verification for a form of electronic stored value account. The method also includes verifying purchaser information related to the purchaser of the electronic stored value account. The method also includes delivering a secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser information. The method also includes verifying recipient information related to the recipient subsequent to, and in response to, accessing of the secure link by the recipient. The method also includes delivering the electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient information.

[0006] In a second aspect of the disclosed embodiments, a stored value account processing system has a processor and a non-transitory computer readable medium having executable instructions stored thereon which, when executed by the processor, causes the processor to receive a purchase verification for an electronic stored value account. The processor is also configured to verify purchaser information related to the purchaser of the electronic stored value account. The processor is also configured to deliver an secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser and transaction information. The processor is also configured to verify recipient information related to the recipient subsequent to, and in response to, registration required for accessing stored value or activation of the secure link by the recipient. The processor is also configured to granting access to electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient or registered user’s information.

[0007] Additional features, which alone or in combination with any other feature(s), such as those listed above and those listed in the claims, may comprise patentable subject matter and will become apparent to those skilled in the art upon consideration of the following detailed description of various embodiments exemplifying the best mode of carrying out the embodiments as presently perceived.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The detailed description particularly refers to the accompanying figures in which: [0009] FIG. 1 is a flowchart for verifying the purchase of an electronic stored value account;

[0010] FIG. 2 is a screenshot of a payment approval screen that is generated in a first email after the purchase of an electronic stored value account; [0011] FIG. 3 is a screenshot of a portion of the payment approval screen shown in FIG. 2 that identifies the recipient of the electronic stored value account;

[0012] FIG. 4 is a screenshot of a secure link that provides access to content that is generated in a second email delivered to the recipient of the electronic stored value account;

[0013] FIG. 5 is a screenshot of redemption instructions for the electronic stored value account that is generated in response to clicking the activation link shown in FIG. 4;

[0014] FIG. 6 illustrates an embodiment of a system and/or environment for facilitating a purchase and activation of a stored value account according to an embodiment of the disclosure; and

[0015] FIG. 7 illustrates a particular machine suitable for implementing the several embodiments of the disclosure.

DETAILED DESCRIPTION

[0016] While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific exemplary embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims. [0017] Referring to FIG. 1, the disclosed embodiments include an electronic stored value account processing system having a processor and a non-transitory computer readable medium having executable instructions stored thereon which, when executed by the processor, causes the processor to perform the steps outlined below. For example, the electronic stored value account processing system is configured to provide novel, unforeseen, and never before suggested processes for securing stored value accounts and the concomitant improvements in components (and the components’ functioning) utilized by the disclosed systems and methods relating to said processes for securing stored value accounts. For example, in embodiments, the electronic stored value account processing system is configured to separate the ownership, possession, and/or custody of a stored value account from the right, authority, ability, or combinations thereof, to use the stored value account, e.g., access funds contained in the stored value account. The electronic stored value account processing system is also configured to facilitate, allow, and/or cause the combining of the ownership, possession, and/or custody of a stored value account with the right, authority, and/or ability to use the stored value account.

[0018] In an exemplary embodiment, a purchaser 100 uses a point of sale 102 to purchase an electronic stored value account 132. In some embodiments, the point of sale 102 is an electronic device, for example a computer or mobile device of the purchaser 100. The purchaser 100 uses the point of sale 102 to visit a website for purchasing the electronic stored value account 132. In some embodiments, the purchaser could be a business user with company information. During the purchase, the purchaser 100 enters purchaser information, for example a name, a physical address, an email address, or a phone number. The purchaser 100 also enters a credit card number for completing the transaction. In a business use scenario, the business can use a bank account or other forms of payment. In a consumer scenario, the payment method could also be other alternative payment methods beyond credit card. Optionally, the purchaser enters a name, physical address, email address, and phone number of an intended recipient 120 of the electronic stored value account 132, in some embodiments the electronic stored value account 132 can be and/or be represented by a physical stored value card, and electronic stored value card, an electronic wallet, or combinations thereof. In some embodiments, the purchaser 100 is the same as the recipient 120. The purchaser information is stored in a risk management system 112 using security such as tokenizing the data, encrypting the data, and/or hashing the data. The purchaser information stored in the risk management system 112 also includes the credit card number, as well as, information related to the point of sale 102, for example, the IP address and location of the point of sale 102.

[0019] The order management system 110 receives a purchase verification for the electronic stored value account 132. The purchaser information related to the purchaser 100 is verified with risk management system 112. First, the risk management system 112 determines whether the credit card is valid or if the credit card is stolen or expired. Is the credit card is determined to be stolen or expired, the purchase of the electronic stored value account 132 is terminated. In such a scenario, the purchaser 100 receives an email notification that the transaction cannot be completed, in some embodiments.

[0020] The risk management system 112 then verifies the remainder of the purchaser information. In some embodiments, if the point of sale 102 is a well-known device that has been approved in past transactions, the risk management system approves the transaction. In some embodiments, the risk management system 1 12 determines whether a first data point of the purchaser information corresponds to a second data point of the purchaser information. For example, in one embodiment, the risk management system 112 determines whether the purchaser email address belongs to the purchaser name. In another embodiment, the risk management system 112 determines whether the purchaser phone number belongs to the purchaser name. It will be appreciated that the risk management system 112 can determine a correlation between any data points in the purchaser information. The risk management system 112 utilizes multi-level, coincidental filtering 103 to efficiently identify, determine, verify and/or deny a transaction request, e.g. an order 105. In this context, coincidental means occurring on or about the same time. Such multi-level, coincidental filtering 103 is an improvement to existing computer technology as it allows the risk management system 112 to operate using reduced processing power and memory requirements.

[0021] In one embodiment, the risk management system 112 determines whether any of the purchaser information is on a fraud watch list. In some embodiments, the risk management system 112 performs a velocity check by monitoring a number of electronic stored value accounts 132 purchased by the purchaser 100 or purchased on the point of sale 102 in a predetermined time. The risk management system 112 is configured to communicate with a secure content access controller 116. The secure content access controller 116 is configured to store, maintain, control, deliver, or combinations thereof, the rights, authorizations, abilities, or combinations thereof, i.e. content package 117, to use electronic stored value account(s) 132, e.g., an electronic stored value account 132 which is the subject of order 105. In an embodiment the secure content access controller 116 is configured to communicate with order management system 110 and respond to order management system 110 requests for a secure link 402 which can be activated and/or accessed by a recipient 120 to receive content package 117. The risk management system 112 may be configured to suspend delivery of the secure link 402 with access to the electronic stored value account 132, if the number of electronic stored value accounts 132 purchased by the purchaser 100 in a predetermined time exceeds a predetermined number.

[0022] If any of the purchaser information verifications fail, the system suspends delivery of the secure link 402. In such a scenario, additional verification checks may be performed. In some embodiments, the purchaser 100 receives an email indicating that the transaction cannot be complete and directing the purchaser to customer service. In some embodiments, the purchaser 100 and/or point of sale 102 is flagged in the risk management system 112 from future transactions. [0023] If the transaction is verified, the order management system 110 sends a receipt email 200 containing a receipt for the purchase. As illustrated in FIG. 2, the email 200 includes an order number 201, order date 202, and an amount of the order 203. Additionally, the credit card number used is confirmed. FIG. 3 illustrates a remainder of the receipt email 300, which identifies an email address of the recipient 301, a delivery date 302, and redemption instructions 303.

[0024] As discussed above, the order management system 110 asks the secure content access controller 116 for permission to send a secure link email 118 to initiate access to the content package 117. If permission is granted by the secure content access controller 116, the secure content access controller 116 provides the order management system 110 with the content package 117 in the form of secure link 402 which has been produced, generated, and/or created by the secure content access controller 116. In an embodiment, the order management system 110 receives the content package 117 from the secure content access controller 116 and the order management system 110 produces, generates, and/or creates secure link 402 which contains the content package 117 for provision to the recipient 120. The order management system 110 delivers to the recipient 120 the secure link email 118 (shown in FIG. 4) having secure link 402. The recipient 120 clicks on the secure link 402 using a recipient system 122, for example a computer or mobile device. Recipient information is then delivered to the risk management system 112 upon access of the secure link 402. In some embodiments, the recipient information is the same as the purchaser information. In one embodiment, the recipient information includes the recipient email address. In other embodiments, the recipient information includes the name of the recipient, a physical address and phone number of the recipient, an IP address of the recipient system 122, or a location of the recipient system 122. In other embodiments, the recipient information could include secret pins or one-time passwords to be verified, or other forms of challenge questions or data input validation.

[0025] Recipient information from the secure link access is then sent to the secure content access controller 116 to verify the recipient information by performing risk checks with the risk management system 112. hi some embodiments, the risk management system 112 verifies the recipient information by determining whether the recipient information matches the purchaser information. For example, the risk management system 112 determines whether the email address of the recipient 120 matches the email address of the purchaser 100. In some embodiments, if the recipient system 122 is a well-known device that has been approved in past transactions, the risk management system approves the transaction. In some embodiments, the risk management system 112 determines whether a first data point of the recipient information corresponds to a second data point of the recipient information. For example, in one embodiment, the risk management system 112 whether the recipient email address belongs to the recipient name. In another embodiment, the risk management system 112 determines whether the recipient phone number belongs to the recipient name. It will be appreciated that the risk management system 112 can determine a correlation between any data points in the recipient information. In one embodiment, the risk management system 112 determines whether any of the recipient information is on a fraud watch list. In some embodiments, the risk management system 112 performs a velocity check by monitoring a number of electronic stored value accounts 132 requested and/or received by the recipient 120 or requested and/or received at the recipient system 122 in a predetermined time. The risk management system 1 12 blocks activating the electronic stored value account 132, if the number of electronic stored value accounts 132 requested and/or received by the recipient 120 in a predetermined time exceeds a predetermined number. Activation of the electronic stored value account 132 is also suspended based on a location or region where the secure link 402 is accessed, in some embodiments. For example, access of the electronic stored value account 132 in high-risk regions may be prohibited. In some embodiments, access of the electronic stored value account 132 is suspended based on a comparison of the location of the point of sale 102 to a location of the recipient system 122. In some embodiments, pattern and other advanced correlation techniques could identify victim assisted or other fraud activity by comparison of recipient and purchaser information points.

[0026] If the recipient information is verified, the secure content access controller 116 sends activation message to activation system 130, and the activation system 130 delivers the electronic stored value account 132 to the recipient 120. As illustrated in FIG. 5, the activation system 130 delivers instructions 502 for redeeming electronic stored value account 132.

[0027] In some embodiments, the system verifies redeemer information of a user redeeming the electronic stored value account 132 at a time of redemption of the electronic stored value account 132. In some embodiments, the system permits redemption of the electronic stored value account subsequent to, and in response to, verifying the redeemer information. In some embodiments, the system verifies the redeemer information by determining a physical distance between a location of redemption of the electronic stored value account 132 and a location of purchase of the electronic stored value account 132. In some embodiments, the system suspends redemption of the electronic stored value account 132 if the physical distance between a location of redemption of the electronic stored value account 132 and a location of purchase of the electronic stored value account 132 exceeds a predetermined distance.

[0028] Figure 6 is a block diagram of an example system network 600 that may be used to implement an embodiment of the system of Figure 1. Those of ordinary skill in the art will appreciate that the system network 600 in Figure 6 is described to illustrate one example of a network that may be used to implement the system described above with reference to Figure 1. Many other network architectures not described here may be used as well. In the embodiment of Figure 6, the system network 600 includes a web server farm 602, a database server farm 604, an electronic data interchange (EDI) farm 607, and an internal access server farm 608. The system network 600 includes a layer 7 switch farm 610 and an Internet firewall infrastructure 612, for example, to implement a consumer front-end over the Internet 614. The consumer front-end may be implemented as a site on the World Wide Web. The system network 600 also includes an EDI virtual local area network (VLAN) 616 with point-to-point connections 618 to EDI partners 620a, 620b, 620c.

[0029] In general, the system network 600 in Figure 6 includes remote and local infrastructure. Connectivity to the system network 600 may be provided by co-location facilities hosting the remote infrastructure. Remote infrastructure includes servers, routers, databases and other network entities that are geographically distributed as needed to provide access to partners and/or to consumers. The remote infrastructure includes devices that may fall under a functional class and may be distributed in the system network 600 as a farm (e.g. web server farm, EDI server farm, etc.). Local infrastructure may include servers, routers, databases, and other network entities that provide limited, primarily internal access within the system, for example, for resource management. Local infrastructure may also be geographically distributed with access limited by network design (e.g. completely internally accessed databases may be maintained within an Intranet).

[0030] The system network 600 in Figure 6 implements a logical separation of server systems based upon type and manner of access. This introduces multiple layers of access, and in turn, provides a deeper layer of security, even within the system network 600. The system network 600 includes a general vertical depth of separation of service and levels of security allowing for several layers of access. The layers of access range from the consumer front-end (via the Internet 614), which is at the forefront and has the lightest layer of security, to a system database 605, which is at the deepest layer of access and security.

[0031] The layers of access are implemented as virtual local area networks (VLANs) having no real access to one another except through routing done by routing modules on the network switches. Each VLAN may be configured appropriately to limit access according to the appropriate level of security. The levels of security correspond in general to four tiers of network entities: the presentation tier, the business logic tier, the data access tier, and the data tier.

[0032] At the top level of access (for the consumer front-end), the presentation tier is responsible for delivery of data to end clients. The end clients may be consumers or partners 620a, 620b, 620c. In the presentation tier, data is formatted for communication with the business logic tier of applications that processes requests and handles data delivery to the client applications. Data in the presentation tier may be in XML format along with XSLT stylesheets to allow rendering by client applications. The presentation tier operations, generally, in a layer of servers from the web server farm 602 that resides in a DMZ (Demilitarized Zone) network. These servers in the DMZ network may be accessed using a web farm DMZ VLAN 630 and the Layer 7 switch farm 610. The DMZ network servers operate as proxy servers between consumers and the enterprise infrastructure.

[0033] The next layer of access includes servers in the web server farm 602 that form the business logic tier. The business logic tier includes application code (Beans) that will handle requests from client applications (such as web browsers) and make requests to the Data Access Tier for relevant data. It will then process the data and deliver it for presentation to the client applications. The business logic tier is kept separate from interaction with consumers to preserve integrity of the applications and access to the database 605. Added security may be provided by an outer web farm VLAN 632.

[0034] In the next layer, the data access tier may make requests directly to the Data Tier (or the database 605). The data access tier may be separate from the business logic tier of applications to differentiate how the data is stored and how it is retrieved from certain platforms. Security may be configured with an inner web farm VLAN 634. [0035] The data tier is in the last layer of security, which includes the database 605, and which has the tightest security to protect the most critical data. Security may be configured with an internal access VLAN 636.

[0036] The system network 600 includes a general horizontal separation of EDI partnerships, which are logical VLANs that separate access by each partner 620a, 620b, 620c to the infrastructure of the example system for implementing the disclosed lottery system using the system network 600. In general, a partner may access their own private VLAN at 616 and 618 into the system network 600 infrastructure through a VPN concentrator or routed through a routing module on the backbone switch. This structure may isolate potential security breaches from single partners 620a, 620b, 620c. It may also prevent any partner 620a, 620b, 620c from being able to access rival partner data from the system network 600.

[0037] The EDI partner access to the system network 600 may also be layered vertically according to level of security. An EDI farm DMZ VLAN 640 provides the lowest level of security at the consumer front-end for access to the EDI server farm 606. The outer EDI farm VLAN 642 provides a higher level of security at a business logic level similar to the business logic tier described above with reference to the web server farm 602. The highest level of security is provided at the inner EDI farm VLAN 644 for access to more critical data via the database server farm 704.

[0038] Connectivity to the system network 600 may be provided by co-location facilities hosting the remote infrastructure. Connectivity may be provided by Tier 1 Internet Backbone providers to ensure access to most networks without having to transcend networks in order to provide the shortest network path from consumer to infrastructure. Besides utilizing connectivity to Tier 1 providers and managing complex BGP routes to the Internet Backbone, a backup connection to InterNAP will also be established.

[0039] In the example system for implementing an embodiment of the disclosed lottery system, the complex backbone connections force the infrastructure to appear “local” to the consumers accessing the system network 600 via their host ISPs. This prevents the consumer from transcending networks between peer networks and eventually experience degraded network performance.

[0040] The web server farm 602 includes two banks of servers for serving either static or dynamic content. Each bank may be designated as either the static web farm or the dynamic web farm. The static web farm may service client requests for static content that is neither databasegenerated nor does it use any type of server content processing and generation before being transmitted through the Internet to the client applications (e.g. web browser). Such examples of content would be images, video, or web templates. The dynamic web farm may be designed to serve dynamic content generated in multiple ways, whether that is done via XML/XLS transformation, server-side scripting, or through middle-tier applications that directly interfaces with the database 605.

[0041] The web server farm 602 may be implemented using any suitable hardware and software systems implementing server functions. In one example implementation, the web server farm 602 is implemented with Sun® multiprocessor blade servers (Sun® is a registered trademark of Oracle America, Inc.) running either the Solaris® (Solaris® is a registered trademark of Oracle America, Inc.) operating system or Red Hat® Enterprise LinuxTM operating system (Red Hat® Enterprise LinuxTM arc trademarks of Red Hat, Inc.). The example implementation of the web server farm 602 also includes the Zeus® web server (ZWS) application (Zeus® is a registered trademark of Marden-Kane, Inc.). Like the Apache® web server Apache Micro Peripherals, Inc.), the ZWS is a robust, commercial-grade, full-featured and highly efficient web server software. However, ZWS is multi-threaded to leverage the symmetric multiprocessing nature of multi-cored hardware platforms, which increases the response times and load servicing for client requests. The web server farm 602 will also house the Java® application server software (Java® is a registered trademark of Oracle America, Inc.) that operates the applications to service consumer requests on the enterprise website. The Java® application server software may be a combination of Apache® Tomcat for simple Java® applications and JBoss Application Server software for J2EE applications.

[0042] It is to be understood that specific implementations of the web server farm 602 may use any suitable hardware and software systems. The hardware and software systems described above are merely examples of the types of hardware and software systems that may be used.

[0043] The database server farm 604 may store data specific to consumer front-end interactions and the EDI partner data collected from partners 620a, 620b, 620c. The database server farm 604 may be implemented using any suitable hardware and software systems configured to operate as database servers. In one example implementation, the database server farm 604 is implemented using Sun multiprocessor Enterprise servers banked with multi-core processors and full redundant power and mirrored drives for the operating system and database application. Depending upon the nature of the application and the database 605 that is needed to interface against such applications, the database server farm 604 may run either the Oracle Database Server product or the MySQL Database server product. Also, depending upon the nature of the data that is being stored, highly complex relational database tables may use Oracle while simplistic database schemas may use MySQL. The database server applications may be clustered to ensure high availability and fault tolerance. This will also provide application load balancing among the database server farm 604.

[0044] The database 605 for the database server farm 604 may reside in a SAN (Storage Area Network) solution that will offer both high availability and fault tolerance.

[0045] It is to be understood that specific implementations of the database server farm 604 may use any suitable hardware and software systems. The hardware and software systems described above arc merely examples of the types of hardware and software systems that may be used.

[0046] The EDI (Electronic Data Interchange) farm 606 may be designated in the system network 600 to communicate with partners 620a, 620b, 620c. The EDI farm servers 606 may have different applications and permissions from the web server farm 602 to access and process, as well as store, data within the database farm 604. The nature of the applications operating on the EDI farm servers 606 may have more direct access to the database 605 to increase efficiency in data processing and storage. The EDI farm servers 606 may reside in a private VLANs (Virtual Local Area Networks) that can only be accessed via VPN (Virtual Private Network) Concentrators or through specific Point-to-Point access into the VLAN as shown at 616 and 618.

[0047] The EDI farm servers 606 may be implemented using any suitable hardware and software system configured to operate server functions, hi an example implementation, the EDI server farm 606 is implemented using the same platform as that of the web server farm 602 or by running IBM Mainframes. The EDI farm servers 606 software in the example implementation may also be similar’ to that of the web server farm 602 software. If the EDI farm servers 606 include IBM Mainframes, then the hardware will run IBM AIX operating systems, and the EDI farm servers 606 will run IBM Websphere Application Server software. [0048] It is to be understood that specific implementations of the EDI server farm 606 may use any suitable hardware and software systems. The hardware and software systems described above are merely examples of the types of hardware and software systems that may be used.

[0049] The internal access farm servers 608 may also resemble the web server farm 602 in platform, software, and resource architecture. However, like the EDI farm servers 606, the applications will be tailored for internal access from an enterprise Intranet. Such applications may include data mining and statistical information for marketing and sales.

[0050] Referring again to Figure 6, in some embodiments, the transaction processing system 620 may be configured for communication with one or more information datastores 630, for example, which may individually or collectively include an entry for each of the stored value accounts offered for sale the retailer 601 or multiple retailers.

[0051] Also, in some embodiments, the transaction processing system 620 may be configured for communication with at least one SAS (c.g., at least one of 640a, 640b, and 640c). In various embodiments, the transaction processing system 620 is configured to utilize one or more application programming interfaces (APIs) that are each configured to allow the transaction processing system 620 to interface and/or interact with a particular SAS (e.g., 640a, 640b, 640c). For example, in the embodiment of Figure 6 the transaction processing system 620 utilize each of a first API 625a, a second API 625b, and a third API 625c to interface and/or interact with each of a first SAS 640a, a second SAS 640b, and a third SAS 640c. For example, one of the first API 625a, second API 625b, or third API 625c may allow the transaction processing system 620 to direct/request activation of a particular stored value account for a particular SAS with one of the first SAS 640a, the second SAS 640b, or the third SAS 640c.

[0052] In some embodiments, the SASs 640a, 640b, 640c may be configured for communication with one or more information datastores, e.g., datastore 645. Datastore 645 may contain separate sub-datastores 645a and 645b. In an embodiment, separate sub-datastores 645a and 645b may individually or collectively include an entry for each of the stored value accounts offered for sale the retailer 601 or multiple retailers. In an embodiment, stored value account information used to verify activation request/information may be stored in a stored value account information database, e.g., datastore 645a. Activation requestor information may be stored in a requestor information database, e.g., datastore 645b. [0053] All of, or a portion of, the system 600 described above may be implemented on any particular machine, or machines, with sufficient processing power, memory resources, and throughput capability to handle the necessary workload placed upon the computer, or computers. Figure 7 illustrates a computer system 780 suitable for implementing all, or a portion of, one or more embodiments disclosed herein. The computer system 780 includes a processor 782 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 784, read only memory (ROM) 786, random access memory (RAM) 788, input/output (I/O) devices 790, and network connectivity devices 792. The processor 782 may be implemented as one or more CPU chips.

[0054] It is understood that by programming and/or loading executable instructions onto the computer system 780, at least one of the CPU 782, the RAM 788, and the ROM 786 are changed, transforming the computer system 780 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well- known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.

[0055] The secondary storage 784 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 788 is not large enough to hold all working data. Secondary storage 784 may be used to store programs which are loaded into RAM 788 when such programs are selected for execution. The ROM 786 is used to store instructions and perhaps data which are read during program execution. ROM 786 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 784. The RAM 788 is used to store volatile data and perhaps to store instructions. Access to both ROM 786 and RAM 788 is typically faster than to secondary storage 784. The secondary storage 784, the RAM 788, and/or the ROM 786 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.

[0056] I/O devices 790 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.

[0057] The network connectivity devices 792 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 792 may enable the processor 782 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 782 might receive information from the network or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 782, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.

[0058] Such information, which may include data or instructions to be executed using processor 782 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.

[0059] The processor 782 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk-based systems may all be considered secondary storage 784), ROM 786, RAM 788, or the network connectivity devices 792. While only one processor 782 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 784, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 786, and/or the RAM 788 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.

[0060] In an embodiment, the computer system 780 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to peimit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 780 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 780. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third-party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third-party provider.

[0061] In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 780, at least portions of the contents of the computer program product to the secondary storage 784, to the ROM 786, to the RAM 788, and/or to other non-volatile memory and volatile memory of the computer system 780. The processor 782 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 780. Alternatively, the processor 782 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 792. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 784, to the ROM 786, to the RAM 788, and/or to other non-volatile memory and volatile memory of the computer system 780.

[0062] In some contexts, the secondary storage 784, the ROM 786, and the RAM 788 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 788, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer 780 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 782 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media. [0063] Embodiments of the invention can be described with reference to the following numbered clauses:

[0064] 1. A method performed by a processor computer device having a processor and executable instructions stored on a non-transitory computer readable medium which, when executed by the processor, causes the processor computer device to perform the method, the method comprising: receiving a purchase verification for a form of electronic stored value account; verifying purchaser information related to the purchaser of the electronic stored value account; delivering a secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser information; verifying recipient information related to the recipient subsequent to, and in response to, accessing of the secure link by the recipient; and delivering the electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient information.

[0065] 2. The method of clause 1, further comprising: verifying redeemer information of a user redeeming the electronic stored value account at a time of redemption of the electronic stored value account; and permitting redemption of the electronic stored value account subsequent to, and in response to, verifying the redeemer information.

[0066] 3. The method of clause 2, wherein verifying a recipient’s entitlement to the electronic stored value account includes determining a negative correlation between a location of redemption of the electronic stored value account, initial access to the stored value account, and a location of purchase of the electronic stored value account.

[0067] 4. The method of clause 2, wherein a subsequent verification is performed for certain stored value products issued by the processor using a location of usage, a timing of use, and retailer information where a stored value is liquidated.

[0068] 5. The method of clause 2, wherein a verification is performed for certain stored value products issued by the processor requiring user registration for the stored value using a location of registration, a timing of registration, and registered user information to which the stored value is registered. [0069] 6. The method of any one of clauses 3-5, further comprising suspending entitlement to the electronic stored value account using risk and timing factors between a location of redemption, use, or registration and purchase of the electronic stored value account using human determined thresholds, rules and machine learning models.

[0070] 7. The method of clause 1, wherein: the purchaser information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the purchaser; and the recipient information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the recipient. [0071] 8. The method of clause 1, wherein verifying the purchaser or recipient or a registered user’s entitlement includes determining whether any of the data elements of the aforesaid participants, the devices and/or transaction characteristics arc on a system or human determined fraud watch list.

[0072] 9. The method of clause 1 , wherein verifying the purchaser or recipient or a registered user’s entitlement includes validation of usage limits including, but not limited to a number of electronic stored value accounts purchased, used, accessed, or registered by the participants within a human or system determined window of time.

[0073] 10. The method of clause 8, wherein the value associated with the secure link is suspended if the number of electronic stored value accounts used by the participant in a predetermined time exceeds a human or system determined threshold.

[0074] 11. The method of clause 1, wherein entitlement to the use of electronic stored value is suspended if the purchaser, recipient, or registered user information cannot be verified.

[0075] 12. The method of clause 1, wherein delivery or entitlement to value account secure link is suspended if the recipient information could not be verified.

[0076] 13. The method of clause 1, wherein the purchaser information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points. [0077] 14. The method of clause 1, wherein the purchaser or recipient or registered users current signature of use, as determined by typical access patterns and gestures when using the system for purchase, use, or registration, matches a known prior signature of use.

[0078] 15. The method of either clause 13 or 14 wherein the first data point includes a name of the purchaser and the second data point includes an email address of the purchaser.

[0079] 16. The method of clause 1, wherein the recipient information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

[0080] 17. The method of clause 16, wherein the first data point includes a name of the recipient and the second data point includes an email address of the recipient.

[0081] 18. The method of either clause 1 or 14, wherein the recipient information is the same as the purchaser information.

[0082] 19. The method of clause 18, wherein verifying the recipient information includes determining whether the recipient information matches the purchaser information and signature of use.

[0083] 20. The method of clause 19, wherein verifying the recipient information includes determining whether an email address of the recipient matches an email address of the purchaser.

[0084] 21. A stored value account processing system having a processor and a non- transitory computer readable medium having executable instructions stored thereon which, when executed by the processor, causes the processor to: receive a purchase verification for an electronic stored value account; verify purchaser information related to the purchaser of the electronic stored value account; deliver an secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser and transaction information; verify recipient information related to the recipient subsequent to, and in response to, registration required for accessing stored value or activation of the secure link by the recipient; and granting access to electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient or registered user’s information.

[0085] 22. The system of clause 21, wherein the processor is further configured to: verify redeemer information of a user redeeming the electronic stored value account at a time of redemption of the electronic stored value account; and permit redemption of the electronic stored value account subsequent to, and in response to, verifying the redeemer information.

[0086] 23. The system of clause 22, wherein the processor is further configured to verify a recipient’s entitlement by determining a negative correlation between a location of redemption of the electronic stored value account, initial access to the stored value account, and a location of purchase of the electronic stored value account.

[0087] 24. The system of clause 22, wherein a subsequent verification is performed for certain stored value products issued by the processor using a location of usage, a timing of use, and retailer information where a stored value is liquidated.

[0088] 25. The system of clause 22, wherein a verification is performed for certain stored value products issued by the processor requiring user registration for the stored value using the location of registration, timing of registration, and registered user information to which the stored value is registered.

[0089] 26. The system of any one of clauses 23-25, wherein the processor is further configured to suspend entitlement to the electronic stored value account using risk and timing factors between a location of redemption, use, or registration and purchase of the electronic stored value account using human determined thresholds, rules and machine learning models.

[0090] 27. The system of clause 21, wherein: the purchaser information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the purchaser; and the recipient information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the recipient. [0091] 28. The system of clause 21, wherein the processor is further configured to verify the purchaser, recipient or registered user’s entitlement by determining whether any of the data elements of the aforesaid participants, the devices and/or transaction characteristics are on a system or human determined fraud watch list.

[0092] 29. The system of clause 21, wherein the processor is further configured to verify the purchaser, recipient or registered user’s entitlement by validation of usage limits including, but not limited to number of electronic stored value accounts purchased, used, accessed, or registered by the participants within a human or system determined window of time.

[0093] 30. The system of clause 28, wherein the value associated with the secure link is suspended if the number of electronic stored value accounts used by the participant in a predetermined time exceeds a human or system determined threshold.

[0094] 31. The system of clause 21, wherein entitlement to the use of electronic stored value is suspended if the purchaser, recipient, or registered user information cannot be verified.

[0095] 32. The system of clause 21 , wherein delivery or entitlement to value account secure link is suspended if the recipient information could not be verified.

[0096] 33. The system of clause 21, wherein the purchaser information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

[0097] 34. The system of clause 21, wherein the purchaser or recipient or registered users current signature of use, as determined by typical access patterns, and gestures when using the system for purchase, use, or registration, matches known prior signature of use.

[0098] 35. The system of either clause 33 or 34 wherein the first data point includes a name of the purchaser and the second data point includes an email address of the purchaser.

[0099] 36. The system of clause 21, wherein the recipient information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

[00100] 37. The system of clause 36, wherein the first data point includes a name of the recipient and the second data point includes an email address of the recipient.

[00101] 38. The system of either clause 21 or 34, wherein the recipient information is the same as the purchaser information. [00102] 39. The system of clause 38, wherein the processor is further configured to verify the recipient information by determining whether the recipient information matches the purchaser information and signature of use.

[00103] 40. The system of clause 39, wherein the processor is further configured to verify the recipient information by determining whether an email address of the recipient matches an email address of the purchaser.

[00104] The ordering of steps in the various processes, data flows, and flowcharts presented are for illustration purposes and do not necessarily reflect the order that various steps must be performed. The steps may be rearranged in different orders in different embodiments to reflect the needs, desires and preferences of the entity implementing the systems. Furthermore, many steps may be performed simultaneously with other steps in some embodiments.

[00105] Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be coupled through some interface or device, such that the items may no longer be considered directly coupled to each other but may still be indirectly coupled and in communication, whether electrically, mechanically, or otherwise with one another. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the ait and could be made without departing from the spirit and scope disclosed. The following numbered entries represent a non-exhaustive collection of exemplary embodiments of the instantly disclosed subject matter.

[00106] It should be understood that only selected embodiments have been shown and described and that all possible alternatives, modifications, aspects, combinations, principles, variations, and equivalents that come within the spirit of the disclosure as defined herein or by any of the following claims are desired to be protected. While embodiments of the disclosure have been illustrated and described in detail in the drawings and foregoing description, the same are to be considered as illustrative and not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Additional alternatives, modifications and variations can be apparent to those skilled in the art. Also, while multiple inventive aspects and principles have been presented, they need not be utilized in combination, and many combinations of aspects and principles are possible in light of the various embodiments provided above. [00107] Any theory, mechanism of operation proof, or finding stated herein is meant to further enhance understanding of principles of the present disclosure and is not intended to make the present disclosure in any way dependent upon such theory, mechanism of operation, illustrative embodiment, proof, or finding. It should be understood that while the use of the word preferable, preferably or preferred in the description above indicates that the feature so described can be more desirable, it nonetheless cannot be necessary and embodiments lacking the same can be contemplated as within the scope of the disclosure, that scope being defined by the claims that follow.

[00108] In reading the claims it is intended that when words such as “a,” “an,” “at least one,” “at least a portion” are used there is no intention to limit the claim to only one item unless specifically stated to the contrary in the claim. When the language “at least a portion” and/or “a portion” is used, the item can include a portion and/or the entire item unless specifically stated to the contrary. It should be understood that only selected embodiments have been shown and described and that all possible alternatives, modifications, aspects, combinations, principles, variations, and equivalents that come within the spirit of the disclosure as defined herein or by any of the following claims are desired to be protected. While embodiments of the disclosure have been illustrated and described in detail in the drawings and foregoing description, the same are to be considered as illustrative and not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Additional alternatives, modifications and variations can be apparent to those skilled in the art. Also, while multiple inventive aspects and principles have been presented, they need not be utilized in combination, and many combinations of aspects and principles are possible in light of the various embodiments provided above.

Claims

CLAIMS:

1. A method performed by a processor computer device having a processor and executable instructions stored on a non-transitory computer readable medium which, when executed by the processor, causes the processor computer device to perform the method, the method comprising: receiving a purchase verification for a form of electronic stored value account; verifying purchaser information related to the purchaser of the electronic stored value account; delivering a secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser information; verifying recipient information related to the recipient subsequent to, and in response to, accessing of the secure link by the recipient; and delivering the electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient information.

2. The method of claim 1, further comprising: verifying redeemer information of a user redeeming the electronic stored value account at a time of redemption of the electronic stored value account; and peimitting redemption of the electronic stored value account subsequent to, and in response to, verifying the redeemer information.

3. The method of claim 2, wherein verifying a recipient’s entitlement to the electronic stored value account includes determining a negative correlation between a location of redemption of the electronic stored value account, initial access to the stored value account, and a location of purchase of the electronic stored value account.

4. The method of claim 2, wherein a subsequent verification is performed for certain stored value products issued by the processor using a location of usage, a timing of use, and retailer information where a stored value is liquidated.

5. The method of claim 2, wherein a verification is performed for certain stored value products issued by the processor requiring user registration for the stored value using a location of registration, a timing of registration, and registered user information to which the stored value is registered.

6. The method of any one of claims 3-5, further comprising suspending entitlement to the electronic stored value account using risk and timing factors between a location of redemption, use, or registration and purchase of the electronic stored value account using human determined thresholds, rules and machine learning models.

7. The method of claim 1, wherein: the purchaser information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the purchaser; and the recipient information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the recipient.

8. The method of claim 1, wherein verifying the purchaser or recipient or a registered user’s entitlement includes determining whether any of the data elements of the aforesaid participants, the devices and/or transaction characteristics are on a system or human determined fraud watch list.

9. The method of claim 1, wherein verifying the purchaser or recipient or a registered user’s entitlement includes validation of usage limits including, but not limited to a number of electronic stored value accounts purchased, used, accessed, or registered by the participants within a human or system determined window of time.

10. The method of claim 8, wherein the value associated with the secure link is suspended if the number of electronic stored value accounts used by the participant in a predetermined time exceeds a human or system determined threshold.

11. The method of claim 1, wherein entitlement to the use of electronic stored value is suspended if the purchaser, recipient, or registered user information cannot be verified.

12. The method of claim 1 , wherein delivery or entitlement to value account secure link is suspended if the recipient information could not be verified.

13. The method of claim 1, wherein the purchaser information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

14. The method of claim 1, wherein the purchaser or recipient or registered users current signature of use, as determined by typical access patterns and gestures when using the system for purchase, use, or registration, matches a known prior signature of use.

15. The method of either claim 13 or 14 wherein the first data point includes a name of the purchaser and the second data point includes an email address of the purchaser.

16. The method of claim 1, wherein the recipient information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

17. The method of claim 16, wherein the first data point includes a name of the recipient and the second data point includes an email address of the recipient.

18. The method of either claim 1 or 14, wherein the recipient information is the same as the purchaser information.

19. The method of claim 18, wherein verifying the recipient information includes determining whether the recipient information matches the purchaser information and signature of use.

20. The method of claim 19, wherein verifying the recipient information includes determining whether an email address of the recipient matches an email address of the purchaser.

21. A stored value account processing system having a processor and a non-transitory computer readable medium having executable instructions stored thereon which, when executed by the processor, causes the processor to: receive a purchase verification for an electronic stored value account; verify purchaser information related to the purchaser of the electronic stored value account; deliver an secure link to a recipient of the electronic stored value account subsequent to, and in response to, verification of the purchaser and transaction information; verify recipient information related to the recipient subsequent to, and in response to, registration required for accessing stored value or activation of the secure link by the recipient; and granting access to electronic stored value account to the recipient subsequent to, and in response to, verification of the recipient or registered user’s information.

22. The system of claim 21, wherein the processor is further configured to: verify redeemer information of a user redeeming the electronic stored value account at a time of redemption of the electronic stored value account; and permit redemption of the electronic stored value account subsequent to, and in response to, verifying the redeemer information.

23. The system of claim 22, wherein the processor is further configured to verify a recipient’s entitlement by determining a negative correlation between a location of redemption of the electronic stored value account, initial access to the stored value account, and a location of purchase of the electronic stored value account.

24. The system of claim 22, wherein a subsequent verification is performed for certain stored value products issued by the processor using a location of usage, a timing of use, and retailer information where a stored value is liquidated.

25. The system of claim 22, wherein a verification is performed for certain stored value products issued by the processor requiring user registration for the stored value using the location of registration, timing of registration, and registered user information to which the stored value is registered.

26. The system of any one of claims 23-25, wherein the processor is further configured to suspend entitlement to the electronic stored value account using risk and timing factors between a location of redemption, use, or registration and purchase of the electronic stored value account using human determined thresholds, rules and machine learning models.

27. The system of claim 21, wherein: the purchaser information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the purchaser; and the recipient information includes at least one data element such as, but not limited to email address, a name, an IP address, a phone number, and a physical address of the recipient.

28. The system of claim 21, wherein the processor is further configured to verify the purchaser, recipient or registered user’s entitlement by determining whether any of the data elements of the aforesaid participants, the devices and/or transaction characteristics are on a system or human determined fraud watch list.

29. The system of claim 21, wherein the processor is further configured to verify the purchaser, recipient or registered user’ s entitlement by validation of usage limits including, but not limited to number of electronic stored value accounts purchased, used, accessed, or registered by the participants within a human or system determined window of time.

30. The system of claim 28, wherein the value associated with the secure link is suspended if the number of electronic stored value accounts used by the participant in a predetermined time exceeds a human or system determined threshold.

31. The system of claim 21 , wherein entitlement to the use of electronic stored value is suspended if the purchaser, recipient, or registered user information cannot be verified.

32. The system of claim 21, wherein delivery or entitlement to value account secure link is suspended if the recipient information could not be verified.

33. The system of claim 21, wherein the purchaser information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

34. The system of claim 21, wherein the purchaser or recipient or registered users current signature of use, as determined by typical access patterns, and gestures when using the system for purchase, use, or registration, matches known prior signature of use.

35. The system of either claim 33 or 34 wherein the first data point includes a name of the purchaser and the second data point includes an email address of the purchaser.

36. The system of claim 21, wherein the recipient information includes a plurality of data points, and verifying the purchaser information includes determining whether a first data point of the plurality of data points corresponds to a second data point of the plurality of data points.

37. The system of claim 36, wherein the first data point includes a name of the recipient and the second data point includes an email address of the recipient.

38. The system of either claim 21 or 34, wherein the recipient information is the same as the purchaser information.

39. The system of claim 38, wherein the processor is further configured to verify the recipient information by determining whether the recipient information matches the purchaser information and signature of use.

40. The system of claim 39, wherein the processor is further configured to verify the recipient information by determining whether an email address of the recipient matches an email address of the purchaser.