System and method for using intelligent codes to add a stored-value card to an electronic wallet

This application is a continuation of U.S. patent application Ser. No. 17/328,268, filed May 24, 2021, which is a continuation of U.S. application Ser. No. 13/857,048, filed Apr. 4, 2013, which claims priority to U.S. Provisional Application No. 61/620,173, filed on Apr. 4, 2012, and to U.S. Provisional Application No. 61/800,704, filed on Mar. 15, 2013, each of which is incorporated by reference herein in its entirety.

This application is related to U.S. patent application Ser. No. 13/483,711 filed on May 30, 2012 which claims priority to: U.S. Provisional Patent Application Ser. Nos. 61/491,791 and 61/491,813, both filed on May 31, 2011 and entitled “A System for Payment via Electronic Wallet;” U.S. Provisional Patent Application Ser. Nos. 61/496,397 and 61/496,404, both filed on Jun. 13, 2011 and entitled “System, Method, and Apparatus for Creating and Distributing a Transaction Credit;” Ser. No. 13/483,711 filed on May 30, 2012 is a continuation-in-part of International Application Serial No. PCT/US11/40055, filed Jun. 10, 2011 and entitled, “Efficient Stored-Value Card Transactions” which claims priority to U.S. Provisional Patent Application Ser. Nos. 61/354,469 and 61/354,470 both filed on Jun. 14, 2010, and 61/360,327 filed on Jun. 30, 2010; Ser. No. 13/483,711 filed on May 30, 2012 is a continuation-in-part of International Application Serial No. PCT/US11/20570, filed on Jan. 7, 2011 and entitled “A System for Processing, Activating and Redeeming Value Added Prepaid Cards,” which claims priority to U.S. Provisional Patent Application Ser. No. 61/293,413, filed on Jan. 8, 2010; this application is a continuation-in-part of International Application Serial No. PCT/US11/49338, filed on Aug. 26, 2011 and entitled “Prepaid Card with Savings Feature,” which claims priority to U.S. Provisional Patent Application Ser. No. 61/377,800, filed on Aug. 27, 2010 each of which is incorporated by reference herein in its entirety.

This application also incorporates by reference the entirety of the disclosure, the subject matter, and concepts of: International Application Serial No. PCT/US13/26501, filed on Feb. 15, 2013, and entitled “System and Method of Registering Stored-Value Cards Into Electronic Wallets”; U.S. patent application Ser. No. 12/538,083, filed Aug. 7, 2009, and entitled “Transaction Processing Platform for Facilitating Electronic Distribution of Plural Prepaid Services” which is a continuation of U.S. patent application Ser. No. 12/338,854, filed Dec. 18, 2008, which is a continuation of U.S. patent application Ser. No. 11/851,337, filed Sep. 6, 2007 (now U.S. Pat. No. 7,477,731), which is a continuation of U.S. patent application Ser. No. 11/007,662, filed Dec. 7, 2004 (now U.S. Pat. No. 7,280,644); U.S. patent application Ser. No. 13/040,074 filed Mar. 3, 2011 and entitled “System and Method for Electronic Prepaid Account Replenishment;” U.S. patent application Ser. No. 10/821,815, filed Apr. 9, 2004 and entitled “System and Method for Distributing Person Identification Numbers Over a Computer Network;” U.S. patent application Ser. No. 12/786,403, filed May 24, 2010, and entitled “System and Method for Distributing Person Identification Numbers Over a Computer Network;” U.S. patent application Ser. No. 12/711,211, filed Feb. 23, 2010, and entitled “System and Method for Distributing Person Identification Numbers Over a Computer Network;” and U.S. patent application Ser. No. 12/719,741, filed Mar. 8, 2010, and entitled “Systems and Methods for Personal Identification Number Distribution and Delivery.”

Not applicable.

Not applicable.

The disclosure generally relates to the use of electronic stored-value cards in electronic transactions.

The electronic transaction market is currently filled with many types of credit cards, debit cards, stored value cards, and loyalty cards, all of which may be offered by different issuers, vendors, and providers. Some of the cards are tailored to be redeemed from a retailer while others may be redeemed by financial institutions. Other cards have promotions attached to them, e.g., loyalty cards. However, the increasing quantity and complexity of the cards makes organization and redemption increasingly difficult, thus potentially hindering the growth of the market. For example, a user may not know or remember that the user has a stored value card for a specific store during a purchase at that store because the user has too many stored value cards. Also, a user may not understand the various types of promotions available to him using a card in combination with a loyalty card, and as such, may not benefit from promotions applicable to the user's purchase. Historically, cards have been embodied in a tangible medium such as plastic, and thus are susceptible to loss, theft, or simply being left at home when needed. With the continued growth in card-based transactional offerings provided to consumers, many consumers are faced with the burdensome task of organizing, managing, tracking, transporting, and storing all of their credit, debit, stored-value, loyalty, and other types of merchant, vendor, and provider issued cards. What today's consumers need is a more efficient, secure, and effective way of accessing and using their card-related assets.

In one aspect, disclosed is a computer implemented method comprising receiving a request to add a stored-value card to an electronic wallet, wherein the request is facilitated by interpreting an intelligent code, wherein the intelligent code directs a user to a URL for an electronic wallet website; prompting a user for credentials to enter the electronic wallet website; determining whether the stored-value card already exists in the electronic wallet; and adding the stored-value card to the electronic wallet.

In another aspect, disclosed is a system comprising a computer device to receive a request to add a stored-value card to an electronic wallet, wherein the request is facilitated by interpreting an intelligent code, wherein the intelligent code directs a user to a URL for an electronic wallet website; to prompt a user for credentials to enter the electronic wallet website, to determine possession of the stored-value card, to determine whether the stored-value card already exists in the electronic wallet, and to add the stored-value card to the electronic wallet.

