WO2013149200A1 - Génération de code à barres mobile et paiement - Google Patents

Génération de code à barres mobile et paiement Download PDF

Info

Publication number
WO2013149200A1
WO2013149200A1 PCT/US2013/034704 US2013034704W WO2013149200A1 WO 2013149200 A1 WO2013149200 A1 WO 2013149200A1 US 2013034704 W US2013034704 W US 2013034704W WO 2013149200 A1 WO2013149200 A1 WO 2013149200A1
Authority
WO
WIPO (PCT)
Prior art keywords
barcode
user
payment
information
merchant
Prior art date
Application number
PCT/US2013/034704
Other languages
English (en)
Inventor
Catherine A. Wong
Original Assignee
Ebay Inc.
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
Priority claimed from US13/433,792 external-priority patent/US8600883B2/en
Application filed by Ebay Inc. filed Critical Ebay Inc.
Priority to CA2907930A priority Critical patent/CA2907930C/fr
Priority to EP13717909.9A priority patent/EP3365852A1/fr
Priority to AU2013237855A priority patent/AU2013237855A1/en
Publication of WO2013149200A1 publication Critical patent/WO2013149200A1/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
    • 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
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device

Definitions

  • the present invention generally relates to facilitating financial transactions and more particularly to facilitating such transactions with a mobile device.
  • Mobile devices such as cell phones
  • mobile phones are being used by more and more people world-wide.
  • consumers can communicate nearly anytime and anywhere to facilitate information access to mobile services and the Internet.
  • Mobile phones have also become multimedia computing platforms with integral digital cameras for taking pictures and video, playing music, recording conversations, and organizing and planning activities and appointments.
  • on-line payment service providers such as PayPal, Inc. of San Jose, CA.
  • on-line payment provider may use an on-line payment provider to transfer money and receive money over electronic networks, such as the Internet.
  • the money transfer may be for payment of goods or services.
  • the payment providers supply an infra-structure, software, and services that enable users to make and receive payments.
  • Mobile phone users may contract with a payment provider to allow the user to make payments over the phone. Typically, this requires the user to open up an application on the phone, such as through a web browser.
  • the user accesses his or her on-line account by entering requested information, such as a user name, phone number, email, and/or password.
  • Payment information can then be entered and transmitted to the payment provider, who then transfers funds from the user's account to the payee's account.
  • a confirmation may then be sent to the payer and/or the payee.
  • an application on a mobile device having a screen enables the user to generate a barcode on the screen, which can be scanned for payment.
  • the barcode is valid for a limited period of time (e.g., one minute) and for a single use.
  • payment is transferred from the user's account to the merchant's account.
  • the user first opens up the application on the phone, which then presents the user with a screen showing a phone number associated with the user and a field for the user to enter a password or PIN. After entering a correct password or PIN, a barcode is generated and appears on the screen.
  • the barcode is generated through a payment provider, such as PayPal.
  • a scanner such as a CCD scanner, scans the barcode at the point of sale (POS) or other physical payment location. Funds are deducted from the user's account and transferred to the retailer's account. The user may be asked for a signature confirmation. A receipt can then be generated on the mobile device, and purchases tracked immediately.
  • POS point of sale
  • a receipt can be displayed on the user's mobile device for performing a refund transaction.
  • the receipt is located on the user's mobile device, using any suitable search, such as by date, recent activity, store, etc.
  • the receipt may have been stored as part of a purchase described above.
  • the receipt in the form of a scannable barcode, is displayed on the user's device.
  • the receipt is then scanned, either by the merchant or user.
  • the returned merchandise can be scanned before or after the receipt is scanned. Once both the returned merchandise and the receipt are scanned, the information is compared to ensure that the receipt matches the returned merchandise. If the refund is approved, the payment provider transfers the appropriate funds from the merchant's account to the user's account.
  • the merchant and/or user may then be given a receipt, either electronically or in printable/paper form.
  • scannable financial products may also be generated, such as a virtual debit/credit card, coupons, and gift cards. If a qualifying purchase provides the user with an instant coupon or rebate, those can be generated as well.
  • the generated barcode contains a mix of funding instruments for the payment transaction.
  • the payment provider retrieves user information as well as location or merchant information and pushes all available funding instruments to the user's digital wallet or phone. Examples of funding instruments include coupons, rebates, gift cards, reward points, etc. Any loyalty or membership information with the merchant can also be pushed to the user's wallet.
  • transaction information may be sent, either by the user device or the merchant, to the payment provider.
  • Transaction information includes details of items to be purchased.
  • the payment provider can then determine which funding instruments are available for the transaction and generates a one-time use barcode (such as QR code) on the user device that includes some or all the funding instruments or sources available.
  • the choice of funding sources can be determined solely by the payment provider, solely by the user, or a combination of both.
  • the merchant then scans the generated barcode for payment A total is presented to the user, with all intended funding sources applied. The user can then approve and complete the purchase. In another embodiment, if any and all restrictions limitations on the barcode are met, the payment may be completed without the user having to authorize. Any loyalty cards can also be conveyed to the merchant for processing any rewards or points to the cards.
  • the user can make a purchase with a barcode that contains multiple funding sources, as well as convey store loyalty card information to the merchant, with a single scan of a barcode by the merchant.
  • a receipt can be generated and stored, as with the embodiment above.
  • FIG. 1 is a flowchart showing steps for a user to make a payment from a mobile phone according to one embodiment
  • FIG. 2A is a flowchart showing steps for a payment provider to enable a user to make a payment from a mobile phone according to one embodiment
  • FIG. 2B is a flowchart showing steps for a merchant to perform a financial transaction from a mobile device according to one embodiment
  • FIG. 2C is a flowchart showing steps to enable a user to obtain a refund from a receipt on a mobile phone according to one embodiment
  • Figs. 3A and 3B show a barcode generated from a mobile phone according to one embodiment
  • FIG. 4 is a system diagram showing various steps performed by different parties to a payment transaction using a mobile device according to one embodiment
  • FIGs. 5 A and 5B are flowcharts showing steps illustrating a user experience and a merchant payment provider experience, respectively for using a barcode for payment according to other embodiments; and [0022] Fig. 6 is a block diagram of one embodiment of a system that can be used to implement one or more components of the system described herein.
  • Fig. 1 is a flowchart 100 showing one embodiment for a user to make a payment from a mobile phone.
  • a user registers with an on-line payment provider, such as PayPal. Registration can be through any suitable means, such as accessing the payment provider site and entering the required information. For example, the user may be asked to create an account if one has not already been established, or if an account is established, to fund the account if needed. The user may then be asked to enter the phone number of the mobile phone and a password or PIN, followed by a confirmation of that password or ⁇ .
  • an application can be installed on the user's registered device, such as a mobile phone.
  • the user When the user is ready to use the service or application, the user opens up the application at step 104, such as by tapping on the application icon on the phone. The user is then presented with a screen showing two fields, a phone number field and a password or PIN field. In one embodiment, the device phone number is already entered. Note that other identifier fields may be used, in any suitable combination, as long as the payment provider is provided sufficient information to authenticate the user.
  • the user enters the PIN (or any other requested identification information). If the PIN and phone number are verified by the payment provider, the user is presented with a screen showing a barcode.
  • step 108 the user presents the barcode image to the merchant This may be at a checkout stand or point of sale (POS) after the user has finished shopping and the items (and/or services) for purchase have been scanned or entered for payment. A total is presented to the user, at which point, the user provides the merchant a form of payment.
  • the user displays the barcode for the merchant to scan.
  • the merchant then scans the barcode for payment.
  • the user may scan the barcode himself, such as by passing the screen through a scanner. Note that a suitable scanner system and type may be required depending on the device showing the barcode.
  • a CCD scanner may be needed to accurately scan a device having a reflective screen, such as on a phone.
  • the user may be given the option, in step 110, of confirming the payment, such as with a signature, checking an "accept" icon, etc.
  • Approval may be in the form of the payment provider transmitting, and the merchant receiving, a text message, such as "Approved," a visual message, such as a green light, a verbal message, such as from a live or automated call to the merchant, or any other suitable indication of approval.
  • Denial of the payment may be indicated in similar ways, such as "Denied,” a red light, etc. Denial of the payment may result from various reasons, such as insufficient funds in the user's account to make the purchase or payment, an error in reading the barcode, or an invalid barcode. If the denial is from an error in reading, the merchant may be notified accordingly and the barcode re-scanned as needed.
  • the barcode may have expired or been used already. If denied, an indication of the reason may be given to the merchant and/or the user so that the reason can be addressed. For example, if the denial is an invalid barcode, the barcode may be scanned again, or a new barcode may be generated for scanning.
  • the barcode generated on the user's phone is valid for only one use (e.g., one confirmed use, where the single use may be from multiple unsuccessful scans and one successful scan) and a specific amount of time.
  • the barcode may only be valid for 30 seconds or one minute after the barcode is generated. This increases security and minimizes misuse or fraudulent use of the barcode.
  • step 112 Assuming the barcode is valid and confirmed, the payment is concluded, and the user is given a receipt at step 112, such as from the merchant terminal in the form of a paper receipt or Short Message Service (SMS) message to the phone.
  • SMS Short Message Service
  • the user may also view a receipt on the phone and manage or otherwise track the purchase through the payment provider. For example, the user may make notes about the purchase for future reference or send the purchase to another application. The user can also check previous transactions and view or cancel pending authorizations. Note that in some embodiments, the user can easily cancel this service completely, such as when the phone is lost. For example, the user can simply log onto the payment provider site, enter information to access the account, and then cancel the service.
  • Another security feature may be that the user is required to first unlock the phone before use. This can be done in various ways, such as biometric scan or entering an ID to unlock the phone. For the latter, the user is then required to enter two passwords or PINS, one for unlocking the phone and one for accessing the application,
  • Fig. 2A is a flowchart 200 showing another embodiment of steps for a payment provider to enable a user to make a payment from a mobile phone.
  • the user registers for service with the payment provider.
  • the payment provider receives and processes information entered by the user to create the application and account if necessary.
  • the information may include a user name, password, financial information, billing address, PIN, security questions and answers, etc. Communication of the information may be by any means, such as through the Internet, Bluetooth, or a wired connection, using suitable components such as antennas and processors.
  • the payment provider installs the appropriate application on the user's device in step 204, which can be done via a web browser.
  • the application may simply be an icon on the user's device screen.
  • the user When the user is ready to use the application or service, the user opens the application and enters requested information as discussed above.
  • the payment provider receives this information to confirm the user in step 206. If the information (e.g., phone number and PIN) does not correspond to a registered user, the payment provider may notify the user accordingly for more chances to login. Once the user is confirmed, the payment provider accesses the user's account at step 208.
  • the payment provider generates a barcode corresponding to the user's account.
  • the barcode can be generated with standard software for display on a screen or terminal, such as through a processor running the software.
  • the barcode may allow access to all the funds in a user's account, only a portion set aside by the user, or be restricted to certain merchants or products/services. For example, a parent may set up an account for a child with limits and restrictions for use.
  • Restrictions may include a maximum amount per transaction or barcode generation, a maximum number of transactions per time period (e.g., week or month), maximum dollar amount of transactions per time period (e.g., week or month), and a pre-determined expiration date of the agreement, such that after expiration, the user can no longer generate the barcodes, unless the user renews the agreement.
  • the barcode may also be for a specific amount, as specified by the user after accessing the application. For example, after access, the user may be given an option of entering the amount, selecting from one of several pre-defined amounts, or using a default amount.
  • Restrictions may also be applied to limit the amount of funds for a particular merchant or potential purchase, such as a stranger at a flea market or from an online want-ad service.
  • the payment provider transmits the barcode to the user device, which displays the barcode on the device. Transmission of the barcode can be by the same or similar means as used to receive information from the user, e.g., antenna, transmitter, or transceiver.
  • the payment provider then waits for information from the merchant or scanner. This information may include the merchant's name, account information, payment amount, etc.
  • the payment provider determines whether the received information will allow the payment provider to make the transfer. As discussed above, information that will make the payment provider deny the payment can include a requested payment exceeding the barcode limit, an expired or already used barcode, a barcode not matching the one for the user, an unrecognized merchant account, etc.
  • the payment provider affects a transfer of funds from the user's account to the merchant's account in step 214, with protocols and software executed by processors such as used by PayPal and other on-line financial institutions.
  • the payment provider may also send a confirmation to both the user and merchant that funds have been transferred. Confirmation may be the same for the user and merchant or different, and may include a text message, a visual indicator, a voice indicator, etc.
  • die payment provider may provide an additional layer of protection for the merchant, e.g., to minimize charge backs and/or obtain proof of user signature or consent.
  • the merchant scans the generated barcode with a scanner, such as described above.
  • the POS software at the merchant location then makes a Do Authorization API call to the payment provider to authorize the payment.
  • the payment provider determines whether the scanned information is consistent with the payment provider information for the user and responds with an authorization or decline to the merchant. If authorized, the merchant can then display the amount for the user to authorize. This can be on an electronic signature pad for the user to sign or just an OK button for the user to press.
  • the POS software then makes a DoCapture API call to the payment provider to capture the payment. The payment provider will then respond with an API response to indicate whether the funds were transferred successfully. If so, the merchant prints a receipt for the user.
  • Fig. 2B is a flowchart 230 showing steps performed by a merchant for performing a financial transaction using a mobile device displaying a barcode, according to one embodiment
  • a user of a mobile device desires to make a financial transaction with the merchant (or anyone else)
  • the user generates and displays a barcode on the mobile device described above. This may be when the user has completed shopping is ready to check out or pay for the items at the register or point of sale.
  • the merchant records the items for purchase and the total amount owed by the purchaser, such as scanning the items for both a description and price.
  • the merchant is presented with a barcode displayed on the user's or purchaser's mobile device, such as a phone.
  • the barcode is then scanned, at step 236, either by the merchant or by the user (such as with a merchant scanner). Again, depending on the display/screen of the user device, an appropriate scanner is needed to accurately read the barcode, such as a CCD scanner.
  • the barcode information and the purchase information are transmitted to the payment provider at step 238, which is processed by the payment provider.
  • the merchant receives a notification that the payment has been accepted or denied, at step 240. If denied, the merchant can inform the user at step 242, and the user can respond accordingly. Options include scanning the barcode again, generating a new barcode, or presenting the merchant with a new form of payment. If accepted, the merchant may receive a confirmation of the transaction at step 244. As a result, funds are transferred from the user's account to the merchant's account for the purchase of the desired item(s).
  • Fig. 2C is a flowchart 2S0 showing an embodiment for a user to retrieve a receipt on a mobile phone and use that for a refund at a POS.
  • the user may want to return the purchase for a refund.
  • the user locates the receipt on the user's mobile phone or device.
  • the receipt may have been stored as part of the initial purchase, as described above.
  • Retrieval of the receipt may include the application having a search menu that allows the user to locate a transaction by the merchant, dollar amount, date, or other category.
  • the user can select the desired transaction to view details, such as item and receipt.
  • the barcode receipt is shown on the display of the mobile device in step 254.
  • a button could be added to the transaction detail page to display the merchant's order D or invoice ID (represented by the barcode).
  • the barcode receipt may also be displayed or generated in any other suitable manner, such as being captured and stored as a barcode during the purchasing process.
  • the merchant scans the barcode, as part of the refund process. Scanning of the barcode can be done before or after the merchant scans the returned merchandise.
  • the POS software at the merchant location makes a refund API call to initiate the refund.
  • the payment provider can then determine if the transaction (refund) is proper and valid. Ways in which the payment provider can do this include confirming whether the merchant and user accounts are valid, matching up the specific merchant account with the merchant, matching up the specific user account with the user, determining whether the refunded hern was truly purchased and if it was purchased at the merchant, matching the returned item to what is indicated on the receipt, any expiration date on the receipt for refunds, etc.
  • the payment provider transfers the refunded amount from the merchant's account to the user's account.
  • the payment provider then transmits an API response to indicate whether the refund was successful. If so, the merchant, at step 260, prints a receipt that shows the refund transaction.
  • the refund receipt may also be stored on the user's phone. This embodiment enables the user to easily and effectively manage receipts and refunds, as compared to saving, storing, and categorizing paper receipts.
  • Figs. 3A and 3B show one embodiment of a barcode generated from a mobile phone 300.
  • the user has opened up the application and is presented with a login screen 302.
  • Login screen 302 includes a phone field 304, which may or may not be populated with the device phone number, and a password or PIN field 306, where the user enters his or her PIN, such as using the phone keys.
  • the user is shown a screen with a barcode 308, which may only be valid for a certain time period and for a single use.
  • the barcode shown on the screen can then be scanned for payment at a POS, as described above.
  • Fig. 4 is a diagram showing various steps performed by different parties to a payment transaction using a mobile device according to one embodiment.
  • Path 1 illustrates steps taken by a buyer to register with the payment provider or create an account whh the payment provider.
  • Selected information such as the PIN, phone number, agreement token, and agreement ID are stored in a database 400 of the payment provider.
  • Database 400 may be stored on a local or remote server or any other suitable storage means.
  • Path 2 shows steps for the buyer when he is ready to make a purchase at a store or POS.
  • the user PIN and phone number are searched in database 400 to find the matching user ID.
  • the barcode is generated, with an associated barcode ID. Both the user ID and barcode ID are stored in database 400.
  • Path 3 shows steps for the merchant after the barcode is generated in path 2. After scanning the barcode, the barcode ID is checked in the database with a matching user ID. When confirmed, the user ID is transmitted to the merchant for confirmation of payment.
  • Fig. SA is a flowchart S00 showing an embodiment where the barcode contains a plurality of funding sources or instruments for use in a transaction.
  • Flowchart 500 illustrates a consumer experience.
  • the user with a mobile device may have entered a merchant store or at a location near one or more merchant stores.
  • the user may launch an app from the mobile device, which requests the user to enter specific authentication information, such as PIN/password, user name, phone number, email, etc.
  • the user enters the requested information into the mobile device, and in step 502, the payment provider processes the information to authenticate the user. For example, the payment provider determines whether an active account exists with the payment provider corresponding to the user and the information provided by the user.
  • the payment provider receives additional data from the mobile device, such as geo-location and user identification. Using the information received, the payment provider may determine available funding sources for the user in step 506. This may include determining which merchants are near the user/mobile device and which funding sources are available from the merchants. Note that funding sources as used herein may include anything used as part of a purchase, such as, but not limited to, coupons, gift cards, rebates, credit cards, debit cards, store credit, account credit, discounts, incentives, loyalty points, and the like.
  • Determining available funding sources may also include determining what funding sources the user has associated with the user's account. Not all account funding sources may be available though, as some funding sources may not be able to be used with the local merchant(s), have other restrictions, such as not yet in the redemption period, not for a particular location or branch, etc.
  • step 508 a determination is made whether the user has a loyalty card, club membership, or reward card with the local merchant(s), such as by checking whether any loyalty cards are associated with the user account or wallet and if so, whether any of those cards are for the identified local merchant(s). If so, the card information (e.g., name on card and card number) is determined in step S 10.
  • the card information e.g., name on card and card number
  • step 512 local and/or relevant offers are determined. Offers may include ones specific to the merchant, to the user, to a specific type of product, to a specific manufacturer, or the like. The determination may be based on the user's geo- location, merchant incentives promotions, user's funding source, and loyalty card information.
  • step 513 offers determined in step 512 are presented to the user, such as on the user device display.
  • the offers may be include a brief description or a more detailed description. For the former, the user may select the offer to view more details about the offer.
  • step 514 the user may choose one or more offers to accept.
  • the user may decide not to accept any offer or may choose to accept all offers presented as well.
  • Selection may be accomplished through the user clicking on or otherwise selecting a box or other indicator corresponding to the offer.
  • Any accepted offers are added to the user's wallet in step 516.
  • the user may be able to view offers directly through the user's mobile device or through the user's account with the payment provider, such as through the payment provider site.
  • the user may then shop or continue shopping at a merchant store.
  • the payment provider When ready to checkout, the payment provider generates a barcode (such as a QR code) in step 518.
  • the barcode and processing can have the same, some, or similar features of the barcodes and processes described in other embodiments above.
  • the barcode contains funding source information as well as any loyalty cards associated with the particular merchant.
  • any offers or incentives accepted by the user may also be included in the barcode information.
  • the barcode can be generated at different times in different embodiments. For example, the user may be ready to checkout (such as by tapping or otherwise selecting an appropriate button or link on the user device) when the user has finished shopping, but before a first item is scanned.
  • Ready to checkout may be prior to the scanning process, during the scanning process, or after all items have been scanned.
  • the payment provider receives transaction information, such as through the merchant POS device or other device like a PC, tablet, or smart phone.
  • the transaction information may include merchant identification information, user
  • transaction information may be communicated to the payment provider at different times and need to be at the same time as when all hems are scanned.
  • the barcode is then communicated to and displayed on the user device in step 520.
  • the user can present the displayed barcode to the merchant or place the display in front of a scanning device.
  • the merchant can then scan the barcode or have the barcode scanned, in step 522, on the mobile device.
  • the scan be through a scanner associated with the merchant POS or other device. For example, if a merchant or other payment recipient can scan the barcode with a smart phone, tablet, or other computing device capable of scanning a barcode and communicating the information to the payment provider.
  • Fig. 5B is a flowchart 550 showing an embodiment where the barcode contains a plurality of funding sources or instruments for use in a specific transaction.
  • Flowchart 550 illustrates a merchant and or payment provider experience.
  • the payment provider receives information contained in the scanned barcode, such as through a communication with the scanning device (e.g., the POS device, smart phone, tablet, etc.).
  • Information contained in the scan includes transaction details, including funding sources, loyalty cards, and offers, as well as merchant information, such as a merchant identifier, merchant name, merchant location, and the like.
  • the payment provider authenticates the merchant in step 554. Authentication may include determining whether the merchant has a valid account with the payment provider, based in part on the merchant identifier. Other information may also be used to authenticate the merchant, such as whether the transaction information matches goods sold by the merchant, the location of the scan matches with a confirmed merchant location, and other authentication measures. [0050] The payment provider also authenticates, in step 556, the barcode from the received scanned information. For example, the payment provider may determine whether the barcode is valid (e.g., whether the barcode is associated with the user account), whether the funding sources can be used with the purchase, such as limits exceeded or restrictions placed, and risk fraud analysis processing.
  • the user may have set an upper limit on the amount that can be purchased through the generated barcode.
  • the transaction may be denied, or the user may be informed that a different funding source, such as a credit card, will be needed to fund the amount over the barcode approved amount.
  • a different funding source such as a credit card
  • the payment provider determines, in step 558, which funding sources to use for the current transaction.
  • the payment provider may determine the best or suggested mix of funding sources for the transaction, which can be based on user settings, user preferences, merchant information, transaction amount, transaction location, expiration of funding sources, etc. For example, a store discount or gift card that will be expiring soon may be part of the funding sources for the transaction. Details of different ways to determine funding sources to use may be found in commonly-owned U.S. Patent Appl. Serial Number 13/330,264, file Dec. 11, 2011, which is incorporated by reference in its entirety. This step (or a separate step) may also determine any reward or club membership numbers for the merchant.
  • the funding sources may only be suggested funding sources that the user can approve or revise as desired.
  • step 560 a determination is made whether any offers contained in the barcode may be used with the purchase.
  • the payment provider may determine whether an offer corresponds to a scanned or purchased item and whether any conditions of the offer are met with the transaction.
  • the payment provider processes redemption of the offer(s) in step 562. This may include the payment provider applying the discount or incentive to the purchase to reduce an item price.
  • Redeemed offers may be processed with entities offering the offers. For example the payment provider may notify an entity that an offer has been redeemed. The entity may then settle with the merchant or the payment provider may handle settlement between the entity and merchant as well.
  • the payment provider processes the payment in step 564.
  • the payment provide may deduct the purchase total from one or more user funding sources and credit a purchase amount to an account of the merchant.
  • the payment provider may format a receipt for the transaction in step 566.
  • the receipt may list all items purchased, any discounts, offers, or incentives applied to each eligible purchase, funding source(s) used, transaction date and time, transaction location, merchant information, and any other desired information.
  • the receipt may then be presented to the user device in step 568, which can be stored in the user account or digital wallet on the phone as discussed herein.
  • the payment provider may also send receipt data to the merchant, which may allow the merchant to store transaction details and/or print a physical receipt for the user.
  • barcode enables the user to have the barcode scanned by a POS device, manned or unmanned, or even by a smart phone (allowing small merchants or payees to process barcode payments), to quickly and easily make a payment. Because the barcode contains a plurality of funding sources, including offers and incentives, and/or
  • the user can pay more intelligently and convey different types of information in a single barcode.
  • Fig. 6 is a block diagram of a computer system or device 600 according to one embodiment, which may be suitable for implementing embodiments of various aspects of this disclosure.
  • device 600 may comprise a personal computing device, such as a personal computer, laptop, PDA, cellular or smart phone, a computing tablet, or other personal computing or communications devices.
  • Database 400 may be within, part of, or comprise a network computing device, such as one or more servers, computer or processor combined to provide the payment services.
  • computer system 600 may include a bus 602 or other communication mechanism for communicating information, which interconnects subsystems and components, such as a processing component 604 (e.g., processor, microcontroller, digital signal processor (DSP), etc.), a system memory component 606 (e.g., RAM), a static storage component 608 (e.g., ROM), a disk drive component 610 (e.g., magnetic or optical), a network interface component 612 (e.g., modem or Ethernet card), a display component 614 (e.g., CRT or LCD for displaying the generated barcode), an input component 616 (e.g., keyboard or keypad for entering a PIN or password), and/or a cursor control component 618 (e.
  • a processing component 604 e.g., processor, microcontroller, digital signal processor (DSP), etc.
  • Computer system 600 may perform specific operations by processor 604 executing one or more sequences of one or more instructions contained in system memory component 606, according to steps described above. Such instructions may be read into system memory component 606 from another computer readable medium, such as static storage component 608 or disk drive component 610.
  • the various storage or memory components may be used to store information about trusted sources for the quick-approval process.
  • hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention.
  • Logic may be encoded in a computer readable medium, which may refer to any medium that participates in providing instructions to processor 604 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
  • the computer readable medium is non-transitory.
  • non-volatile media includes optical or magnetic disks, such as disk drive component 610
  • volatile media includes dynamic memory, such as system memory component 606
  • transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 602.
  • transmission media may take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
  • Some common forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, carrier wave, or any other medium from which a computer is adapted to read.
  • execution of instruction sequences for practicing embodiments of the invention may be performed by computer system 600.
  • communication link 620 may perform instruction sequences to practice the invention in coordination with one another.
  • Computer system 600 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) through
  • Received program code may be executed by processor 604 as received and/or stored in disk drive component 610 or some other non-volatile storage component for execution.
  • various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and/or software components set forth herein may be combined into composite components comprising software, hardware, and/or both without departing from the spirit of the present disclosure. Where applicable, the various hardware components and/or software components set forth herein may be separated into sub-components comprising software, hardware, or both without departing from the scope of the present disclosure. In addition, where applicable, it is contemplated that software components may be implemented as hardware components and vice-versa.
  • Software in accordance with the present disclosure, such as program code and/or data, may be stored on one or more computer readable mediums. It is also contemplated that software identified herein may be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein may be changed, combined into composite steps, and/or separated into sub-steps to provide features described herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Selon l'invention, une application sur le dispositif mobile (ayant un écran d'affichage) d'un utilisateur génère un code à barres spécifique à une transaction sur le dispositif d'affichage, le code à barres contenant une pluralité de sources de financement pour la transaction et/ou de numéros de fidélité, de récompense ou d'adhésion de commerçant. Le code à barres peut être balayé pour réaliser des achats à un point de vente (POS).
PCT/US2013/034704 2012-03-29 2013-03-29 Génération de code à barres mobile et paiement WO2013149200A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CA2907930A CA2907930C (fr) 2012-03-29 2013-03-29 Generation de code a barres mobile et paiement
EP13717909.9A EP3365852A1 (fr) 2012-03-29 2013-03-29 Génération de code à barres mobile et paiement
AU2013237855A AU2013237855A1 (en) 2012-03-29 2013-03-29 Mobile barcode generation and payment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13/433,792 2012-03-29
US13/433,792 US8600883B2 (en) 2008-12-02 2012-03-29 Mobile barcode generation and payment

Publications (1)

Publication Number Publication Date
WO2013149200A1 true WO2013149200A1 (fr) 2013-10-03

Family

ID=49261314

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/034704 WO2013149200A1 (fr) 2012-03-29 2013-03-29 Génération de code à barres mobile et paiement

Country Status (4)

Country Link
EP (1) EP3365852A1 (fr)
AU (1) AU2013237855A1 (fr)
CA (2) CA2907930C (fr)
WO (1) WO2013149200A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3624039A4 (fr) * 2017-06-13 2020-06-03 Sony Corporation Dispositif et système de traitement d'informations
US10902473B2 (en) * 2012-01-23 2021-01-26 Visa International Service Association Systems and methods to formulate offers via mobile devices and transaction data
US11574332B1 (en) * 2018-06-25 2023-02-07 Sprint Communications Company, L.P. Method for generating and using a 2D barcode
EP4191500A1 (fr) * 2015-11-23 2023-06-07 Loyalty Angels Ltd Système et procédé d'extraction de données

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10977650B2 (en) 2013-10-30 2021-04-13 Tencent Technology (Shenzhen) Company Limited Information transmission method, apparatus and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002015062A2 (fr) * 2000-08-18 2002-02-21 Telefonaktiebolaget L M Ericsson (Publ) Procede et systeme ameliores d'execution d'une transaction financiere
EP1551140A1 (fr) * 2003-12-29 2005-07-06 Nokia Corporation Codage visuelle d'une addresse de contenu pour faciliter des transmission de données entre des dispositifs digital
US20060080111A1 (en) * 2002-09-26 2006-04-13 Homeier-Beals Thomas E Mobile electronic transaction system, device and method therefor
US20080133366A1 (en) * 2006-11-30 2008-06-05 Mobilocity Rendering barcodes on mobile device screens for use at retailer point of sale locations to obtain discounts
US20080210754A1 (en) * 2005-06-13 2008-09-04 Robert Lovett Account payment using barcode information exchange

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002015062A2 (fr) * 2000-08-18 2002-02-21 Telefonaktiebolaget L M Ericsson (Publ) Procede et systeme ameliores d'execution d'une transaction financiere
US20060080111A1 (en) * 2002-09-26 2006-04-13 Homeier-Beals Thomas E Mobile electronic transaction system, device and method therefor
EP1551140A1 (fr) * 2003-12-29 2005-07-06 Nokia Corporation Codage visuelle d'une addresse de contenu pour faciliter des transmission de données entre des dispositifs digital
US20080210754A1 (en) * 2005-06-13 2008-09-04 Robert Lovett Account payment using barcode information exchange
US20080133366A1 (en) * 2006-11-30 2008-06-05 Mobilocity Rendering barcodes on mobile device screens for use at retailer point of sale locations to obtain discounts

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10902473B2 (en) * 2012-01-23 2021-01-26 Visa International Service Association Systems and methods to formulate offers via mobile devices and transaction data
EP4191500A1 (fr) * 2015-11-23 2023-06-07 Loyalty Angels Ltd Système et procédé d'extraction de données
EP3624039A4 (fr) * 2017-06-13 2020-06-03 Sony Corporation Dispositif et système de traitement d'informations
US11301826B2 (en) 2017-06-13 2022-04-12 Sony Corporation Information processing apparatus and information processing system
US11574332B1 (en) * 2018-06-25 2023-02-07 Sprint Communications Company, L.P. Method for generating and using a 2D barcode

