WO2020142105A1 - Systèmes et procédés de paiement intelligent - Google Patents

Systèmes et procédés de paiement intelligent Download PDF

Info

Publication number
WO2020142105A1
WO2020142105A1 PCT/US2019/012370 US2019012370W WO2020142105A1 WO 2020142105 A1 WO2020142105 A1 WO 2020142105A1 US 2019012370 W US2019012370 W US 2019012370W WO 2020142105 A1 WO2020142105 A1 WO 2020142105A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
payment account
payment
smart
benefit
Prior art date
Application number
PCT/US2019/012370
Other languages
English (en)
Inventor
Prasanth Yeddula
Ashwini Laxminarayana TANTRY
Original Assignee
Visa International Service Association
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Visa International Service Association filed Critical Visa International Service Association
Priority to PCT/US2019/012370 priority Critical patent/WO2020142105A1/fr
Publication of WO2020142105A1 publication Critical patent/WO2020142105A1/fr

Links

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
    • 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
    • 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/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • 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/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • 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/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • 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/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates

Definitions

  • the invention relates to systems and methods for managing payment account selection.
  • Many payment accounts offer various loyalty or rewards programs to incentivize consumers to use their respective payment accounts for making purchases.
  • a credit card company may offer rewards points to its users based upon the amount of dollars spent through transactions using that company’s credit card.
  • Many other payment accounts may also offer rewards, such as bank debit cards, retailers that offer rewards cards, or even groups of retailers or other merchants offering shared rewards.
  • Some credit or debit card issuers may offer various different types of rewards programs that offer bonus points for certain types of purchases, such as airline tickets, hotels, gasoline, restaurants, groceries, etc. Some rewards programs may even offer different bonus rewards multipliers from week to week, or from month to month.
  • a single user may sign up with more than one of payment account, for which the user may receive multiple cards.
  • a user would need to decide which payment account to use for each new transaction, often unaware of what particularly rewards or points are available for each separate payment account.
  • a system is needed that will help users more effectively take advantage of their various payment account programs.
  • the disclosure describes a smart payment system that may optimize benefits to a user associated with a plurality of user payment accounts.
  • the system and methods may include determining a payment account plan for a transaction that may assign individual purchase items in the transaction to particular payment accounts based on the benefits those payment accounts may provide.
  • FIG. 1 is an illustration of the elements of an embodiment of a system that includes a system for monitoring and preventing fraud as disclosed herein;
  • Fig. 2 is a schematic illustration of elements of an embodiment of an example computing device;
  • FIG. 3 is a schematic illustration of elements of an embodiment of a server type computing device
  • FIG. 4 is a block diagram illustrating system elements for an embodiment of a smart payment system in accordance with the current disclosure
  • FIG. 5 is an example signaling flow diagram showing communications within a smart payment system in accordance with the current disclosure
  • FIG. 6A is a user interface diagram illustrating example features of an embodiment of a graphical user interface for the smart payment system as described herein;
  • Fig. 6B is a user interface diagram illustrating example features of the graphical user interface of Fig. 6A;
  • FIG. 7 is a flow chart of an embodiment of a process for using the smart payment system described herein;
  • FIG. 8 is a flow chart of another embodiment of a process for using the smart payment system described herein.
  • FIG. 9 is a transaction flow diagram of an embodiment of the smart payment system as described herein.
  • the smart payment system and methods described herein may provide a user of multiple payments accounts an efficient way to maximize the rewards received through one or more payment accounts for a given purchase or transaction using a digital wallet device or service.
  • a user may add one or more payment accounts to the user’s digital wallet, which may then be tokenized and ready for making payments using a user device that includes the digital wallet.
  • the various payment accounts associated with the digital wallet may each correspond to a particular points or rewards program, or may provide other benefits to the user.
  • Each rewards account program may accumulate rewards points for each purchase made using the program’s respective payment account, or provide rewards for purchases of items in particular product categories or brands. Additionally, some merchants may offer additional rewards, rebates, discounts, etc., for certain purchases or for using a particular payment account.
  • a user making purchases or other transactions using a digital wallet program or another payment method may need to select which of the multiple payment accounts the user would like to use for a particular transaction, which may include various multiple purchased items.
  • a default payment account may be selected by the user, or the user may be prompted to select an account for each transaction.
  • a user may be unaware of the loyalty, rewards points, or other benefits available for any particular product or service or overall transaction, or what type of rewards or points may be earned with a given transaction. This may mean a user could use a card or other payment account at random without knowing the loyalty points that could be earned by using a different account, or the other benefits that could be received (e.g., offers, cash back, discounts, etc.).
  • the smart payment system may allow a user to take advantage of the benefits associated with their payment accounts even if the user may not be aware of those benefits at the time of the purchase.
  • a smart wallet application on or available to a user computing device may automatically select the payment account among the user’s multiple payment accounts that provides the greatest benefit to the user.
  • the user may only need to trigger the transaction by tapping a button on a smart wallet application or other triggering activity, and the smart payment system may complete the transaction with one or more of the user’s payment accounts in an optimal combination. For example, in a user may use the smart payment application to initiate a purchase of multiple items that may belong to different product categories.
  • the smart payment system may determine that it would be most advantageous to the user to use different payment accounts for each product in the transaction, and may use each respective payment account to pay for each respective item without the user needing to provide additional input or initiate multiple transactions.
  • the smart payment system may base its determination on issuer rewards points, merchant offers, issuer-gateway offers, membership-based issuer offers, merchandise-based incentives or offers, gift cards or pre-paid cards available, retail credit cards, category of merchandise purchased, etc.
  • the smart payment system may provide the user with an option to proceed with a transaction using smart payments or with manual payment account selection.
  • the manual payment account selection may include providing the user an opportunity to select which payment account to use for the transaction.
  • Using smart payments may trigger the smart payment system to initiate the automatic payment account selection as described herein.
  • the smart payment system may send a notification to a user computing device.
  • the notification may alert the user regarding the payment account or accounts selected for the transaction.
  • the user may then authorize the smart payment system to complete the transaction via the user device, e.g., through the smart payment application.
  • the smart payment system may automatically select the payment account(s) used for the transaction based on the benefits without contacting the user for authorization. In some embodiments, once the user has authorized the transaction, the smart payment system may reach out to the issuer(s) of the selected account(s) and request an open authorization (OAuth) and proceed with the transaction.
  • OAuth open authorization
  • a first payment account associated may offer different benefits for a given transaction or purchase than a second payment account.
  • the smart payment system may, in some embodiments, determine which of the user’s various payment accounts or combination of payment accounts would provide the user with the greatest benefit. The system may then, either automatically or upon additional prompting from the user, select the payment account or combination of accounts that will provide the greatest benefit to the user. For example, if the system determines that the second payment account will provide a more advantageous benefit than the first payment account, the system may execute the transaction with the second payment account in order to earn those benefits.
  • the system may determine that purchasing a first product with the first payment account and the second product with the second payment account will maximize benefits for the user. In some embodiments, the system may determine an optimal combination of payment accounts based on any number of factors such as category of merchandise purchased, retail offers, credit card or payment account reward points, issuer-gateway offers, merchant offers, manufacturer offers, membership-based issuer offers, merchandise- based decisions, gift or prepaid cards or credits, retail credit cards, etc.
  • the system may, among other things, provide a technical solution to the problem of imperfect knowledge of rewards or other benefits associated with payment accounts, and a technical problem of the inability to readily access benefit information for multiple different payment accounts and multiple different purchase items.
  • the systems and methods described herein are not merely computer implemented activities that could be performed in a person’s head or using pen and paper.
  • the systems and method of the smart payment system provide at least technical solutions rooted in computer technology that.
  • the disclosure describes a processor- implemented method for payment selection.
  • the method may include receiving, from a user computing device, a user identifier associated with a user and payment account information associated with a plurality of user payment accounts associated with the user.
  • the method may also include receiving, from the user computing device, the user identifier and a beacon identifier associated with a smart billing machine.
  • the method may include receiving, from the smart billing machine, the beacon identifier associated with the smart billing machine and purchase item information associated with one or more purchase items in a transaction. Based on receiving the beacon identifier from both the user computing device and the smart billing machine, the method may include identifying the plurality of user payment accounts associated with the user.
  • the method may also include determining benefit information associated with each of the plurality of user payment accounts associated with the user. Based on the benefit information, the method may include determining a payment account plan that includes assigning each of the one or more purchase items to one of the plurality of user payment accounts, and transmitting the payment account plan to the user computing device so as to enable the user computing device to complete the transaction based on the payment account plan.
  • the disclosure describes a method comprising including receiving, from a user computing device, a user identifier associated with a user and payment account information associated with a plurality of user payment accounts associated with the user.
  • the plurality of user payment accounts may include a first user payment account and a second user payment account.
  • the method may also include receiving, from the user computing device, the user identifier and a beacon identifier associated with a smart billing machine.
  • the method my include receiving, from the smart billing machine, the beacon identifier associated with the smart billing machine and purchase item information associated with one or more purchase items in a transaction.
  • the one or more purchase items may include a first purchase item and a second purchase item.
  • the method may include identifying the plurality of user payment accounts associated with the user and determining benefit information associated with each of the plurality of user payment accounts.
  • the method may include determining that a benefit associated with purchasing the first purchase item with the first user payment account is greater than a benefit associated with purchasing the first purchased item with the second user payment account, and determining that a benefit associated with purchasing the second purchase item with the second user payment account is greater than a benefit associated with purchasing the second purchase item with the first user payment account.
  • the method may include determining a payment account plan that includes assigning each the first purchase item to the first user payment account and the second purchase item to the second user payment account, and transmitting the payment account plan to the user computing device so as to enable the user computing device to complete the transaction based on the payment account plan.
  • the disclosure describes a method that may include receiving, from a user computing device, a user identifier associated with a user and payment account information associated with a plurality of user payment accounts associated with the user. The method may include determining benefit information associated with each of the plurality of user payment accounts associated with the user.
  • the method may include receiving, from the user computing device, the user identifier and a beacon identifier associated with a smart billing machine and receiving, from the smart billing machine, the beacon identifier associated with the smart billing machine and purchase item information associated with one or more purchase items in a transaction.
  • the method may include, in response at least to receiving the beacon identifier from both the user computing device and the smart billing machine, determining that a first purchase item of the one or more purchase items belongs to the first product category and that a second purchase item of the one or more purchase items belongs to the second product category.
  • the method may also include determining a payment account plan that includes assigning the first purchase item to the first user payment account and the second purchase item to the second user payment account, and transmitting the payment account plan to the user computing device so as to enable the user computing device to complete the transaction based on the payment account plan.
  • a payment account plan that includes assigning the first purchase item to the first user payment account and the second purchase item to the second user payment account
  • transmitting the payment account plan to the user computing device so as to enable the user computing device to complete the transaction based on the payment account plan.
  • Connection to the digital communication network 60 may be wired or wireless, and may be via the internet or via a cellular network or any other suitable connection service.
  • the system 50 may also include at least one point-of-sale (POS) device 69, such as in a merchant store, that may be able to connect to wirelessly connect to the user computing device 55.
  • POS device 69 may be a smart POS device.
  • the POS device 69 may also be connected to or be a part of a smart billing machine 71.
  • the POS device, the smart billing machine 71 or both may be connected wired or wirelessly to the digital communication network 60.
  • Various other computer servers may also be connected to via the digital communication network 60, such as a smart payment server 65 and a payment server 70.
  • the smart payment server 65 may be included as a server within or be a part of the payment server 70.
  • the payment server 70 may represent, for example, a credit card issuer, a bank, or another financial institution.
  • Various of these servers or computer entities may also be connected through a secure payment network 75.
  • the payment network 75 may be an electronic payment system used to accept, transmit, or process transactions made by users with payment cards for money, goods, or services, and to transfer information and funds among payment card issuers, merchants, payment card holders, payment processors, acquirers, etc.
  • At least the smart payment server 65, the payment server 70, a token server 80, an issuer server 85, and a merchant server 90 may be connected via the payment network 75, but it is contemplated that other entities, such as one or more acquirer, may be connected as well.
  • other entities such as one or more acquirer, may be connected as well.
  • multiple issuer servers associated with multiple different issuers and/or multiple merchant servers associated with multiple different merchants may also be connected to the payment network 75.
  • the payment server 70 and smart payment server 65 may also be connected to the one or more user computing devices 55 over the digital communication network 60.
  • the computing device 55 may be a device that operates using a portable power source, such as a battery.
  • the computing device 55 may also have a display 56 which may or may not be a touch sensitive display. More specifically, the display 56 may have a capacitance sensor, for example, that may be used to provide input data to the computing device 55.
  • an input pad 57 such as arrows, scroll wheels, keyboards, etc., may be used to provide inputs to the computing device 55.
  • the computing device 55 may have a microphone 58 which may accept and store verbal data, a camera 59 to accept images and a speaker 61 to communicate sounds.
  • FIG. 2 is a simplified illustration of the physical elements that make up an embodiment of a computing device 55
  • Fig. 3 is a simplified illustration of the physical elements that make up an embodiment of a server type computing device, such as the smart payment server 65, but the merchant server 90, the token server 80, and the issuer server 85 may reflect similar physical elements in some embodiments.
  • a sample computing device 55 is illustrated that is physically configured according to be part of the computing system 50 shown in Fig. 1.
  • the user computing device 55 may have a processor 1451 that is physically configured according to computer executable instructions.
  • the processor can be specially designed or configured to optimize communication between the server 65 and the computing device 55 relating to the smart payment service described herein.
  • the computing device 55 may have a portable power supply 1455 such as a battery, which may be rechargeable. It may also have a sound and video module 1461 which assists in displaying video and sound and may turn off when not in use to conserve power and battery life.
  • the computing device 55 may also have volatile memory 1465 and non volatile memory 1471.
  • the computing device 55 may have GPS capabilities that may be a separate circuit or may be part of the processor 1451.
  • There also may be an input/output bus 1475 that shuttles data to and from the various user input/output devices such as a microphone, a camera 59, a display 56, or other input/output devices.
  • the user computing device 55 also may control communicating with the networks, such as communications network 60 in Fig. 1 , either through wireless or wired devices. Of course, this is just one embodiment of the user computing device 55 and the number and types of user computing devices 55 is limited only by the imagination.
  • the smart payment server 65 is specially configured to run the smart payment service as described herein.
  • the smart payment server 65 may include a digital storage such as a magnetic disk, an optical disk, flash storage, non-volatile storage, etc. Structured data may be stored in the digital storage such as in a database.
  • the server 65 may have a processor 1500 that is physically configured according to computer executable instructions.
  • the processor 1500 can be specially designed or configured to optimize communication between a user computing device, such as computing device 55, and the server 65 relating to the payment selection service as described herein.
  • the server 65 may also have a sound and video module 1505 which assists in displaying video and sound and may turn off when not in use to conserve power and battery life.
  • the server 65 may also have volatile memory 1510 and non-volatile memory 1515.
  • a database 1525 for digitally storing structured data may be stored in the memory 1510 or 1515 or may be separate.
  • the database 1525 may also be part of a cloud of servers and may be stored in a distributed manner across a plurality of servers.
  • the input/output bus 1520 also may control communicating with the networks, such as communications network 60 and payment network 75, either through wireless or wired devices.
  • a smart payment controller for running the payment selection service through a smart payment application may be located on the user computing device 55.
  • the smart payment controller may be located on smart payment server 65, or both the computing device 55 and the server 65. Of course, this is just one embodiment of the smart payment server 65 and additional types of servers are contemplated herein.
  • the smart payment server 65 may be connected to the merchant server 90 either through the digital communication network 60, through the payment network 75 or through other connections.
  • the merchant server 90 may be associated with any type of merchant offering goods or services for purchase with payment cards, whether those purchases are online or otherwise.
  • the merchant server 90 or a group of servers may host a merchant website where the merchant’s goods or services may be purchased by a user.
  • the smart payment system may collect payment information from the user, such as payment card credentials, that may be used for the immediate transactions as well as for future purchases with the same or other merchants as further described herein. As such, the smart payment system may consolidate the entities to which a user shares its confidential payment information.
  • the user may share its payment card information with the smart payment system via software or other interface hosted by the system, and the smart payment system may store the payment and other account information for use in future purchases.
  • the smart payment system may also store information regarding rewards points, loyalty programs, or other benefits associated with the stored payment accounts.
  • the smart payment system may also be in contact with other payment account issuers to receive up-to-date information regarding the details of associated account benefits.
  • the smart payment system may be hosted on or otherwise run by the smart payment server 65.
  • the smart payment system may be hosted by another entity, such as an issuer using an issuer server 85 or a merchant using a merchant server 90.
  • a user may access the smart payment server 65 via a computing device 55 such as a smartphone, and may set up an account with the smart payment system.
  • the user may provide payment account or banking information for one or more payment accounts provided by one or more card issuers or associated with one or more merchants or banks.
  • One or more of the payment accounts may be associated with any of a variety of benefit programs.
  • the smart payment system may store such payment account information associated with the user’s account that can be retrieved at the user’s request to complete e-commerce transactions. Purchases using payment information stored with the smart payment system, however, may occur in any of a variety of ways.
  • the user may select a payment account or card stored through the smart payment system for use performing a given transaction.
  • the smart payment system may determine which of a user’s payment accounts to use for a given transaction based on the benefits available.
  • the computing device 55, the POS device 69, and the smart billing machine 71 may be able to communicate with a computer server or a plurality servers, such as the smart payment server 65, the payment server 70, issuer servers 85, and merchant servers 90.
  • the computing device 55 may be able to communicate in a variety of ways.
  • the communication may be wired such as through an Ethernet cable, a USB cable or RJ6 cable.
  • the communication may be wireless such as through Wi-Fi (802.11 standard), Bluetooth, cellular communication or near field communication devices.
  • the communication may be direct to the server or may be through a digital communication network 60 such as cellular service, through the Internet, through a private network, through Bluetooth, etc.
  • the user computing device 55 may communicate with the POS device 69 and/or the smart billing machine 71 wirelessly using any of the wireless communication methods listed above.
  • the smart payment server 65 may be associated with the smart payment system, and may send and receive information to and from a user computing device 55 associated with the user payment accounts of a user.
  • software may be included on the user computing device 55 allowing notifications to be received from the smart payment system via the digital communications network 60.
  • the software may be an application, such as a smart payment application, through which a user may complete transactions, such as banking, money transfer, merchant purchases, etc.
  • the software may be an add-on to a web browser included on the user computing device 55.
  • the smart payment system may be an application installed on the user computing device 55 that allows for the use of other applications on the user computing device, such as applications provided by a bank, online merchant, email service, payment provider, etc.
  • the smart payment service may provide notifications using software native to the user computing device 55, such as SMS messaging or other notifications.
  • the smart payment system may send notifications to the user computing device 55 regarding smart payment selections, such as are described in further detail below.
  • Fig. 4 is a data flow diagram generally illustrating an embodiment of a smart payment system 100 that may determine which of a plurality of user payment accounts to use for each item in a transaction in order to maximize or otherwise optimize user benefits associated with the transaction.
  • aspects of the smart payment system 100 as represented in the data flow diagram may generally indicate an application of the system for transactions taking place in physical retailers, it is contemplated that, in some embodiments, at least certain aspects of the system 100 may occur alternatively in an online retailer environment. Those aspects should be clear to those skilled in the art upon reviewing this disclosure.
  • a transaction may be initiated, at 102, when one or more purchase items are scanned at a checkout counter or otherwise registered by a smart billing machine 71 , such as in an electronic shopping cart, etc..
  • the purchase items may be scanned using a barcode scanning, radio frequency identification (RFID), manual entry, or any other suitable method of registering an item for purchase.
  • the purchase items may be selected in an online retail space.
  • the smart billing machine 71 may be associated with a unique beacon identifier (beacon ID) that may be used to identify a particular smart billing machine.
  • the smart billing machine 71 or a component connected to the smart billing machine, may transmit the beacon ID to a user computing device 55.
  • the beacon ID may be transmitted over wire or wirelessly, using any suitable wireless transmission protocol; for example, Wi-Fi (802.11 standard), Bluetooth, cellular communication or near field communication (NFC), RFID, etc.
  • the smart billing machine 71 may broadcast an NFC or other wireless signal substantially continuously. In some embodiments, the smart billing machine 71 may begin broadcasting the beacon ID when purchase items are being scanned or otherwise registered by the smart billing machine.
  • the user computing device 55 may receive the beacon ID. More specifically, in some embodiments, a smart wallet application running on the user computing device 55 may receive the beacon ID and store it, at least temporarily, as the beacon ID associated with a current transaction for which the purchase items may be scanned. In some embodiments, upon receiving the beacon ID from the smart billing machine 71 , the user computing device 55, via the smart wallet application, may present the user with the option of proceeding with payment using the smart payment system or using a manual payment system. If the user selects payment using a manual payment system, the transaction may proceed by requesting, from the user, which payment account to use for the entire transaction or for each individual purchase item. If the user chooses to proceed using the smart payment system, however, the smart payment system may proceed as described herein. It is contemplated that, in some embodiments, the user computing device may not request a selection by the user before proceeding, or that a user may predetermine whether to be asked for a selection for subsequent transactions during setup of the system 100 or application enrollment.
  • the user computing device 55 may transmit, using the smart wallet application, the beacon ID and a user identifier (user ID) associated with the smart wallet application to a smart payment server 65.
  • the user ID may be any type of identifying information associated with a particular user’s smart payment accounts, or information that may identify the particular user’s account.
  • a user may have a user ID associated with the smart wallet account, and one or more payment accounts associated with the smart wallet account that may be accessible using the smart payment application, via the user computing device 55 or otherwise.
  • the user may have previously provided the smart wallet application with any required user credentials (e.g., user ID and/or password) or provided permission to conduct transactions using those payment accounts through an access token system or other suitable methods known to those skilled in the art.
  • the user ID and the beacon ID may be transmitted to the smart payment server 65 over a digital communication network, such as the digital communication network 60 described with reference to Fig. 4.
  • the smart billing machine 71 may transmit the same beacon ID and purchase item information about the purchase items scanned for the transaction to the smart payment server 65 over the digital communication network.
  • the smart payment server 65 may receive, from the user computing device 55, a user ID for the user’s smart wallet account and the beacon ID of the smart billing machine 71 associated with a particular transaction. Likewise, the smart payment server 65 may receive, from the smart billing machine 71 , purchase item information reflecting the products or services being purchased in the transaction, and the same beacon ID of the smart billing machine that was received from the user computing device 55. Thus, based on the determination that the beacon ID received from the user computing device 55 matches the beacon ID received from the smart billing machine 71 , the smart payment server 65 may associate the received user ID and associated smart wallet account with the purchase item information provided by the smart billing machine.
  • the smart payment server 65 may, at 110, transmit a request for benefit information to a payment server, such as the payment server 70 shown in Fig. 1.
  • the request for benefit information may include may include requesting that the payment server 70 determine any benefits available to the user through any of the one or more payment accounts associated with the user’s smart wallet account or any benefits provided by the merchant or merchants, either generally or based on the particular item being purchased.
  • a user may have a first payment account and a second payment account associated with the user’s smart wallet account, and may additionally have a first merchant account and a second merchant account.
  • the payment accounts may be credit card accounts, debit accounts, bank accounts, or any other suitable payment account.
  • the merchant accounts may be loyalty or frequent buyer programs through a particular merchant retailer or brand.
  • the request for benefit information may additionally check with each underlying merchant for each purchase item to determine whether any benefits may be accrued to the user for any particular combination of payment account with a particular purchase item.
  • an issuer of the first payment account may be offering a benefit particularly for purchases of a particular brand, or a particular product brand may be offering a discount or rebate for purchases made using a particular type of payment or payment account.
  • an issuer of the first payment account may offer benefits based on a first category of purchases, and the second payment account may offer benefits based on a second category of purchases. It should be understood that the combinations of payment account benefits, merchant benefits, or brand benefits may be large in number.
  • the payment server 70 may be one in the same as the smart payment server 65, or the smart payment server may be included within the payment server.
  • the payment server may request and receive, at 112 and 114, benefit information from one or more issuer servers 85a, 85b via, in some embodiments, a payment network such as the payment network 75 referenced in Fig. 1.
  • a first issuer server 85a may be associated with a first payment account offering first payment account benefits
  • a second issuer server 85b may be associated with a second payment account offering second payment account benefits.
  • the payment server 70 may similarly request and receive benefit information from one or more merchant servers 90a, 90b.
  • a first merchant server 90a may be associated with a first merchant and a second merchant server 90b may be associated with a second merchant.
  • the first merchant server 90a may provide benefits related to card-based merchant offers
  • the second merchant server 90b may provide benefits relating to gifts or other prepared offers from the merchant or issuer.
  • the benefit information for each payment account or merchant may have been cached prior to the request.
  • the payment server 70 may respond to the request without retrieving additional benefit information.
  • the payment server 70 may transmit the retrieved benefit information to the smart payment server in response to the request for benefit information.
  • the benefit information may be transmitted as a whole for the entire transaction, or in some embodiments, the payment server 70 may transmit the benefit information in multiple transmissions separated by issuer, merchant, purchase product, etc.
  • the smart payment server 65 may determine the optimal combination of payment accounts or other purchasing offers (e.g., gift cards or merchant credit) for the user to maximize overall user benefits.
  • the optimal combination of benefits may be determined based on algorithms or other methods to maximize the user’s desired benefit.
  • the smart payment system 100 may maximize the discounts, cash back, rebates, etc., that are available in order to save the user as much money as possible.
  • maximizing the overall benefit may include minimizing the cost of the particular transaction.
  • the overall benefit may be determined by comparing a benefit provided by a first payment account for a particular purchase item to a benefit provided by a second purchase account for the same purchase item, and repeating this process for each purchase item and for each payment account.
  • the payment account plan may be determined by individually assigning each purchase item to one of the one or more payment accounts based on which payment account may provide the best benefit. In some embodiments, however, it is contemplated that some payment accounts may offer bulk benefits for purchasing a minimum number of purchase items or if the sum of prices for a group of purchase items exceeds some minimum threshold price.
  • the overall benefit to a user may be greater by taking advantage of such bulk benefits even though the benefits for a particular one of the purchase items in the bulk purchase group may be higher for a different payment account. It is contemplated that the smart payment system 100 would take such scenarios into account when determining the payment account plan that will provide the maximum benefit to the user.
  • the smart payment system 100 may provide users with options for how to optimize benefits. For example, a user may instruct the smart payment system 100 to save as much money as possible, as described above. Alternatively, the user may choose to maximize points for a particular payment account, for example frequent flyer miles or hotel chain points. Alternatively, the user may choose to find a balance between various types of benefits, providing a rank or weight to each benefit type or category. In such embodiments, the algorithm for determining an optimal payment account plan may differ. In some embodiments, a user may select the type or types of benefits to optimize using the smart wallet application run on the user’s user payment device 55, for example. In some embodiments, the user may provide which benefit(s) to optimize upon setting up the smart payment account.
  • the smart payment server 65 may determine multiple payment account plans that may optimize different benefits, and provide the user with an option to select which plan to use for a given transaction. In other embodiments, a user may select which benefits to optimize at the onset of a transaction, for example, when the user computing device 55 receives the beacon ID from the smart billing machine 71. [0047] Regardless of which benefits are to be optimized, the smart payment server 65 may determine a payment account plan based on the available benefits. The payment account plan may include which payment accounts or other resources (e.g., gift cards or merchant credit) to use for which particular purchase items in the transaction, or for which categories of purchase items.
  • the payment account plan may include which payment accounts or other resources (e.g., gift cards or merchant credit) to use for which particular purchase items in the transaction, or for which categories of purchase items.
  • the payment account plan may include dividing the purchase items into groups of transactions, or determining the sequence of transactions that may result in the optimum benefits.
  • the smart payment server 65 may transmit the payment account plan to the user computing device 55.
  • the user computing device 55 via the smart wallet application in some embodiments, present the one or more payment accounts to the smart POS device 69 or the smart billing machine 71 in the order determined by the smart payment server 65 to complete the transaction.
  • the smart payment server 65 may also transmit the payment account plan to the smart billing machine 71.
  • the smart billing machine 71 may organize the payment authorizations expected from the user computing device 55 based on the payment account plan.
  • the smart billing machine 71 may transmit the payment account plan to the smart POS device 69 to organize authorizations expected from the user computing device 55.
  • the smart POS device 69 may broadcasting NFC signals and prepare for accepting one or more payment account authorizations according to that plan.
  • payment account plan may be transmitted to only one of the user computing device 55 or the smart billing machine 71 (or smart POS device 69).
  • the smart wallet application may generate a notification on the user computing device 55 to request purchase approval for the payment account plan determined by the smart payment server 65.
  • the smart wallet application may proceed with completing the transaction without further input from the user.
  • the user may predetermine whether the smart wallet application will request purchase approval or not prior to completing the purchase.
  • a transaction may be made purchasing multiple products or services using multiple payments accounts that optimizes user benefits through a single input or selection by the user through the user computing device 55.
  • the smart wallet application may provide a notification on the user computing device 55 once the transaction is complete. The notification may provide the details of which payment accounts were used to purchase each purchase item, and a summary of the benefits that were accrued based on the transaction.
  • Fig. 5 illustrates an embodiment of a signal flow diagram 200 for using the smart payment system.
  • the smart billing machine 71 may receive one or more purchase items, which may be products or services, or other transaction items.
  • the smart billing machine 71 may transmit a beacon ID particular to the smart billing machine and purchase item information for the purchase items (received at 202) to the smart payment server 65.
  • the smart payment server may receive the beacon ID and the purchase item information.
  • the smart billing machine 71 may also transmit the beacon ID to the user computing device 55, which may receive the beacon ID at 210.
  • the user computing device 55 may transmit the beacon ID and a user ID associated with a user’s smart wallet account to the smart payment server 65, which may receive them at 214.
  • the smart payment server 65 may match the beacon ID received from the smart billing machine 71 and the beacon ID received from the user computing device 55. Based on the matching beacon IDs, at 216, the smart payment server may determine the payment account issuers or providers and/or merchants included in the transaction based on the payment accounts or merchant accounts associated with the smart wallet account matching the provided user ID and/or the merchant, brands, or retailers included in the purchase item information.
  • the smart payment server 65 may transmit a request for benefit information for the one or more payment accounts or merchants identified in 216 to the payment server 70, which may receive the request at 220.
  • the payment server 70 may transmit a request for benefit information from one or more issuer servers 85a, 85b associated with one or more payment accounts included in the user’s smart wallet account and one or more merchant servers 85a, 85b associated with the smart wallet account or with the particular transaction information.
  • Each issuer server 85a, 85b may receive the request for benefit information at 228 and transmit the benefit information associated with the particular issuer payment account back to the payment server 70 at 230.
  • each merchant server 90a, 90b may receive the request for benefit information at 224 and transmit the benefit information associated with the particular merchant back to the payment server 70 at 226.
  • the payment server 70 may receive the benefit information from the one or more issuer servers 85a, 85b and the one or more merchant servers 85a 85b at 232.
  • the payment server 70 may transmit the received benefit information, either one at a time or all at once, to the smart payment server 65, which may receive the benefit information at 236.
  • the smart payment server 65 may process the benefit information based on one or more benefit optimization algorithms to determine a payment account plan that may provide the maximum benefit to the user. As described above, the maximum benefit may be providing the user with as much money as possible, or may include maximizing other benefits such as loyalty points, frequent flyer miles, cash back, rebates, coupon offerings, etc.
  • the smart payment server may transmit the payment account plan to the user computing device 55 at 240, and the user computing device may receive the payment account plan at 242.
  • the smart payment server 65 may also transmit the payment account plan to the smart billing machine 71 to prepare to receive the particular order of authorizations detailed in the payment account plan.
  • the user computing device 55 may present the payment accounts from the payment account plan to the smart billing machine 71 or an associated smart POS device.
  • the user computing device may present the payment account authorizations all at once to the smart billing machine 71 , or may present each payment account authorization one by one, moving on to subsequent payment account authorizations once the previous authorization has been accepted by the smart billing machine.
  • the smart billing machine 71 may process the payment provided through the one or more accounts associated with the user’s smart wallet account.
  • the smart wallet application may request approval from the user to complete the transaction according to the account payment plan prior to executing the one or more authorizations. In other embodiments, the smart wallet application may execute the planned authorizations and transactions automatically.
  • Figs. 6A and 6B illustrate example embodiments of a graphical user interface (GUI) 300 that may be provided on a user computing device 55 through an embodiment of the smart payment application.
  • GUI graphical user interface
  • the GUI 300 may include an alert banner 302 notifying the user that a beacon ID from a smart billing machine, such as smart billing machine 71 , has been received and detected by the user computing device 55.
  • the GUI 300 may also include an inquiry banner 304, and response buttons 306, 308.
  • the inquiry banner 304 may ask the user whether the user would like to use the smart payment system or manual payment selection for the current transaction.
  • the smart payment application may provide options for the user to select which payment account or accounts included in the user’s smart payment account to use for the transaction. If the user selects the smart payment system response button 306, the smart payment application may proceed to execute the smart payment system as described with reference to Figs. 4 and 5, for example.
  • the GUI 300 may show a smart payment transaction summary 310.
  • the smart payment transaction summary 310 may include an account summary 312 and a benefits summary 314.
  • the account summary 312 may show the breakdown of how the smart payment system divided the purchase items amongst the user’s payment accounts. For example, in Fig.
  • the smart payment system used Account A to purchase Items 1 -3, Account B to purchase Items 4-6, Account C to purchase Items 7-9, and Account D to purchase Items 10-12 because the system may have determined that such a distribution was optimal for the transaction.
  • the benefits summary 314 may include a summary of the benefits earned by each account based on the current transaction, and the total benefit received as a result of the particular account distribution. In the example shown, Account A earned $5, Account B earned $3, Account C earned $4, and Account D earned $5, for a total benefit of $17.
  • the benefits may be quantified differently or be distributed in any number of ways.
  • the user may prefer or the smart payment application may default to quantifying benefits in terms of loyalty points or some other denomination of benefits.
  • the benefits awarded through a first payment account program and a second payment account program may not be directly comparable.
  • the user may include pre-determ ined weighting to compare the benefits from each payment account or merchant account.
  • one type of payment account may offer benefits as cash back, while another type of payment account may offer loyalty points or frequent flyer miles, for instance.
  • the user may determine and select how to weigh the cash back versus the loyalty points depending on the payment account.
  • the smart payment application may include a default weighting in order to compare benefits for payment accounts including different benefit denominations.
  • Fig. 7 is a flow chart of an embodiment of a method of using the smart payment system.
  • a server such as smart payment server 65 or payment server 70, may receive a user ID from a user computing device such as user computing device 55.
  • the user computing device 55 may be running a smart payment application that transmits the user ID.
  • the user ID may be associated with a smart payment account of a user, and the user may select one or more payment accounts for association with the smart payment account.
  • Payment account information may be received for the one or more payment accounts of the user.
  • the payment accounts may be tokenized for use by the smart payment system.
  • the smart payment server 65 may store the user ID and payment account information in a database, such as database 1525 referred to in Fig. 3, so as to associate the user ID and the one or more payment accounts with one another.
  • the smart payment server may receive a beacon ID and user ID from a user computing device.
  • the beacon ID may be associated with a smart billing machine, such as smart billing machine 71.
  • the beacon ID may have been transmitted (wirelessly or otherwise) by the smart billing machine 71 (e.g., via an associated smart POS device 69), received by the user computing device 55, and then transmitted from the user computing device to the smart payment server 65 via a digital communication network.
  • the smart payment server 65 may receive a beacon ID and purchase item information from a smart billing machine 71.
  • the purchase item information may be information related to items being purchased in a transaction that have been scanned or otherwise entered into the smart billing machine
  • the beacon ID may be associated with the smart billing machine 71.
  • the smart payment server 65 may determine whether the beacon ID received at 406 from the user computing device matches the beacon ID received at 408 from the smart billing machine 71. If both beacon IDs match, the smart payment server 65 may determine that the purchase item information received from smart billing machine 71 is associated with purchase items in a transaction being initiated by the user associated with the received user ID and payment accounts. Accordingly, at 412, the smart payment server 65 may identify the one or more payment accounts associated with the received user ID and, in some embodiments, the merchant or brands associated with the purchase items. For example, the smart payment server 65 may identify that one or more of the purchase items are being sold by a first merchant, or that the type of product being purchased is branded or otherwise sold by a second merchant.
  • the payment server may, at 414, transmit one or more requests for benefit information associated with the identified payment accounts or merchants.
  • the user’s smart payment account may include a first payment account associated with a first issuer having a first issuer server, and a second payment account associated with a second issuer server.
  • the smart payment server 65 may transmit a request for benefit information related to the first payment account to the first issuer server, and transmit a request for benefit information related to the second payment account to the second issuer server.
  • fewer or more payment accounts with associated issuer servers may be used in other embodiments.
  • the payment account may include loyalty or other merchant accounts for the merchant at which the transaction may be being made.
  • the smart payment server may transmit a request for benefits associated with the merchant account.
  • the user payment account may include a gift card or other such merchandise credit for the particular merchant with which the transaction is taking place.
  • the smart payment server may transmit a benefit request to the merchant server or another server that may store data related to gift card or other merchandise credit accounts.
  • a payment server such as payment server 70 may transmit requests to each issuer or merchant server at the request of the smart payment server, but the smart payment server may transmit the benefit information requests itself in other embodiments.
  • the smart payment server may receive the requested benefit information from the issuer servers, merchant servers, or other requested locations.
  • the smart payment server 65 may analyze the benefit information related to each of the payment accounts and in view of the purchase items and other merchant benefit available to determine a payment account plan for the particular transaction that may optimize the benefit to the user. For example, in some embodiments, a first payment account may include the highest overall cash-back benefit of all the available payment accounts, but a second payment account may include a relatively higher cash-back benefit for a first particular purchase item. Further, a second particular purchase item may be eligible for a rebate through the merchant or manufacturer if a merchant account is used.
  • the smart payment server 65 may determine the payment account plan for such an exemplary transaction to include using the second payment account to purchase the first particular purchase item, the merchant account to purchase the second particular purchase item, and the first payment account to purchase any remaining purchase items. It should be understood, however, that in other embodiments, many other combinations of payment accounts and purchase items may result in a more beneficial payment account plan.
  • the smart payment server may transmit the payment account plan to the user computing device 55, and may transmit the payment account plan to the smart billing machine 71 at 422.
  • the user computing device 55 through the smart payment application, may communicate with the smart billing machine 71 , or a smart POS device 69 associated with the smart billing machine, to execute the transaction according to the payment account plan, thus automatically optimizing the benefits to the user through the smart payment system.
  • the smart payment server 65 determine payment account plans based on benefit information that has been received by the smart payment server prior to any particular transaction. The smart payment server 65 may then pre-determ ine a hierarchy of payment accounts to be used for the purchases of products or services in one or more product categories.
  • Figure 8 is a flow chart of one such embodiment of a method 500 of using the smart payment system.
  • a server such as the smart payment server 65 or payment server 70 may receive and store a user ID and payment account info in a similar manner as described above with reference to method 400 shown in Figure 7.
  • the smart payment server 65 may identify one or more payment accounts received by the user and associated with the user ID received from, for example, a user computing device.
  • the one or more payment accounts may be associated with one or more issuers, merchants, or other entities.
  • the smart payment server may transmit a request for benefit information to the one or more issues, merchants, or other entities associated with the one or more payment accounts, and receive the benefit information in return.
  • request for benefit information may occur periodically so that the smart payment server 65 may include updated benefit information.
  • the individual issuers and/or merchants may push updated benefit information to the smart payment server 65 when the updates occur or on a periodic basis.
  • the smart payment server 65 may determine product categories for each of the one or more payment accounts based on the benefit information associated with each payment account. For example, a first payment account may provide 5% cash back for all purchases in a first category, (e.g., gasoline purchases), while a second payment account may offer 7% cash back for purchases in a second category (e.g., grocery purchases). A third payment account may offer 3% cash back on all purchases regardless of category.
  • a first payment account may provide 5% cash back for all purchases in a first category, (e.g., gasoline purchases)
  • a second payment account may offer 7% cash back for purchases in a second category (e.g., grocery purchases).
  • a third payment account may offer 3% cash back on all purchases regardless of category.
  • the smart payment server 65 may receive a beacon ID and user ID from a user computing device 55 in a similar manner as received at 406 in Figure 7.
  • the beacon ID may be associated with a smart billing machine 71 , and may have been previously transmitted to the user computing device 55 during, for example, a checkout process in a store.
  • the smart payment server 65 may also receive a beacon ID and purchase item information from a smart billing machine 71 that has received the purchase item information during a scanning of products to be purchased by a user in a transaction.
  • the smart payment server 65 may determine whether the beacon ID received at 510 from the user computing device matches the beacon ID received at 512 from the smart billing machine 71.
  • the smart payment server 65 may determine that the purchase item information received from smart billing machine 71 is associated with purchase items in a transaction being initiated by the user associated with the received user ID and payment accounts. Accordingly, in some embodiments, the smart payment server 65 may identify the one or more payment accounts associated with the received user ID.
  • the smart payment server 65 may identify one or more product categories for the purchase items.
  • the product categories may be included within the purchase item information received from the smart billing machine 71.
  • the product categories may be stored in a database accessible to the smart payment server 65.
  • one or more purchase items may not fall within any particular product category and may be categorized as“unknown” or“miscellaneous,” for example.
  • the smart payment server 65 may determine whether a particular purchase item falls within a first product category, for example, a gasoline purchase.
  • the smart payment server 65 may proceed with the purchase of the that purchase item using the first payment account, at 520, based on the predetermination that gasoline purchases (first product category) should be assigned to the first payment account to achieve optimal benefits. It should be understood that proceeding with the purchase of the particular purchase item using the first payment account may mean that the smart payment server 65 assigns the first payment account to the particular purchase item in a payment account plan, such as that referred to and described at 418 of Figure 7. If the purchase item is not included in the first product category, then the smart payment server 65 may, at 522, determine whether a particular purchase item falls within a second product category, for example a grocery purchase.
  • a second product category for example a grocery purchase.
  • the smart payment server 65 may proceed to associate the purchase item with the second payment account in the payment account plan based on the previous determination that using the second payment account for grocery purchases may result in optimal benefits. If the purchase item does not fall within the second product category, at 526, the smart payment server may assign the purchase item to be purchased using the third payment account, for example, because of the predetermination that the third payment account is optimal for purchase items that do not fall within the first or second product categories.
  • the steps of identifying whether a particular purchase item falls within a particular product category may repeat for as many purchase items in a particular transaction, such that each purchase item may be categorized into a product category or deemed to have an unknown product category.
  • the smart payment server 65 may transmit the payment account plan to one or both of the user computing device 55 and the smart billing machine 71 for completion of the transaction.
  • Fig. 9 shows an embodiment of a transaction data flow 600 that may be implemented in the smart payment system 100, particularly in embodiments of the system that may provide options for a“single tap” for multiple transactions.
  • a user may initiate the smart payment system using the smart payment application running on the user computing device 55 merely by making a selection to use the smart payment system to complete a purchase (e.g., by selecting smart payment system 306 in the user interface shown in Fig. 6A).
  • the single selection to use the smart payment system may, in some embodiments, result in multiple transactions using multiple payment accounts for different purchase items.
  • FIG. 9 an example data flow 600 between a smart billing machine 71 and a user computing device 55 is shown.
  • the smart billing machine 71 may conduct preprocessing prior to enabling a contactless interface between the smart billing machine and a user computing device.
  • contactless interfacing may be enable at this point.
  • discovery processing occur, and the user computing device 55 may be presented for payment at 605.
  • presentment for payment may include the user computing device 55 moving within NFC or Bluetooth range of the smart billing machine 71 (or associated smart POS device 69).
  • the smart billing machine 71 or smart POS device 69 may undergo an application selection process that may include selecting a proximity payment system environment (PPSE) command at 608.
  • the user computing device 55 may accept an application from the smart billing machine 71 , for example, the application “2PAY.SYS.DDF01 ,” but other applications may be used in other embodiments.
  • the user computing device 55 may response back with file control information (FCI) data that includes a list of application identifications (AIDS) for each payment account included in the smart wallet account for the particular user initiating the transaction.
  • FCI file control information
  • the smart billing machine 71 or smart POS device 69 may accept the list of AIDS for each payment account and may select one AID for each payment account and, at 612, confirm the selection back to the user computing device 55.
  • PDOL multi/single processing options data object list
  • SW1 SW2 ‘9000’
  • the data status may be different and the smart billing machine 71 or smart POS device 69 may repeat the process with a different AID.
  • the smart billing machine 71 or smart POS device 69 may proceed with initiating application processing, and may, at 616, respond back to the user computing device 55 with GET processing options (GPO) commands including a command template for each payment account
  • GPO GET processing options
  • the user computing device 55 may, at 618, process data element in the GPO command and respond back to the smart billing machine 71 or smart POS device 69 with personalization data for each payment account. In some embodiments, this may include determining path, performing account action analysis, performing any cryptography (e.g., tokenization), and returning application data.
  • the smart billing machine 71 or smart POS device 69 may read the application data and respond back to the user computing device 55 with read record command at 622.
  • the user computing device 55 may then, at 624, respond back to the smart billing machine 71 or smart POS device 69 by providing application records and/or additional data (e.g., Track2 data, etc.) for each payment account.
  • additional data e.g., Track2 data, etc.
  • the user computing device 55 may be removed from NFC or RFID range, and the account read may be complete at 626.
  • processing restrictions may be implemented.
  • the various participants and elements described herein may operate one or more computer apparatuses to facilitate the functions described herein. Any of the elements in the above-described Figures, including any servers, user terminals, or databases, may use any suitable number of subsystems to facilitate the functions described herein.
  • Any of the software components or functions described in this application may be implemented as software code or computer readable instructions that may be executed by at least one processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques.
  • the at least one processor may be specifically programmed.
  • the software code may be stored as a series of instructions, or commands on a non-transitory computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • a non-transitory computer readable medium such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • RAM random access memory
  • ROM read only memory
  • magnetic medium such as a hard-drive or a floppy disk
  • optical medium such as a CD-ROM.
  • One or more of the elements of the present system may be claimed as means for accomplishing a particular function. Where such means-plus-function elements are used to describe certain elements of a claimed system it will be understood by those of ordinary skill in the art having the present specification, figures and claims before them, that the corresponding structure is a general purpose computer, processor, or microprocessor (as the case may be) programmed (or physically configured) to perform the particularly recited function using functionality found in any general purpose computer without special programming and/or by implementing one or more algorithms to achieve the recited functionality.
  • the present disclosure provides a solution to the long-felt need described above.
  • the system and the methods described herein may be configured to efficiently provide substantially real-time or automatically approvable payment selection to maximize the benefits for a user.
  • Further advantages and modifications of the above described system and method will readily occur to those skilled in the art.
  • the disclosure in its broader aspects, is therefore not limited to the specific details, representative system and methods, and illustrative examples shown and described above.
  • Various modifications and variations can be made to the above specification without departing from the scope or spirit of the present disclosure, and it is intended that the present disclosure covers all such modifications and variations provided they come within the scope of the following claims and their equivalents.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention concerne un procédé implémenté par processeur pour une sélection de paiement, ledit procédé comprenant la réception d'un identifiant d'utilisateur et d'un identifiant de balise en provenance d'un dispositif informatique d'utilisateur, et la réception de l'identifiant de balise et des informations d'article d'achat à partir d'une machine de facturation intelligente associée à l'ID de balise dans une transaction. Le procédé comprend l'identification des comptes de paiement d'utilisateur de l'utilisateur et la détermination d'informations de bénéfice pour chacun des comptes de paiement. Le procédé comprend la détermination d'un plan de compte de paiement qui comprend l'attribution de chacun du ou des articles d'achat à un des comptes de paiement d'utilisateur et la transmission du plan de compte de paiement au dispositif informatique d'utilisateur de façon à permettre au dispositif informatique d'utilisateur de compléter la transaction sur la base du plan de compte de paiement.
