US20140012704A1 - Selecting a preferred payment instrument based on a merchant category - Google Patents
Selecting a preferred payment instrument based on a merchant category Download PDFInfo
- Publication number
- US20140012704A1 US20140012704A1 US13/542,303 US201213542303A US2014012704A1 US 20140012704 A1 US20140012704 A1 US 20140012704A1 US 201213542303 A US201213542303 A US 201213542303A US 2014012704 A1 US2014012704 A1 US 2014012704A1
- Authority
- US
- United States
- Prior art keywords
- merchant
- category
- computer
- user
- transaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0613—Third-party assisted
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
Definitions
- the present disclosure relates generally to contactless payment transactions, and more particularly to a method for selecting a preferred payment instrument in a contactless payment transaction based on a category of the merchant.
- Contactless payments can be transacted by a mobile device of a user with a point of sale terminal of a merchant.
- the mobile device can communicate with the terminal via near field communication (“NFC”), BLUETOOTH, Wi-Fi, infrared, or any other suitable communication technology.
- NFC near field communication
- BLUETOOTH BLUETOOTH
- Wi-Fi Wi-Fi
- infrared or any other suitable communication technology.
- the mobile device can host a payment application, such as a digital wallet, that can complete a transaction with the terminal.
- the point of sale terminal can obtain the payment information from the user device and transmit transaction details to the user device.
- the point of sale terminal can submit the transaction details to the card network to receive payment from the card issuer.
- the payment application on a mobile device can support multiple financial accounts and the cards associated with the account.
- the user can conduct a transaction with different financial instruments, such as credit cards, debit cards, stored value cards, or other payment cards, supported by the application.
- financial instruments such as credit cards, debit cards, stored value cards, or other payment cards, supported by the application.
- the user must select a card at the time of purchase with which to conduct the transaction. That is, at the time of purchase, the user must select a card and apply it to the purchase. Alternatively, the user may assign a card for all transactions until the assignment is changed.
- Some cards may be better suited for a particular transaction than other cards. For example, some cards provide better rewards or provide better terms for transactions with certain merchant categories. Remembering which card is the best card for every transaction can create a burden for a user.
- a similar process and corresponding deficiencies apply to the use of a payment application for conducting a transaction with an online merchant.
- the user can attempt a purchase with an online merchant, select a card on the payment application to conduct the transaction, and submit the payment information.
- the user may have a digital wallet for online purchases that has a card assigned to all purchases.
- the present invention provides a computer-implemented method to select a preferred card for a purchase based on a merchant category.
- the computer associates a plurality of financial accounts with an account of a user, the user account being maintained on the computer; associates a merchant category with a financial account associated with the user account; and receives data from a transaction of the user account with a merchant from a user network device.
- the computer can maintain a database of merchant categories; determine the category of the merchant based on the data associated with the transaction; and extract data to identify the merchant, such as merchant name, address, or telephone number.
- the computer can determine the geo-location of the user device and determine the merchant identify from the location.
- the computer can determine a merchant category of the merchant from the merchant identity; select the financial account associated with the merchant category of the merchant; and communicate the financial account selected to conduct the transaction.
- the computer program product includes a non-transitory computer-readable storage device having computer-readable program instructions stored therein.
- the computer-readable program instructions include computer program instructions to associate a plurality of financial accounts with an account of a user, the user account being maintained on the computer; associate a merchant category with a financial account associated with the user account; and receive data from a transaction of the user account with a merchant from a user network device.
- the instructions can be further configured to maintain a database of merchant categories; determine the category of the merchant based on the data associated with the transaction; and extract data to identify the merchant, such as merchant name, address, or telephone number.
- the instructions can be further configured to determine the geo-location of the user device and determine the merchant identify from the location.
- the instructions can be further configured to determine a merchant category of the merchant from the merchant identity; select the financial account associated with the merchant category of the merchant; and communicate the financial account selected to conduct the transaction.
- FIG. 1 is a block diagram depicting a system for a payment system to select a preferred card for a contactless payment transaction based on the merchant category, in accordance with certain exemplary embodiments.
- FIG. 2 is a block flow diagram depicting a method to establish a preferred card rule, in accordance with certain exemplary embodiments.
- FIG. 3 is a block flow diagram depicting a method for selecting a preferred card in a contactless payment transaction based on the merchant category, in accordance with certain exemplary embodiments.
- FIG. 4 is a block flow diagram depicting a method to analyze transaction details and determine a merchant category, in accordance with certain exemplary embodiments.
- a payment system and payment application include specified information for multiple financial accounts, including, but not limited to debit cards, credit cards, stored value cards, loyalty/rewards cards, and coupons (including purchased offers and other offers), each accessible by a digital wallet on a user device.
- the different financial accounts used for payment transactions will be collectively referred to as “cards”.
- the user sets rules specifying which financial account will be accessed when a contactless transaction is attempted.
- the user can then add, delete, or change the default payment rules associated with the user.
- the user can change these default static rules, create new rules, or delete a rule.
- the user can access the payment system account and modify the rules at any time, including a time immediately before a payment transaction is initiated.
- the user can access the payment system account using a mobile device application.
- the rules can be maintained on the payment application on the user devise or on a server at the payment system.
- the user can access a user interface through the user device or on the payment system to establish rules for the preferred card selection.
- the user can identify a card and associate a merchant category with the card. A transaction at any merchant who is associated with the merchant category will be conducted with the identified card.
- a user can associate different merchant categories with different cards.
- the user can be presented with a list of merchant categories and associate cards with the categories that the user is likely to encounter.
- Merchants can be categorized based on user-configured categories, payment system configured categories, or industry standard categories such as a merchant category code (“MCC”).
- MCC merchant category code
- a database of merchant categories and the assigned merchants can be maintained on the payment system and/or the payment application.
- the merchants in the database can be identified based on data including products sold, address, name, geo-location, phone number, and any other identifying data.
- the payment system may recommend an association to the user.
- the payment system can receive the identities of cards associated with merchant categories from other users of the payment system.
- the payment system can determine which card of the user is the most often selected for a particular merchant category.
- the payment system can recommend that the user associate the identified card with that particular merchant category.
- the payment system can be configured to use the recommended card as a default option should the user not make a selection for a particular category.
- the payment system may be configured to use a recommended card in all transactions. That is, the user may not associate any cards with merchant categories and may use a recommended card for all transactions.
- a user can tap or swipe a mobile device to initiate a payment transaction.
- the user may initiate the transaction in any other suitable manner, such as pressing a real or virtual button or speaking a voice command.
- the user device and the point of sale terminal or other terminal reader device can establish a communication.
- the point of sale terminal can transmit details of the merchant and/or the product to be purchased to the user device.
- the payment application on the user device can receive the details and determine if the merchant is identified in a category.
- the merchant details can be compared to the details of merchant categories stored in the merchant category database.
- Merchant details can include any information that may identify the merchant such as address, name, phone number, and any other identifying data.
- the user device can additionally or alternatively determine the geo-location of the merchant based on a location application on the device. For example, the user device can use the global positioning system capabilities of the user device or other location determining hardware or software to determine the geo-location of the merchant. The geo-location can be compared to the geo-location of merchants stored in the database to identify a merchant. Alternatively, any other database, registry, or source may be utilized to determine the identity of a merchant based on the geo-location provided.
- the payment system can use the purchased products to identify a merchant category.
- the purchased products can be compared to the products sold by merchants in the category database. If an unidentified merchant sells similar products to other merchants in a category then the unidentified merchant can be placed into that category.
- the payment system can select the preferred card and transmit the identity of the preferred card to the user device. Additionally or alternatively, the payment system can transmit the category of the merchant to the user device and the payment application can determine the preferred card.
- the payment application can display, via a user interface, the identity of the preferred card to the user.
- the user can accept the card selected and proceed with the transaction or reject the selected card and select an alternative card. Alternatively, the payment application may proceed with the transaction without the approval of the user.
- the payment application can transmit the card information to the point of sale terminal and complete the transaction.
- all of the steps can be performed in an online transaction.
- the user device may attempt a transaction with an online merchant.
- the merchant can submit the transaction and the merchant details.
- the payment system can determine a category of the online merchant.
- the payment system can select a preferred card for that category and transmit the identification of the preferred card to the merchant to conduct the transaction.
- FIG. 1 is a block diagram depicting a system for selecting a preferred card in a contactless payment transaction with a user network device, in accordance with certain exemplary embodiments.
- the system 100 includes network devices 110 , 130 , 140 , and 170 that are configured to communicate with one another via one or more networks 105 .
- Each network 105 includes a wired or wireless telecommunication means by which network devices (including devices 110 , 130 , 140 , and 170 ) can exchange data.
- each network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof.
- LAN local area network
- WAN wide area network
- intranet an Internet
- Internet a mobile telephone network
- Each network device 110 , 130 , 140 , and 170 includes a device having a communication module capable of transmitting and receiving data over the network 105 .
- each network device 110 , 130 , 140 , and 170 can include a server, desktop computer, laptop computer, tablet computer, smart phone, handheld computer, personal digital assistant (“PDA”), or any other wired or wireless, processor-driven device.
- PDA personal digital assistant
- the network devices 110 , 130 , 140 and 170 are operated by end-users or consumers, merchant operators, payment system operators, and card issuer operators, respectively.
- the user 101 can use a communication application 112 , such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributed network 105 .
- the network 105 includes a wired or wireless telecommunication system or device by which network devices (including devices 110 , 130 , 140 , and 170 ) can exchange data.
- the network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
- LAN local area network
- WAN wide area network
- intranet an Internet
- SAN storage area network
- PAN personal area network
- MAN metropolitan area network
- WLAN wireless local area network
- VPN virtual private network
- cellular or other mobile communication network Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
- the communication application 112 can interact with web servers or other computing devices connected to the network 105 , including the point of sale terminal 132 of the merchant 130 , the merchant server 135 of the merchant 130 , the web server 141 of the payment system 140 , and the card issuer 170 .
- the communication application 112 can further communicate with the terminal reader 132 and/or the point of sale terminal 132 of the merchant 130 via any contactless communication technology such as NFC,z BLUETOOTH, Wi-Fi, infrared, or other suitable technology.
- the user network device 110 may include a digital wallet application 111 .
- the digital wallet 111 may encompass any application, hardware, software, or process the user device 110 may employ to assist the user 101 in completing a purchase.
- the digital wallet 111 can interact with the communication application 112 or can be embodied as a companion application of the communication application 112 .
- the digital wallet 111 executes within the communication application 112 . That is, the digital wallet 111 may be an application program embedded in the communication application 112 .
- the user device 110 can include a payment application 115 .
- the payment application 115 can interact with the communication application 112 or be embodied as a companion application of the communication application 112 and execute within the communication application 112 .
- the payment application 115 may further be embodied as a companion application of the digital wallet 111 and execute within the digital wallet 111 .
- the payment application 115 may employ a software interface for configuration that may open in the digital wallet application 111 or may open in the web browser application 112 . Alternatively, the payment application 115 may be execute on the user device 110 independent of the digital wallet 111 and the communication application 112 .
- the payment application 115 is operable to allow a user 101 to configure payment accounts on the user device 110 and the payment system 140 .
- the payment application 115 can allow the user 101 to receive transaction details, select preferred cards for a transaction, receive notice of a card selection, provide card information, and provide other suitable services.
- the user device 110 also includes a data storage unit 113 accessible by the digital wallet 111 , the payment application 115 , and the communication application 112 .
- the exemplary data storage unit 113 can include one or more tangible computer-readable storage devices.
- the data storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110 .
- the data storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory.
- the payment system 140 includes a data storage unit 147 accessible by the web server 144 .
- the exemplary data storage unit 147 can include one or more tangible computer-readable storage devices.
- Some or all of the functions of the payment system 140 may be alternatively performed on the payment application 115 of the digital wallet 111 . Additionally or alternatively, some or all of the functions of the payment application 115 and the digital wallet 111 may be performed on the payment system 140 .
- the user 101 can use a web server 144 on the payment system 140 to view, register, download, upload, or otherwise access the payment system 140 via a website (not illustrated) and a communication network 105 ).
- the user 101 associates one or more registered financial card accounts, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, store rewards cards, or other type of financial account that can be used to make a purchase or redeem value-added services with the user account.
- the registered financial card accounts may have multiple issuers 170 that maintain each financial account.
- the payment system 140 also may function as the issuer for the associated financial account.
- the user's 101 registration information is saved in the payment system's 140 data storage unit 147 and is accessible the by web server 144 .
- the user 101 also may use the web server 144 to define contactless payment rules and bidding rules.
- the creation of payment application 115 card selection rules is discussed in more detail hereinafter with reference to the methods described in FIG. 3 .
- the merchant 130 may use a web server 135 to view, download, upload, create offers, sell products online, or otherwise access the payment system 140 via a website 134 and a communication network 105 .
- the web server 135 may be part of the merchant 130 and located at the merchant 130 location.
- the web server 135 may alternatively be located at a remote location.
- the merchant 130 represents an entity that offers products for the user 101 to purchase or use.
- the merchant 130 includes a point of sale (“POS”) terminal 132 .
- the POS terminal 132 may be operated by a salesperson that enters the purchase data into the POS terminal 132 to complete the purchase transaction.
- the merchant 130 may be embodied as a physical merchant at a physical location or an online merchant.
- the merchant 130 can employ a terminal reader 131 that can communicate with the user device 110 and receive payment information.
- the terminal reader 131 may be a function of the POS terminal 132 or may be logically coupled to the POS terminal 132 .
- the user 101 may request a purchase from the merchant 130 .
- the purchase is initiated by a wireless “tap” of the mobile device 110 with the terminal reader 131 .
- the purchase is initiated when the user 101 enters an account identification number at the POS terminal 132 or in the mobile device 110 .
- the purchase is initiated online with the merchant server 135 .
- the purchase may be initiated via the merchant website 136 .
- the purchase is initiated by use of a permanent/temporary virtual/physical token, QR code, bar code, or other suitable machine-readable medium captured by the terminal reader 131 .
- the merchant's POS terminal 132 interacts with an acquirer (for example Chase PaymentTech, or other third party payment processing companies), a card network (for example VISA, MasterCard, American Express, Discover or other card processing networks), the payment system 140 , and the issuer 170 (for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment).
- acquirer for example Chase PaymentTech, or other third party payment processing companies
- card network for example VISA, MasterCard, American Express, Discover or other card processing networks
- the payment system 140 for example VISA, MasterCard, American Express, Discover or other card processing networks
- issuer 170 for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment.
- the components of the exemplary operating environment 100 are described hereinafter with reference to the exemplary methods illustrated in FIGS. 2 .
- FIG. 2 is a block flow diagram depicting a method 200 to select a preferred card in a contactless payment transaction with a user network device, in accordance with certain exemplary embodiments.
- the user 101 configures the rules for the payment application 115 .
- the rules can include instructions for selecting a card to use in a transaction with a merchant 130 .
- the rules include instructions to select a card based on the merchant categories associated with the card. The details of a method to define the preferred card rules are discussed in greater detail in the method 205 with reference to FIG. 3 .
- FIG. 3 is a block flow diagram depicting a method 205 for establishing a preferred card rule in a payment application 115 , in accordance with certain exemplary embodiments.
- a user 101 identifies a card associated with a financial account with a card issuer 170 .
- the payment system 140 and payment application 115 can include specified information for multiple financial accounts, including, but not limited to debit cards, credit cards, stored value cards, loyalty/rewards cards, and coupons (including purchased offers and other offers).
- the user 101 can set rules specifying which financial account will be accessed when a contactless transaction is attempted.
- the user 101 can then add, delete, or change the default payment rules associated with the user 101 .
- the user 101 can change these default static rules, create new rules, or delete a rule.
- the user 101 can access the payment system account and modify the rules at any time, including a time immediately before a payment transaction is initiated.
- the user 101 can access the payment system account using a payment application 115 on a user device 110 .
- the rules can be maintained on the payment application 115 on the user devise 110 or on a server 144 at the payment system 140 .
- the user 101 can associate one or more merchant categories with the identified card. For example, the user 101 can configure all transactions with the merchants from a particular category to be conducted with the identified card. Merchants 130 can be categorized based on user 101 configured categories, payment system 140 configured categories, or industry standard categories such as a merchant category code (“MCC”). A database of merchant categories and the assigned merchants can be maintained on the payment system 140 and/or the payment application 115 . The user 101 may be presented with a list of merchant categories and offered the opportunity to associate one or more of the categories with the identified card. Alternatively, the user 101 may be presented with the option of entering text descriptions of businesses, names of businesses, or other text input. The payment system 140 may receive the user input and determine the corresponding merchant category from a database of merchant categories.
- MCC merchant category code
- the payment system 140 can recommend a card.
- the payment system 140 can recommend a card at the time of a transaction with a merchant 130 in a category that is not associated with a card.
- the payment system 140 can search the accounts of other users of a card issued by a card network 170 associated with the account of the user 101 .
- the payment system 140 can additionally or alternatively focus the search on other users of a card that has the same conditions, terms, rewards, or any other suitable criteria.
- the payment system 140 can identify frequently associated merchant categories in the accounts of the other users of the card.
- the payment system 140 can recommend the identified merchant category to the user 101 .
- the recommendation can be transmitted to the user 101 via the payment application 115 , email, text, or other suitable communication technology.
- the payment system 140 may alternatively search the merchant categories for a ranking of the most frequent cards with which the merchant categories are associated.
- the payment system 140 can search the associated cards to determine if the user 101 has any of the highly ranked cards associated with the user account.
- the payment system 140 can determine which card of the user 101 is the most highly ranked for a particular merchant category.
- the payment system 140 can recommend the user 101 associate the most highly ranked card and the particular merchant category.
- the recommendation may be transmitted to the user 101 via the payment application 115 , email, text, or other suitable communication technology.
- the user 101 associates the recommended card with the recommended merchant category.
- the association may be performed by the user 101 during configuration or at any time after configuration. Additionally or alternatively, the recommendation may be made at the time that a purchase is attempted at a merchant 130 that belongs to a merchant category that has not been associated with a card.
- the user account may be configured to automatically associate a merchant category with a card if the user 101 has not previously performed the association.
- the automatic association may occur at any time in the process including, but not limited to, the time of sign up, the time of configuration, or when a purchase is attempted.
- the user 101 may additionally configure a default card to be used for any transaction with a merchant 130 belonging to a merchant category that has not been associated with a card.
- the default card may additionally or alternatively, be employed in a transaction where the merchant category cannot be established.
- a user 101 visits a merchant 130 and selects a product for purchase.
- product(s) should be interpreted to include tangible and intangible products, as well as services.
- the user 101 can approach a point of sale (“POS”) terminal 132 of a merchant 130 .
- POS point of sale
- the user 101 can “tap” or swipe a user network device 110 , such as a near field communication (“NFC”) enabled user device 110 , to a terminal reader 131 executing on, or logically coupled to, the POS device 132 .
- NFC near field communication
- the user 101 may initiate the transaction in any other suitable manner, such as pressing a real or virtual button or speaking a voice command.
- the user device 110 and the POS terminal 132 or other terminal reader 131 device can establish a communication.
- the user device 110 and the POS terminal 132 can communicate via near field communication (“NFC”), BLUETOOTH, Wi-Fi, infrared, or any other suitable communication technology.
- NFC near field communication
- BLUETOOTH BLUETOOTH
- Wi-Fi Wi-Fi
- infrared any other suitable communication technology.
- the POS terminal 132 can transmit a payment processing request to the user device 110 .
- the POS terminal 132 can transmit details of the transaction to the user device 110 and request details of the financial account or card that will conduct the transaction.
- the POS terminal 132 can transmit details of the merchant 130 .
- the details about the merchant 130 may include, but not be limited to, the merchant category code (“MCC”), the location, the name, the products sold by the merchant 130 , and other suitable details that may assist the payment system 140 in determining the merchant category.
- MCC merchant category code
- the user device 110 can additionally or alternatively determine the geo-location of the merchant 130 based on a location application on the device. For example, the user device 110 can use the global positioning system capabilities of the user device 110 or other location determining application or hardware to determine the geo-location of the merchant 130 . The geo-location of the transaction can be compared to the geo-location of merchants stored in a database to identify a merchant 130 .
- the transaction details and the merchant details can be transmitted to the payment system 140 by the payment application 115 .
- the transmission may be conducted via an Internet connection over the network 105 , email, text, or any other suitable communication technology.
- the payment system 140 can compare the details of the merchant 130 to determine the category of the merchant 130 .
- the payment system 140 may utilize the categories as defined by the MCC or the payment system 140 may create and maintain another established category system or develop a new category system.
- the category system may additionally or alternatively be configured by the user 101 or other operator.
- the categorizing of the merchant 130 may be executed on the payment application 115 .
- the category of the merchant 130 can be determined through an analysis of the details provided with the transaction.
- the details may specify an MCC of the merchant 130 .
- the payment system can use the MCC to directly establish the category of the merchant 130 .
- the details may additionally or alternatively provide a different type of category designation, such as one developed by the payment system 140 , the merchant 130 , the user 101 or another suitable party.
- the details may provide a general description of the category of the merchant.
- the details may specify that the merchant 130 associated with the transaction is a restaurant, an oil change facility, or a hair salon.
- the payment system 140 can use the specified merchant type to associate the merchant with a category.
- method 220 follows the “YES” branch of block 405 to block 225 with respect to FIG. 2 . If the MCC or other category designation is not provided, then method 220 follows the “NO” branch of block 405 to block 410 .
- the payment system 140 can determine if the merchant 130 name or other identifying detail has previously been recorded in a database. If the merchant 130 has previously conducted a transaction with the payment system 140 , the merchant 130 may already be identified by name in a category. If the details provide the name of the merchant 130 , the payment system 140 can identify the category to which the merchant 130 belongs by searching the category database and determining the category with which the merchant 130 identity has previously been associated. The payment system 140 can use other identifying information from the details to find the merchant 130 in the database to determine the category of the merchant 130 . Other identifiers that may be in a category database for a merchant 130 may include the address, phone number, or other identifying details of a merchant 130 .
- method 220 follows the “YES” branch of block 410 to block 425 . If the merchant is not identified, then method 220 follows the “NO” branch of block 410 to block 415 .
- the payment system 140 can identify the geo-location of the user device 110 .
- the payment system 140 can identify the merchant 130 associated with that location.
- the geo-location of the user device 110 can be determined from the global positioning system hardware and software utilized by the user device 110 .
- the user device 110 can transmit the geo-location to the payment system 140 upon request or with every transaction request.
- the user device 110 can determine the geo-location from any other hardware or software technology available to the user device 110 , such as a geo-location received from a Wi-Fi system being accessed by the user device 110 or other system.
- the payment system 140 can use the geo-location of the user device 110 , and thus the location of the merchant 130 , to determine the identity of the merchant 130 .
- the identity may be determined by using a registry of merchant addresses, a mapping application or website, or other database or system to identify a merchant 130 from the geo-location of the merchant 130 .
- method 220 follows the “YES” branch of block 420 to block 425 . If the merchant is not identified, then method 220 follows the “NO” branch of block 420 to block 430 .
- the payment system can use the identity of the merchant 130 to identify the category to which the merchant 130 belongs. If the merchant 130 has previously conducted a transaction with the payment system 140 , then the payment system 140 may have placed the merchant 130 in a category at that time. If the payment system 140 has previously placed the merchant 130 into a category, then the payment system 140 can identify the merchant in the database and extract the category in which the merchant 130 is stored.
- the payment system 140 may employ a system for identifying merchants 130 and placing the merchants 130 in categories at a time other than at the time of a transaction. That is, the payment system 140 may continuously or periodically search for merchants 130 that are not categorized and attempt to place the merchants 130 in categories in the database.
- the payment system 140 may additionally or alternatively, subscribe to a system or service that updates the category codes, such as an MCC, and supplies the categories of merchants 130 to the payment system 140 .
- the payment system 140 may utilize any other system or process to update the merchants 130 located in the category database.
- the payment system 140 can determine that the merchant 130 associated with the current transaction is the same merchant 130 located in the database. The payment system 140 can thus determine the category of the merchant 130 .
- method 220 follows the “YES” branch of block 425 to block 225 with respect to FIG. 2 . If the merchant category is not determined from the merchant 130 identity, then method 220 follows the “NO” branch of block 425 to block 430 .
- the payment system 140 can use the products associated with the transaction to identify a merchant category.
- the products associated with the transaction can be identified from the description of the products, a model number associated with the products, a stock-keeping unit (“SKU”) or other identifying code, or other identifier from the transaction.
- SKU stock-keeping unit
- the products can be compared to the products sold by other merchants in the category database. If the merchant 130 sells similar products to other merchants in a category then the merchant 130 can be placed into that category.
- the payment system 140 may employ a scoring system to determine the category. For example, the merchant 130 may receive points for every product in common with the merchants in a product category. A threshold of points may be required to place the merchant 130 in the category. Any scoring system or other system for determining if the products of the merchant 130 match the products of the merchants in a category may be utilized.
- the payment system 140 associates the merchant 130 with the category of the merchants with which the merchant 130 sells similar products.
- the payment system 140 may associate the merchant 130 with the category for only the pending transaction or the payment system 140 may associate the merchant 130 with the selected category for future transactions.
- the association may be permanent or may be associated until such time as a more accurate category is assigned.
- the method 220 returns to block 225 in FIG. 2 .
- the payment system 140 can select the preferred card and transmit the identity of the preferred card to the user device 110 .
- the payment system 140 can transmit the category of the merchant 130 to the user device and the payment application 115 can determine the preferred card for the merchant category.
- the payment application 115 can display, via a user interface, the identity of the preferred card to the user 101 .
- the user 101 can accept the card selected and proceed with the transaction or reject the selected card and select an alternative card.
- the payment application 115 may proceed with the transaction without the approval of the user 101 .
- the payment application 115 can transmit the card information to the POS terminal 132 and complete the transaction.
- the merchant 130 can receive the card information and conduct the transaction with the issuer 170 of the selected card.
- Some or all of the functions of the payment system 140 may be alternatively performed on the payment application 115 of the digital wallet 111 . Additionally or alternatively, some or all of the functions of the payment application 115 and the digital wallet 111 may be performed on the payment system 140 .
- all of the steps can be performed in an online transaction.
- the user device 110 can attempt a transaction with an online merchant 130 .
- the merchant 130 can submit the transaction and the merchant details.
- the payment system 140 or a payment application 115 can determine a category of the online merchant 130 via the process as described above.
- the payment system 140 or a payment application 115 can select a preferred card for that category and transmit the identification of the preferred card to the merchant 130 to conduct the transaction.
- Users may be allowed to limit or otherwise affect the operation of the features disclosed herein. For example, users may be given opportunities to opt-in or opt-out of the collection or use of certain data or the activation of certain features. In addition, users may be given the opportunity to change the manner in which the features are employed. Instructions also may be provided to users to notify them regarding policies about the use of information, including personally identifiable information, and manners in which each user may affect such use of information. Thus, information can be used to benefit a user, if desired, through receipt of relevant advertisements, offers, or other information, without risking disclosure of personal information or the user's identity.
- One or more aspects of the invention may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions.
- the invention should not be construed as limited to any one set of computer program instructions.
- a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed invention based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the invention.
- the exemplary embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously.
- the systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry.
- the software can be stored on computer-readable media.
- computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc.
- Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Cash Registers Or Receiving Machines (AREA)
Abstract
The invention provides a computer-implemented method to select a preferred card for a purchase based on a merchant category. In the exemplary method, the computer associates a plurality of financial accounts with an account of a user; associates a merchant category with a financial account associated with the user account; and receives data from a transaction. The computer can maintain a database of merchant categories; determine the category of the merchant based on the data associated with the transaction; and extract data to identify the merchant, such as merchant name, address, or telephone number. The computer can determine the geo-location of the user device and determine the merchant identify from the location. The computer can determine a merchant category of the merchant from the merchant identity; select the financial account associated with the merchant category of the merchant; and communicate the financial account selected to conduct the transaction.
Description
- The present disclosure relates generally to contactless payment transactions, and more particularly to a method for selecting a preferred payment instrument in a contactless payment transaction based on a category of the merchant.
- Contactless payments can be transacted by a mobile device of a user with a point of sale terminal of a merchant. The mobile device can communicate with the terminal via near field communication (“NFC”), BLUETOOTH, Wi-Fi, infrared, or any other suitable communication technology. The mobile device can host a payment application, such as a digital wallet, that can complete a transaction with the terminal.
- The point of sale terminal can obtain the payment information from the user device and transmit transaction details to the user device. The point of sale terminal can submit the transaction details to the card network to receive payment from the card issuer.
- The payment application on a mobile device can support multiple financial accounts and the cards associated with the account. The user can conduct a transaction with different financial instruments, such as credit cards, debit cards, stored value cards, or other payment cards, supported by the application. Currently, the user must select a card at the time of purchase with which to conduct the transaction. That is, at the time of purchase, the user must select a card and apply it to the purchase. Alternatively, the user may assign a card for all transactions until the assignment is changed.
- Some cards may be better suited for a particular transaction than other cards. For example, some cards provide better rewards or provide better terms for transactions with certain merchant categories. Remembering which card is the best card for every transaction can create a burden for a user.
- A similar process and corresponding deficiencies apply to the use of a payment application for conducting a transaction with an online merchant. The user can attempt a purchase with an online merchant, select a card on the payment application to conduct the transaction, and submit the payment information. The user may have a digital wallet for online purchases that has a card assigned to all purchases.
- The present invention provides a computer-implemented method to select a preferred card for a purchase based on a merchant category. In the exemplary method, the computer associates a plurality of financial accounts with an account of a user, the user account being maintained on the computer; associates a merchant category with a financial account associated with the user account; and receives data from a transaction of the user account with a merchant from a user network device. The computer can maintain a database of merchant categories; determine the category of the merchant based on the data associated with the transaction; and extract data to identify the merchant, such as merchant name, address, or telephone number. The computer can determine the geo-location of the user device and determine the merchant identify from the location. The computer can determine a merchant category of the merchant from the merchant identity; select the financial account associated with the merchant category of the merchant; and communicate the financial account selected to conduct the transaction.
- Another aspect of the present invention provides a computer program product that is installed on a server located in a payment system to select a preferred card for a purchase based on a merchant category. The computer program product includes a non-transitory computer-readable storage device having computer-readable program instructions stored therein. The computer-readable program instructions include computer program instructions to associate a plurality of financial accounts with an account of a user, the user account being maintained on the computer; associate a merchant category with a financial account associated with the user account; and receive data from a transaction of the user account with a merchant from a user network device. The instructions can be further configured to maintain a database of merchant categories; determine the category of the merchant based on the data associated with the transaction; and extract data to identify the merchant, such as merchant name, address, or telephone number. The instructions can be further configured to determine the geo-location of the user device and determine the merchant identify from the location. The instructions can be further configured to determine a merchant category of the merchant from the merchant identity; select the financial account associated with the merchant category of the merchant; and communicate the financial account selected to conduct the transaction.
- These and other aspects, objects, features and advantages of the exemplary embodiments will become apparent to those having ordinary skill in the art upon consideration of the following detailed description of illustrated exemplary embodiments, which include the best mode of carrying out the invention as presently presented.
-
FIG. 1 is a block diagram depicting a system for a payment system to select a preferred card for a contactless payment transaction based on the merchant category, in accordance with certain exemplary embodiments. -
FIG. 2 is a block flow diagram depicting a method to establish a preferred card rule, in accordance with certain exemplary embodiments. -
FIG. 3 is a block flow diagram depicting a method for selecting a preferred card in a contactless payment transaction based on the merchant category, in accordance with certain exemplary embodiments. -
FIG. 4 is a block flow diagram depicting a method to analyze transaction details and determine a merchant category, in accordance with certain exemplary embodiments. - A payment system and payment application include specified information for multiple financial accounts, including, but not limited to debit cards, credit cards, stored value cards, loyalty/rewards cards, and coupons (including purchased offers and other offers), each accessible by a digital wallet on a user device. The different financial accounts used for payment transactions will be collectively referred to as “cards”. The user sets rules specifying which financial account will be accessed when a contactless transaction is attempted. The user can then add, delete, or change the default payment rules associated with the user. The user can change these default static rules, create new rules, or delete a rule. In an exemplary embodiment, the user can access the payment system account and modify the rules at any time, including a time immediately before a payment transaction is initiated. In an exemplary embodiment, the user can access the payment system account using a mobile device application. The rules can be maintained on the payment application on the user devise or on a server at the payment system.
- The user can access a user interface through the user device or on the payment system to establish rules for the preferred card selection. The user can identify a card and associate a merchant category with the card. A transaction at any merchant who is associated with the merchant category will be conducted with the identified card. A user can associate different merchant categories with different cards.
- Additionally or alternatively, the user can be presented with a list of merchant categories and associate cards with the categories that the user is likely to encounter.
- Merchants can be categorized based on user-configured categories, payment system configured categories, or industry standard categories such as a merchant category code (“MCC”). A database of merchant categories and the assigned merchants can be maintained on the payment system and/or the payment application. The merchants in the database can be identified based on data including products sold, address, name, geo-location, phone number, and any other identifying data.
- If a user has not associated a card and a merchant account, the payment system may recommend an association to the user. The payment system can receive the identities of cards associated with merchant categories from other users of the payment system. The payment system can determine which card of the user is the most often selected for a particular merchant category. The payment system can recommend that the user associate the identified card with that particular merchant category. Additionally or alternatively, the payment system can be configured to use the recommended card as a default option should the user not make a selection for a particular category. Additionally or alternatively, the payment system may be configured to use a recommended card in all transactions. That is, the user may not associate any cards with merchant categories and may use a recommended card for all transactions.
- At the point of sale device of a merchant a user can tap or swipe a mobile device to initiate a payment transaction. The user may initiate the transaction in any other suitable manner, such as pressing a real or virtual button or speaking a voice command. The user device and the point of sale terminal or other terminal reader device can establish a communication.
- The point of sale terminal can transmit details of the merchant and/or the product to be purchased to the user device. The payment application on the user device can receive the details and determine if the merchant is identified in a category. The merchant details can be compared to the details of merchant categories stored in the merchant category database. Merchant details can include any information that may identify the merchant such as address, name, phone number, and any other identifying data.
- The user device can additionally or alternatively determine the geo-location of the merchant based on a location application on the device. For example, the user device can use the global positioning system capabilities of the user device or other location determining hardware or software to determine the geo-location of the merchant. The geo-location can be compared to the geo-location of merchants stored in the database to identify a merchant. Alternatively, any other database, registry, or source may be utilized to determine the identity of a merchant based on the geo-location provided.
- Alternatively, if the identity of the merchant cannot be determined, the payment system can use the purchased products to identify a merchant category. The purchased products can be compared to the products sold by merchants in the category database. If an unidentified merchant sells similar products to other merchants in a category then the unidentified merchant can be placed into that category.
- When the payment system identifies the category of the merchant, the payment system can select the preferred card and transmit the identity of the preferred card to the user device. Additionally or alternatively, the payment system can transmit the category of the merchant to the user device and the payment application can determine the preferred card.
- The payment application can display, via a user interface, the identity of the preferred card to the user. The user can accept the card selected and proceed with the transaction or reject the selected card and select an alternative card. Alternatively, the payment application may proceed with the transaction without the approval of the user.
- After selecting the preferred card, the payment application can transmit the card information to the point of sale terminal and complete the transaction.
- In an alternate embodiment, all of the steps can be performed in an online transaction. The user device may attempt a transaction with an online merchant. The merchant can submit the transaction and the merchant details. The payment system can determine a category of the online merchant. The payment system can select a preferred card for that category and transmit the identification of the preferred card to the merchant to conduct the transaction.
- The functionality of the exemplary embodiments will be explained in more detail in the following description, read in conjunction with the figures illustrating the program flow.
- Turning now to the drawings, in which like numerals represent like (but not necessarily identical) elements throughout the figures, exemplary embodiments of the present invention are described in detail.
-
FIG. 1 is a block diagram depicting a system for selecting a preferred card in a contactless payment transaction with a user network device, in accordance with certain exemplary embodiments. As depicted inFIG. 1 , thesystem 100 includesnetwork devices more networks 105. - Each
network 105 includes a wired or wireless telecommunication means by which network devices (includingdevices network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, a mobile telephone network, or any combination thereof. Throughout the discussion of exemplary embodiments, it should be understood that the terms “data” and “information” are used interchangeably herein to refer to text, images, audio, video, or any other form of information that can exist in a computer-based environment. - Each
network device network 105. For example, eachnetwork device FIG. 1 , thenetwork devices - The
user 101 can use acommunication application 112, such as a web browser application or a stand-alone application, to view, download, upload, or otherwise access documents or web pages via a distributednetwork 105. Thenetwork 105 includes a wired or wireless telecommunication system or device by which network devices (includingdevices network 105 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (SAN), personal area network (PAN), a metropolitan area network (MAN), a wireless local area network (WLAN), a virtual private network (VPN), a cellular or other mobile communication network, Bluetooth, NFC, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages. - The
communication application 112 can interact with web servers or other computing devices connected to thenetwork 105, including the point ofsale terminal 132 of themerchant 130, themerchant server 135 of themerchant 130, the web server 141 of thepayment system 140, and thecard issuer 170. Thecommunication application 112 can further communicate with theterminal reader 132 and/or the point ofsale terminal 132 of themerchant 130 via any contactless communication technology such as NFC,z BLUETOOTH, Wi-Fi, infrared, or other suitable technology. - The user network device 110 may include a
digital wallet application 111. Thedigital wallet 111 may encompass any application, hardware, software, or process the user device 110 may employ to assist theuser 101 in completing a purchase. Thedigital wallet 111 can interact with thecommunication application 112 or can be embodied as a companion application of thecommunication application 112. As a companion application, thedigital wallet 111 executes within thecommunication application 112. That is, thedigital wallet 111 may be an application program embedded in thecommunication application 112. - The user device 110 can include a
payment application 115. Thepayment application 115 can interact with thecommunication application 112 or be embodied as a companion application of thecommunication application 112 and execute within thecommunication application 112. Thepayment application 115 may further be embodied as a companion application of thedigital wallet 111 and execute within thedigital wallet 111. Thepayment application 115 may employ a software interface for configuration that may open in thedigital wallet application 111 or may open in theweb browser application 112. Alternatively, thepayment application 115 may be execute on the user device 110 independent of thedigital wallet 111 and thecommunication application 112. - The
payment application 115 is operable to allow auser 101 to configure payment accounts on the user device 110 and thepayment system 140. Thepayment application 115 can allow theuser 101 to receive transaction details, select preferred cards for a transaction, receive notice of a card selection, provide card information, and provide other suitable services. - The user device 110 also includes a
data storage unit 113 accessible by thedigital wallet 111, thepayment application 115, and thecommunication application 112. The exemplarydata storage unit 113 can include one or more tangible computer-readable storage devices. Thedata storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110. For example, thedata storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory. - The
payment system 140 includes adata storage unit 147 accessible by theweb server 144. The exemplarydata storage unit 147 can include one or more tangible computer-readable storage devices. - Some or all of the functions of the
payment system 140 may be alternatively performed on thepayment application 115 of thedigital wallet 111. Additionally or alternatively, some or all of the functions of thepayment application 115 and thedigital wallet 111 may be performed on thepayment system 140. - The
user 101 can use aweb server 144 on thepayment system 140 to view, register, download, upload, or otherwise access thepayment system 140 via a website (not illustrated) and a communication network 105). Theuser 101 associates one or more registered financial card accounts, including bank account debit cards, credit cards, gift cards, loyalty cards, coupons, offers, prepaid offers, store rewards cards, or other type of financial account that can be used to make a purchase or redeem value-added services with the user account. The registered financial card accounts may havemultiple issuers 170 that maintain each financial account. Thepayment system 140 also may function as the issuer for the associated financial account. The user's 101 registration information is saved in the payment system's 140data storage unit 147 and is accessible the byweb server 144. - The
user 101 also may use theweb server 144 to define contactless payment rules and bidding rules. The creation ofpayment application 115 card selection rules is discussed in more detail hereinafter with reference to the methods described inFIG. 3 . - The
merchant 130 may use aweb server 135 to view, download, upload, create offers, sell products online, or otherwise access thepayment system 140 via a website 134 and acommunication network 105. Theweb server 135 may be part of themerchant 130 and located at themerchant 130 location. Theweb server 135 may alternatively be located at a remote location. Themerchant 130 represents an entity that offers products for theuser 101 to purchase or use. Themerchant 130 includes a point of sale (“POS”)terminal 132. ThePOS terminal 132 may be operated by a salesperson that enters the purchase data into thePOS terminal 132 to complete the purchase transaction. Themerchant 130 may be embodied as a physical merchant at a physical location or an online merchant. Themerchant 130 can employ aterminal reader 131 that can communicate with the user device 110 and receive payment information. Theterminal reader 131 may be a function of thePOS terminal 132 or may be logically coupled to thePOS terminal 132. - The
user 101 may request a purchase from themerchant 130. In an exemplary embodiment, the purchase is initiated by a wireless “tap” of the mobile device 110 with theterminal reader 131. In an alternative exemplary embodiment, the purchase is initiated when theuser 101 enters an account identification number at thePOS terminal 132 or in the mobile device 110. In another alternative exemplary embodiment, the purchase is initiated online with themerchant server 135. The purchase may be initiated via themerchant website 136. In yet another alternative exemplary embodiment, the purchase is initiated by use of a permanent/temporary virtual/physical token, QR code, bar code, or other suitable machine-readable medium captured by theterminal reader 131. The merchant'sPOS terminal 132 interacts with an acquirer (for example Chase PaymentTech, or other third party payment processing companies), a card network (for example VISA, MasterCard, American Express, Discover or other card processing networks), thepayment system 140, and the issuer 170 (for example Citibank, CapitalOne, Bank of America, and other financial institutions to authorize payment). System Process - The components of the
exemplary operating environment 100 are described hereinafter with reference to the exemplary methods illustrated inFIGS. 2 . -
FIG. 2 is a block flow diagram depicting amethod 200 to select a preferred card in a contactless payment transaction with a user network device, in accordance with certain exemplary embodiments. - With reference to
FIGS. 1 and 2 , inblock 205, theuser 101 configures the rules for thepayment application 115. The rules can include instructions for selecting a card to use in a transaction with amerchant 130. The rules include instructions to select a card based on the merchant categories associated with the card. The details of a method to define the preferred card rules are discussed in greater detail in themethod 205 with reference toFIG. 3 . -
FIG. 3 is a block flow diagram depicting amethod 205 for establishing a preferred card rule in apayment application 115, in accordance with certain exemplary embodiments. - In
block 305, auser 101 identifies a card associated with a financial account with acard issuer 170. Thepayment system 140 andpayment application 115 can include specified information for multiple financial accounts, including, but not limited to debit cards, credit cards, stored value cards, loyalty/rewards cards, and coupons (including purchased offers and other offers). Theuser 101 can set rules specifying which financial account will be accessed when a contactless transaction is attempted. Theuser 101 can then add, delete, or change the default payment rules associated with theuser 101. Theuser 101 can change these default static rules, create new rules, or delete a rule. In an exemplary embodiment, theuser 101 can access the payment system account and modify the rules at any time, including a time immediately before a payment transaction is initiated. In an exemplary embodiment, theuser 101 can access the payment system account using apayment application 115 on a user device 110. The rules can be maintained on thepayment application 115 on the user devise 110 or on aserver 144 at thepayment system 140. - In
block 310, theuser 101 can associate one or more merchant categories with the identified card. For example, theuser 101 can configure all transactions with the merchants from a particular category to be conducted with the identified card.Merchants 130 can be categorized based onuser 101 configured categories,payment system 140 configured categories, or industry standard categories such as a merchant category code (“MCC”). A database of merchant categories and the assigned merchants can be maintained on thepayment system 140 and/or thepayment application 115. Theuser 101 may be presented with a list of merchant categories and offered the opportunity to associate one or more of the categories with the identified card. Alternatively, theuser 101 may be presented with the option of entering text descriptions of businesses, names of businesses, or other text input. Thepayment system 140 may receive the user input and determine the corresponding merchant category from a database of merchant categories. - In
block 315, during configuration, if auser 101 has not associated a merchant category with any card of theuser 101, thepayment system 140 can recommend a card. Alternatively, thepayment system 140 can recommend a card at the time of a transaction with amerchant 130 in a category that is not associated with a card. - The
payment system 140 can search the accounts of other users of a card issued by acard network 170 associated with the account of theuser 101. Thepayment system 140 can additionally or alternatively focus the search on other users of a card that has the same conditions, terms, rewards, or any other suitable criteria. Thepayment system 140 can identify frequently associated merchant categories in the accounts of the other users of the card. - In
block 320, if a merchant category is associated in the account of a number of users over a defined threshold or a threshold percentage of users, thepayment system 140 can recommend the identified merchant category to theuser 101. The recommendation can be transmitted to theuser 101 via thepayment application 115, email, text, or other suitable communication technology. - In
block 325, thepayment system 140 may alternatively search the merchant categories for a ranking of the most frequent cards with which the merchant categories are associated. Thepayment system 140 can search the associated cards to determine if theuser 101 has any of the highly ranked cards associated with the user account. - In
block 330, thepayment system 140 can determine which card of theuser 101 is the most highly ranked for a particular merchant category. Thepayment system 140 can recommend theuser 101 associate the most highly ranked card and the particular merchant category. The recommendation may be transmitted to theuser 101 via thepayment application 115, email, text, or other suitable communication technology. - In
block 335, theuser 101 associates the recommended card with the recommended merchant category. The association may be performed by theuser 101 during configuration or at any time after configuration. Additionally or alternatively, the recommendation may be made at the time that a purchase is attempted at amerchant 130 that belongs to a merchant category that has not been associated with a card. - Additionally or alternatively, the user account may be configured to automatically associate a merchant category with a card if the
user 101 has not previously performed the association. The automatic association may occur at any time in the process including, but not limited to, the time of sign up, the time of configuration, or when a purchase is attempted. - The
user 101 may additionally configure a default card to be used for any transaction with amerchant 130 belonging to a merchant category that has not been associated with a card. The default card may additionally or alternatively, be employed in a transaction where the merchant category cannot be established. - From
block 335, themethod 205 returns to block 210 inFIG. 2 . - Returning now to
FIG. 2 , inblock 210, auser 101 visits amerchant 130 and selects a product for purchase. The term “product(s)” should be interpreted to include tangible and intangible products, as well as services. Theuser 101 can approach a point of sale (“POS”)terminal 132 of amerchant 130. To initiate a payment transaction, theuser 101 can “tap” or swipe a user network device 110, such as a near field communication (“NFC”) enabled user device 110, to aterminal reader 131 executing on, or logically coupled to, thePOS device 132. Theuser 101 may initiate the transaction in any other suitable manner, such as pressing a real or virtual button or speaking a voice command. The user device 110 and thePOS terminal 132 or otherterminal reader 131 device can establish a communication. The user device 110 and thePOS terminal 132 can communicate via near field communication (“NFC”), BLUETOOTH, Wi-Fi, infrared, or any other suitable communication technology. - In
block 215, thePOS terminal 132 can transmit a payment processing request to the user device 110. ThePOS terminal 132 can transmit details of the transaction to the user device 110 and request details of the financial account or card that will conduct the transaction. ThePOS terminal 132 can transmit details of themerchant 130. The details about themerchant 130 may include, but not be limited to, the merchant category code (“MCC”), the location, the name, the products sold by themerchant 130, and other suitable details that may assist thepayment system 140 in determining the merchant category. - The user device 110 can additionally or alternatively determine the geo-location of the
merchant 130 based on a location application on the device. For example, the user device 110 can use the global positioning system capabilities of the user device 110 or other location determining application or hardware to determine the geo-location of themerchant 130. The geo-location of the transaction can be compared to the geo-location of merchants stored in a database to identify amerchant 130. - In
block 220, the transaction details and the merchant details can be transmitted to thepayment system 140 by thepayment application 115. The transmission may be conducted via an Internet connection over thenetwork 105, email, text, or any other suitable communication technology. Thepayment system 140 can compare the details of themerchant 130 to determine the category of themerchant 130. - The details of the
block 220 to determine the category of themerchant 130 are further described inmethod 220 inFIG. 4 . - In
block 405 ofFIG. 4 , thepayment system 140 may utilize the categories as defined by the MCC or thepayment system 140 may create and maintain another established category system or develop a new category system. The category system may additionally or alternatively be configured by theuser 101 or other operator. - In an alternate exemplary embodiment, the categorizing of the
merchant 130 may be executed on thepayment application 115. - The category of the
merchant 130 can be determined through an analysis of the details provided with the transaction. For example, the details may specify an MCC of themerchant 130. The payment system can use the MCC to directly establish the category of themerchant 130. The details may additionally or alternatively provide a different type of category designation, such as one developed by thepayment system 140, themerchant 130, theuser 101 or another suitable party. Additionally or alternatively, the details may provide a general description of the category of the merchant. For example, the details may specify that themerchant 130 associated with the transaction is a restaurant, an oil change facility, or a hair salon. Thepayment system 140 can use the specified merchant type to associate the merchant with a category. - If the MCC or other category designation is provided, then
method 220 follows the “YES” branch ofblock 405 to block 225 with respect toFIG. 2 . If the MCC or other category designation is not provided, thenmethod 220 follows the “NO” branch ofblock 405 to block 410. - Following the “NO” branch of to block 410, if no MCC or other category is provided, the
payment system 140 can determine if themerchant 130 name or other identifying detail has previously been recorded in a database. If themerchant 130 has previously conducted a transaction with thepayment system 140, themerchant 130 may already be identified by name in a category. If the details provide the name of themerchant 130, thepayment system 140 can identify the category to which themerchant 130 belongs by searching the category database and determining the category with which themerchant 130 identity has previously been associated. Thepayment system 140 can use other identifying information from the details to find themerchant 130 in the database to determine the category of themerchant 130. Other identifiers that may be in a category database for amerchant 130 may include the address, phone number, or other identifying details of amerchant 130. - If the merchant is identified, then
method 220 follows the “YES” branch ofblock 410 to block 425. If the merchant is not identified, thenmethod 220 follows the “NO” branch ofblock 410 to block 415. - Following the “NO” branch of to block 415, if the identity of the
merchant 130 cannot be determined, thepayment system 140 can identify the geo-location of the user device 110. By determining the location of the user device 110, thepayment system 140 can identify themerchant 130 associated with that location. In an offline transaction, one skilled in the art would understand that if theuser 101 is conducting a transaction utilizing the user device 110, then the user device 110 would be at the same location as themerchant 130 associated with the transaction. The geo-location of the user device 110 can be determined from the global positioning system hardware and software utilized by the user device 110. For example, the user device 110 can transmit the geo-location to thepayment system 140 upon request or with every transaction request. Additionally or alternatively, the user device 110 can determine the geo-location from any other hardware or software technology available to the user device 110, such as a geo-location received from a Wi-Fi system being accessed by the user device 110 or other system. - In
block 420, thepayment system 140 can use the geo-location of the user device 110, and thus the location of themerchant 130, to determine the identity of themerchant 130. The identity may be determined by using a registry of merchant addresses, a mapping application or website, or other database or system to identify amerchant 130 from the geo-location of themerchant 130. - If the merchant is identified from the geo-location, then
method 220 follows the “YES” branch ofblock 420 to block 425. If the merchant is not identified, thenmethod 220 follows the “NO” branch ofblock 420 to block 430. - Following the YES branches of
blocks merchant 130 to identify the category to which themerchant 130 belongs. If themerchant 130 has previously conducted a transaction with thepayment system 140, then thepayment system 140 may have placed themerchant 130 in a category at that time. If thepayment system 140 has previously placed themerchant 130 into a category, then thepayment system 140 can identify the merchant in the database and extract the category in which themerchant 130 is stored. - Alternatively, the
payment system 140 may employ a system for identifyingmerchants 130 and placing themerchants 130 in categories at a time other than at the time of a transaction. That is, thepayment system 140 may continuously or periodically search formerchants 130 that are not categorized and attempt to place themerchants 130 in categories in the database. Thepayment system 140 may additionally or alternatively, subscribe to a system or service that updates the category codes, such as an MCC, and supplies the categories ofmerchants 130 to thepayment system 140. Thepayment system 140 may utilize any other system or process to update themerchants 130 located in the category database. - If the
merchant 130 is identified in a category, thepayment system 140 can determine that themerchant 130 associated with the current transaction is thesame merchant 130 located in the database. Thepayment system 140 can thus determine the category of themerchant 130. - If the merchant category is determined from the
merchant 130 identity, thenmethod 220 follows the “YES” branch ofblock 425 to block 225 with respect toFIG. 2 . If the merchant category is not determined from themerchant 130 identity, thenmethod 220 follows the “NO” branch ofblock 425 to block 430. - Following the NO branch of
block 425, inblock 430, thepayment system 140 can use the products associated with the transaction to identify a merchant category. The products associated with the transaction can be identified from the description of the products, a model number associated with the products, a stock-keeping unit (“SKU”) or other identifying code, or other identifier from the transaction. - In
block 435, the products can be compared to the products sold by other merchants in the category database. If themerchant 130 sells similar products to other merchants in a category then themerchant 130 can be placed into that category. Thepayment system 140 may employ a scoring system to determine the category. For example, themerchant 130 may receive points for every product in common with the merchants in a product category. A threshold of points may be required to place themerchant 130 in the category. Any scoring system or other system for determining if the products of themerchant 130 match the products of the merchants in a category may be utilized. - In
block 440, thepayment system 140 associates themerchant 130 with the category of the merchants with which themerchant 130 sells similar products. Thepayment system 140 may associate themerchant 130 with the category for only the pending transaction or thepayment system 140 may associate themerchant 130 with the selected category for future transactions. The association may be permanent or may be associated until such time as a more accurate category is assigned. - From
block 440, themethod 220 returns to block 225 inFIG. 2 . - Returning to
FIG. 2 , inblock 225, when thepayment system 140 identifies the category of themerchant 130, thepayment system 140 can select the preferred card and transmit the identity of the preferred card to the user device 110. In an alternative exemplary embodiment, thepayment system 140 can transmit the category of themerchant 130 to the user device and thepayment application 115 can determine the preferred card for the merchant category. - In
block 230, thepayment application 115 can display, via a user interface, the identity of the preferred card to theuser 101. Theuser 101 can accept the card selected and proceed with the transaction or reject the selected card and select an alternative card. Alternatively, thepayment application 115 may proceed with the transaction without the approval of theuser 101. - In
block 235, after selecting the preferred card, thepayment application 115 can transmit the card information to thePOS terminal 132 and complete the transaction. - In
block 240, themerchant 130 can receive the card information and conduct the transaction with theissuer 170 of the selected card. - Some or all of the functions of the
payment system 140 may be alternatively performed on thepayment application 115 of thedigital wallet 111. Additionally or alternatively, some or all of the functions of thepayment application 115 and thedigital wallet 111 may be performed on thepayment system 140. - In an alternate embodiment, all of the steps can be performed in an online transaction. The user device 110 can attempt a transaction with an
online merchant 130. Themerchant 130 can submit the transaction and the merchant details. Thepayment system 140 or apayment application 115 can determine a category of theonline merchant 130 via the process as described above. Thepayment system 140 or apayment application 115 can select a preferred card for that category and transmit the identification of the preferred card to themerchant 130 to conduct the transaction. - From
block 240, themethod 200 ends. - Users may be allowed to limit or otherwise affect the operation of the features disclosed herein. For example, users may be given opportunities to opt-in or opt-out of the collection or use of certain data or the activation of certain features. In addition, users may be given the opportunity to change the manner in which the features are employed. Instructions also may be provided to users to notify them regarding policies about the use of information, including personally identifiable information, and manners in which each user may affect such use of information. Thus, information can be used to benefit a user, if desired, through receipt of relevant advertisements, offers, or other information, without risking disclosure of personal information or the user's identity.
- One or more aspects of the invention may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions. However, it should be apparent that there could be many different ways of implementing the invention in computer programming, and the invention should not be construed as limited to any one set of computer program instructions. Further, a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed invention based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the invention. Further, those skilled in the art will appreciate that one or more aspects of the invention described herein may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems. Moreover, any reference to an act being performed by a computer should not be construed as being performed by a single computer as more than one computer may perform the act.
- The exemplary embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously. The systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry. The software can be stored on computer-readable media. For example, computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc. Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
- The exemplary systems, methods, and acts described in the embodiments presented previously are illustrative, and, in alternative embodiments, certain acts can be performed in a different order, in parallel with one another, omitted entirely, and/or combined between different exemplary embodiments, and/or certain additional acts can be performed, without departing from the scope and spirit of the invention. Accordingly, such alternative embodiments are included in the inventions described herein.
- Although specific embodiments have been described above in detail, the description is merely for purposes of illustration. It should be appreciated, therefore, that many aspects described above are not intended as required or essential elements unless explicitly stated otherwise. Modifications of, and equivalent components or acts corresponding to, the disclosed aspects of the exemplary embodiments, in addition to those described above, can be made by a person of ordinary skill in the art, having the benefit of the present disclosure, without departing from the spirit and scope of the invention defined in the following claims, the scope of which is to be accorded the broadest interpretation so as to encompass such modifications and equivalent structures.
Claims (18)
1. A computer-implemented method to select a payment instrument for a purchase based on a merchant category, comprising:
associating, by a computer, a plurality of financial accounts with a user account of a user, the user account being maintained by the computer;
for one or more of the financial accounts associated with the user account, associating, by the computer, one of a plurality of merchant categories with the respective financial account in a category database;
receiving, by the computer from a user network device, data from a transaction of the user account with a merchant;
determining, by the computer, a merchant category of the merchant by extracting an identification of the merchant from the data from the transaction, locating the identified merchant in the category database, and determining the category associated with the merchant in the database;
selecting, by the computer, one of the financial accounts associated with the merchant category of the merchant; and
communicating, by the computer, the selected financial account to the user network device to conduct the transaction.
2. The computer-implemented method of claim 1 , wherein extracting the identification of the merchant from the data comprises identifying, by the computer, one of more of the following features of the merchant from the data:
a merchant name;
a merchant address;
a merchant telephone number; and
a merchant store number.
3. The computer-implemented method of claim 1 , wherein the transaction data comprises location data identifying a location of the user network device, and wherein extracting the identification of the merchant from the transaction data comprises:
extracting, by the computer, the location data identifying the location of the user network device; and
determining, by the computer, the identity of the merchant associated with the location of the user network device.
4. The computer-implemented method of claim 1 , wherein determining the merchant category of the merchant comprises:
identifying, by the computer, one of more products associated with the transaction;
comparing, by the computer, the associated products with a list of products associated with other merchants in the category database; and
determining, by the computer, that the merchant is associated with a category of merchants based on a similarity of the products associated with the merchant and the products associated with the merchants associated with the category.
5. The computer-implemented method of claim 1 , further comprising:
receiving, by the computer, data from a plurality of accounts of other users;
determining, by the computer, financial accounts of the accounts of other users that are in common with the user account;
determining, by the computer, merchant categories associated with the common financial accounts of the user account and the other user accounts; and
recommending, by the computer, the merchant categories that are most frequently associated with the financial accounts of the accounts of other users that are in common with the user account.
6. The computer-implemented method of claim 1 , wherein the category database comprises merchant names, merchant addresses, merchant phone numbers, merchant product offerings, merchant category codes, and merchant geo-locations.
7. A computer program product, comprising:
a non-transitory computer-readable storage device having computer-executable program instructions embodied thereon that when executed by a computer select a payment instrument for a purchase based on a merchant category, the computer-executable program instructions comprising:
computer-executable program instructions to associate a plurality of financial accounts with a user account of a user, the user account being maintained by the computer;
computer-executable program instructions to associate, for one or more of the financial accounts associated with the user account, one of a plurality of merchant categories with the respective financial account in a category database;
computer-executable program instructions to receive, from a user network device, data from a transaction of the user account with a merchant;
computer-executable program instructions to determine a merchant category of the merchant by
extracting, from the transaction data, a location identifying the location of the user network device,
determining the identity of the merchant associated with the location of the user network device,
locating the identified merchant in the category database, and
determining the category associated with the merchant in the database;
computer-executable program instructions to select one of the financial accounts associated with the merchant category of the merchant; and
computer-executable program instructions to communicate the selected financial account to the user network device to conduct the transaction.
8. The computer program product of claim 7 , wherein extracting the identification of the merchant from the data comprises identifying, by the computer, one of more of the following features of the merchant from the data:
a merchant name;
a merchant address;
a merchant telephone number; and
a merchant store number.
9. The computer program product of claim 7 , wherein the transaction data comprises identification data identifying a merchant, and wherein determining the category of the merchant from the transaction data comprises:
extracting an identification of the merchant from the data from the transaction;
locating the identified merchant in the category database; and
determining the category associated with the merchant in the database.
10. The computer program product of claim 7 , wherein determining the merchant category of the merchant comprises:
identifying one of more products associated with the transaction;
comparing the associated products with a list of products associated with other merchants in the category database; and
determining that the merchant is associated with a category of merchants based on a similarity of the products associated with the merchant and the products associated with the merchants associated with the category.
11. The computer program product of claim 7 , further comprising:
computer-executable program instructions to receive data from a plurality of accounts of other users;
computer-executable program instructions to determine financial accounts of the accounts of other users that are in common with the user account;
computer-executable program instructions to determine merchant categories associated with the common financial accounts of the user account and the other user accounts; and
computer-executable program instructions to recommend the merchant categories that are most frequently associated with the financial accounts of the accounts of other users that are in common with the user account.
12. The computer program product of claim 7 , wherein the category database comprises merchant names, merchant addresses, merchant phone numbers, merchant product offerings, merchant category codes, and merchant geo-locations.
13. A system to select a payment instrument for a purchase based on a merchant category, the system comprising:
a storage resource;
a network module; and
a processor communicatively coupled to the storage resource and the network module, wherein the processor executes application code instructions that are stored in the storage resource and that cause the system to:
associate a plurality of financial accounts with a user account of a user, the user account being maintained by the computer;
associate, for one or more of the financial accounts associated with the user account, one of a plurality of merchant categories with the respective financial account in a category database;
receive, from a user network device, data from a transaction of the user account with a merchant;
determine a merchant category of the merchant by
identifying one of more products associated with the transaction,
comparing the associated products with a list of products associated with other merchants in the category database,
determining that the merchant is associated with a category of merchants based on a similarity of the products associated with the merchant and the products associated with the merchants associated with the category;
select one of the financial accounts associated with the merchant category of the merchant; and
communicate the selected financial account to the user network device to conduct the transaction.
14. The system of claim 13 , wherein extracting the identification of the merchant from the data comprises identifying, by the computer, one of more of the following features of the merchant from the data:
a merchant name;
a merchant address;
a merchant telephone number; and
a merchant store number.
15. The system of claim 13 , wherein the transaction data comprises location data identifying a location of the user network device, and wherein determining the category of the merchant from the transaction data comprises instructions further causing the system to:
extract the location data identifying the location of the user network device; and
determine the identity of the merchant associated with the location of the user network device;
locate the identified merchant in the category database; and
determine the category associated with the merchant in the database.
16. The system of claim 13 , wherein the transaction data comprises identification data identifying a merchant, and wherein determining the category of the merchant from the transaction data comprises:
extracting an identification of the merchant from the data from the transaction;
locating the identified merchant in the category database; and
determining the category associated with the merchant in the database.
17. The system of claim 13 , the instructions further causing the system to:
receive data from a plurality of accounts of other users;
determine financial accounts of the accounts of other users that are in common with the user account;
determine merchant categories associated with the common financial accounts of the user account and the other user accounts; and
recommend the merchant categories that are most frequently associated with the financial accounts of the accounts of other users that are in common with the user account.
18. The system of claim 13 , wherein the category database comprises merchant names, merchant addresses, merchant phone numbers, merchant product offerings, merchant category codes, and merchant geo-locations.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/542,303 US20140012704A1 (en) | 2012-07-05 | 2012-07-05 | Selecting a preferred payment instrument based on a merchant category |
PCT/US2013/049446 WO2014008471A1 (en) | 2012-07-05 | 2013-07-05 | Selecting a preferred payment instrument based on a merchant category |
AU2013207643A AU2013207643B2 (en) | 2012-07-05 | 2013-07-05 | Selecting a preferred payment instrument based on a merchant category |
US15/072,191 US10185954B2 (en) | 2012-07-05 | 2016-03-16 | Selecting a preferred payment instrument based on a merchant category |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/542,303 US20140012704A1 (en) | 2012-07-05 | 2012-07-05 | Selecting a preferred payment instrument based on a merchant category |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/072,191 Continuation US10185954B2 (en) | 2012-07-05 | 2016-03-16 | Selecting a preferred payment instrument based on a merchant category |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140012704A1 true US20140012704A1 (en) | 2014-01-09 |
Family
ID=49879250
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/542,303 Abandoned US20140012704A1 (en) | 2012-07-05 | 2012-07-05 | Selecting a preferred payment instrument based on a merchant category |
US15/072,191 Active 2033-06-08 US10185954B2 (en) | 2012-07-05 | 2016-03-16 | Selecting a preferred payment instrument based on a merchant category |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/072,191 Active 2033-06-08 US10185954B2 (en) | 2012-07-05 | 2016-03-16 | Selecting a preferred payment instrument based on a merchant category |
Country Status (3)
Country | Link |
---|---|
US (2) | US20140012704A1 (en) |
AU (1) | AU2013207643B2 (en) |
WO (1) | WO2014008471A1 (en) |
Cited By (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140114777A1 (en) * | 2012-10-22 | 2014-04-24 | Remi Guyot | Tailored Display of Payment Options |
US20150058146A1 (en) * | 2013-08-23 | 2015-02-26 | Ajit Gaddam | Dynamic Account Selection |
US20150120428A1 (en) * | 2013-10-28 | 2015-04-30 | U.S. Bank, National Association | Mobile-enabled commerce service aggregation |
CN105279646A (en) * | 2015-09-25 | 2016-01-27 | 宇龙计算机通信科技(深圳)有限公司 | Payment application selection method and mobile terminal |
WO2016048863A1 (en) * | 2014-09-22 | 2016-03-31 | Mastercard International Incorporated | Payment systems and methods for managing payment card use |
WO2016054226A1 (en) * | 2014-10-01 | 2016-04-07 | Google Inc. | Annotating a transaction history record with merchant information identified from a merchant identifier and user computing device location data |
US20160140535A1 (en) * | 2014-09-22 | 2016-05-19 | Mastercard International Incorporated | Payment systems and methods for managing payment card use |
US20160140541A1 (en) * | 2014-11-18 | 2016-05-19 | Google Inc. | Automatically communicating user device data to a transaction computing system |
WO2016098774A1 (en) * | 2014-12-16 | 2016-06-23 | 大日本印刷株式会社 | Store terminal device, membership management server, proxy settlement server, and settlement method |
US20160335702A1 (en) * | 2015-05-13 | 2016-11-17 | Sony Corporation | Method and system for providing recommendation for selection of a merchant store |
WO2017015138A1 (en) * | 2015-07-17 | 2017-01-26 | Google Inc. | Merchant-specific functionality services |
US20170046686A1 (en) * | 2015-08-13 | 2017-02-16 | Lg Electronics Inc. | Mobile Terminal |
US9679284B2 (en) | 2013-03-04 | 2017-06-13 | Google Inc. | Selecting a preferred payment instrument |
WO2017116645A1 (en) * | 2015-12-31 | 2017-07-06 | Mastercard International Incorporated | Method and system for secure consumer identification |
US9916575B2 (en) | 2014-11-19 | 2018-03-13 | Qualcomm Incorporated | Systems and methods for adaptive routing for multiple secure elements |
US9934494B1 (en) * | 2013-10-24 | 2018-04-03 | United Services Automobile Association (Usaa) | Methods and systems for systematic recognition of recurring payees and payments |
EP3333790A1 (en) * | 2016-12-07 | 2018-06-13 | Mastercard International Incorporated | Automatic context-based selection from a digital wallet |
US20180288562A1 (en) * | 2017-04-03 | 2018-10-04 | Bank Of America Corporation | Data Transfer Between Computing Device and User Device Over Session or Connection in Response to Wireless Sensing Device Detecting User Device at a Location |
US10185954B2 (en) | 2012-07-05 | 2019-01-22 | Google Llc | Selecting a preferred payment instrument based on a merchant category |
WO2019040150A1 (en) * | 2017-08-25 | 2019-02-28 | Google Llc | Conducting transactions with multiple payment service providers |
US10223754B1 (en) | 2014-08-12 | 2019-03-05 | Wells Fargo Bank, N.A. | Personal financial planning and engagement with peer-based comparison |
EP3474210A1 (en) * | 2017-10-19 | 2019-04-24 | Capital One Services, LLC | User account controls for online transactions |
US10402829B1 (en) * | 2016-09-09 | 2019-09-03 | Worldpay, Llc | Systems and methods for using shared databases for managing supplemental payment sources |
US10402896B1 (en) | 2014-07-03 | 2019-09-03 | Wells Fargo Bank, N.A. | Systems and methods for interactive financial categorization and budgeting |
US10423947B1 (en) * | 2016-09-09 | 2019-09-24 | Worldpay, Llc | User interfaces for using shared databases for managing supplemental payment sources |
US10558975B2 (en) | 2016-08-17 | 2020-02-11 | Mastercard International Incorporated | Systems and methods for use in facilitating transactions |
US10601934B2 (en) | 2017-04-03 | 2020-03-24 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and one or more servers for transmitting data to a third party computing device |
US10601718B2 (en) | 2017-04-03 | 2020-03-24 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and server associated with a routing network for modifying one or more parameters of the routing network |
US10608918B2 (en) | 2017-04-03 | 2020-03-31 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and one or more servers to determine likelihood of user device using a routing network |
US10609156B2 (en) | 2017-04-03 | 2020-03-31 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and server associated with one or more routing networks in response to detecting activity |
EP3648036A1 (en) * | 2018-10-29 | 2020-05-06 | Mastercard International Incorporated | Non-default application selection during a transaction |
WO2020121063A1 (en) * | 2018-12-11 | 2020-06-18 | Orange | Method for operating a device for selecting a virtual card in a digital wallet |
US10699289B1 (en) | 2015-06-05 | 2020-06-30 | Wells Fargo Bank, N.A. | Systems and methods for providing real-time payment recommendations and offers |
US10716060B2 (en) | 2017-04-03 | 2020-07-14 | Bank Of America Corporation | Data transfer between computing device and user device at different locations and over session or connection to display one or more routing networks to use |
US10740852B1 (en) * | 2015-06-23 | 2020-08-11 | Square, Inc. | Classifying merchants |
US10878394B1 (en) | 2018-11-29 | 2020-12-29 | Square, Inc. | Intelligent inventory recommendations |
US10909486B1 (en) | 2015-07-15 | 2021-02-02 | Square, Inc. | Inventory processing using merchant-based distributed warehousing |
US10949796B1 (en) | 2015-07-15 | 2021-03-16 | Square, Inc. | Coordination of inventory ordering across merchants |
US10949825B1 (en) | 2017-06-30 | 2021-03-16 | Square, Inc. | Adaptive merchant classification |
US11017369B1 (en) | 2015-04-29 | 2021-05-25 | Square, Inc. | Cloud-based inventory and discount pricing management system |
US11030603B1 (en) * | 2017-06-26 | 2021-06-08 | Wells Fargo Bank, N.A. | Systems and methods for distinguishing between profiles in a passive authentication scheme |
US20210217014A1 (en) * | 2020-01-09 | 2021-07-15 | Visa International Service Association | Method, System, and Computer Program Product for Co-Located Merchant Anomaly Detection |
US20210248668A1 (en) * | 2018-09-11 | 2021-08-12 | Nippon Food Manufacturer Co. | Virtual store provision system |
CN113837755A (en) * | 2018-07-05 | 2021-12-24 | 创新先进技术有限公司 | Offline transaction distinguishing method and device and computer equipment |
US11210725B2 (en) | 2014-03-24 | 2021-12-28 | Square, Inc. | Determining pricing information from merchant data |
US11348119B1 (en) | 2017-10-18 | 2022-05-31 | Block, Inc. | Intelligent merchant onboarding |
US11861579B1 (en) | 2018-07-31 | 2024-01-02 | Block, Inc. | Intelligent inventory system |
EP4300397A1 (en) * | 2022-06-28 | 2024-01-03 | Thales Dis France Sas | Method for managing a card |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10621658B1 (en) | 2015-01-15 | 2020-04-14 | Wells Fargo Bank, N.A. | Identity verification services with identity score through external entities via application programming interface |
US10997654B1 (en) | 2015-01-15 | 2021-05-04 | Wells Fargo Bank, N.A. | Identity verification services through external entities via application programming interface |
US10990974B1 (en) | 2015-01-15 | 2021-04-27 | Wells Fargo Bank, N.A. | Identity verification services and user information provision via application programming interface |
US10937025B1 (en) | 2015-01-15 | 2021-03-02 | Wells Fargo Bank, N.A. | Payment services via application programming interface |
CN107292598A (en) * | 2017-05-31 | 2017-10-24 | 杭州大搜车汽车服务有限公司 | One kind pays method for routing and pays route middleware |
US11995619B1 (en) | 2017-12-28 | 2024-05-28 | Wells Fargo Bank, N.A. | Account open interfaces |
US11106515B1 (en) | 2017-12-28 | 2021-08-31 | Wells Fargo Bank, N.A. | Systems and methods for multi-platform product integration |
US11676126B1 (en) | 2017-12-28 | 2023-06-13 | Wells Fargo Bank, N.A. | Account open interfaces |
US11379850B1 (en) | 2018-12-10 | 2022-07-05 | Wells Fargo Bank, N.A. | Third-party payment interfaces |
EP3719727A1 (en) * | 2019-04-04 | 2020-10-07 | Mastercard International Incorporated | Transaction selection mechanism |
US11044246B1 (en) | 2019-06-21 | 2021-06-22 | Wells Fargo Bank, N.A. | Secure communications via third-party systems through frames |
US11521248B2 (en) * | 2019-12-13 | 2022-12-06 | AiFi Inc. | Method and system for tracking objects in an automated-checkout store based on distributed computing |
US11687519B2 (en) | 2021-08-11 | 2023-06-27 | T-Mobile Usa, Inc. | Ensuring availability and integrity of a database across geographical regions |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060151598A1 (en) * | 2005-01-13 | 2006-07-13 | Yen-Fu Chen | Categorization based spending control |
US20100017325A1 (en) * | 2008-07-17 | 2010-01-21 | International Business Machines Corporation | Multiple financial account transaction processing |
US20100082445A1 (en) * | 2008-09-30 | 2010-04-01 | Apple Inc. | Smart menu options |
US20120078786A1 (en) * | 2010-09-24 | 2012-03-29 | Bank Of America Corporation | Deposit transaction-level information |
US20130110658A1 (en) * | 2011-05-05 | 2013-05-02 | Transaction Network Services, Inc. | Systems and methods for enabling mobile payments |
US20130275303A1 (en) * | 2012-04-11 | 2013-10-17 | Mastercard International Incorporated | Method and system for two stage authentication with geolocation |
US20140006198A1 (en) * | 2012-06-30 | 2014-01-02 | At&T Mobility Ii Llc | Generating and Categorizing Transaction Records |
Family Cites Families (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5221838A (en) | 1990-12-24 | 1993-06-22 | Motorola, Inc. | Electronic wallet |
US5590038A (en) | 1994-06-20 | 1996-12-31 | Pitroda; Satyan G. | Universal electronic transaction card including receipt storage and system and methods of conducting electronic transactions |
US5881287A (en) | 1994-08-12 | 1999-03-09 | Mast; Michael B. | Method and apparatus for copy protection of images in a computer system |
US5619219A (en) | 1994-11-21 | 1997-04-08 | International Business Machines Corporation | Secure viewing of display units using a wavelength filter |
US5537476A (en) | 1994-11-21 | 1996-07-16 | International Business Machines Corporation | Secure viewing of display units by image superposition and wavelength separation |
US5614920A (en) | 1994-11-21 | 1997-03-25 | International Business Machines Corporation | Secure viewing of display units using an electronic shutter |
US6535929B1 (en) | 1996-07-02 | 2003-03-18 | Sun Microsystems, Inc. | Universal communication mechanism for applications running in a multitasking environment |
US5883810A (en) | 1997-09-24 | 1999-03-16 | Microsoft Corporation | Electronic online commerce card with transactionproxy number for online transactions |
US6000832A (en) | 1997-09-24 | 1999-12-14 | Microsoft Corporation | Electronic online commerce card with customer generated transaction proxy number for online transactions |
US6266647B1 (en) | 1997-11-03 | 2001-07-24 | Xtec, Incorporated | Methods and apparatus for electronically storing and retrieving value information on a portable card |
US6636833B1 (en) | 1998-03-25 | 2003-10-21 | Obis Patents Ltd. | Credit card system and method |
US6450407B1 (en) | 1998-04-17 | 2002-09-17 | Viztec, Inc. | Chip card rebate system |
US20040049452A1 (en) | 2002-09-09 | 2004-03-11 | First Data Corporation | Multiple credit line presentation instrument |
US6298446B1 (en) | 1998-06-14 | 2001-10-02 | Alchemedia Ltd. | Method and system for copyright protection of digital images transmitted over networks |
EP1153375B1 (en) | 1999-02-18 | 2003-01-15 | Orbis Patents Limited | Credit card system and method |
US6317650B1 (en) | 1999-04-29 | 2001-11-13 | Softcard Systems, Inc. | System and method employing portable cards to monitor a commercial system |
US20090094164A1 (en) | 1999-07-09 | 2009-04-09 | Bally Gaming, Inc. | Remote access verification environment system and method |
WO2001045052A2 (en) | 1999-10-18 | 2001-06-21 | Sutton David B | Auction system requiring advance credit information from both buyer and seller |
US6879959B1 (en) | 2000-01-21 | 2005-04-12 | Quality Care Solutions, Inc. | Method of adjudicating medical claims based on scores that determine medical procedure monetary values |
US6742704B2 (en) | 2000-01-21 | 2004-06-01 | American Express Travel Related Services Company, Inc. | Multiple-service card system |
US7283977B1 (en) | 2000-02-25 | 2007-10-16 | Kathleen Tyson-Quah | System for reducing risk payment-based transactions wherein a risk filter routine returns instructions authorizing payment to a payment queue for later re-evaluation |
US7865414B2 (en) | 2000-03-01 | 2011-01-04 | Passgate Corporation | Method, system and computer readable medium for web site account and e-commerce management from a central location |
TW550477B (en) | 2000-03-01 | 2003-09-01 | Passgate Corp | Method, system and computer readable medium for Web site account and e-commerce management from a central location |
WO2001082243A2 (en) | 2000-04-20 | 2001-11-01 | Innovative Payment Systems, Llc | Method and system for ubiquitous enablement of electronic currency |
WO2002011019A1 (en) | 2000-08-01 | 2002-02-07 | First Usa Bank, N.A. | System and method for transponder-enabled account transactions |
US6601759B2 (en) | 2000-10-04 | 2003-08-05 | American Express Travel Related Services | System and method for providing feedback in an interactive payment system |
WO2002037386A1 (en) | 2000-11-06 | 2002-05-10 | First Usa Bank, N.A. | System and method for selectable funding of electronic transactions |
US7996288B1 (en) | 2000-11-15 | 2011-08-09 | Iprivacy, Llc | Method and system for processing recurrent consumer transactions |
US6961941B1 (en) | 2001-06-08 | 2005-11-01 | Vmware, Inc. | Computer configuration for resource management in systems including a virtual machine |
US7073070B2 (en) | 2001-06-29 | 2006-07-04 | Intel Corporation | Method and apparatus to improve the protection of information presented by a computer |
US7996324B2 (en) | 2001-07-10 | 2011-08-09 | American Express Travel Related Services Company, Inc. | Systems and methods for managing multiple accounts on a RF transaction device using secondary identification indicia |
US7225156B2 (en) | 2001-07-11 | 2007-05-29 | Fisher Douglas C | Persistent dynamic payment service |
AU2002327322A1 (en) | 2001-07-24 | 2003-02-17 | First Usa Bank, N.A. | Multiple account card and transaction routing |
US7203310B2 (en) | 2001-12-04 | 2007-04-10 | Microsoft Corporation | Methods and systems for cryptographically protecting secure content |
US7380130B2 (en) | 2001-12-04 | 2008-05-27 | Microsoft Corporation | Methods and systems for authentication of components in a graphics system |
US7631184B2 (en) | 2002-05-14 | 2009-12-08 | Nicholas Ryan | System and method for imposing security on copies of secured items |
US7768522B2 (en) | 2002-01-08 | 2010-08-03 | Apple Inc. | Virtualization of graphics resources and thread blocking |
US7065651B2 (en) | 2002-01-16 | 2006-06-20 | Microsoft Corporation | Secure video card methods and systems |
US20030191661A1 (en) | 2002-04-09 | 2003-10-09 | Doyle Robert E. | Method for the standardization and syndication of business transactions |
US7206940B2 (en) | 2002-06-24 | 2007-04-17 | Microsoft Corporation | Methods and systems providing per pixel security and functionality |
US8930270B2 (en) | 2002-07-30 | 2015-01-06 | Aol Inc. | Smart payment instrument selection |
US6786400B1 (en) | 2002-09-06 | 2004-09-07 | Capital One Financial Corporation | Multiple account banking system and method |
US7181744B2 (en) | 2002-10-24 | 2007-02-20 | International Business Machines Corporation | System and method for transferring data between virtual machines or other computer entities |
EP1579356A4 (en) | 2002-11-07 | 2005-12-28 | Planet Group Inc | Time-of-transaction foreign currency conversion |
US6920611B1 (en) | 2002-11-25 | 2005-07-19 | Visa U.S.A., Inc. | Method and system for implementing a loyalty merchant component |
US7293178B2 (en) | 2002-12-09 | 2007-11-06 | Microsoft Corporation | Methods and systems for maintaining an encrypted video memory subsystem |
US8695019B2 (en) | 2003-02-14 | 2014-04-08 | Actividentity (Australia) Pty Ltd | System and method for delivering external data to a process running on a virtual machine |
US20040225509A1 (en) * | 2003-05-07 | 2004-11-11 | Olivier Andre | Use of financial transaction network(s) information to generate personalized recommendations |
US7689483B2 (en) | 2003-05-20 | 2010-03-30 | Amegy Bank of Texas | System to facilitate payments for a customer through a foreign bank, software, business methods, and other related methods |
US20060259390A1 (en) | 2003-06-19 | 2006-11-16 | Rosenberger Ronald J | Multiple account preset parameter method, apparatus and systems for financial transactions and accounts |
US9020801B2 (en) | 2003-08-11 | 2015-04-28 | Scalemp Inc. | Cluster-based operating system-agnostic virtual computing system |
US7784060B2 (en) | 2003-11-06 | 2010-08-24 | Intel Corporation | Efficient virtual machine communication via virtual machine queues |
US7922083B2 (en) | 2003-11-19 | 2011-04-12 | Harrison Sarah E | Payment programs for healthcare plans |
US7310534B2 (en) | 2003-12-16 | 2007-12-18 | Sony Ericsson Mobile Communications Ab | Location status indicator for mobile phones |
US20050160424A1 (en) | 2004-01-21 | 2005-07-21 | International Business Machines Corporation | Method and system for grid-enabled virtual machines with distributed management of applications |
US7708190B2 (en) | 2004-03-10 | 2010-05-04 | At&T Intellectual Property I, L.P. | Multiple options to decline authorization of payment card charges |
US7552419B2 (en) | 2004-03-18 | 2009-06-23 | Intel Corporation | Sharing trusted hardware across multiple operational environments |
US20050216424A1 (en) * | 2004-03-23 | 2005-09-29 | Star Systems, Inc. | Transaction system with special handling of micropayment transaction requests |
WO2005098702A2 (en) | 2004-03-26 | 2005-10-20 | Citicorp Credit Services, Inc. | Methods and systems for integration of multiple rewards programs |
EP1870814B1 (en) | 2006-06-19 | 2014-08-13 | Texas Instruments France | Method and apparatus for secure demand paging for processor devices |
US7421533B2 (en) | 2004-04-19 | 2008-09-02 | Intel Corporation | Method to manage memory in a platform with virtual machines |
US7257811B2 (en) | 2004-05-11 | 2007-08-14 | International Business Machines Corporation | System, method and program to migrate a virtual machine |
US8885894B2 (en) | 2004-06-14 | 2014-11-11 | Michael John Rowen | Reduction of transaction fraud through the use of automatic centralized signature/sign verification combined with credit and fraud scoring during real-time payment card authorization processes |
US7788713B2 (en) | 2004-06-23 | 2010-08-31 | Intel Corporation | Method, apparatus and system for virtualized peer-to-peer proxy services |
US7577959B2 (en) | 2004-06-24 | 2009-08-18 | International Business Machines Corporation | Providing on-demand capabilities using virtual machines and clustering processes |
US20060069828A1 (en) | 2004-06-30 | 2006-03-30 | Goldsmith Michael A | Sharing a physical device among multiple clients |
US20060050929A1 (en) | 2004-09-09 | 2006-03-09 | Rast Rodger H | Visual vector display generation of very fast moving elements |
US7620984B2 (en) | 2004-10-06 | 2009-11-17 | Hewlett-Packard Development Company, L.P. | Method of managing computer system |
US7600267B2 (en) | 2004-10-21 | 2009-10-06 | International Business Machines Corporation | Preventing a copy of a protected window |
US9606821B2 (en) | 2004-12-17 | 2017-03-28 | Intel Corporation | Virtual environment manager for creating and managing virtual machine environments |
US7792697B2 (en) * | 2004-12-28 | 2010-09-07 | American Express Travel Related Services Company, Inc. | System and method for predicting card member spending using collaborative filtering |
US9875491B2 (en) | 2004-12-30 | 2018-01-23 | Paypal, Inc. | Systems and methods for facilitating lending between two or more parties |
US20060155862A1 (en) | 2005-01-06 | 2006-07-13 | Hari Kathi | Data traffic load balancing based on application layer messages |
US7634664B2 (en) | 2005-02-15 | 2009-12-15 | Hewlett-Packard Development Company, L.P. | Devices, systems, and methods for secure download of data |
US20060271497A1 (en) | 2005-05-24 | 2006-11-30 | Cullen Andrew J | Payment authorisation process |
US20060271542A1 (en) | 2005-05-25 | 2006-11-30 | Harris Steven T | Clustered object state using logical actions |
US7401731B1 (en) * | 2005-05-27 | 2008-07-22 | Jpmorgan Chase Bank, Na | Method and system for implementing a card product with multiple customized relationships |
US7802000B1 (en) | 2005-08-01 | 2010-09-21 | Vmware | Virtual network in server farm |
US7752436B2 (en) | 2005-08-09 | 2010-07-06 | Intel Corporation | Exclusive access for secure audio program |
US20070079307A1 (en) | 2005-09-30 | 2007-04-05 | Puneet Dhawan | Virtual machine based network carriers |
US20070170247A1 (en) | 2006-01-20 | 2007-07-26 | Maury Samuel Friedman | Payment card authentication system and method |
US20070174429A1 (en) | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment |
US7689926B2 (en) | 2006-03-31 | 2010-03-30 | Microsoft Corporation | Selective window exclusion for captured content |
US7619622B2 (en) | 2006-03-31 | 2009-11-17 | Microsoft Corporation | Selective rendering for driver classes |
US7702559B2 (en) | 2006-05-12 | 2010-04-20 | Ebay Inc. | Methods and apparatus for funding transactions |
US20080015988A1 (en) | 2006-06-28 | 2008-01-17 | Gary Brown | Proxy card authorization system |
TW200820109A (en) | 2006-07-26 | 2008-05-01 | Joseph Sally | Method for managing multiple credit accounts |
US8464938B2 (en) | 2007-06-22 | 2013-06-18 | Intelispend Prepaid Solutions, Llc | Client customized virtual or physical card for use with selected merchants |
US20080046349A1 (en) | 2006-08-17 | 2008-02-21 | Verizon Data Services Inc. | Method and systems for providing online banking and account aggregation services |
US7346909B1 (en) | 2006-08-28 | 2008-03-18 | Intel Corporation | Network-like communication and stack synchronization for different virtual machines on the same physical device |
US9176765B2 (en) | 2006-09-25 | 2015-11-03 | Lenovo (Beijing) Limited | Virtual machine system and a method for sharing a graphics card amongst virtual machines |
US20110106607A1 (en) * | 2006-11-30 | 2011-05-05 | Chris Alfonso | Techniques For Targeted Offers |
US7688719B2 (en) | 2006-12-11 | 2010-03-30 | Sap (Ag) | Virtualization and high availability of network connections |
US8256666B2 (en) | 2007-01-30 | 2012-09-04 | Phil Dixon | Processing transactions of different payment devices of the same issuer account |
CN101241445B (en) | 2007-02-08 | 2011-07-27 | 联想(北京)有限公司 | Virtual machine system and its method for accessing display card |
EP1962192A1 (en) | 2007-02-21 | 2008-08-27 | Deutsche Telekom AG | Method and system for the transparent migration of virtual machine storage |
US8374634B2 (en) | 2007-03-16 | 2013-02-12 | Finsphere Corporation | System and method for automated analysis comparing a wireless device location with another geographic location |
US8356286B2 (en) | 2007-03-30 | 2013-01-15 | Sap Ag | Method and system for providing on-demand profiling infrastructure for profiling at virtual machines |
US20080297433A1 (en) | 2007-05-29 | 2008-12-04 | Winbond Electronics Corporation | Secure activation of auxiliary display |
US7930249B2 (en) | 2007-07-11 | 2011-04-19 | Qualcomm Incorporated | Mobile wireless financial instrument for automatically selecting a payment instrument |
US8468310B2 (en) | 2007-07-31 | 2013-06-18 | Vmware, Inc. | Method and system for tracking data correspondences |
US8326758B2 (en) | 2007-08-06 | 2012-12-04 | Enpulz, L.L.C. | Proxy card representing many monetary sources from a plurality of vendors |
US8060876B2 (en) | 2007-08-10 | 2011-11-15 | Intel Corporation | Methods and apparatus for creating an isolated partition for a virtual trusted platform module |
KR100861390B1 (en) | 2007-09-07 | 2008-10-01 | 박수민 | Artificial intelligence settlement system for optimum card recommendation service and payment apparatus and combination card payment terminal for the same |
KR100929852B1 (en) | 2007-09-20 | 2009-12-04 | 한국전자통신연구원 | Apparatus and method for communication between applications on virtual machine using shared memory |
US8689224B2 (en) | 2007-09-26 | 2014-04-01 | The Boeing Company | Methods and systems for preserving certified software through virtualization |
US8249257B2 (en) | 2007-09-28 | 2012-08-21 | Intel Corporation | Virtual TPM keys rooted in a hardware TPM |
US20090098854A1 (en) | 2007-10-11 | 2009-04-16 | Harexinfotech Inc. | Method of providing billing and payment service using settlement service function of mobile electronic wallet and system therefor |
US20090204964A1 (en) | 2007-10-12 | 2009-08-13 | Foley Peter F | Distributed trusted virtualization platform |
US8539098B2 (en) | 2007-10-17 | 2013-09-17 | Dispersive Networks, Inc. | Multiplexed client server (MCS) communications and systems |
US8560634B2 (en) | 2007-10-17 | 2013-10-15 | Dispersive Networks, Inc. | Apparatus, systems and methods utilizing dispersive networking |
US8396799B2 (en) | 2007-11-29 | 2013-03-12 | Visa U.S.A. Inc. | Media device payments remote control personalization and protection |
US7797748B2 (en) | 2007-12-12 | 2010-09-14 | Vmware, Inc. | On-access anti-virus mechanism for virtual machine architecture |
US8321261B2 (en) * | 2007-12-14 | 2012-11-27 | John Nicholas and Kristin Gross | Integrated gourmet item data collection, recommender and vending system and method |
US8259948B2 (en) | 2007-12-29 | 2012-09-04 | Intel Corporation | Virtual TPM key migration using hardware keys |
US20090172331A1 (en) | 2007-12-31 | 2009-07-02 | Balaji Vembu | Securing content for playback |
US7766244B1 (en) | 2007-12-31 | 2010-08-03 | Jpmorgan Chase Bank, N.A. | System and method for processing transactions using a multi-account transactions device |
US8233841B2 (en) | 2008-01-30 | 2012-07-31 | Ebay Inc. | Near field communication initialization |
US20090240620A1 (en) | 2008-03-24 | 2009-09-24 | Propay Usa, Inc. | Secure payment system |
US9519933B2 (en) | 2008-06-13 | 2016-12-13 | United Parcel Service Of America, Inc. | Delivery payment systems |
US7941539B2 (en) | 2008-06-30 | 2011-05-10 | Oracle America, Inc. | Method and system for creating a virtual router in a blade chassis to maintain connectivity |
US8069121B2 (en) | 2008-08-04 | 2011-11-29 | ProPay Inc. | End-to-end secure payment processes |
EP2329439A4 (en) | 2008-08-07 | 2013-10-02 | Mastercard International Inc | A method for providing a credit cardholder with multiple funding options |
US8627312B2 (en) | 2008-08-28 | 2014-01-07 | Netapp, Inc. | Methods and systems for integrated storage and data management using a hypervisor |
US20100114739A1 (en) | 2008-09-03 | 2010-05-06 | David Johnston | Systems and methods for a comprehensive integrated and universal content selling and buying platform |
US10380573B2 (en) | 2008-09-30 | 2019-08-13 | Apple Inc. | Peer-to-peer financial transaction devices and methods |
JP5104958B2 (en) | 2008-10-03 | 2012-12-19 | 富士通株式会社 | Virtual computer system test method, test program, recording medium thereof, and virtual computer system |
US8352368B2 (en) | 2008-10-13 | 2013-01-08 | Visa International Service Association | P2P transfer using prepaid card |
US9292852B2 (en) | 2008-11-08 | 2016-03-22 | FonWallet Transactions Solutions, Inc. | System and method for applying stored value to a financial transaction |
US8868675B2 (en) | 2008-12-04 | 2014-10-21 | Cisco Technology, Inc. | Network optimization using distributed virtual resources |
CA2749637A1 (en) | 2009-01-15 | 2010-07-22 | Visa U.S.A. Inc. | Incentives associated with linked financial accounts |
US8600857B2 (en) * | 2009-01-21 | 2013-12-03 | Truaxis, Inc. | System and method for providing a savings opportunity in association with a financial account |
CN101819564B (en) | 2009-02-26 | 2013-04-17 | 国际商业机器公司 | Method and device for assisting communication between virtual machines |
US20100257040A1 (en) | 2009-03-19 | 2010-10-07 | Shop.Com | Multi-Merchant Reward Points Payment System |
US20100274718A1 (en) | 2009-04-27 | 2010-10-28 | Bank Of America Corporation | Financial institute-implemented account management system |
US9131007B2 (en) | 2009-05-19 | 2015-09-08 | Vitrual World Computing, Inc. | System and method for dynamically transcoding data requests |
US8167200B2 (en) | 2009-07-09 | 2012-05-01 | Kenichi Uchikura | Authorization verification system |
US20110087592A1 (en) * | 2009-10-13 | 2011-04-14 | Van Der Veen Larry | Systems and methods for facilitating transactions |
US20110145152A1 (en) | 2009-12-15 | 2011-06-16 | Mccown Steven Harvey | Systems, apparatus, and methods for identity verification and funds transfer via a payment proxy system |
US20110153402A1 (en) * | 2009-12-23 | 2011-06-23 | Jack Wells Craig | Methods and Apparatus for Credit Card Reward and Cost Management |
US9367834B2 (en) | 2010-01-22 | 2016-06-14 | Iii Holdings 1, Llc | Systems, methods, and computer products for processing payments using a proxy card |
US20110191149A1 (en) | 2010-01-29 | 2011-08-04 | Bank Of America Corporation | Customer-selected payment clearinghouse |
US20110218849A1 (en) | 2010-03-03 | 2011-09-08 | Rutigliano John R | Cloud platform for multiple account management & automated transaction processing |
EP2545456A4 (en) | 2010-03-11 | 2014-01-08 | Aol Inc | Systems and methods for location tracking in a social network |
US20110282780A1 (en) | 2010-04-19 | 2011-11-17 | Susan French | Method and system for determining fees and foreign exchange rates for a value transfer transaction |
US20110320345A1 (en) | 2010-06-29 | 2011-12-29 | Ebay, Inc. | Smart wallet |
US20120066681A1 (en) | 2010-09-12 | 2012-03-15 | Levy Tomer | System and method for management of a virtual machine environment |
US8571937B2 (en) | 2010-10-20 | 2013-10-29 | Playspan Inc. | Dynamic payment optimization apparatuses, methods and systems |
US20120267432A1 (en) | 2010-11-12 | 2012-10-25 | Kuttuva Avinash | Secure payments with global mobile virtual wallet |
WO2012103128A2 (en) | 2011-01-24 | 2012-08-02 | Visa International Service Association | Statement portal with receipt tagging and associated enhanced benefit messaging |
US20130030934A1 (en) | 2011-01-28 | 2013-01-31 | Zumigo, Inc. | System and method for credit card transaction approval based on mobile subscriber terminal location |
US20120197773A1 (en) | 2011-01-31 | 2012-08-02 | Bank Of America Corporation | Systems and methods for providing position-based budgeting information |
US9083747B2 (en) | 2011-03-07 | 2015-07-14 | Facebook, Inc. | Automated location check-in for geo-social networking system |
US20120259768A1 (en) | 2011-04-05 | 2012-10-11 | Ebay Inc. | System and method for providing proxy accounts |
SG187283A1 (en) | 2011-07-27 | 2013-02-28 | goodwin Russell | Intelligent payment system |
US8687784B2 (en) | 2011-08-01 | 2014-04-01 | International Business Machines Corporation | Determining local time in a location of a telephone |
US8521180B2 (en) | 2011-08-12 | 2013-08-27 | Disney Enterprises, Inc. | Location-based automated check-in to a social network recognized location using a token |
US20130054458A1 (en) | 2011-08-24 | 2013-02-28 | Moneygram International, Inc. | Money Transfer Utilizing a Social Network Environment |
US8401904B1 (en) | 2011-11-13 | 2013-03-19 | Google Inc. | Real-time payment authorization |
US20140114776A1 (en) | 2011-12-31 | 2014-04-24 | Kaushal Solanki | System and Method for Obtaining Services at a Service Point Using a Mobile Device |
US8639621B1 (en) | 2012-04-25 | 2014-01-28 | Wells Fargo Bank, N.A. | System and method for a mobile wallet |
US20130311357A1 (en) | 2012-05-16 | 2013-11-21 | Wolfgang Kring | Methods for facilitating online transactions involving a plurality of unique currencies |
US20140012704A1 (en) | 2012-07-05 | 2014-01-09 | Google Inc. | Selecting a preferred payment instrument based on a merchant category |
US8676709B2 (en) | 2012-07-31 | 2014-03-18 | Google Inc. | Merchant category codes in a proxy card transaction |
US9092767B1 (en) | 2013-03-04 | 2015-07-28 | Google Inc. | Selecting a preferred payment instrument |
-
2012
- 2012-07-05 US US13/542,303 patent/US20140012704A1/en not_active Abandoned
-
2013
- 2013-07-05 WO PCT/US2013/049446 patent/WO2014008471A1/en active Application Filing
- 2013-07-05 AU AU2013207643A patent/AU2013207643B2/en active Active
-
2016
- 2016-03-16 US US15/072,191 patent/US10185954B2/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060151598A1 (en) * | 2005-01-13 | 2006-07-13 | Yen-Fu Chen | Categorization based spending control |
US20100017325A1 (en) * | 2008-07-17 | 2010-01-21 | International Business Machines Corporation | Multiple financial account transaction processing |
US20100082445A1 (en) * | 2008-09-30 | 2010-04-01 | Apple Inc. | Smart menu options |
US20120078786A1 (en) * | 2010-09-24 | 2012-03-29 | Bank Of America Corporation | Deposit transaction-level information |
US20130110658A1 (en) * | 2011-05-05 | 2013-05-02 | Transaction Network Services, Inc. | Systems and methods for enabling mobile payments |
US20130275303A1 (en) * | 2012-04-11 | 2013-10-17 | Mastercard International Incorporated | Method and system for two stage authentication with geolocation |
US20140006198A1 (en) * | 2012-06-30 | 2014-01-02 | At&T Mobility Ii Llc | Generating and Categorizing Transaction Records |
Cited By (91)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10185954B2 (en) | 2012-07-05 | 2019-01-22 | Google Llc | Selecting a preferred payment instrument based on a merchant category |
US20140114777A1 (en) * | 2012-10-22 | 2014-04-24 | Remi Guyot | Tailored Display of Payment Options |
US20180204197A1 (en) * | 2012-10-22 | 2018-07-19 | Ebay Inc. | Tailored display of payment options |
US11004047B2 (en) | 2012-10-22 | 2021-05-11 | Ebay Inc. | Tailored display of payment options |
US20210224771A1 (en) * | 2012-10-22 | 2021-07-22 | Ebay Inc. | Tailored display of payment options |
US9934500B2 (en) * | 2012-10-22 | 2018-04-03 | Ebay Inc. | Tailored display of payment options |
US9679284B2 (en) | 2013-03-04 | 2017-06-13 | Google Inc. | Selecting a preferred payment instrument |
US10579981B2 (en) | 2013-03-04 | 2020-03-03 | Google Llc | Selecting a preferred payment instrument |
US11144902B2 (en) | 2013-08-23 | 2021-10-12 | Visa International Service Association | Dynamic account selection |
US10346822B2 (en) * | 2013-08-23 | 2019-07-09 | Visa International Service Association | Dynamic account selection |
US20150058146A1 (en) * | 2013-08-23 | 2015-02-26 | Ajit Gaddam | Dynamic Account Selection |
US10460299B1 (en) | 2013-10-24 | 2019-10-29 | United Services Automobile Association (Usaa) | Methods and systems for systematic recognition of recurring payees and payments |
US11151529B1 (en) | 2013-10-24 | 2021-10-19 | United Services Automobile Association (Usaa) | Methods and systems for systematic recognition of recurring payees and payments |
US9934494B1 (en) * | 2013-10-24 | 2018-04-03 | United Services Automobile Association (Usaa) | Methods and systems for systematic recognition of recurring payees and payments |
US20150120428A1 (en) * | 2013-10-28 | 2015-04-30 | U.S. Bank, National Association | Mobile-enabled commerce service aggregation |
US11210725B2 (en) | 2014-03-24 | 2021-12-28 | Square, Inc. | Determining pricing information from merchant data |
US10402896B1 (en) | 2014-07-03 | 2019-09-03 | Wells Fargo Bank, N.A. | Systems and methods for interactive financial categorization and budgeting |
US11551291B1 (en) | 2014-07-03 | 2023-01-10 | Wells Fargo Bank, N.A. | Systems and methods for interactive financial categorization and budgeting |
US11244406B1 (en) | 2014-08-12 | 2022-02-08 | Wells Fargo Bank, N.A. | Personal financial planning and engagement with peer-based comparison |
US10223754B1 (en) | 2014-08-12 | 2019-03-05 | Wells Fargo Bank, N.A. | Personal financial planning and engagement with peer-based comparison |
KR20170059467A (en) * | 2014-09-22 | 2017-05-30 | 마스터카드 인터내셔날, 인코포레이티드 | Payment systems and methods for managing payment card use |
US20160140535A1 (en) * | 2014-09-22 | 2016-05-19 | Mastercard International Incorporated | Payment systems and methods for managing payment card use |
US11455612B2 (en) * | 2014-09-22 | 2022-09-27 | Mastercard International Incorporated | Payment systems and methods for managing payment card use |
CN107004189A (en) * | 2014-09-22 | 2017-08-01 | 万事达卡国际股份有限公司 | Payment system and the method used for managing payment card |
WO2016048863A1 (en) * | 2014-09-22 | 2016-03-31 | Mastercard International Incorporated | Payment systems and methods for managing payment card use |
KR102117977B1 (en) * | 2014-09-22 | 2020-06-02 | 마스터카드 인터내셔날, 인코포레이티드 | Payment systems and methods for managing payment card use |
US10255631B2 (en) * | 2014-10-01 | 2019-04-09 | Google Llc | Annotating a transaction history record with merchant information identified from a merchant identifier and user computing device location data |
US20160098790A1 (en) * | 2014-10-01 | 2016-04-07 | Google Inc. | Annotating a transaction history record with merchant information identified from a merchant identifier and user computing device location data |
WO2016054226A1 (en) * | 2014-10-01 | 2016-04-07 | Google Inc. | Annotating a transaction history record with merchant information identified from a merchant identifier and user computing device location data |
US10706411B2 (en) * | 2014-11-18 | 2020-07-07 | Google Llc | Automatically communicating user device data to a transaction computing system |
US11948143B2 (en) | 2014-11-18 | 2024-04-02 | Google Llc | Automatically communicating user device data to a transaction computing system |
US20160140541A1 (en) * | 2014-11-18 | 2016-05-19 | Google Inc. | Automatically communicating user device data to a transaction computing system |
CN107209892A (en) * | 2014-11-18 | 2017-09-26 | 谷歌公司 | Customer equipment data is transmitted automatically to transaction computing system |
WO2016081648A1 (en) * | 2014-11-18 | 2016-05-26 | Google Inc. | Automatically communicating user device data to a transaction computing system |
US11538024B2 (en) * | 2014-11-18 | 2022-12-27 | Google Llc | Automatically communicating user device data to a transaction computing system |
US9916575B2 (en) | 2014-11-19 | 2018-03-13 | Qualcomm Incorporated | Systems and methods for adaptive routing for multiple secure elements |
WO2016098774A1 (en) * | 2014-12-16 | 2016-06-23 | 大日本印刷株式会社 | Store terminal device, membership management server, proxy settlement server, and settlement method |
US11017369B1 (en) | 2015-04-29 | 2021-05-25 | Square, Inc. | Cloud-based inventory and discount pricing management system |
US20160335702A1 (en) * | 2015-05-13 | 2016-11-17 | Sony Corporation | Method and system for providing recommendation for selection of a merchant store |
US10719865B2 (en) * | 2015-05-13 | 2020-07-21 | Sony Corporation | Method and system for providing recommendation for selection of a merchant store |
US11227301B1 (en) | 2015-06-05 | 2022-01-18 | Wells Fargo Bank, N.A. | Systems and methods for providing real-time payment recommendations and offers |
US11544730B1 (en) | 2015-06-05 | 2023-01-03 | Wells Fargo Bank, N.A. | Systems and methods for providing real-time payment recommendations and offers |
US10699289B1 (en) | 2015-06-05 | 2020-06-30 | Wells Fargo Bank, N.A. | Systems and methods for providing real-time payment recommendations and offers |
US10740852B1 (en) * | 2015-06-23 | 2020-08-11 | Square, Inc. | Classifying merchants |
US10949796B1 (en) | 2015-07-15 | 2021-03-16 | Square, Inc. | Coordination of inventory ordering across merchants |
US10909486B1 (en) | 2015-07-15 | 2021-02-02 | Square, Inc. | Inventory processing using merchant-based distributed warehousing |
WO2017015138A1 (en) * | 2015-07-17 | 2017-01-26 | Google Inc. | Merchant-specific functionality services |
WO2017015131A1 (en) * | 2015-07-17 | 2017-01-26 | Google Inc. | Merchant-specific functionality services |
WO2017015128A1 (en) * | 2015-07-17 | 2017-01-26 | Google Inc. | Merchant-specific functionality services |
US10430782B2 (en) | 2015-07-17 | 2019-10-01 | Google Llc | Merchant-specific functionality services |
US20170046686A1 (en) * | 2015-08-13 | 2017-02-16 | Lg Electronics Inc. | Mobile Terminal |
US10467613B2 (en) * | 2015-08-13 | 2019-11-05 | Lg Electronics Inc. | Mobile terminal |
CN105279646A (en) * | 2015-09-25 | 2016-01-27 | 宇龙计算机通信科技(深圳)有限公司 | Payment application selection method and mobile terminal |
WO2017116645A1 (en) * | 2015-12-31 | 2017-07-06 | Mastercard International Incorporated | Method and system for secure consumer identification |
US10558975B2 (en) | 2016-08-17 | 2020-02-11 | Mastercard International Incorporated | Systems and methods for use in facilitating transactions |
US10423947B1 (en) * | 2016-09-09 | 2019-09-24 | Worldpay, Llc | User interfaces for using shared databases for managing supplemental payment sources |
US20210209577A1 (en) * | 2016-09-09 | 2021-07-08 | Worldpay, Llc | User interfaces for using shared databases for managing supplemental payment sources |
US10402829B1 (en) * | 2016-09-09 | 2019-09-03 | Worldpay, Llc | Systems and methods for using shared databases for managing supplemental payment sources |
US20210224807A1 (en) * | 2016-09-09 | 2021-07-22 | Worldpay, Llc | Systems and methods for using shared databases for managing supplemental payment sources |
US10977658B2 (en) * | 2016-09-09 | 2021-04-13 | Worldpay, Llc | Systems and methods for using shared databases for managing supplemental payment sources |
US10990952B2 (en) * | 2016-09-09 | 2021-04-27 | Worldpay, Llc | User interfaces for using shared databases for managing supplemental payment sources |
US11847628B2 (en) * | 2016-09-09 | 2023-12-19 | Worldpay, Llc | User interfaces for using shared databases for managing supplemental payment sources |
US11978056B2 (en) * | 2016-09-09 | 2024-05-07 | Worldpay, Llc | Systems and methods for using shared databases for managing supplemental payment sources |
EP3333790A1 (en) * | 2016-12-07 | 2018-06-13 | Mastercard International Incorporated | Automatic context-based selection from a digital wallet |
US10608918B2 (en) | 2017-04-03 | 2020-03-31 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and one or more servers to determine likelihood of user device using a routing network |
US20180288562A1 (en) * | 2017-04-03 | 2018-10-04 | Bank Of America Corporation | Data Transfer Between Computing Device and User Device Over Session or Connection in Response to Wireless Sensing Device Detecting User Device at a Location |
US10601934B2 (en) | 2017-04-03 | 2020-03-24 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and one or more servers for transmitting data to a third party computing device |
US10798007B2 (en) | 2017-04-03 | 2020-10-06 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and server associated with a routing network for modifying one or more parameters of the routing network |
US10716060B2 (en) | 2017-04-03 | 2020-07-14 | Bank Of America Corporation | Data transfer between computing device and user device at different locations and over session or connection to display one or more routing networks to use |
US10601718B2 (en) | 2017-04-03 | 2020-03-24 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and server associated with a routing network for modifying one or more parameters of the routing network |
US10609156B2 (en) | 2017-04-03 | 2020-03-31 | Bank Of America Corporation | Data transfer, over session or connection, and between computing device and server associated with one or more routing networks in response to detecting activity |
US11810092B1 (en) * | 2017-06-26 | 2023-11-07 | Wells Fargo Bank, N.A. | Systems and methods for distinguishing between profiles in a passive authentication scheme |
US11030603B1 (en) * | 2017-06-26 | 2021-06-08 | Wells Fargo Bank, N.A. | Systems and methods for distinguishing between profiles in a passive authentication scheme |
US10949825B1 (en) | 2017-06-30 | 2021-03-16 | Square, Inc. | Adaptive merchant classification |
CN111066045A (en) * | 2017-08-25 | 2020-04-24 | 谷歌有限责任公司 | Transacting with multiple payment service providers |
WO2019040150A1 (en) * | 2017-08-25 | 2019-02-28 | Google Llc | Conducting transactions with multiple payment service providers |
US11348119B1 (en) | 2017-10-18 | 2022-05-31 | Block, Inc. | Intelligent merchant onboarding |
US11720905B2 (en) | 2017-10-18 | 2023-08-08 | Block, Inc. | Intelligent merchant onboarding |
CN109685654A (en) * | 2017-10-19 | 2019-04-26 | 资本一号服务有限责任公司 | For the user account control of online transaction |
US11062320B2 (en) | 2017-10-19 | 2021-07-13 | Capital One Services, Llc | User account controls for online transactions |
EP3474210A1 (en) * | 2017-10-19 | 2019-04-24 | Capital One Services, LLC | User account controls for online transactions |
CN113837755A (en) * | 2018-07-05 | 2021-12-24 | 创新先进技术有限公司 | Offline transaction distinguishing method and device and computer equipment |
US11861579B1 (en) | 2018-07-31 | 2024-01-02 | Block, Inc. | Intelligent inventory system |
US20210248668A1 (en) * | 2018-09-11 | 2021-08-12 | Nippon Food Manufacturer Co. | Virtual store provision system |
EP3648036A1 (en) * | 2018-10-29 | 2020-05-06 | Mastercard International Incorporated | Non-default application selection during a transaction |
US10878394B1 (en) | 2018-11-29 | 2020-12-29 | Square, Inc. | Intelligent inventory recommendations |
US11481749B1 (en) | 2018-11-29 | 2022-10-25 | Block, Inc. | Intelligent inventory recommendations |
WO2020121063A1 (en) * | 2018-12-11 | 2020-06-18 | Orange | Method for operating a device for selecting a virtual card in a digital wallet |
US20210217014A1 (en) * | 2020-01-09 | 2021-07-15 | Visa International Service Association | Method, System, and Computer Program Product for Co-Located Merchant Anomaly Detection |
EP4300397A1 (en) * | 2022-06-28 | 2024-01-03 | Thales Dis France Sas | Method for managing a card |
WO2024002596A1 (en) * | 2022-06-28 | 2024-01-04 | Thales Dis France Sas | Method for managing a card |
Also Published As
Publication number | Publication date |
---|---|
AU2013207643B2 (en) | 2014-09-18 |
WO2014008471A1 (en) | 2014-01-09 |
US10185954B2 (en) | 2019-01-22 |
AU2013207643A1 (en) | 2014-01-23 |
US20160196549A1 (en) | 2016-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10185954B2 (en) | Selecting a preferred payment instrument based on a merchant category | |
US20200234270A1 (en) | Selecting a Preferred Payment Instrument | |
US11107110B2 (en) | Customer data aggregation | |
US9767471B1 (en) | Determining recommendations from buyer information | |
US8972298B2 (en) | Merchant category codes in a proxy card transaction | |
US10853890B2 (en) | Social media transaction visualization structure | |
US9996829B1 (en) | System for global point-of-sale capabilities | |
US20170116599A1 (en) | Method for predicting purchasing behaviour of digital wallet users for wallet-based transactions | |
US20140257958A1 (en) | Merchant incentive programs on proxy card systems | |
US20130080236A1 (en) | Systems and Methods for Enrolling Consumers in Loyalty Programs | |
US20140095385A1 (en) | Selecting merchants for automatic payments | |
US11847633B1 (en) | Connected payment card systems and methods | |
WO2014047120A2 (en) | Data sharing platform | |
US20170061461A1 (en) | Secondary device communications for intelligent selection of electronic sources | |
EP3111400A1 (en) | Cross-channel system for electronic commerce and methods useful in conjunction therewith | |
US20140067462A1 (en) | Integrating electronic payments and social media | |
US20150310402A1 (en) | Transaction conversion with payment card | |
US11741446B2 (en) | Electronic system and method for transaction processing | |
WO2020046461A1 (en) | Systems and methods for use in contactless communication | |
US20170308897A1 (en) | Systems, methods, and computer program products for the receipt of health and wellness transaction offers | |
US9785921B2 (en) | Systems and methods for processing decoupled debit transactions | |
US20200082429A1 (en) | Payment selection systems and methods | |
US20170255882A1 (en) | Systems and Methods for Facilitating Event Access Through Payment Accounts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GOOGLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MIZHEN, BORIS;CURTIS, KENDRA SHANNON;SIGNING DATES FROM 20120626 TO 20120629;REEL/FRAME:028511/0036 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |