Abstract:
Mobile device payments using barcodes are displayed on mobile devices and scanned by merchants at checkout counters. When a customer is ready to tender a payment to a merchant, instead of using a credit card, cash, or check, the customer activates an application on his mobile device. The mobile device includes or obtains information about the payment system of this merchant. Furthermore, the mobile device includes or obtains information about the customer/mobile device user and then uses these two pieces of information to generate and display a barcode that encodes customer payment information specific to this merchant. The barcode is scanned by one scan or one touch at the checkout counter and processed to retrieve customer records from a database of the payment processing system. These records are then used to transfer funds between the merchant and customer, obtain discounts, and/or perform other retail transactions.

Description:
RELATED PATENT APPLICATION AND INCORPORATION BY REFERENCE 
       [0001]    This application is a continuation-in-part of U.S. patent application Ser. No. 13/185,491, entitled ‘FACILITATING MOBILE DEVICE PAYMENTS USING PRODUCT CODE SCANNING,’ filed on Jul. 18, 2011, and U.S. patent application Ser. No. 14/979,613,“ONE-SCAN AND ONE-TOUCH PAYMENT AND BUYING USING HAPTIC CONTROL VIA MESSAGING AND CALLING MULTIMEDIA SYSTEM ON MOBILE AND WEARABLE DEVICE, CURRENCY TOKEN INTERFACE, POINT OF SALE DEVICE, AND ELECTRONIC PAYMENT CARD&#39;, filed on Dec. 28, 2015, and U.S. patent application Ser. No. 14/957,644, entitled ‘SYSTEMS AND METHODS FOR MOBILE APPLICATION, WEARABLE APPLICATION, TRANSACTIONAL MESSAGING, CALLING, DIGITAL MULTIMEDIA CAPTURE AND PAYMENT TRANSACTIONS’, filed on Dec. 3, 2015, which is Continuation-in-Part of U.S. patent application Ser. No. 14/815,988, entitled ‘SYSTEMS AND METHODS FOR MOBILE APPLICATION, WEARABLE APPLICATION, TRANSACTIONAL MESSAGING, CALLING, DIGITAL MULTIMEDIA CAPTURE AND PAYMENT TRANSACTIONS’, filed on Aug. 1, 2015, which claims priority to U.S. patent application Ser. No. 12/749,412, entitled ‘EFFICIENT TRANSACTIONAL MESSAGING BETWEEN LOOSELY COUPLED CLIENT AND SERVER OVER MULTIPLE INTERMITTENT NETWORKS WITH POLICY BASED ROUTING’, filed on Mar. 29, 2010, and U.S. patent application Ser. No. 14/034,509, entitled ‘EFFICIENT TRANSACTIONAL MESSAGING BETWEEN LOOSELY COUPLED CLIENT AND SERVER OVER MULTIPLE INTERMITTENT NETWORKS WITH POLICY BASED ROUTING’, filed on Sep. 23, 2013, which is Continuation-in-Part of U.S. patent application Ser. No. 10/677,098, entitled ‘EFFICIENT TRANSACTIONAL MESSAGING BETWEEN LOOSELY COUPLED CLIENT AND SERVER OVER MULTIPLE INTERMITTENT NETWORKS WITH POLICY BASED ROUTING’, filed on Sep. 30, 2003, which claims priority to U.S. Provisional Patent Application No. 60/415,546, entitled ‘DATA PROCESSING SYSTEM’, filed on Oct. 1, 2002, which are incorporated herein by reference in its entirety. 
     
    
     SUMMARY OF INVENTION 
       [0002]    (1) Field of the Invention 
         [0003]    This application relates generally to data processing, and more specifically to methods and systems for one-touch and one-scan buying and paying performed via a mobile and wearable device. 
         [0004]    (2) Background 
         [0005]    Mobile payments generally refer to payment operations performed via a mobile or wearable device. The operations performed via mobile and wearable devices may include electronic commerce transactions, retail purchasing, micropayments, and other daily payments. Mobile payments may utilize credit cards, debit cards, gift cards, and virtual currencies. While mobile payments facilitate and stimulate the trade, the procedure of providing financial details and authenticating of identity may be tedious and time-consuming. Therefore, the convenience of mobile payments for daily micropayments is hindered. 
       SUMMARY 
       [0006]    This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. 
         [0007]    Provided are computer implemented methods and systems for messaging, calling, and one-touch and one-scan payments and buying via a mobile and wearable device. Using the methods or systems described herein a user may perform facilitated electronic payments from any location. For this purpose, the user may register with the messaging, calling, and one-touch and one-scan payment and buying system. During the registration the user may provide his financial information. The financial information may include bank account information, credit card information, debit card information, gift card information, prepaid card information, insurance account information, merchant account information, mobile currency information, digital money account, SDK payment information, in-app payment information, social networking payment information, prepaid card information, API payment information, mobile account payment information, mobile currency information, and so forth. When required, the user may activate a haptic control associated with a messaging, calling, and one-touch and one-scan payment and buying system. The haptic control may be displayed over the video output of the device and overlap other applications or pages. The haptic control may provide for mode selection elements associated with a payment mode, a messaging mode, a calling mode, and a multimedia capture mode. Through the haptic control the messaging, calling, and one-touch and one-scan payment and buying system may receive the selection of the payment mode via the mode selection elements of the haptic control from a user. Upon the selection, context may be extracted from the display of the mobile and wearable device. Based on the context, a payment transaction type which the user intends to perform may be determined. The payment transaction type may include a payment receiving transaction and a payment sending transaction. Based on the determining, a transaction request may be generated using data of the extraction and the financial information of the user provided during the registration. 
         [0008]    To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0009]    Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: 
           [0010]      FIG. 1  is a block diagram showing an environment within which a system for messaging, calling, and one-touch and one-scan payment and buying system and a method of using thereof can be implemented, in accordance with an example embodiment. 
           [0011]      FIG. 2  is a block diagram showing various modules of the messaging, calling, and one-touch and one-scan payment and buying system, in accordance with certain embodiments. 
           [0012]      FIG. 3  is a flow chart illustrating a method for messaging, calling, and one-touch and one-scan payments and buying via a mobile and wearable device, in accordance with certain embodiments. 
           [0013]      FIG. 4  is a block diagram illustrating a haptic control, in accordance with certain embodiments. 
           [0014]      FIG. 5  is a block diagram illustrating a one-touch and one-scan payment and buying operation using the messaging, calling, and one-touch and one-scan payment and buying system, in accordance with certain embodiments. 
           [0015]      FIG. 6  is a block diagram showing various modules of a messaging, calling, and one-touch and one-scan payment and buying mobile service using a one-touch button, in accordance with certain embodiments. 
       
    
    
     DETAILED DESCRIPTION 
       [0016]    In the following description, numerous specific details are set forth in order to provide a thorough understanding of the presented concepts. The presented concepts may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail so as to not unnecessarily obscure the described concepts. While some concepts will be described in conjunction with the specific embodiments, it will be understood that these embodiments are not intended to be limiting. 
         [0017]    Various computer implemented methods and systems for messaging, calling, and one-touch and one-scan payments and buying via a mobile and wearable device are described herein. The described system enables a user to make and request payments using a mobile device by one touch. To facilitate access to the system, the user initiates the system. When the system is initiated, a one-touch button is shown on a display of the mobile device on top of other applications and/or widgets. The one-touch button has at least three controls to activate messaging, calling, or one-touch and one-scan payment. One-touch payment control, when activated, determines whether the user intends to make a payment or to request a payment by the context in view on the display and performs the corresponding operation. Such accelerated payment procedure may facilitate electronic purchases and stimulate electronic trade. 
         [0018]    Referring now to the drawings,  FIG. 1  illustrates an environment  100  within which messaging, calling, and one-touch and one-scan payment and buying system and a method of using thereof can be implemented. The environment  100  may include a user  120 , a client device  130 , network  110 , a messaging, calling, and one-touch and one-scan payment and buying system  200 . On a user request, the messaging, calling, and one-touch and one-scan payment and buying system  200  may provide a haptic control on a display of the client device  130 . The haptic control may include, for example, a one-touch button. The client device  130   
         [0019]    Via the haptic control, the user  120  may exchange messages  160  with a recipient  140 , make calls  170 , and perform or request one-touch and one-scan payments  180 . The messages  160 , calls  170 , and one-touch and one-scan payments  180  are transmitted to the system  200  and further to the recipient  140  or payee (not shown) via the network  110  using the client device  130   
         [0020]    The network  110  may include the Internet or any other network capable of communicating data between devices. Suitable networks may include or interface with any one or more of, for instance, a local intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtual private network (VPN), a storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Furthermore, communications may also include links to any of a variety of wireless networks, including WAP (Wireless Application Protocol), GPRS (General Packet Radio Service), GSM (Global System for Mobile Communication), CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access), cellular phone networks, GPS (Global Positioning System), CDPD (cellular digital packet data), RIM (Research in Motion, Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-based radio frequency network. The network  110  can further include or interface with any one or more of an RS-232 serial connection, an IEEE-1394 (Firewire) connection, a Fiber Channel connection, an IrDA (infrared) port, a SCSI (Small Computer Systems Interface) connection, a Universal Serial Bus (USB) connection or other wired or wireless, digital or analog interface or connection, mesh or Digi® networking. The network  110   
         [0021]      FIG. 2  is a block diagram showing various modules of the messaging, calling, and one-touch and one-scan payment and buying system  200 , in accordance with certain embodiments. The system  200  may comprise a processor  202  a database  204 , and a haptic control  206 . The processor  202  may include a programmable processor, such as a microcontroller, central processing unit (CPU), and so forth. In other embodiments, the processor  202  may include an application-specific integrated circuit (ASIC) or programmable logic array (PLA), such as a field programmable gate array (FPGA), designed to implement the functions performed by the system  200 . Thus, the processor  202  may provide a haptic control associated with a messaging, calling, and one-touch and one-scan payment and buying system. The haptic control may be represented, for example, by a one-touch button shown on a display of a mobile and wearable device. The haptic control may overlap other visual elements on the display so that the haptic control was always visible for the user and not hidden by other screens. In some embodiments, the haptic control  206  may be integrated with a mobile application associated with the mobile and wearable device and/or the system  200 . The haptic control may provide mode selection elements associated with a payment mode, a messaging mode, a calling mode, and multimedia capture mode. The processor  202  may further receive the selection of the payment mode via the mode selection element of the haptic control  206  from a user. When the payment mode is selected, the processor may extract context from the display of the mobile and wearable device. The context may include information on a web page, an application screen, or a message in view on the display. For example, the context may include a check-out page of an online shop. Based on the context, the processor  202  may determine a payment transaction type (i.e. a payment receiving transaction or a payment sending transaction) which the user intends to perform. For this purpose, the processor  202  may parse the context and identify key words associated with a specific payment transaction type. For instance, the payment sending transaction may be associated with the following key words: ‘check-out,’ ‘cart,’ and so forth. According to the determined transaction, a transaction request may be sent to a financial institution using the information extracted from the context and financial information of the user stored in the database  204   
         [0022]    The transaction request may be sent without requesting financial information, authorizing, or confirmations from the user. However, in some embodiments, the user, with the help of options of the system  200   
         [0023]    Furthermore, the user may select a messaging mode via the mode selection elements of the haptic control  206 . Then, the processor may provide a messaging interface on the display of the mobile and wearable device. When a message and a choice of a recipient is received from the user via the messaging interface, the processor  202   
         [0024]    If the calling mode is selected via the haptic control  206 , the processor  202  may provide a calling interface on the display of the mobile and wearable device. Via the calling interface, the processor  202   
         [0025]    If the multimedia mode is selected via the haptic control  206 , the processor  202  may initiate one or more sensors to capture multimedia to obtain captured multimedia. The processor  202  may analyze a duration of the single touch to the section element of the one-touch button associated with the multimedia capture mode. Based on the analysis, the processor  202   
         [0026]      FIG. 3  is a flow chart illustrating a method  300  for messaging, calling, and one-touch and one-scan payments and buying via a mobile and wearable device, in accordance with some example embodiments. The method  300  may be performed by logic that may comprise hardware (e.g., dedicated logic, programmable logic, and microcode), software (such as software run on a general-purpose computer system or a dedicated machine), or a combination of both. In one example embodiment, the processing logic resides at the system  200  for providing compensation for using a mobile payment service, and the various elements of the system  200  can perform the method  300   
         [0027]    As shown in  FIG. 3 , the method  300  may commence at operation  302  with receiving payment information associated with a user. The payment information may be also associated with a mobile payment account of the user in a messaging, calling, and one-touch and one-scan payment and buying system. At operation  304 , a unique code encoding the payment information is generated. The unique code is provided to the user at operation  306   
         [0028]    At operation  308   
         [0029]    At operation  310 , a selection of the payment mode via the mode selection elements of the haptic control is received from the user. Upon the selection, context is extracted from the display at operation  312 . Information from the screen in view on the mobile and wearable device and be captured and analyzed to identify the context. Based on the context, a payment transaction type to be performed may be determined at operation  314   
         [0030]    Based on the determining of the payment transaction type, a transaction request associated with the determined payment transaction type may be sent at operation  316   
         [0031]    If the transaction request is associated with the payment sending transaction, a deposit amount associated with the payment sending transaction related to the user may be received at operation  318 . Further, at operation  320   
         [0032]    Furthermore, if the messaging mode is selected via the haptic control, the system  200  of  FIG. 2   
         [0033]    If the calling mode is selected, a calling interface may be provided to the user. The user may select a call recipient in his contacts and make a call request. The system  200  may receive the call request from the user. Based on the call request, the system  200   
         [0034]    On selection of the multimedia mode, one or more sensors may be initiated to capture multimedia to obtain captured multimedia. A duration of the single touch to the section element of the one-touch button associated with the multimedia capture mode may be analyzed. Based on the analysis, a type of the captured multimedia may be determined: an image and a video recording. When the type if determined, the captured multimedia may be recorded to the database according to the type determined based on the duration. For instance, if the duration of the single touch to the section element of the one-touch button associated with the multimedia capture mode is one second, an image is recorded to the database, if the duration is more than one second, a video recording may be stored to the database. 
         [0035]    In an example embodiment, the data of the payment card may be stored into a cloud network. In some embodiments, the data of the payment card may be stored in the cloud network as a token. 
         [0036]    In some embodiments, the transaction request may include a unique code associated with the user. The unique code may encode at least bank account information of the user and a payment amount. In further embodiments, the unique code may be displayed on the mobile and wearable device for scanning by the merchant. 
         [0037]    In a further example embodiment, the system  200  may receive product data based on scanning of the product data by the mobile and wearable device associated with the user. The product data may be associated with one or more products. 
         [0038]    The system  200  may determine that the total price for the one or more products exceeds a predetermined price. 
         [0039]    In some embodiments, the transaction request may include at least a user phone number. In such a case, the payment sending transaction may include sending a payment from a phone account of the user to a merchant account. 
         [0040]    In further embodiments, the payment receiving transaction and the payment sending transaction may be performed by pairing of the mobile and wearable device and a merchant device using a reader. The reader may be connected to the merchant device and plugged into the mobile and wearable device. 
         [0041]    Thus, one-touch and one-scan payment and buying features may improve buying experience for customers and merchant. Additionally, for the user that pays and buys products and services using the mobile application associated with one-touch and one-scan payment and buying, the number of taps and times the user is required to enter a user login (identification number) and a password for future purchases may be minimized. 
         [0042]    In some embodiments, upon launching of the at least one mobile application by the user, a list of payment cards may be provided for selection by the user. The payment cards may be associated with one or more of the following: a bank account, a bank mobile account, a service provider account, a digital currency, a universal national currency token interface, a national digital currency, an electric payment card, and the like. Upon the selection, a token may be sent to the mobile and wearable device. The token may be associated with a selected payment card, and further payments may be performed using the token. 
         [0043]      FIG. 4  is a block diagram  400  illustrating a haptic control, in accordance with certain embodiments. The haptic control  414  may be shown on the display  410  of the mobile and wearable device  412 . The haptic control may include one or more mode selection elements. The mode selection elements may include a messaging mode  402 , a calling mode  404 , and a payment mode  406 . A user  408  may give a haptic command (e.g. touch) to select a desired mode. 
         [0044]    The transaction request may be generated using data of a mobile application or a page from which the payment mode is activated. For example, the user may activate the payment mode from a purchase page of an online store. The payment may be immediately initiated without requesting further details. Data of a payment recipient and a payment amount may be received from the actual page or application and financial information of the user may be stored in the database of the messaging, calling, and one-touch and one-scan payment and buying system  200 . The user financial information may be provided by the user during registration with the messaging, calling, and one-touch and one-scan payment and buying system  200 . 
         [0045]    Alternatively, the transaction request may be generated using data of a page associated with billing In that case, the system  200  may generate a payment request using information extracted from the page as well as the financial information of the user stored in the system  200 . 
         [0046]    Transactions can be associated with transactional payments based on Unstructured Supplementary Service Data (USSD) or Short Message Service (SMS), direct operator billing, credit card mobile payments, online wallets, QR code payments, contactless near field communication (NFC), cloud-based mobile payments, audio signal-based payment, Bluetooth Low Energy (BLE) signal beacon payment, in-application payment, SDK payment, API payment, social networking payment, and direct carrier/bank co-operation. 
         [0047]    Contactless NFC may be used to receive data for the payment request. For example, when the one touch and one-scan payment mode is selected, the user may make a payment for purchases in physical stores or transportation services. The mobile and wearable device may be equipped with a smart card. When a user waves the mobile and wearable device near a radar module, a payment is made. In some cases, the payment may require authentication. The NFC payment could be deducted from a pre-paid account or changed to a mobile or band account directly. NFC payment may include displaying a barcode on the mobile device screen for mobile payment. The payment barcode can include one or more of the following: a linear barcode, a two-dimensional barcode, a three-dimensional barcode, a machine readable code, and so forth. 
         [0048]    The audio channel of the mobile phone may be another wireless interface that is used to receive data for a transaction request. Chip, ultra sound and acoustic features of the mobile and wearable device may support mobile payments. Near sound data transfer (NDST), data over voice and NFC produce audio signatures that the mobile phone can pick up to enable electronic transactions. 
         [0049]    In some embodiments, the payment receiving transaction and the payment sending transaction are performed using a NFC. The NFC may be used to pair the mobile and wearable device and a merchant device by bringing the mobile and wearable device into proximity to the merchant device. The mobile and wearable device and the merchant device may be connected to a cloud network. The financial data and authorizing data associated with the user may be stored in the cloud network. In an example embodiment, upon pairing the mobile and wearable device with the merchant device, a Bluetooth connection between the mobile and wearable device and the merchant device may be established. The payment receiving transaction and the payment sending transaction may include at least a pear-to-pear transaction. 
         [0050]    In some embodiments, a beacon mobile payment sends out a Bluetooth Low Energy (BLE) signal to anyone or any device with mobile application to transfer payment data and get electronic receipt. When a customer checks in, their picture and name may pop up on the retailer&#39;s point-of-sale system, when a sales associate at the store totals a bill on a cash register or a card-reading terminal, the beacon mobile payment user gives verbal confirmation to the associate, who matches the customer with the picture on the POS screen and concludes the transaction. 
         [0051]      FIG. 5  is a block diagram illustrating a one-touch payment operation  500  using the messaging, calling, and one-touch and one-scan payment system, in accordance with certain embodiments. The user selects a payment mode  504  using a one-touch button  502  (i.e. haptic control). The user selection may be transmitted to the system  200 , and the system may determine information on a page  506  in view on the display. The system  200  may automatically provide financial information of the user on the page  506   
         [0052]      FIG. 6  is a block diagram showing various modules of a messaging, calling, and one-touch payment and buying mobile platform shown as a messaging, calling, and one-touch payment mobile service  600  using a one-touch button  608 , in accordance with certain embodiments. The messaging, calling, and one-touch payment mobile service  600  may include a central processing unit (CPU)  604 , for example, associated with a remote server  602 , a database  606  storing financial information of a user, and a one-touch button  608  presented on a device of the user. The CPU  604  may provide the one-touch button  608  on a display of a mobile and wearable device. The one-touch button  608  may overlap other visual elements on the display. The CPU  604  may receive a selection of the payment mode via the mode selection elements of the one-touch button  608  from a user. The selection may include a single touch of the user to the one-touch button  608 . Upon the selection, the CPU  604  may extract context from the display of the mobile and wearable device to determine a payment transaction type which the user intends to perform. Based on the determining, the CPU  604  may send a transaction request to a financial institution using the extraction and financial data stored in the database  606   
         [0053]    In some embodiments, the user may select one of the stored payment accounts to perform a payment. Authentication may be made when the user accesses the messaging, calling, and one-touch payment mobile service  600   
         [0054]    Furthermore, using the messaging, calling, and one-touch payment mobile service  600  the user may create automatic payments. For example, the user may give instructions to transfer $1 to a specific account every week day at 1:25 PM. The messaging, calling, and one-touch payment mobile service  600  may receive the instructions and automatically perform the payment according to the instructions. After a predefined period, for example, after one month, or every week, or every year, the messaging, calling, and one-touch payment mobile service  600 . 
         [0055]    Thus, various systems and methods for messaging, calling, and one-touch and one-scan payments and buying via a mobile and wearable device have been described. Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the system and method described herein. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.