PCT/US2019/012370 2019-01-04 2019-01-04 Systèmes et procédés de paiement intelligent WO2020142105A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2019/012370 WO2020142105A1 (fr) 2019-01-04 2019-01-04 Systèmes et procédés de paiement intelligent

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2019/012370 WO2020142105A1 (fr) 2019-01-04 2019-01-04 Systèmes et procédés de paiement intelligent

Publications (1)

Publication Number Publication Date
WO2020142105A1 true WO2020142105A1 (fr) 2020-07-09

Family

ID=71406669

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/012370 WO2020142105A1 (fr) 2019-01-04 2019-01-04 Systèmes et procédés de paiement intelligent

Country Status (1)

Country Link
WO (1) WO2020142105A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110060629A1 (en) * 2009-09-10 2011-03-10 Jeanette Marie Yoder Third party merchant-funded rewards accrual and redemption network
US20110218849A1 (en) * 2010-03-03 2011-09-08 Rutigliano John R Cloud platform for multiple account management & automated transaction processing
US20130117094A1 (en) * 2011-11-04 2013-05-09 Megan Jones Automated System for Optimizing Retail Savings Using Coupons
US20130204728A1 (en) * 2012-02-07 2013-08-08 David Aaron Lichterman Intelligent Meta-Payment System
US8622308B1 (en) * 2007-12-31 2014-01-07 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
US20140304057A1 (en) * 2008-04-16 2014-10-09 Visa U.S.A. Inc. Loyalty rewards optimization bill payables and receivables service
US20170178095A1 (en) * 2013-07-08 2017-06-22 Mastercard International Incorporated Intelligent advice and payment routing engine

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8622308B1 (en) * 2007-12-31 2014-01-07 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
US20140304057A1 (en) * 2008-04-16 2014-10-09 Visa U.S.A. Inc. Loyalty rewards optimization bill payables and receivables service
US20110060629A1 (en) * 2009-09-10 2011-03-10 Jeanette Marie Yoder Third party merchant-funded rewards accrual and redemption network
US20110218849A1 (en) * 2010-03-03 2011-09-08 Rutigliano John R Cloud platform for multiple account management & automated transaction processing
US20130117094A1 (en) * 2011-11-04 2013-05-09 Megan Jones Automated System for Optimizing Retail Savings Using Coupons
US20130204728A1 (en) * 2012-02-07 2013-08-08 David Aaron Lichterman Intelligent Meta-Payment System
US20170178095A1 (en) * 2013-07-08 2017-06-22 Mastercard International Incorporated Intelligent advice and payment routing engine

