Source: http://www.patentsencyclopedia.com/app/20120330830
Timestamp: 2017-10-19 23:59:33
Document Index: 53501855

Matched Legal Cases: ['art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1600', 'art 1671', 'art 1671', 'art 1671']

SYSTEM AND METHOD FOR CREATING AND MANAGING A STORED VALUE ACCOUNT ASSOCIATED WITH A CLIENT UNIQUE IDENTIFIER - Patent application
Patent application title: SYSTEM AND METHOD FOR CREATING AND MANAGING A STORED VALUE ACCOUNT ASSOCIATED WITH A CLIENT UNIQUE IDENTIFIER
Inventors: James P. Mason (Atlanta, GA, US) Robert L. Dessert (Atlanta, GA, US) Robert L. Dessert (Atlanta, GA, US) Henry H. Fann (Atlanta, GA, US) Zhirong Chen (Atlanta, GA, US) Krishnakanth S. Chimalamarri (Atlanta, GA, US)
Patent application number: 20120330830
1. A method for exchanging stored value accounts, the method comprising: creating a first stored value account having an account value and associated with a first merchant; creating a first virtual token associated the first stored value account; displaying a graphical representation of the first virtual token on a display of a client device; receiving a request to exchange at least a portion of the account value of the first stored value account, the request including information identifying the first stored value account and information identifying a second merchant; creating, in response to the request, a second stored value account having an account value and associated with the second merchant; creating a second virtual token associated the second stored value account; and displaying an animation on the display of the client device, the animation including a transition from displaying the graphical representation of the first virtual token to displaying a graphical representation of the second virtual token.
2. The method of claim 1, wherein: the graphical representation of the first virtual token has a card-like shape; and the graphical representation of the second virtual token has a card-like shape.
5. The method of claim 1, further comprising: calculating an exchange fee.
6. The method of claim 5, wherein: the step of displaying a graphical representation of the first virtual token on a display of a client device further comprises displaying a confirmation screen including an account balance and an exchange fee; and the step of receiving a request to exchange at least a portion of the account value of the first stored value account comprises receiving an indication of a user confirmation in response to displaying the confirmation screen.
7. The method of claim 6, wherein: the confirmation screen includes an initial account balance reflecting an amount prior to subtracting the exchange fee and a final account balance reflecting an amount after subtracting the exchange fee.
8. The method of claim 1, wherein the client device comprises: one of a mobile hand-held device, a desktop computer, and a laptop computer.
9. The method of claim 8, wherein the mobile hand-held device comprises: a wireless mobile telephone.
10. The method of claim 9, wherein the step of displaying an animation on the display of the client device comprises: the client device executing an animation software routine.
11. A computer system for creating and managing a stored value account associated with a client device, the system comprising: a processor operable to: create a first stored value account having an account value and associated with a first merchant; create a first virtual token associated the first stored value account; display a graphical representation of the first virtual token on a display of a client device; receive a request to exchange at least a portion of the account value of the first stored value account, the request including information identifying the first stored value account and information identifying a second merchant; create, in response to the request, a second stored value account having an account value and associated with the second merchant; create a second virtual token associated the second stored value account; and display an animation on the display of the client device, the animation including a transition from displaying the graphical representation of the first virtual token to displaying a graphical representation of the second virtual token.
12. The computer system of claim 11, wherein: the graphical representation of the first virtual token has a card-like shape; and the graphical representation of the second virtual token has a card-like shape.
16. The computer system of claim 15, wherein: the processor being operable to display a graphical representation of the first virtual token on a display of a client device further comprises the processor being operable to display a confirmation screen including an account balance and an exchange fee; and the processor being operable to receive a request to exchange at least a portion of the account value of the first stored value account comprises the processor being operable to receive an indication of a user confirmation in response to displaying the confirmation screen.
17. The computer system of claim 16, wherein: the confirmation screen includes an initial account balance reflecting an amount prior to subtracting the exchange fee and a final account balance reflecting an amount after subtracting the exchange fee.
18. The computer system of claim 11, wherein the client device comprises: one of a mobile hand-held device, a desktop computer, and a laptop computer.
21. A computer system for creating and managing a stored value account associated with a client device, the system comprising: means for creating a first stored value account having an account value and associated with a first merchant; means for creating a first virtual token associated the first stored value account; means for displaying a graphical representation of the first virtual token on a display of a client device; means for receiving a request to exchange at least a portion of the account value of the first stored value account, the request including information identifying the first stored value account and information identifying a second merchant; means for creating, in response to the request, a second stored value account having an account value and associated with the second merchant; means for creating a second virtual token associated the second stored value account; and means for displaying an animation on the display of the client device, the animation including a transition from displaying the graphical representation of the first virtual token to displaying a graphical representation of the second virtual token.
22. The computer system of claim 21, wherein: the graphical representation of the first virtual token has a card-like shape; and the graphical representation of the second virtual token has a card-like shape.
25. The computer system of claim 21, further comprising: means for calculating an exchange fee.
26. The computer system of claim 25, wherein: the means for displaying a graphical representation of the first virtual token on a display of a client device further comprises means for displaying a confirmation screen including an account balance and an exchange fee; and the means for receiving a request to exchange at least a portion of the account value of the first stored value account comprises means for receiving an indication of a user confirmation in response to displaying the confirmation screen.
27. The computer system of claim 26, wherein: the confirmation screen includes an initial account balance reflecting an amount prior to subtracting the exchange fee and a final account balance reflecting an amount after subtracting the exchange fee.
28. The computer system of claim 21, wherein the client device comprises: one of a mobile hand-held device, a desktop computer, and a laptop computer.
30. The computer system of claim 29, wherein the means for displaying an animation on the display of the client device comprises: means for executing an animation software routine on the client device.
31. A computer program product comprising a computer-usable medium having a computer-readable program code embodied therein, said computer-readable program code adapted to be executed to implement a method for managing a stored value account, said method comprising: creating a first stored value account having an account value and associated with a first merchant; creating a first virtual token associated the first stored value account; displaying a graphical representation of the first virtual token on a display of a client device; receiving a request to exchange at least a portion of the account value of the first stored value account, the request including information identifying the first stored value account and information identifying a second merchant; creating, in response to the request, a second stored value account having an account value and associated with the second merchant; creating a second virtual token associated the second stored value account; and displaying an animation on the display of the client device, the animation including a transition from displaying the graphical representation of the first virtual token to displaying a graphical representation of the second virtual token.
32. The computer program product of claim 31, wherein: the graphical representation of the first virtual token has a card-like shape; and the graphical representation of the second virtual token has a card-like shape.
35. The computer program product of claim 31, wherein the method further comprises: calculating an exchange fee.
36. The computer program product of claim 35, wherein: the step of displaying a graphical representation of the first virtual token on a display of a client device further comprises displaying a confirmation screen including an account balance and an exchange fee; and the step of receiving a request to exchange at least a portion of the account value of the first stored value account comprises receiving an indication of a user confirmation in response to displaying the confirmation screen.
37. The computer program product of claim 36, wherein: the confirmation screen includes an initial account balance reflecting an amount prior to subtracting the exchange fee and a final account balance reflecting an amount after subtracting the exchange fee.
[0001] The subject matter of this disclosure is related to U.S. patent application Ser. No. 12/851,724, filed Aug. 6, 2010, entitled "SYSTEM AND METHOD FOR CREATING AND MANAGING A STORED VALUE ACCOUNT ASSOCIATED WITH A CLIENT UNIQUE IDENTIFIER."
[0004] Accordingly, what is needed is an improved system and method of conducting transactions using a virtual stored value token that may be managed with a mobile client device and which may provide increased flexibility of use of a stored value account by the token holder.
[0008] In another aspect, a computer program product is disclosed and may include a computer-usable medium having a computer-readable program code embodied therein. The computer readable program code may be adapted to execute and to implement a method for managing a stored value account. The method implemented by the code may include creating a first stored value and an associated first virtual token, displaying a graphical representation of the first virtual token on a display of a client device, receiving an exchange request, creating a second stored value account and an associated second virtual token, and displaying an animation that includes a transition from the first virtual token to the second virtual token.
[0012] FIG. 3 is a diagram of exemplary computer architecture for the system of FIG. 1;
[0021] FIG. 10c is a diagram of a detailed purchase/redemption presentation screen for a stored value transaction;
[0023] FIG. 12 is a diagram of a screen for confirming an exchange operation involving stored value accounts selected for the exchange by a user of the client device;
[0024] FIG. 13 is a diagram of a screen for displaying a visual representation of the exchange operation, including an animation depicting a transition from one account to the other;
[0034] In this description, the terms "communication device," "wireless device," "wireless telephone," "wireless communication device," and "wireless handset" are used interchangeably. With the advent of third generation ("3G") wireless technology, greater bandwidth availability has enabled more electronic devices with a greater variety of wireless capabilities. Therefore, a wireless device could be a cellular telephone, a pager, a PDA, a smartphone, a navigation device, or a computer with a wireless connection.
[0035] Referring to FIG. 1, this figure is a diagram of a first aspect of a system 100 for creating and managing a stored value account 142 associated with a client device 102. Stored value accounts 142 may include gift card accounts available as of this writing from various merchants 120. Stored value accounts 142 cover and may include, but are not limited to, payroll cards, government benefit cards, prepaid debit cards, and telephone.
[0036] There are usually two main categories of stored value accounts 142: (a) single-purpose or "closed-loop" accounts and (b) "open-loop" accounts. Gift cards, which may only be used to purchase goods at particular retailers, and prepaid telephone cards, which may only be used to make telephone calls, are examples of single-purpose stored value accounts 142.
[0037] The second type of account 142 is a multipurpose or "open-loop" account 142, which may be used to make debit transactions at a wide variety of retail locations (not limited to a single retailer), as well as for other purposes, such as receiving direct deposits and withdrawing cash from ATMs. Some multipurpose accounts may be a branded credit card network, like VISA® or MASTERCARD® brand networks, and may be used wherever those brands are accepted. The stored value account 142 of this disclosure covers both open-loop and closed-loop types.
[0038] The system 100 may include a client device management server 106, a stored value account processor server 108A, a stored value account issuer server 108B, a merchant acquirer 116B, a client device management ("CDM") acquirer 116A, a sender funding source 118, client devices 102, and a merchant 120.
[0039] Many of the system elements illustrated in FIG. 1 are coupled via communications links 103A-I to a computer or communications network 105. The links 103 illustrated in FIG. 1 may be wired or wireless links Wireless links include, but are not limited to, radio-frequency ("RF") links, infrared links, acoustic links, and other wireless mediums. The communications network 105 may comprise a wide area network ("WAN"), a local area network ("LAN"), the Internet, a Public Switched Telephony Network ("PSTN"), a paging network, or a combination thereof.
[0040] Many of the system elements illustrated in FIG. 1 are also shown to be coupled by virtual links 107A-H illustrated with dashed lines. The virtual links 107 depict direct communications between elements when, in fact, the actual communications are supported by the communications links 103 that couple a respective element to the communications network 105. The virtual links 107 are shown for exemplary purposes and for understanding the flow of communications between and among respective elements in the system 100.
[0041] The client device management server 106 may support a mobile wallet system 134 which is responsible for managing and maintaining mobile wallets 114 that are stored in memory by the sender client device 102A and the recipient client device 102B. Each client device 102 is shown to have an antenna 372 so that a respective client device may establish wireless communication links 103 with the communications network 105. However, client devices 102 which have wired or hard line links 103 to the communications network 105, such as laptop or handheld computers, are included within the scope of the invention.
[0042] The client device management server 106 may communicate with the sender client device 102A in order to establish a stored value account 142 that may be created and sent to a mobile wallet 114B of a recipient client device 102B. The client device management server 106 also works with the stored value account processor server 108A and the stored value account issuer server 108B in order to manage transactions associated with the stored value accounts 142. The stored value account processor server 108A may work directly with a merchant acquirer 116B that also works with a merchant 120. In some instances, a merchant 120 may work directly with the stored value account processor server 108A without sending communications through or receiving communications from a merchant acquirer 116B.
[0043] While a stored value account 142A is illustrated with the sender client device 102A, it is recognized that the user of the sender client device 102A does not need to have a stored value account 142A in order to send or create the stored value account 142B for the recipient client device 102B. Therefore, the stored value account 142A in connection with the sender client device 102A may be eliminated or it may not be created without departing from the scope of the invention.
[0044] The stored value account issuer server 108B may be responsible for establishing/creating the stored value accounts 142 managed and held in the stored value account database 146. Specifically, the stored value account issuer server 108B is responsible for creating and managing the client unique identifiers 155, virtual card identification numbers 167, primary account numbers ("PANs") 165, and merchant identifiers 170 of FIG. 2 discussed in greater detail below. While the stored value account issuer server 108B and stored value account processor 108A have been illustrated in FIG. 1 as separate elements, one of ordinary skill in the art recognizes that a single computer server could perform the functions of these two elements. With this in mind, the remaining disclosure, on occasion, may refer to the stored value account processor server 108A and stored value account issuer server 108B as a single hardware/software element.
[0045] The merchant 120 may accept and process stored value accounts 142 in exchange for goods and services. The client device management server 106 may communicate with a client device management ("CDM") acquirer 116A. The CDM acquirer 116A communicates with a sender funding source 118. The sender funding source 118 may comprise a financial institution that maintains a contractual relationship with a merchant 120 or the client device management server 106.
[0047] The sender funding source 118 may comprise a financial institution, such as a bank, that is associated with a user of the sender client device 102A. The sender funding source 118 may be accessed by the sender client device 102A to purchase a stored value account 142 for the recipient client device 102B. The stored value account 142 may be managed and serviced by the stored value account processor server 108A and stored value account issuer server 108B which receive all of their client device communications from the client device management server 106.
[0048] The stored value account processor server 108A and the stored value account issuer server 108B may maintain a database 146 of stored value accounts 142 that may be associated with a plurality of client devices 102. The stored value account processor server 108A may also communicate with merchant acquirers 116B or merchants 120 directly in order to process any request from a client device 102 to a merchant 120 for redeeming a value of a stored value account at a point of sale ("POS") terminal or in a virtual store environment present on a computer/communications network 105.
[0051] The system 100 may provide certain advantages when the client device 102 comprises a mobile wireless device such as a mobile telephone so that a merchant 120 may be provided with geographical coordinates of the recipient client device 102B as well as the identity of the user of the client device 102B by the client device management server 106. In this way, by knowing the identity of the recipient client device 102B and the geographical coordinates of the recipient client device 102B, the merchant 120 may be able to send offers or promotions to the recipient client device 102. In this manner, offers or promotions that are unique to a particular merchant 120 may be specifically targeted to a recipient 102B.
[0053] Referring to FIG. 2, this figure is a diagram of a data structure 179 for a stored value account database 146 managed by the stored value account processor server 108A and the stored value account issuer server 108B illustrated in FIG. 1. The data structure 179 may comprise a client unique identifier 155 and one or more primary account numbers ("PANs") 165 and one or more virtual card identification numbers ("VCARD ID#") 167. The PANs 165 and VCARD IDs 167 may be created for each stored value account 142 associated with a respective client device 102. The client device management server 106 may be responsible for creating the client unique identifier 155 and passing this unique identifier 155 to the stored value account issuer server 108B. Alternatively, the stored value account issuer server 108B may create the client unique identifier 155.
[0055] The client unique identifier 155 may be associated with a virtual card identification number ("VCARD ID#") 167 and unbranded account 160 when the sender client device 102A does not designate a particular merchant 120 to be associated with a set of funds for the stored value account 142. In other words, the unbranded account 160 may keep track of the funds which have been allocated to the stored value account 142 of a user who has a client unique identifier 155 but have not been associated with any particular merchant 120, such as a TARGET® or K-MART® brand store. The unbranded account 160 will not have any merchant name associated with the account but will have a virtual card identification number ("VCARD ID#") 167 associated with the unbranded account 160. The VCARD ID#167 is associated with the client unique identifier 155.
[0057] One particular standard for the PAN 165, as of this writing, may include the ISO/IEC 7812 standard. The ISO/IEC 7812 standard contains a single-digit Major Industry Identifier ("MII"), a six-digit Issuer Identification Number ("IIN"), an account number, and a single digit check sum calculated using the Luhn algorithm. The prefix of the PAN 165 may be the sequence of digits at the beginning of the number that determine the credit card network to which the number belongs. The first 6 digits of the PAN 165 may be referred to as the Issuer Identification Number ("IIN"). These identify the institution that issued the card to the card holder. The rest of the number may allocated or determined by the issuer, such as the stored value account issuer server 108B. The PAN 165 may comprise a sixteen digit number, but other multi-digit numbers as well as alphanumeric identifiers are within the scope of the invention.
[0060] The client unique identifier 155A has been associated with three primary account numbers ("PANs") 165A, 165B, 165C that are assigned to a first merchant having a merchant identifier 170A of "Merchant ID#1" and a second merchant having a merchant identifier 170B of "Merchant ID#2." The virtual card associated with the first PAN 165A has a stored value of $25.00 and the virtual card associated with the second PAN 165B has a stored value of $30.00. The virtual card associated with the third PAN 165C has a stored value of $35.00. The second and third virtual cards having PAN#2 and PAN#3 and associated with only the second merchant identifier 170B illustrate that a user of the recipient client device 102B may receive two separate gifts of different or same values but which are associated with the same merchant 120. While US currency has been used in these examples, one of ordinary skill in the art recognizes that any type of monetary currency may be used and is within the scope of the invention.
[0061] While the first unbranded account 160A associated with the VCARD ID#4 167D has a stored value of $10.00, according to one exemplary embodiment of the invention, a user of the recipient client device 102B may need to associate the funds of the unbranded first account 160A with a particular merchant 120 prior to being able to redeem the value of the first unbranded account 160A. In this particular example, a user of the client device 102 could transfer the funds from the unbranded account 160A to either the first or second virtual cards associated with the first PAN 165A or the second PAN 165B. Alternatively, a user could create a new virtual card associated with a new merchant 120 (relative to the merchants 120 represented by the merchant identifiers 170A, 170 in the account 142B) or an existing merchant 120 that has a fourth PAN 165 (not illustrated) for this stored value account 142A.
[0062] Also associated with each client unique identifier 155 may be one or more near field communication ("NFC") PANs 165, such as NFC PAN #1A 165A1 associated with client unique identifier #1 155A of the first stored value account 142B in FIG. 2 and NFC PAN #1B 165A2 associated with client unique identifier #2 155B of the second stored value account 142C in FIG. 2. These NFC PANs 165 correspond to physical tokens which may be attached to a client device 102 and which utilize near-field communications to exchange information with point-of-sale ("POS") terminals as is known to one of ordinary skill in the art.
[0063] FIG. 3 is a diagram of an exemplary computer architecture 101 for the system 100 of FIG. 1. The exemplary architecture 101 may include a client device 102. A client device server 106 may be connected to the mobile client device 102. The client device management server 106 may be connected to the mobile device 102 via a wired or wireless communications link 103, such as a mobile telephone network. Further, the client device management server 106 may be connected to a stored value account processor/issuer server 108A,B via a direct communications link 109A,C, such as by a WAN. As noted previously, the stored value account processor server 108A and the stored value account issuer server 108B may be two physically separate devices or software as illustrated in FIG. 1, or alternatively, the functions of these two elements 108A, B may be performed by a single device or software module as illustrated in FIG. 3. One of ordinary skill in the art will appreciate that either option may be selected depending upon computer architecture design constraints and without departing from the scope of the invention.
[0067] As depicted in FIG. 3, the stored value account processor/issuer server 108A, B may include a processor 140 and a memory 142 coupled to the processor 140. The memory 142 may include instructions for one or more of the method steps described herein. Further, the processor 140 and the memory 142 may serve as a means for executing one or more of the method steps described herein. As illustrated, the memory 144 may include a stored value account 142 associated with a user of the mobile device 102. A database 146 may also be connected to the stored value account processor server/issuer server 108A,B. The database 146 may include account information associated with the stored value account 142 and account information associated with other user accounts associated with other mobile devices.
[0070] As further illustrated in FIG. 4, a stereo audio CODEC 350 may be coupled to the analog signal processor 326. Moreover, an audio amplifier 352 may be coupled to the stereo audio CODEC 350. In an exemplary aspect, a first stereo speaker 354 and a second stereo speaker 356 are coupled to the audio amplifier 352. FIG. 4 shows that a microphone amplifier 358 may be also coupled to the stereo audio CODEC 350. Additionally, a microphone 360 may be coupled to the microphone amplifier 358. In a particular aspect, a frequency modulation ("FM") radio tuner 362 may be coupled to the stereo audio CODEC 350. Also, an FM antenna 364 is coupled to the FM radio tuner 362. Further, stereo headphones 366 may be coupled to the stereo audio CODEC 350.
[0075] Referring now to FIG. 6, this figure is a diagram of a message screen 600. The message screen 600 may be accessed by selecting a message option or message icon, such as one of the program icons 505 as illustrated in FIG. 5. The message screen 600 may include a listing of various types of messages that may be received and monitored in connection with the mobile wallet 114 stored in the client device 102. The exemplary messages illustrated in FIG. 6 include a stored value account notice 602, a balance alert, a bill pay alert, and a bank statement hypertext link. When a user selects one of the listed messages, such as the stored value account notice 602, a message detail screen such as screen 700 of FIG. 7 may be generated. The message screen 600 may also support one or more icons at the bottom of the screen, such as a dollar sign, purse icon, exclamation point icon, or other icon which may launch other software applications on the client device 102.
[0077] As discussed above, according to an exemplary aspect, a sender client device 102A may purchase a stored value account 142A (that may be referred to as a virtual gift card) and send the stored value account 142B to a recipient client device 102B. A user selects a stored value account 142A at the sender client device 102A and sends it to the recipient client device 102B where the received account is referred to as 142B.
[0079] As illustrated in FIG. 8, a screen 800 includes options for managing a stored value account 142. The options screen 800 may include virtual token 702 corresponding to the virtual card represented by the stored value account 142 and various screen navigation and display icons, as well as icons that are associated with various options for managing the stored value account 142.
[0083] If the user selects virtual token 702, the display changes from the display 800 shown in FIG. 8 to the display 900 shown in FIG. 9. In display 900, the reverse side of the card-like virtual token 702 is depicted. The reverse side includes identifying information such as the "Merchant #1" brand name or logo associated with the stored value account 142, the identity of the sender of the stored value account 142 ("Sender"), and the then-current balance. The reverse side of virtual token 702 also includes a "Present to Cashier" button 902 and a "Present Online" button 904.
[0084] In response to a user of the recipient client device 102B selecting the "Present to Cashier" button 902 on the virtual token 702, another screen 1000A is displayed, as illustrated in FIG. 10A. Screen 1000A is a purchase/redemption presentation screen for a stored value transaction. A merchant (cashier) may use a scanner to read a one-dimensional barcode 1004A. Exemplary one-dimensional bar codes may include, but are not limited to, U.P.C., Codabar, Code 25--Non-interleaved 2 of 5, Code 25--Interleaved 2 of 5, Code 39, Code 93, Code 128, Code 128A, Code 128B, Code 128C, Code 11, CPC Binary, DUN 14, EAN 2, EAN 5, EAN 8, EAN 13, Facing Identification Mark, GS1-128 (formerly known as UCC/EAN-128), GS1 DataBar formerly Reduced Space Symbology ("RSS"), HIBC (HIBCC Bar Code Standard), ITF-14, Latent image bar code, Pharmacode, Plessey, PLANET, POSTNET, Intelligent Mail Bar code, MSI, PostBar, RM4SCC/KIX, JAN, and Telepen.
[0085] The current value of the stored value account 142 may be retrieved by the client device 102 immediately prior to the display of the account information and the barcode 1004A to ensure the information is as current as possible at the time of sale.
[0089] As illustrated in FIG. 10c, a screen 1000C may be displayed instead of screen 1000A (FIG. 10A) in some instances. In screen 1000C, a two-dimensional (2-D) bar code 1004C is displayed instead of a one-dimensional bar code 1004A as in screen 1000A. A cashier may use a POS terminal having a bar code reader to scan 2-D bar code 1004C in essentially the same manner as the cashier may scan bar code 1004A. The format of the 2-D bar code 1004C include, but is not limited to, one or more of the following symbologies: Aztec Code, 3-DI, ArrayTag, Small Aztec Code, Chromatic Alphabet, Chromocode, Codablock, Code 1, Code 16K, Code 49, ColorCode, Compact Matrix Code, CP Code, CyberCode, d-touch, DataGlyphs, Datamatrix, Datastrip Code, Dot Code A, EZcode, Grid Matrix Code, High Capacity Color Bar code, HueCode, INTACTA.CODE, InterCode, MaxiCode, mCode, MiniCode, Micro PDF417, MMCC, Nintendo e-Reader#Dot code, Optar, PaperDisk, PDF417, PDMark, QR Code, QuickMark Code, Semacode, SmartCode, Snowflake Code, ShotCode, SuperCode, Trillcode, UltraCode, UnisCode, VeriCode, VSCode, WaterCode, for example.
[0090] In an instance in which the recipient client device 102B is a desktop or laptop computer, or the recipient client device 102B is being used for an e-commerce transaction, then the user may select the "Present Online" button 904 (FIG. 9). In response to the user selecting the "Present Online" button 904, a display similar to that shown in FIG. 10B may be presented on the display device, such as a computer screen. A user may copy and paste the PAN indication 1004B into an e-commerce website. The recipient client device 102B may be provided with text based instructions on how to enter PAN indication 1004B that represents the sixteen-digit PAN 165 into an e-commerce website. Exemplary text based instructions may include where to find the expiration date associated with the PAN 165 and what to enter if a card verification value ("CVV") or card identification ("CID") number is requested by a merchant 120.
[0092] The exchange icon 908 allows a user of the client device 102 to exchange value associated with one merchant for value associated with another merchant. In response to a user selecting "Exchange" icon 908, the screen 1100 shown in FIG. 11 is presented. Screen 1100 includes a number of merchant icons 1102. Each of merchant icons 1102 has a card-like appearance and includes identifying information such as a name or logo (e.g., "Merchant #2," "Merchant #3," "Merchant #4," etc.) associated with one of merchants 120. Screen 1100 may include a "Back" button 1104 that allows the user to return to the previously displayed screen 900.
[0095] An animation that may be used to depict such an action is sometimes referred to in the art as a "page curl." As the animation continues, the portions of the virtual token 702 adjacent the corner appear to lift away in a manner resembling the turning of a page in a book or the peeling of a sticker to reveal the new virtual token 1202, as illustrated in FIG. 14. The animation may depict virtual token 702 gradually dissolving away as it is peeled off. When the animation is completed, the display 1500 shown in FIG. 15 includes only the new virtual token 1202 and does not include virtual token 702. Note that display 1500 is similar to display 800, except that display 1500 includes the new virtual token 1202 instead of virtual token 702. Providing software for implementing a "page curl" or "peel-off" animation of the type shown in FIGS. 13-15 on client device 120 is well within the capabilities of one of ordinary skill in the art. Accordingly, the software and other aspects of this animation are not described in further detail in this disclosure.
[0096] Referring to FIG. 16A, this figure is a first flowchart 1600A illustrating a method 1600 for creating and managing a stored value account 142 associated with a client device 102. Block 1603 is the first step in a process 1600 in which the client management server 106 may receive a log-in identifier from a sender client device 102A to access the mobile wallet system 114. At block 1605, the sender client device 102A may identify the recipient of the stored value account 142 that may be purchased by an operator of sender client device 102A. In this step, the sender client device 102A is prompted to provide contact information for the recipient of the stored value account 142. Usually, at a minimum, the sender client device 102A will need to provide an e-mail address or a mobile telephone number of the recipient of the stored value account 142.
[0097] Also at block 1605, the client device management server 106 may also prompt the sender client device 102A for the name of the user associated with the sender client device 102A. This name associated with the sender client device 102A will be used in the notification that may be delivered to the recipient client device 102B. This name field for the sender client device 102A may be pre-populated by the client device management server 106.
[0098] Next, at block 1607, the client device management server 106 may present or display stored value account(s) 142 associated with merchants 120 available for purchase on the sender client device 102A. A listing of stored value accounts organized by merchant types as illustrated in FIG. 11 may be presented on the display device 332 of the sender client device 102A. At this block 1607, an unbranded stored value account 142 may be listed as one of the options for selection by the sender client device 102A. Also, the user of the sender client device 102A may be provided with the ability to select the amount of value that he or she desires to purchase for associating with the stored value account 142. The value that may be purchased for each stored value account 142 may be based on preferences selected by a merchant 120 associated with a stored value account 142. This means that a merchant 120 may establish a set of pre-denomination values that are available to the sender client device 102A.
[0099] Moving to block 1609, the client device management server 106 may receive a selection of the stored value account 142 from the sender client device 102A. Also, the client device management server 106 may also receive the selected value for purchase from the sender client device 102A that will be associated with the stored value account 142. The selected stored value account 142 may have a merchant identifier unique to a particular merchant 120, such as an alphanumeric code. At this stage, a sender client device 102A may also select an unbranded stored value account 142 that is not associated with any particular merchant 120 and which does not have any merchant identifier.
[0100] At block 1611, the client device management server 106 may display a graphical representation of the virtual token 702 associated with the selected stored value account 142, similar to that illustrated in FIG. 8. The sender client device 102A may have the ability to preview each graphical representation or artwork that may be used for the virtual token 702. The options for the graphical representation or artwork of the virtual token 702 may be provided by a merchant 120 associated with the stored value account 142 that was selected. For unbranded accounts 142, the client device management server 106 may also display artwork available for such accounts 142 based on preferences maintained by the client device management server 106.
[0101] Subsequently, at block 1615, the client device management server 106 may receive the selection(s) for the artwork made by an input entered on the sender client device 102A. At block 1617, the client device management server 106 may display a plurality of options for personalizations of the stored value account 142. Personalizations may include the ability of the sender client device 102A to include one or more of the following elements to be associated with the stored value account 142 that will be sent to the recipient client device 102B as part of the gifted stored value account 142: a text note, an audio recording, an image, and a video recording. The client device management server 106 may also display fees that may be charged for each type of personalization.
[0102] The text note form of personalization may be the default personalization associated with the "gifting" of a stored value account 142 by the sender client device 102A. This text note may be part of the notification of the stored value account 142 that is sent to the recipient client device 102B. The text note may be viewed on a mobile telephone or on a website depending upon the form of the recipient client device 102B that is selected by a user to access the gifted stored value account 142. The text note may be limited to a predetermined length of characters, such as three hundred. However, one of ordinary skill in the art recognizes that other character lengths are included within the scope of the invention.
[0103] The audio recording personalization to be associated with the stored value account 142 and its corresponding virtual token 702 may require an additional fee from the sender client device 102A. The audio recording may also be limited to a predetermined length. One exemplary length is sixty seconds, however, other lengths of recording periods for the audio recording are within the scope of the invention. Other lengths of recording periods for the audio recording may be offered for additional surcharges. The sender client device 102A may be provided with the ability to preview, re-record, or remove the audio recording at any point prior to confirming the purchase of the stored value account 142. During the audio recording, the sender client device 102A may present a user interface that displays the amount of remaining time left to complete a particular audio recording.
[0104] The image capture personalization may be defined by the current camera settings of the sender client device 102A. A standard surcharge may be imposed on the sender client device 102A for any image associated with the stored value account 142 and its corresponding virtual token 702. Similar to the audio recording, the sender client device 102A may be provided with the ability to preview, retake, or review the captured image at any point prior to confirming the purchase of the stored value account 142.
[0105] For the video recording personalization option, a standard surcharge may also be imposed on the sender client device 102A for selecting this option. The length of the recording period of the video recording may also be predetermined or predefined. An exemplary maximum video length for the recording period may include one limited to sixty seconds, however, other lengths for the recording periods are within the scope of the invention. Other lengths for the recording periods for the video recording may be offered for additional surcharges.
[0106] According to one exemplary embodiment, only a single personalization may be selected by the sender client device 102A. In other words, if an image personalization is selected by the sender client device 102A, then all remaining personalizations which would include the text note, the audio recording, and video recording options may be disabled. However according to alternate exemplary embodiments, multiple personalizations could be offered and permitted as long as the sender client device 102A pays the additional surcharges associated with each personalization. According to a further alternate exemplary embodiment, personalizations could be bundled to provide discounts as incentives for the sender client device 102A to purchase multiple personalizations that may be associated with the gifted stored value account 142.
[0107] Referring back to block 1618 of FIG. 16A, the client device management server 106 may receive the one or more selections for the personalizations of the stored value account 142 that may be purchased by the sender client device 102A.
[0108] At block 1619, the client device management server 106 may display a plurality of options for minigifts that may be sent with stored value account 142. Minigifts may include the ability of the sender client device 102A to include one or more of the following digital elements to be associated with the stored value account 142 that will be sent to the recipient client device 102B as part of the gifted stored value account 142: electronic games, ring tones, video, music, and other like digital elements.
[0109] Next, in block 1620, selection(s) of the minigifts that may chosen by the user of the sending client device 102A may be received. One or more minigifts may be selected by a user of the client device 102.
[0110] At block 1621, the client device management server 106 may display a user interface that prompts the operator of the sender client device 102A to confirm the purchase of the selected stored value account 142 and its corresponding virtual token 702 and any personalizations selected using the sender client device 102A. Also at block 1621, the client device management server 106 may receive the confirmation for purchase of the stored valued account 142 from the sender client device 102A. The process 1600 then proceeds from FIG. 16A to the continuation flow chart of FIG. 16B.
[0111] FIG. 16B is a second flowchart 1600B that is a continuation of the first flowchart 1600A illustrating the method 1600 for creating and managing a stored value account 142 with a client device 102. At block 1623, a routine or sub-method for the client device management server 106 issuing a stored value account purchase request to the sender funding source 118 is provided. This routine or sub-method at block 1623 provides the details on how funds are transferred between the funding account associated with the sender client device 102A and the client device management server 106. The routine or sub-method of block 1623 is discussed in further detail below in connection with FIG. 17. The stored value account 142 may be purchased by the sender client device 102A by using a credit card, a checking account, PAYPAL® brand electronic payments, AMAZON® brand electronic payments, GOOGLE® Checkout brand payments, GREEN DOT® electronic payments, REVOLUTION CARD® brand card payments, and other like forms of payment.
[0112] After block 1623, in decision block 1627, the client device management server 106 determines if the funding provided by the sender client device 102A has been approved by its funding source 118. If the funding source 118 does not provide an approval for the purchase of the stored value account 142 by the sender client device 102A, then the process 1600 proceeds to transition oval 1625 (technically not a block--a transition oval) in which the method is returned to block 1621 of FIG. 16A.
[0113] If the funding source 118 provides an approval message to the client device management server 106, then the process 1600 proceeds to block 1629 in which the client device management server 106 creates the client unique identifier 155 for associating with the stored value account 142B as illustrated in FIG. 2. This stored value account 142B corresponds to the recipient client device 102B. Proceeding to block 1631, the client unique identifier 155 is stored in memory such as in the database 136 and memory 132 of the client device management server 106, as illustrated in FIG. 3.
[0114] Next, in block 1633, the client device management server 106 sends each of the client unique identifier 155, the amount of value purchased for the stored value account 142, and a merchant identifier associated with the stored value account 142 to the stored value account issuer server 108B. The merchant identifier may comprise an alphanumeric string.
[0115] At block 1635, the stored value account issuer server 108B creates the primary account number ("PAN") 165 as illustrated in FIG. 2 that is associated with the stored value account and other data received from the client device management server 106. If the stored value account 142 is unbranded, then it is assigned to an unbranded account 160. In the unbranded scenario, the stored value account issuer server 108B also does not create a PAN 165 and only associates the unbranded account 160 with the client unique identifier 155 and its corresponding value which was purchased by the sender client device 102A, as illustrated in FIG. 2.
[0116] Proceeding to block 1637, the client device management server 106 sends a notice to the recipient client device 102B. This notice may be delivered by a text message if the sender client device 102A only provided a mobile telephone number for the recipient client device 102B. Alternatively, this notice may be delivered by an e-mail message from the client device management server 106 if the sender client device 102A provided the e-mail address associated with the recipient client device 102B. This notice may take the format as illustrated in screen 600 of FIG. 6.
[0117] If the notice is delivered by an e-mail message, then this e-mail message may include a hypertext link comprising a universal resource locater ("URL") that directs a browser to a website that prompts the user of the recipient client device 102B to activate the stored value account 142. Similarly, if the notice is delivered by a text message to a mobile recipient client device 102B, then the notice may identify a sender of the virtual gift card account 142, what merchant 120 is associated with the virtual gift card account 142, and a URL hypertext link that may take the user to the activation website.
[0118] The website for activating the gifted stored value account 142 may include the following elements: the name of the user associated with the sender client device 102A, the name of a merchant 120 selected by the sender client device 102A, the value of the gifted stored value account 142, instructions for activating the stored value account 142 such as downloading software for a mobile client device 102 like as a mobile telephone, and frequently asked questions ("FAQs"). The FAQs may address common questions a recipient may have as to the authenticity of the stored value account 142 and/or redemption methods for the stored value account 142.
[0119] The activation website may include any of the personalizations that were selected by the sender client device 102A. For example, the activation website may include hypertext links to the audio or video recording selected by the sender client device 102A. The activation website may also display the text message selected by the sender client device 102A.
[0120] At block 1639, a routine or sub-method may be executed for receiving funds in the escrow account 136 of the client device management server 106 and which are associated with the stored value account 142 for the recipient client device 102B that is purchased. This routine may occur at the end of a business day under a credit card purchase model. However, this routine may be performed much earlier in the process 1600 under other funding models, such as a debit model in which the funding source 118 is a personal identification number ("PIN")-debit issuer for the client device 102B. Further details of this routine at block 1639 are described below in connection with FIG. 18.
[0121] Proceeding to decision block 1641, the client device management server 106 determines if the recipient client device 102B has activated the stored value account 142. Activation of the stored value account 142 generally means that an operator of the recipient client device 102B has become a subscriber of the mobile wallet system 114 that is maintained by the client device management server 106, and the recipient client device 102B has viewed the stored value account 142 through the mobile wallet system 114. If the recipient client device 102B is already a subscriber of the mobile wallet system 114, then activation may include a user of the recipient client device 102B viewing the stored value account 142 through the mobile wallet system 114, as illustrated in FIG. 8.
[0122] If the stored value account 142 is activated in decision block 1641, then the process 1600 proceeds to block 1643 transition oval in which the method is taken to step 1657 of FIG. 16c. If the stored value account 142 is not activated in decision block 1641, then the process 1600 proceeds to block 1645 in which the client device management server 106 sends a notice to the sender client device 102A to indicate that the stored value account 142 has not been activated by the recipient client device 102B. This notice to the sender client device 102A may also present an option for the sender client device 102A to resend a notice about the gifted stored value account 142 through another communication channel such as through an e-mail message or mobile telephone text message.
[0123] If the sender client device 102A decides to resend another notice to the recipient client device 102B, then the client device manager server 106 may set a predetermined amount of time in which the recipient client device 102B will need to respond to the subsequent notice. According to one exemplary embodiment, this predetermined amount of time set by the client device management server 106 may be 72 hours. However, other lengths of time are within the scope of the invention. At the expiration of the predetermined amount of time, additional notices may be sent to the sender client device 102A to indicate that the recipient client device 102B has not activated the gifted stored value account 142.
[0124] After block 1645, the process 1600 proceeds to block 1647 of FIG. 16C. FIG. 16c is a third flowchart 1600C that is a continuation of the second flowchart 1600B illustrating the method 1600 for creating and managing a stored value account with a client device. At block 1647, the client device management server 106 may send additional notices to the recipient client device 102B. At decision block 1651, if a predetermined number of notices have been sent to the recipient client device 102B and the recipient client device 102B has not activated the gifted stored value account 142, then the process 1600 may proceed to block 1653. At decision block 1651, if the predetermined number of notices have not been sent to the recipient client device 102B, then the process 1600 may proceed to block 1649 in which the method returns to decision block 1641 of FIG. 16B.
[0125] The client device manager server 106 may establish in decision block 1651 a predetermined number of notices which must be sent to a recipient client device 102B prior to allowing the sender client device 102A to have additional options with respect to handling the gifted stored value account 142. This predetermined number may be of any magnitude such as three or four, or any number. At block 1653, the sender client device 102A will be presented with an option to retain the purchased stored value account 142 for his or her benefit. After block 1653, the process 1600 proceeds to block 1655 in which the method proceeds to block 1661 of FIG. 16c.
[0126] At block 1659, the client device management server 106 may transmit an activation message to the sender client device 102A that the recipient client device 102B has activated the gifted stored value account 142. This activation message transmitted to the sender client device 102A may contain the following elements: a time date stamp, the merchant 120 associated with the stored value account 142, the recipient's name, the recipient's e-mail address, the purchased value for the stored value account 142, the transaction amount for the purchase of the stored value account 142, and an authorization code generated by the stored value account issuer server 108B.
[0127] Proceeding to block 1661, the client device management server 106 may display the stored value account 142 to the recipient client device 102B after the stored value account 142 has been activated at block 1641.
[0128] The process 1600 may proceed to decision block 1669 of FIG. 16D. FIG. 16D is a fourth flowchart 1600D that is a continuation of the third flowchart 1600C illustrating a method 1600 for creating and managing a stored value account 142 with a client device 102. At decision block 1669, the client device management server 106 may determine if the operator of the recipient client device 102B desires to exchange the gifted stored value account 142 for another stored value account 142 that may or may not be different relative to the gifted stored value account 142. In other words, at this stage, the client device management server 106 may determine if the recipient client device 102B desires to exchange a gifted stored value account 142 associated with a first merchant 120 for another stored value account 142 associated with a different second merchant. As described above, screen 900 (FIG. 9) includes an "Exchange" button 908 through which the user may indicate a desire to perform an exchange operation.
[0129] If the operator of the recipient client device 102B does not desire to exchange the gifted stored value account 142, then block 1671 is skipped and the process 1600 proceeds to block 1673. However, if the operator of the recipient client device 102B does desire to exchange the gifted stored value account 142 for another brand, then the process 1600 may continue to block 1671 in which an exchange routine or sub-method is executed. Further details of the stored value account exchange routine of block 1671 are described in further detail below in connection with FIG. 19.
[0130] At block 1673, the client device management server 106 may receive a request from the recipient client device 102B to redeem the value associated with the stored value account 142 in order to purchase goods or services. The recipient client device 102B may redeem the value of the stored value account 142 at a point-of-sale ("POS") terminal, on-line at a website, or using a telephone system. As described above with regard to FIG. 9, a user may select a "Present to Cashier" button 902 or a "Present Online" button 904 to indicate a desire to redeem the value of the stored value account 142.
[0131] At block 1675, the client device management server 106 may transmit the stored value account information to the recipient client device 102B over the communications network 105. If the recipient client device 102B is a mobile telephone, then the client device management server 106 may transmit the data associated with screen 1000A, 1000B or 1000C (FIGS. 10A-10C). If the recipient client device 102B is a laptop or desktop computer, then the client device management server 106 may transmit the data associated with screen 1000B, including instructions for entering the stored value account 142 into an e-commerce site, such as what card type to select on the e-commerce site as well as what to enter for any verification codes usually associated with a physical card or physical token.
[0132] Next, at block 1677, the client device management server 106 may record the date and time of the presentment of the stored value account 142 for redemption as requested by the sender client device 102B. At block 1679, the merchant 120 using its point-of-sale terminal or through its website may issue a redemption request corresponding to the stored value account 142 to the merchant acquirer 116B as illustrated in FIG. 1. Alternatively, in certain situations for a merchant 120 which does not use a merchant acquirer 116B, the redemption request may be sent over the communications network 105 that may comprise sub-network within the communications network 105, like the DISCOVER® brand credit card communications network. In this situation, block 1677 may be skipped when the merchant 120 communicates directly with the stored value account processor server 108A. This redemption request may comprise the 16-digit PAN 165, the expiration date for the stored value account 142, and a verification number.
[0133] Proceeding to block 1681, the merchant acquirer 116B may send the redemption request over the communications network 105 to the stored value account processor server 108A. As noted previously, the merchant acquirer 116 be may have access to specific proprietary sub-networks within the communications network 105 such as the VISA® credit card network, the MASTERCARD® card network, the DISCOVER® credit card network, the AMERICAN EXPRESS® credit card network, and other similar charge card proprietary networks.
[0134] Subsequently, at block 1683, the redemption request is received by the stored value account processor server 108A from the communications network 105. Also at block 1683, the stored value account processor server 108A will check the balance of the stored value account 142 associated with the PAN 165 that corresponds with the sender client device 102B. At this stage the stored value account processor server 108A is determining if the value associated with the stored value account 142 is greater than or equal to the redemption request. After block 1683, the process 1600 proceeds to block 1685 FIG. 16E.
[0135] FIG. 16E is a fifth flowchart 1600E that is a continuation of the fourth flowchart 1600D illustrating a method 1600 for creating and managing a stored value account 142 with a client device 102. If at block 1683 in FIG. 16D, the stored value account processor server 108A determines that the value associated with the stored value account 142 is greater than or equal to the redemption request, then the stored value account processor server 108A will generate and send an authorization message over the communications network 105 to the merchant acquirer 116B at block 1685. However, if the stored value account processor server 108A determines at block 1683 that the value associated with the stored value account is less than the redemption request, then the stored value account processor server 108A will generate and send a denial message over the communications network 105 to the merchant acquirer 116B at block 1685.
[0136] Proceeding to block 1687, the point-of-sale terminal, e-commerce website, or phone system will receive the authorization code or denial message from the communications network 105. If an authorization code was received, then the point-of-sale terminal, e-commerce website, or phone system will allow the purchase of the good(s) and/or service(s) based on the redemption request. If the point-of-sale terminal, e-commerce website, or phone system receives a denial message from the merchant acquirer 116B, then the user of the recipient client device 102B will not be permitted to purchase the good(s) and/or service(s).
[0137] At block 1691, usually at the end of a business day such as in the evening hours, a merchant 120 will settle their daily purchases and send a settlement request to the merchant acquirer 116B. The merchant acquirer 116B will generally pass on this settlement request over the communications network 105 to the stored value account processor server 108A.
[0138] Next at block 1693, the stored value account processor server 108A will transfer funds associated with any stored value account purchases from the client device management escrow account 136 to the merchant's demand deposit account 121. The process 1600 then ends.
[0139] FIG. 17 is a flowchart illustrating a routine or a sub-method 1623 of FIG. 16 for processing a stored value account purchase request. Commencing at block 1705, the client device management server 106 receives a purchase request from the sender client device 102A for purchasing the selected stored value account 142. At block 1705, the client device management server 106 may send an authorization request to its client device management ("CDM") acquirer 116A as illustrated in FIG. 1. Next, at block 1710, the client device management ("CDM") acquirer 116A may forward the authorization request over the communications network 105 to the sender funding source 118. Like the merchant acquirer 116B noted above, the CDM acquirer 116B may have access to specific proprietary sub-networks within the communications network 105 such as such as the VISA® credit card network, the MASTERCARD® card network, the DISCOVER® credit card network, the AMERICAN EXPRESS® credit card network, and other similar charge card proprietary networks.
[0140] At block 1715, the sender funding source 118 may receive the authorization or purchase request from the CDM acquirer 116A. If there are sufficient funding sources, meaning that an account associated with the sender client device 116A has available funds which are equal or greater than the value listed in the purchase request, then the sender funding source 118 may improve the authorization request or stored value account purchase request.
[0141] The sender funding source 118 may comprise any one of a plurality of financial institution types. For example, the sender funding source 118 may include, but is not limited to, a credit card issuer (that may support proprietary credit card networks such as the such as the VISA® credit card network, the MASTERCARD® card network, the DISCOVER® credit card network, the AMERICAN EXPRESS® credit card network, and other similar charge card proprietary networks), a signature debit issuer, and a pin-debit issuer. One of ordinary skill the art recognizes that depending upon the issuer and corresponding network that is supported, an acquirer such as the CDM acquirer 116A may or may not be needed. Similarly, one of ordinary skill the art recognizes that under a debit model, settlement or transfer of funds from the funding source 118 occurs almost immediately, which is contrary to the end of the day settlement processes that generally occur with credit card type transactions.
[0142] At block 1720, assuming that sufficient funds are available at the funding source 118, the funding source 118 may send an authorization for the purchase request or authorization request over the communications network 105 to the CDM acquirer 116A. If sufficient funds are not available at the funding source 118, then the funding source 118 may send a denial message over the communications network 105.
[0143] At block 1725, the client device management server 106 may receive an approval message from CDM acquirer 116A if sufficient funds were available at the funding source 118. Alternatively, at block 1725, the client device management server 106 could receive a denial message from the CDM acquirer 116A. The process 1600 then returns to decision block 1627 in FIG. 16B.
[0144] Referring now to FIG. 18, this figure is a flowchart illustrating a routine or a sub-method 1639 of FIG. 16 for processing receiving funds in an escrow account 136 of a client device management server 106. As noted previously, the settlement of funds between the funding source 118 and the escrow account 136 of the client device management server 106 will be dependent upon the type of funding source 118 that is associated or being used by the sender client device 102A.
[0145] If the funding source 118 comprises some form of debit system, then many of these steps illustrated in FIG. 18 may be changed or deleted as is understood by one of ordinary skill in the art. For the exemplary embodiment described in connection with FIG. 18, it is assumed that the funding source 118 comprises some form of a credit card model that uses proprietary networks within the communications network 105 and which may require the client device management acquirer 116A.
[0146] At block 1805, the client device management server 106 sends a periodic, typically a nightly, batch transaction request to the CDM acquirer 116A. The CDM acquirer 116A relays the batch transaction request over the communications network 105 at block 1810. At block 1815, the sender funding source 118, which may comprise a credit card issuer, may route the funds, such as communicating a credit to a merchant account corresponding to the batch request to the CDM acquirer 116A over the communications network 105.
[0147] The sender funding source 118, at block 1820, may also send an authorization over the communications network to the CDM acquirer 116A that authorizes the CDM acquirer 116A to transfer the funds from the CDM acquirer 116A to the escrow account 136 of the client device management server 106. At block 1825, the escrow account 136 may receive the funds from the CDM acquirer 116A. As noted previously, this transfer of funds between the CDM acquirer 116A and the escrow account 136 usually takes place at the end of the business day under a credit card model. This means that this subroutine or sub-method 1639 may actually occur much later in the overall process 1600 than is described above. Meanwhile, if the subroutine or sub-method 1639 operates under a debit model, then the funds may be transferred immediately between accounts. The process 1600 then returns to decision block 1641 of FIG. 16B.
[0148] Referring now to FIG. 19A, this figure is a flowchart 1671A illustrating a routine or a sub-method 1671 of FIG. 16 for exchanging a stored value account 142. Starting with block 1905 of routine 1671, the client device management server 106 may send instructions to the recipient client device 102B for exchanging stored value account 142.
[0149] Next, at block 1910, the client device management server 106 may acquire a location of the recipient client device 102B if the client device 102B comprises a mobile device such as a mobile telephone. At block 1915, the client device management server 106 may send information relating to the selected stored value account 142 that is to be exchanged, such as the then-current amount of value owned or associated with the recipient client device 102B.
[0150] At block 1935, the client device management server 106 may send the stored value account(s) 142 associated with particular merchants 120 that are available for exchange. The client device management server 106 may generate and send a user interface such as screen 1100 of FIG. 11. As described above with regard to FIG. 11, screen 1100 includes merchant icons 1102 from which the user may select. Each merchant icon 1102 may correspond to one of the stored value accounts 142 associated with merchants 120 available for exchange. At block 1940, the client device management server 106 may receive a selection of a new stored value account(s) 142 from the recipient client device 102B.
[0151] At block 1945, in response to the recipient client device 102B confirming the selection of a new stored value account 142 to be acquired in the exchange, the client device management server 106 may calculate an exchange rate or fee that may incorporate or weigh (consider) the location of the recipient client device 102B. Further information about this exchange rate calculation of block 1945 will be discussed in detail below in connection with FIG. 19c.
[0152] Then, at block 1950, the client device management server 106 may send the calculated exchange fee and other information relating to the selected new stored value account 142 for display through a user interface, such as screen 1200 of FIG. 12. The exchange fee may be presented in the listing of the exchange details of the screen 1200, as described above with regard to FIG. 12. The process then proceeds to decision step 1955 of FIG. 19B.
[0153] FIG. 19B is a second flowchart 1671B that is a continuation of the flowchart of flowchart 1671A (FIG. 19A) illustrating a routine or a sub-method 1671 for exchanging a stored value account. At decision block 1955, the client device management server 106 may determine if the operator of the recipient client device 102B desires to proceed with the selected stored value account exchange. At block 1955, the client device management server may present a user interface such as screen 1200 of FIG. 12, which prompts a user of the recipient client device 102B to either select the "Submit" button 1204 to proceed with the exchange operation or select the "Cancel" button 1206 to continue without performing the exchange operation, i.e., to cancel the exchange operation. If the exchange operation is canceled, then the process may proceed to step 1960 in which the process may return back to decision block 1669 of FIG. 16D.
[0154] In response to selecting the "Submit" button 1204 to confirm the exchange operation, the process 1600 may continue to block 1961. At block 1961, the client device management server 106 receives a message from the client device 102B confirming the exchange operation.
[0155] At block 1962, the client device management server 106 sends a message to the stored value account issuer server 108B to create one or more new PAN(s) 165 in the database 146 and to allocate funds corresponding to the new PAN(s).
[0156] At block 1963, the client device management server 106 sends the client device 102B information associated with the selected new stored value account 142, such as the graphical representation of the new virtual token 1202 (FIG. 12). At block 1964, the client device 102B displays an animation depicting a transition from the virtual token 702 to the new virtual token 1202, as described above with regard to FIGS. 13-15. The process 1600 then may return to block 1673 of FIG. 16D.
[0157] A recipient client device 102B having more than one stored value account associated with a particular brand of merchant 120, meaning that the recipient client device 102B has more than one PAN 165 that may be associated with a single merchant 120, may merge such stored value accounts 142 into a single account 142 having a single PAN 165. Any personalization(s) associated with each of the separate stored value accounts 142 will be transferred to the consolidated stored value account 142. According to one exemplary embodiment, once multiple stored value accounts 142 are merged, they typically will not be able to be separated into different accounts 142.
[0158] As noted previously, the calculation of the exchange fee at block 1945 in the exchange sub-method or routine 1671 may be governed by one or more different equations. According to one exemplary embodiment, the resulting value (R) of the desired stored value account 142 may be determined by the following equation:
R=[(F×O)+(F×X)]/(1-D) (EQ. 1)
[0159] where R is the resulting value of the desired or destination stored value account 142; F is the current face value of the original stored value account 142 to be exchanged; O is the discount rate negotiated with the merchant of the original stored value account 142 that will be exchanged; X is the exchange rate set by the client device management server 106; and D is the discount rate charged to the merchant 120 of the desired or destination stored value account 142.
[0160] Referring now to FIG. 19c, this FIG. is a table 1975 that illustrates exemplary exchange rates for stored value accounts 142 that may be provided to a user of a client device 102. The table 1975 may have an original stored value account column 1977, and a destination or desired stored value account column 1979. In the first column 1977, a first discount rate 1981 which corresponds to the "O" variable in the exemplary equation discussed above is presented. A plurality of second discount rates 1986 which correspond to the "D" variable of the exemplary equation EQ. 1 described above may be presented. The resulting values "R" 1987 that are calculated by the client device management server 106 are presented adjacent to the second discount rates 1986. The resulting values "R" 1987 will be the value associated with the new or desired stored value account 142 that will be created under an exchange.
[0161] Merchants 120 may be able to dynamically set the discount rates 1986 which correspond to the variable "D" in the equation described above. The merchants 120 may set these discount rates 1986 to encourage more users of the recipient client devices 102B to exchange existing stored value accounts 142 associated with different merchants 120 to their brand.
[0162] Further, as discussed above, the merchants 120 may tie or associate the discount rates 1986 based on the relative location of the recipient client device 102B. For example, a merchant 120 could offer a significantly higher discount rate 1986 if the recipient client device 102B is physically located near or adjacent to the premises of the merchant 120. The discount rates 1986 may also be adjusted higher if the client device 102B happens to be physically located within the premises of a merchant 120, such as inside a brick-and-mortar store owned by the merchant 120.
[0163] By offering significant discount rates 1986, it is possible for a recipient client device 102B to exchange an existing or original stored value account 142 that has a first value to a desired stored value account 142 which has a second value that is higher than the first value. Long-term, merchants 120 will be able to dynamically set the discount rates 1986 to encourage more consumers to "exchange" one brand for the merchant's brand at any given time of day.
[0164] This level of dynamic pricing may begin to mimic a liquid market for stored value account s142 that may operate in much the same way as foreign exchange markets may perform today. The client device management server 106 may take on the role of a "market maker" allowing merchants 120 and the recipient client devices 102B to find a relative equilibrium exchange rate between any two merchant brands with enormous implications for delivery of value-added services and market insight.
[0165] As noted previously, the inventive system 100 may provide merchants 120 with the ability to know the buying characteristics and trends by the users of the stored value account 142. The client device management server 106 may generate many different types of reports for the benefit of merchants 120 who are associated with stored value accounts 142 that are held by one or more recipient client devices 102B.
[0166] Such reports generated by the client device management server 106 may include, but are not limited to the following usage data: the current stored value account volume associated with a particular brand of a merchant 120 with an average count per recipient client device 102B of the number of stored value accounts 142 held by a particular recipient client device 102B; current stored value account volume associated with a particular brand of merchant 120 with an average volume per recipient client device 102B; presentation/redemption totals on a regional basis; presentation/redemption totals at a per location bases; and presentation/redemption breakdown by channel (retail, online, and phone transactions). Stored value account usage trending reports may be offered by the client device management server 106 as a premium offering to merchants 120 and may have a configurable surcharge associated with such trending reports.
[0167] The client device management server 106 may also provide reports that convey stored value account behavior trending. Such reports may include, but are not limited to, the following usage data: current stored value account numbers associated with the brand of a particular merchant 120; the current total stored value account volume associated with the brand of a particular merchant 120; month-over-month rate increases or decreases associated with the brand of a particular merchant 120; month-over-month rate of exchanges to and from a brand of a particular merchant 120; a percentage of the stored value accounts 142 being shared with a breakdown of a number of the shared participants; a percentage of stored value accounts 142 being re-gifted; and a percentage of the stored value account 142 being reloaded with a breakdown of the average amount of value being added. Stored value account behavior trending reports may be offered by the client device management server 106 as a premium offering to merchants 120 and may have a configurable surcharge associated with such behavior reports.
[0168] The client device management server 106 may also provide reports that convey personal characteristics of the users of the stored value accounts 142. Such reports may include, but are not limited to, the following data: the average age of a user of a client recipient device 102B associated with a brand of the merchant 120; a gender breakdown of recipient client devices 102B holding at least one stored value account 142 associated with a brand of a particular merchant 120; a regional distribution breakdown a stored value accounts 142; an average monthly overall stored value account balance for recipient client devices 102B having at least one stored value account 142 associated with a particular brand of a merchant 120; and an average monthly stored value account redemption for client recipient devices 102B having at least one stored value account 142 associated with a particular brand of a merchant 120. Personal characteristics reports may be offered by the client device management server 106 as a premium offering to merchants 120 and may have a configurable surcharge associated with such personal characteristics reports.
[0169] Certain steps in the processes or process flows described in this specification naturally precede others for the invention to function as described. However, the invention is not limited to the order of the steps described if such order or sequence does not alter the functionality of the invention. That is, it is recognized that some steps may performed before, after, or parallel (substantially simultaneously with) other steps without departing from the scope and spirit of the invention. In some instances, certain steps may be omitted or not performed without departing from the invention. Further, words such as "thereafter", "then", "next", etc. are not intended to limit the order of the steps. These words are simply used to guide the reader through the description of the exemplary method.
[0170] Additionally, one of ordinary skill in programming is able to write computer code or identify appropriate hardware at circuits to implement the disclosed invention without difficulty based on the flow charts and associated description in this specification, for example.
[0172] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer.
[0173] Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line ("DSL"), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
[0175] Although selected aspects have been illustrated and described in detail, it will be understood that various substitutions and alterations may be made therein without departing from the spirit and scope of the present invention, as defined by the following claims.
Patent applications by Krishnakanth S. Chimalamarri, Atlanta, GA US
2012-03-22 System and method for collection and communication of data from multiple patient care devices
2012-03-22 Agent referral system and method with integrated buyer, lender, and agent communication
2012-03-22 Method of selling a custom product as an over-the-counter commodity item
2013-08-08 Virtual ruler