Also Published As

Publication number Publication date
CA3061601C (fr) 2022-02-22
CA2907930C (fr) 2020-01-07
AU2013237855A1 (en) 2016-01-07
CA2907930A1 (fr) 2013-10-03
EP3365852A1 (fr) 2018-08-29
CA3061601A1 (fr) 2013-10-03

Similar Documents

Publication Publication Date Title
US20210201301A1 (en) Mobile barcode generation and payment
US10176474B2 (en) Mobile barcode generation and payment
US11868974B2 (en) Systems, methods, and computer program products providing push payments
US11127009B2 (en) Methods and systems for using a mobile device to effect a secure electronic transaction
US10580049B2 (en) System and method for incorporating one-time tokens, coupons, and reward systems into merchant point of sale checkout systems
US20170236118A1 (en) Transaction token issuing authorities
US20150206128A1 (en) Contactless wireless transaction processing system
US20120232981A1 (en) Contactless wireless transaction processing system
JP2015092387A (ja) 動作方法及びモバイル装置
WO2013066910A1 (fr) Système et procédé d'incorporation de jetons à usage unique, de bons et de systèmes de récompense dans des systèmes de caisse de point de vente de marchand
CA3061601C (fr) Generation de code a barres mobile et paiement
AU2013201177B2 (en) Mobile barcode generation and payment
AU2015213383A1 (en) Mobile barcode generation and payment
WO2013170101A2 (fr) Système de traitement de transactions sans fil et sans contact

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: 13717909

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2013717909

Country of ref document: EP

122 Ep: pct application non-entry in european phase

Ref document number: 13717909

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2907930

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2013237855

Country of ref document: AU

Date of ref document: 20130329

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2013717909

Country of ref document: EP

Effective date: 20141029