Disclosed herein are systems and methods for adding stored-value cards (hereinafter “SVC” or “SVCs”), such as physical stored-value cards (hereinafter “pSVC” or “pSVCs”) and electronic stored-value cards (hereinafter “eSVC” or “eSVCs”) to an electronic wallet (also referred to herein as “e-wallet”). Particularly, the systems and methods disclosed herein may add a SVC in response to a user request to add a SVC to a user's electronic wallet (hereinafter “Add Request”), which the request is made via an intelligent code. The systems and methods disclosed herein additionally may provide an eSVC in response to a user request for an eSVC (hereinafter “eSVC Request”), e.g., a request for an eSVC to be generated in order to add a pSVC or eSVC to the user's e-wallet. Additionally, the disclosed systems and methods may provide use of value tokens in the electronic wallet(s) for electronic transactions.

Acquisition and/or purchase of a stored-value card (e.g., a pSVC or an eSVC) may involve an account vendor, a redeeming merchant, a processor, and an account issuer. In various embodiments, the account vendor, redeeming merchant, processor, and account issuer may be the same, different, or related entities. The point of sale where the SVC is purchased and/or acquired is referred to herein as the account vendor or simply vendor. An entity that will accept value contained in the SVC for business transactions, for example, as tender for a purchase, is referred to as a redeeming merchant. An entity that provides the financial backing and/or payment processing accessed via use of the stored-value card is referred to as the account issuer, or simply, issuer. Account issuers may include direct issuers of SVCs such as store-branded cards (e.g., Macy's, Target), and in some embodiments the account vendor may also be the account issuer and/or the redeeming merchant. Account issuers also may include banks, financial institutions, and processors such as VISA, Mastercard, American Express, etc., and stored-value cards issued by such institutions may be readily accepted by a number of redeeming merchants to conduct transactions such as purchases. Account issuers may be in various industries, such as the entertainment, health, medical, pharmaceutical industries. For example, the account issuer may be a pharmaceutical company utilizing promotional physical and/or electronic stored-value cards for pharmaceutical products. An entity that provides payment processing for an SVC is referred to as the processor. In some instances, a SVC may be sold and/or issued at the same or different account vendor (e.g., account vendor is Store X or a different or unrelated Store Z). In such instances, the Store X branded stored-value card may be issued by Store X, by Store Z, or by a third party such as bank or financial institution.

As used herein, “electronic-stored value card” or “eSVC” refers to an electronic embodiment of an account that may be used to transact business with a merchant willing to accept a value (e.g., points, miles, dollars, or any other measure of value such as a value token described hereinbelow), for example as tender for a purchase or discount for a purchase. As used herein, “electronic stored-value card” or “eSVC” may additionally or alternatively refer to an electronic embodiment of an account used for promotional and/or marketing purposes. The accounts may comprise credit accounts, debit accounts, gift accounts, telephone accounts, loyalty accounts, membership accounts, ticket accounts, entertainment accounts, sports accounts, prepaid accounts, discount accounts, healthcare accounts, the like, or combinations thereof. Such accounts may be associated with corresponding physical cards, including credit cards, debit cards, gift cards, telephone cards, loyalty cards, membership cards, ticket cards, entertainment cards, sports cards, prepaid cards, discount cards, healthcare cards, the like, or combinations thereof. Such accounts may additionally or alternatively comprise electronic accounts, such as electronic credit accounts, electronic debit accounts, electronic gift accounts, electronic telephone accounts, electronic loyalty accounts, electronic membership accounts, electronic ticket accounts, electronic entertainment accounts, electronic sports accounts, electronic prepaid accounts, electronic discount accounts, electronic healthcare accounts, the like, or combinations thereof. In embodiments, the value of an electronic stored-value card may be embodied as an “electronic value token” or “value token,” both of which are described in detail hereinbelow.

As use herein, “physical card” refers to a pSVC or to a card which has no stored value (e.g., a chit as described herein below) but which bears an SVC identifier as disclosed herein. A pSVC may comprise a known form of stored-value cards often referred to as a credit card, a debit card, a gift-card, a loyalty card, a rewards card, a membership card, a discount card, a promotional card, etc. In the embodiments disclosed herein, pSVCs may be converted to eSVCs by first interpreting the intelligent code of the pSVC to request an eSVC (discussed herein below) and/or to request the pSVC (after conversion to an eSVC) be added to an electronic wallet.

As used herein, “intelligent code” may refer to a barcode; a QR code; an arrangement of numerals, letters, symbols, images, and/or colors; an electromagnetic signal (e.g., near field communication (“NFC”), infrared, RFID); a mechanical wave (e.g., sound); or combinations thereof. In an embodiment, the intelligent code may be affixed (permanently (e.g., the intelligent code may be printed on a pSVC (or other physical structure)) or non-permanently (e.g., the intelligent code may be printed on a removable “sticker” which is placed on a pSVC (or other physical structure))) to a pSVC, a pSVC carrier (e.g., card package, display sleeve, etc.), a chit, an advertisement, a flyer, or other physical structure. In an embodiment, an intelligent code may be interpreted, scanned, input, and/or read (“scan” may be used to reference any of the foregoing) by a user's device via voice recognition, camera manipulation, physical gesture (e.g., finger swipe), NFC communication, Bluetooth communication, or other known methods for engaging a user's device for information reception. Information contained in the intelligent code may be conveyed, transmitted, delivered, or otherwise communicated to an electronic wallet provider, an eSVC provider and/or distribution system, or both, via phone line, cellular communication, Wi-Fi communication, Bluetooth communication, radio communication, USB, MiniPin, email, webpage interaction, internet communication, VoIP, short message service (“SMS”), Instant messaging, infrared communication, Android Beam, or other methods of communication known to those of skill in the art.

Card product retailers often carry displays having many packaged-physical card products from a variety of brands. Such displays may be referred to as “endcaps.” As such, a consumer or customer of the retailer may purchase a variety of physical card products. A consumer or customer may need to purchase multiple card products at in a single transaction, giving rise to a problem of managing the multiple card products. Additionally, when a retailer sells packaged-physical card products, e.g., via an endcap, the supply of products is subject to going “out of stock,” giving rise to lost sales. Moreover, manufacturing and distribution costs are associated with packaged-physical card products. The disclosed methods and systems allow for a customer or consumer to purchase card products without the hassle of managing physical cards and/or packages. Additionally, the disclosed methods and systems allow for the sale of eSVCs in place of, or in combination with, physical cards, reducing and/or eliminating costs associated with the manufacture and distribution of physical card products.

shows a flowchart of an embodiment of a method for adding a SVC to an electronic wallet via interpretation of an intelligent code. The various steps of the method shown inmay be omitted, substituted, and rearranged except where specified hereinbelow.

The method instarts at block. At block, a request to add a SVC to an electronic wallet is received (e.g., by an electronic wallet provider). To facilitate (e.g., make) the request to add the SVC to the user's e-wallet (“Add Request”), the user may interpret an intelligent code with a user device. In embodiments, “interpret” may comprise scan, read, record, sense by electrical signal, sense by mechanical signal, sense by acoustic signal, sense by visual signal, or combinations thereof. For example, a user may scan a QR code with a user's mobile device. Information contained in the intelligent code may direct the user to an electronic wallet website and/or provide stored-value card information (hereinafter “SVC information”) to an electronic wallet provider. For example, by interpreting (e.g., scanning) an intelligent code comprising a barcode or QR code, the user may be directed to an electronic wallet website (and/or an app) according to technology known for directing users to a website (and/or app) via a scan of such codes. The intelligent code (e.g., embodied as a barcode, QR code, etc.), in addition to providing a traditional URL to the user, may additionally provide stored-value card information (e.g., within the URL) to another entity, e.g., an electronic wallet provider. The SVC information may comprise a globally unique identifier for the SVC, redemption information for the SVC, a retailer identifier (e.g., store ID), a card number for the SVC, a PIN for the SVC, or combinations thereof. A PIN and/or globally unique identifier may both be referred to herein as a “security key.” In an embodiment, the intelligent code does not provide information which can be used to redeem, activate, reload, or use the SVC. In embodiments, the Add Request may be received when a user visits the URL containing the information provided by the intelligent code, when an entity (e.g., the electronic wallet provider) receives the SVC information, or both.

In embodiments where the intelligent code provides a globally unique identifier for the SVC, the globally unique identifier may be assigned to the SVC by the SVC issuer, which maintains a database of SVC information for SVCs which the issuer has issued. The globally unique identifier may also be assigned by a non-issuing entity which receives the SVC information from the issuer in exchange for generation of an intelligent code containing a globally unique identifier by the non-issuing entity, which can be printed on the SVC, for example, by the SVC issuer. Thus, a globally unique identifier for an SVC may be contained in the intelligent code in addition or in the alternative to SVC information (e.g., redemption information, a retailer identifier (e.g., store ID), a card number, a PIN for the SVC, or combinations thereof). In such embodiments, the globally unique identifier is used to “look up” SVC information (e.g., redemption information, a retailer identifier (e.g., store ID), a card number, a PIN for the SVC, or combinations thereof) once an Add Request is received.

An Add Request for multiple SVCs (e.g., a SVC for a restaurant and a SVC for a movie theater) may be made with a single interpretation of an intelligent code (e.g., a scan of a QR code). For example, an Add Request may result from the scan of an intelligent code by a user for a “Dinner and a Movie” intelligent code (hereinafter a “combo code”), wherein the combo code comprises the combination of different SVCs (i.e., the combo code represents both a request to add the restaurant SVC and a request to add the movie theater SVC to an e-wallet), and the result of the Add Request via a combo code scan is the addition of two separate SVCs to the user's e-wallet. In embodiments, an Add Request from a combo code may deliver one of the SVCs to the user and one of the SVCs to a third-party recipient, or may deliver the SVCs to the same or different third-party recipients.

A customer or consumer of card products (also referred to herein as a “user” in the disclosed embodiments) may generally make the Add Request at a physical retail (e.g., merchant) location, at a virtual location (e.g., an online merchant portal), via a user device (e.g., user deviceof), or combinations thereof. A physical retail location or online merchant portal may have a physical or virtual “endcap” which is a display for the intelligent codes for various brands and/or values of SVCs (eSVCs or pSVCs) or combinations of SVCs (eSVCs and pSVCs). In embodiments, a physical retail location may comprise both a physical endcap and a virtual endcap. A user may scan one or more intelligent codes (e.g., with a user device such as a mobile phone) at an endcap to make the request to add a SVC to the user's electronic wallet.

In embodiments, physical card products are not needed because purchase of the eSVC is initiated with a scan (e.g., by a user's device) of an intelligent code of a desired eSVC (e.g., at the virtual or physical endcap). In other embodiments, physical card products bearing one or more intelligent codes can be used at a physical endcap either alone or in combination with intelligent codes for eSVCs displayed on the endcap. In other embodiments, a virtual endcap may be employed for the sale and or delivery of eSVCs as well as pSVCs, such as to promote the sale of physical “multipacks,” e.g., a package which contains multiple physical cards to be purchased and activated, wherein the multiple cards may share a common issuer or may not share a common issuer. Embodiments of the endcap (virtual or physical display) which use no physical cards in order to sell eSVCs require no distribution or manufacture of physical card products. However, embodiments disclosed herein contemplate an intelligent code may be located on the front or back of a physical cards such as a pSVC or chit (chits are discussed below for).

At block, a user is prompted for credentials to add a SVC to the user's electronic wallet. The user is prompted for credentials after being directed to a URL provided by the intelligent code. Credentials may comprise security information such as a username and/or password. If the user is unable to enter valid credentials, the SVC cannot be added to the user's e-wallet (e.g., because the user has not established an e-wallet with the e-wallet provider). The user may then be prompted to create an e-wallet in which to add the SVC, e.g., by establishing a new e-wallet account with the e-wallet provider. If the user successfully enters credentials, the user is passed into the e-wallet website. Flow may then proceed to decision block; to any combination of blocks,, and; or to decision block.

Embodiments of the disclosed method may flow to decision block. At decision block, possession of the SVC is determined. In an embodiment, possession may be determined by requesting a security key for the SVC. In embodiments, the security key may comprise a PIN (personal identification number) for the SVC or a globally unique identifier (described above). The security key for the SVC may be printed on a pSVC (e.g., in the form of a scratch PIN), may be presented on a user device (e.g., in the form of a virtual security key for a pSVC or eSVC), may be printed on a physical card which is not a pSVC (e.g., on a chit in the form of a PIN, scratch PIN, or globally unique identifier for a eSVC or pSVC), or combinations thereof. In embodiments, the electronic wallet provider may request the security key from a user which scans the intelligent code and is directed to the electronic wallet provider's website. The user may view the PIN on the pSVC or chit in a retail location (e.g., at an endcap) and enter the PIN using a user device, for example, after the user is prompted for credentials (and enters an e-wallet website) as discussed for block. The e-wallet provider may receive the entered security key (e.g., entered PIN or entered globally unique identifier) and determine if the entered security key (e.g., entered PIN or entered globally unique identifier) is valid. In embodiments, determining if the entered security key is valid may comprise determining whether the received-entered security key (e.g., received-entered PIN or received-entered globally unique identifier) matches the security key (e.g., PIN or globally unique identifier) provided by the intelligent code (e.g., to the e-wallet provider). If the received-entered security key matches the security key provided by the intelligent code, possession of the SVC may be determined to be ‘YES’. Flow may then proceed to decision blockor to any of blocksto. If the received-entered security key does not match the security key provided by the intelligent code, possession of the SVC may be determined to be ‘NO’, flow stops, and the SVC may not be added to an e-wallet in embodiments which require determining possession as discussed hereinabove. In additional or alternative embodiments, determining possession of the SVC at blockmay be performed before the user is prompted for credentials as discussed for block.

shows blocks,, andcontained in areadefined by dashed lines. The dashed lines of areaindicate embodiments of the method may flow to one or any combination of blocks,, and. For example, flow from blocksormay continue to any block or combination of blocks, i.e., block,,, or combinations thereof, contained in area.

In embodiments, flow may proceed to block(e.g., from blocks,,,, or). At block, a card number for the SVC is displayed. In embodiments, at least a portion of the card number for the SVC is displayed. For example, the last four digits of the card number may be displayed. The card number for the SVC may be displayed concurrently with the request for a security key made in decision blockor separately from the request for a security key.

In embodiments, flow may proceed to block(e.g., from blocks,,, or). At block, a balance for the SVC is displayed. For example, the balance may be displayed on a user device. The balance for the SVC may be displayed concurrently with the request for a security key made in decision block, separately from the request for a security key, concurrently with the display of the card number according to block, separately from the display of the card number, or combinations thereof. In embodiments, the balance is displayed as a currency value, a percentage of a discount or purchase or promotion, points value, rewards value, or combinations thereof.

At block, the user is prompted for a call to action. A call to action may comprise adding a value (e.g., value tokens, points, rewards, currency, discount, etc.) to the SVC, viewing available offers and/or coupons, viewing the e-wallet of the user, or combinations thereof. The prompt for call to action may be made concurrently with the request for a security key made in decision block, separately from the request for a security key, concurrently with the display of the card number according to block, separately from the display of the card number, concurrently with the display of the balance according to block, separately from the display of the card balance, or combinations thereof. The prompt for call to action may be made via the website (and/or app) of the e-wallet provider, and the prompt may provide links for the calls to action which a user may select. After selection of a call to action by the user, the user may follow the link for to accomplish the corresponding call to action.

At block, a determination is made for whether the SVC already exists in the e-wallet of the user. Some or all of the SVC information received in the Add Request may be compared with the SVC information for all eSVCs in the e-wallet. If any of the eSVCs in the e-wallet have SVC information which matches the SVC information of the SVC associated with the Add Request, then a determination that the SVC already exists in the e-wallet may be made, and the user may not be allowed to add the SVC to the user's e-wallet. In an embodiment, the user may be notified (e.g., via a user device) that the SVC was not added to the e-wallet because it already exists in the e-wallet. If none of the eSVC in the e-wallet have SVC information which matches the SVC information of the SVC associated with the Add Request, then a determination may be made that the SVC does not already exist in the e-wallet. Flow may then proceed to block; alternatively, to block.

Embodiments of the method contemplate that the activation of the SVC associated with the Add Request be confirmed. At block, activation of the SVC is confirmed. In embodiments, the activation is confirmed before the SVC is added to the e-wallet. Activation of the SVC may be confirmed according to methods recognized by one skilled in the art with the aid of this disclosure. For example, the e-wallet provider may retrieve activation information from a database containing such information. The database may be associated with a computer device of the e-wallet provider or associated with another entity (e.g., the SVC issuer, SVC processor, etc.). In alternative embodiments, a wait period may exist to confirm the SVC is activated because the SVC may not yet be purchased and/or activated. In such embodiments, activation may be confirmed by receipt of a purchase verification, for example, according to the methods described inhereinbelow. In additional or alternative embodiments, the e-wallet may comprise the eSVC shopping cart discussed forbelow, or vice-versa, and the e-wallet may experience pausing and unpausing during the wait period for confirming activation of the SVC while the steps for purchasing and activating the SVC according to the method embodiments ofare performed.

At block, a SVC is added to the e-wallet as an eSVC. As used herein, an “electronic wallet” (also referred to as “e-wallet”) may include an electronically maintained data file (e.g., maintained on a computer device of a provider of the electronic wallet) which may comprise pre-existing eSVCs, SVC information for each eSVC in the e-wallet, authentication information, rules for use, sub-wallets (e.g., for separately maintaining eSVC-related information), and electronic value tokens (e.g., electronic representations of the monetary and/or other value associated with the electronic stored-value card-related information contained in the e-wallet/sub-wallet). The eSVC processor may prompt the user (e.g., before or after activation of the eSVC) whether the user would like to create an electronic wallet and add the eSVC thereto, or whether the user has a pre-existing e-wallet and would like to add the eSVC thereto. The processor may add the activated eSVC to an e-wallet designated by the user upon instruction by the user, or automatically according to preferences in the e-wallet which may be recognized in embodiments where the use purchases the eSVC from the user's e-wallet provider or in another arrangement where the e-wallet provider may recognize the purchase of the eSVC which needs to be automatically added to the user's e-wallet.

In certain embodiments (e.g., as reflected in) a user may create an e-wallet, establish rules for the e-wallet, provision the e-wallet, and access the e-wallet to facilitate electronic transactions. Suitable processes for registering the eSVC are disclosed in International Application Serial No. PCT/US13/26501, filed on Feb. 15, 2013, and entitled “System and Method of Registering Stored-Value Cards Into Electronic Wallets.” Examples of techniques for authenticating, allocating, and provisioning an eSVC are described hereinbelow. Various registration, authentication, allocation, and provisioning techniques may be performed prior to use of the eSVC which would be recognized by one skilled in the art with the aid of this disclosure. For example, the user may register the eSVC in one or more electronic wallets (e.g., electronic walletof).

In embodiments, before the user obtains (e.g., receives, activates, redeems, or combinations thereof) the SVC, the SVC provider, the e-wallet provider, the SVC processor, the SVC issuer, the merchant, or combinations thereof may provide fraud mitigation. In an embodiment, providing fraud mitigation may comprise blocking access to an SVC before a user views the SVC as an eSVC, blocking access to an eSVC before a user activates the eSVC, or both. In an additional or alternative embodiment, providing fraud mitigation may comprise determining a digital fingerprint of a user device (e.g., user device), at the time a user attempts to view an eSVC to determine the risk associated with the user, the eSVC, or both. In an additional or alternative embodiment, providing fraud mitigation may comprise withholding the providing of the eSVC (e.g., withholding the delivery of redemption information for the eSVC). In an additional or alternative embodiment, providing fraud mitigation may comprise determining a geographic location of the eSVC and/or user and pausing the providing of the eSVC for a period of time determined by the geographic location. For example, the providing of the eSVC may be held for a longer period of time in geographic locations known or determined to be of high risk of fraud, and the providing of the eSVC may be held for a short period of time or for a period of time comprising zero in geographic locations known or determined to be of low or no risk of fraud.

show flowcharts of embodiments of methods for providing an eSVC via receipt of information contained in an intelligent code. The various steps of the methods may be omitted, substituted, and rearranged except where specified hereinbelow. In an embodiment, information contained in the intelligent code may provide a request for multiple eSVCs, e.g., an eSVC for a restaurant and eSVC for a movie theater. For example, a user Request may include an intelligent code that was scanned by a user which was offered as a “Dinner and a Movie” intelligent code (hereinafter a “combo code”), wherein the entity offering the intelligent code only offers the combination and does not offer the corresponding restaurant eSVC and movie theater eSVC as separately available items for purchase but the user receives the result of the requested combo code as two separate eSVCs. Moreover, the two separate eSVCs may be delivered to different recipients upon request. Moreover, the eSVCs may also be subject to the fraud mitigation capabilities described above.

The method instarts at block. At block, a request for an eSVC (hereinafter “eSVC Request”) is received. The eSVC Request may be associated with a request for a tutorial for obtaining the electronic stored-value card via an intelligent code. The eSVC Request may be conveyed (e.g., to an eSVC provider) via an interpretation of an intelligent code, a tutorial for obtaining the eSVC may be conveyed via an interpretation of an intelligent code, or both may be conveyed by the interpretation of one or more intelligent codes. In an embodiment, the eSVC Request may comprise additional user provided information (e.g., zip code of location) or additional user device provided information (e.g., geographic location information based on GPS or other locationing methods). The above-described additional information may be used by an eSVC processor, an eSVC issuer, or an eSVC processor/issuer to filter eSVC offerings available for the identified geographic location. In embodiments, the intelligent code may include information comprising eSVC activation information, eSVC redemption information, eSVC reload information, retailer identification (e.g., store ID), eSVC brand, rack, eSVC category, GPS coordinates of the user (e.g., of the merchant location and/or user's mobile device), type of user device (e.g., of the user's mobile device), identification of the user device, IP address, one or more email addresses, a requested value for the eSVC, whether the request is for multiple eSVCs (e.g., a combo code), e-wallet account information (e.g., e-wallet login), loyalty program information (e.g., loyalty number, loyalty login information), where to deliver the eSVC (e.g., a third-party via communication means described herein), whether the user wishes to purchase now or later, whether the user wishes to purchase in-store or online, other information known to those skilled in the art with the aid of this disclosure, or combinations thereof. In an embodiment, the intelligent code does not comprise information which can be used to redeem, activate, reload, or use an electronic stored-value card. A tutorial may comprise a ‘Try Me’ app where a user can scan an intelligent code and follow the various method steps without actually purchasing an eSVC. The tutorial may alternatively comprise a website explaining how the intelligent code method works for obtaining an eSVC. The tutorial may alternatively comprise a demo video of how to interpret the intelligent code to obtain an eSVC. The tutorial may additionally comprise a link to move the user to a live purchase of an eSVC according to the embodiments disclosed herein.

A customer or consumer of card products (also referred to herein as a “user” in the disclosed embodiments) may generally make the request for the eSVC at a physical retail (e.g., merchant) location, an online merchant portal, via a user device (e.g., user deviceof), or combinations thereof. A physical retail location or online merchant portal may have a physical or virtual “endcap” which is a display for the intelligent codes for various brands and/or values of eSVCs or combinations of eSVCs. Thus, no physical card products are needed because purchase of the eSVC is initiated with a scan of an intelligent code of a desired eSVC. However, the virtual “endcap” may be employed for the sale and or delivery of physical stored-value cards as well, such as to promote the sale of physical “multipacks,” e.g., a package which contains multiple cards to be purchased and activated, wherein the multiple cards may share a common issuer or may not share a common issuer. Because the endcap (virtual or physical display) uses no physical cards in order to sell eSVCs, no distribution or manufacture of physical card products is needed. However, embodiments disclosed herein contemplate an intelligent code may be located on the front or back of a physical stored-value card. The physical stored-value card may comprise a known form of stored-value cards often referred to as a credit card, a debit card, a gift-card, a loyalty card, a rewards card, a membership card, a discount card, a promotional card, etc. Thus, embodiments disclosed herein may be used with physical stored-value cards, which may be converted to eSVCs by first scanning the intelligent code of the physical stored-value card to request an eSVC.

The request for an electronic stored-value card may comprise a request to view a selection of eSVCs available for purchase, a request to view an eSVC value available for purchase, a request to purchase an eSVC (or multiple eSVCs), or combinations thereof. In response to a request to view a selection of eSVCs, an entity (e.g., an eSVC processor, an eSVC issuer, or an eSVC processor/issuer) may provide the selection of eSVCs available for purchase and/or exchange (e.g., in an eSVC exchange service) to the user, the selection of eSVC values available to the user, eSVC purchase information as described hereinbelow, or combinations thereof.

At blockof, an eSVC shopping cart is established. The eSVC shopping cart may be established in response to the information received from interpretation of the intelligent code (e.g., a QR code scan). The eSVC shopping cart may comprise a digital representation of a physical shopping cart used to buy goods or services (e.g., such as the shopping carts commonly used on merchant websites to purchase goods or services (e.g., a hotel website, an airline website, a bookstore website, etc.). The eSVC shopping cart may comprise unactivated eSVCs associated with the received information from an interpretation of the intelligent code. For example, after an eSVC processor receives information of an interpretation of an intelligent code (e.g., information from a QR code scan) from a user, the eSVC processor may create an eSVC shopping cart which stores the intelligent code information identifying the eSVC associated with the intelligent code. The eSVC shopping cart may also associate any information captured in blockof the method ofwith one or more eSVCs therein. The eSVC in the eSVC shopping cart may comprise an unactivated state. For example, as a digital representation of the eSVC status on a device such as the user's mobile device, the eSVC shopping cart may be shown as a webpage, popup window, app, or combinations thereof, and the eSVC may be shown with a visual identifier such as a logo or icon (e.g., a Brand X logo if the eSVC is a Brand X eSVC). The visual identifier may be made transparent and/or without interactivity on the user's device to indicate the eSVC is in the eSVC shopping cart but not yet activated. In embodiments, the eSVC shopping cart is not displayed to the user until the user purchases and activates the eSVC. As indicated above at blockfor the method in, the e-wallet may comprise the eSVC shopping cart, or vice-versa.

At blockof, information may be captured in response to the request for an eSVC. In addition to information contained in the intelligent code, captured information may comprise GPS coordinates of the user (e.g., of the user's mobile device), type of user device (e.g., of the user's mobile device), identification of the user device, IP address, one or more email addresses, a requested value for the eSVC, whether the request is for multiple eSVCs, e-wallet account information (e.g., e-wallet login), loyalty program information (e.g., loyalty number, loyalty login information), where to deliver the eSVC (e.g., a third-party via communication means described herein), whether the user wishes to purchase now or later, whether the user wishes to purchase in-store or online, other information known to those skilled in the art with the aid of this disclosure, or combinations thereof. In embodiments, the user may be prompted on a device (e.g., a user device) and asked to submit the information which is desirably captured. The user may enter and submit the information, may deny entering the information, may request to enter the information later, may take no action, or combinations thereof. In embodiments wherein the eSVC shopping cart has not been paused before capturing information and pausing the eSVC shopping cart is desired, flow may proceed from blockto blockof. In embodiments where the eSVC shopping cart has already been paused or pausing is not desired, flow from blockofmay proceed to blockof; alternatively, to blockof; alternatively, to blockof.

At blockof, the eSVC shopping cart may be paused. For example, the provider of the eSVC shopping cart, e.g., the eSVC processor or the eSVC issuer, may pause further activity associated with the eSVC shopping cart (in embodiments, other than adding more eSVCs via intelligent code interpretation). In embodiments, activity associated with the eSVC shopping cart may be paused until a condition is satisfied, such as a purchase of an eSVC, an activation of an eSVC, or in one-step activation scenarios, the purchase and activation of the eSVC. In embodiments where information is not captured before pausing the eSVC shopping cart and captured information is desired, flow proceeds to blockof. In embodiments where information has already been captured or is not desired, flow may proceed to blockof; alternatively, to blockof; alternatively, to blockof.

In the disclosed embodiments, the user may choose (e.g., via a prompt embodied as a selection screen, popup window, which can be prompted while entering information at blockof, etc.) to purchase the eSVC via in-store purchase (e.g., via a point-of-sale device) or via an online payment portal (e.g., provided by a computer device of the eSVC processor which acts as an online merchant for the purchase of the eSVC, of a third-party merchant, or of an eSVC issuer which acts as an online merchant for the purchase of the eSVC). In embodiments, the user may automatically be taken to online payment unless the user elects not to purchase online, or the eSVC may automatically be prepared (e.g., according to blocksand) for in-store purchase unless the user elects not to purchase in-store. In embodiments, the user may use a user device to request the online purchase without need for a point-of-sale device, e.g., via an online payment portal, or the user may use the user device to elect in-store payment for the eSVC. If the user requests online payment, flow may proceed to block. If the user elects to pay in-store, flow may proceed to blockor blockdepending on which entity (e.g., eSVC processor or eSVC issuer) provides the barcode and activation information for the eSVC. In embodiments, the user may choose not to purchase at the time of prompting, and the eSVC shopping cart may remain paused as discussed in blockuntil further action is taken (e.g., in-store purchase of the eSVC, online purchase of the eSVC, deletion of the eSVC from the eSVC shopping cart, etc.).

At blockof, purchase information (e.g., a barcode and/or activation information) for the eSVC purchase is obtained. In embodiments, purchase information is obtained after the user chooses to purchase the eSVC in-store. In an embodiment, the entity processing the purchase of the eSVC (i.e., via the initiating intelligent code interpretation) may not be the same entity as the issuer of the eSVC. The processing entity may obtain the barcode and/or activation information of the requested eSVC from another entity such as the issuer of the eSVC. The issuer of the eSVC may generate, or retrieve a pre-generated, unique barcode and/or activation information for purchase of the eSVC. The barcode may comprise an EAN128 barcode, a dynamic EAN128 barcode, or a UPC. Activation information may comprise an activation code. In an embodiment, the barcode comprises the activation information in an issuer account portion of the barcode. Additionally the barcode comprises a vendor product identification in a vendor product identification portion of the barcode.

At blockof, purchase information (e.g., a unique barcode and/or unique activation information) for the eSVC purchase is provided (e.g., made available for retrieval, sent via digital communication, etc.). In an embodiment where the entity processing the purchase of the eSVC (i.e., via the initiating intelligent code interpretation) may be the issuer of the eSVC, the processing entity may generate, or retrieve a pre-generated, unique barcode and/or activation information for purchase of the eSVC. The eSVC processor may then provide (e.g., send) the barcode and/or activation information to the user (e.g., via user device), to a merchant (e.g., via a merchant computer device, described in the discussion for), or combinations thereof. In an embodiment where the processor of purchase of the eSVC is an entity separate from the issuer of the eSVC and the issuer is responsible for providing barcode and/or activation information, the issuer of the eSVC may provide (e.g., send) the barcode and/or activation information to the processor of the eSVC (e.g. for forwarding to the user), directly to the user (e.g., via a user device), to the merchant (e.g., via a merchant computer device, described in the discussion for), or combinations thereof. After performing the step at blockof, flow may proceed to blockof.

At blockof, an online payment portal may be provided. In embodiments, an online payment portal may be provided (e.g., by the eSVC processor acting as a merchant, or by a third-party merchant) to the user through which the user may purchase the eSVC. The online payment portal may request payment information (e.g., account number, expiration date, security code) for a card other than the eSVC being purchased (e.g., a physical card, another eSVC, or combination thereof). The user, e.g., via the user device, may enter the payment information (e.g., card number (or another eSVC number), billing address (postal code), expiration date, security code, or combinations thereof) and the payment information may be processed by the eSVC processor (in embodiments where the eSVC processor provides the payment portal), or by a third-party merchant that forwards the payment information to the eSVC processor.

At blockof, purchase verification is received. The purchase verification may comprise an activation request of the eSVC. In embodiments where the eSVC is purchased in-store, the barcode may be sent to and displayed on a user device (e.g., the user's mobile device), and the user may scan the barcode displayed on the user device (or have the barcode scanned by in-store personnel) with a merchant computer device (e.g., a point-of-sale terminal of a merchant). Scanning the barcode and activation information may be considered a one-step activation method, as opposed to a two-step activation method where the barcode and activation information are separately provided and purchase of the eSVC is a separate step from activation of the eSVC. The one-step activation of the eSVC embodied by scanning the barcode and activation information may comprise simultaneously or serially (e.g., one after another without separate request) scanning the barcode and activation information (e.g., comprising an activation code, a vendor product identification, an issuer account code, or combinations thereof) at a merchant computer device (e.g., point-of-sale terminal). One-step activation of the eSVC only requires a single entry by a clerk operating the point-of-sale terminal to activate the eSVC. For example, the one step may be performed at the point-of-sale terminal by scanning the barcode, (e.g., an EAN/UCC-128 barcode) comprising both a vendor product identification portion and an issuer account portion. The vendor product identification portion may be used to perform a look-up to determine eSVC identity and price, or may contain the eSVC identity and price without need for merchant look-up. In embodiments, the price does not match the value of the eSVC, for example, when a promotional offer sells an eSVC of a greater value (e.g., $30) for a price of a lesser value (e.g., $20). The issuer account portion may be used to activate the particular account associated with the eSVC such that the eSVC may be used (e.g., to transact business with a merchant). Upon being entered at the point-of-sale terminal, the issuer account portion may be conveyed (for example, via a network described hereinbelow) to, and received by, the issuer of the eSVC (e.g., as a purchase verification and/or an activation request); the issuer account portion may be conveyed (for example, via a network described hereinbelow) to, and received by, the processor of the eSVC (e.g., as a purchase verification and/or as an activation request); the issuer account portion may be conveyed (for example, via a network described hereinbelow) to, and received by, a third-party eSVC processor responsible for activating the eSVC (e.g., as a purchase verification and/or as an activation request); or combinations thereof. Once the purchase verification and/or activation request is received, the processor, issuer, third-party processor, or combinations thereof, may activate the eSVC via methods known in the art with the aid of this disclosure.

In embodiments with an online purchase of the eSVC, the barcode may not be provided. In online purchase embodiments, when the online payment portal requests payment information (e.g., account number, expiration date, security code) for a card other than the eSVC being purchased (e.g., a physical card, another eSVC, or combination thereof), the user, e.g., via the user device, may enter the payment information (e.g., card number (or another eSVC number), billing address (postal code), expiration date, security code, or combinations thereof) and the payment information may be processed by the eSVC processor (in embodiments where the eSVC processor provides the payment portal), or by a third-party merchant that forwards the payment information to the eSVC processor. Upon online payment, a purchase verification may be conveyed (for example, via a network described hereinbelow) to, and received by, the issuer of the eSVC (e.g., as a purchase verification and/or an activation request); the purchase verification may be conveyed (for example, via a network described hereinbelow) to, and received by, the processor of the eSVC (e.g., as a purchase verification and/or as an activation request); the purchase verification may be conveyed (for example, via a network described hereinbelow) to, and received by, a third-party eSVC processor responsible for activating the eSVC (e.g., as a purchase verification and/or as an activation request); or combinations thereof.

Once the purchase verification and/or activation request is received, the processor, issuer, third-party processor, or combinations thereof, may activate the eSVC via methods known in the art with the aid of this disclosure. In embodiments, the purchase of the eSVC may be processed by the provider of the eSVC and/or e-wallet (e.g., via eSVC processor), by a merchant, by the eSVC issuer, or combinations thereof. In an embodiment, the purchase may be processed by applying a purchase value to complete the transaction. In an embodiment, to process the purchase, authentication information to process the purchase may be identified, a value associated with the eSVC (e.g., embodied as a value token, described below) may be assigned, at least a portion of the value of another eSVC (e.g., value token) may be applied to at least a portion of the purchase price, at least a portion of the value of a physical card may be applied to at least a portion of the purchase price, or combinations thereof. In an embodiment, identifying authentication information may comprise authentication techniques known to those skilled in the art with the aid of this disclosure. In embodiments, processing the purchase may further comprise processing at least a portion of the purchase in a primary wallet of an e-wallet (e.g., electronic walletof), processing at least a portion of the purchase in a sub-wallet of an e-wallet (e.g., of electronic walletof), or both. In embodiment, a notification may be sent to the user, merchant, processor, and or issuer that the purchase has been processed. After performing an embodiment of the step at blockof, flow may proceed to blockof.

At blockof, the eSVC shopping cart is unpaused. In embodiments, the eSVC shopping cart is unpause after purchase of an eSVC contained therein, after activation of an eSVC therein, or both. In embodiments, the eSVC shopping cart is unpaused only for the eSVC purchased and/or activated while the eSVC shopping cart remains paused for non-purchased and/or unactivated eSVCs. Flow may proceed to blockof; alternatively, to blockof; alternatively to blockof.

At blockof, the purchased and activated eSVC may be added to an electronic wallet (e.g., of the user). In embodiments, the eSVC may be added to the electronic wallet according embodiments of the method described forabove. In additional or alternative embodiments, the eSVC processor may prompt the user (e.g., before or after activation of the eSVC) whether the user would like to create an electronic wallet and add the eSVC thereto, or whether the user has a pre-existing e-wallet and would like to add the eSVC thereto. The processor may add the activated eSVC to an e-wallet designated by the user upon instruction by the user, or automatically according to preferences in the e-wallet which may be recognized in embodiments where the use purchases the eSVC from the user's e-wallet provider or in another arrangement where the e-wallet provider may recognize the purchase of the eSVC which needs to be automatically added to the user's e-wallet.

In certain embodiments (e.g., as reflected in) a user may create an e-wallet, establish rules for the e-wallet, provision the e-wallet, and access the e-wallet to facilitate electronic transactions. Suitable processes for registering the eSVC are disclosed in International Application Serial No. PCT/US13/26501, filed on Feb. 15, 2013, and entitled “System and Method of Registering Stored-Value Cards Into Electronic Wallets.” Examples of techniques for authenticating, allocating, and provisioning an eSVC are described hereinbelow. Various registration, authentication, allocation, and provisioning techniques may be performed prior to use of the eSVC which would be recognized by one skilled in the art with the aid of this disclosure. For example, the user may register the eSVC in one or more electronic wallets (e.g., electronic walletof).

After adding the eSVC to an e-wallet, flow may proceed to blockof; alternatively, to blockof.