US20140207689A1 - Secure payment and billing method using mobile phone number or account - Google Patents
Secure payment and billing method using mobile phone number or account Download PDFInfo
- Publication number
- US20140207689A1 US20140207689A1 US14/222,616 US201414222616A US2014207689A1 US 20140207689 A1 US20140207689 A1 US 20140207689A1 US 201414222616 A US201414222616 A US 201414222616A US 2014207689 A1 US2014207689 A1 US 2014207689A1
- Authority
- US
- United States
- Prior art keywords
- payment
- mobile
- mobile phone
- operator
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/16—Payments settled via telecommunication systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
- G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/386—Payment protocols; Details thereof using messaging services or messaging apps
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1467—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network involving prepayment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/126—Applying verification of the received information the source of the received data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4012—Verifying personal identification numbers [PIN]
Abstract
Description
- The present invention is a continuation of co-pending, U.S. patent application Ser. No. 13/148,043 of Rammal, entitled “SECURE PAYMENT AND BILLING METHOD USING MOBILE PHONE NUMBER OR ACCOUNT,” filed on Aug. 4, 2011, now allowed, which claims the benefit of priority from PCT Patent Application Serial No. PCT/US10/23863 of Rammal, entitled “SECURE PAYMENT AND BILLING METHOD USING MOBILE PHONE NUMBER OR ACCOUNT,” filed on Feb. 11, 2010, now expired, U.S. Provisional Patent Application Ser. No. 61/152,696 of Rammal, entitled “SECURE PAYMENT AND BILLING METHOD USING MOBILE PHONE NUMBER OR ACCOUNT,” filed on Feb. 14, 2009, now expired, the entire contents of all of the disclosures of which are hereby incorporated by reference.
- 1. Field of the Invention
- The present invention generally relates to methods and systems for conducting secure purchase and payment transactions, and more particularly to a method, system and computer program product for conducting secure purchase and payment transactions using a mobile phone.
- 2. Discussion of the Background
- Customers in today's world have unprecedented access to retailers and merchants selling goods and/or services of all types in stores, through vendors and vending machines, restaurants and the internet. Beyond the traditional shopping practice of buying goods and services in ones own neighborhood, town, city, and country, access to foreign goods and services is made possible through travel and/or the internet.
- Once customers select their goods, they have several options to pay the retailer/merchant with. While cash is still “king,” customers have other payment options such as using credit cards, debit cards and payment service providers that act on behalf of customers as intermediaries between financial institutions and retailers to try and protect customer's financial and personal information. Other payment options also include, pre-paid credit/debit cards, stored value cards, bank checks, bank transfers, travelers checks, money order, demand drafts, money transfer using a third independent financial entity, E-mail payments, and mobile wallet applications that act as intermediaries or interfaces between a customer's financial institution (typically a bank or a credit card company) and the retailer/merchant. Certain computer based financial services software programs also provide transaction payment features.
- However, all these payment options have their merits and demerits and various complexities. Customers are still weary about giving their credit card and personal information to pay for purchases on the internet, even at stores, restaurants and vending machines as fraud and identity theft cases have occurred and are on the rise. Given the surge in identity theft, one can't blame customers for fearing the worst. In addition, use of the other financial transaction instruments may be costly or sheer complex cumbersome.
- Accordingly, customers are constantly looking to simplify their life and reduce complexities in any way possible as long as it doesn't jeopardize their personal or financial security. Given that security, fraud and identity theft are major concerns, it is imperative that customers are protected. Customers are also weary of unreasonable hidden costs that are additionally charged by credit cards, mobile wallets and other financial instruments that are above and beyond what the retailer is already charging.
- Conventional systems of payment and methods using mobile phones have limitations, including requiring downloading of complex software, need to use hi-tech mobile phones, need for additional security codes, hidden costs, and additional charges by the customer's bank or credit card company. In addition, such complex mobile phone payment systems and other payment methods are also limited in their availability and usage for the world's population at large that purchases goods and services. The estimate for the world's population stands at 6.6 billion in 2008. Less than 30% of the world's population has credit cards. However, almost 70% of the world's population has a mobile phone and an active mobile account and a robust system and method to leverage this market has yet to be developed.
- Accordingly, there is a need for a method and system that addresses the above and other problems with convention transaction and payment systems to leverage the opportunity for a mobile phone user, anywhere in the world, with the most basic mobile phone device, a mobile number/account, and a mobile phone service provider to be able to pay for goods and services locally as well as globally using their mobile phone number/account. The above and other needs are addressed by the exemplary method and system for conducting secure purchase payment transactions using a mobile (e.g., a cell phone) phone number (or e.g., a mobile phone account number) which, at the prompt of the retailer, via a payment processor and the customer's mobile phone service provider, is then approved and authenticated by the customer/user using their unique password or PIN Code, and hence their mobile phone account is debited by the mobile phone service provider (e.g., who may or may not include an additional charge) who then pays the payment processor who then pays the retailer.
- Accordingly, in exemplary aspect of the present invention there is provided a novel system, method and computer program product for processing payments for goods or services, including a payment processor that receives a payment request from a merchant for goods or services and that includes a mobile phone number or mobile phone account of a user, sends a payment authorization request text message to the mobile phone requesting payment authorization, and receives a payment authorization text message from the mobile phone authorizing or not authorizing the payment. If the payment is authorized, the payment processor pays the merchant and charges the mobile phone account for the payment. If the payment is not authorized or if the payment is not received within a predetermined period of time, the payment processor declines to pay the merchant for the goods or services.
- Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, by illustrating a number of exemplary embodiments and implementations, including the best mode contemplated for carrying out the present invention. The present invention is also capable of other and different embodiments, and its several details can be modified in various respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive.
- The embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
-
FIGS. 1-2 illustrate an exemplary process for customers to purchase goods and/or services from a retailer; -
FIGS. 3-7 illustrate an exemplary flow chart corresponding to the exemplary process ofFIGS. 1-2 ; and -
FIGS. 8-11 illustrate the operation of an exemplary system corresponding to the exemplary process and flow chart ofFIGS. 1-7 . - The present invention includes recognition of and addresses problems associated with conventional systems such those described in U.S. Pat. No. 5,991,749 and United States Patent Application Nos. 20050086164; 20050222917; 20070063017; and the like. Although such systems and methods may provide peer to peer deposits and value transfers, mobile device identification centric authentication, mobile wallet software, voice activated and device based user prompted payment functions, and mobile banking, etc., to address payment security and convenience to a certain level, such conventional system and methods still may compromise security, leave customers vulnerable to identity theft, and require complex customer billing systems and procedures. Advantageously, the exemplary method and system for conducting secure purchase payment transactions using a mobile phone number recognizes and addresses these and other limitations with such conventional systems and provide customer control over payment authorization, identity protection, and security through a simple and convenient payment method.
- Advantageously, the novel method and system of the exemplary embodiments addresses the above and other problems with conventional payment processing systems and methods and allow the 4 billion plus and growing mobile phone users worldwide to pay for goods and services through their mobile phone service provider, using their mobile phone number and/or mobile phone account number (also referred to as “mobile number” or “mobile phone number”) securely for goods and/or services they purchase locally and/or globally. The novel system and method enables online and offline commerce transactions using mobile phone numbers, with customers being billed by their mobile phone service provider/operator/carrier (also referred to as “mobile operator”).
- The novel system and method, advantageously, provides a simple and secure payment system based on a novel process that enables a customer to remain in control of the payment authorization process by using their mobile phone number to pay for purchases of goods and services, for example, at the point of sale or via the internet, via telephone sales persons or other interactive interfaces, via vending machines, other such retail environments and interfaces, and the like, or any other suitable way that a retailer or merchant may be selling goods and/or services, locally or globally, and get billed for the transaction by their mobile operator who then settles payment on the customer's behalf with the retailer through a payment processor.
- As compared with conventional systems, the novel system and process does not require mobile phone users to download any additional software on to their mobile phone devices, as long as their mobile phones are able to receive and send Short Message Service (SMS) text messages, and the like. Nor are users required to register or create any financial relationship with a retailer or vendor or a transaction payment processing/clearing house (also referred to as “payment processor”). Nor do users need to disclose their password or personal identification (PIN) code, and the like, to a retailer or a payment processor, advantageously enhancing security levels and protection against financial fraud and identity theft. By not requiring customers to establish a relationship between their financial institutions (e.g., banks, credit card companies, money managers and others) and/or retailers, and/or payment processors, the novel system and method provides a customer with the advantage of always being in control of authorizing the transaction payment, which is eventually billed to them through their mobile operator.
- The exemplary method involves a customer buying goods and/or services and opting to pay for the goods and/or services through their mobile operator by providing the retailer their mobile number (and e.g., related information where necessary, such as country that the mobile number is issued in and the name of the mobile operator that issued the mobile number, such as AT&T or T-Mobile or Verizon, etc.). The retailer then requests the customer's mobile operator's approval, and customer authentication and authorization to bill the payment charge to the customer's mobile number with the amount of the purchase (the customer's mobile operator may or may not add a surcharge in the case of pre-paid and may or may not in the case of post-paid customers) through a payment processor, for example, of a company that offers this novel service to retailers, mobile operators, and customers.
- The mobile operator checks the customer's mobile number account balance (or charge protocols that can be set mutually with post-paid and/or pre-paid customers) and if found sufficient to pay for the purchase (and any additional charges that the mobile operator may levy), sends a SMS text message to the customer on their mobile number giving them details of the retailer and the total amount payable (which may or may not include additional charges of the mobile operator), and requesting a response from the customer for approval via text message, replying with their unique PIN Code associated with the customer's mobile number and account, or a simple “no” as a response to reject the transaction payment (and which may not be necessary as the transaction will not consummate without a positive response in any case). In the case that the customer may decide not to respond, after a pre-set time lapse, the mobile operator will consider the customer's inaction as a “no” and reject the transaction payment.
- If, however, the customer wants to approve the transaction payment, the customer replies to the mobile operator's text message by simply sending a text message with their PIN Code for authentication purposes, allowing the mobile operator to then deduct or bill the amount to the customer's mobile number account. Upon receiving the PIN Code text message and having authenticated the customer's PIN Code, the mobile operator debits the customer's account balance for the total amount (e.g., including any additional mobile operator surcharges). The mobile operator then sends approval to the payment processor creating a liability to pay the net amount due as per the terms agreed between the two parties. By contrast, most conventional systems bill the customer's financial institution (e.g., a credit card company, bank, etc).
- The payment processor sends the approval to the retailer, creating a liability to pay the retailer the net amount due as per the terms agreed between the two parties. The retailer, upon receiving the approval from the payment processor, concludes the transaction and sends the customer a receipt via text message and/or other means such as email, mail, and the like. Advantageously, the retailer can include shipping information, promotional messages and/or coupons along with or following the receipt to the customer.
- Referring now to the drawings, wherein like reference numerals designate identical or corresponding parts throughout the several views and more particularly to
FIGS. 1-2 thereof there is illustrated an exemplary general process flow, according to an exemplary embodiment. InFIG. 1 , the process begins withcustomer 102 who interfaces/interacts 103 with a retailer's 104 store, e-store (e.g., web site), telephone sales persons, interactive voice response (IVR) system, vendor, restaurant, other such interface, and the like, and including personal face-to-face, purchase/consumption of goods and/or services.Customer 102 selects/purchases or consumes goods and/orservices 105 fromretailer 104 and proceeds to pay for it at check-out 106 where he has several payment options to choose from.Customer 102 chooses a mode ofpayment 107. Theretailer 104 requests customer's mobile number andrelated billing data 108 ofcustomer 102.Customer 102 provides data (a) 108 relating to his mobile number,mobile operator 112 and may or may not need to provide the country that the phone number is registered and issued in.Retailer 104 packages thecustomer 102 data (a) 108 and adds his invoice detail and sends data (b) 109 to apayment processor 110.Payment processor 110 adds their own transaction ID and other relevant information, to the retailer's data (b) 109 and sends data (c) 111 to the customer's 102mobile operator 112. - In
FIG. 2 , themobile operator 112 adds their transaction ID, other relevant information, and or any additional charges to the retailer's invoice and packages it as data (d) 212 and sends it as a Text message (e.g., a SMS text message, etc.) to the customer's 102 mobile number requesting approval or rejection of payment using a means of authentication/authorization with their PIN Code, or “no,” or ignoring the message (with a pre-set time lag) to reject the approval request.Customer 102 by authenticating/authorizing 213 approves the charge using a PIN Code sent via a reply through text message data (e) 214 to themobile operator 112, confirming the payment approval. Mobile operator sends an approval/confirmation data (f) 215 package to thepayment processor 110 creating a liability to pay as per the terms agreed between the two parties.Payment processor 110 sends approval confirmation with relevant transaction data (g) 216 to theretailer 104 creating a liability to pay as per the terms agreed between the two parties.Retailer 104 prepares receipt and sends data (h) 217 via text message and/or email or other such means, including but not limited to, mail tocustomer 102 to conclude the transaction. The data may include shipping and promotional information. -
FIGS. 3-7 illustrate an exemplary flow chart corresponding to the exemplary process ofFIGS. 1-2 . InFIG. 3 , thecustomer 301 selects goods and/or services, for example, from a retailer/vendor/merchant atstep 302 at a store, on the internet, vendor, vending machine, restaurant, mobile browser, through a telephone sales person or sales IVR, and/or other such sales avenues/interfaces as the customer may be presented with by the retailer. Retailer atstep 303 presents the customer with various payment options, for example, including cash, credit card, debit card, mobile wallet, mobile phone number or account, bank transfer, stored value cards, and others. - In
FIG. 4 , the retailer presents various payment options atstep 401 to the customer who selects a payment option atstep 402 and chooses to pay with the customer's mobile number atstep 403. Should the customer not choose to pay using the mobile number, step 403 ends the process. Customer provides information related to their mobile number for billing atstep 404 whereby the information can include, for example, mobile phone number, mobile operator and the country the mobile number and mobile operator are registered in. Retailer adds transaction details atstep 405, for example, including retailer name and ID, store number, invoice number, goods and/or services purchased, amount billed and payable by customer and sends it to the payment processor to seek payment approval, authorization and authentication from the customer and the customer's mobile operator's agreement, and that of the payment processor to pay the retailer on behalf of the customer. Payment processor adds a unique transaction ID code atstep 406 related to the information received by the retailer (e.g., whose account would already exist in the database of the payment processor) and any other information that may be relevant, and sends it across to the customer's mobile operator (whose account would also already exist in the database of the payment processor). - In
FIG. 5A , the payment processor sends the transaction data and ID and the amount payable by the customer to the customer's mobile operator atstep 501 who receives it atstep 502 and verifies the customer atstep 503. If the customer's mobile number is not verified as a customer of the mobile operator, then the error is referred to the payment processor and further detailed inFIG. 5B . If the mobile operator confirms the customer, it then proceeds to check their balance in the case of, for example, pre-paid customers, and/or the payment limit protocols as may be set/mutually agreed with the mobile operator in the case of, for example, post-paid customers atstep 504. If the pre-paid customer's balance is insufficient or the post-paid customer has exceeded their payment limit protocol, then the low balance or limit exceeded message is sent to the customer via text message and further detailed inFIG. 5C . If the balance and payment limit protocol is sufficient to cover the payment due to the retailer and an additional charge that may or may not be levied by the mobile operator, the customer is then sent a text message requesting approval for the mobile operator to charge the customer's mobile number to pay the retailer for the transaction atstep 505. The request for approval message includes, for example, information stating the retailer's name, total owed for purchases, plus the mobile operator charge (if applicable) and a request for approval by replying with the customer's PIN Code (that would′ve been already registered by the customer with the mobile operator for accessing voice mail and/or value added services and/or specifically created to access this transaction payment facility) in a text message to the mobile operator. To reject, the customer would need to send “NO” as a response or just ignore the message and a pre-set time lapse protocol at the mobile operator's end would consider no response from the customer as a rejection. -
FIG. 5B illustrates the steps associated with a customer verification error generated by the mobile operator inFIG. 5A step 503. InFIG. 5B , the mobile operator sends the payment processor a “customer verification error” indicating that the mobile number (hence the customer) as indicated by the retailer's data doesn't exist with the mobile operator atstep 507. The payment processor sends the mobile operator's message along with the transaction ID (and other data that may be applicable) to the retailer identifying the customer'smobile number error 508. Retailer receives the error and notifies the customer atstep 509. Customer receives notification of error atstep 510. Customer then decides whether to correct the error and provide their mobile number again or to use another payment option atstep 511. In case customer decides to choose another payment option atstep 512, retailer will provide that and go to process step as indicated inFIG. 4 step 402. If the customer decides to provide the retailer with their mobile phone number atstep 513, the retailer performsstep 403 ofFIG. 4 . -
FIG. 5C illustrates the steps associated with a customer's account balance with the mobile operator being insufficient to pay the total amount of the transaction (including mobile operator charge where applicable) or the customer's payment protocol limit has or would exceed with the amount that is payable for the transaction (including mobile operator charge where applicable). InFIG. 5C , the mobile operator sends the customer a notification regarding this issue atstep 514. Customer receives the notification atstep 515 and then decides whether or not to add money to their mobile phone account or to pay with another method/option atstep 516. In case customer decides to choose other option atstep 517, retailer will provide that atstep 402 ofFIG. 4 . If the customer decides to add money to their mobile phone account balance or increase their payment limit atstep 518, then they would need to inform the retailer atstep 519 to re-submit their mobile number payment information as inFIG. 4 step 405. - In
FIG. 6A , thestep 505 fromFIG. 5A is shown, whereby the mobile operator sends the customer a text message with the transaction information, including but not limited to, retailer's name, total amount payable to retailer, may or may not add mobile operator surcharge, and a request to approve or reject payment by replying with a text message to the mobile operator with either their PIN Code to approve the payment for the transaction, or reply “no” or simply ignore the message to affect a time lapse protocol at the mobile operator's end to reject the payment approval. Should the customer decide to reject the payment approval request by either replying “no” or simply ignoring the message and thus affecting a time lapse rejection protocol at the mobile operator end atstep 602, then the process is further detailed inFIG. 6B . If the customer approves the payment by sending their PIN Code in a text message reply to their mobile operator atstep 603, then the mobile operator receives the PIN Code atstep 604, verifies it atstep 605 and if correct, logs it as acceptance of the customer to be charged the total amount to the mobile number balance or bill. If the PIN Code fails the mobile operator authentication, the process is further detailed inFIG. 6C . -
FIG. 6B describes steps of the process in the case where the customer rejects the approval to pay and the mobile operator logs the customer's rejection to pay atstep 606 and sends the payment processor a notification of customer's rejection of payment along with the transaction ID and other relevant information atstep 607. InFIG. 6B , the payment processor tags and sends the rejection notification to the retailer atstep 608 who receives it atstep 609 and informs the customer to choose another payment option. Customer uses another payment option atstep 610, which goes to step 402 inFIG. 4 to choose a payment option. -
FIG. 6C describes steps of the process in the case where the PIN Code approval text message sent by the customer doesn't authenticate with the mobile operator's log of the customer's PIN Code authentication and the mobile operator then sends the error message to the customer atstep 611. InFIG. 6C , the customer receives the notification atstep 612 and follows the steps as per the process detailed inFIG. 6A ,step 603. This loop for PIN Code can be a predetermined amount times before it is understood that the customer can't remember their PIN Code and would be automatically treated as a rejection and the payment processor would be informed accordingly. For example, the customer can be sent a final text message by the mobile operator asking them to contact customer service for help. -
FIG. 7 describes the continuation of theprocess step 605 fromFIG. 6A , where the mobile operator verifies the customer's PIN Code successfully, and atstep 702 sends approval to the payment processor indicating the net amount that is payable between the two parties as per their agreement. InFIG. 7 , payment processor receives the approval notification and adds other transaction approval information and sends an approval notification to the retailer indicating the net amount that is payable between the two parties as per their agreement atstep 703. The retailer receives the payment processor's approval notification and logs it as transaction payment approved and cleared by the customer and payment owed by the payment processor atstep 704. The retailer also sends the customer a receipt via text message and/or email or other means such as, but not limited to, mail, indicating they have received indication of payment clearance and may include shipping and promotional information and/or a customer service number atstep 705, concluding the transaction payment process. - Advantageously, the novel method allows a customer to pay a retailer through their mobile operator via a payment processor. This method protects the financial information of the customer and their identity that is susceptible to theft and exploitation by malicious acts by parties that may or may not be part of the payment process. The present method as described above virtually presents an anti-fraudulent payment system that provides peace of mind and convenience to customers as they and their mobile operator are the only ones who know the PIN Code to authorize payments to retailers.
-
FIGS. 8-11 illustrate the operation of an exemplary system corresponding to the exemplary process and flow chart ofFIGS. 1-7 . InFIG. 8 , there is illustrated the mobilenumber payment system 800, according to an exemplary embodiment of the present invention. Thesystem 800, begins with thecustomer 801 who interacts with a retailer'sinterface 803 whereby selecting goods and/or services presented by the retailer to the customer to select and/or consume 802 through a variety of ways including, for example, retailer's Internet website (e-commerce/e-retail, shop/sales front), telephone sales/retail/catalogue shop/team (call center, catalogue sales), mobile phone enabled shop/sales presence using, for example, Wireless Application Protocol (WAP) technologies, and the like, interfacing with, for example, the internet, physical store front or other such establishment in the form of retail store/shop, including, for example, restaurants, vending machines, vendors, third party representatives, point-of-sale including, for example, services such as payment mechanisms configured for public transport such as taxis, buses, subways/metro/underground and over ground transport/trains/monorails, commercial aircraft/airlines/buses and other transport, toll-booths, ticket vendors/stands/internet sites for public and private events, exhibits and special occasions, and the like. - The customer selects/consumes goods and/or services and proceeds to pay for it at which point, the retailer provides
payment options 805 that they accept. The payment options include, for example, mobile number/account, cash, credit cards, debit cards, payment service provider, mobile wallet, mobile banking, stored value card, bank transfer, third party wire transfer, money order, travelers' checks, loyalty scheme value, and other such methods. - In
FIG. 9 , the customer selects the mobile phone number/account option 805 formobile number payment 902 to pay the retailer and provides the retailer details 901 of their account. Customer entersdetails 901 include the following information, for example, a mobile account/number, indicates the country that it belongs to and the name of the mobile operator. The retailer packages the customer's mobile data and the invoice details for the customer's purchase and electronically sends the data viaelectronic transmission 903 to a payment processor'sdatabase 904 through/over/using electronic data transmission means 903, for example, including: world wide web, the internet, point of sale, mobile phone with minimum of SMS text messaging capability, WAP enabled wire or wireless device which may or may not be a mobile phone, telephone and/or telephone call, interactive voice response over phone or mobile phone, telephone input system using interactive selection response (example: press “1” to select Country, Press “2” to select Operator, etc.), on paper, facsimile transmission, via email, postal mail, encrypted information transportability software running on devices capable of receiving and sending such encrypted information over, but not limited to wireless networks, telephone lines, cable networks, internet, mobile networks, and the like. - The payment processor's
database 904 identifies the retailer and thedata 901, logs the transaction, generates a transaction ID and sends the retailer's payment charge and approval request to the customer's mobile operator'sdatabase 906 through/over/using electronic data transmission means 903, for example, including: world wide web, the internet, point of sale, mobile phone with minimum of SMS text messaging capability, WAP enabled wire or wireless device which may or may not be a mobile phone, telephone and/or telephone call, interactive voice response over phone or mobile phone, telephone input system using interactive selection response (example: press “1” to enter customer's mobile number, Press “2” to enter charge, etc.), on paper, facsimile transmission, via email, postal mail, encrypted information transportability software running on devices capable of receiving and sending such encrypted information over, but not limited to wireless networks, telephone lines, cable networks, internet, mobile networks, and the like. - In
FIG. 10 , the mobile operator'sdatabase 906 receives the data, verifies the customer's mobile phone/account number, checks whether it has sufficient balance or is within the defined payment protocol as may have been agreed between customer and mobile operator, to pay for the retailer's charge (and the mobile operator's surcharge if any). Upon positive verification, the mobile operator'sdatabase 906 sends the customer a request via, for example,SMS text message 1001 on theirmobile phone 1002 for approval and authorization with theinformation 1003, for example, including: retailer's name from which the customer has purchased goods and/or services, retailer's invoice number, total payment owed (and the mobile operator's surcharge if any), and a request for the customer to reply the SMS text message back with their unique PIN Code to approve or “NO” or ignore the message to reject the charge. - Customer replies the mobile operator's message by sending their unique PIN Code to the mobile operator's
database 906 via, for example,SMS text message 1004 to approve that mobile operator can charge the total amount and deduct it from their mobile account balance or bill it to their monthly mobile account bill. The mobile operator'sdatabase 906 receives theSMS text message 1004 from the customer, verifies the PIN Code and deducts the charge from the customer's account balance or adds it to their monthly mobile phone bill. - In
FIG. 11 , the mobile phone operator'sdatabase 906 generates an approval message along with the original transaction ID and sends it to the payment processor'sdatabase 904 through/over/using electronic data transmission means 903, for example, including: world wide web, the internet, point of sale, mobile phone with minimum of SMS text messaging capability, WAP enabled wire or wireless device which may or may not be a mobile phone, telephone and/or telephone call, interactive voice response over phone or mobile phone, telephone input system using interactive selection response (example: press “1” to select Approval, Press “2” to select Rejection, press “3” to enter transaction ID, etc.), on paper, facsimile transmission, via email, postal mail, encrypted information transportability software running on devices capable of receiving and sending such encrypted information over, but not limited to wireless networks, telephone lines, cable networks, internet, mobile networks. - The payment processor's
database 904 receives the approval from the mobile operator'sdatabase 906 viaelectronic data transmission 903 and logs the approval and information, debits the operator's account with the amount due by the operator under the agreed terms between the two parties, creates a liability to pay the retailer in their account as per the terms agreed between the two parties and sends an approval to theretailer 803 through/over/using electronic data transmission means 903, for example, including: world wide web, the internet, point of sale, mobile phone with minimum of SMS text messaging capability, WAP enabled wire or wireless device which may or may not be a mobile phone, telephone and/or telephone call, interactive voice response over phone or mobile phone, telephone input system using interactive selection response (example: press “1” to select Approval, Press “2” to select Rejection, press “3” to enter transaction ID, etc.), on paper, facsimile transmission, via email, postal mail, encrypted information transportability software running on devices capable of receiving and sending such encrypted information over, but not limited to wireless networks, telephone lines, cable networks, internet, mobile networks. - The
retailer 803 receives the approval from thepayment processor 904, logs it in their books and generates a payment receipt which is sent to thecustomer 801. The receipt can be sent through/over/using electronic data transmission means 903, for example, including: world wide web, the internet, point of sale, mobile phone with minimum of SMS text messaging capability, WAP enabled wire or wireless device which may or may not be a mobile phone, telephone and/or telephone call, interactive voice response over phone or mobile phone, telephone input system using interactive selection response (example: press “1” to select Approval, Press “2” to select Rejection, press “3” to enter transaction ID, etc.), on paper, facsimile transmission, via email, postal mail, encrypted information transportability software running on devices capable of receiving and sending such encrypted information over, but not limited to wireless networks, telephone lines, cable networks, internet, mobile networks. Thecustomer 801 receives the receipt and other relevant information to their purchase, including but not limited to shipping information, promotional offers, promotional coupons, promotional bar-codes, gift certificates, etc. - The above-described devices and subsystems of the exemplary embodiments can include, for example, any suitable servers, workstations, PCs, laptop computers, PDAs, Internet appliances, handheld devices, cellular telephones, wireless devices, other devices, and the like, capable of performing the processes of the exemplary embodiments. The devices and subsystems of the exemplary embodiments can communicate with each other using any suitable protocol and can be implemented using one or more programmed computer systems or devices.
- One or more interface mechanisms can be used with the exemplary embodiments, including, for example, Internet access, telecommunications in any suitable form (e.g., voice, modem, and the like), wireless communications media, and the like. For example, employed communications networks or links can include one or more wireless communications networks, cellular communications networks, G3 communications networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, a combination thereof, and the like.
- It is to be understood that the devices and subsystems of the exemplary embodiments are for exemplary purposes, as many variations of the specific hardware used to implement the exemplary embodiments are possible, as will be appreciated by those skilled in the relevant art(s). For example, the functionality of one or more of the devices and subsystems of the exemplary embodiments can be implemented via one or more programmed computer systems or devices.
- To implement such variations as well as other variations, a single computer system can be programmed to perform the special purpose functions of one or more of the devices and subsystems of the exemplary embodiments. On the other hand, two or more programmed computer systems or devices can be substituted for any one of the devices and subsystems of the exemplary embodiments. Accordingly, principles and advantages of distributed processing, such as redundancy, replication, and the like, also can be implemented, as desired, to increase the robustness and performance of the devices and subsystems of the exemplary embodiments.
- The devices and subsystems of the exemplary embodiments can store information relating to various processes described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like, of the devices and subsystems of the exemplary embodiments. One or more databases of the devices and subsystems of the exemplary embodiments can store the information used to implement the exemplary embodiments of the present inventions. The databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein. The processes described with respect to the exemplary embodiments can include appropriate data structures for storing data collected and/or generated by the processes of the devices and subsystems of the exemplary embodiments in one or more databases thereof.
- All or a portion of the devices and subsystems of the exemplary embodiments can be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present inventions, as will be appreciated by those skilled in the computer and software arts. Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as will be appreciated by those skilled in the software art. Further, the devices and subsystems of the exemplary embodiments can be implemented on the World Wide Web. In addition, the devices and subsystems of the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be appreciated by those skilled in the electrical art(s). Thus, the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.
- Stored on any one or on a combination of computer readable media, the exemplary embodiments of the present inventions can include software for controlling the devices and subsystems of the exemplary embodiments, for driving the devices and subsystems of the exemplary embodiments, for enabling the devices and subsystems of the exemplary embodiments to interact with a human user, and the like. Such software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like. Such computer readable media further can include the computer program product of an embodiment of the present inventions for performing all or a portion (if processing is distributed) of the processing performed in implementing the inventions. Computer code devices of the exemplary embodiments of the present inventions can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, Common Object Request Broker Architecture (CORBA) objects, and the like. Moreover, parts of the processing of the exemplary embodiments of the present inventions can be distributed for better performance, reliability, cost, and the like.
- As stated above, the devices and subsystems of the exemplary embodiments can include computer readable medium or memories for holding instructions programmed according to the teachings of the present inventions and for holding data structures, tables, records, and/or other data described herein. Computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, non-volatile media, volatile media, transmission media, and the like. Non-volatile media can include, for example, optical or magnetic disks, magneto-optical disks, and the like. Volatile media can include dynamic memories, and the like. Transmission media can include coaxial cables, copper wire, fiber optics, and the like. Transmission media also can take the form of acoustic, optical, electromagnetic waves, and the like, such as those generated during radio frequency (RF) communications, infrared (IR) data communications, and the like. Common forms of computer-readable media can include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read.
- While the present inventions have been described in connection with a number of exemplary embodiments, and implementations, the present inventions are not so limited, but rather cover various modifications, and equivalent arrangements, which fall within the purview of the appended claims.
Claims (12)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/222,616 US20140207689A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15269609P | 2009-02-14 | 2009-02-14 | |
PCT/US2010/023863 WO2010093770A2 (en) | 2009-02-14 | 2010-02-11 | Secure payment and billing method using mobile phone number or account |
US201113148043A | 2011-08-04 | 2011-08-04 | |
US14/222,616 US20140207689A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2010/023863 Continuation WO2010093770A2 (en) | 2009-02-14 | 2010-02-11 | Secure payment and billing method using mobile phone number or account |
US13/148,043 Continuation US8682792B2 (en) | 2009-02-14 | 2010-02-11 | Secure payment and billing method using mobile phone number or account |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140207689A1 true US20140207689A1 (en) | 2014-07-24 |
Family
ID=42562267
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/148,043 Active 2030-04-14 US8682792B2 (en) | 2009-02-14 | 2010-02-11 | Secure payment and billing method using mobile phone number or account |
US14/222,613 Abandoned US20140207687A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
US14/222,615 Abandoned US20140207688A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
US14/222,616 Abandoned US20140207689A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
US16/426,064 Active US11232428B2 (en) | 2009-02-14 | 2019-05-30 | System for securing user information by employing phone number and personal identification number |
US17/582,219 Abandoned US20220147968A1 (en) | 2009-02-14 | 2022-01-24 | System for securing user information using encryption |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/148,043 Active 2030-04-14 US8682792B2 (en) | 2009-02-14 | 2010-02-11 | Secure payment and billing method using mobile phone number or account |
US14/222,613 Abandoned US20140207687A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
US14/222,615 Abandoned US20140207688A1 (en) | 2009-02-14 | 2014-03-22 | Secure payment and billing method using mobile phone number or account |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/426,064 Active US11232428B2 (en) | 2009-02-14 | 2019-05-30 | System for securing user information by employing phone number and personal identification number |
US17/582,219 Abandoned US20220147968A1 (en) | 2009-02-14 | 2022-01-24 | System for securing user information using encryption |
Country Status (22)
Country | Link |
---|---|
US (6) | US8682792B2 (en) |
EP (3) | EP2396754B1 (en) |
CN (2) | CN102317963A (en) |
AP (2) | AP2015008527A0 (en) |
AU (2) | AU2010213767B2 (en) |
BR (1) | BRPI1008787A2 (en) |
CA (1) | CA2752555C (en) |
CY (3) | CY1121370T1 (en) |
DK (3) | DK2396754T3 (en) |
EA (2) | EA022027B1 (en) |
ES (3) | ES2879944T3 (en) |
HK (1) | HK1216793A1 (en) |
HR (3) | HRP20190190T1 (en) |
HU (3) | HUE050806T2 (en) |
LT (3) | LT2396754T (en) |
PH (2) | PH12014502067B1 (en) |
PL (3) | PL3447702T3 (en) |
PT (3) | PT3667588T (en) |
SG (1) | SG173205A1 (en) |
SI (3) | SI2396754T1 (en) |
TR (1) | TR201900651T4 (en) |
WO (1) | WO2010093770A2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150287021A1 (en) * | 2011-05-11 | 2015-10-08 | Mark Itwaru | Mobile image payment system |
WO2017155518A1 (en) * | 2016-03-08 | 2017-09-14 | Visa International Service Association | Point of sale device with additional service capabilities |
US11295280B2 (en) | 2011-05-11 | 2022-04-05 | Riavera Corp. | Customized transaction flow for multiple transaction types using encoded image representation of transaction information |
US11645588B2 (en) * | 2001-08-21 | 2023-05-09 | Smartcom Labs Oy | Mobile device implemented logistics functionality based on semantic analysis |
Families Citing this family (119)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8359278B2 (en) | 2006-10-25 | 2013-01-22 | IndentityTruth, Inc. | Identity protection |
US8768778B2 (en) | 2007-06-29 | 2014-07-01 | Boku, Inc. | Effecting an electronic payment |
GB0809383D0 (en) | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Customer to supplier funds transfer |
US9652761B2 (en) | 2009-01-23 | 2017-05-16 | Boku, Inc. | Systems and methods to facilitate electronic payments |
AP2015008527A0 (en) * | 2009-02-14 | 2015-06-30 | Net2Text Ltd | Secure payment and billing method using mobile phone number or account |
US8548426B2 (en) | 2009-02-20 | 2013-10-01 | Boku, Inc. | Systems and methods to approve electronic payments |
US9990623B2 (en) | 2009-03-02 | 2018-06-05 | Boku, Inc. | Systems and methods to provide information |
US8700530B2 (en) | 2009-03-10 | 2014-04-15 | Boku, Inc. | Systems and methods to process user initiated transactions |
US8224727B2 (en) | 2009-05-27 | 2012-07-17 | Boku, Inc. | Systems and methods to process transactions based on social networking |
US9886693B2 (en) | 2009-03-30 | 2018-02-06 | Yuh-Shen Song | Privacy protected anti identity theft and payment network |
US9595028B2 (en) * | 2009-06-08 | 2017-03-14 | Boku, Inc. | Systems and methods to add funds to an account via a mobile communication device |
US9697510B2 (en) | 2009-07-23 | 2017-07-04 | Boku, Inc. | Systems and methods to facilitate retail transactions |
US9519892B2 (en) | 2009-08-04 | 2016-12-13 | Boku, Inc. | Systems and methods to accelerate transactions |
US8660911B2 (en) * | 2009-09-23 | 2014-02-25 | Boku, Inc. | Systems and methods to facilitate online transactions |
US8224709B2 (en) | 2009-10-01 | 2012-07-17 | Boku, Inc. | Systems and methods for pre-defined purchases on a mobile communication device |
US8412626B2 (en) * | 2009-12-10 | 2013-04-02 | Boku, Inc. | Systems and methods to secure transactions via mobile devices |
US8566188B2 (en) | 2010-01-13 | 2013-10-22 | Boku, Inc. | Systems and methods to route messages to facilitate online transactions |
US20110213671A1 (en) * | 2010-02-26 | 2011-09-01 | Boku, Inc. | Systems and Methods to Process Payments |
US20110217994A1 (en) * | 2010-03-03 | 2011-09-08 | Boku, Inc. | Systems and Methods to Automate Transactions via Mobile Devices |
US9652802B1 (en) | 2010-03-24 | 2017-05-16 | Consumerinfo.Com, Inc. | Indirect monitoring and reporting of a user's credit data |
US8219542B2 (en) | 2010-03-25 | 2012-07-10 | Boku, Inc. | Systems and methods to provide access control via mobile phones |
US20110238483A1 (en) * | 2010-03-29 | 2011-09-29 | Boku, Inc. | Systems and Methods to Distribute and Redeem Offers |
US8583504B2 (en) * | 2010-03-29 | 2013-11-12 | Boku, Inc. | Systems and methods to provide offers on mobile devices |
WO2011131821A1 (en) * | 2010-04-21 | 2011-10-27 | Payzapper | Telephone payment system |
US20130232075A1 (en) * | 2010-07-20 | 2013-09-05 | Stephen Robert Monaghan | System and methods for transferring money |
CA2808093A1 (en) | 2010-08-11 | 2012-02-16 | Boku, Inc. | Systems and methods to identify carrier information for transmission of premium messages |
US8699994B2 (en) | 2010-12-16 | 2014-04-15 | Boku, Inc. | Systems and methods to selectively authenticate via mobile communications |
US8412155B2 (en) | 2010-12-20 | 2013-04-02 | Boku, Inc. | Systems and methods to accelerate transactions based on predictions |
US8583496B2 (en) | 2010-12-29 | 2013-11-12 | Boku, Inc. | Systems and methods to process payments via account identifiers and phone numbers |
US8700524B2 (en) | 2011-01-04 | 2014-04-15 | Boku, Inc. | Systems and methods to restrict payment transactions |
US20120203695A1 (en) * | 2011-02-09 | 2012-08-09 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating secure transactions |
CA2827478C (en) | 2011-02-18 | 2020-07-28 | Csidentity Corporation | System and methods for identifying compromised personally identifiable information on the internet |
US8543087B2 (en) | 2011-04-26 | 2013-09-24 | Boku, Inc. | Systems and methods to facilitate repeated purchases |
US9191217B2 (en) | 2011-04-28 | 2015-11-17 | Boku, Inc. | Systems and methods to process donations |
US9830622B1 (en) | 2011-04-28 | 2017-11-28 | Boku, Inc. | Systems and methods to process donations |
US8805326B2 (en) * | 2011-05-10 | 2014-08-12 | Ebay Inc. | Payment transactions on mobile device using mobile carrier |
US8538845B2 (en) | 2011-06-03 | 2013-09-17 | Mozido, Llc | Monetary transaction system |
US20120317003A1 (en) * | 2011-06-09 | 2012-12-13 | Mcgrane Russell | Automated expense account report generator |
US10055740B2 (en) * | 2011-06-27 | 2018-08-21 | Amazon Technologies, Inc. | Payment selection and authorization |
US20130024366A1 (en) * | 2011-07-21 | 2013-01-24 | Ebay, Inc. | Merchant initiated payment using consumer device |
CN102999838B (en) * | 2011-09-19 | 2015-11-25 | 腾讯科技(深圳)有限公司 | The disposal route of order data and disposal system in network payment system |
CN103020820A (en) * | 2011-09-20 | 2013-04-03 | 深圳市财付通科技有限公司 | Transaction payment method and system |
US8819793B2 (en) | 2011-09-20 | 2014-08-26 | Csidentity Corporation | Systems and methods for secure and efficient enrollment into a federation which utilizes a biometric repository |
US11030562B1 (en) | 2011-10-31 | 2021-06-08 | Consumerinfo.Com, Inc. | Pre-data breach monitoring |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US20130144738A1 (en) * | 2011-12-01 | 2013-06-06 | Spenzi, Inc. | Gifting and Sharing Using SMS Messages for Shared Coupon/Gift-Card Auto-Redemption and Multi-Source Payment from Buyer's Mobile Phone |
US9111301B2 (en) | 2011-12-13 | 2015-08-18 | Boku, Inc. | Activating an account based on an SMS message |
US10127540B2 (en) | 2011-12-19 | 2018-11-13 | Paypal, Inc. | System and method for facilitating electronic financial transactions during a phone call |
JP5550630B2 (en) * | 2011-12-28 | 2014-07-16 | 楽天株式会社 | Electronic money server, electronic money processing method, and electronic money processing program |
US20130186193A1 (en) * | 2012-01-25 | 2013-07-25 | WABCO Freight Car Products | System and Method for Testing Railroad Brake Control Valves |
US9129320B2 (en) * | 2012-02-08 | 2015-09-08 | Boku, Inc. | Default phone bill charging |
US8630904B2 (en) | 2012-02-14 | 2014-01-14 | Boku, Inc. | Transaction authentication with a variable-type user-stored account identifier |
US8924711B2 (en) | 2012-04-04 | 2014-12-30 | Zooz Mobile Ltd. | Hack-deterring system for storing sensitive data records |
WO2014000257A1 (en) * | 2012-06-29 | 2014-01-03 | France Telecom | Mobile payment method and system for scheduled payments |
US20150227900A1 (en) * | 2012-08-23 | 2015-08-13 | Gcs International, Ltd. | Business to business invoice generation and payment system and method using mobile phones |
EP2717207A1 (en) * | 2012-10-05 | 2014-04-09 | Alcatel Lucent | Cloud based payment method |
US20140257926A1 (en) * | 2013-03-11 | 2014-09-11 | Tyco Fire & Security Gmbh | Systems and methods for mobile point-of-sale process management |
US8812387B1 (en) | 2013-03-14 | 2014-08-19 | Csidentity Corporation | System and method for identifying related credit inquiries |
US9704146B1 (en) | 2013-03-14 | 2017-07-11 | Square, Inc. | Generating an online storefront |
US9940616B1 (en) | 2013-03-14 | 2018-04-10 | Square, Inc. | Verifying proximity during payment transactions |
US9003078B2 (en) | 2013-03-18 | 2015-04-07 | Boku, Inc. | Merchant managed subscriptions at a merchant server |
JP6347829B2 (en) * | 2013-03-18 | 2018-06-27 | ボク インコーポレイテッド | Merchant management subscription |
US20140337216A1 (en) * | 2013-05-13 | 2014-11-13 | Ramalingam Krishnamurthi Anand | Fraud prevention for transactions |
US9020859B2 (en) * | 2013-05-13 | 2015-04-28 | Ramalingam Krishnamurthi Anand | Fraud prevention for transactions |
US10032144B1 (en) * | 2013-06-21 | 2018-07-24 | Jpmorgan Chase Bank, N.A. | Systems and methods for enhanced dining and other experiences using a mobile device |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US20150095231A1 (en) * | 2013-09-27 | 2015-04-02 | Insperity Services, L.P. | Method, apparatus and system for automatically triggering a transaction |
US11574299B2 (en) | 2013-10-14 | 2023-02-07 | Equifax Inc. | Providing identification information during an interaction with an interactive computing environment |
AU2014334713A1 (en) | 2013-10-14 | 2016-05-19 | Equifax Inc. | Providing identification information to mobile commerce applications |
US9922321B2 (en) * | 2013-10-22 | 2018-03-20 | Square, Inc. | Proxy for multiple payment mechanisms |
US10417635B1 (en) | 2013-10-22 | 2019-09-17 | Square, Inc. | Authorizing a purchase transaction using a mobile device |
US8892462B1 (en) | 2013-10-22 | 2014-11-18 | Square, Inc. | Proxy card payment with digital receipt delivery |
US9836739B1 (en) | 2013-10-22 | 2017-12-05 | Square, Inc. | Changing a financial account after initiating a payment using a proxy card |
US20150134439A1 (en) | 2013-11-08 | 2015-05-14 | Square, Inc. | Interactive digital receipt |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
CN104732384A (en) * | 2013-12-24 | 2015-06-24 | 中兴通讯股份有限公司 | Processing method and system for application software online payment |
US10810682B2 (en) | 2013-12-26 | 2020-10-20 | Square, Inc. | Automatic triggering of receipt delivery |
US10621563B1 (en) | 2013-12-27 | 2020-04-14 | Square, Inc. | Apportioning a payment card transaction among multiple payers |
US9672512B1 (en) | 2014-01-02 | 2017-06-06 | Sprint Communications Company L.P. | Processor routing number for mobile communication service provider billing |
US10198731B1 (en) | 2014-02-18 | 2019-02-05 | Square, Inc. | Performing actions based on the location of mobile device during a card swipe |
US10692059B1 (en) | 2014-03-13 | 2020-06-23 | Square, Inc. | Selecting a financial account associated with a proxy object based on fund availability |
US9864986B1 (en) | 2014-03-25 | 2018-01-09 | Square, Inc. | Associating a monetary value card with a payment object |
US9619792B1 (en) | 2014-03-25 | 2017-04-11 | Square, Inc. | Associating an account with a card based on a photo |
US20150332223A1 (en) | 2014-05-19 | 2015-11-19 | Square, Inc. | Transaction information collection for mobile payment experience |
US20150339662A1 (en) * | 2014-05-23 | 2015-11-26 | LoopPay Inc. | Systems and methods for linking devices to user accounts |
US10614450B1 (en) | 2014-08-08 | 2020-04-07 | Squre, Inc. | Controlled emulation of payment cards |
US10304053B1 (en) | 2014-08-08 | 2019-05-28 | Square, Inc. | Shopping check-out with a payment card |
US10296910B1 (en) | 2014-08-08 | 2019-05-21 | Square, Inc. | Pay-by-name payment check-in with a payment card |
US9558483B2 (en) | 2014-09-08 | 2017-01-31 | Mastercard International Incorporated | Systems and methods for transferring value to payment accounts |
US9477957B2 (en) | 2014-09-08 | 2016-10-25 | Mastercard International Incorporated | Systems and methods for transferring value to payment accounts |
US9922375B1 (en) | 2014-09-22 | 2018-03-20 | Certify, Inc. | Systems and methods of parsing receipts |
US10210579B1 (en) | 2014-09-22 | 2019-02-19 | Certify, Inc. | Automated expense reports systems and methods |
US10339518B2 (en) * | 2014-10-13 | 2019-07-02 | Mastercard International Incorporated | Method and system for direct carrier billing |
US10339527B1 (en) | 2014-10-31 | 2019-07-02 | Experian Information Solutions, Inc. | System and architecture for electronic fraud detection |
CA2965542C (en) * | 2015-01-13 | 2020-03-31 | Mastercard International Incorporated | Systems and methods for transferring value to payment accounts |
WO2016179012A1 (en) * | 2015-05-01 | 2016-11-10 | Pay2Day Solutions, Inc. | Methods and systems for message-based bill payment |
US10026062B1 (en) | 2015-06-04 | 2018-07-17 | Square, Inc. | Apparatuses, methods, and systems for generating interactive digital receipts |
US9877190B1 (en) | 2015-06-04 | 2018-01-23 | Sprint Communications Company L.P. | System and method for authentication and sharing of subscriber data |
US11151468B1 (en) | 2015-07-02 | 2021-10-19 | Experian Information Solutions, Inc. | Behavior analysis using distributed representations of event data |
US9330383B1 (en) * | 2015-09-23 | 2016-05-03 | Square, Inc. | Message dispatcher for payment system |
CN106997529B (en) * | 2016-01-25 | 2021-12-24 | 创新先进技术有限公司 | Credit payment method and device based on mobile terminal eSE |
US10636019B1 (en) | 2016-03-31 | 2020-04-28 | Square, Inc. | Interactive gratuity platform |
CA3059371A1 (en) | 2017-04-13 | 2018-04-13 | Equifax Inc. | Location-based detection of unauthorized use of interactive computing environment functions |
EP3416122A1 (en) | 2017-06-15 | 2018-12-19 | IDEMIA France | Mobile payment roaming |
WO2019040047A1 (en) * | 2017-08-22 | 2019-02-28 | Visa International Service Association | System, method, and computer program product for conducting a payment transaction |
US10699028B1 (en) | 2017-09-28 | 2020-06-30 | Csidentity Corporation | Identity security architecture systems and methods |
US10896472B1 (en) | 2017-11-14 | 2021-01-19 | Csidentity Corporation | Security and identity verification system and architecture |
US11449630B2 (en) | 2017-12-14 | 2022-09-20 | Equifax Inc. | Embedded third-party application programming interface to prevent transmission of sensitive data |
CN116527384A (en) * | 2018-05-14 | 2023-08-01 | 维萨国际服务协会 | Mobile network operator authentication protocol |
US11265324B2 (en) | 2018-09-05 | 2022-03-01 | Consumerinfo.Com, Inc. | User permissions for access to secure data at third-party |
WO2020096546A2 (en) * | 2018-11-08 | 2020-05-14 | Turkiye Garanti Bankasi Anonim Sirketi | A gsm payment system |
US20200259826A1 (en) * | 2019-02-04 | 2020-08-13 | Scba, Llc | System and method for smart sign-in and registration |
WO2021231602A1 (en) * | 2020-05-12 | 2021-11-18 | Prupay, Llc | Touchless payment processing methods and systems |
US20220318810A1 (en) * | 2021-04-01 | 2022-10-06 | Igt | Securing gaming establishment retail purchases |
EP4348552A1 (en) * | 2021-05-27 | 2024-04-10 | Visa International Service Association | User verification with digital tag |
US11888854B2 (en) | 2021-08-23 | 2024-01-30 | The Toronto-Dominion Bank | Systems and methods for authenticating end users of a web service |
US20230230063A1 (en) * | 2022-01-18 | 2023-07-20 | Bank Of America Corporation | System and method for self correcting errors in data resource transfers |
US20230306391A1 (en) * | 2022-03-22 | 2023-09-28 | Block, Inc. | Processing payments using electronic messages |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060029296A1 (en) * | 2004-02-15 | 2006-02-09 | King Martin T | Data capture from rendered documents using handheld device |
US20070063012A1 (en) * | 2005-09-19 | 2007-03-22 | Silverbrook Research Pty Ltd | Method of performing an action in relation to a software object |
US20070260556A1 (en) * | 2005-06-06 | 2007-11-08 | Michael Pousti | System and method for verification of identity for transactions |
US20080097851A1 (en) * | 2006-10-17 | 2008-04-24 | Vincent Bemmel | Method of distributing information via mobile devices and enabling its use at a point of transaction |
US20080167961A1 (en) * | 2007-01-09 | 2008-07-10 | Dave Wentker | Contactless transaction |
US20080228651A1 (en) * | 2003-09-29 | 2008-09-18 | Zan Tapsell | Public Key Crytography Method and System |
US20080255991A1 (en) * | 2004-12-24 | 2008-10-16 | Huawiei Technologies Co., Ltd. | Payment System and a Realizing Method Thereof |
US20080255947A1 (en) * | 2007-04-11 | 2008-10-16 | First Data Corporation | Mobile commerce infrastructure systems and methods |
Family Cites Families (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5265033A (en) * | 1991-09-23 | 1993-11-23 | Atm Communications International, Inc. | ATM/POS based electronic mail system |
US5991749A (en) | 1996-09-11 | 1999-11-23 | Morrill, Jr.; Paul H. | Wireless telephony for collecting tolls, conducting financial transactions, and authorizing other activities |
KR100314210B1 (en) | 1999-02-23 | 2001-11-17 | 김용훈 | Method for paying a charge of goods using mobile phone |
US7461010B2 (en) * | 1999-09-13 | 2008-12-02 | Khai Hee Kwan | Computer network method for conducting payment over a network by debiting and crediting telecommunication accounts |
IL134741A (en) * | 2000-02-27 | 2003-11-23 | Adamtech Ltd | Mobile transaction system and method |
CA2337672A1 (en) | 2000-04-26 | 2001-10-26 | International Business Machines Corporation | Payment for network-based commercial transactions using a mobile phone |
US20020073027A1 (en) * | 2000-12-11 | 2002-06-13 | Hui Helen Shan-Shan | Mobile payment system |
FR2820853B1 (en) * | 2001-02-12 | 2003-04-11 | France Telecom | TELEPAYING METHOD AND SYSTEM |
US20020143634A1 (en) * | 2001-03-30 | 2002-10-03 | Kumar K. Anand | Wireless payment system |
US20030055733A1 (en) * | 2001-09-20 | 2003-03-20 | Marshall Carl S. | Mobile digital receipts |
MY135209A (en) | 2001-12-04 | 2008-02-29 | Conceptm Company Ltd | System and method for facilitating electronic financial transactions using a mobile telecommunication device |
US20040019564A1 (en) * | 2002-07-26 | 2004-01-29 | Scott Goldthwaite | System and method for payment transaction authentication |
GB0308629D0 (en) * | 2003-04-14 | 2003-05-21 | Tagboard Ltd | Payment apparatus and method |
WO2005086593A2 (en) * | 2004-02-05 | 2005-09-22 | A Little World Private Limited | Inter-operable, multi-operator, multi-bank, multi-merchant mobile payment method and a system therefor |
US20050222917A1 (en) | 2004-04-01 | 2005-10-06 | Jeffery Moore | Messaging business method, system and method of conducting business |
GB0420409D0 (en) * | 2004-09-14 | 2004-10-20 | Waterleaf Ltd | Online commercial transaction system and method of operation thereof |
US20060131390A1 (en) * | 2004-12-16 | 2006-06-22 | Kim Mike I | Method and system for providing transaction notification and mobile reply authorization |
US20060149644A1 (en) | 2005-01-03 | 2006-07-06 | Pilgrim Telephone, Inc. | Premium SMS billing method |
JP2006338414A (en) * | 2005-06-02 | 2006-12-14 | Trust System:Kk | Card usage authorization device, card usage information notification device, and its program |
US7731086B2 (en) | 2005-06-10 | 2010-06-08 | American Express Travel Related Services Company, Inc. | System and method for mass transit merchant payment |
US20070063017A1 (en) | 2005-09-21 | 2007-03-22 | Yaofei Chen | System and method for securely making payments and deposits |
US8352376B2 (en) | 2005-10-11 | 2013-01-08 | Amazon Technologies, Inc. | System and method for authorization of transactions |
US7819307B2 (en) * | 2005-10-27 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Method and system for managing monetary value on a mobile device |
US20070156579A1 (en) * | 2006-01-05 | 2007-07-05 | Ubequity, Llc | System and method of reducing or eliminating change in cash transaction by crediting at least part of change to buyer's account over electronic medium |
US8489067B2 (en) * | 2006-07-06 | 2013-07-16 | Qualcomm Incorporated | Methods and systems for distribution of a mobile wallet for a mobile device |
KR20080005800A (en) * | 2006-07-10 | 2008-01-15 | 주식회사 빛 일일사 | Method for payment of taxi fare using mobile phone |
KR20080096721A (en) * | 2007-04-10 | 2008-11-03 | 배재광 | Method and system for processing payment of credit card using by mobile terminal |
US8166118B1 (en) * | 2007-10-26 | 2012-04-24 | Sendside Networks Inc. | Secure communication architecture, protocols, and methods |
US9367839B2 (en) * | 2007-11-30 | 2016-06-14 | U.S. Bank National Association | Disparate network systems and methods |
GB2457445A (en) * | 2008-02-12 | 2009-08-19 | Vidicom Ltd | Verifying payment transactions |
US20090240620A1 (en) * | 2008-03-24 | 2009-09-24 | Propay Usa, Inc. | Secure payment system |
ES2347113B1 (en) * | 2008-04-03 | 2011-09-07 | Vodafone España, S.A. | METHOD AND SYSTEM FOR THE TRANSFER OF RESOURCES BETWEEN USER TERMINALS. |
WO2009136406A2 (en) * | 2008-05-05 | 2009-11-12 | Shree Mishra | Method and apparatus of multi-currency pin based sms based payments or e-commerce payments through mobile currency |
US8412625B2 (en) * | 2008-08-25 | 2013-04-02 | Bruno Pilo' & Associates, Llc | System and methods for a multi-channel payment platform |
AP2015008527A0 (en) * | 2009-02-14 | 2015-06-30 | Net2Text Ltd | Secure payment and billing method using mobile phone number or account |
CA2678831A1 (en) * | 2009-09-15 | 2011-03-15 | Daniel Mccann | Anonymized payment in e-commerce transactions |
-
2010
- 2010-02-11 AP AP2015008527A patent/AP2015008527A0/en unknown
- 2010-02-11 BR BRPI1008787A patent/BRPI1008787A2/en not_active IP Right Cessation
- 2010-02-11 HU HUE18197485A patent/HUE050806T2/en unknown
- 2010-02-11 AU AU2010213767A patent/AU2010213767B2/en not_active Ceased
- 2010-02-11 EP EP10741708.1A patent/EP2396754B1/en active Active
- 2010-02-11 LT LTEP10741708.1T patent/LT2396754T/en unknown
- 2010-02-11 PT PT201551249T patent/PT3667588T/en unknown
- 2010-02-11 EP EP18197485.8A patent/EP3447702B1/en active Active
- 2010-02-11 WO PCT/US2010/023863 patent/WO2010093770A2/en active Application Filing
- 2010-02-11 ES ES20155124T patent/ES2879944T3/en active Active
- 2010-02-11 AP AP2011005836A patent/AP3395A/en active
- 2010-02-11 HU HUE20155124A patent/HUE054839T2/en unknown
- 2010-02-11 SI SI201031851T patent/SI2396754T1/en unknown
- 2010-02-11 PL PL18197485T patent/PL3447702T3/en unknown
- 2010-02-11 LT LTEP18197485.8T patent/LT3447702T/en unknown
- 2010-02-11 CN CN2010800079189A patent/CN102317963A/en active Pending
- 2010-02-11 DK DK10741708.1T patent/DK2396754T3/en active
- 2010-02-11 SI SI201032077T patent/SI3667588T1/en unknown
- 2010-02-11 US US13/148,043 patent/US8682792B2/en active Active
- 2010-02-11 TR TR2019/00651T patent/TR201900651T4/en unknown
- 2010-02-11 CN CN201510541199.3A patent/CN105205655A/en active Pending
- 2010-02-11 EA EA201171017A patent/EA022027B1/en unknown
- 2010-02-11 ES ES10741708T patent/ES2709749T3/en active Active
- 2010-02-11 HU HUE10741708A patent/HUE042583T2/en unknown
- 2010-02-11 ES ES18197485T patent/ES2811030T3/en active Active
- 2010-02-11 LT LTEP20155124.9T patent/LT3667588T/en unknown
- 2010-02-11 SG SG2011055928A patent/SG173205A1/en unknown
- 2010-02-11 PL PL10741708T patent/PL2396754T3/en unknown
- 2010-02-11 CA CA2752555A patent/CA2752555C/en active Active
- 2010-02-11 SI SI201032029T patent/SI3447702T1/en unknown
- 2010-02-11 DK DK20155124.9T patent/DK3667588T3/en active
- 2010-02-11 EA EA201492077A patent/EA036171B1/en unknown
- 2010-02-11 EP EP20155124.9A patent/EP3667588B1/en active Active
- 2010-02-11 PL PL20155124T patent/PL3667588T3/en unknown
- 2010-02-11 PT PT10741708T patent/PT2396754T/en unknown
- 2010-02-11 PT PT181974858T patent/PT3447702T/en unknown
- 2010-02-11 DK DK18197485.8T patent/DK3447702T3/en active
-
2014
- 2014-03-22 US US14/222,613 patent/US20140207687A1/en not_active Abandoned
- 2014-03-22 US US14/222,615 patent/US20140207688A1/en not_active Abandoned
- 2014-03-22 US US14/222,616 patent/US20140207689A1/en not_active Abandoned
- 2014-06-26 AU AU2014203475A patent/AU2014203475B2/en not_active Ceased
- 2014-09-18 PH PH12014502067A patent/PH12014502067B1/en unknown
-
2016
- 2016-04-28 HK HK16104858.5A patent/HK1216793A1/en unknown
-
2019
- 2019-01-29 HR HRP20190190TT patent/HRP20190190T1/en unknown
- 2019-02-05 CY CY20191100157T patent/CY1121370T1/en unknown
- 2019-03-14 PH PH12019500547A patent/PH12019500547A1/en unknown
- 2019-05-30 US US16/426,064 patent/US11232428B2/en active Active
-
2020
- 2020-08-18 HR HRP20201291TT patent/HRP20201291T1/en unknown
- 2020-08-24 CY CY20201100790T patent/CY1123277T1/en unknown
-
2021
- 2021-06-28 HR HRP20211014TT patent/HRP20211014T1/en unknown
- 2021-06-29 CY CY20211100577T patent/CY1124267T1/en unknown
-
2022
- 2022-01-24 US US17/582,219 patent/US20220147968A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080228651A1 (en) * | 2003-09-29 | 2008-09-18 | Zan Tapsell | Public Key Crytography Method and System |
US20060029296A1 (en) * | 2004-02-15 | 2006-02-09 | King Martin T | Data capture from rendered documents using handheld device |
US20080255991A1 (en) * | 2004-12-24 | 2008-10-16 | Huawiei Technologies Co., Ltd. | Payment System and a Realizing Method Thereof |
US20070260556A1 (en) * | 2005-06-06 | 2007-11-08 | Michael Pousti | System and method for verification of identity for transactions |
US20070063012A1 (en) * | 2005-09-19 | 2007-03-22 | Silverbrook Research Pty Ltd | Method of performing an action in relation to a software object |
US20080097851A1 (en) * | 2006-10-17 | 2008-04-24 | Vincent Bemmel | Method of distributing information via mobile devices and enabling its use at a point of transaction |
US20080167961A1 (en) * | 2007-01-09 | 2008-07-10 | Dave Wentker | Contactless transaction |
US20080255947A1 (en) * | 2007-04-11 | 2008-10-16 | First Data Corporation | Mobile commerce infrastructure systems and methods |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11645588B2 (en) * | 2001-08-21 | 2023-05-09 | Smartcom Labs Oy | Mobile device implemented logistics functionality based on semantic analysis |
US20150287021A1 (en) * | 2011-05-11 | 2015-10-08 | Mark Itwaru | Mobile image payment system |
US11295280B2 (en) | 2011-05-11 | 2022-04-05 | Riavera Corp. | Customized transaction flow for multiple transaction types using encoded image representation of transaction information |
WO2017155518A1 (en) * | 2016-03-08 | 2017-09-14 | Visa International Service Association | Point of sale device with additional service capabilities |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11232428B2 (en) | System for securing user information by employing phone number and personal identification number | |
US9978059B2 (en) | Systems, apparatus and methods for mobile companion prepaid card | |
US7499889B2 (en) | Transaction system | |
US8924299B2 (en) | Method and system for facilitating payment transactions using access devices | |
US20010034720A1 (en) | System for facilitating a transaction | |
EP1421732B1 (en) | Transaction system | |
EP1546956A2 (en) | Method and system for facilitating payment transactions using access devices | |
WO2009146415A1 (en) | System and method for processing transactions without providing account information to a payee | |
CN101273373A (en) | Method and system for making a payment through a mobile communication device | |
US20140222595A1 (en) | Payment Systems and Methods | |
EP1744518A2 (en) | Transaction system | |
Peters | Emerging ecommerce credit and debit card protocols | |
OA17553A (en) | Systems, apparatus and methods for mobile companion prepaid card. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NET2TEXT LTD, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RAMMAL, KARIM ANWAR;REEL/FRAME:033774/0914 Effective date: 20110920 |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCV | Information on status: appeal procedure |
Free format text: REQUEST RECONSIDERATION AFTER BOARD OF APPEALS DECISION |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED AFTER REQUEST FOR RECONSIDERATION |
|
AS | Assignment |
Owner name: BOLORO GLOBAL LIMITED, NEW YORK Free format text: CHANGE OF NAME;ASSIGNOR:NET2TEXT LIMITED;REEL/FRAME:050163/0813 Effective date: 20130822 |
|
STCV | Information on status: appeal procedure |
Free format text: APPLICATION INVOLVED IN COURT PROCEEDINGS |
|
STCV | Information on status: appeal procedure |
Free format text: COURT PROCEEDINGS TERMINATED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |