US 8,548,426 B2Grant
Systems and methods to approve electronic payments
Issue Date:2013-10-01
•23 Claims
•15 Drawing Sheets
Abstract
Systems and methods are provided to facilitate online transactions via mobile communications. In one aspect, a system includes a data storage facility to store an account identifier of a user and a phone number of the user and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of different controllers of mobile communications. The converters are configured to communicate with the common format processor in a common format and to communicate with the controllers in different formats. The interchange uses the converters to communicate with the mobile phone of a user to confirm the identity of the user using a user terminal separate from the mobile phone for subsequent payment requests from the user terminal to be fulfilled using the account identifier.
Metadata
Assignee
- Boku, Inc.
Inventor
- Glyn Barry Smith
Application Information
Application Number:US 12/406,084
Filing Date:2009-03-17
Priority Date:2009-02-20
Art Unit:2643
Classifications
IPC:
H04M11/00
Patent Drawings (15 sheets)
Description
[0001] The present application claims priority to Provisional U.S. Patent Application Ser. No. 61/154,318, filed Feb. 20, 2009 and entitled “Systems and Methods to Approve Electronic Payments,” the disclosure of which is hereby incorporated herein by reference.
Field of the Technology
[0002] At least some embodiments of the disclosure relate to mobile communications in general and, more particularly but not limited to, mobile communications to facilitate online transactions.
Background
[0003] Short Message Service (SMS) is a communications protocol that allows the interchange of short text messages between mobile telephone devices. SMS messages are typically sent via a Short Message Service Center (SMSC) of a mobile carrier, which uses a store-and-forward mechanism to deliver the messages. When a mobile telephone is not reachable immediately for the delivery of the message, the SMSC stores the message for later retry.
[0004] SMS messages can be sent via gateways. Some gateways function as aggregators. An aggregator typically does not have the capacity to deliver the messages directly to the mobile phones. An aggregator typically interfaces with and relies upon the SMSC of a mobile carrier to deliver SMS messages.
[0005] Some gateways function as providers that are capable of sending text messages to mobile devices directly, without going through the SMSC of other mobile operators.
[0006] Text messaging between mobile telephones can also be performed using other protocols, such as SkyMail and Short Mail in Japan.
[0007] Some mobile carriers provide email gateway services to allow text messages to be sent to mobile phones via email. For example, a non-subscriber of the mobile carrier may send a message to an email address associated with a mobile phone of a subscriber of the mobile carrier to have the message delivered to the mobile phone via text messaging.
[0008] Emails can also be sent to mobile telephone devices via standard mail protocols, such as Simple Mail Transfer Protocol (SMTP) over Internet Protocol Suite (commonly TCP/IP, named from two of the protocols: the Transmission Control Protocol (TCP) and the Internet Protocol (IP)).
[0009] Short messages may be used to provide premium services to mobile phones, such as news alerts, ring tones, etc. The premium content providers may send the messages to the SMSC of the mobile operator using a TCP/IP protocol, such as Short Message Peer-to-peer Protocol (SMPP) or Hypertext Transfer Protocol, for delivery to a mobile phone; and the mobile phone is billed by the mobile operator for the cost of receiving the premium content.
[0010] Premium services may also be delivered via text messages initiated from the mobile phone. For example, a televoting service provider may obtain a short code to receive text messages from mobile phones; and when the user sends a text message to the short code, the mobile carrier routes the message to the televoting service provider and charges the user a fee, a portion of which is collected for the televoting service provider.
Summary of the Description
[0011] Systems and methods are provided to facilitate online transactions via mobile communications. Some embodiments are summarized in this section.
[0012] In one aspect, a system includes a data storage facility to store an account identifier of a user and a phone number of the user and an interchange coupled with the data storage facility. The interchange includes a common format processor and a plurality of converters to interface with a plurality of different controllers of mobile communications. The converters are configured to communicate with the controllers in different formats; and the converters are configured to communicate with the common format processor in a common format to facilitate electronic payment transactions using the account identifier.
[0013] In one embodiment, the common format processor is configured to instruct a first controller of the controllers, via a first converter of the converters, to communicate with a telephone at the telephone number of the user to confirm an identity of the user of a user terminal separate from the telephone. Subsequent to confirming the identity of the user, the interchange is to receive a payment request including the phone number of the user from the user terminal. The interchange is configured to approve the request based at least in part on the confirming of the identity of the user and to process the payment request using the account identifier stored and associated with the telephone number on the data storage facility.
[0014] The disclosure includes methods and apparatuses which perform these methods, including data processing systems which perform these methods, and computer readable media containing instructions which when executed on data processing systems cause the systems to perform these methods.
[0015] Other features will be apparent from the accompanying drawings and from the detailed description which follows.
Brief Description of the Drawings
[0016] The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
[0017] FIG. 1 shows a system to facilitate online transactions according to one embodiment.
[0018] FIG. 2 shows an interchange to route messages according to one embodiment.
[0019] FIG. 3 shows a message processor according to one embodiment.
[0020] FIG. 4 shows a method to facilitate an online transaction using an interchange according to one embodiment.
[0021] FIG. 5 illustrates a user interface to associate an account with a telephone number according to one embodiment.
[0022] FIG. 6 illustrates another user interface to associate an account with a telephone number according to one embodiment.
[0023] FIG. 7 illustrates a user interface to initiate a payment transaction according to one embodiment.
[0024] FIG. 8 illustrates a user interface to initiate a payment request according to one embodiment.
[0025] FIG. 9 illustrates a user interface to confirm a payment request according to one embodiment.
[0026] FIG. 10 illustrates a user interface to confirm the completion of a payment transaction according to one embodiment.
[0027] FIG. 11 illustrates a way to redirect a payment confirmation according to one embodiment.
[0028] FIG. 12 illustrates a user interface to receive payment options according to one embodiment.
[0029] FIG. 13 shows a method to process an online payment according to one embodiment.
[0030] FIG. 14 shows another method to facilitate a payment transaction according to one embodiment.
[0031] FIGS. 15-18 show methods to approve a payment transaction according to some embodiments.
[0032] FIG. 19 shows a data processing system, which can be used in various embodiments.
Detailed Description
[0033] The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.
[0034] Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
[0035] In one embodiment, an interchange is used to interface with a plurality of different controllers of mobile communications, such as SMS messages. The interchange can be used to associate account information with phone numbers to facilitate electronic payments via mobile devices, such as cellular phones. The interchange is configured to communicate with the mobile phones through the different controllers to provide security and convenience for online transactions.
[0036] FIG. 1 shows a system to facilitate online transactions according to one embodiment. In FIG. 1 , an interchange (101) is provided to interface with a plurality of different controllers (115) for communications with the mobile phones (117) over the wireless telecommunications network (105).
[0037] In FIG. 1 , a data storage facility (107) stores user account information (121) and the corresponding phone numbers (123) of the mobile phones (117). The interchange (101) is coupled with the data storage facility (107) to communicate with the mobile phones (117) at the corresponding phone numbers (123) to confirm operations that are performed using the account information (121). Since the account information (121) is secured by the interchange (101), the account information (121) can be used to pay for products and services offered by the servers (113) of various merchants, without being revealed to the merchants.
[0038] In one embodiment, the server (113) offers products and/or services adapted for a virtual world environment, such as an online game environment, a virtual reality environment, etc. The products may be virtual goods, which can be delivered via the transmission of data or information (without having to physically deliver an object to the user). For example, the virtual goods may be a song, a piece of music, a video clip, an article, a computer program, a decorative item for an avatar, a piece of virtual land in a virtual world, a virtual object in a virtual reality world, etc. For example, an online game environment hosted on a server (113) may sell services and products via points or virtual currency, which may be consumed by the user while engaging in a game session. For example, a virtual reality world hosted on a server (113) may have a virtual currency, which may be used by the residents of the virtual reality world to conduct virtual commerce within the virtual reality world (e.g., buy virtual lands, virtual stocks, virtual objects, services provided in the virtual reality world, etc). In other embodiments, the server (113) may also offer physical goods, such as books, compact discs, photo prints, postcards, etc.
[0039] In FIG. 1 , the interchange (101) may communicate with different controllers (115) of mobile communications via different networks (e.g., 105 and 103) and/or protocols. The interchange (101) processes the requests in a common format and uses a set of converters for communications with the different controllers (115) respectively.
[0040] For example, the controllers (115) may be different aggregators, providers and/or SMSCs of different mobile carriers. Based on the phone numbers (123), the interchange (101) interfaces with the corresponding controllers (115) to communicate with the mobile phones (117) via text messaging to confirm the operations related to the corresponding account information (121), such as bank accounts, credit card numbers, charge card numbers, etc.
[0041] In FIG. 1 , the user terminals (111) may use a unified interface to send requests to the interchange (101). For example, a web site of the interchange (101) may be used to receive the account information (121) from the web browsers running in the user terminals (111). The user terminals (111) are typically different from the mobile phones (117). However, in some embodiments, users may use the mobile phone (117) to access the web and submit the account information (121). Alternatively, the users may use the mobile phone (117) to submit the account information (121) to the interchange (101) via text messaging, email, instant messaging, etc.
[0042] The use of the mobile phones (117) in the confirmation of activities that involve the account information (121) increases the security of the transaction, since the mobile phones (117) are typically secured in the possession of the users.
[0043] Further, in one embodiment, the interchange (101) may use the phone bills of the mobile phones (117) to pay for purchases, in order to use the account information (121) to pay for the phone bills, and/or to deposit funds into the accounts identified by the account information (121) by charging on the phone bills of the corresponding mobile phones (117). In some embodiments, the accounts identified by the account information (121) are hosted on the data storage facility (107). In other embodiments, the accounts are hosted on the account servers (125) of financial institutions, such as banks, credit unions, credit card companies, etc.
[0044] In one embodiment, once the account information (121) is associated with the mobile phones (117) via their phone numbers (123) stored in the data storage facility (107), the users may use the user terminals (111) to access online servers (113) of various merchants or service providers to make purchases. From the user terminals (111), the users can use the accounts identified by the account information (121) to make the payment for the purchases, without revealing their account information (121) to the operators of the servers (113).
[0045] In one embodiment, the mobile phones (117) are used by the corresponding users to make payments and/or manage funds, such as for making purchases in various websites hosted on the servers (113) of merchants and service providers and/or for transferring funds to or from an account identified by the account information (121), such as phone bills of land-line telephone services, credit card accounts, debit card accounts, bank accounts, etc., or an account hosted on the data storage facility (107) or telecommunication accounts of the mobile phones (117) with telecommunication carriers. The mobile phones (117) are used to confirm and/or approve the transactions associated with the account identified by the account information (121) (or other accounts). The interchange (101) interfaces the mobile phones (117) and the servers (113) to confirm and/or approve transactions and to operate on the account identified by the account information (121) (and/or other accounts associated with the phone number (123)).
[0046] For example, the user terminal (111) may provide the phone numbers (123) to the servers (113) to allow the servers (113) to charge the account identified by the account information (121) associated with the phone number (123). The interchange (101) sends a message to the mobile phone (117) via the phone number (123) to confirm the payment request. Once the payment is confirmed or approved via the corresponding mobile phone (117), the interchange (101) charges the account identified by the account information (121) (e.g., by communicating with the account server (125) on which the corresponding accounts are hosted) and pays the server (113) on behalf of the user, using the funds obtained from the corresponding account identified by the account information (121).
[0047] In one embodiment, the user terminal (111) may not even provide the phone number (123) to the server (113) to process the payment. The server (113) may redirect a payment request to the interchange (101), which then prompts the user terminal (111) to provide the phone number (123) to the web site of the interchange (101) to continue the payment process.
[0048] For example, the server (113) may redirect the payment request to the web site of the interchange (101) with a reference indicating the purchase made via the user terminal (111). The interchange (101) can use the reference to subsequently complete the payment with the server (113) for the purchase, after receiving the phone number (123) directly from the user terminal (111) to confirm the payment via the mobile phone (117).
[0049] In some embodiments, instead of directly providing the phone number (123) to identify the account information (121), the user may provide other information to identify the phone number (123), such as an account identifier of the user assigned to the user for obtaining the services of the interchange (101).
[0050] In one embodiment, the account information (121) is pre-associated with the phone number (123) prior to the payment request. The account information (121) may be submitted to the interchange (101) via the user terminal (111) or the mobile phone (117) via a secure connection.
[0051] Alternatively, the user may supply the account information (121) to the interchange (101) at the time the payment request is submitted from the user terminal (111) to the interchange (101). Alternatively, the user may supply the account information (121) to the interchange (101) at the time the user responds to the confirmation message for the payment request.
[0052] In some embodiments, the user may supply the account information (121) after a transaction using funds collected via the telecommunication carrier of the mobile phone (117) at the phone number (123). For example, after the transaction, the interchange (101) may send an invitation message, such as a text message to the mobile phone (117) at the phone number (123), to the user to invite the user to register with the interchange (101) and provide the account information (121). The user may register with the interchange (101) via the mobile phone (117) (e.g., by a replying text message), or via a web page of the interchange (101) (e.g., using a link and/or a unique code provided in the invitation message).
[0053] After the user registers with the interchange (101) (e.g., via the mobile phone (117) and by providing the account information (121)), the user may create a customized personal identification number (PIN) or receive a PIN for enhanced security. Using the PIN, the user may use the account information (121) to complete an online transaction without having to confirm and/or approve a transaction using the mobile phone (117). In some embodiments, the PIN may be used to reduce unwanted messages to the mobile phone (117). For example, once the phone number (123) and the account information (121) are associated with a PIN, the interchange (101) may require the user of the user terminal (111) to provide the correct PIN to initiate the payment process. Thus, a spammer having only the phone number (123) (or a different user mistakenly using the phone number (123)) may not successfully use the user terminal (111) to request the interchange (101) to send confirmation messages to the mobile phone (117) protected by the PIN. In some embodiments, the interchange (101) may offer further incentives to the user for registering with the interchange (101), such as reduced fees, discounts, coupons, free products and services, etc.
[0054] In one embodiment, once the account information (121) is associated with the phone number (123) in the data storage facility (107), the user does not have to resubmit the account information (121) in subsequent payment requests.
[0055] By delegating the payment task to the interchange (101) and securing the account information (121) in the data storage facility (107), the system as shown in FIG. 1 can increase the security of using the account information (121) in an online environment.
[0056] In some embodiments, the interchange (101) can also fulfill the payment requests using the funds collected via the phone bill of the phone numbers (123). The interchange (101) can collect the funds via sending premium messages to the mobile phones (117) at the phone numbers (123), after receiving confirmation from the mobile phone (117).
[0057] For example, after the confirmation or approval message is received from the mobile phone (117), the interchange (101) performs operations to collect funds via the phone bill of the phone number (123). The interchange (101) may calculate the required premium messages to bill to the mobile phone (117). For example, mobile terminated premium SMS messages may have a predetermined set of prices for premium messages. The interchange (101) determines a combination of the premium messages that has a price closest to the amount required by the transaction, and sends this combination of premium messages to the mobile phone (117). For example, mobile originated premium SMS messages may also have a predetermined set of prices for premium messages. The interchange (101) can calculate the set of messages required for the transaction and transmit a text message to the mobile phone (117) of the user to instruct the user to send the required number of premium messages to provide the funds.
[0058] In one embodiment, the data storage facility (107) stores the transaction history (127) associated with the phone number (123) and uses the transaction history (127) to approve payment requests and to reduce the time period for processing a subsequent payment request.
[0059] For example, from the transaction history (127) the interchange (101) may identify a pattern of prior payment requests made via the phone number (123) and match subsequent requests with the identified pattern. When a subsequent request matches the pattern, the interchange (101) may skip the communication with the mobile phone (117) at the phone number (123), which communication is otherwise performed after the payment request and before the payment operation for payment confirmation and/or approval. Skipping such a communication between the payment request and the payment operation can reduce the time period for payment processing and improve user experience.
[0060] Examples of transaction patterns may include the use of the individual user terminals (111), the typical time period of payment requests, range of payment amounts, and/or certain characteristics of payees, such as a collection of frequently used payees, payees who provide certain types of products or services, the geographical region of payees, etc.
[0061] In one embodiment, when the subsequent payment request is received within a predetermined time limit of a previous confirmed payment request from the same user terminal (111), the interchange (101) may approve the payment request without communicating with the mobile phone (117) at the phone number (123) for approval or confirmation.
[0062] In one embodiment, when the interchange (101) skips the communication with the mobile phone (117) at the phone number (123) for approval or confirmation and approves a transaction request based on the transaction history (127), the interchange (101) may send a notification message to the mobile phone (117) at the phone number (123) for enhanced security but not requiring a response from the user. If the user determines that the notification message corresponds to an unauthorized use of the phone number (123), the user may reply to the notification message from the mobile phone (117) to report the unauthorized use and/or stop or reverse the payment operation.
[0063] In some embodiments, the user may start a session (e.g., a web session) authenticated using a password associated with the phone number (123), prior to the payment request. When the payment request is made within the authenticated session (e.g., before the user logs off the session, or before the session times out), the interchange (101) may skip the confirmation/approval communication with the mobile phone (117) at the phone number (123) to reduce the time period for payment processing.
[0064] In one embodiment, the session is authenticated via communications with the mobile phone (117) at the phone number (123). For example, after the user provides the phone number (123) to log into a session on a user terminal (111), the interchange (101) may generate a code (e.g., a code for one time use) and send the code to the user via the user terminal (111) (or the mobile phone (117) at the phone number (123)). The interchange (101) then requests the code back from the user via the mobile phone (117) at the phone number (123) (or the user terminal (111)), which is not used to send the code. When the code sent by the interchange (101) matches the code received back from the user, the association between the user terminal (111) and the mobile phone (117) at the phone number (123) can be established; and the identity of the user of the user terminal (111) can be confirmed. Such confirmation can be logged in the transaction history (127) for subsequent approval of payment requests.
[0065] In one embodiment, the user may specify a time period for the session, or the time period for the association between the user terminal (111) and the phone number (123). The user may specify the time period using the user terminal (111) when providing the phone number (123) to initiate the session, or specify the time period using the mobile phone (117) when providing the one-time code back to the interchange (101). During the time period of the confirmed association between the user terminal (111) and the phone number (123), a payment request from the user terminal (111) can be automatically identified with the phone number (123) without the user having to explicitly specify the phone number (123) for the payment request. Alternatively, for enhanced security and/or flexibility, the interchange (101) may require the user to identify the phone number (123) in the payment request, even though the payment request is from the user terminal (111) that is associated with the phone number (123).
[0066] In one embodiment, the code for the authentication of the session can be communicated to and/or from the mobile phone (117) via short message service (SMS), voice message, voice mail, or other services, such as email, instant messaging, multimedia messaging service (MMS), etc.
[0067] In one embodiment, after the user provides the phone number (123) to log into a session on a user terminal (111), the interchange (101) provides a message to the mobile phone (117) at the phone number (123) and receives a reply to the message from the mobile phone (117) within a predetermined period of time to authenticate the session and associate the user terminal (111) with the phone number (123). If the reply is not received from the mobile phone (117) with the predetermined period of time, the session is not authenticated.
[0068] In one embodiment, the user may provide an advance approval for subsequent payment requests to pay via the phone number (123). The advance approval may include a number of limitations, such as the time limit for the expiration of the advance approval, the budget limit for the advance approval, a limit on payees for the advance approval, etc. For example, the advance approval may limit the payees based on their business category, web address, product type, service type, geographic location, etc. For example, the budget limit may include the frequency of subsequent payment requests, limit for individual payment requests, and total limit for subsequent payment requests, etc.
[0069] In one embodiment, the advance approval is specific for a user terminal. For example, the advance approval may be obtained via communications with the user via both a specific user terminal (111) and the mobile phone (117) at the phone number (123). Thus, the advance approval applies only to subsequent payment requests from the specific user terminal (111) identified by the advance approval.
[0070] Alternatively, the advance approval may not be limited to a specific user terminal (111). The advance approval may be used for any user terminals (111) used by the user of the phone number (123) to request payments via the phone number (123). In some embodiments, the advance approval is limited to user terminals (111) of certain characteristics identified by the advance approval, such as a geographic region of the user terminal (111) (e.g., determined based on the communication addresses, routing paths, access points for wireless connections, base stations for cellular communications, etc.). In some embodiments, the interchange (101) automatically identifies these characteristics based on the communications to obtain the advance approval (e.g., based on transaction history (127)), without the user explicitly specifying the characteristics.
[0071] FIG. 2 shows an interchange to route messages according to one embodiment. In FIG. 2 , the interchange (101) includes a unified data interface (135) for interaction with the servers (113). The servers (113) may redirect the payment requests to the interchange (101) to allow the interchange (101) to subsequently communicate with the user to process the payment request, including obtaining payment options and identifying user accounts (123), before returning to communicating with the server (113). Alternatively, the servers (113) may collect account related information (e.g., the phone number of the user) to request payment from the interchange (101).
[0072] In FIG. 2 , the interchange (101) includes a common format processor (133), which processes various payment options in a common format. In one embodiment, the common format processor (133) can handle the payments via mobile terminated text message, mobile originated text message, operator bill, credit card, stored value account, and other online payment options. The common format processor (133) determines the actual amount that is to be billed to the user, based on the payment options (e.g., mobile terminated premium SMS, mobile originated premium SMS, operator billing, credit cards, etc.), and selects a converter (131) to communicate with a corresponding controller (115).
[0073] Different converters (131) are configured to communicate with corresponding controllers (115) in different languages and protocols. The converters (131) perform the translation between the common format used by the common format processor (133) and the corresponding formats used by the controllers (115).
[0074] The use of the common format processor (133) simplifies the structure of the interchange (101) and reduces the development effort required for the interchange (101) to interface with the increasing number of different controllers, such as SMSC, mobile providers, aggregators, gateways, etc.
[0075] FIG. 3 shows a message processor according to one embodiment. In FIG. 3 , the common format processor (133) includes a billing engine (157) that calculates the amount to be billed to the user, by adding or subtracting transaction costs for different billing methods, such as mobile terminated text message, mobile originated text message, operator billing, credit card, stored value account, and other online payment options.
[0076] In one premium message billing method, the interchange (101) sends mobile terminated premium SMS messages to the mobile phone (117) to bill the user, or requests the mobile phone (117) to send mobile originated premium SMS messages to a short code representing the interchange (101).
[0077] In one operator billing method, the interchange (101) directly sends a message to the mobile carrier of the mobile phone (117) to bill the amount on the phone bill of the mobile phone (117), without having to send a premium message to the mobile phone (117).
[0078] The common format processor (133) includes a decision engine (151) which decides how to generate a set of one or more messages to the mobile phone (117) based on a set of rules (141), regulations (143), limits (145), records (147) and restrictions (149).
[0079] For example, different countries have different regulations (143) governing the mobile communications with the mobile phones (117). For example, different mobile carriers have different rules (141) regarding premium messages. For example, past transaction records (147) can be used to monitor the transactions to discover suspected fraudulent activities. For example, parental limits (145) and merchant restrictions (149) can be imposed.
[0080] Based on results of the decision engine (151), the mobile message generator (153) generates one or more messages to communicate with the mobile phone (117) about the transaction (e.g., a request to collect funds via the phone bill of the user for a payment request, or for deposit into an account identified by the account information (121)). The converter (131) then interfaces with the corresponding controller (115) to transmit the messages to the mobile phones (117).
[0081] FIG. 4 shows a method to facilitate an online transaction using an interchange according to one embodiment. In FIG. 4 , the user terminal (111) provides (171) account information (121) to the interchange (101) for association with the phone number (123). For example, the user may use a device running a web browser as the user terminal (111) to submit the account information (121) via a secure web connection. The user terminal (111) is typically different from the mobile phone (117). However, in some embodiments, the mobile phone (117) may also be used as the user terminal (111) to submit the account information (121) (e.g., via a wireless application protocol (WAP) application, or via a message sent via short message service (SMS) or multimedia message service (MMS), or via an email message or an instant message).
[0082] After the user provides the account information (121) to the interchange (101) for storage in the data storage facility (107), the user can send (177) a charge request to the server (113) of a merchant from the user terminal (111). The server (113) of the merchant can send or redirect (179) the charge request to the interchange (101). In response to the charge request, the interchange (101) sends (173) a confirmation message to the mobile phone (117). If the user sends (173) an approval, or an appropriate reply, to the confirmation message from the mobile phone (117), the interchange (101) communicates with the account server (125) to charge an account of the user identified by the account information (121), without revealing the account information (121) to the server (113). The interchange (101) pays the merchant on behalf of the user using the funds collected via charging the account of the user. For example, the interchange (101) may use its own bank account to pay the merchant operating the server (113). Thus, the financial information of the user is not revealed to the merchant.
[0083] Upon the completion of the payment process, the interchange (101) can notify the user via the mobile phone (117) and/or the user terminal (111).
[0084] In some embodiments, the server (113) of the merchant redirects the charge request to allow the user terminal (111) to communicate with the interchange (101) to continue the payment process; and the user terminal (111) may provide (171) the account information (121) directly to the interchange (101) after the charge request is redirected.
[0085] In alternative embodiments, the user may provide the account information (121) from the mobile phone (117) together with the approval of the charge request.
[0086] In one embodiment, the interchange (101) communicates with the mobile phone (117) for the confirmation of the charge request via SMS messages. Alternatively, the confirmation and approval messages can be sent (173) via emails, instant messages, voice message, live calls from operators, etc.
[0087] In some embodiments, the user of the mobile phone (117) may choose to fulfill the charge request via the phone bill, instead of charging the account identified by the account information (121). Thus, after the confirmation, the interchange (101) sends the premium messages to the mobile phone (117) to collect funds via the phone bill of the mobile phone (117). In other embodiments, the interchange (101) may send an instruction with the confirmation message to the mobile phone (117) to instruct the user to send mobile originated premium messages to the interchange (101) to collect the funds via the phone bill of the mobile phone (117).
[0088] FIG. 5 illustrates a user interface to associate an account with a telephone number according to one embodiment. In FIG. 5 , the user interface (180) includes a text field (183) that allows the user to specify the phone number (123) with which the account information (121) provided in the text field (181) is to be associated.
[0089] In FIG. 5 , the user interface (180) further includes an option list, which allows the user to select various types of accounts, such as credit card accounts, bank accounts, charge card accounts, etc. In the example illustrated in FIG. 5 , the checkbox (185) is selected to specify a credit card account.
[0090] In some embodiments, the user interface (180) may further present a text field (not shown in FIG. 5 ) to allow the user to specify an alias for the account information (121) supplied in the text input field (181). For enhanced security, the alias can be used for subsequent communications with the user without revealing the account information (121).
[0091] In FIG. 5 , the user interface (180) may be presented via a web browser (or a custom application) to submit account information (121) in the text input field (181) from a user terminal (111) to the interchange (101). Alternatively, the account number can be submitted from the mobile phone (117) via a message sent via SMS, WAP, voice mail, or via an interactive voice response (IVR) system.
[0092] In one embodiment, the server (113) presents the payment option (185) via an online shopping cart system or a third party checkout system. Alternatively or in combination, the server (113) presents the payment option (185) via a web widget. For example, a web widget may include a program code that is portable and executable within a web page without requiring additional compilation. The web widget allows the user to select the option (185) to pay for the product and/or service without leaving the web page or refreshing the web page. In one embodiment, the interchange (101) provides the web widget to facilitate the payment processing.
[0093] FIG. 6 illustrates another user interface to associate an account with a telephone number according to one embodiment. In FIG. 6 , the user interface (190) is presented on the mobile phone (117) of the user. The user interface (190) presents a message (191) from the interchange (101) to the mobile phone (117) at the phone number (123). The message (191) prompts the user to submit the account information (121) by providing a reply message (193). The user may select the “send” button (195) to provide the account information (121) for association with the phone number (123) or select the “cancel” button (197) to ignore the prompt.
[0094] In one embodiment, the messages (191 and 193) are transmitted to the mobile phone (117) via a short message service (SMS). Alternatively, the messages can be transmitted to the mobile phone (117) via other protocols, such as multimedia message service (MMS), email, instant messaging, WAP, voice mail, voice messages via an interactive voice response (IVR) system, etc.
[0095] FIG. 7 illustrates a user interface to initiate a payment transaction according to one embodiment. In FIG. 7 , the user interface (201) provides an option (205) to request the interchange (101) to process the payment for the amount (203) required to make a purchase from the server (113) of a merchant.
[0096] In one embodiment, after the user selects the payment option (205), the server (113) directs the request to the web server of the interchange (101), with a set of parameters to indicate the amount (203), the identity of the merchant, a reference to the purchase, etc. Thus, the user does not have to provide any personal information to the server (113) of the merchant to complete the payment process.
[0097] Alternatively, the user may provide the phone number to the merchant to process the payment. Thus, the user does not have to visit the web site of the interchange (101) to complete the payment.
[0098] FIG. 8 illustrates a user interface to initiate a payment request according to one embodiment, after the payment request is redirected to the web site of the interchange (101). In FIG. 8 , the user interface (201) includes the identity of the merchant and the amount (203) of the requested payment. The user interface (201) includes a text field (183) to allow the user to provide the phone number (123) to identify the account information (121) via its association with the phone number (123) in the data storage facility (107).
[0099] Further, user authentication may be used to reduce false messages to the phone number (123). For example, the user interface (201) may request a PIN for enhanced security. For example, the user may be required to register with the interchange (101) prior to using the services of the interchange (101); and after registering with the interchange (101), the user is provided with the PIN or can created a customized PIN to access the functionality provided by the user interface (201).
[0100] Alternatively, the user interface (201) may request an identifier associated with the phone number (123) to initiate the payment transaction. In some embodiments, the user interface (201) requires the user to provide no information other than the phone number (123) in the text field (183) to initiate the transaction.
[0101] In FIG. 8 , the user interface (201) allows the user to select one option from a plurality of payment options, including paying via the phone bill, and paying via one or more of the accounts identified by the account information (121) associated with the phone number (123) in the data storage facility (107).
[0102] In some embodiments, the user interface (201) may present the payment options after authenticating the user (e.g., via a personal identification number or password) for enhanced security.
[0103] In some embodiments, the user interface (201) identifies the different accounts represented by the account information (121) by showing aliases of the accounts. The aliases may be previously specified by the user, or be dynamically generated by the interchange (101) based on the types of the accounts and/or portions of the account information (121) (e.g., the first or last few digits of the account number, etc.)
[0104] In one embodiment, once the user submits the payment request via the user interface (201), the interchange (101) transmits a confirmation message to the mobile phone (117) according to the phone number (123) provided in the text field (183). In one embodiment, the interchange (101) transmits the confirmation to the mobile phone (117) after the user is authenticated via the user interface (201) to reduce the possibility of unauthorized/unwelcome messages to the mobile phone (117), which may occur when the user intentionally or unintentionally provides an unrelated phone number in the entry box (183).
[0105] FIG. 9 illustrates a user interface to confirm a payment request according to one embodiment. In FIG. 9 , the confirmation message (217) includes the amount (203) of the requested payment and the identity of the payee (e.g., a merchant operating the server (113)).
[0106] In one embodiment, the confirmation message (217) includes the instruction to reply with a code, such as a code (e.g., “pay”) provided in the confirmation message (217) as illustrated in FIG. 9 .
[0107] The presence of the code in the reply message is an indication of the user approving the request; and the requirement for such a code in the reply eliminates false confirmations (e.g., generated via accidental replies or automated replies).
[0108] Alternatively or in combination, the requested code may include a PIN associated with the account, and/or a code (not shown) randomly generated and presented in the user interface used to initiate the payment transaction (e.g., user interface (201)).
[0109] In some embodiments, the code requested in the text message (217) may be a personal identification number (PIN) associated with the phone number (123). The text message (217) does not include the code; and the knowledge of the code is an indication of the identity of the user. Thus, the use of such a code increases the security of the transaction.
[0110] In a further embodiment, the code requested in the text message (217) includes a code that is provided in response to the payment request (e.g., via the user interface (201), not shown in FIG. 8 ). The code may be generated randomly at the time the request is received via the user interface (201), or when the user interface (201) is presented to the user. The code provided to the user interface (201) can be requested in the reply received from the user interface (190) to indicate that the user who is in possession of the mobile phone (117) has actual knowledge about the payment request submitted via the user interface (201).
[0111] After the correct reply is received, the interchange (101) communicates with the account server (125) to electronically charge the user using the account information (121) and pays the payee using the funds collected via communicating with the account server (125). The interchange (101) then notifies the user when the payment transaction is complete.
[0112] For example, the interchange (101) may notify the user via a text message to the mobile phone (117), as illustrated in FIG. 10 . FIG. 10 illustrates a user interface to confirm the completion of a payment transaction according to one embodiment. No reply to the message that confirms the completion of the payment transaction is necessary. Once the payment transaction is complete, the user would have access to the product purchased via the payment transaction.
[0113] In one embodiment, the interchange (101) stores an address of the user associated with the phone number (123). After the completion of the payment transaction, the interchange (101) provides the address to the server (113) of the merchant for the delivery of the purchased product. In some embodiments, the user may provide multiple addresses associated with the phone number (123) and may select one as a delivery address in the confirmation/approve message to the interchange (101). Alternatively, the interchange (101) may receive an address for product delivery from the mobile phone (117) together with the confirmation/approve message and then forward the address to the server (113) of the merchant. Thus, the shipping address of the transaction is verified to be associated with the mobile phone (117). In alternative embodiments, the user may directly provide the shipping address in the website hosted on the server (113) of the merchant.
[0114] In other embodiments, the user is provided with the options to pay via the mobile phone bill associated with the phone number (123). The interchange (101) may dynamically calculate a set of premium messages, based on a set of limited number of predetermined prices for premium messages, to match the purchase price. The interchange (101) sends the set of premium messages to the mobile phone (117) at the phone number (123) to collect the funds via the telecommunication carriers to pay for the purchases. Thus, the purchase prices are not limited to the set of predetermined prices for premium messages. In some embodiments, the interchange (101) may send the set of premium messages in a period of time (e.g., a week, a month, a number of mouths, etc.) to spread the payments over the period of time (e.g., to overcome budget limits and/or limits imposed by regulations).
[0115] FIG. 11 illustrates a way to redirect a payment confirmation according to one embodiment. For example, after the user submits the payment request to the interchange (101) via the user interface (201) shown in FIG. 8 , the interchange (101) may present the user interface (201) illustrated in FIG. 11 to the user. The user interface (201) indicates that the request is being processed; and the user interface (201) is periodically updated to show progress. Once the payment transaction is completed, the user interface (201) provides a confirmation message and may automatically redirect the user back to the website of the payee (e.g., to access the purchased products or services).
[0116] In one embodiment, the user is required to provide the approval in response to the confirmation message (217), as illustrated in FIG. 9 , within a predetermined period of time. If the user fails to provide the approval from the mobile phone (117) within the predetermined period of time, the payment request may be rejected; and the user interface (201) may present a message indicating the failure and then redirect the user back to the website of the payee.
[0117] In some embodiments, instead of redirecting the user back to the website of the payee after the expiration of a predetermined period of time (e.g., after the failure of the payment process, or after the completion of the payment), the user interface (201) may provide a link to the website of the payee to allow the user to manually select the link to go back to the website of the payee to continue the process at the website of the payee.
[0118] FIG. 12 illustrates a user interface to receive payment options according to one embodiment. In FIG. 12 , the interchange (101) sends a message (217) to the mobile phone (117) to provide a number of options to the user. The message (217) identifies the amount (203) of the requested payment and the identity of the payee (e.g., a merchant operating the server (113)) and asks the user to approve the payment request via a reply that contains a selected payment option.
[0119] In FIG. 12 , the user may reply with the code “1” to approve the payment request and to pay via the phone bill of the mobile phone (117). Alternatively, the user may reply with the credit card information to charge the payment to a credit card, as illustrated in FIG. 12 .
[0120] In one embodiment, if the user provides credit card account information in the approval message, the credit card account information is stored and associated with the phone number (123) in the data storage facility (107). Thus, in subsequent approval messages, the user does not have to supply the same information again.
[0121] For example, the data storage facility (107) may store account information for each of a plurality of account types (e.g., Visa, MasterCard, checking, savings, etc.) Thus, each of the accounts can be identified to the user via the account type in the confirmation message, without revealing the details of the account information.
[0122] For example, the interchange (101) may combine the name of the financial institutions and the type of accounts to generate aliases for the account information.
[0123] In some embodiment, the user may define the aliases for the account information by supplying the aliases with the account information (121) for association with the phone number (123).
[0124] FIG. 13 shows a method to process an online payment according to one embodiment. In FIG. 13 , the interchange (101) receives (301) an account identifier (e.g., 121) from a user and associates (303) the account identifier with a phone number (123) of the user in the data storage facility (107). Over the Internet the interchange (101) subsequently receives (305) a request for payment to be paid to a payee via the mobile phone (117) identified by the phone number (123). In response to the request, the interchange (101) transmits (307) a message (217) to the mobile phone (117) to confirm the payment.
[0125] After receiving (309) a confirmation or approval from the mobile phone (117) for the payment, the interchange (101) electronically charges (311) the user an amount using the account identifier (e.g., via communicating with the account server (125) using the account identifier). The interchange (101) then transfers (313) the amount to a payee to fulfill the payment.
[0126] FIG. 14 shows another method to facilitate a payment transaction according to one embodiment. In FIG. 14 , the interchange (101) receives (331) a request to pay an amount to a payee via a mobile phone (117). The interchange (101) transmits (333) a message (217) to the mobile phone (117) to confirm the request via the converter (131) corresponding to the controller (115) of the mobile phone (117).
[0127] After the interchange (101) receives (335) a confirmation with an account identifier (e.g., 121) from the mobile phone (117) for the request, the interchange (101) electronically communicates (337) with a financial institution to charge the user the specified amount using the account identifier. The interchange (101) pays (339) the payee according to the amount, optionally charges (341) the user a first fee to pay the payee, and optionally charges (343) the payee a second fee for processing the payment.
[0128] In one embodiment, the users are given an incentive to provide the account information (121) for electronic payments via the account servers (125). For example, the interchange (101) may charge a lower fee for fulfilling payment requests via the account server (125) than for fulfilling payments requests via the phone bill. For example, the interchange (101) may offer rebates, discounts, etc. to the users who provide the account information (121). In some embodiments, the interchange (101) can complete a payment process via the account server (125) with fewer restrictions than via the phone bill.
[0129] In one embodiment, the merchant may specify the second fee. Different merchants may offer different percentages of the purchase prices as the second fee; and the interchange (101) may calculate the first fee based on the second fee offered by the merchant, by deducting the second fee from the total fees to be charged (e.g., fees charged by the telecommunication carrier for collecting the funds via the mobile phone bill associated with the telephone number and/or the fees charged by the interchange (101) for processing the payments). Since the first fee is charged to the customer (e.g., the purchaser of products and services), the cost to the customer can vary based on the selection of the merchant. For the same purchase prices, the first fee (and thus the cost to the customer) may be different for purchases made via different merchants, because the merchants may offer different percentage of the purchase price as the second fee. In some embodiments, the first and second fees include both fees charged by the telecommunication carrier for collecting the funds via the mobile phone bill/account associated with the phone number (123) and the fees charged by the interchange (101) for processing the payments. In some embodiments, the first fee includes the fees charged by the telecommunication carrier but no fees charged by the interchange (101). In some embodiments, the second fee includes the fees charged by the telecommunication carrier but no fees charged by the interchange (101). In some embodiments, the first fee and/or the second fee do not include the fees charged by the telecommunication carrier. In some embodiments, the first fee is not charged; and in other embodiments, the second fee is not charged.
[0130] FIGS. 15-18 show methods to approve a payment transaction according to some embodiments.
[0131] In FIG. 15 , after the interchange (101) confirms (341) an identity of a user of a user terminal (111), the interchange (101) receives (343) from the user terminal (111) a request to pay via a telephone number (123) of the user. In one embodiment, the interchange (101) confirms the identify of the user of the user terminal (111) and/or associates the identity of the user of the user terminal (111) with the phone number (123) of the mobile phone (117) prior to the user submitting a request to pay via the phone number (123). Thus, communications with the mobile phone (117) at the phone number (123) for the confirmation and/or approval of the request does not have to take place between the request and the payment operation; and thus the delay between the request and the payment operation can be reduced.
[0132] For example, the user terminal (111) may include a web browser; and the user may log into a web server of the interchange (101) using the web browser. The interchange (101) may prompt the user via the web browser running on the user terminal (111) to provide the phone number (123) and a password associated with the phone number (123). After verifying the password, the user is logged into a session tracked by the web browser on the user terminal (111); and the web browser running on the user terminal (111) is associated with the phone number (123).
[0133] In one embodiment, the interchange (101) further communicates with the mobile phone (117) at the phone number (123) to complete the verification process. For example, the interchange (101) may send a one-time verification code to the mobile phone (117) at the phone number (123) and request the user to provide the correct one-time verification code back via the user terminal (111) to verify the association between the user terminal (111) and the phone number (123). Alternatively, the interchange (101) may provide the one-time verification code to the user terminal (111) and instruct the user to communicate the code back to the interchange (101) via the mobile phone (117) at the phone number (123). Alternatively, after the user logs in using the user terminal (111), the interchange (101) may send a message to the mobile phone (117) to request a reply from the mobile phone (117) at the phone number (123) within a predetermined period of time to validate the session. In some embodiments, after the user provides the phone number (123) using the user terminal (111) to the interchange (101), the user is instructed to provide the password via the mobile phone (117) to complete the log in process.
[0134] In one embodiment, the user terminal (111) tracks the session. For example, the user terminal (111) may use a web browser to track the session via information maintained by the web browser (e.g., cookies). Alternatively or in combination, the interchange (101) may track the session by maintaining information on the data storage facility (107). For example, after the user completes the log in process, the interchange (101) may identify the user terminal (111) via identifiers such as Internet address, Media Access Control address (MAC address), a different phone number (e.g., when the user terminal is a different cell phone), or other software or hardware identification number associated with the user terminal (111), such as a digital certificate; and the interchange (101) may associate the phone number (123) with such identifiers until the expiration of a predetermined time period, or after the user signals an end of the session using the user terminal (111) or using the mobile phone (117) at the phone number (123). In one embodiment, the interchange (101) associates a plurality of identifiers of the user terminal (111) with the phone number (123) for the session. When at least one of the identifiers of the user terminal (111) is changed, the interchange (101) may terminate the session automatically.
[0135] In FIG. 15 , after the user terminal (111) submits the request to pay via the telephone number (123), the interchange (101) approves (345) the request based on the confirming of the identity of the user performed prior to the request and processes (347) the request using funds associated with the telephone number (123). For example, the interchange (101) may transmit premium messages, via a corresponding converter (131), to a mobile phone (117) at the telephone number (123) to collect the funds, or receive premium messages from a mobile phone (117) at the telephone number (123) to collect the funds. For example, the interchange (101) may determine the account information (121) (e.g., an account identifier, such as a credit card number, a bank account number, a debit card number, etc.) stored and associated with the telephone number (123) on the data storage facility (107) of the interchange (101) to charge the user using the account information (121).
[0136] In one embodiment, in response to the payment request from the user terminal (111), the interchange (101) may send a notification message to the mobile phone (117) at the phone number (123). The user is not required to provide a reply to complete the payment process. However, the user of the mobile phone (117) is provided with the option/opportunity to reply and report a fraudulent use, or to cancel the request (e.g., within a predetermined period of time).
[0137] In one embodiment, the data storage facility (107) stores a password associated with the phone number (123) for authentication. In FIG. 16 , after the interchange (101) receives (351) a password and a telephone number (123) from a user terminal (111), the interchange (101) determines (352) whether the received password is the correct password for the telephone number (123). If the received password is the correct password for the telephone number (123), the interchange (101) associates (353) the user terminal (111) with the telephone number (123) in the data storage facility (107). If, during the time period in which the user terminal (111) is associated with the telephone number (123), the interchange (101) receives (355) from the user terminal (111) a request to pay a payee (e.g., via the user interface (201) illustrated in FIG. 8 ), the interchange (101) may approve (357) the request based on the confirmed association between the user terminal (111) and the telephone number (123) and pay the payee using funds associated with the telephone number (123), without requiring a confirmation via the mobile phone (117) at the phone number (123). In some embodiments, after the user terminal (111) submits the phone number (123) to the interchange (101), the interchange (101) may request the password from the mobile phone (117) at the phone number (123).
[0138] In one embodiment, during the time period in which the user terminal (111) is associated with the telephone number (123), the interchange (101) may automatically provide the phone number (123) in the text field (183) in the user interface (201) for submitting a payment request, illustrated in the FIG. 8 , based on the association between the user terminal (111) and the telephone number (123). The phone number (123) can be provided by the interchange (101) in the text field (183) as a default input. Alternatively, the interchange (101) may not provide the phone number (123) and may require the user to enter the phone number (123) in the text field (183) for enhanced security. In some embodiments, the interchange (101) may dynamically determine whether or not to present the phone number (123) in the text field (183) based on a transaction pattern associated with the phone number (123). For example, if the current request matches the pattern, the interchange (101) presents the phone number (123) as the default input to simplify user interactions; otherwise, the interchange (101) does not provide the phone number (123) in the text field (183) for enhanced security.
[0139] In FIG. 17 , after the interchange (101) receives (361) a telephone number (123) from a user terminal (111), the interchange (101) communicates (363) with the user for an advance approval for the user terminal (111) via a mobile phone (117) at the telephone number (123). For example, the interchange (101) may communicate with the mobile phone (117) at the phone number (123) for the advance approval and/or communicate with the user terminal (111) to confirm a password associated with the phone number (123).
[0140] In one embodiment, the advance approval is specific for the user terminal (111); and the interchange (101) stores identifiers of the user terminal (111) with the advance approval. For example, the interchange (101) may communicate with the user terminal (111) and/or the mobile phone (117) to associate the user terminal (111) with the phone number (123) for the advance approval of one or more subsequent payment requests.
[0141] In some embodiments, the advance approval is not limited to a particular user terminal (111). For example, the user may directly use the mobile phone (117) at the phone number (123) to communicate the advance approval to the interchange (101) without having to identify the user terminal (111). Alternatively, the user may use a particular user terminal (111) to initiate the communications with the interchange (101) for the advance approval without limiting the advance approval to subsequent payment requests for the same particular user terminal (111).
[0142] In one embodiment, the advance approval is associated with the phone number (123) on the data storage facility (107). When a request to pay via the funds associated with the phone number (123) is received, the advance approval associated with the phone number (123) is identified and applied by the interchange (101). The user does not have to explicitly identify the advance approval in making the payment request.
[0143] In one embodiment, the interchange (101) may assign an identification code for the advance approval for enhanced security. The user may use the identification code in the payment request to explicitly identify the advance approval.
[0144] In one embodiment, the advance approval specifies a time limit for the expiration of the approval, a budget amount for one or more payment requests, a limit on the types of permitted products and/or services, a time window for permissible payment requests, a frequency for permissible payment requests, and one or more limits based on certain characteristics of the payees (e.g., web addresses, countries, categories, etc.).
[0145] In one embodiment, the advance approval may specify some limits on the permissible user terminals (111). For example, the advance approval may limit the advance approval to user terminals located with certain geographic areas. The interchange (101) may determine the geographic areas of the user terminals (111) based on the IP addresses of the user terminals (111), the access points for wireless local area communications, the base stations for cellular communications, etc.
[0146] After the advanced approval is associated with the phone number (123), the interchange (101) may receive (365) from the user terminal (111) a request to pay a payee via the telephone number (123). Based on the advance approval the interchange (101) may approve (367) the request and pay (369) the payee using funds associated with the telephone number (123), without requiring a confirmation message from the user via communications with the mobile phone (117) at the phone number (123).
[0147] In some embodiments, the interchange (101) may use the transaction history (127) to determine whether or not to require a confirmation message from the user via communications with the mobile phone (117) at the phone number (123). The transaction history (127) may include a number of records of prior confirmed/approved payment requests.
[0148] For example, based on the records of prior payment requests the interchange (101) may determine a payment pattern for the phone number (123), such as a list of frequently used user terminals (111) for the phone number (123), a range for typical payment amounts, a time period of a day within which typical payment requests are received for the phone number (123), a list of frequently used payees paid via the phone number (123), a list of categories of services and/or products frequently paid via the phone number (123), a recent payment requested confirmed within a predetermined period of time, etc.
[0149] In FIG. 18 , the interchange (101) processes (371) a plurality of requests to pay via a phone number (123). The interchange (101) processes (371) the requests via communicating with the mobile phone (117) at the phone number (123). For example, the interchange (101) may send a message to the mobile phone (117) at the phone number (123) and request a reply to the message from the mobile phone (117). For example, the interchange (101) may request a PIN from the mobile phone (117) at the phone number (123) to confirm the requests. For example, the interchange (101) may send one-time codes representing the requests to the mobile phone (117) or receive one-time codes representing the requests from the mobile phone (117).
[0150] The interchange (101) stores (373) transaction records of the payment requests and determines (375) a pattern of the payment requests.
[0151] Subsequently, when the interchange (101) receives (377) from a user terminal (111) a request to pay a payee via the telephone number (123), the interchange (101) determines (378) whether the request matches the pattern. If the request matches the pattern, the interchange (101) pays (379) the payee using funds associated with the telephone number (123), without requiring a confirmation communicated via the mobile phone (117) at the phone number (123) to speed up the payment process. The interchange (101) may send a notification to the mobile phone (117) at the phone number (123), without requiring a reply prior to making the payment.
[0152] FIG. 19 shows a data processing system, which can be used in various embodiments. While FIG. 19 illustrates various components of a computer system, it is not intended to represent any particular architecture or manner of interconnecting the components. Some embodiments may use other systems that have fewer or more components than those shown in FIG. 19 .
[0153] In one embodiment, each of the interchange (101), the data storage facility (107), the controllers (115), the mobile phones (117), the user terminals (111), the account server (125) and the servers (113) can be implemented as a data processing system, with fewer or more components, as illustrated in FIG. 19 .
[0154] In FIG. 19 , the data processing system (401) includes an inter-connect (402) (e.g., bus and system core logic), which interconnects a microprocessor(s) (403) and memory (408). The microprocessor (403) is coupled to cache memory (404) in the example of FIG. 19 .
[0155] The inter-connect (402) interconnects the microprocessor(s) (403) and the memory (408) together and also interconnects them to a display controller, display device (407), and to peripheral devices such as input/output (I/O) devices (405) through an input/output controller(s) (406).
[0156] Typical I/O devices include mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices which are well known in the art. In some embodiments, when the data processing system is a server system, some of the I/O devices, such as printer, scanner, mice, and/or keyboards, are optional.
[0157] The inter-connect (402) may include one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment, the I/O controller (406) includes a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
[0158] The memory (408) may include ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.
[0159] Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.
[0160] The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
[0161] In this description, various functions and operations may be described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize that what is meant by such expressions is that the functions result from execution of the code/instructions by a processor, such as a microprocessor. Alternatively, or in combination, the functions and operations can be implemented using special purpose circuitry, with or without software instructions, such as using Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
[0162] While some embodiments can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
[0163] At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
[0164] Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
[0165] A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.
[0166] Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others.
[0167] The computer-readable media may store the instructions. The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc.
[0168] In general, a tangible machine readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
[0169] In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
[0170] Although some of the drawings illustrate a number of operations in a particular order, operations which are not order dependent may be reordered and other operations may be combined or broken out. While some reordering or other groupings are specifically mentioned, others will be apparent to those of ordinary skill in the art and so do not present an exhaustive list of alternatives. Moreover, it should be recognized that the stages could be implemented in hardware, firmware, software or any combination thereof.
[0171] In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Claims
What is claimed is:
1. A computer-implemented method, comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number;
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request and at least in part on payment amount; and
processing the payment request using funds associated with the telephone number.
2. The method of claim 1, wherein the confirming the identity of the user comprises: transmitting a first code to a device at the telephone number of the user;
receiving a second code from the user terminal; and
matching the first code and the second code to confirm the identity of the user.
3. The method of claim 2, wherein the first code is transmitted to the device at the telephone number of the user via short message service (SMS).
4. The method of claim 1, wherein the confirming the identity of the user comprises:
providing a first code to the user terminal;
receiving a second code from an apparatus at the telephone number of the user; and
matching the first code and the second code to confirm the identity of the user.
5. The method of claim 4, wherein the apparatus comprises a mobile device, and the second code is received from the mobile device via short message service (SMS).
6. The method of claim 1, wherein the confirming of the identity of the user is performed in connection with a separate payment request received from the user terminal.
7. The method of claim 1, wherein the pattern is based at least in part on payee of the payment request.
8. The method of claim 1, wherein the confirming the identity of the user includes:
obtaining an advance approval from a telephone at the telephone number of the user, wherein the approving the request is based at least in part on the advance approval.
9. The method of claim 8, wherein the advance approval includes at least one of: a time limit for expiration of the advance approval, a budget limit for the advance approval, and a limit on payees for the advance approval.
10. The method of claim 9, wherein the advance approval is associated with the user terminal.
11. The method of claim 1, wherein the mobile device at the telephone number is a different processing system than the terminal.
12. The method of claim 1, wherein the confirming the identity of the user comprises receiving a password stored and associated with the telephone number at the server from the user terminal.
13. A tangible non-transitory computer-readable storage media storing instructions, the instructions causing a computer to perform a method, the method comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request and at least in part on payment amount;
processing the payment request using funds associated with the telephone number.
14. A system, comprising:
a data storage facility to store and associate an account identifier of a user with a telephone number of the user; and
an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format, the common format processor to instruct a first controller of the controllers, via a first converter of the converters, to communicate with a telephone at the telephone number of the user to confirm an identity of the user of a user terminal separate from the telephone, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises receiving the telephone number of the user from the user terminal, transmitting a first code to a mobile device at the telephone number of the user, receiving a second code from the mobile device at the telephone number and matching the first code and the second code to confirm the identity of the user, subsequent to confirming the identity of the user, the interchange to receive a payment request including the phone number of the user from the user terminal, the interchange, wherein the pattern is based at least in part on time instance of the payment request, to approve the payment request based at least in part on the confirming of the identity of the user and at least in part on payment amount, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests,] and to process the payment request using the account identifier stored and associated with the telephone number on the data storage facility.
15. A computer-implemented method, comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request and at least in part on payee of the payment request;
processing the payment request using funds associated with the telephone number.
16. A tangible non-transitory computer-readable storage media storing instructions, the instructions causing a computer to perform a method, the method comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request and at least in part on a payee of the payment request;
processing the payment request using funds associated with the telephone number.
17. A system, comprising:
a data storage facility to store and associate an account identifier of a user with a telephone number of the user; and
an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format, the common format processor to instruct a first controller of the controllers, via a first converter of the converters, to communicate with a telephone at the telephone number of the user to confirm an identity of the user of a user terminal separate from the telephone, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises receiving the telephone number of the user from the user terminal, transmitting a first code to a mobile device at the telephone number of the user, receiving a second code from the mobile device at the telephone number and matching the first code and the second code to confirm the identity of the user, subsequent to confirming the identity of the user, the interchange to receive a payment request including the phone number of the user from the user terminal, the interchange, wherein the pattern is based at least in part on time instance of the payment request, to approve the payment request based at least in part on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests and at least in part on a payee of the payment request, and to process the payment request using the account identifier stored and associated with the telephone number on the data storage facility.
18. A computer-implemented method, comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user, wherein the device at the telephone number is a different processing system than the terminal;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request;
processing the payment request using funds associated with the telephone number.
19. A tangible non-transitory computer-readable storage media storing instructions, the instructions causing a computer to perform a method, the method comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user, wherein the mobile device at the telephone number is a different processing system than the terminal;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request;
processing the payment request using funds associated with the telephone number.
20. A system, comprising:
a data storage facility to store and associate an account identifier of a user with a telephone number of the user; and
an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format, the common format processor to instruct a first controller of the controllers, via a first converter of the converters, to communicate with a telephone at the telephone number of the user to confirm an identity of the user of a user terminal separate from the telephone, wherein the confirming of the identity of the user is performed in connection with a plurality of separate payment requests received from the user terminal, wherein the confirming the identity of the user comprises receiving the telephone number of the user from the user terminal, transmitting a first code to a mobile device at the telephone number of the user, wherein the mobile device at the telephone number is a different processing system than the terminal, receiving a second code from the mobile device at the telephone number and matching the first code and the second code to confirm the identity of the user, subsequent to confirming the identity of the user, the interchange to receive a payment request including the phone number of the user from the user terminal, the interchange, wherein the pattern is based at least in part on time instance of the payment request, to approve the payment request based at least in part on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, and to process the payment request using the account identifier stored and associated with the telephone number on the data storage facility.
21. A computer-implemented method, comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user, wherein the confirming the identity of the user includes obtaining an advance approval from a telephone at the telephone number of the user, wherein the approving the request is based at least in part on the advance approval, wherein the advance approval includes at least one of: a time limit for expiration of the advance approval, a budget limit for the advance approval, and a limit on payees for the advance approval, wherein the advance approval is associated with the user terminal;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request;
processing the payment request using funds associated with the telephone number.
22. A tangible non-transitory computer-readable storage media storing instructions, the instructions causing a computer to perform a method, the method comprising:
communicating by a server computer with a user terminal over a data communications network;
confirming an identity of the user of the user terminal prior to the user submitting a payment request to the server computer from the user terminal over the data communications network, wherein the confirming the identity of the user comprises:
receiving the telephone number of the user from the user terminal;
transmitting a first code to a mobile device at the telephone number of the user;
receiving a second code from the mobile device at the telephone number; and
matching the first code and the second code to confirm the identity of the user, wherein the confirming the identity of the user includes obtaining an advance approval from a telephone at the telephone number of the user, wherein the approving the request is based at least in part on the advance approval, wherein the advance approval includes at least one of: a time limit for expiration of the advance approval, a budget limit for the advance approval, and a limit on payees for the advance approval, wherein the advance approval is associated with the user terminal;
receiving the payment request from the user terminal, the payment request including a telephone number of the user;
approving the payment request based on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, wherein the pattern is based at least in part on time instance of the payment request;
processing the payment request using funds associated with the telephone number.
23. A system, comprising:
a data storage facility to store and associate an account identifier of a user with a telephone number of the user; and
an interchange coupled with the data storage facility, the interchange including a common format processor and a plurality of converters to interface with a plurality of controllers, the converters configured to communicate with the controllers in different formats, the converters to communicate with the common format processor in a common format, the common format processor to instruct a first controller of the controllers, via a first converter of the converters, to communicate with a telephone at the telephone number of the user to confirm an identity of the user of a user terminal separate from the telephone, wherein the confirming the identity of the user comprises receiving the telephone number of the user from the user terminal, transmitting a first code to a mobile device at the telephone number of the user, receiving a second code from the mobile device at the telephone number and matching the first code and the second code to confirm the identity of the user, wherein the confirming the identity of the user includes obtaining an advance approval from a telephone at the telephone number of the user, wherein the approving the request is based at least in part on the advance approval, wherein the advance approval includes at least one of: a time limit for expiration of the advance approval, a budget limit for the advance approval, and a limit on payees for the advance approval, wherein the advance approval is associated with the user terminal, subsequent to confirming the identity of the user, the interchange to receive a payment request including the phone number of the user from the user terminal, the interchange, wherein the pattern is based at least in part on time instance of the payment request, to approve the payment request based at least in part on the confirming of the identity of the user, wherein the approving is further based on matching the payment request with a pattern of the separate payment requests, and to process the payment request using the account identifier stored and associated with the telephone number on the data storage facility.
Patent Citations (244)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5283829(A) | 1994-02-01 | Anderson | Applicant |
| US5708422(A) | 1998-01-01 | Blonder et al. | Applicant |
| US5845260(A) | 1998-12-01 | Nakano et al. | Applicant |
| US5905873(A) | 1999-05-01 | Hartmann et al. | Applicant |
| US5914472(A) | 1999-06-01 | Foladare et al. | Applicant |
| US5953710(A) | 1999-09-01 | Fleming | Applicant |
| US6227447(B1) | 2001-05-01 | Campisano | Applicant |
| US6282276(B1) | 2001-08-01 | Felger | Applicant |
| US6302326(B1) | 2001-10-01 | Symonds et al. | Applicant |
| US6473808(B1) | 2002-10-01 | Yeivin et al. | Applicant |
| US6612488(B2) | 2003-09-01 | Suzuki | Applicant |
| US6704409(B1) | 2004-03-01 | Dilip et al. | Applicant |
| US6718178(B1) | 2004-04-01 | Sladek et al. | Applicant |
| US6788771(B2) | 2004-09-01 | Manto | Applicant |
| US6807410(B1) | 2004-10-01 | Pailles et al. | Applicant |
| US6928558(B1) | 2005-08-01 | Allahwerdi et al. | Applicant |
| US6965872(B1) | 2005-11-01 | Grdina | Applicant |
| US6996409(B2) | 2006-02-01 | Gopinath et al. | Applicant |
| US7013125(B2) | 2006-03-01 | Henrikson et al. | Examiner |
| US7080049(B2) | 2006-07-01 | Truitt et al. | Applicant |
| US7089208(B1) | 2006-08-01 | Levchin et al. | Applicant |
| US7107068(B2) | 2006-09-01 | Benzon et al. | Applicant |
| US7174301(B2) | 2007-02-01 | Florance et al. | Applicant |
| US7221951(B2) | 2007-05-01 | Anvekar et al. | Applicant |
| US7292996(B2) | 2007-11-01 | Nobrega et al. | Applicant |
| US7308254(B1) | 2007-12-01 | Rissanen | Applicant |
| US7315541(B1) | 2008-01-01 | Housel et al. | Applicant |
| US7331518(B2) | 2008-02-01 | Rable | Applicant |
| US7357310(B2) | 2008-04-01 | Calabrese et al. | Applicant |
| US7366702(B2) | 2008-04-01 | David | Applicant |
| US7374079(B2) | 2008-05-01 | Nam et al. | Applicant |
| US7386477(B2) | 2008-06-01 | Fano | Applicant |
| US7413119(B2) | 2008-08-01 | Kubo et al. | Examiner |
| US7437331(B1) | 2008-10-01 | Rosenberger | Applicant |
| US7458507(B2) | 2008-12-01 | Fillinger et al. | Applicant |
| US7478055(B2) | 2009-01-01 | Goino | Applicant |
| US7487114(B2) | 2009-02-01 | Florance et al. | Applicant |
| US7527192(B1) | 2009-05-01 | Chaskin et al. | Applicant |
| US7558777(B1) | 2009-07-01 | Santos | Examiner |
| US7748614(B2) | 2010-07-01 | Brown | Applicant |
| US7752135(B2) | 2010-07-01 | Brown et al. | Applicant |
| US7792518(B2) | 2010-09-01 | Trioano et al. | Applicant |
| US7848500(B2) | 2010-12-01 | Lynam et al. | Applicant |
| US7870044(B2) | 2011-01-01 | Robertson | Applicant |
| US7870077(B2) | 2011-01-01 | Woo et al. | Applicant |
| US7890433(B2) | 2011-02-01 | Singhal | Applicant |
| US8073774(B2) | 2011-12-01 | Pousti | Applicant |
| US8116730(B2) | 2012-02-01 | Smith | Applicant |
| US2001/0003093(A1) | 2001-06-01 | Lundin | Applicant |
| US2001/0037264(A1) | 2001-11-01 | Husemann et al. | Applicant |
| US2002/0013727(A1) | 2002-01-01 | Lee | Applicant |
| US2002/0016769(A1) | 2002-02-01 | Barbara et al. | Applicant |
| US2002/0035539(A1) | 2002-03-01 | O'Connell | Applicant |
| US2002/0059146(A1) | 2002-05-01 | Keech | Applicant |
| US2002/0087471(A1) | 2002-07-01 | Ganesan et al. | Applicant |
| US2002/0111908(A1) | 2002-08-01 | Milberger et al. | Applicant |
| US2002/0120582(A1) | 2002-08-01 | Elston et al. | Applicant |
| US2002/0193094(A1) | 2002-12-01 | Lawless et al. | Applicant |
| US2003/0065525(A1) | 2003-04-01 | Giachhetti et al. | Applicant |
| US2003/0119478(A1) | 2003-06-01 | Nagy et al. | Applicant |
| US2003/0125969(A1) | 2003-07-01 | Kizer et al. | Applicant |
| US2003/0126076(A1) | 2003-07-01 | Kwok | Applicant |
| US2003/0212601(A1) | 2003-11-01 | Silva et al. | Applicant |
| US2004/0019564(A1) | 2004-01-01 | Goldthwaite et al. | Applicant |
| US2004/0044582(A1) | 2004-03-01 | Chowdhary | Applicant |
| US2004/0122685(A1) | 2004-06-01 | Bunce | Applicant |
| US2004/0185827(A1) | 2004-09-01 | Parks | Applicant |
| US2004/0230257(A1) | 2004-11-01 | Hansen et al. | Applicant |
| US2004/0248596(A1) | 2004-12-01 | Panchal | Applicant |
| US2004/0252814(A1) | 2004-12-01 | Eakin | Applicant |
| US2005/0055296(A1) | 2005-03-01 | Hattersley et al. | Applicant |
| US2005/0055309(A1) | 2005-03-01 | Williams et al. | Applicant |
| US2005/0086164(A1) | 2005-04-01 | Kim et al. | Applicant |
| US2005/0177442(A1) | 2005-08-01 | Sullivan et al. | Applicant |
| US2005/0177517(A1) | 2005-08-01 | Leung et al. | Applicant |
| US2005/0199709(A1) | 2005-09-01 | Linlor | Applicant |
| US2005/0245257(A1) | 2005-11-01 | Woodhill | Applicant |
| US2006/0018450(A1) | 2006-01-01 | Sandberg-Diment | Applicant |
| US2006/0131390(A1) | 2006-06-01 | Kim | Applicant |
| US2006/0206709(A1) | 2006-09-01 | Labrou et al. | Applicant |
| US2006/0248011(A1) | 2006-11-01 | Hecht-Nielsen | Applicant |
| US2006/0253335(A1) | 2006-11-01 | Keena et al. | Applicant |
| US2006/0258331(A1) | 2006-11-01 | Syrett et al. | Examiner |
| US2006/0259438(A1) | 2006-11-01 | Randle et al. | Applicant |
| US2006/0276171(A1) | 2006-12-01 | Pousti | Applicant |
| US2006/0294025(A1) | 2006-12-01 | Mengerink | Applicant |
| US2007/0005467(A1) | 2007-01-01 | Haigh et al. | Applicant |
| US2007/0011104(A1) | 2007-01-01 | Leger et al. | Applicant |
| US2007/0022019(A1) | 2007-01-01 | Sherwin et al. | Applicant |
| US2007/0027775(A1) | 2007-02-01 | Hwang | Applicant |
| US2007/0027803(A1) | 2007-02-01 | Brandes et al. | Applicant |
| US2007/0043664(A1) | 2007-02-01 | Wilkes | Applicant |
| US2007/0055440(A1) | 2007-03-01 | Denker et al. | Applicant |
| US2007/0061244(A1) | 2007-03-01 | Ramer et al. | Applicant |
| US2007/0063017(A1) | 2007-03-01 | Chen et al. | Applicant |
| US2007/0094080(A1) | 2007-04-01 | Wilken | Applicant |
| US2007/0118477(A1) | 2007-05-01 | Graves et al. | Applicant |
| US2007/0123219(A1) | 2007-05-01 | Lovell, Jr. | Applicant |
| US2007/0123229(A1) | 2007-05-01 | Pousti | Applicant |
| US2007/0124490(A1) | 2007-05-01 | Kalavade et al. | Applicant |
| US2007/0130025(A1) | 2007-06-01 | Nakajima | Applicant |
| US2007/0130044(A1) | 2007-06-01 | Rowan | Applicant |
| US2007/0133768(A1) | 2007-06-01 | Singh | Applicant |
| US2007/0168462(A1) | 2007-07-01 | Grossberg | Applicant |
| US2007/0175978(A1) | 2007-08-01 | Stambaugh | Applicant |
| US2007/0198510(A1) | 2007-08-01 | Ebanks | Applicant |
| US2007/0203836(A1) | 2007-08-01 | Dodin | Applicant |
| US2007/0208632(A1) | 2007-09-01 | Downes et al. | Applicant |
| US2007/0233597(A1) | 2007-10-01 | Petersen et al. | Applicant |
| US2007/0244731(A1) | 2007-10-01 | Barhydt et al. | Applicant |
| US2007/0244811(A1) | 2007-10-01 | Tumminaro et al. | Applicant |
| US2007/0250711(A1) | 2007-10-01 | Storey | Applicant |
| US2007/0255653(A1) | 2007-11-01 | Tumminard et al. | Applicant |
| US2007/0255662(A1) | 2007-11-01 | Tumminaro et al. | Applicant |
| US2007/0260556(A1) | 2007-11-01 | Pousti | Applicant |
| US2007/0265921(A1) | 2007-11-01 | Rempe | Applicant |
| US2007/0266034(A1) | 2007-11-01 | Pousti | Applicant |
| US2007/0266130(A1) | 2007-11-01 | Mazur et al. | Applicant |
| US2007/0270125(A1) | 2007-11-01 | Pousti | Applicant |
| US2008/0000923(A1) | 2008-01-01 | Pousti | Applicant |
| US2008/0010192(A1) | 2008-01-01 | Rackley, III et al. | Applicant |
| US2008/0040139(A1) | 2008-02-01 | Pousti | Applicant |
| US2008/0040265(A1) | 2008-02-01 | Rackley, III et al. | Applicant |
| US2008/0040733(A1) | 2008-02-01 | Pousti | Applicant |
| US2008/0051122(A1) | 2008-02-01 | Fisher | Applicant |
| US2008/0052091(A1) | 2008-02-01 | Vawter | Applicant |
| US2008/0052363(A1) | 2008-02-01 | Pousti | Applicant |
| US2008/0057904(A1) | 2008-03-01 | Pousti | Applicant |
| US2008/0082509(A1) | 2008-04-01 | Bessieres et al. | Applicant |
| US2008/0091614(A1) | 2008-04-01 | Bas Bayod et al. | Applicant |
| US2008/0097851(A1) | 2008-04-01 | Bemmel et al. | Applicant |
| US2008/0103984(A1) | 2008-05-01 | Choe et al. | Applicant |
| US2008/0109279(A1) | 2008-05-01 | Csoka | Applicant |
| US2008/0109528(A1) | 2008-05-01 | Knight et al. | Applicant |
| US2008/0120698(A1) | 2008-05-01 | Ramia | Applicant |
| US2008/0126145(A1) | 2008-05-01 | Rackley, III et al. | Applicant |
| US2008/0133403(A1) | 2008-06-01 | Hamzeh | Applicant |
| US2008/0133735(A1) | 2008-06-01 | Thayer et al. | Applicant |
| US2008/0140569(A1) | 2008-06-01 | Handel | Applicant |
| US2008/0154727(A1) | 2008-06-01 | Carlson | Applicant |
| US2008/0154772(A1) | 2008-06-01 | Carlson | Applicant |
| US2008/0167017(A1) | 2008-07-01 | Wentker et al. | Applicant |
| US2008/0177628(A1) | 2008-07-01 | Payette | Applicant |
| US2008/0177661(A1) | 2008-07-01 | Mehra | Applicant |
| US2008/0189186(A1) | 2008-08-01 | Choi et al. | Applicant |
| US2008/0189211(A1) | 2008-08-01 | Obadia et al. | Applicant |
| US2008/0201201(A1) | 2008-08-01 | Pousti | Applicant |
| US2008/0208739(A1) | 2008-08-01 | Phillips | Applicant |
| US2008/0228595(A1) | 2008-09-01 | Hill et al. | Applicant |
| US2008/0233918(A1) | 2008-09-01 | Pousti | Applicant |
| US2008/0275779(A1) | 2008-11-01 | Lakshminarayanan | Applicant |
| US2008/0281726(A1) | 2008-11-01 | Gupta | Applicant |
| US2008/0287095(A1) | 2008-11-01 | Pousti | Applicant |
| US2008/0288299(A1) | 2008-11-01 | Schultz | Applicant |
| US2008/0288351(A1) | 2008-11-01 | Leung et al. | Applicant |
| US2009/0006184(A1) | 2009-01-01 | Leach et al. | Applicant |
| US2009/0006217(A1) | 2009-01-01 | Smith | Applicant |
| US2009/0024614(A1) | 2009-01-01 | Pousti | Applicant |
| US2009/0029687(A1) | 2009-01-01 | Ramer et al. | Applicant |
| US2009/0044216(A1) | 2009-02-01 | McNicoll | Applicant |
| US2009/0055292(A1) | 2009-02-01 | Chong et al. | Applicant |
| US2009/0063178(A1) | 2009-03-01 | Pousti et al. | Applicant |
| US2009/0063312(A1) | 2009-03-01 | Hurst | Applicant |
| US2009/0070583(A1) | 2009-03-01 | Von Mueller et al. | Applicant |
| US2009/0081989(A1) | 2009-03-01 | Wuhrer | Applicant |
| US2009/0104888(A1) | 2009-04-01 | Cox | Applicant |
| US2009/0112765(A1) | 2009-04-01 | Skowronek | Applicant |
| US2009/0112768(A1) | 2009-04-01 | Hammad et al. | Applicant |
| US2009/0119190(A1) | 2009-05-01 | Realinij | Applicant |
| US2009/0124238(A1) | 2009-05-01 | Wilson | Applicant |
| US2009/0150257(A1) | 2009-06-01 | Abrams et al. | Applicant |
| US2009/0156170(A1) | 2009-06-01 | Rossano et al. | Applicant |
| US2009/0157792(A1) | 2009-06-01 | Fiatal | Applicant |
| US2009/0172402(A1) | 2009-07-01 | Tran | Applicant |
| US2009/0177581(A1) | 2009-07-01 | Garcia et al. | Applicant |
| US2009/0182634(A1) | 2009-07-01 | Park et al. | Applicant |
| US2009/0182674(A1) | 2009-07-01 | Patel et al. | Applicant |
| US2009/0192928(A1) | 2009-07-01 | Abifaker | Applicant |
| US2009/0204546(A1) | 2009-08-01 | Haidar | Applicant |
| US2009/0216687(A1) | 2009-08-01 | Burdick | Applicant |
| US2009/0220060(A1) | 2009-09-01 | Wilson | Applicant |
| US2009/0248483(A1) | 2009-10-01 | Kiefer | Applicant |
| US2009/0265273(A1) | 2009-10-01 | Guntupali et al. | Applicant |
| US2009/0281904(A1) | 2009-11-01 | Pharris | Applicant |
| US2010/0010911(A1) | 2010-01-01 | Smith | Applicant |
| US2010/0015944(A1) | 2010-01-01 | Smith | Applicant |
| US2010/0015957(A1) | 2010-01-01 | Smith | Applicant |
| US2010/0017285(A1) | 2010-01-01 | Smith | Applicant |
| US2010/0049654(A1) | 2010-02-01 | Pilo | Applicant |
| US2010/0057623(A1) | 2010-03-01 | Kapur et al. | Applicant |
| US2010/0070757(A1) | 2010-03-01 | Martinez | Applicant |
| US2010/0094732(A1) | 2010-04-01 | Smith | Applicant |
| US2010/0106620(A1) | 2010-04-01 | Marcus | Applicant |
| US2010/0114775(A1) | 2010-05-01 | Griffen | Applicant |
| US2010/0125514(A1) | 2010-05-01 | Blackhurst et al. | Applicant |
| US2010/0145802(A1) | 2010-06-01 | Nowacek et al. | Applicant |
| US2010/0153249(A1) | 2010-06-01 | Yuan et al. | Applicant |
| US2010/0179907(A1) | 2010-07-01 | Atkinson | Applicant |
| US2010/0190471(A1) | 2010-07-01 | Smith | Applicant |
| US2010/0191646(A1) | 2010-07-01 | Smith | Applicant |
| US2010/0191648(A1) | 2010-07-01 | Smith | Applicant |
| US2010/0217696(A1) | 2010-08-01 | Schuba et al. | Applicant |
| US2010/0223183(A1) | 2010-09-01 | Smith | Applicant |
| US2010/0235276(A1) | 2010-09-01 | Smith | Applicant |
| US2010/0250359(A1) | 2010-09-01 | Gillenson et al. | Applicant |
| US2010/0250687(A1) | 2010-09-01 | Smith | Applicant |
| US2010/0267362(A1) | 2010-10-01 | Smith et al. | Applicant |
| US2010/0299220(A1) | 2010-11-01 | Baskerville | Applicant |
| US2010/0299731(A1) | 2010-11-01 | Atkinson | Applicant |
| US2010/0306015(A1) | 2010-12-01 | Kingston | Applicant |
| US2010/0306099(A1) | 2010-12-01 | Hirson | Applicant |
| US2010/0312645(A1) | 2010-12-01 | Niejadlik | Applicant |
| US2010/0312678(A1) | 2010-12-01 | Davis | Applicant |
| US2011/0010292(A1) | 2011-01-01 | Giordano et al. | Applicant |
| US2011/0022484(A1) | 2011-01-01 | Smith et al. | Applicant |
| US2011/0035264(A1) | 2011-02-01 | Zaloom | Applicant |
| US2011/0035302(A1) | 2011-02-01 | Martell et al. | Applicant |
| US2011/0065418(A1) | 2011-03-01 | Ryu et al. | Applicant |
| US2011/0071922(A1) | 2011-03-01 | Goodsall et al. | Applicant |
| US2011/0072039(A1) | 2011-03-01 | Tayloe | Applicant |
| US2011/0078077(A1) | 2011-03-01 | Hirson | Applicant |
| US2011/0082767(A1) | 2011-04-01 | Ryu et al. | Applicant |
| US2011/0082772(A1) | 2011-04-01 | Hirson | Applicant |
| US2011/0125610(A1) | 2011-05-01 | Goodsall et al. | Applicant |
| US2011/0143710(A1) | 2011-06-01 | Hirson | Applicant |
| US2011/0143711(A1) | 2011-06-01 | Hirson | Applicant |
| US2011/0295750(A1) | 2011-12-01 | Rammal | Applicant |
| GB2379525 | 2003-03-01 | Applicant | |
| JP2007109014 | 2007-04-01 | Applicant | |
| JP2007179383 | 2007-07-01 | Applicant | |
| KR20000036574 | 2000-07-01 | Applicant | |
| KR20030030684 | 2003-04-01 | Applicant | |
| KR20060103797 | 2006-10-01 | Applicant | |
| KR20070051817 | 2007-05-01 | Applicant | |
| KR20070103650 | 2007-10-01 | Applicant | |
| KR20080011338 | 2008-02-01 | Applicant | |
| WO9738538 | 1997-10-01 | Applicant | |
| WO-2006/092726(A2) | 2006-09-01 | Applicant | |
| WO-2007004792 | 2007-01-01 | Applicant | |
| WO-2007084593 | 2007-07-01 | Applicant | |
| WO2007102648 | 2007-09-01 | Applicant | |
| WO2007127521 | 2007-11-01 | Applicant | |
| WO-2009/036511 | 2009-03-01 | Applicant | |
| WO2009044396 | 2009-04-01 | Applicant |
Non-Patent Literature (54)
- Amazon.com, Inc., “Get Gold Box Deals Every Day with Amazon Text Alerts,” located at http://www.amazon.com/gp/anywhere/sms/goldbox, available at least by Jun. 10, 2009.Applicant
- Aradiom Inc., “The Real Solution—Aradiom SolidPass”, located at http://www.aradiom.com/SolidPass/2fa-OTP-security-token.htm, available at least by Apr. 24, 2009.Applicant
- Chua, Lye Heng, “How Customers Applied Java CAPS?” Sun Microsystems, Inc. presentation, Nov. 6, 2007.Applicant
- Hassinen, Marko et al., “An Open, PKI-Based Mobile Payment System,” Emerging Trends in Information and Communication Security, Lecture Notes in Computer Science, vol. 3995/2006, pp. 86-89, Jun. 1, 2006.Applicant
- International Application No. PCT/US10/24525, International Search Report and Written Opinion, May 17, 2010.Applicant
- International Application No. PCT/US10/57472, International Search Report and Written Opinion, Jan. 18, 2011.Applicant
- International Application No. PCT/US10/59295, International Search Report and Written Opinion, Feb. 1, 2011.Applicant
- International Application No. PCT/US10/59466, International Search Report and Written Opinion, Feb. 1, 2011.Applicant
- International Application No. PCT/US11/22419, International Search Report and Written Opinion, Mar. 29, 2011.Applicant
- International Application No. PCT/US11/22426, International Search Report and Written Opinion, Mar. 28, 2011.Applicant
- International Application No. PCT/US2009/033823, International Search Report and Written Opinion, Sep. 24, 2009.Applicant
- International Application No. PCT/US2009/039723, International Search Report and Written Opinion, Oct. 30, 2009.Applicant
- International Application No. PCT/US2010/020189, International Search Report and Written Opinion, Dec. 10, 2010.Applicant
- International Application No. PCT/US2010/021054, International Search Report and Written Opinion, Jul. 29, 2010.Applicant
- International Application No. PCT/US2010/024535, International Search Report and Written Opinion, May 25, 2010.Applicant
- International Application No. PCT/US2010/030338, International Search Report & Written Opinion, Jun. 3, 2010.Applicant
- International Application No. PCT/US2010/032668, International Search Report and Written Opinion, Jul. 1, 2010.Applicant
- International Application No. PCT/US2010/036940, International Search Report and Written Opinion, Jul. 21, 2010.Applicant
- International Application No. PCT/US2010/037816, International Search Report and Written Opinion, Aug. 5, 2010.Applicant
- International Application No. PCT/US2010/042703, International Search Report and Written Opinion, Sep. 13, 2010.Applicant
- International Application No. PCT/US2010/046266, International Search Report and Written Opinion, Oct. 20, 2010.Applicant
- Mobilians Co. Ltd., company website located at http://www.mobilians.co.kr/english/, available at least by Jan. 12, 2009.Applicant
- PayPal, Inc., “Get What You Want, When You Want It,” located at https://www.paypal.com/cgi-bin/webscr?cmd=xpt/Marketing/mobile/MobileBuyStuff-outside, available at least by Mar. 5, 2009.Applicant
- PayPal, Inc., “Texting with PayPal—Easy as Lifting a Finger,” located at https://www.paypal.com/cgi-bin/webscr?cmd=xpt/Marketing/mobile/MobileAdvancedFeatures-outside, available at least by Mar. 5, 2009.Applicant
- Squidoo, LLC, “Introducing MobillCash: Make a Secure Sale Even When an Online Customer Has No Cash, Credit Cards or I.D.,” located at http://www.squidoo.com/mobillcash-pay-by-mobile-phone, available at least by Aug. 29, 2008.Applicant
- Sun Microsystems Inc., “The Road to Mobile Banking,” white paper, Jun. 2008.Applicant
- Tindal, Suzanne, “St. George Counts Down to Two-Factor Authentication,” ZDNet Australia, Feb. 19, 2008.Applicant
- Trusted Mobile Payment Framework, “Scheme Rules,” version 2.0, Aug. 6, 2008.Applicant
- VISUALtron Software Corporation, “2-Factor Authentication—What is MobileKey?” located at http://www.visualtron.com/products—mobilekey.htm, available at least by 2008.Applicant
- Wikimedia Foundation, Inc., “Authentication,” located at en.wikipedia.org/wiki/Authentication, Mar. 17, 2009.Applicant
- Wikimedia Foundation, Inc., “Credit Card,” located at en/wikipedia.org/wiki/Credit—card, Dec. 5, 2008.Applicant
- Wikimedia Foundation, Inc., “Security Token,” located at en.wikipedia.org/wiki/Security—token, Apr. 13, 2009.Applicant
- Wikimedia Foundation, Inc., “Two-Factor Authentication,” located at en.wikipedia.org/wiki/Two-factor—authentication, Apr. 24, 2009.Applicant
- Zabawskyj, Bohdan, “In the Media: The Mobile Money Opportunity,” Billing World and OSS Today, located at http://www.redknee.com/news—events/in—the—media/43/?PHPSESSID=1e0ca1ab057bf9dc2c88104877ca8010, Sep. 2007.Applicant
- European Patent Application No. 09711520.8, Extended Search Report mailed Apr. 27, 2011.Applicant
- International Application No. PCT/US2010/050616, International Search Report and Written Opinion, Apr. 26, 2011.Applicant
- International Application No. PCT/US2011/029760, International Search Report and Written Opinion,, Oct. 28, 2011.Applicant
- International Application No. PCT/US2011/051094, International Search Report and Written Opinion, Date: Dec. 23, 2011.Applicant
- International Application No. PCT/US2011/30039, International Search Report and Written Opinion, May 23, 2011.Applicant
- International Application No. PCT/US2011/30038, International Search Report and Written Opinion, May 25, 2011.Applicant
- ONEBIP S.R.L , “OneBip—to Pay Online with Your Mobile Phone”, Youtube online video at http://www.youtube.com/watch?v=RiEsMcc0tJY, May 23, 2007.Applicant
- Arrington, Michael , “Mobile Payments Getting Traction on Social Networks but Fees are Sky High”, Tech Crunch, located a http://techcrunch.com/2009/01/13mobile-payments-getting-traction-on-social-networks-but-fees-are-sky-high/,, Jan. 13, 2009.Applicant
- Brooks, Rod , “MobilCash:Worlds First in Mobile Payments”, YouTube online video located at http://youtube.com/wacth?v=j6Xv35qSmbg,, Oct. 12, 2007.Applicant
- Bruene, Jim , “PayPal Launches on Facebook: Who Wants to be the First Bank?”, located at http://www.netbanker.com/2007/06paypal—launches—on—facebook—who—wants—to—be—the—first—bank—on—facebook.hml,, Jun. 22, 2007.Applicant
- Chen, Will , “Gift Shop Credits Have Arrived”, The Facebook Blog, located at gttp://blog.facebook.com/blog.php?post=36577782130, Oct. 31, 2008.Applicant
- Federal Trade Commission, , “Children's Online Privacy Protection Act (COPPA)”, 15 U.S.C. §§ 6501-6506, Oct. 21, 1998.Applicant
- Ihlwan, Moon , “In Korea, Cell Phones Get a New Charge”, http://businessweek.com/globalbiz/content/mar2006/gb20060301—260288.htm, Mar. 1, 2006.Applicant
- Lee, Jessica , “Payment Industry Perspectives: Q&A with Zong CEO David Marcus”, http://www.insidefacebook.com/2009/05/19payment-industry-perspectives-qa-with-zong-ceo-david-marcus/, May 19, 2009.Applicant
- Nicole, Kirsten , “Pay me Lets You Send and Receive Money Through Facebook”, http://mashable.com/2007/06/17pay-me-facebook-app, Jun. 17, 2007.Applicant
- Zong, Inc., , “Virtual Goods/Currency and Mobile Payments: The Business Model for Social Apps”, The Zong Blog at http://blog-zong.com/2008/10/25/virtual-goods-currency-and-mobile-payments-the business-model-for-social-apps/, Oct. 28, 2008.Applicant
- Zong, Inc., , “Zong Mobile Payment Demo on A Facebook App”, You Tube online video at http://www.youtube.com/watch?v=aLjRcAFrGil, Jan. 5, 2009.Applicant
- Zong, Inc. “Zong-Mobile Payments for Your Web App”, You tube online video at http://www.youtube.com/watch?v=O2C3SQraAvQ, Sep. 5, 2008l.Applicant
- Zong, Inc., , “Zong Mobile Payments in Smallworlds”, You Tube online video at htttp://www.youtube.com/watch?v=Y6CEw3tSgBc, Feb. 10, 2009.Applicant
- International Application No. PCT/US12/25195, International Filing Date Feb. 15, 2012, International Search Report and Written Opinion, Apr. 26, 2012.Applicant