WO2012083113A2 - Portefeuille numérique - Google Patents

Portefeuille numérique Download PDF

Info

Publication number
WO2012083113A2
WO2012083113A2 PCT/US2011/065363 US2011065363W WO2012083113A2 WO 2012083113 A2 WO2012083113 A2 WO 2012083113A2 US 2011065363 W US2011065363 W US 2011065363W WO 2012083113 A2 WO2012083113 A2 WO 2012083113A2
Authority
WO
WIPO (PCT)
Prior art keywords
digital wallet
computer
merchant
payment
user
Prior art date
Application number
PCT/US2011/065363
Other languages
English (en)
Other versions
WO2012083113A3 (fr
Inventor
Jonathan Wall
Rob Von Behren
Original Assignee
Google 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/235,167 external-priority patent/US20120158654A1/en
Priority claimed from US13/277,182 external-priority patent/US9691055B2/en
Application filed by Google Inc. filed Critical Google Inc.
Priority to AU2011343638A priority Critical patent/AU2011343638B2/en
Priority to CA2814115A priority patent/CA2814115C/fr
Publication of WO2012083113A2 publication Critical patent/WO2012083113A2/fr
Publication of WO2012083113A3 publication Critical patent/WO2012083113A3/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/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/363—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes with the personal data of a user

Definitions

  • the present disclosure relates generally to electronic commerce, and more particularly to a digital wallet for facilitating transactions and storing information associated with transactions.
  • Online shopping websites generally provide a user interface for customers to select products to purchase. After the customer has selected products for purchase, the customer typically can choose from multiple payment options to purchase the products.
  • Two conventional payment options generally supported by online merchants are using a financial account (for example, a credit card account or checking account) and using a third party payment processor, such as PAYPAL ® or other processor.
  • a consumer To complete an online purchase using a credit card or other financial account, a consumer typically provides a significant amount of information to the merchant via the merchant's website.
  • This information generally includes an account identifier (for example, credit card number, debit card number, etc.), shipping information, and the name, address, and contact information of the consumer.
  • the requirement of entering this information for each merchant from which the consumer makes purchases can be cumbersome and frustrating to the consumers. This requirement can be particularly frustrating and difficult for consumers making online purchases using a mobile device, as many mobile devices do not include a user interface optimized to enter significant amounts of information. This deficiency for mobile devices results in substantially lower mobile browser conversion rates from product searching to product purchase compared to desktop browser conversion rates.
  • toolbar plug-in application for web browsers.
  • Conventional toolbar applications are used to automatically populate web forms, such as a web form for receiving payment and consumer information for completing an online purchase, with stored information.
  • these conventional toolbar applications often are inaccurate, as they merely attempt to predict which form is presented on a web page and then preload default values for the predicted form.
  • a third party payment processor requires a consumer to register for an account and to provide one or more payment options. After registering, the consumer can use the payment options to complete purchases at participating merchants' websites.
  • the consumer To complete an online purchase using the third party payment processor, the consumer generally selects a link at the merchant's website and, in response, the consumer is redirected from the merchant's website to a website of the third party payment processor.
  • the consumer At this website, the consumer first has to provide login information and then can select one of the payment options to complete and confirm the purchase. After the purchase is confirmed, the consumer is directed back to the merchant's website.
  • the third party payment processor then settles with the financial institution associated with the selected payment option and with the merchant to complete the transaction.
  • the use of a third party processor has several deficiencies. First, the process is disruptive to the consumer as the consumer is directed away from the merchant's website to the third party payment processor's website and then back to the merchant's website. Second, the use of a third party payment processor limits the amount of information that the merchant receives. For example, the merchant may not have access to information associated with the consumer or information regarding the payment method used. The use of a third party processor also presents an additional cost to the merchant.
  • An aspect of the present invention provides a computer-implemented method for completing an online transaction.
  • a digital wallet module resident on a client device receives a request for payment information to complete the transaction.
  • the request originates from a website of a merchant.
  • the digital wallet module retrieves the payment information from a storage location on the client device and transmits the retrieved payment information to the merchant website.
  • the computer program product includes a computer- readable storage device having computer-readable program instructions stored therein.
  • the computer-readable program instructions includes computer program instructions for receiving a request for payment information to complete the transaction, the request originating from a website of a merchant; computer program instructions for retrieving, in response to the request, the payment information; and computer program instructions for transmitting the retrieved payment information to the merchant website.
  • the apparatus includes a web browser application a digital wallet module logically coupled to the web browser application.
  • the digital wallet module is configured to receive a request for payment information to use in completing the purchase from the merchant website; retrieve payment information from a computer-readable storage device logically coupled to the digital wallet module; and transmit the retrieved payment information to the merchant.
  • Another aspect of the present invention provides a computer-implemented method for completing a purchase from a merchant via a website of the merchant.
  • a digital wallet module embedded in a web browser in communication with the merchant website receives a purchase request message including a request for payment information for use in compensating the merchant for the purchase.
  • the digital wallet module presents a confirmation display requesting a user to authorize the purchase.
  • the digital wallet module retrieves stored payment information and transmits a payment authorization message including the retrieved payment information to the merchant website.
  • Figure 1 is a block diagram depicting an operating environment of a digital wallet, in accordance with certain exemplary embodiments.
  • Figure 2 is a block diagram depicting a general component architecture of a computer system, in accordance with certain exemplary embodiments.
  • Figure 3 is a flow chart depicting a method for completing an online purchase using a digital wallet, in accordance with certain exemplary embodiments.
  • Figure 4 is a flow chart depicting a method for a digital wallet to interact with a merchant website to complete a purchase, in accordance with certain exemplary embodiments.
  • Figure 5 is a flow chart depicting a method for installing a digital wallet on a user device, in accordance with certain exemplary embodiments.
  • the exemplary embodiments provide a digital wallet that can facilitate fast, convenient, and secure commerce using a mobile electronic device (or non-mobile electronic device) and that stores information associated with transactions, such as purchase confirmations and receipts.
  • the digital wallet can provide a user interface for entering information for use in transactions, such as information associated with one or more financial accounts (for example, credit card or debit card information), contact information, and shipping information.
  • the digital wallet can store this information for subsequent use in online (for example, via the Internet) and offline purchases (for example, via a merchant point of sale device, including a contactless payment device).
  • the user can use the digital wallet to complete purchases by selecting a payment option stored by the digital wallet without the need to re-enter financial account information, contact information, or shipping information for each purchase.
  • the user also may select a default payment option to use such that the user can confirm a purchase without making a payment option selection.
  • the digital wallet can be particularly advantageous when utilized to complete a purchase using a mobile device, such as a mobile phone or other electronic device, having a limited user interface that may not be optimized to enter a significant amount of information.
  • the digital wallet can be embodied as a stand alone application program or as a companion program to a web browser, for example, as a companion program to a Hypertext Markup Language revision 5 ("HTML5") compliant web browser or other type of web browser having messaging and storage capabilities.
  • HTML5 Hypertext Markup Language revision 5
  • the digital wallet can leverage the messaging and storage capabilities of the web browser to provide a consistent buying experience across multiple merchant websites. That is, the digital wallet can provide a consistent user interface independent of merchants' differing websites.
  • the digital wallet also can allow a user to complete a purchase without navigating from the merchant's website as required by third party payment processors. While certain embodiments are described in which parts of the digital wallet are implemented in software, it will be appreciated that one or more acts or functions of the digital wallet may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems.
  • a user can navigate to a merchant's website using a web browser and locate one or more products. After the user indicates a desire to purchase one or more products, the digital wallet can interact with the merchant's website and with the user in a secure manner to complete the transaction. Once the transaction is completed, the digital wallet can receive or generate a confirmation or receipt for the transaction and can store the confirmation or receipt. The digital wallet also can synchronize the confirmation or receipt with a remote storage location, such as a cloud computing environment.
  • a remote storage location such as a cloud computing environment.
  • the digital wallet can interact with a merchant's point of sale device and with the user.
  • the user can activate the digital wallet, for example, by launching an application, by pressing a physical or virtual button on the mobile device, or by making a gesture with the mobile device.
  • the digital wallet can then communicate payment information to the point of sale device and, when the payment information is confirmed, receive a receipt from the point of sale device.
  • the mobile device can communicate with the point of sale device using a wireless technology, such as near field communication technology (NFC), BLUETOOTH, or other suitable wireless technology.
  • NFC near field communication technology
  • BLUETOOTH wireless technology
  • the digital wallet can also store coupons or loyalty reward for use in transactions and can automatically apply the stored coupons during a purchase transaction, if appropriate. For example, a coupon for a product may be displayed to a user in response to an Internet search. The user can download the coupon to the digital wallet and store the coupon on the mobile device. The digital wallet can search the coupons during purchases to determine if one or more of the stored coupons may be applied to the purchase. If so, the digital wallet can automatically apply the stored coupon.
  • the digital wallet can communicate with a remote system to facilitate multiple functions.
  • the digital wallet can receive security information that identifies trusted merchants and non-trusted merchants from the remote system.
  • the digital wallet can use this security information to prevent the user from providing financial account information or other information to non-trusted merchants.
  • the digital wallet may compare a merchant name, merchant website Uniform Resource Locator (URL), or Internet Protocol (IP) address to a list of known non-trusted merchants prior to passing information from the digital wallet to the merchant's website.
  • URL Uniform Resource Locator
  • IP Internet Protocol
  • the remote system also can maintain an account for each individual user.
  • This user account can include information associated with payment options for use in transactions and receipts or other information regarding completed transactions.
  • the digital wallet can synchronize, for example, periodically, with the remote system to maintain current information at both locations.
  • the remote system also may provide a user interface via a web browser that enables the user to modify information, such as financial account information of stored payment options and contact information for use in transactions, and to access stored receipts.
  • the user can access the stored receipts, for example, to determine when a certain purchase was made, to determine how much the user paid for an item, or for budgeting purposes.
  • the remote system or a third party having access to the receipts stored at the remote system can use the receipts to target advertisements or other promotional materials to the user.
  • Users may, in appropriate circumstances, be allowed to limit or otherwise affect the operation of the features disclosed in this specification. For example, users may be given an initial opportunity to opt-in or opt-out of the collection or use of certain data or the activation of certain features. In addition, users may be provided opportunities to change the manner in which the features are employed, including for situations in which users may have concerns regarding their privacy. Instructions also may be provided to users to notify the users regarding policies about the use of information, including personally identifiable information and receipt information, and manners in which the users may affect such use of information. Thus, sensitive personal information can be used to benefit a user, if desired, through receipt of targeted advertisements or other information, without risking disclosure of personal information or the user's identity.
  • One or more aspects of the invention may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions.
  • the invention should not be construed as limited to any one set of computer program instructions.
  • a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed invention based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the invention.
  • Figure 1 is a block diagram depicting an operating environment 100 for a digital wallet, in accordance with certain exemplary embodiments.
  • the exemplary operating environment 100 includes a merchant system 130, a cloud computing environment 150, and a user device 110 associated with a user 101.
  • the user device 110 may be a personal computer, mobile device, (for example, notebook computer, tablet computer, netbook computer, personal digital assistant (PDA), video game device, GPS locator device, cellular telephone, smartphone, or other mobile device), or other appropriate technology that includes or is coupled to a web browser application module 112, such as GOOGLE'S CHROME, MICROSOFT'S INTERNET EXPLORER ® , or MOZILLA'S FIREFOX ® .
  • a web browser application module 112 such as GOOGLE'S CHROME, MICROSOFT'S INTERNET EXPLORER ® , or MOZILLA'S FIREFOX ® .
  • the web browser application 112 is an HTML5 compliant web browser.
  • HTML5 compliant web browsers include a cross-document messaging application programming interface (API) and a local storage API that previous HTML versions did not have.
  • the cross-document messaging API of HTML5 compliant web browsers enables documents, such as web pages, to communicate with each other. For example, a first document can send a message to a second document requesting information. In response, the second document can send a message including the requested information to the first document.
  • the local storage API of HTML5 compliant web browsers enables the web browser to store information on a client device upon which the web browser is installed or is executing, such as the user device 110. Websites also can employ the local storage API to store information on a client device.
  • Other web browsers having cross-document messaging and/or local storage capabilities also may be used in certain exemplary embodiments.
  • the user 101 can use the web browser application 112 to view, download, upload, or otherwise access documents or web pages via a distributed network 105.
  • the network 105 includes a wired or wireless telecommunication system or device by which network devices (including devices 110, 130, and 150) can exchange data.
  • the network 105 can include a local area network ("LAN”), a wide area network ("WAN”), an intranet, an Internet, or any combination thereof.
  • LAN local area network
  • WAN wide area network
  • intranet an Internet
  • Internet Internet
  • the web browser application 112 can interact with web servers (or other computing devices) connected to the network 105, such as web server 132 of the merchant system 130 and/or web server 151 of the cloud computing environment 150.
  • the user device 110 also includes a digital wallet application module 111.
  • the exemplary digital wallet 111 can interact with the web browser application 112 or can be embodied as a companion application of the web browser application 112. As a companion application, the digital wallet 111 executes within the web browser application 112. That is, the digital wallet 111 may be an application program embedded in the web browser application 112.
  • the user device 110 also includes a data storage unit 113 accessible by the digital wallet 111 and the web browser application 112.
  • the exemplary data storage unit 113 can include one or more tangible computer-readable storage devices as discussed below with reference to Figure 2.
  • the data storage unit 113 can be stored on the user device 110 or can be logically coupled to the user device 110.
  • the data storage unit 113 can include on-board flash memory and/or one or more removable memory cards or removable flash memory.
  • the exemplary digital wallet 111 enables storage of one or more payment options that can be used for online purchases and offline purchases.
  • Each payment option can include or be associated with a financial account, such as a credit card account, a debit card account, a checking account, a savings account, a loyalty rewards account, or other type of account that can be used to make a purchase.
  • the digital wallet 111 can store, for each payment option, information associated with the financial account for that payment option. This payment information can include a financial account identifier (for example, account number, card number), an expiration date of one or more financial cards associated with the financial account, and a billing address for the account.
  • the payment information can also include information associated with the user 101, such as name, contact information (for example, residential address, phone number, e-mail address), demographic information, or any other suitable information associated with the user 101.
  • the payment information also can include shipping information, such as one or more shipping addresses, preferred shipping provider(s), and preferred shipping method(s) (for example, ground, air, expedited, signature confirmation, or other shipping method).
  • the payment information for each payment option can be maintained by the digital wallet 111 and stored in the data storage unit 113.
  • the user 101 can interact with a user interface provided by the digital wallet 111 to add, modify, or remove payment information from the digital wallet 111.
  • this user interface can be provided via the web browser application 112.
  • the payment information may be synchronized with a remote storage location, such as the cloud computing environment 150.
  • the user 101 can access the payment information stored at the remote location using another device, such as a desktop computer connected to the network 105.
  • the remote storage location can update the digital wallet 111 in response to any changes made at the remote storage location.
  • the payment option(s) stored in the digital wallet 111 can be used to complete purchases from merchants via a merchant's website 133 operating on the web server 131 or via a merchant's point of sale device 134.
  • each merchant's website 133 (operating on the web server 131) that accepts payment via a digital wallet 111 can include a set of computer-readable program instructions, for example, using JavaScript, that enable the merchant's website 133 to interact with the digital wallet 111.
  • These program instructions can include program instructions for detecting whether the user device 110 includes a digital wallet 111 and program instructions for attaching to a detected digital wallet 111. Once attached, the merchant's website 133 can communicate with the digital wallet 111, for example, via cross-document messaging.
  • the computer-readable instructions also include program instructions for downloading a digital wallet 111 onto a user device 110.
  • the merchant's website 133 detects that the user device 110 does not have a digital wallet 111
  • the merchant's website 133 can prompt the user 101 to download and install the digital wallet 111.
  • the computer-readable program code can download and install the digital wallet 111 on the user device 101. Embedding this computer-readable program instructions in a website 133 for interacting with a digital wallet 111 supports a simpler and efficient integration for the merchant system 130 compared to integrating with a third party payment processor.
  • the merchant's website 133 and the digital wallet 111 can communicate using a defined messaging protocol.
  • the digital wallet 111 can encode a message using the protocol and send the encoded message to the merchant's website 133, where the message is decoded using the protocol.
  • the merchant's website 133 can encode a message using the protocol and send the encoded message to the digital wallet 111 where the message is decoded using the protocol.
  • the merchant system 130 includes a payment processor 132 logically coupled to the web server 131.
  • the payment processor 132 can receive payment information via the web server 131 and interact with the financial institution (not shown) or an acquirer (not shown) to authorize payment information.
  • the digital wallet 111 can interact with a website 133 of the merchant system 130 and with the user 101.
  • the user 101 can browse the merchant's website 133 for products using the web browser 112 and indicate a desire to purchase one or more products.
  • the term "products" should be interpreted to include tangible and intangible products, as well as services.
  • the merchant's website 133 can present a user interface in the form of a web page to receive payment information from the user 101.
  • the merchant's website 133 also can detect whether the user device 110 includes a digital wallet 111.
  • the merchant's website 133 can automatically attach to the digital wallet 111 as discussed in further detail below in connection with Figure 4.
  • the merchant's website 133 can include a "pay with wallet” link or control that, when actuated, causes the merchant's website 133 to attach to the digital wallet 111. Once attached, the merchant's website 133 sends a purchase request message to the digital wallet 111 requesting payment information.
  • the purchase request message also can include information regarding the requested purchase, including information regarding the product(s) for purchase (for example, name and/or description of each product, price for each product, total price, etc.), information regarding the merchant system 130 (for example, merchant name, payment methods accepted by merchant, etc.), and requests for the user 101 to provide additional information.
  • the digital wallet 111 can present a user interface to the user 101 for the user 101 to confirm the purchase. This user interface can display all or a portion of the information in the purchase request and an actuatable button or link for the user 101 to confirm the purchase.
  • This user interface also can allow the user 101 to select from multiple payment options stored by the digital wallet 111 to use as payment for the product(s) and from multiple shipping options. If the user 101 confirms the purchase, the digital wallet 111 can retrieve the information requested in the purchase request message, generate a merchant request message that contains the information and the confirmation, and transmit the merchant request message to the merchant's website 133. If the purchase is authorized via the payment processor 132, the merchant's website 133 can transmit an electronic confirmation and/or a receipt to the digital wallet 111 and then detach from the digital wallet 111. The digital wallet 111 can store the confirmation and/or receipt at the user device 110 and also synchronize with the cloud computing environment 150. An exemplary method for completing an online purchase using the digital wallet 111 is illustrated in Figure 3 and discussed below.
  • the receipt received by the digital wallet 111 can include line item details of the completed purchase.
  • the receipt can include a list of products purchased, a description of each product purchased, the price for each product purchased, a product category for each product purchased, a total price, a stock keeping unit (SKU) or similar identifier for each product purchased, taxes paid, rebates for one or more of the products purchased, payment method used, discounts applied, the time and/or date of purchase, warranty information for one or more of the products purchased, or other suitable information.
  • the receipt also can include information regarding the merchant system 130, including a name of the merchant associated with the merchant system 130, a description of the 130, the URL of the merchant's website 133, and any other suitable information regarding the merchant system 130.
  • the digital wallet 111 can generate a receipt for a purchase rather than or in addition to receiving a receipt from the merchant's website 133.
  • the digital wallet 111 can generate the receipt using the information in the purchase request message received from the merchant's website 133 or from the merchant request message sent to the merchant's website 133.
  • the exemplary cloud computing environment 150 includes the web server 151, one or more data storage units 152, and one or more application servers 153.
  • the cloud computing environment 150 may be provided by the provider of the digital wallet, by a merchant 130, or by another party.
  • multiple cloud computing environments 150 may be employed.
  • a first cloud computing environment may store receipt information and provide access to the receipts from a user device 110 connected to the first cloud computing environment
  • a second cloud computing environment may provide security information, such as lists of non-trusted merchants, to the digital wallet 111.
  • the illustrated environment includes a cloud computing environment, other types of computing environments, such as a client-server environment may be used instead.
  • the application server 153 can maintain a digital wallet account for each user, including the user 101.
  • This digital wallet account can store (in the data storage unit 152) the payment options created by the user 101 and their associated payment information and receipts and other information obtained by the digital wallet 111 in response to completed transactions.
  • the application server 153 can synchronize this information with the digital wallet 111 periodically, on command (for example, by the user 101), or in response to an update in information at the digital wallet 111 or at the cloud computing environment 150.
  • the digital wallet 111 and the web browser application 112 can interact with the application server 151 via the web server 151.
  • the application server 153 can provide a user interface via the web server 151 that enables the user 101 to access, view, and/or modify content stored in the user's digital wallet account using the user device 110 or another device connected to the network.
  • the user 101 may add or modify payment information using a web browser application residing on a desktop computer having a better user interface for entering a significant amount of information.
  • the exemplary digital wallet 111 can include a user interface for accessing receipt information stored on the user device 110 or at the cloud computing environment 150 in a meaningful and useful way.
  • This user interface enables the user 101 to search the receipts for information.
  • the user 101 may search for a product purchased to determine the price that was paid for the product or when the product was purchased.
  • the user 101 may search for warranty information regarding a product to determine if the warranty has expired.
  • the user 101 may search the receipts for merchant return policy information.
  • This digital wallet's user interface also includes a budgeting feature.
  • This budgeting feature of the digital wallet 111 enables the user 101 to set a budget for expenditures associated with one or more products or product categories and to monitor this budget using the stored receipts. For example, the user 101 can set a budget of $200 to spend eating out each month.
  • the digital wallet 111 can run a query on the receipts corresponding to transactions completed in the current month to identify receipts that correspond to a restaurant purchase or otherwise to eating out. The digital wallet 111 can then determine the total dollar amount of these receipts and the remaining budget for the current month.
  • the digital wallet's user interface also enables the user 101 to filter information associated with receipts and view the filtered information.
  • the receipt information can be filtered by product category, merchant, time period, or any other receipt parameter or combination thereof.
  • the user 101 can use the digital wallet 111 to view the total amount spent at a particular merchant, such as the merchant associate with merchant system 130, in the past three months or other desired time period.
  • One or more of the components of the exemplary operating environment 100 can include one or more computer systems, such as the computer system 200 illustrated in Figure 2.
  • the computer system 200 includes a processing unit 221, a system memory 222, and a system bus 223 that couples system components, including the system memory 222, to the processing unit 221.
  • the system bus 223 can include any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, or a local bus, using any of a variety of bus architectures.
  • the system memory 222 includes a read-only memory (“ROM”) 224 and a random access memory (“RAM”) 225.
  • a basic input/output system (BIOS) 226 containing the basic routines that help to transfer information between elements within the computer system 200, such as during start-up, is stored in the ROM 224.
  • the computer system 200 also includes a hard disk drive 227 for reading from and writing to a hard disk (not shown), a magnetic disk drive 228 for reading from or writing to a removable magnetic disk 229 such as a floppy disk, and an optical disk drive 230 for reading from or writing to a removable optical disk 231 such as a CD-ROM, compact disk - read/write (CD/RW), DVD, or other optical media.
  • the hard disk drive 227, magnetic disk drive 228, and optical disk drive 230 are connected to the system bus 223 by a hard disk drive interface 232, a magnetic disk drive interface 233, and an optical disk drive interface 234, respectively.
  • the exemplary computer system 200 employs a ROM 224, a RAM 225, a hard disk drive 227, a removable magnetic disk 229, and a removable optical disk 231, other types of computer-readable media also can be used in the exemplary computer system 200.
  • the computer-readable media can include any apparatus that can contain, store, communicate, propagate, or transport data for use by or in connection with one or more components of the computer system 200, including any electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or propagation medium, such as magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, and the like.
  • the drives and their associated computer-readable media can provide nonvolatile storage of computer-executable instructions, data structures, program modules, and other data for the computer system 200.
  • a number of modules can be stored on the ROM 224, RAM 225, hard disk drive 227, magnetic disk 229, or optical disk 231, including an operating system 235, an application module 238, and the web browser application 112, the digital wallet 111, and the website application discussed above in connection with Figure 1.
  • the web browser application 112, the digital wallet 111, website application, and application module 238 can include routines, sub-routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types.
  • a user can enter commands and information to the computer system 200 through input devices, such as a keyboard 240 and a pointing device 242.
  • the pointing device 242 can include a mouse, a trackball, an electronic pen that can be used in conjunction with an electronic tablet, or any other input device, such as a microphone, joystick, game pad, satellite dish, scanner, or the like.
  • These and other input devices are often connected to the processing unit 222 through a serial port interface 246 that is coupled to the system bus 223, but can be connected by other interfaces, such as a parallel port, game port, a universal serial bus (USB), or the like.
  • USB universal serial bus
  • a display device 247 such as a monitor, also can be connected to the system bus 223 via an interface, such as video adapter 248.
  • the computer 220 can include other peripheral output devices, such as speakers (not shown) and a printer 243.
  • the computer system 200 is configured to operate in a networked environment using logical connections to one or more remote computers 249.
  • the remote computer 249 can be any network device, such as a personal computer, a server, a client, a router, a network PC, a peer device, or other device. While the remote computer 249 typically includes many or all of the elements described above relative to the computer system 200, only a memory storage device 250 has been illustrated in Figure 2 for simplicity.
  • the logical connections depicted in Figure 2 include a LAN 204 A and a WAN 204B. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.
  • the computer system 200 When used in a LAN networking environment, the computer system 200 is often connected to the LAN 204 A through a network interface or adapter 253.
  • the computer system 200 When used in a WAN networking environment, the computer system 200 typically includes a modem 254 or other means for establishing communications over the WAN 204B, such as the Internet.
  • the modem 254 which can be internal or external, is connected to system bus 223 via a serial port interface 246.
  • program modules depicted relative to computer system 200, or portions thereof, can be stored in the remote memory storage device 250.
  • the components of the exemplary operating environment 100 are described hereinafter with reference to the exemplary methods illustrated in Figures 3-5.
  • the exemplary embodiments can include one or more computer programs that embody the functions described herein and illustrated in the appended flow charts.
  • computer programs that embody the functions described herein and illustrated in the appended flow charts.
  • a skilled programmer would be able to write such computer programs to implement exemplary embodiments based on the flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use the exemplary embodiments.
  • one or more acts described may be performed by hardware, software, or a combination thereof, as may be embodied in one or more computing systems.
  • FIG. 3 is a flow chart depicting a method 300 for completing an online purchase using a digital wallet 111, in accordance with certain exemplary embodiments.
  • the merchant installs computer-readable program instructions on the merchant's website 133 for interacting with the digital wallet 111.
  • These computer-readable program instructions can be implemented as an embedded script, such as JavaScript, in a web page of the merchant system 130.
  • the merchant system 130 can embed the computer-readable program instructions on a "checkout" web page of the merchant's website 133.
  • a digital wallet 111 is installed, then the browser is instructed to surface a wallet control button for selection by the user. If a digital wallet 111 is not installed, then the browser is instructed to surface another control for interaction with the user, such as an option to install a wallet application 111.
  • the digital wallet 111 is installed on the user device 110.
  • the user 101 can navigate to a website 133 of a provider of the digital wallet 111 and download and install the digital wallet 111.
  • a merchant's website 133 can prompt the user 101 to download and install the digital wallet 111, for example, upon selecting the "checkout" option on the merchant's website 133.
  • the user 101 may provide payment information to the merchant's website 133 in a conventional manner and then download and install the digital wallet 111.
  • the payment information provided to the merchant's website 133 can then be automatically stored in the digital wallet 111 installed on the user device 101.
  • An exemplary method of installing a digital wallet 111 is discussed further in connection with Figure 5.
  • the digital wallet 111 sends a merchant request message including the confirmation and payment information associated with the payment option to the merchant's website 133.
  • the payment processor 132 can interact with an acquirer or the financial institution associated with the payment information to authorize the purchase.
  • Block 335 is discussed in further detail in connection with Figure 4. [0062]
  • the merchant's website 133 sends a message including a receipt to the digital wallet 111.
  • the receipt can include information associated with the purchase, such as a list of products purchased, a description of each product purchased, the price for each product purchased, a product category for each product purchased, a total price, a stock keeping unit (SKU) or similar product identifier for each product purchased, taxes paid, rebates for one or more of the products purchased, payment method used, discounts applied, the time and/or date of purchase, warranty information for one or more of the products purchased, or other suitable information.
  • the receipt also can include information regarding the merchant associated with the merchant system 130, including a name of the merchant, a description of the merchant, the URL of the merchant's website 133, and other suitable information regarding the merchant or the merchant system 130.
  • the digital wallet 111 stores the receipt in the data storage unit 113.
  • the digital wallet 111 can employ the local storage functionality of the web browser application to store the receipt in the data storage unit 113.
  • the digital wallet 111 synchronizes with the cloud computing environment 150 by sending the receipt to the web server 151.
  • the web server 151 stores, in the data storage unit 152, the received receipt in the user's digital wallet account with the cloud computing environment 150. From step 350, the method 300 ends.
  • FIG 4 is a flow chart depicting a method 335 for a digital wallet to interact with a merchant website 133 to complete a purchase, in accordance with certain exemplary embodiments, as referenced in step 335 of Figure 3.
  • the merchant's website 133 attaches to the digital wallet 111 by establishing a connection between the website 133 and the digital wallet 111.
  • the digital wallet 111 and the merchant's website 133 establish a secure connection for communication between the digital wallet 111 and the merchant's website 133.
  • the digital wallet 111 may authenticate the merchant's website 133 prior to establishing the secure connection. For example, the digital wallet 111 may compare the merchant name, the URL of the merchant's website 133, or the IP address of the merchant's website 133 to a list of known trusted or known non-trusted merchants prior to establishing the secure connection. If the merchant system 130 is not trusted by the digital wallet 111, then the digital wallet 111 will not authorize the secure connection, rather the digital wallet 111 detaches from the merchant's website 133 by disconnecting the connection between the website 133 and the digital wallet 111.
  • the merchant's website 133 transmits a purchase request message to the digital wallet 111.
  • the purchase request message includes a request for payment information from the digital wallet 111 to complete the purchase.
  • the purchase request message also can include information regarding the product(s) for purchase, such as a name and/or description of each product, a price for each product, a total price for all products, taxes, shipping charges, handling charges, other charges, a SKU or other product identifier for each product, shipping options and associated costs, and/or a discount amount for each product.
  • the purchase request message also can include information regarding the merchant, such as the merchant's name, a description of the merchant, and/or payment methods accepted by the merchant (for example, VISA, MASTERCARD, debit card, or other payment method).
  • the purchase request message also can include a request for the user 101 to provide additional information. This request can be configured by the merchant to solicit additional information from the user 101, such as an e-mail address or a loyalty rewards account number.
  • the digital wallet 111 receives the purchase request message from the merchant's website 133 and interacts with the user 101 to confirm the purchase.
  • this interaction includes the digital wallet 111 presenting a user interface on the user device 110 that displays information associated with the purchase to the user 101 and requests confirmation to complete the purchase.
  • the information displayed by the digital wallet 111 may include some or all of the information included in the purchase request message.
  • the user interface displayed by the digital wallet 111 also enables the user 101 to select from multiple payment options stored by the digital wallet 111.
  • the user interface also may allow the user 101 to select or update shipping information.
  • the digital wallet 111 may block the user from using a payment option not accepted by the merchant system 130 as indicated in the purchase request message.
  • the user interface also may prompt the user 101 to enter information requested by the merchant system 130 in the purchase request message.
  • the user 101 actuates a link or button control to confirm the purchase. If the user 101 does not want to confirm the purchase, the user 101 selects a "cancel" link or button control to cancel the purchase, thereby terminating the session between the digital wallet 111 and the website 133.
  • the digital wallet 111 In block 425, if the user 101 confirmed the purchase in block 420, the digital wallet 111 generates and transmits a merchant request message to the merchant's website 133.
  • the merchant request message includes confirmation of the purchase and payment information to use in completing the purchase.
  • the merchant request message can include the form of payment and all information needed to process that payment (for example, credit card number), shipping method, shipping address, e-mail address, user name, and any other information for the purchase transaction.
  • the merchant request message also can include the information in the purchase request message and any information requested by the merchant system 130.
  • the digital wallet 111 can automatically retrieve payment information for a selected payment option from the data storage unit 113 to include in the merchant request message upon confirmation from the user 101 and/or a selection of a payment option by the user 101.
  • the merchant's website 133 receives the merchant request message and sends the payment information to the payment processor 132 for processing.
  • the payment processor 132 interacts with an acquirer or a financial institution associated with the payment information to authorize the payment information and to credit and debit the appropriate accounts for payment from the user 101 to the merchant.
  • the web server 131 receives a message from the payment processor 132 indicating whether the payment information was authorized. If the payment information was authorized, the method 335 follows the "YES" branch to step 340, as referenced in Figure 3. Otherwise, the method 335 follows the "NO" branch to step 440.
  • step 440 the merchant's website 133 notifies the user 101 that the payment information was not authorized and can prompt the user 101 to try another payment option.
  • the method 335 returns to block 420 where the digital wallet 111 interacts with the user 101 to complete the purchase using a different payment option. The user 101 could cancel the purchase if the user 101 does not want to complete the purchase using a different payment option.
  • FIG. 5 is a flow chart depicting a method 500 for installing a digital wallet on a user device, in accordance with certain exemplary embodiments.
  • the user 101 indicates a desire to purchase one or more products at the merchant's website 133.
  • This act performed in block 505 can be substantially similar to steps 315-325 illustrated in Figure 3 and discussed above.
  • the merchant's website 133 scans the user device 110 and/or the web browser application 112 to determine whether a digital wallet 111 is installed on the user device 110 or embedded in the web browser application 112. In block 515, if the merchant's website 133 detects a digital wallet 111, then the method 500 follows the "YES" branch and ends as a digital wallet 111 is already installed on the user device 110. If a digital wallet 111 is not detected by the merchant's website 133, the method 500 follows the "NO" branch to block 520.
  • the merchant's website 133 presents a form for the user 101 to provide payment information to complete the purchase of the one or more products.
  • This form can be similar to a conventional web form having text entry fields for receiving credit card, debit card, or other payment information, shipping address, billing address, e-mail address, name, phone number, and other user information.
  • the form also can include fields for receiving user information and user contact information.
  • the user 101 completes the form by providing the requested information and submits the form to the merchant's website 133.
  • the merchant system 130 processes the received payment information and completes the transaction.
  • the merchant's website 133 prompts the user 101 to download and install the digital wallet 111 on the user device 110.
  • the merchant's website 133 downloads and initiates the installation of the digital wallet 111 on the user device 110.
  • the digital wallet 111 can prompt the user 101 to set up a digital wallet account at the cloud computing environment.
  • the user 101 can opt-in or opt-out of this feature and also can select to install or activate certain features only. If the user 101 opts-in to the digital wallet account, the digital wallet 111 can obtain information from the user 101 for the account, such as payment information, contact information, preferred shipping information, and a user name and password for security purposes.
  • the installed digital wallet 111 can interact with the merchant's website 133 to obtain the payment information used to complete the purchase and a receipt for the purchase.
  • the digital wallet 111 stores the payment information and the receipt in the data storage unit 113. If the user 101 elected to create a digital wallet account with the cloud computing environment, the digital wallet 111 synchronizes the receipt and the payment information with the digital wallet account.
  • the installation of the digital wallet 111 on user device 110 can occur prior to step 520, whereby the user downloads the digital wallet application 111, provides the payment and user information for storage by the digital wallet 111 on the date storage unit 113, and then completes the purchase with the website 133 via the digital wallet 111.
  • the exemplary embodiments described herein can be used with computer hardware and software that perform the methods and processing functions described previously.
  • the systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry.
  • the software can be stored on computer-readable media.
  • computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto -optical media, CD-ROM, etc.
  • Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.

Abstract

L'invention a trait à un portefeuille numérique qui est conçu pour le commerce au moyen d'un dispositif électronique mobile (ou d'un dispositif électronique qui n'est pas mobile) et qui rend ce commerce rapide, pratique et sécurisé, ce portefeuille numérique mémorisant des informations associées à des transactions, telles que des confirmations d'achat et des reçus. Ledit portefeuille numérique peut mémoriser des informations destinées à être utilisées dans des transactions, y compris des informations associées à un ou plusieurs comptes d'opérations financières, des informations sur l'utilisateur et des informations d'expédition. Pour mener à bien un achat en ligne, ce portefeuille numérique peut interagir avec le site Web d'un vendeur afin d'obtenir des informations concernant ledit achat. Le portefeuille numérique comprend une interface utilisateur qui permet à l'utilisateur de vérifier et de confirmer les informations d'achat. Grâce à ladite interface utilisateur, l'utilisateur peut également faire un choix parmi plusieurs options de paiement, personnaliser les informations d'expédition ou donner des informations demandées par le vendeur. Le portefeuille numérique peut transmettre la confirmation de l'utilisateur au site Web du vendeur et recevoir un reçu correspondant à l'achat. Le portefeuille numérique peut mémoriser le reçu et le synchroniser avec un emplacement de mémoire distant.
PCT/US2011/065363 2010-12-17 2011-12-16 Portefeuille numérique WO2012083113A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2011343638A AU2011343638B2 (en) 2010-12-17 2011-12-16 Digital wallet
CA2814115A CA2814115C (fr) 2010-12-17 2011-12-16 Portefeuille numerique

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US201061424611P 2010-12-17 2010-12-17
US201061424610P 2010-12-17 2010-12-17
US61/424,611 2010-12-17
US61/424,610 2010-12-17
US13/235,167 US20120158654A1 (en) 2010-12-17 2011-09-16 Receipt storage in a digital wallet
US13/235,167 2011-09-16
US13/277,182 2011-10-19
US13/277,182 US9691055B2 (en) 2010-12-17 2011-10-19 Digital wallet

Publications (2)

Publication Number Publication Date
WO2012083113A2 true WO2012083113A2 (fr) 2012-06-21
WO2012083113A3 WO2012083113A3 (fr) 2013-01-10

Family

ID=46245380

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2011/065363 WO2012083113A2 (fr) 2010-12-17 2011-12-16 Portefeuille numérique

Country Status (3)

Country Link
AU (1) AU2011343638B2 (fr)
CA (1) CA2814115C (fr)
WO (1) WO2012083113A2 (fr)

Cited By (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2015100709B4 (en) * 2014-05-29 2016-03-10 Apple Inc. User interface for payments
US9324067B2 (en) 2014-05-29 2016-04-26 Apple Inc. User interface for payments
US9547419B2 (en) 2014-09-02 2017-01-17 Apple Inc. Reduced size configuration interface
US9574896B2 (en) 2015-02-13 2017-02-21 Apple Inc. Navigation user interface
US9691055B2 (en) 2010-12-17 2017-06-27 Google Inc. Digital wallet
US9842330B1 (en) 2016-09-06 2017-12-12 Apple Inc. User interfaces for stored-value accounts
US9847999B2 (en) 2016-05-19 2017-12-19 Apple Inc. User interface for a device requesting remote authorization
US9898642B2 (en) 2013-09-09 2018-02-20 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US9940637B2 (en) 2015-06-05 2018-04-10 Apple Inc. User interface for loyalty accounts and private label accounts
US9967401B2 (en) 2014-05-30 2018-05-08 Apple Inc. User interface for phone call routing among devices
US10066959B2 (en) 2014-09-02 2018-09-04 Apple Inc. User interactions for a mapping application
WO2018175006A1 (fr) * 2017-03-23 2018-09-27 Mastercard International Incorporated Systèmes et procédés de génération dynamique d'enregistrements personnalisés
US10142835B2 (en) 2011-09-29 2018-11-27 Apple Inc. Authentication with secondary approver
US10216351B2 (en) 2015-03-08 2019-02-26 Apple Inc. Device configuration user interface
US10250735B2 (en) 2013-10-30 2019-04-02 Apple Inc. Displaying relevant user interface objects
US10255595B2 (en) 2015-02-01 2019-04-09 Apple Inc. User interface for payments
US10332079B2 (en) 2015-06-05 2019-06-25 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US10339293B2 (en) 2014-08-15 2019-07-02 Apple Inc. Authenticated device used to unlock another device
US10395128B2 (en) 2017-09-09 2019-08-27 Apple Inc. Implementation of biometric authentication
US10484384B2 (en) 2011-09-29 2019-11-19 Apple Inc. Indirect authentication
US10496808B2 (en) 2016-10-25 2019-12-03 Apple Inc. User interface for managing access to credentials for use in an operation
US10521579B2 (en) 2017-09-09 2019-12-31 Apple Inc. Implementation of biometric authentication
US10546289B1 (en) 2015-12-30 2020-01-28 Wells Fargo Bank, N.A. Mobile wallets with automatic element selection
US10621581B2 (en) 2016-06-11 2020-04-14 Apple Inc. User interface for transactions
US10783576B1 (en) 2019-03-24 2020-09-22 Apple Inc. User interfaces for managing an account
US10853783B1 (en) 2015-12-30 2020-12-01 Wells Fargo Bank, N.A. Processing online transactions with an intermediary system
US10860199B2 (en) 2016-09-23 2020-12-08 Apple Inc. Dynamically adjusting touch hysteresis based on contextual data
US10860096B2 (en) 2018-09-28 2020-12-08 Apple Inc. Device control using gaze information
US10902405B1 (en) 2016-05-11 2021-01-26 Wells Fargo Bank, N.A. Transient mobile wallets
US10956550B2 (en) 2007-09-24 2021-03-23 Apple Inc. Embedded authentication systems in an electronic device
US11037150B2 (en) 2016-06-12 2021-06-15 Apple Inc. User interfaces for transactions
US11100349B2 (en) 2018-09-28 2021-08-24 Apple Inc. Audio assisted enrollment
US11169830B2 (en) 2019-09-29 2021-11-09 Apple Inc. Account management user interfaces
US11170085B2 (en) 2018-06-03 2021-11-09 Apple Inc. Implementation of biometric authentication
US11477609B2 (en) 2019-06-01 2022-10-18 Apple Inc. User interfaces for location-related communications
US11481094B2 (en) 2019-06-01 2022-10-25 Apple Inc. User interfaces for location-related communications
US11676373B2 (en) 2008-01-03 2023-06-13 Apple Inc. Personal computing device control using face detection and recognition
US11681537B2 (en) 2019-09-29 2023-06-20 Apple Inc. Account management user interfaces
US11782573B2 (en) 2020-04-10 2023-10-10 Apple Inc. User interfaces for enabling an activity
US11816194B2 (en) 2020-06-21 2023-11-14 Apple Inc. User interfaces for managing secure operations
US11868989B1 (en) 2015-12-30 2024-01-09 Wells Fargo Bank, N.A. Mobile wallets and companion smart cards

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050088517A (ko) * 2004-03-02 2005-09-07 신재득 무선인터넷 단말기를 이용한 신용카드 결제 방법 및 단말기상에서 실행 가능한 프로그램
WO2008005018A2 (fr) * 2006-07-06 2008-01-10 Firethorn Holdings, Llc Procédés et systèmes de conduite de transactions financières dans un environnement mobile
US20100125495A1 (en) * 2008-11-17 2010-05-20 Smith Steven M System and method of providing a mobile wallet at a mobile telephone
WO2010110625A2 (fr) * 2009-03-26 2010-09-30 Park Jung Chual Procédé de service de portefeuille électronique et système basé sur une application d'écran de veille

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9167000B2 (en) * 2006-02-14 2015-10-20 Ca, Inc. Dynamic threat event management system and method
US8489067B2 (en) * 2006-07-06 2013-07-16 Qualcomm Incorporated Methods and systems for distribution of a mobile wallet for a mobile device
US20100217682A1 (en) * 2009-02-26 2010-08-26 Research In Motion Limited System and method for capturing user inputs in electronic forms

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050088517A (ko) * 2004-03-02 2005-09-07 신재득 무선인터넷 단말기를 이용한 신용카드 결제 방법 및 단말기상에서 실행 가능한 프로그램
WO2008005018A2 (fr) * 2006-07-06 2008-01-10 Firethorn Holdings, Llc Procédés et systèmes de conduite de transactions financières dans un environnement mobile
US20100125495A1 (en) * 2008-11-17 2010-05-20 Smith Steven M System and method of providing a mobile wallet at a mobile telephone
WO2010110625A2 (fr) * 2009-03-26 2010-09-30 Park Jung Chual Procédé de service de portefeuille électronique et système basé sur une application d'écran de veille

Cited By (109)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10956550B2 (en) 2007-09-24 2021-03-23 Apple Inc. Embedded authentication systems in an electronic device
US11468155B2 (en) 2007-09-24 2022-10-11 Apple Inc. Embedded authentication systems in an electronic device
US11676373B2 (en) 2008-01-03 2023-06-13 Apple Inc. Personal computing device control using face detection and recognition
US9691055B2 (en) 2010-12-17 2017-06-27 Google Inc. Digital wallet
US11507944B2 (en) 2010-12-17 2022-11-22 Google Llc Digital wallet
US11755712B2 (en) 2011-09-29 2023-09-12 Apple Inc. Authentication with secondary approver
US10142835B2 (en) 2011-09-29 2018-11-27 Apple Inc. Authentication with secondary approver
US11200309B2 (en) 2011-09-29 2021-12-14 Apple Inc. Authentication with secondary approver
US10419933B2 (en) 2011-09-29 2019-09-17 Apple Inc. Authentication with secondary approver
US10516997B2 (en) 2011-09-29 2019-12-24 Apple Inc. Authentication with secondary approver
US10484384B2 (en) 2011-09-29 2019-11-19 Apple Inc. Indirect authentication
US9898642B2 (en) 2013-09-09 2018-02-20 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US11768575B2 (en) 2013-09-09 2023-09-26 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on unlock inputs
US10803281B2 (en) 2013-09-09 2020-10-13 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US10055634B2 (en) 2013-09-09 2018-08-21 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US10410035B2 (en) 2013-09-09 2019-09-10 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US11494046B2 (en) 2013-09-09 2022-11-08 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on unlock inputs
US10262182B2 (en) 2013-09-09 2019-04-16 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on unlock inputs
US10372963B2 (en) 2013-09-09 2019-08-06 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces based on fingerprint sensor inputs
US11287942B2 (en) 2013-09-09 2022-03-29 Apple Inc. Device, method, and graphical user interface for manipulating user interfaces
US10972600B2 (en) 2013-10-30 2021-04-06 Apple Inc. Displaying relevant user interface objects
US10250735B2 (en) 2013-10-30 2019-04-02 Apple Inc. Displaying relevant user interface objects
US11316968B2 (en) 2013-10-30 2022-04-26 Apple Inc. Displaying relevant user interface objects
US10043185B2 (en) 2014-05-29 2018-08-07 Apple Inc. User interface for payments
US10482461B2 (en) 2014-05-29 2019-11-19 Apple Inc. User interface for payments
US10282727B2 (en) 2014-05-29 2019-05-07 Apple Inc. User interface for payments
US10902424B2 (en) 2014-05-29 2021-01-26 Apple Inc. User interface for payments
US9324067B2 (en) 2014-05-29 2016-04-26 Apple Inc. User interface for payments
US10796309B2 (en) 2014-05-29 2020-10-06 Apple Inc. User interface for payments
US9483763B2 (en) 2014-05-29 2016-11-01 Apple Inc. User interface for payments
US10748153B2 (en) 2014-05-29 2020-08-18 Apple Inc. User interface for payments
US10977651B2 (en) 2014-05-29 2021-04-13 Apple Inc. User interface for payments
US11836725B2 (en) 2014-05-29 2023-12-05 Apple Inc. User interface for payments
US9911123B2 (en) 2014-05-29 2018-03-06 Apple Inc. User interface for payments
AU2015100709B4 (en) * 2014-05-29 2016-03-10 Apple Inc. User interface for payments
US10438205B2 (en) 2014-05-29 2019-10-08 Apple Inc. User interface for payments
US9967401B2 (en) 2014-05-30 2018-05-08 Apple Inc. User interface for phone call routing among devices
US10616416B2 (en) 2014-05-30 2020-04-07 Apple Inc. User interface for phone call routing among devices
US10178234B2 (en) 2014-05-30 2019-01-08 Apple, Inc. User interface for phone call routing among devices
US10339293B2 (en) 2014-08-15 2019-07-02 Apple Inc. Authenticated device used to unlock another device
US11126704B2 (en) 2014-08-15 2021-09-21 Apple Inc. Authenticated device used to unlock another device
US11733055B2 (en) 2014-09-02 2023-08-22 Apple Inc. User interactions for a mapping application
US10579225B2 (en) 2014-09-02 2020-03-03 Apple Inc. Reduced size configuration interface
US11609681B2 (en) 2014-09-02 2023-03-21 Apple Inc. Reduced size configuration interface
US10324590B2 (en) 2014-09-02 2019-06-18 Apple Inc. Reduced size configuration interface
US10914606B2 (en) 2014-09-02 2021-02-09 Apple Inc. User interactions for a mapping application
US10066959B2 (en) 2014-09-02 2018-09-04 Apple Inc. User interactions for a mapping application
US10936164B2 (en) 2014-09-02 2021-03-02 Apple Inc. Reduced size configuration interface
US9547419B2 (en) 2014-09-02 2017-01-17 Apple Inc. Reduced size configuration interface
US10255595B2 (en) 2015-02-01 2019-04-09 Apple Inc. User interface for payments
US9574896B2 (en) 2015-02-13 2017-02-21 Apple Inc. Navigation user interface
US10024682B2 (en) 2015-02-13 2018-07-17 Apple Inc. Navigation user interface
US10216351B2 (en) 2015-03-08 2019-02-26 Apple Inc. Device configuration user interface
US10254911B2 (en) 2015-03-08 2019-04-09 Apple Inc. Device configuration user interface
US11079894B2 (en) 2015-03-08 2021-08-03 Apple Inc. Device configuration user interface
US10600068B2 (en) 2015-06-05 2020-03-24 Apple Inc. User interface for loyalty accounts and private label accounts
US11734708B2 (en) 2015-06-05 2023-08-22 Apple Inc. User interface for loyalty accounts and private label accounts
US9940637B2 (en) 2015-06-05 2018-04-10 Apple Inc. User interface for loyalty accounts and private label accounts
US10026094B2 (en) 2015-06-05 2018-07-17 Apple Inc. User interface for loyalty accounts and private label accounts
US11321731B2 (en) 2015-06-05 2022-05-03 Apple Inc. User interface for loyalty accounts and private label accounts
US11783305B2 (en) 2015-06-05 2023-10-10 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US10332079B2 (en) 2015-06-05 2019-06-25 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US10990934B2 (en) 2015-06-05 2021-04-27 Apple Inc. User interface for loyalty accounts and private label accounts for a wearable device
US11625705B1 (en) 2015-12-30 2023-04-11 Wells Fargo Bank, N.A. Processing online transactions with an intermediary system
US10853783B1 (en) 2015-12-30 2020-12-01 Wells Fargo Bank, N.A. Processing online transactions with an intermediary system
US10546289B1 (en) 2015-12-30 2020-01-28 Wells Fargo Bank, N.A. Mobile wallets with automatic element selection
US11868989B1 (en) 2015-12-30 2024-01-09 Wells Fargo Bank, N.A. Mobile wallets and companion smart cards
US11769136B1 (en) 2016-05-11 2023-09-26 Wells Fargo Bank, N.A. Transient mobile wallets
US10902405B1 (en) 2016-05-11 2021-01-26 Wells Fargo Bank, N.A. Transient mobile wallets
US11206309B2 (en) 2016-05-19 2021-12-21 Apple Inc. User interface for remote authorization
US9847999B2 (en) 2016-05-19 2017-12-19 Apple Inc. User interface for a device requesting remote authorization
US10749967B2 (en) 2016-05-19 2020-08-18 Apple Inc. User interface for remote authorization
US10334054B2 (en) 2016-05-19 2019-06-25 Apple Inc. User interface for a device requesting remote authorization
US11481769B2 (en) 2016-06-11 2022-10-25 Apple Inc. User interface for transactions
US10621581B2 (en) 2016-06-11 2020-04-14 Apple Inc. User interface for transactions
US11900372B2 (en) 2016-06-12 2024-02-13 Apple Inc. User interfaces for transactions
US11037150B2 (en) 2016-06-12 2021-06-15 Apple Inc. User interfaces for transactions
US9842330B1 (en) 2016-09-06 2017-12-12 Apple Inc. User interfaces for stored-value accounts
US11074572B2 (en) 2016-09-06 2021-07-27 Apple Inc. User interfaces for stored-value accounts
US10860199B2 (en) 2016-09-23 2020-12-08 Apple Inc. Dynamically adjusting touch hysteresis based on contextual data
US10496808B2 (en) 2016-10-25 2019-12-03 Apple Inc. User interface for managing access to credentials for use in an operation
US11574041B2 (en) 2016-10-25 2023-02-07 Apple Inc. User interface for managing access to credentials for use in an operation
WO2018175006A1 (fr) * 2017-03-23 2018-09-27 Mastercard International Incorporated Systèmes et procédés de génération dynamique d'enregistrements personnalisés
US11741451B2 (en) 2017-03-23 2023-08-29 Mastercard International Incorporated Systems and methods for dynamically generating customized records
US10872256B2 (en) 2017-09-09 2020-12-22 Apple Inc. Implementation of biometric authentication
US10395128B2 (en) 2017-09-09 2019-08-27 Apple Inc. Implementation of biometric authentication
US10410076B2 (en) 2017-09-09 2019-09-10 Apple Inc. Implementation of biometric authentication
US11393258B2 (en) 2017-09-09 2022-07-19 Apple Inc. Implementation of biometric authentication
US10521579B2 (en) 2017-09-09 2019-12-31 Apple Inc. Implementation of biometric authentication
US11386189B2 (en) 2017-09-09 2022-07-12 Apple Inc. Implementation of biometric authentication
US10783227B2 (en) 2017-09-09 2020-09-22 Apple Inc. Implementation of biometric authentication
US11765163B2 (en) 2017-09-09 2023-09-19 Apple Inc. Implementation of biometric authentication
US11170085B2 (en) 2018-06-03 2021-11-09 Apple Inc. Implementation of biometric authentication
US11928200B2 (en) 2018-06-03 2024-03-12 Apple Inc. Implementation of biometric authentication
US11100349B2 (en) 2018-09-28 2021-08-24 Apple Inc. Audio assisted enrollment
US10860096B2 (en) 2018-09-28 2020-12-08 Apple Inc. Device control using gaze information
US11809784B2 (en) 2018-09-28 2023-11-07 Apple Inc. Audio assisted enrollment
US11619991B2 (en) 2018-09-28 2023-04-04 Apple Inc. Device control using gaze information
US11610259B2 (en) 2019-03-24 2023-03-21 Apple Inc. User interfaces for managing an account
US11688001B2 (en) 2019-03-24 2023-06-27 Apple Inc. User interfaces for managing an account
US10783576B1 (en) 2019-03-24 2020-09-22 Apple Inc. User interfaces for managing an account
US11328352B2 (en) 2019-03-24 2022-05-10 Apple Inc. User interfaces for managing an account
US11669896B2 (en) 2019-03-24 2023-06-06 Apple Inc. User interfaces for managing an account
US11481094B2 (en) 2019-06-01 2022-10-25 Apple Inc. User interfaces for location-related communications
US11477609B2 (en) 2019-06-01 2022-10-18 Apple Inc. User interfaces for location-related communications
US11169830B2 (en) 2019-09-29 2021-11-09 Apple Inc. Account management user interfaces
US11681537B2 (en) 2019-09-29 2023-06-20 Apple Inc. Account management user interfaces
US11782573B2 (en) 2020-04-10 2023-10-10 Apple Inc. User interfaces for enabling an activity
US11816194B2 (en) 2020-06-21 2023-11-14 Apple Inc. User interfaces for managing secure operations

Also Published As

Publication number Publication date
WO2012083113A3 (fr) 2013-01-10
CA2814115A1 (fr) 2012-06-21
CA2814115C (fr) 2017-01-17
AU2011343638B2 (en) 2015-03-19
AU2011343638A1 (en) 2013-05-02

Similar Documents

Publication Publication Date Title
US20230082253A1 (en) Digital Wallet
AU2011343638B2 (en) Digital wallet
US20120158654A1 (en) Receipt storage in a digital wallet
US10592884B2 (en) Split tender in a prepaid architecture
US10223677B2 (en) Completion of online payment forms and recurring payments by a payment provider systems and methods
US10152705B2 (en) Quick payment using mobile device binding
US20240062183A1 (en) System and method for integrating data from a remote server with a client application
US9953314B2 (en) System, method, and computer-readable storage medium for payment of online purchases via a portable computing device
US11250414B2 (en) Cloud based system for engaging shoppers at or near physical stores
US10147112B2 (en) Delayed processing window in a prepaid architecture
AU2013207664B2 (en) Processing payment information for online orders at a local merchant's point of sale
US9430796B1 (en) Direct purchase from user-received advertisement
KR102053384B1 (ko) 세금 환급 서비스를 제공하는 기법
US20160140633A1 (en) Presenting user interface elements and accepting input optimistically when application state is unknown
US20220245662A1 (en) Redemption Code Auto-Complete for Online Offers and Tracking
JP7463452B2 (ja) 情報処理装置、情報処理方法及び情報処理プログラム
KR20190135443A (ko) 세금 환급 서비스를 제공하는 기법

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

Country of ref document: EP

Kind code of ref document: A2

ENP Entry into the national phase in:

Ref document number: 2814115

Country of ref document: CA

ENP Entry into the national phase in:

Ref document number: 2011343638

Country of ref document: AU

Date of ref document: 20111216

Kind code of ref document: A

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11849088

Country of ref document: EP

Kind code of ref document: A2