Similar Documents

Publication Publication Date Title
US10885515B1 (en) System and method for canceling a payment after initiating the payment using a proxy card
US9224141B1 (en) Encoding a magnetic stripe of a card with data of multiple cards
AU2008316696B2 (en) Device including multiple payment applications
US20170178095A1 (en) Intelligent advice and payment routing engine
US11599863B1 (en) Selection of a financial account associated with a proxy object
US20140207680A1 (en) System and method for providing a mobile wallet shopping companion application
US11238418B2 (en) Using incentives at transaction devices
US11238426B1 (en) Associating an account with a card
JP6300382B2 (ja) カード決済システム、カード決済管理サーバ、カード決済プログラム及びカード決済方法
KR20190041539A (ko) 전자 지갑을 통한 결제 시스템
US11948139B2 (en) System and method for auctioning a first-in-wallet payment account status
AU2019283828B2 (en) NFC mobile wallet processing systems and methods
WO2013120007A1 (fr) Utilisation de barres de carte de crédit/bancaires pour accéder au compte d'un utilisateur à un point de vente (pos)
EP3210135B1 (fr) Systèmes et procédés destinés à mettre en oeuvre une opération dans un système informatique connecté à une pluralité de systèmes informatiques par le biais d'un réseau d'ordinateurs au moyen de la communication en boucle d'un identificateur de l'opération
US20170352095A1 (en) Portfolio optimized offers for mobile device
US11526882B2 (en) Cryptocurrency rewards for a virtual cash card
CN111226247A (zh) 用于动态应用程序选择的系统、方法和计算机程序产品
WO2020142105A1 (fr) Systèmes et procédés de paiement intelligent
US20190095884A1 (en) Electronic system and method for facilitating payment of a transaction
US20200082429A1 (en) Payment selection systems and methods
US20240119449A1 (en) Rewards for a virtual cash card
US20140200982A1 (en) Dynamic Beneficiary System
CA3200021A1 (fr) Recompenses en cryptomonnaie pour carte de paiement virtuelle

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19907686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19907686

Country of ref document: EP

Kind code of ref document: A1