Patent Grant
9864986
Consumers today use many types of payment cards (e.g., credit cards, debit cards, prepaid gift cards) and other payment objects (e.g., a smartphone with a digital wallet or a card with a quick response (QR) code) to make purchases. Consumers may carry multiple payment cards or other payment objects for a variety of reasons, however, some consumers find carrying such an array of payment options inconvenient and burdensome. For example, all these multiple payment cards may add to an overstuffed wallet or purse, making it difficult for the consumer to find a particular payment card. As another example, the consumer may misplace or forget a payment card, such as a gift card, and may not have the card when needed to pay for a purchase.
Embodiments of the present invention will be described and explained through the use of the accompanying drawings in which:
In this description, references to “an embodiment”, “one embodiment” or the like, mean that the particular feature, function, structure or characteristic being described is included in at least one embodiment of the technique introduced here. Occurrences of such phrases in this specification do not necessarily all refer to the same embodiment. On the other hand, the embodiments referred to also are not necessarily mutually exclusive.
This application discloses a technique and related technology for associating monetary value cards with a payment object, for example a credit or debit card, to enable a consumer to use the payment object for a financial transaction that is paid for with funds of the monetary value card. A monetary value card is a payment card that is not issued in the name of any person or entity, but rather can be used by any person to make a payment. Further, a monetary value card has no associated credit account or credit funds, but rather has an associated zero or positive monetary value that is stored at a financial account associated with the monetary value card, or that is stored on the card itself. Examples of monetary value cards include gift cards and stored-value cards. A person, such as a purchaser of a monetary value card, can add funds to the monetary value of the monetary value card by, for example, providing funds to a merchant that sells the monetary value card. The merchant can add the funds, less any associated fees, to the monetary value of the monetary value card.
The disclosed technology enables a consumer to make a payment in a financial transaction, by using funds of a monetary value card without having to carry the monetary value card, thereby providing greater convenience to the consumer and avoiding adding to the consumer's possibly overstuffed wallet.
Consider the following illustrative use case. A consumer receives a gift card as a gift. He uses the gift card at a merchant to purchase a cup of coffee, where the merchant swipes the gift card using a card reader associated with a point-of-sale (POS) system. The POS system initiates processing of the purchase payment by sending transaction information, such as the cost of the purchase, and gift card information, such as information obtained from the gift card by the card reader, to a payment service system, which can be a computer system that is part of a financial system or that is separate from the financial system. For this illustrative case, the payment service system is separate from the financial system, The payment service system processes a payment for the purchase, such as by sending a message to the financial system to cause funds for the purchase to be obtained based on the monetary value of the gift card. The financial system causes funds for the purchase to be debited from a financial account associated with the gift card, and credited to a financial account associated with the merchant.
The term “cause” and variations thereof, as used in the preceding paragraph and elsewhere in this description, refers to either direct causation or indirect causation. For example, a computer system can “cause” an action by sending a message to a second computer system that commands, requests or prompts the second computer system to perform the action. Any number of intermediary devices may examine and/or relay the message during this process. In this regard, a device can “cause” an action even though it may not be known to the device whether the action will ultimately be executed or completed.
Further, any references to sending or transmitting a message, signal, etc. to another device (recipient device), as used above and elsewhere in this description, means that the message is sent with the intention that its information content ultimately be delivered to the recipient device; hence, such references do not mean that the message must be sent directly to the recipient device. That is, unless stated otherwise, there can be one or more intermediary entities that receive and forward the message/signal, either “as is” or in modified form, prior to its delivery to the recipient device. This clarification also applies to any references herein to receiving a message/signal from another device; i.e., direct point-to-point communication is not required unless stated otherwise herein.
Additionally, the term “swipe” herein refers to any manner of triggering a card reader to read a card, such as passing a card through a magnetic stripe reader, smartcard reader, optical code reader, radio frequency identification (RFID) reader, etc. The term “card reader” herein refers to any object that can be used to obtain information from an object used to make an electronic payment where the card reader must be in the general vicinity of the object, such as an optical scanner, a near field communications device, a Bluetooth communications device, etc.
Continuing with the illustrative use case, the payment service system sends a message to the POS system that prompts the POS system to display a message asking the consumer whether he would like an electronic receipt for his purchase. The consumer indicates that he would like an electronic receipt, and enters personal information, such as his phone number or email address, to indicate where the electronic receipt should be sent. The payment service system, based on the personal information, determines that the consumer has a credit card, such as by performing a database search based on the email address or phone number to determine if either is associated with a consumer and/or a credit card. The payment service system sends a message to the POS system that prompts the POS system to display a message asking if the consumer would like to link (associate) the gift card with his credit card. The consumer indicates an affirmative response, and the payment service system links the gift card to the consumer's credit card via a database association.
At a later time, the consumer visits another merchant to purchase some goods. The consumer brings the goods to a checkout stand and presents the same credit card to the merchant to pay for the purchase. The merchant swipes the credit card using a card reader associated with a second POS system. The second POS system initiates processing of the purchase payment by sending transaction information, such as the cost of the purchase, and credit card information, such as information obtained from the credit card by the card reader, to the payment service system. The payment service system, based on the credit card information, determines that the gift card is associated with the credit card.
The payment service system sends a message to the second POS system to prompt the second POS system to display a message notifying the consumer that he has a gift card linked to his credit card, and asks the consumer if he would like to use the gift card for the purchase. The consumer indicates an affirmative response, and the payment service system processes a payment for the purchase based on the gift card. For example, the computer system sends a message to a financial system to cause funds for the purchase to be obtained based on the monetary value of the gift card. The financial system causes funds for the purchase to be debited from a financial account associated with the gift card, and credited to a financial account associated with the merchant.
In the following description, the example of a merchant selling goods to a customer is used, for illustrative purposes only, to explain various aspects of the technique introduced here. Note, however, that the technique is not limited in applicability to merchants and customers, nor to the sales of goods. The technique can be utilized with essentially any transaction that traditionally would be initiated by or involve the use of a card reader. Hence, the term “sale”, as in point-of-sale (POS) for example, refers to any type of payment-oriented transaction, including for example a lease, a rental, or services, and is not limited to an actual purchase. Note also that in this description the terms “customer” or “payer” generally refer to the person (or other entity) making the payment related to the transaction, while “merchant” or “payee” generally refer to the person (or other entity) receiving the payment related to the transaction.
In contrast, a monetary value card is a payment card that is not issued in the name of any person or entity, but rather can be used by any person who rightfully has possession of the card to make a payment. Further, a monetary value card has no associated credit account or credit funds, but rather has an associated zero or positive monetary value that is stored at a financial account associated with the monetary value card, or that is stored on the card itself. Examples of monetary value cards include gift cards and stored-value cards. A person, such as a purchaser of a monetary value card, can add funds to the monetary value of the monetary value card by, for example, providing funds to a merchant that sells the monetary value card. The merchant can add the funds, less any associated fees, to the monetary value of the monetary value card.
A monetary value card may not be associated with a defined set of people and/or entities who are authorized users of the monetary value card, and may resultantly not be a proxy card. For example, a monetary value card that can be used anonymously (referred to herein as an “anonymous monetary value card”) is not associated with a defined set of people and/or entities who are authorized users of the monetary value card, and is therefore not a proxy card. Like cash, an anonymous monetary value card can legally be used to pay for a financial transaction by anyone who rightfully has possession of the card.
For example, a first person who rightfully has possession of an anonymous monetary value card can physically give the card to a second person who is a stranger to the first person (i.e., the first person has no knowledge of the identity of the second person, and vice versa). The second person, now having rightful possession of the anonymous monetary value card, can rightfully use the card to electronically pay for a financial transaction. An anonymous monetary value card is not associated with a defined set of people or entities who are authorized users of the proxy card (i.e., there is no list of authorized users that is maintained), but rather any person who has rightful possession of the anonymous monetary value card can legally use the card.
A proxy card can be indicated in several ways. In a first example, a proxy card can be indicated based on meta-data of the proxy card. In the first example a first proxy card is similar to a credit card. The first proxy card has a magnetic stripe that can be read by a card reader that is compatible with payment cards such as credit cards, debit card, etc. The first proxy card can be indicated to be a proxy card by meta-data of the first proxy card, such as meta-data that is stored via a magnetic stripe of the first proxy card, and that can be read based on the magnetic stripe during a “swipe” of the first proxy card by the card reader. The meta-data can indicate that the first proxy card is a proxy card by, e.g., including data that enables an electronic payment based on the card to be routed to a computer associated with an internet protocol (IP) address or a phone number that is included in the meta-data.
A proxy card need not include meta-data that indicates that the card is a proxy card. As a second example, a proxy card can be indicated by association information that is stored at a computer. In the second example, a computer system has access to association information that is stored at a storage device. The association information associates payment card information with information that indicates whether the payment card is a proxy card. The payment card information is information obtained based on the payment card, such as information stored at the magnetic stripe of the payment card and that can be read by a card reader during a “swipe” of the payment card at the card reader. The payment card information can further, or alternately, include information that can be obtained by a visual inspection of the payment card, such as an account number that is visible on the proxy card.
A computer system that has access to the association information can obtain an indication whether a particular payment card is a proxy card based on the payment card information. For example, the computer system can access the stored association information based on the payment card information of the particular payment card, such as via a database access based on the payment card information. The database can return data that indicates whether the payment card is a proxy card, such as a listing of financial accounts that are associated with the payment card, or a simply a logical true or false that indicates whether the payment card is a proxy card. A computer system of a financial system, such as a computer system of financial system 160 of
When a proxy card is indicated to be a proxy card based on association information stored at a computer system, rather than based on meta-data of the proxy card, an electronic payment based on one of the accounts linked to the proxy card via the association information may need to pass through an intermediary computer system that has access to the association information, such as computer system 170 of
An example will be discussed. A payment card that is a credit card, a charge card, a debit card, or an automated teller machine (ATM) card can be a proxy card. In the example, a credit card was issued in the name of a user, and was associated with a credit account at the time of issue. Later, the user linked a second financial account to the credit card, such as a financial account associated with a debit card or a gift card, via a database stored at computer system 170 of
When an electronic payment is initiated, but does not pass through an intermediary computer system with access to the association information before passing to a financial system, the electronic payment cannot be based on one of the financial accounts that is associated with the credit card via the association information. For example, if an electronic payment is initiated based on the credit card of this example at either POS system 158B or POS sys 158C of
When an electronic payment is initiated and passes through an intermediary computer system with access to the association information before passing to a financial system, the electronic payment can be based on one of the financial accounts that is associated with the credit card via the association information. For example, if an electronic payment is initiated based on the credit card of this example at POS system 158A of
The example process illustrated in
The consumer presents proxy card 150 to a seller to pay for a purchase. The seller executes card swipe 105, which includes step 103, in which the seller swipes proxy card 150 through card reader 155, and step 108, in which card reader 155 transmits information obtained from proxy card 150 to POS system 158, a point-of-sales (POS) system to which card reader 155 is coupled (either directly or indirectly).
POS system 158 then begins the second phase, which is payment authorization 130. Payment authorization 130 includes steps for obtaining an authorization for the payment and includes steps 110, 115, 120, 125, and 180. Payment authorization 130 starts with step 110. At step 110 POS system 158 initiates transmission of information associated with proxy card 150, i.e., the proxy card information, to financial system 160. In this example, the proxy card information includes identifying information for the proxy card and meta-data which can be used to determine that proxy card 150 is a proxy card, among other purposes. POS system 158 is agnostic to what financial system 160 and proxy card 150 are. As far as POS system 158 can tell, proxy card 150 is no different than other payment cards, and sending information to financial system 160 for proxy card 150 is no different than sending information for other payment cards.
POS system 158 further transmits information associated with the purchase transaction, referred to herein as the transaction information, to financial system 160. The transaction information includes the amount of the transaction, and can further include information regarding the payee and individual line items from the transaction, among other information. At step 110, financial system 160 receives the proxy card information and the transaction information. At step 115, financial system 160 parses the meta-data and determines, based on the meta-data, to send a message to computer system 170. The message sent to computer system 170 at step 115 can include all or part of the proxy card information and the transaction information, among other information. The meta-data can include data such as an IP address or a phone number that indicate where the message should be sent.
Computer system 170, upon receiving the proxy card information, accesses a database access to obtain payment account information associated with proxy card 150. At step 180, computer system 170 applies an algorithm, which in some embodiments is customized by the consumer, to select the payment account to use for the purchase transaction. At step 120, computer system 170 transmits the transaction information and the payment account information to financial system 160, and financial system 160 determines the results of payment authorization 130 using the selected payment account. If the payment account has access to adequate funds for the payment, and no other issue exists, financial system 160 determines that the result of payment authorization 130 is that the payment is authorized.
If some issue exists, such as the payment account does not have access to adequate funds for the payment or the payment account has a fraud alert, financial system 160 determines that the result of payment authorization 130 is that the payment is declined. Other results, such as declining the purchase transaction and instructing the seller to take possession of the proxy card, or additional information, such as an authorization number, can be transmitted to financial system 160 at step 120. At step 125, financial system 160 transmits the results of payment authorization 130 to POS system 158.
In some embodiments, instead of financial system 160 determining and sending the results of payment authorization 130, computer system 170 determines and sends the results of the payment authorization. Computer system 170 decides the payment authorization based on information such as the consumer's credit reports or scores and the history of past payments processed by computer system 170. Computer system 170 sends the payment authorization results to POS system 158, or to financial system 160, which relays the results to POS system 158.
At this point, assuming that the purchase transaction was authorized and the consumer accepted the purchase transaction, the purchase transaction is complete and the consumer is free to walk out of the store with the purchased items. At a later time, for example when the consumer arrives at home, the consumer can optionally start phase 3, change of payment account 145. If the consumer does not utilize this phase, financial system 160 will transfer funds for the payment from the selected payment account to an account associated with the seller, such as by debiting the funds from the payment account and crediting the funds to the account associated with the seller. However, during this phase, the consumer can select a second different payment account from which funds to for the payment are to be obtained.
The consumer uses personal computing device 165, for example a smartphone or a laptop computer, to initiate change of payment account 145 which includes steps 135, 140, and 175. At step 135, personal computing device 165 communicates with computer system 170 to initiate change of payment account 145. At step 140, computer system 170 provides information regarding the purchase transaction to the consumer via personal computing device 165. Examples of the information provided include the date of the purchase, information regarding the seller, and the amount of the purchase. Computer system 170 further provides information regarding the payment accounts associated with proxy card 150 to the consumer via personal computing device 165. Computer system 170 has access to a database containing various information associated with proxy card 150, as well as information associated with the consumer and/or the payment accounts associated with proxy card 150.
When there are multiple payment accounts associated with proxy card 150, the consumer, using personal computing device 165, can select any payment account associated with proxy card 150 from which funds for the payment are to be obtained. At step 140, personal computing device 165 transmits information indicating the selection to computer system 170. After the selection is made, at step 175 computer system 170 transmits information related to the selection, such as identifying information for the selected payment account, to financial system 160, which causes financial system 160 to obtain funds for the purchase based on the selected payment account, such as by debiting the selected payment account. Computer system 170 additionally prevents the funds from being obtained from the initially selected payment account, such as by canceling the payment initially to be obtained from the initially selected payment account.
As a first example, object 250 can be proxy card 150 of
Object identifier 255 begins the second phase, which is payment authorization 230 and includes steps 210, 215, 220, 225, and 280. Payment authorization 230 includes the steps for obtaining authorization for the payment related to the purchase transaction. Payment authorization 230 starts with step 210. At step 210, object identifier 255 obtains object information associated with object 250. For example, a POS system obtains proxy card information from the proxy card. Step 210 continues with the transmission of the object information to financial system 160, for example the POS system transmits the proxy card information to financial system 160. Information related to the purchase transaction (i.e., the transaction information), such as the amount of the purchase, is also transmitted to financial system 160.
Object identifier 255 is, for example, a card reader which transmits the object information and the transaction information to financial system 160. Financial system 160 receives the transmitted information, and based on this information, decides to relay the transmitted information to computer system 170 for further processing. At step 215, financial system 160 relays the transmitted information, along with other information, to computer system 170.
For example, financial system 160 receives the transmitted proxy card information, which includes meta-data, and the purchase amount. Upon receiving the proxy card information, and based on the proxy card information, financial system 160 decides to relay the transmitted information to computer system 170. At this point in time, financial system 160 does not have the information needed to complete or authorize the purchase transaction, as financial system 160 without computer system 170 is not able to determine a payment account associated with the proxy card to use for the purchase transaction.
Computer system 170, upon receiving the proxy card information, accesses a database to obtain payment account information associated with the proxy card information. At step 280, computer system 170 applies an algorithm, which in some embodiments can be customized by the consumer, to select the payment account to use for the purchase transaction. The following are example algorithms which can additionally be used for step 180 of
For example, a consumer can use a proxy card to purchase gas and a snack item at a gas station as part of a single purchase transaction. For this purchase transaction, the payment account selection algorithm can select a gas credit card associated with the proxy card for the gas line item, and can select a VISA credit card associated with the proxy card for the snack line item. In some embodiments, the consumer can set, modify, or change the algorithm for selecting the payment account to use for a purchase transaction. In some embodiments, the algorithm is based on inputs received from the consumer.
At step 220, computer system 170 transmits the transaction information and the payment account information to financial system 160, and financial system 160 determines the results of payment authorization 230 using the selected payment account. If the payment account has access to adequate funds for the payment, and no other issue exists, financial system 160 determines that the result of payment authorization 230 is that the payment is authorized.
If some issue exists, such as the payment account does not have access to adequate funds for the payment or the payment account has a fraud alert, financial system 160 determines that the result of payment authorization 230 is that the payment is declined. Other results, such as declining the purchase transaction and instructing the seller to take possession of the proxy card, or additional information, such as an authorization number, can be transmitted to financial system 160 at step 220. At step 225, financial system 160 transmits the results of payment authorization 230 to object identifier 255.
In some embodiments, instead of financial system 160 determining and sending the results of payment authorization 230, computer system 170 determines and sends the results of the payment authorization. Computer system 170 decides the payment authorization based on information such as the consumer's credit reports or scores and the history of past payments processed by computer system 170. Computer system 170 can send the payment authorization results to object identifier 255, or can send the results to financial system 160, which can relay the results to object identifier 255.
At this point, assuming that the purchase transaction was authorized and the consumer accepted the purchase transaction, the purchase transaction is complete and the consumer is free to walk out of the store with the purchased items. At a later time, for example when the consumer arrives at home, the consumer can optionally start phase 3, change of payment account 245. If the consumer does not utilize this phase, financial system 160 will transfer funds for the payment from the selected payment account to an account associated with the seller. However, during this phase, the consumer can select a second different payment account from which funds for the payment are to be obtained.
The consumer uses personal computing device 165, for example a smartphone or a laptop computer, to initiate change of payment account 245, which includes steps 235, 240, and 275. At step 235, personal computing device 165 communicates with computer system 170 to initiate change of payment account 245. At step 240, computer system 170 provides information regarding the purchase transaction to the consumer via personal computing device 165. Examples of the information provided include the date of the purchase, information regarding the seller, and the amount of the purchase. Computer system 170 further provides information regarding the payment accounts associated with object 250 to the consumer via personal computing device 165. Computer system 170 has access to a database containing various information associated with object 250 as well as associated with the consumer and the payment accounts associated with object 250.
When there are multiple payment accounts associated with object 250, the consumer, using personal computing device 165, can select any payment account associated with object 250 from which funds for the payment are to be obtained. At step 240, personal computing device 165 transmits information indicating the selection to computer system 170. After the selection is made, at step 275 computer system 170 transmits information related to the selection, such as payment account information, to financial system 160. This causes financial system 160 to obtain funds for the payment from the selected payment account. Computer system 170 additionally prevents the funds from being obtained from the initially selected payment account, such as by canceling the payment from the initially selected payment account. The funds can correspond to the amount of the purchase, the amount of a line item, the amount of multiple line items, or some other amount corresponding to the purchase, and can be transferred to an account associated with the seller. The funds transferred can correspond to an amount by being for the amount less a transaction fee. Further, purchase transactions can be batched, and the funds can be for an amount corresponding to the amount of the batch of purchase transactions.
Object 250 is compatible with financial system 160. In various embodiments, object 250 can be a magnetic stripe card, a smart card, a proximity card, a re-programmable magnetic stripe card, an card containing an optical code such as a quick response (QR) code or a bar code, or a biometrically identifiable object, such as a finger, a hand, an iris, a retina, or a face, among others. Object 250 can be associated with various payment objects and payment object accounts, including accounts associated with credit cards, charge cards, ATM cards, debit cards, pre-paid credit cards, pre-paid debit cards, gift cards, pre-paid gift cards, stored value cards, and fleet cards, among others. The payment accounts can be associated with object 250 by, for example, being linked to object 250. The link can be implemented, for example, using a database which links object 250 with the payment accounts.
In an embodiment, object 250 is a proxy card implemented as a magnetic stripe card similar to a credit card. The proxy card has an account number similar to a credit card, but, unlike a credit card or debit card, the account number is not linked to a particular bank or credit union. Instead, swiping the proxy card, as one would swipe a credit card, triggers the sending of transaction information and proxy card information to a secondary payment processor. The secondary payment processor creates and maintains a database that links the proxy card with the payment accounts. A customer can link various payment card accounts with the proxy card by logging in to a website associated with the secondary payment processor, and entering information into the website that enables the link. For example, the account number of the proxy card, and the account number of a payment card can be entered, and the secondary payment processor can link the two.
Linking can be done by taking photos of the proxy card and the payment card and sending the photos to the secondary payment processor, which can obtain the information needed to link the cards from the photos. The photos can be taken by a mobile device, and an application running on the mobile device can send the photos to the secondary payment processor. Linking can be done by swiping the two cards through a card reader connected to the customer's mobile device, and sending the data obtained by the card reader to the secondary payment processor. An application running on the mobile device can obtain the information for the two card from the card reader, and can send the data obtained by the card reader to the secondary payment processor.
In some embodiments, the proxy card has a visible number on its face, similar to a credit card. In some embodiments, the proxy card has no visible number. In an embodiment with no visible number, information for the proxy card is obtained from the magnetic stripe of the proxy card. In some embodiments, information for the proxy card is obtained via Bluetooth Low Energy (BLE), near field communications (NFC), or other contactless payment mechanism embedded in the proxy card that triggers payment using a POS system.
Further, object 250 can be associated with loyalty programs, wherein the loyalty programs are another type of payment account which can be used to make the purchase. In some embodiments, object 250 can be a mobile device. Examples of mobile devices include smartphones, tablets, portable media devices, wearable devices, laptops, and other portable computers. In some embodiments, when object 250 is a mobile device, the mobile device includes a digital wallet application that triggers payment using a POS system.
Object identifier 255 can obtain information associated with object 250, where the information is part of the object information. In embodiments where object 250 is a magnetic stripe card or a re-programmable magnetic stripe card, object identifier 255 can read the magnetic stripe. In embodiments where object 250 is a smart card, object identifier 255 can communicate with the smart card to obtain information related to object 250. In embodiments where object 250 is a proximity card, object identifier 255 can cause the proximity card to transmit information associated with the proximity card, such as a radio frequency identification (RFID), which object identifier 255 can receive. In embodiments where object 250 is a card with an optical code such as a QR code or bar code, object identifier 255 can obtain the optical code, for example, by scanning the optical code. In embodiments where object 250 is a mobile device, object identifier 250 can communicate with the mobile device to obtain information related to object 250, such as via 3G, 4G, WiFi, Bluetooth, or BLE. Object identifier 255 can further transmit the object information to financial system 160.
Object identifier 255 can further include a sales system, such as POS system 158 of
In embodiments where object 250 is a biometrically identifiable object, such as a finger, a hand, an iris, a retina, or a face, object identifier 255 can identify the biometrically identifiable object or can obtain information from the biometrically identifiable object and can transmit that information to a computer system that can use the information to identify the biometrically identifiable object. For example, when the biometrically identifiable object is a finger, object identifier 255 can obtain data related to the fingerprint of the finger. In some embodiments, object identifier 255 can recognize the fingerprint to identify the finger (e.g., this is the finger of Jane Doe). For example, object identifier 255 can include a biometric scanner coupled to a computer system such as a POS system, wherein the biometric scanner can scan the consumer's fingerprint, can transmit the biometric scan results to the computer system to which the biometric scanner is coupled, and the computer system can use the consumer's fingerprint to identify the finger. In other embodiments, object identifier 255 can transmit the data related to the fingerprint to a second computer system, for example, to a compute server associated with the seller, to financial system 160, to computer system 170, or to another computer system, and the second computer system can use the transmitted fingerprint data to identify the finger. The second computer system can transmit identifying information associated with the finger to object identifier 255, where the identifying information is part of the object information. Object identifier 255 can further transmit the object information to financial system 160.
In embodiments where object 250 is a mobile device, object identifier 255 can obtain identifying information associated with the mobile device. In one example where object 250 is a smartphone, object identifier 255 can communicate with the smartphone via 3G to obtain identifying information related to a digital wallet associated with the smartphone, where the identifying information is part of the object information. Object identifier 255 in various embodiments can communicate with the mobile device via WiFi, 3G, 4G, Near Field Communication (NFC), or Bluetooth, or can obtain an optical code such as a QR code or a bar code or any machine readable code from the mobile device, for example, by scanning an optical code displayed by the mobile device. Object identifier 255 can further transmit the object information to financial system 160.
Personal computing device 165 can be a mobile device. Examples of mobile devices include smartphones, tablets, portable media devices, wearable devices, laptops, and other portable computers. Personal computing device 165 can further be a non-portable computer, such as a desktop computer.
Object 250 can be associated with multiple payment accounts, and a loyalty program can be a payment account. A seller may be motivated to encourage certain behaviors in consumers. For example, the seller may want the consumer to return to the seller's store, or to purchase a certain item, or to return to the store at a certain time or during a certain time window and make a purchase. To encourage behaviors such as these, a seller can participate in or offer a loyalty program. The seller can provide loyalty points or some equivalent for each purchase made by a consumer. By coming back to the seller's store and making additional purchases, the consumer can grow his loyalty points. The loyalty points can be redeemed for purchases made at the seller's store or another of the seller's stores or with other businesses that participate in the loyalty program.
In addition to encouraging loyalty to a store or a brand by providing loyalty points for purchases made at the store or for brand products, a seller can use the loyalty program to encourage other behaviors. For example, if the store has a slow period, such as a coffee shop is slow between 3 pm and 4 pm, the store owner can, in order to give consumers incentive to make purchases at the store during this slow time, offer increased loyalty points for purchases made between 3 pm and 4 pm at the store. The store owner can also offer increased redemption value for a consumer's loyalty points, or can lower the cost of products or services in terms of loyalty points, during this time window. For example, the store owner could offer to redeem 100 loyalty points and provide 150 points of value, or could reduce an item that normally costs 150 loyalty points to 100 loyalty points, for purchases made between 3 pm and 4 pm. As another example, if a business owner wants to encourage consumers to purchase a new item that the business owner is introducing, the business owner can offer increased loyalty points to consumers for purchasing this new item. The business owner can also offer increased loyalty point redemption value or reduced loyalty point costs to a consumer for purchasing this new item using loyalty program points. For example, if the new item can be normally purchased with 150 loyalty points, the business owner can offer 150 points of loyalty program value for 100 redeemed loyalty points to a consumer for purchasing this new item, or the business owner can reduce the cost of the new item to 100 loyalty points.
The transaction of this example starts with a consumer presenting proxy card 150 to seller 310. Seller 310 initiates card swipe 105 at step 103 by swiping proxy card 150 through card reader 155. Card reader 155 at step 108 then sends the information obtained from proxy card 150, the proxy card information, to POS system 158. Card reader 155 is coupled to POS system 158. Payment authorization 130 starts at step 110 with POS system 158 transmitting the proxy card information to financial system 160. In the example of
In the embodiment of
POS system 158 at step 110 transmits the proxy card information to financial system 160, where the proxy card information is received by processing service 320. An example of processing service 320 is Bank of America Merchant Services. Processing service 320, based on the received proxy card information, determines that proxy card 150 is encoded as a VISA branded payment card. Based on this determination, processing service 320 relays the received information to the financial service that processes VISA branded payment cards. In various embodiments, financial service 330 can be a debit card payment network such as STAR or PULSE, a credit card payment network such as Visa's VisaNet Payment system or MasterCard's BankNet network, etc. In this example, financial service 330 is VISA's VisaNet Payment System, which processes payments made using VISA branded payment cards.
The proxy card information includes meta-data which financial service 330 uses to determine to transmit the proxy card and transaction information to computer system 170. As illustrated in
Connector 390 shows two connections to financial service 330 in order to facilitate explaining the example of
Computer system 170 at step 180 selects the payment account to use for the purchase transaction, which in this example is also a VISA branded payment card account. Computer system 170 performs step 120 which includes sending the transaction information and the payment account information to financial system 160. In the financial system embodiment of
As is represented by label 390A of
Returning to the description of
For the embodiment represented in
Returning to the description of
In the financial system embodiment of
A particular monetary value card can either be used at a plurality of different merchants, and is referred to herein as a “multi-merchant monetary value card”, or can be used at only a particular merchant, and is referred to herein as a “single merchant monetary value card”. A particular monetary value card can be either a multi-merchant monetary value card or a single merchant monetary value card, but cannot be both.
A monetary value card is associated with a monetary balance (i.e., a “monetary value card balance”). A “trust fund monetary value card” is associated with a monetary balance that represents money that is held in trust for the consumer by a party. A “faux money monetary value card” is associated with a monetary balance that represents an amount of a financial transaction, such as a purchase of merchandise/services/rentals/etc., that the consumer can complete at a single particular merchant (e.g., the single merchant) based on the card, and does not represent an amount of funds that is held in trust for the consumer. A particular monetary value card can be either a trust fund monetary value card or a faux money monetary value card, but cannot be both.
A particular monetary value card can be one of a faux money monetary value card that is also a single merchant monetary value card, a trust fund monetary value card that is also a single merchant monetary value card, or a trust fund monetary value card that is also a multi-merchant monetary value card.
In some embodiments, such as when the monetary value card is a trust fund monetary value card, computer system 170 causes funds for the financial transaction to be obtained based on the monetary value card, e.g., the gift card (step 615). In these embodiments, funds for the monetary value card are maintained at a financial institution, such as a banking service 340. Computer system 170 can send the transaction information and the monetary value card information, e.g., the gift card information, to financial system 160 to cause funds for the financial transaction to be obtained based on the monetary value card (step 615). The funds can be obtained, for example, by sending information to financial system 160 to cause a transfer of funds from a financial account associated with the monetary value card to a financial account associated with the merchant. The financial account associated with the merchant can be, for example, at a bank.
In some embodiments, such as when the monetary value card is a trust fund monetary value card as well as a single merchant monetary value card, rather than transferring funds between financial accounts, the particular merchant can transfer money between the consumer and the merchant by updating financial account balances associated with the financial account of the merchant.
For example, a friend of a consumer pays a merchant twenty dollars for a gift card (ignoring various possible fees associated with the gift card). The merchant deposits the twenty dollars into a financial account of the merchant, where the merchant holds the twenty dollars in trust for the possessor of the gift card. The financial account also holds funds of the merchant (i.e., funds that are not held in trust for others, but rather that the merchant can freely spend). The balances of the various gift card financial accounts that the merchant holds in trust for others, and the balance of the merchants funds, are maintained by the merchant.
The friend of the consumer gives the gift card to the consumer, who uses the gift card to make a purchase. Being a gift card that is only valid at the particular merchant, the consumer makes the purchase at the merchant. The purchase is for goods totaling fifteen dollars. In order to cause a transfer of funds for the financial transaction based on the gift card, the merchant simply decreases the balance of funds of the gift card account by fifteen dollars, from twenty dollars to five dollars (ignoring various possible fees, such as transaction fees). The merchant also increases the merchant account balance by fifteen dollars (once again, ignoring various possible fees). The total amount of funds in the financial account of the merchant is unchanged. It is just the balance of the funds of the gift card account and the balance of the funds of the merchant account that change via updated accounting of these account balances.
In some embodiments where the monetary value card is a trust fund monetary value card as well as a single merchant monetary value card, computer system 170 causes funds for the financial transaction to be obtained based on the monetary value card (step 615) by updating an amount of funds that are available at the gift card financial account, and by updating an amount of funds that are freely available to the merchant (e.g., funds that are “owned” by the merchant and are not held in trust for others).
In some embodiments, such as when the monetary value card is a stored value card, computer system 170 causes funds for the financial transaction to be obtained based on the stored value card (step 615) by transferring funds from the stored value card to a financial account of the merchant.
In some embodiments, such as when the monetary value card is a faux money monetary value card, step 615 is not executed. In these embodiments, no funds are obtained by the merchant for the financial transaction based on the financial transaction. In these embodiments, the monetary value card balance is updated, such as at step 620, to reflect the remaining amount of goods/services/rentals/etc. that the consumer can purchase after completion of the financial transaction. For example, the monetary value card balance can be reduced by an amount that corresponds to the amount of the financial transaction, such as by the amount of the financial transaction or by the amount of the financial transaction plus associated transaction fees.
Computer system 170 updates a monetary value card balance (step 620) to reflect an amount of funds available based on the monetary value card, or to reflect an amount of goods/services/rentals/etc. that can be purchase from the merchant. In a first example where a monetary value card is a trust fund monetary value card, the monetary value card has a total amount of funds available of twenty dollars. A financial transaction involves a payment by the consumer of fifteen dollars, which will be paid based on the monetary value card. The updated monetary value card balance, based on using the monetary value card to pay for the financial transaction, is five dollars (assuming that there are no transaction fees associated with use of the monetary value card for the financial transaction).
In a second example where the monetary value card is a faux money monetary value card, the monetary value card has an associated monetary value card balance that indicates that the possessor of the monetary value card can purchase twenty dollars of goods/services/rentals/etc. at the particular merchant. A financial transaction involves a payment by the consumer of fifteen dollars, which will be accommodated via the monetary value card. The updated monetary value card balance, based on using the monetary value card for the financial transaction, is five dollars (assuming that there are no transaction fees associated with use of the monetary value card for the financial transaction).
Computer system 170 sends a message to POS system 158A to prompt the consumer to provide personal information (step 625). The message can cause POS system 158A to display an inquiry message that prompts the consumer to provide personal information of the customer. The inquiry message can be or include, for example: an inquiry as to whether the consumer would like to receive a digital receipt for the financial transaction; an inquiry as to whether the consumer has an account/profile, such as with financial transaction platform 575, with a company that is associated with computer system 170, etc.; an inquiry as to whether the consumer would like to link his monetary value card with a payment card; an inquiry as to whether the consumer would like to purchase an extended warranty for an item that is part of a financial transaction; a request to send a photo of the payment card if he would like to link the two cards, etc. The inquiry can include a request for personal information of the consumer, such as one or more of an email address, an Internet Protocol (IP) address, a phone number, etc., associated with the consumer, and to which further communications regarding the inquiry can be directed. The personal information can also include a photo of a payment card in the possession of the consumer, and to which he would like to link his monetary value card.
The consumer can indicate an affirmative response to the inquiry request by, for example, inputting his personal information at or via POS system 158A, by tapping an icon at POS system 158A that indicates an affirmative response, etc. Inputting his personal information at POS system 158A can include taking a photo of a payment card with which he wishes to associate the monetary value card with POS system 158A, or sending a photo that he takes with his mobile device to POS system 158A, such as via Bluetooth or a wireless network. When the affirmative response is not associated with an inputting of the personal information, POS system 158A can prompt the consumer to input his personal information. Upon receipt of the personal information, POS system 158A can send the personal information to computer system 170, where the personal information is received (step 630).
In some embodiments, computer system 170 can access stored association information, such as association information that is stored in a database, based on the personal information (step 635) to determine whether the consumer is associated with a payment card via the database (step 640). For example, the consumer may have an account/profile at computer system 170 and/or financial transaction platform 575, may have an account/profile with a company that is associated with computer system 170, etc. Information associated with the account/profile, such as the personal information or card information for a payment card of the consumer, can be stored with the stored association information. When the account/profile of the consumer includes personal information for the consumer, computer system 170 can determine that the personal information that was provided by the consumer is associated with the account/profile. The account/profile information can further contain card information for a payment card that is associated with the consumer.
When computer system 170 determines that the consumer is associated with a payment card, computer system 170 can send a message to POS system 158A, or to any destination that is associated with the consumer via the stored association information, to prompt the consumer to associate the monetary value card with the payment card (step 645). Destinations that can be associated with the consumer via the stored association information include a computing device, such as the consumer's mobile device, an email address, a phone number, etc. The message can be, for example: an email sent to the email address; a text message sent to the phone number or the mobile device, such as via short message service (SMS) or multimedia messaging service (MMS); a message sent to an IP address of the computing device or the mobile device; etc.
The message can prompt the consumer to associate the monetary value card with the payment card in any of various ways. For example, the message: can cause POS system 158A to display a message asking whether the consumer would like to associate the monetary value card with the payment card; can cause a mobile device that is associated with the consumer, such as via the stored association information, to display a message asking whether the consumer would like to associate the monetary value card with the payment card; can be an email sent to the email address associated with the consumer, such as via the stored association information, asking whether the consumer would like to associate the monetary value card with the payment card; can be a text message sent to a mobile device or phone number associated with the consumer, such as via the stored association information, asking whether the consumer would like to associate the monetary value card with the payment card; etc.
Based on receiving an indication to associate the monetary value card with the payment card (step 650), computer system 170 can update the stored association information to reflect an association between the monetary value card and the payment card (step 655). If computer system 170 does not receive an indication to associate the monetary value card with the payment card (e.g., where the consumer does not wish to create such an association), no association is created between the monetary value card and the payment card.
In some embodiments, the monetary value card is associated/linked with the payment card in other ways. For example, in some embodiments, the consumer can take a photo of the monetary value card and of the payment card using his mobile device. The consumer can send the photos to computer system 170, or to an application running at the mobile device, either of which can obtain, based on an analysis of the photos, the card information needed to link the cards. When the cards are linked via the application, the application can send a message to computer system 170 to cause computer system 170 to update, based on the message, the stored association information to reflect an association between the monetary value card and the payment card. As a second example, the consumer can swipe the two cards through a card reader connected to a mobile device of the consumer, and can send, via the mobile device, the data obtained by the card reader to computer system 170.
As a third example, the consumer can login to a website that is associated with computer system 170, and can enter card information obtained from the monetary value card. When the payment card information is available to the website, such as via a account/profile of the consumer at the website, the website can cause computer system 170 to update the stored association information to reflect an association between the monetary value card and the payment card. When the payment card information is not available to the website, the card information from the payment card can be entered at the website. The website can send a message to computer system 170 to cause computer system 170 to update the stored association information to reflect an association between the monetary value card and the payment card based on the card information from the monetary value card and/or the payment card.
When the personal information of step 630 includes a photo of a payment card of the consumer, instead of performing steps 635-645, steps 660-670 can be performed. When the personal information includes a photo of a payment card with which the consumer wishes to link his monetary value card, computer system 170 can perform character recognition on the photo to determine an account number and other information that is visible on the card (step 660). Based on the account number, computer system 170 can access the database to determine whether the database includes the account number (step 665).
When the database does not include the account number, computer system 170 updates the database with information obtained based on the photo, such as based on the character recognition of the photo (step 670). Based on receiving the photo, which is an indication to associate the monetary value card with the payment card (step 675), computer system 170 can update the stored association information to reflect an association between the monetary value card and the payment card (step 680). Steps 675 and 680 are, respectively, substantially similar to steps 650 and 655.
In some embodiments, in addition to, or as an alternative to, steps 635-655 or steps 660-680, computer system 170 can perform some or all of steps 685-695. Computer system 170 can send a message to prompt the payer to associate the monetary value card with the personal information (step 685), and can receive a message indicating to associate the monetary value card with the personal information (step 690). Steps 685 and 690 are, respectively, substantially similar to steps 645 and 650, except that the monetary value card is to be associated with the personal information rather than the payment card.
In some embodiments, based on the message of step 690, computer system 170 updates the database to associate the monetary value card with the personal information (step 695). In some embodiments, steps 685 and 690 are skipped, and step 695 is performed based on step 630. Step 695 is substantially similar to step 655, except that the monetary value card is being associated with the personal information rather than the payment card.
The consumer orders the coffee from the merchant, and the merchant rings up the order using a POS system, such as POS system 158A of
Computer system 170 accesses a database to determine whether the payment card and/or the personal information is associated with a monetary value card (step 715). The database contains association information that represents an association between the payment card and a monetary value card, and/or that represents an association between the personal information and the monetary value card. In other embodiments, computer system 170 can access other computer based storage mechanisms to determine whether the payment card and/or the personal information is associated with a monetary value card. The other computer based storage mechanisms, such as a file, a spreadsheet, etc., can also contain association information that represents an association between the payment card and the monetary value card, and/or that represents an association between the personal information and the monetary value card.
In some embodiments, computer system 170 sends a message to prompt the consumer to indicate whether to use the payment card or the monetary value card for the financial transaction (step 720). In various embodiments, computer system 170 can send the message to POS system 158A or a mobile device of the consumer, where the message causes POS system 158A or the mobile device to display a message inquiring whether the consumer wants to use the monetary value card or the payment card for the financial transaction. When the monetary value card is associated with personal information, the message of step 720 can inquire whether the consumer wants to use the monetary value card for the financial transaction. The payer indicates his response, such as by touching an icon on POS system 158A or the mobile device, that indicates to use the monetary value card. POS system 158A or the mobile device send a message to computer system 170 that indicates to use the monetary value card for the financial transaction, where the message is received (step 725).
In some embodiments, rather than performing steps 720 and 725, computer system 170 accesses the database to determine whether to use the payment card or the monetary value card for the financial transaction (step 730). For example, the payer can access a website associated with computer system 170, or can access an application running on his mobile device that can communicate with computer system 170. Using the website or the application, the user can access a profile or other account-related mechanism associated with computer system 170, such as a profile or a personal payment processing policy at financial transaction platform 575. Via the profile, the personal payment processing policy, etc., the payer can indicate that any electronic payments that are initiated with his payment card or with his personal information are to be paid for using a monetary value card associated with the payment card or the personal information whenever possible.
Computer system 170, based on the indication of step 725 or the database access of step 730, determines to use the monetary value card for the financial transaction (step 735). The determination of step 735 can additionally be based on further verification of identity of the consumer, such as when step 710 includes receiving personal information and not payment card information. For example, computer system 170 can perform two factor identity verification, such as by sending a text message to a phone number of the consumer and/or by sending an email to an email address of the consumer, and by verifying the identity of the consumer based on a response to the text message or email. The text message and/or email address can be obtained based on the personal information, or based on data associated with the consumer via the database. As an additional example, the merchant can verify the identity of the payer, such as by checking the payer's driver's license, and can send a message via POS system 158A to computer system 170 to indicate the further identity verification.
In some embodiments, computer system 170 causes funds for the financial transaction to be obtained based on the monetary value card (step 740). Step 740 is similar to step 615 of
In some embodiments, computer system 170 determines a second amount of funds that correspond to a remaining balance of the financial transaction (step 750). Computer system 170 determines a balance of funds that are available via the monetary value card, and determines that the balance of funds is less than the amount of the financial transaction. Computer system 170 determines a second amount that corresponds to a remaining balance for the financial transaction after funds for the second financial transaction are obtained.
For example, a consumer purchases of groceries from a grocer for an amount of $100. The consumer initiates a payment using a payment card, and uses a monetary value card linked to the payment card to pay for the groceries. However, computer system 170 determines that the monetary value card only has $80 of funds available, and that this is less than the amount of the groceries. In this example, there are no transaction fees associated with using the monetary value card. Computer system 170 determines that, after exhausting the funds of the monetary value card to pay for the groceries, the financial transaction will have a remaining balance of $20.
In some embodiments, computer system 170 sends a message to prompt the consumer to indicate whether to use the payment card for the second amount of funds (step 755). In various embodiments, computer system 170 can send the message to POS system 158A or a mobile device of the consumer, where the message causes POS system 158A or the mobile device to display a message asking whether the consumer wants to use the payment card for the second amount of funds. The payer indicates his response, such as by touching an icon on POS system 158A or the mobile device, that indicates whether to use the payment card. POS system 158A or the mobile device send a message to computer system 170 that indicates whether to use the payment card for the second amount of funds, where the message is received (step 760).
In some embodiments, rather than performing steps 755 and 760, computer system 170 accesses the database to determine whether to use the payment card for the second amount of funds (step 765). Using methods similar to step 730, the consumer can indicate to use the payment card to pay a remaining balance for a financial transaction whenever the monetary value card does not have sufficient funds to fully pay for the financial transaction.
Computer system 170 determines, based on the indication of step 760 or the database access of step 765, to use the payment card for the second amount of funds (step 770). Computer system 170 causes funds for the financial transaction to be obtained based on the payment card (step 775). Computer system 170 sends the transaction information to a financial system, such as financial system 160 of
Financial system 160 authorizes a payment based on the payment card information, and sends a payment authorization to computer system 170. Financial system 160 processes a payment for the second amount of funds based on a financial account that is associated with the payment card. For example, when the payment card is a debit card or an ATM card, financial system 160 causes a financial account associated with the payment card to be debited by a third amount that corresponds to the second amount of funds, and causes a financial account associated with the merchant to be credited by a fourth amount that corresponds to the second amount of funds. When there are no transaction fees associated with using the payment card, the second amount, the third amount, and the fourth amount are all the same amount of funds. When there is a transaction fee or fees associated with using the card, the third amount and/or the fourth amount can differ from the second amount by a portion or all of the transaction fee(s).
As a second example, when the payment card is a credit card or a charge card, financial system 160 causes a credit balance of a financial account associated with the payment card to be increased by a fifth amount that corresponds to the second amount of funds, and causes a financial account associated with the merchant to be credited by a sixth amount that corresponds to the second amount of funds. When there are no transaction fees associated with using the payment card, the second amount, the fifth amount, and the sixth amount are all the same amount of funds. When there is a transaction fee or fees associated with using the card, the fifth amount and/or the sixth amount can differ from the second amount by a portion or all of the transaction fee(s).
After receipt of the proxy card (or the debit card when proxy card is a debit card), the consumer links/associates the proxy card with one or more financial accounts. The linking can happen in any of multiple ways. For example, the consumer can login to a website associated with a payment processing system, can launch an application that is associated with the payment processing system on his mobile phone, etc. The consumer can input proxy card information, which is information obtained from the proxy card, to the website or application. The consumer can further input account information for the financial accounts that he wishes to have linked with the proxy card. For the application, the consumer can input the proxy card or the account information in various additional ways, such as by scanning the proxy card or a payment card associated with the financial account with a card reader that is coupled to his mobile device or to a POS system, by taking a photo of the proxy card or the payment card associated with the financial account so the application or payment processing system can analyze the photo to obtain the proxy card and/or account information, etc. Card information from a payment card can be account information for an associated financial account.
For example, when a financial account to be linked is a checking account, the account information can be debit card information from a debit card associated with the checking account. When the financial account is a credit account associated with a credit card, the account information can be credit card information from the credit card. When the financial account is an online payment account, the account information can be the account login identity.
The website or application send the financial account information, for each financial account that the payment processing system is to link with the proxy card, and the proxy card information to the payment processing system, where the information is received (step 805). The payment processing system associates, such as via a database, the financial accounts with the proxy card (step 810). A message sent by an application is inherently also sent by the mobile device on which the application is executing.
To enable the consumer to indicate a financial account to use for a payment via a POS system, the consumer assigns a selection indicator to one or more of the financial accounts. The selection indicator enables the consumer to identify, via a POS system, one or more of the financial accounts associated with the proxy card to use for a payment initiated based on a swipe of the proxy card at the POS system. The selection indicator can be any of various indicators.
As a first example, the selection indicator can be a selection indicator PIN. The selection indicator PIN is text string that in various embodiments is a numeric string, an alphanumeric string, etc., and that is compatible with the system(s) that will process the selection indicator PIN, such as a POS system and a debit processing network. Another type of PIN, which is sometimes referred to in this application as a “security PIN”, has a different purpose and is distinguishable from a selection indicator PIN. A security PIN is a security authentication code that is required for security purposes to process an electronic payment for a financial account, such as a PIN for authorizing a debit card transaction. The consumer can indicate selection indictor PINs for one or more of the financial accounts, for example by inputting the selection indicator PINs via the website or application, and can indicate the associated financial account for each selection indicator PIN. The payment processing system can determine to select, based on the selection indicator PIN, one of the financial accounts linked with the proxy card.
As a second example, the selection indicator can be a card type. For example, a consumer has a proxy card that is manufactured to be compatible with a debit card processing system. When the consumer swipes the proxy card at a POS system, he can indicate to process the debit card as a credit type card (i.e., a credit transaction) or a debit type card (i.e., a debit transaction), such as by touching either a first button to indicate a credit transaction or a second button to indicate a debit transaction. The consumer can provide a selection indicator to the website/application that indicates to use a first account of the financial accounts associated with the proxy card when the card type is credit, and to use a second financial account when the card type is debit. As another example, the consumer can provide a selection indicator to the website/application that indicates to use a first account when the card type indicated by the consumer using the POS system matches the card type of the proxy card, and that indicates to use a second account when the indicated card type does not match the card type of the proxy card. For example, the consumer can indicate that the proxy card is an EBT type card, when, in fact, the proxy card is a debit type card. In this case, the indicated card type does not match the card type of the proxy card, so the second account would be used for this payment.
As a third example, the selection indicator can be a tip amount. For example, the consumer presents his proxy card to use for a meal. The payment is processed as a credit transaction, and a receipt is provided to the consumer. The receipt includes an area to indicate a tip amount. The consumer can provide a selection indicator to the website/application that indicates to use a first account of the financial accounts associated with the proxy card when the tip ends in, for example, and even number, and to use a second account when the tip ends in an odd number. As another example, a first account can be used when the tip is below five percent, a second account can be used when the tip is between five and ten percent, and a third account can be used when the tip is above ten percent. As is apparent, there are a number of different schemes that can be used to indicate a financial account to use based on the tip amount.
As a fourth example, the selection indicator can be a cash back amount. For example, the consumer presents his proxy card to pay for groceries at a store, and processes the payment as a debit transaction and requests a cash back amount. The consumer can provide a selection indicator to the website/application that indicates to use a first account of the financial accounts associated with the proxy card when the cash back amount is a first amount, to use a second account when the cash back amount is a second amount, etc. As another example, a first account can be used when the cash back amount ends in an even number, and a second account can be used when the cash back amount ends in an odd number. As is apparent, there are a number of different schemes that can be used to indicate a financial account to use based on the cash back amount.
As a fifth example, the selection indicator can be based on signature data. For example, the consumer presents his proxy card to pay for a meal. His waiter processes the payment as a credit transaction using a POS system, and the waiter provides a signature pad that is coupled to the POS system to the consumer to electronically capture his signature to authorize the transaction. The consumer writes his signature on the signature pad, and then writes “VISA card” on the signature pad. The signature data, which includes data representing both his written signature and the “VISA card” that he wrote, is forwarded to a payment processing system, where the signature can be analyzed based on character recognition. Based on the signature data, which states “VISA card”, a VISA credit account associated with the proxy card is used for the payment. The consumer can provide a selection indicator to the website/application that indicates an account to use when the signature data indicates a certain combination of alphanumeric character symbols, geometric symbols, punctuation symbols, etc.
As a sixth example, the selection indicator can be based on a biometrically identifiable body part or an orientation of a body part. For example, the consumer presents his proxy card to pay for a purchase. The merchant processes the payment with a POS system, and asks to scan a body part to authorize the transaction. The consumer can provide a selection indicator to the website/application that indicates a first account to use when the body part is a first body part or is a first orientation, and a second account to use when the body part is a second body part or is a second orientation. For example, the consumer can provide a selection indicator that indicates to use a first account when the consumer provides a right thumb print, and to use a second account when the consumer provides a left thumb print.
The consumer can use the website or application to identify one or more of the financial accounts associated with the proxy card, and to input one or more selection indicators for each financial account. The one or more of the financial accounts that are identified and assigned a selection indicator are those that will be enabled for selection to use for a payment via the POS system based on a selection indicator that is indicated via a POS system. The payment processing system can determine to select, based on the selection indicator, one of the financial accounts linked with the proxy card. The website or application sends the selection indicator(s) to the payment processing system, where the selection indicator(s) is(are) received (step 815). The payment processing system associates, such as via the database, each selection indicator with the corresponding financial account (step 820).
In some embodiments, for the financial accounts that require a security authentication code, and that that consumer wants to indicate to use for a payment via a POS system, the consumer provides the code. For example, to process a payment made via a debit card and processed as a debit transaction, and where funds for the payment will be debited from a checking account, a consumer may need to provide a personal identification code (PIC), such as a security PIN. This PIC is a security authentication code. As a second example, to process an online payment made via an online payment processor, the consumer may need to provide a password for the consumer's account at the online payment processor. This password is also a security authorization code.
The consumer indicates the security authentication codes and the associated financial account, for example by entering the security authentication code at the website and indicating the account with which the security authentication code is associated. The website sends the security authentication codes for one or more of the financial accounts to the payment processing system, where the codes are received (step 825). The one or more financial accounts are those financial accounts that the consumer wishes to enable for selection via a POS system, etc. The payment processing system associates, such as via the database, each security authentication code with the corresponding financial account (step 830).
The selection indicator that the consumer can indicate can be any of the selection indicators discussed in the description of
The POS system forwards the proxy card information, transaction information, and the PIN to a processing service, such as processing service 320 of
Computer system 170, based on the proxy card information, accesses a database containing association information and determines that the proxy card is associated with multiple financial accounts. Computer system 170 further determines that one or more of the multiple financial accounts have selection indicator PINs associated with them. Based on the PIN received at step 905, which computer system 170 has determined, based on the database access, that the PIN is a selection indicator PIN. Based on the selection indicator PIN, computer system 170 accesses the database to determine the financial account that corresponds to the selection indicator PIN, and selects that financial account to use to pay for the coffee (step 910). In this example, the selected financial account is a checking account that is associated with a debit card.
For financial accounts that require a security authentication code to process an electronic payment based on the account, the security authentication code can be obtained in various ways. For example, when the financial account is associated with a security authentication code, such as a security authentication code associated with a financial account at step 830 of
Computer system 170 sends a message to a financial system, such as financial system 160 of
For example, a bank may charge a first transaction fee from the consumers financial account, and a payment processor may charge a second transaction fee. When the financial transaction involves one payment from an account that has adequate funds for the payment, the amount debited from the consumer's financial account can be the total of the purchase (i.e., the first amount) plus the first transaction fee. The amount credited to the merchant's account can be the first amount less the second transaction fee. When there are no transaction fees, the amount debited from the consumer's account is the first amount, and equals the amount credited to the merchant's account.
In some cases, the selected financial account may not have funds adequate to pay the purchase total (i.e., the first amount of funds). In some embodiments, computer system 170 determines whether more funds are needed (step 925). When more funds are needed, computer system 170 can cause an additional payment for the financial transaction to be processed by use of a second financial account that is associated with the proxy card (step 930). In some embodiments, the consumer indicates a second selection indicator via the POS system.
For example, the second indicator can be a tip amount, a card type, etc., that is entered via the POS system. Computer system 170 can select a first financial account to make a payment for the financial transaction based on the selection indicator PIN, and can select a second account for an additional payment for the financial transaction based on a tip amount selection indicator that is associated with the financial account via the database. In some embodiments, the second account is selected based on a default setting. For example, the consumer can indicate a default financial account to use for financial transactions, and the additional payment can be based on the default account.
In the illustrated embodiment, the processing system 1000 includes one or more processors 1010, memory 1011, a communication device 1012, and one or more input/output (I/O) devices 1013, all coupled to each other through an interconnect 1014. The interconnect 1014 may be or include one or more conductive traces, buses, point-to-point connections, controllers, adapters and/or other conventional connection devices. Each processor 1010 may be or include, for example, one or more general-purpose programmable microprocessors or microprocessor cores, microcontrollers, application specific integrated circuits (ASICs), programmable gate arrays, or the like, or a combination of such devices. The processor(s) 1010 control the overall operation of the processing device 1000. Memory 1011 may be or include one or more physical storage devices, which may be in the form of random access memory (RAM), read-only memory (ROM) (which may be erasable and programmable), flash memory, miniature hard disk drive, or other suitable type of storage device, or a combination of such devices. Memory 1011 may store data and instructions that configure the processor(s) 1010 to execute operations in accordance with the techniques described above. The communication device 1012 may be or include, for example, an Ethernet adapter, cable modem, Wi-Fi adapter, cellular transceiver, Bluetooth transceiver, or the like, or a combination thereof. Depending on the specific nature and purpose of the processing device 1000, the I/O devices 1013 can include devices such as a display (which may be a touch screen display), audio speaker, keyboard, mouse or other pointing device, microphone, camera, etc.
Unless contrary to physical possibility, it is envisioned that (i) the methods/steps described above may be performed in any sequence and/or in any combination, and that (ii) the components of respective embodiments may be combined in any manner.
The techniques introduced above can be implemented by programmable circuitry programmed/configured by software and/or firmware, or entirely by special-purpose circuitry, or by a combination of such forms. Such special-purpose circuitry (if any) can be in the form of, for example, one or more application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc.
Software or firmware to implement the techniques introduced here may be stored on a machine-readable storage medium and may be executed by one or more general-purpose or special-purpose programmable microprocessors. A “machine-readable medium”, as the term is used herein, includes any mechanism that can store information in a form accessible by a machine (a machine may be, for example, a computer, network device, cellular phone, personal digital assistant (PDA), manufacturing tool, any device with one or more processors, etc.). For example, a machine-accessible medium includes recordable/non-recordable media (e.g., read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; etc.), etc.
Note that any and all of the embodiments described above can be combined with each other, except to the extent that it may be stated otherwise above or to the extent that any such embodiments might be mutually exclusive in function and/or structure.
Although the present invention has been described with reference to specific exemplary embodiments, it will be recognized that the invention is not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense.
This application is a continuation-in-part of U.S. patent application Ser. No. 14/225,338, entitled “ASSOCIATING AN ACCOUNT WITH A CARD BASED ON A PHOTO”, which was filed on Mar. 25, 2014, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5276311 | Hennige | Jan 1994 | A |
| 5530232 | Taylor | Jun 1996 | A |
| 5585787 | Wallerstein | Dec 1996 | A |
| 5590038 | Pitroda | Dec 1996 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 6175922 | Wang | Jan 2001 | B1 |
| 6193155 | Walker | Feb 2001 | B1 |
| 6263352 | Cohen | Jul 2001 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6764005 | Cooper | Jul 2004 | B2 |
| 7085812 | Sherwood | Aug 2006 | B1 |
| 7155411 | Blinn et al. | Dec 2006 | B1 |
| 7233843 | Budhraja et al. | Jun 2007 | B2 |
| 7478054 | Adams et al. | Jan 2009 | B1 |
| 7493390 | Bobde et al. | Feb 2009 | B2 |
| 7552087 | Schultz et al. | Jun 2009 | B2 |
| 7575166 | McNamara | Aug 2009 | B2 |
| 7580873 | Silver et al. | Aug 2009 | B1 |
| 7603382 | Halt, Jr. | Oct 2009 | B2 |
| 7805378 | Berardi et al. | Sep 2010 | B2 |
| 7818809 | Sobel et al. | Oct 2010 | B1 |
| 8060259 | Budhraja et al. | Nov 2011 | B2 |
| 8190514 | Bishop et al. | May 2012 | B2 |
| 8266551 | Boldyrev et al. | Sep 2012 | B2 |
| 8401710 | Budhraja et al. | Mar 2013 | B2 |
| 8423459 | Green et al. | Apr 2013 | B1 |
| 8459544 | Casey et al. | Jun 2013 | B2 |
| 8498888 | Raff et al. | Jul 2013 | B1 |
| 8577803 | Chatterjee et al. | Nov 2013 | B2 |
| 8579203 | Lambeth et al. | Nov 2013 | B1 |
| 8602296 | Velline et al. | Dec 2013 | B1 |
| 8630586 | Dvortsov et al. | Jan 2014 | B2 |
| 8676119 | Cohen et al. | Mar 2014 | B2 |
| 8788418 | Spodak et al. | Jul 2014 | B2 |
| 8855312 | Hodgman et al. | Oct 2014 | B1 |
| 8859337 | Gaul et al. | Oct 2014 | B2 |
| 8892462 | Borovsky et al. | Nov 2014 | B1 |
| 8939357 | Perry | Jan 2015 | B1 |
| 8972298 | Kunz et al. | Mar 2015 | B2 |
| 9010644 | Workley | Apr 2015 | B1 |
| 9064249 | Borovsky et al. | Jun 2015 | B1 |
| 9092767 | Andrews et al. | Jul 2015 | B1 |
| 9092776 | Dessert | Jul 2015 | B2 |
| 9092828 | Hosp | Jul 2015 | B2 |
| 20030061157 | Hirka et al. | Mar 2003 | A1 |
| 20030065805 | Barnes, Jr. | Apr 2003 | A1 |
| 20030115126 | Pitroda | Jun 2003 | A1 |
| 20040030601 | Pond et al. | Feb 2004 | A1 |
| 20040138999 | Friedman et al. | Jul 2004 | A1 |
| 20040204990 | Lee et al. | Oct 2004 | A1 |
| 20040215520 | Butler et al. | Oct 2004 | A1 |
| 20040219971 | Ciancio et al. | Nov 2004 | A1 |
| 20060085333 | Wah et al. | Apr 2006 | A1 |
| 20060131385 | Kim | Jun 2006 | A1 |
| 20060146839 | Hurwitz et al. | Jul 2006 | A1 |
| 20060261149 | Raghavendra Tulluri | Nov 2006 | A1 |
| 20070069013 | Seifert et al. | Mar 2007 | A1 |
| 20070073619 | Smith | Mar 2007 | A1 |
| 20070208930 | Blank et al. | Sep 2007 | A1 |
| 20070255653 | Tumminaro et al. | Nov 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20080037442 | Bill | Feb 2008 | A1 |
| 20080040265 | Rackley, III et al. | Feb 2008 | A1 |
| 20080052176 | Buchheit | Feb 2008 | A1 |
| 20080078831 | Johnson et al. | Apr 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080177826 | Pitroda | Jul 2008 | A1 |
| 20080262925 | Kim et al. | Oct 2008 | A1 |
| 20080270246 | Chen | Oct 2008 | A1 |
| 20080277465 | Pletz et al. | Nov 2008 | A1 |
| 20080296978 | Finkenzeller et al. | Dec 2008 | A1 |
| 20090070228 | Ronen | Mar 2009 | A1 |
| 20090099961 | Ogilvy | Apr 2009 | A1 |
| 20090106138 | Smith et al. | Apr 2009 | A1 |
| 20090112766 | Hammad et al. | Apr 2009 | A1 |
| 20090119190 | Realini | May 2009 | A1 |
| 20090159663 | Mullen et al. | Jun 2009 | A1 |
| 20090192904 | Patterson et al. | Jul 2009 | A1 |
| 20090266884 | Killian et al. | Oct 2009 | A1 |
| 20090271265 | Lay et al. | Oct 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090313132 | McKenna et al. | Dec 2009 | A1 |
| 20090319421 | Mathis et al. | Dec 2009 | A1 |
| 20090319638 | Faith et al. | Dec 2009 | A1 |
| 20100010906 | Grecia | Jan 2010 | A1 |
| 20100076777 | Paretti et al. | Mar 2010 | A1 |
| 20100082420 | Trifiletti et al. | Apr 2010 | A1 |
| 20100102125 | Gatto | Apr 2010 | A1 |
| 20100174596 | Gilman et al. | Jul 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100306099 | Hirson et al. | Dec 2010 | A1 |
| 20110029416 | Greenspan | Feb 2011 | A1 |
| 20110047013 | McKenzie, III | Feb 2011 | A1 |
| 20110055084 | Singh | Mar 2011 | A1 |
| 20110071892 | Dickelman | Mar 2011 | A1 |
| 20110087550 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110131128 | Vaananen | Jun 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110145052 | Lin et al. | Jun 2011 | A1 |
| 20110178883 | Granbery et al. | Jul 2011 | A1 |
| 20110180598 | Morgan et al. | Jul 2011 | A1 |
| 20110218871 | Singh | Sep 2011 | A1 |
| 20110246284 | Chaikin et al. | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110251962 | Hruska | Oct 2011 | A1 |
| 20110258689 | Cohen et al. | Oct 2011 | A1 |
| 20110270747 | Xu | Nov 2011 | A1 |
| 20110276418 | Velani | Nov 2011 | A1 |
| 20110295750 | Rammal | Dec 2011 | A1 |
| 20110302019 | Proctor, Jr. et al. | Dec 2011 | A1 |
| 20110302080 | White et al. | Dec 2011 | A1 |
| 20110313840 | Mason et al. | Dec 2011 | A1 |
| 20110313867 | Silver | Dec 2011 | A9 |
| 20110313871 | Greenwood | Dec 2011 | A1 |
| 20110320345 | Taveau et al. | Dec 2011 | A1 |
| 20120011072 | Lodolo | Jan 2012 | A1 |
| 20120016731 | Smith et al. | Jan 2012 | A1 |
| 20120029990 | Fisher | Feb 2012 | A1 |
| 20120030044 | Hurst | Feb 2012 | A1 |
| 20120059701 | van der Veen et al. | Mar 2012 | A1 |
| 20120059718 | Ramer et al. | Mar 2012 | A1 |
| 20120059758 | Carlson | Mar 2012 | A1 |
| 20120084210 | Farahmand | Apr 2012 | A1 |
| 20120110568 | Abel et al. | May 2012 | A1 |
| 20120143772 | Abadir | Jun 2012 | A1 |
| 20120150611 | Isaacson et al. | Jun 2012 | A1 |
| 20120150643 | Wolfe et al. | Jun 2012 | A1 |
| 20120150742 | Poon et al. | Jun 2012 | A1 |
| 20120166311 | Dwight et al. | Jun 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120197740 | Grigg et al. | Aug 2012 | A1 |
| 20120197743 | Grigg et al. | Aug 2012 | A1 |
| 20120197794 | Grigg et al. | Aug 2012 | A1 |
| 20120209749 | Hammad et al. | Aug 2012 | A1 |
| 20120209773 | Ranganathan | Aug 2012 | A1 |
| 20120214416 | Kent et al. | Aug 2012 | A1 |
| 20120244885 | Hefetz | Sep 2012 | A1 |
| 20120254031 | Walker et al. | Oct 2012 | A1 |
| 20120271707 | Harrison et al. | Oct 2012 | A1 |
| 20120271725 | Cheng | Oct 2012 | A1 |
| 20120278727 | Ananthakrishnan et al. | Nov 2012 | A1 |
| 20120290422 | Bhinder | Nov 2012 | A1 |
| 20120290609 | Britt | Nov 2012 | A1 |
| 20120296679 | Im | Nov 2012 | A1 |
| 20120296726 | Dessert et al. | Nov 2012 | A1 |
| 20120323685 | Ullah | Dec 2012 | A1 |
| 20130006773 | Lutnick et al. | Jan 2013 | A1 |
| 20130019284 | Pacyga et al. | Jan 2013 | A1 |
| 20130024341 | Jeon et al. | Jan 2013 | A1 |
| 20130024364 | Shrivastava et al. | Jan 2013 | A1 |
| 20130024371 | Hariramani et al. | Jan 2013 | A1 |
| 20130030889 | Davich et al. | Jan 2013 | A1 |
| 20130041824 | Gupta | Feb 2013 | A1 |
| 20130048719 | Bennett | Feb 2013 | A1 |
| 20130050080 | Dahl et al. | Feb 2013 | A1 |
| 20130054320 | Dorso et al. | Feb 2013 | A1 |
| 20130065672 | Gelman et al. | Mar 2013 | A1 |
| 20130066783 | Wolff | Mar 2013 | A1 |
| 20130073363 | Boal | Mar 2013 | A1 |
| 20130103574 | Conrad et al. | Apr 2013 | A1 |
| 20130103946 | Binenstock | Apr 2013 | A1 |
| 20130117329 | Bank et al. | May 2013 | A1 |
| 20130124333 | Doughty et al. | May 2013 | A1 |
| 20130132274 | Henderson et al. | May 2013 | A1 |
| 20130134962 | Kamel et al. | May 2013 | A1 |
| 20130138563 | Gilder et al. | May 2013 | A1 |
| 20130144707 | Isaacson et al. | Jun 2013 | A1 |
| 20130151613 | Dhawan et al. | Jun 2013 | A1 |
| 20130159081 | Shastry et al. | Jun 2013 | A1 |
| 20130159172 | Kim | Jun 2013 | A1 |
| 20130159173 | Sivaraman et al. | Jun 2013 | A1 |
| 20130159446 | Carlson et al. | Jun 2013 | A1 |
| 20130166402 | Parento et al. | Jun 2013 | A1 |
| 20130166445 | Isaacson et al. | Jun 2013 | A1 |
| 20130173407 | Killian et al. | Jul 2013 | A1 |
| 20130179227 | Booth et al. | Jul 2013 | A1 |
| 20130181045 | Dessert et al. | Jul 2013 | A1 |
| 20130198018 | Baig | Aug 2013 | A1 |
| 20130204727 | Rothschild | Aug 2013 | A1 |
| 20130204777 | Irwin, Jr. et al. | Aug 2013 | A1 |
| 20130204793 | Kerridge et al. | Aug 2013 | A1 |
| 20130218697 | Kingston et al. | Aug 2013 | A1 |
| 20130218721 | Borhan et al. | Aug 2013 | A1 |
| 20130225081 | Doss et al. | Aug 2013 | A1 |
| 20130228616 | Bhosle et al. | Sep 2013 | A1 |
| 20130236109 | Madden et al. | Sep 2013 | A1 |
| 20130246203 | Laracey | Sep 2013 | A1 |
| 20130246280 | Kirsch | Sep 2013 | A1 |
| 20130248591 | Look et al. | Sep 2013 | A1 |
| 20130268431 | Mohsenzadeh | Oct 2013 | A1 |
| 20130290173 | Nemeroff | Oct 2013 | A1 |
| 20130290522 | Behm, Jr. | Oct 2013 | A1 |
| 20130291018 | Billings et al. | Oct 2013 | A1 |
| 20130317835 | Mathew | Nov 2013 | A1 |
| 20130317950 | Abraham et al. | Nov 2013 | A1 |
| 20130332354 | Rhee et al. | Dec 2013 | A1 |
| 20130332385 | Kilroy et al. | Dec 2013 | A1 |
| 20130339253 | Sincai | Dec 2013 | A1 |
| 20130346223 | Prabhu et al. | Dec 2013 | A1 |
| 20140006205 | Berry et al. | Jan 2014 | A1 |
| 20140012754 | Hanson et al. | Jan 2014 | A1 |
| 20140032297 | Germann et al. | Jan 2014 | A1 |
| 20140052617 | Chawla et al. | Feb 2014 | A1 |
| 20140057667 | Blankenship et al. | Feb 2014 | A1 |
| 20140058861 | Argue et al. | Feb 2014 | A1 |
| 20140067557 | van Niekerk et al. | Mar 2014 | A1 |
| 20140074569 | Francis et al. | Mar 2014 | A1 |
| 20140074655 | Lim et al. | Mar 2014 | A1 |
| 20140074658 | Sanchez | Mar 2014 | A1 |
| 20140074691 | Bank et al. | Mar 2014 | A1 |
| 20140074716 | Ni | Mar 2014 | A1 |
| 20140081783 | Paranjape et al. | Mar 2014 | A1 |
| 20140081853 | Sanchez et al. | Mar 2014 | A1 |
| 20140081854 | Sanchez et al. | Mar 2014 | A1 |
| 20140084059 | Sierchio et al. | Mar 2014 | A1 |
| 20140089073 | Jacobs et al. | Mar 2014 | A1 |
| 20140089078 | Dessert et al. | Mar 2014 | A1 |
| 20140096179 | Ben-Shalom et al. | Apr 2014 | A1 |
| 20140099888 | Flanagan et al. | Apr 2014 | A1 |
| 20140100931 | Sanchez et al. | Apr 2014 | A1 |
| 20140100973 | Brown et al. | Apr 2014 | A1 |
| 20140101737 | Rhee | Apr 2014 | A1 |
| 20140108245 | Drummond et al. | Apr 2014 | A1 |
| 20140114775 | Cloin et al. | Apr 2014 | A1 |
| 20140114781 | Watanabe | Apr 2014 | A1 |
| 20140122345 | Argue et al. | May 2014 | A1 |
| 20140129357 | Goodwin | May 2014 | A1 |
| 20140129942 | Rathod | May 2014 | A1 |
| 20140136318 | Alberth, Jr. et al. | May 2014 | A1 |
| 20140136349 | Dave et al. | May 2014 | A1 |
| 20140149282 | Philliou et al. | May 2014 | A1 |
| 20140156508 | Argue et al. | Jun 2014 | A1 |
| 20140156517 | Argue et al. | Jun 2014 | A1 |
| 20140164234 | Coffman et al. | Jun 2014 | A1 |
| 20140180805 | Argue et al. | Jun 2014 | A1 |
| 20140184505 | Fullerton et al. | Jul 2014 | A1 |
| 20140201067 | Lai et al. | Jul 2014 | A1 |
| 20140207669 | Rosenberg | Jul 2014 | A1 |
| 20140214567 | Llach et al. | Jul 2014 | A1 |
| 20140214652 | Zheng et al. | Jul 2014 | A1 |
| 20140249947 | Hicks et al. | Sep 2014 | A1 |
| 20140250002 | Isaacson et al. | Sep 2014 | A1 |
| 20140254820 | Gardenfors et al. | Sep 2014 | A1 |
| 20140257958 | Andrews | Sep 2014 | A1 |
| 20140278589 | Rados et al. | Sep 2014 | A1 |
| 20140279098 | Ham | Sep 2014 | A1 |
| 20150012426 | Purves et al. | Jan 2015 | A1 |
| 20150025983 | Cicerchi | Jan 2015 | A1 |
| 20150032567 | Bhatia | Jan 2015 | A1 |
| 20150058146 | Gaddam et al. | Feb 2015 | A1 |
| 20150066765 | Banks et al. | Mar 2015 | A1 |
| 20150073907 | Purves et al. | Mar 2015 | A1 |
| 20150095228 | Su et al. | Apr 2015 | A1 |
| 20150100481 | Ghosh et al. | Apr 2015 | A1 |
| 20150120418 | Cervenka et al. | Apr 2015 | A1 |
| 20150134513 | Olson et al. | May 2015 | A1 |
| 20150134528 | Fineman et al. | May 2015 | A1 |
| 20150178755 | Barroso | Jun 2015 | A1 |
| 20150194023 | Brackenridge et al. | Jul 2015 | A1 |
| 20160086166 | Pomeroy et al. | Mar 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 10-2006-0103089 | Sep 2006 | KR |
| 2015061005 | Apr 2015 | WO |
| 2015069389 | May 2015 | WO |
| 2015100378 | Jul 2015 | WO |
| 2015179316 | Nov 2015 | WO |
| Entry |
|---|
| U.S. Appl. No. 13/830,350 of Morgan, T.B., et al., filed Mar. 14, 2013. |
| U.S. Appl. No. 13/837,562 of Chin, H.C.A., et al., filed Mar. 15, 2013. |
| U.S. Appl. No. 14/088,113 of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| U.S. Appl. No. 14/145,895 of Aaron, P., et al., filed Dec. 31, 2013. |
| U.S. Appl. No. 14/149,754 of Spindel, N., et al., filed Jan. 7, 2014. |
| U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014. |
| U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014. |
| U.S. Appl. No. 14/168,274 of Odawa, A., et al., filed Jan. 30, 2014. |
| U.S. Appl. No. 14/182,655 of Spindel, N., et al., filed Feb. 18, 2014. |
| U.S. Appl. No. 14/184,503 of Borovsky, A., et al., filed Feb. 19, 2014. |
| U.S. Appl. No. 14/189,869 of Lamba, K., et al., filed Feb. 25, 2014. |
| U.S. Appl. No. 14/189,880 of Aaron, P., et al., filed Feb. 25, 2014. |
| U.S. Appl. No. 14/208,800 of Thome, J.P., et al., filed Mar. 13, 2014. |
| U.S. Appl. No. 14/513,076 of Borovsky, A., et al., filed Oct. 13, 2014. |
| U.S. Appl. No. 14/088,141 of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Apr. 4, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A., et al., filed Feb. 4, 2014. |
| Non-Final Office Action dated Apr. 10, 2014, U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014. |
| Restriction Requirement dated Apr. 28, 2014, U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014. |
| Non-Final Office Action dated May 29, 2014, U.S. Appl. No. 13/837,562 of Chin, H.C.A., et al., filed Mar. 15, 2013. |
| Notice of Allowance dated Aug. 1, 2014, U.S. Appl. No. 14/172,842 of Borovsky, A., et al., filed Feb. 4, 2014. |
| Non-Final Office Action dated Aug. 27, 2014, U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014. |
| Final Office Action dated Aug. 28, 2014, U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014. |
| Advisory Action dated Nov. 18, 2014, U.S. Appl. No. 14/160,490 of Moring, D., et al., filed Jan. 21, 2014. |
| International search report and written opinion for PCT Application No. PCT/US2014/058398 dated Dec. 24, 2014. |
| Non-Final Office Action dated Jan. 9, 2015, U.S. Appl. No. 14/145,895 of Aaron, P., et al., filed Dec. 31, 2013. |
| International search report and written opinion for PCT Application No. PCT/US2014/058447 dated Jan. 15, 2015. |
| Final Office Action dated Jan. 26, 2015, U.S. Appl. No. 13/837,562 of Chin, H.C.A., et al., filed Mar. 15, 2013. |
| Notice of Allowance dated Feb. 20, 2015, U.S. Appl. No. 14/513,076 of Borovsky, A., et al., filed Oct. 13, 2014. |
| Final Office Action dated Mar. 17, 2015, U.S. Appl. No. 14/165,256 of Aaron, P., filed Jan. 27, 2014. |
| International search report and written opinion for PCT Application No. PCT/US2014/072269 dated Mar. 31, 2015. |
| Restriction Requirement dated Apr. 9, 2015, U.S. Appl. No. 14/225,338 of Aaron, P., et al., filed Mar. 25, 2014. |
| U.S. Appl. No. 14/692,655 of Borovsky, A., et al., filed Apr. 21, 2015. |
| Non-Final Office Action dated Apr. 27, 2015, U.S. Appl. No.14/184,503 of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated May 12, 2015, U.S. Appl. No. 14/189,869 of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Jul. 2, 2015, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014. |
| Restriction Requirement dated Jul. 24, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Final Office Action dated Aug. 18, 2015, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2015/031423 dated Aug. 13, 2015. |
| “Another EBay Band-Aid Fails to Fix the New Pricing Structure Flaws,” dated Oct. 18, 2008, Retrieved from the Internet URL: https://thebrewsnews.wordpress.com/2008/10/18/another-ebay-band-aid-fails-to-fix-the-new-pricing-structure-flaws/, pp. 1-5. |
| “Online Shopping,” dated Nov. 2, 2014, Retrieved from the Internet URL: http://en.wikipedia.org/wiki/Online—shopping, on Nov. 10, 2014, pp. 1-12. |
| Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D, dated Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3. |
| Myres, L., “What is Multi-Factor Authentication, and How Will it Change in the Future?, ” Intego, dated Aug. 17, 2012, Retrieved from the Internet URL: http://www.intego.com/mac-security-blog/what-is-multi-factor-authentication-and-how-will-it-change-in-the-future/, on Nov. 11, 2014, pp. 1-4. |
| Wallen, J., “Five Top Apps for Managing Inventory,” Tech Republic, dated Aug. 15, 2012, Retrieved from the Internet URL: http://www.techrepublic.com/blog/five-apps/five-top-apps-for-managing-inventory/, on Nov. 10, 2014, pp. 1-7. |
| U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| U.S. Appl. No. 14/730,860, of Sasmaz, Y., et al., filed Jun. 4, 2015. |
| Non-Final Office Action dated Mar. 19, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| Non-Final Office Action dated May 20, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated May 26, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Non-Final Office Action dated May 27, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| Non-Final Office Action dated Jun. 11, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Restriction Requirement dated Jun. 19, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| “Tracking Inventory,” PayPal, dated Jan. 4, 2010, Retrieved from the Internet URL: https://www.paypal-community.com/t5/How-to-use-PayPal-Archive/Tracking-inventory/td-p/19392, pp. 1-3. |
| Final Office Action dated Sep. 17, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Notice of Allowance dated Sep. 18, 2015, for U.S. Appl. No. 14/197,704, of Lamba, K., et al., filed Mar. 5, 2014. |
| Final Office Action dated Sep. 21, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Sep. 30, 2015, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014. |
| Final Office Action dated Oct. 2, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Non-Final Office Action dated Oct. 5, 2015, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Oct. 6, 2015, for U.S. Appl. No. 14/329,658, of Aaron, P., et al. filed Jul. 11, 2014. |
| Non-Final Office Action dated Oct. 8, 2015, for U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014. |
| Non-Final Office Action dated Oct. 8, 2015, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Final Office Action dated Oct. 16, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Final Rejection dated Oct. 21, 2015, for U.S. Appl. No. 14/329,638, of Aaron, P., et al. filed Jul. 11, 2014. |
| Non-Final Office Action dated Nov. 18, 2015, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Advisory Action dated Nov. 24, 2015, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Dec. 4, 2015, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| “Merchantindustry.com—Best Merchant Services,” retrieved from Internet URL: https://web.archive.org/web/20121020212419/http://www.merchantindustry.com/, on Dec. 30, 2015, pp. 1-7. |
| Advisory Action dated Dec. 30, 2015, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Final Office Action dated Dec. 31, 2015, for U.S. Appl. No. 14/208,800, of Thome, J. P., et al., filed Mar. 13, 2014. |
| Advisory Action dated Dec. 31, 2015, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Non-Final Office Action dated Jan. 22, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Feb. 2, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T, B., et al., filed Mar. 14, 2013. |
| Restriction Requirement dated Feb. 29, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Mar. 14, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Restriction Requirement dated Mar. 16, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D. W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Mar. 24, 2016, U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Non-Final Office Action dated Jul. 21, 2016, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Sep. 1, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Notice of Allowance dated Sep. 13, 2016, for U.S. Appl. No. 14/692,655, of Borovsky, A., et al., filed Apr. 21, 2015. |
| Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Sep. 21, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Non-Final Office Action dated Sep. 21, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., filed Feb. 25, 2014. |
| Non-Final Office Action dated Sep. 22, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Final Office Action dated Apr. 13, 2016, for U.S. Appl. No. 14/165,256, of Aaron, P., filed Jan. 27, 2014. |
| Final Office Action dated Apr. 27, 2016, for U.S. Appl. No. 14/182,655, of Spindel, N., et al., filed Feb. 18, 2014. |
| Final Office Action dated Apr. 28, 2016, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated May 3, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T. B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated May 9, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2013. |
| Non-Final Office Action dated Jan. 20, 2017, for U.S. Appl. No. 14/168,274, of Odawa, A.W., et al., filed Jan. 30, 2014. |
| Corrected Notice of Allowance dated Feb. 27, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Notice of Allowance dated Mar. 2, 2017, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Final Office Action dated Mar. 2, 2017, for U.S. Appl. No. 14/189,880, of Aaron, P., et al., filed Feb. 25, 2014. |
| Advisory Action dated Mar. 9, 2017, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Non-Final Office Action dated Mar. 13, 2017, for U.S. Appl. No. 14/189,869, of Lamba, K., et al., filed Feb. 25, 2014. |
| Non-Final Office Action dated Mar. 15, 2017, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Examiner Requisition for Canadian Patent Application No. 2,930,186, mailed Jan. 30, 2017. |
| Notice of Acceptance for Australian Patent Application No. 2014347192, mailed Feb. 16, 2017. |
| Final Office Action dated Nov. 10, 2016, for U.S. Appl. No. 13/830,350, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Final Office Action dated Nov. 29, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Final Office Action dated Nov. 30, 2016, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014. |
| Final Office Action dated Dec. 12, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Advisory Action dated Dec. 22, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Final Office Action dated Dec. 27, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Notice of Allowance dated Jan. 13, 2017, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Jan. 27, 2017, for U.S. Appl. No. 14/329,638, of Aaron, P., et al., filed Jul. 11, 2014. |
| Examination Report No. 1 for Australian Patent Application No. 2014347192, dated Dec. 15, 2016. |
| Advisory Action dated Sep. 29, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Final Office Action dated Oct. 11, 2016, for U.S. Appl. No. 13/829,080, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Advisory Action dated Oct. 11, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K, et al., filed Feb. 25, 2014. |
| Final Office Action dated Oct. 12, 2016, for U.S. Appl. No. 14/145,895, of Aaron, P., et al., filed Dec. 31, 2013. |
| Final Office Action dated Nov. 1, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Notice of Allowance dated Nov. 8, 2016, for U.S. Appl. No. 14/225,338, of Aaron, P., et al., filed Mar. 25, 2014. |
| Shalmanese, “The Straight Dope Message Board,” message dated Oct. 5, 2013, Retrieved from the internet URL: http://boards.straightdope.com/sdmb/showthread.php?t=703989%BB, on Jul. 18, 2016, pp. 1-10. |
| Final Office Action dated May 20, 2016, for U.S. Appl. No. 14/329,658, of Aaron, P., et al., filed Jul. 11, 2014. |
| Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/088,113, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Jun. 7, 2016, for U.S. Appl. No. 14/208,800, of Thome, J.P., et al., filed Mar. 13, 2014. |
| Non-Final Office Action dated Jun. 8, 2016, for U.S. Appl. No. 14/088,141, of Maxwell, D.W., et al., filed Nov. 22, 2013. |
| Non-Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/184,503, of Borovsky, A., et al., filed Feb. 19, 2014. |
| Final Office Action dated Jun. 17, 2016, for U.S. Appl. No. 14/149,754, of Spindel, N., et al., filed Jan. 7, 2014. |
| Final Office Action dated Jun. 20, 2016, for U.S. Appl. No. 13/829,658, of Morgan, T.B., et al., filed Mar. 14, 2013. |
| Non-Final Office Action dated Jul. 14, 2016, for U.S. Appl. No. 14/160,490, of Moring, D., et al., filed Jan. 21, 2014. |
| Final Office Action dated Jul. 18, 2016, for U.S. Appl. No. 14/189,869, of Lamba, K., el al., filed Feb. 25, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14225338 | Mar 2014 | US |
| Child | 14526361 | US |
