US20120143737A1 - Billing system and method for micro-transactions - Google Patents
Billing system and method for micro-transactions Download PDFInfo
- Publication number
- US20120143737A1 US20120143737A1 US13/312,944 US201113312944A US2012143737A1 US 20120143737 A1 US20120143737 A1 US 20120143737A1 US 201113312944 A US201113312944 A US 201113312944A US 2012143737 A1 US2012143737 A1 US 2012143737A1
- Authority
- US
- United States
- Prior art keywords
- customer
- billing
- mobile
- identification code
- community platform
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/73—Validating charges
-
- 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- 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/085—Payment architectures involving remote charge determination or related payment 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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking 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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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/14—Payment architectures specially adapted for billing 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/22—Payment schemes or models
- G06Q20/29—Payment schemes or models characterised by micropayments
-
- 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/04—Billing or invoicing
-
- 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
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- 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/1442—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level
- H04L12/1446—Charging, metering or billing arrangements for data wireline or wireless communications at network operator level inter-operator billing
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/48—Secure or trusted billing, e.g. trusted elements or encryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/83—Notification aspects
- H04M15/84—Types of notifications
- H04M15/844—Message, e.g. SMS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0156—Secure and trusted billing, e.g. trusted elements, encryption, digital signature, codes or double check mechanisms to secure billing calculation and information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/70—Administration aspects, modify settings or limits or counter-check correct charges
- H04M2215/7072—Validate charges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/81—Notifying aspects, e.g. notifications or displays to the user
- H04M2215/8129—Type of notification
- H04M2215/8137—Message, e.g. alphanumeric text, SMS, MMS, EMS or www-based messaging service
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S705/00—Data processing: financial, business practice, management, or cost/price determination
- Y10S705/901—Digital rights management
- Y10S705/902—Licensing digital content
Definitions
- the present invention concerns the automated processing of transactions, including small transactions known as micro-transactions.
- the invention concerns the use of an intermediate billing system that acts on behalf of third party providers of content or services by interacting with various external billing mechanisms to effectuate transactions between such third party providers and their customers.
- many users of the internet that do not have access to a credit card or do not want to use their credit card for an internet based transaction out of security concerns.
- Many such users most likely have a mobile phone or mobile device, and it would be more easy and efficient to have a mechanism for billing the user for transactions through the user's pre-existing account with the mobile carrier associated with the user's mobile phone number.
- the use of a credit card is economically viable only if the transaction amount, or a volume of such transactions, exceeds a particular amount that depends on the underlying efficiency of the billing and collecting system implemented by the merchant and by the credit card provider.
- Retailers or vendors such as internet commercial websites, may desire to provide their respective content or services to mobile phone users via the internet or directly through the user's mobile phone, and bill the user for such content or services as micro-transactions.
- a retailer or vendor will find it very difficult and inefficient to bill and collect for such a micro-transaction because the retailer/vendor would need to negotiate and enter into a contractual relationship with the mobile phone carrier in order to bill the mobile phone user subscribed to that carrier.
- the process is further complicated by the fact that the universe of customers with mobile phones use different mobile phone carriers. Accordingly, the retailer/vendor would need to enter into contractual relationships with many different mobile phone carriers in order to be able to provide a mobile phone based micro-transaction billing option to the desired global market of mobile phone users.
- a retailer or vendor can try to use billing mechanisms other than mobile carriers, such as prepaid card services, web-based payment services, bank account and credit card billing services, and other such external billing mechanisms to support customer transactions.
- billing mechanisms other than mobile carriers such as prepaid card services, web-based payment services, bank account and credit card billing services, and other such external billing mechanisms to support customer transactions.
- the same problem still exists for the vendor/retailer because they would still need to have pre-existing relationships with all of the various external billing mechanisms that their various customers wish to use for payment of transactions.
- the present invention solves the foregoing problems by providing a method and system that uses a single intermediate billing system to effectuate transactions between retailers/vendors and their customers through a wide variety of external billing mechanisms, without the need for the retailer/vendor to individually establish a pre-existing relationship with each of the wide variety of external billing mechanisms.
- the invention is directed to a method and system for billing a customer through an intermediary billing system for a transaction, by receiving, at the intermediary billing system, a transaction request associated with a transaction amount and a customer identification code, validating, in the intermediary billing system, the transaction request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and sending, in the case that the transaction request is valid, a billing event trigger associated with the customer identification code to an external billing mechanism, the billing event trigger representing the transaction amount.
- the invention is directed to a method and system for billing a customer through an intermediary billing system for a transaction between the customer and a third party provider, by receiving, at the intermediary billing system, a registration request to register the customer, registering the customer in the intermediary billing system by providing a mobile phone number of the customer to the intermediary billing system, assigning a customer identification code to the customer, the customer identification code being shared with the third party provider, and associating the mobile phone number of the customer with the customer identification code assigned to the customer, receiving, at the intermediary billing system, a billing request from the third party provider, the billing request including a product identification code corresponding to a product associated with the transaction between the customer and the third party provider, a customer identification code assigned to the customer and a provider identification code corresponding to the third party provider, validating, in the intermediary billing system, the billing request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and by determining whether the provider identification code corresponds to a valid third party provider,
- a method and system for billing a customer through an intermediary billing system for a transaction between the customer and a third party provider, by receiving, at the intermediary billing system, a transaction activation request from the third party provider to activate a customer for the transaction associated with a product offered by the third party provider, the customer being automatically directed from the third party provider to the intermediary billing system, prompting, by the intermediary billing system, the customer to confirm an instruction to proceed with the transaction, sending, in the case that the customer confirms the instruction to proceed with the transaction, at least one message from the intermediary billing system to a mobile phone number associated with a customer identification code for the customer, the at least one message representing a billing value that corresponds to the product, generating, in the intermediary billing system, an encrypted verification code in association with the customer identification code for the customer, installing the encrypted verification code on a web browser application of the customer (for browsing web pages on the internet), and automatically directing the customer from the intermediary billing system to the third party provider, receiving, at the intermediary billing system
- the present invention provides that an efficient and timely billing system that utilizes mobile text messages to bill customers for transactions between the customers and third-party providers of content or services, without the need for a third-party provider to have any relationship or interaction with the mobile phone carrier of the customer.
- FIG. 1 is a block diagram of a computer system with which the present invention may be practiced, according to one embodiment of the invention
- FIG. 2 is a block diagram of a mobile community environment in which the invention may be practiced, according to one embodiment of the invention
- FIG. 3 is a block diagram providing a detailed view of the mobile community platform shown in FIG. 2 ;
- FIG. 4 is a flowchart for explaining the registration and activation of a customer for transaction billing, according to one embodiment of the invention.
- FIG. 5 is a flowchart for explaining the processing of a billing request for a transaction, according to one embodiment of the invention.
- FIG. 6 is a flowchart for explaining the processing of a transaction, according to another embodiment of the invention.
- FIG. 7 is a flowchart for explaining the processing of a billing request for a transaction, according to another embodiment of the invention.
- the present invention is a method and system that utilizes an intermediary billing system in conjunction with one or more external billing mechanisms for supporting transactions between customers and third-party providers of content or services, without the need for a third-party provider to have a relationship or interaction with any of the external billing mechanisms.
- FIG. 1 is a block diagram of an exemplary computer system with which one embodiment of the present invention may be practiced.
- computer system 100 includes a bus 102 or other communication mechanism for communicating information, and a processor 104 coupled with bus 102 for processing information.
- Computer system 100 also includes a main memory 106 , such as a random access memory (RAM) or other dynamic storage device, coupled to bus 102 for storing information and instructions to be executed by processor 104 .
- Main memory 106 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 104 .
- Computer system 100 further includes a read only memory (ROM) 108 or other static storage device coupled to bus 102 for storing static information and instructions for processor 104 .
- ROM read only memory
- a storage device 110 such as a magnetic disk or optical disk, is provided and coupled to bus 102 for storing information and instructions.
- Computer system 100 may be coupled via bus 102 to a display 112 , such as a cathode ray tube (CRT), for displaying information to a computer user.
- a display 112 such as a cathode ray tube (CRT)
- An input device 114 is coupled to bus 102 for communicating information and command selections to processor 104 .
- cursor control 116 is Another type of user input device
- cursor control 116 such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to processor 104 and for controlling cursor movement on display 112 .
- This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
- Computer system 100 operates in response to processor 104 executing one or more sequences of one or more instructions contained in main memory 106 . Such instructions may be read into main memory 106 from another computer-readable medium, such as storage device 110 . Execution of the sequences of instructions contained in main memory 106 causes processor 104 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
- Non-volatile media includes, for example, optical or magnetic disks, such as storage device 110 .
- Volatile media includes dynamic memory, such as main memory 106 .
- Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 102 . Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications.
- Computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
- Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 104 for execution.
- the instructions may initially be carried on a magnetic disk of a remote computer.
- the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
- a modem local to computer system 100 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal.
- An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data on bus 102 .
- Bus 102 carries the data to main memory 106 , from which processor 104 retrieves and executes the instructions.
- the instructions received by main memory 106 may optionally be stored on storage device 110 either before or after execution by processor 104 .
- Computer system 100 also includes a communication interface 118 coupled to bus 102 .
- Communication interface 118 provides a two-way data communication coupling to a network link 120 that is connected to a local network 122 .
- communication interface 118 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line.
- ISDN integrated services digital network
- communication interface 118 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
- LAN local area network
- Wireless links may also be implemented.
- communication interface 118 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
- Network link 120 typically provides data communication through one or more networks to other data devices.
- network link 120 may provide a connection through local network 122 to a host computer 124 or to data equipment operated by an Internet Service Provider (ISP) 126 .
- ISP 126 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 128 .
- Internet 128 uses electrical, electromagnetic or optical signals that carry digital data streams.
- the signals through the various networks and the signals on network link 120 and through communication interface 118 , which carry the digital data to and from computer system 100 are exemplary forms of carrier waves transporting the information.
- Computer system 100 can send messages and receive data, including program code, through the network(s), network link 120 and communication interface 118 .
- a server 130 might transmit a requested code for an application program through Internet 128 , ISP 126 , local network 122 and communication interface 118 .
- the received code may be executed by processor 104 as it is received, and/or stored in storage device 110 , or other non-volatile storage for later execution.
- computer system 100 may obtain application code in the form of a carrier wave.
- other forms of computing systems may be used to implement the present invention.
- FIG. 2 is a block diagram of a mobile community environment in which the invention may be practiced according to an exemplary embodiment.
- FIG. 2 depicts a block diagram of a computer-based mobile community platform 202 .
- Mobile community platform 202 can be implemented in the computing system show in FIG. 1 , or some other form of computing system.
- users 212 , 214 , 216 can connect to the mobile community platform 202 via a network or similar communications channel 210 .
- network 210 is the internet by which users 212 , 214 and 216 can access internet-enabled applications and websites, such as third party providers 231 , 232 and 233 .
- third party providers 231 , 232 and 233 can be websites that provide only information, or may be commercial websites that offer a product, such as access to premium content or services, for purchase by the user, whereby the user is provided with access to the product after opting-in (purchasing) the product from that particular website.
- third party providers 231 , 232 and 233 can be internet-enabled applications such as a software application that is enabled to access the internet and that can provide content or services to the user of the software application for a price.
- a software game being executed on a user's computer, or an internet-enabled game device may allow the user to access the internet in order to purchase additional features of the game to be downloaded or “premium” information about how to play the game for a price.
- a third party provider can be any type of application, game, product or service that is internet-enabled and that offers additional product (software, content, information, or services) to the user for a price. Any such third party provider can maintain a website to which the user is directed when the user elects to purchase a product from the third party provider.
- Third party providers 231 , 232 and 233 are maintained and operated by known means and can be implemented in a computing system such as that shown in FIG. 1 , or other known types of networked computing environments, such as a server, or combination of computers and servers.
- a user e.g., 212
- This profile page can include various files and content that the user wants to share with other members of the mobile community platform 202 .
- the user's profile page may include a hierarchy of pages, some of which are for public view and some of which have restrictions on viewing.
- the mobile community platform 202 can be logically organized into neighborhoods such as “friends”, “family”, “workplace”, “dog owners”, etc. Users 212 , 214 , 216 can belong to these different neighborhoods and share different pages with the members of the different neighborhoods.
- mobile community platform 202 connects with various mobile carrier systems 204 , 206 , 208 , each of which has an associated community of mobile phone subscribers, 224 , 226 and 228 .
- each of mobile carrier systems 204 , 206 , 208 is a carrier network and system for supporting mobile devices including mobile phones and other mobile devices such as personal device assistants (pda).
- Each mobile carrier system is generally a wireless network provider, which can be cellular, PCS, or other wireless spectrum.
- Users 212 , 214 , 216 of the mobile community platform 202 are also subscribers of one or more of the various mobile carriers, which support the mobile phones, or other mobile devices, of users 212 , 214 , 216 .
- users 212 , 214 , 216 of mobile community platform 202 can access other users' profile pages through the computer-based platform of mobile community platform 202 , and they can also access the subscribers 224 , 226 and 228 of the various mobile carrier systems 204 , 206 , and 208 who also belong to mobile community platform 202 .
- the mobile community platform 202 has pre-existing contractual relationships with the various mobile carrier systems 204 , 206 , 208 for accessing subscribers through each carrier systems and for billing subscribers through their respective carrier system for content and services purchased by the subscriber through mobile community platform 202 .
- the mobile carrier systems 204 , 206 , 208 provide text messaging and also premium text message functionality. Such messages are sent via the mobile carrier's infrastructure to its mobile subscribers and, internal to the mobile carrier's infrastructure, the sending of such a message generates a billing event according to a particular tariff rate, which then is added to the subscriber's bill from that mobile carrier.
- mobile community platform 202 When mobile community platform 202 sends a message via a mobile carrier system (e.g., 204 ), it is billing the subscriber-recipient of the message using the existing billing system of that mobile carrier.
- the billing event is often a micro-transaction of a small monetary amount (e.g., less than one dollar).
- a user (e.g., 212 ) of the mobile community platform may purchase a service or content within mobile community platform 202 and be billed for those transactions through that user's mobile carrier service account.
- the present invention provides for such micro-transaction billing support through mobile community platform 202 for a transaction between a user (e.g., 212 ) and a third party provider (e.g., 231 ) which is external to mobile community platform 202 .
- a third party provider need only communicate with mobile community platform 202 to conduct transactions with users, and does not require any affiliation or agreement with the various mobile carrier systems of the users.
- FIG. 3 depicts a more detailed view of mobile community platform 202 .
- mobile community platform 202 can be used to conduct micro-transactions in which a mobile carrier's billing system is used by mobile community platform 202 to automatically bill the user for each micro-transactions with a third party provider, without the need for a negotiation or contract between the third party provider and the mobile carrier.
- a third party provider that operates a website which offers sports score updates to users of mobile community platform 202 for a predetermined price, while taking advantage of the billing arrangements already in place between mobile community platform 202 and the mobile carriers 204 , 206 , 208 .
- a third party provider may provide other types of content, products and services to users of mobile community platform 202 .
- mobile community platform 202 includes multimedia messaging system 302 , user area 304 , which supports content, community and commerce functions for the users, including website interface for users to mobile community platform 202 , and intermediary billing interface 306 .
- multimedia messaging system 302 includes multimedia messaging system 302 , user area 304 , which supports content, community and commerce functions for the users, including website interface for users to mobile community platform 202 , and intermediary billing interface 306 .
- user area 304 which supports content, community and commerce functions for the users, including website interface for users to mobile community platform 202 , and intermediary billing interface 306 .
- users 212 , 214 , 216 can visit user area 304 of mobile community platform 202 in order to participate in an online-based community of users that includes various communication, content and commerce opportunities.
- the user accesses a website of user area 304 through the user's web browser that may be hosted on a laptop or desktop computer, or, in the alternative, even on the user's mobile device such as a PDA or mobile phone.
- user area 304 includes a web server that communicates with users 212 , 214 , 216 and includes a data store (database) of user information and other content.
- mobile community platform 202 is able to present a profile page (“home page”) to a user (e.g., 212 ) that reflects a set of content, information and products associated with, and desired by, that particular user.
- This set of content, information and products is not maintained on the local computer being used by the user 212 but, rather, is maintained and managed by the computing environment of mobile community platform 202 .
- FIG. 3 one of ordinary skill will recognize that there are numerous functionally equivalent techniques to create, manage, store and serve user information, user profiles, user content, software tools and other resources within the user area 304 . Included in these techniques are methods to ensure security, data integrity, data availability and quality of service metrics.
- Multimedia messaging system (MMS) 302 includes applications for connecting with and communicating with the multiple different mobile carriers 204 , 206 , 208 that have been partnered with mobile community platform 202 .
- MMS 302 is configured to generate message requests in the appropriate format for each of the mobile carriers 204 , 206 , 208 including tariff information that determines the amount for which the recipient of the message will be charged.
- the mobile carriers 204 , 206 , 208 Upon receipt of the message request, the mobile carriers 204 , 206 , 208 will use the information in the request to generate an appropriate message to the intended recipient/subscriber of the mobile carrier and then bill the recipient/subscriber's mobile service account for that specified amount.
- mobile community platform 202 uses the mobile carriers to bill user/subscribers of the mobile carriers for transactions conducted through mobile community platform 202 .
- the MMS 302 communicates with the user area 304 , such that users of mobile community platform 202 can advantageously use the connectivity between MMS 302 and the mobile carriers 204 , 206 and 208 in order to send messages to subscribers of any of the mobile carriers 204 , 206 , 208 .
- the messages may be SMS messages, MMS messages, or other known message formats or subsequently developed message formats. Some of these messages may have zero tariff and, therefore do not generate a bill to the recipient/subscriber (other than the underlying charges implemented by the mobile carrier) and others may have non-zero tariffs resulting in a billing event for the recipient/subscriber.
- Intermediary billing interface 306 provides an interface between third party providers 231 , 232 and 233 and mobile community platform 202 for enabling transactions between such third party providers and users 212 , 214 and 216 , through the use of sending messages to the users as a billing mechanism.
- intermediary billing interface 306 is accessed by the third party providers via network connection 210 (internet).
- intermediary billing interface 306 is in communication with user area 304 , both of which are in communication with MMS 302 . Accordingly, intermediary billing interface 306 can access user information from user area 304 , such as whether the user is registered and verified for billing through their mobile phone number, as discussed more fully below.
- Intermediary billing interface 306 can interface with user area 304 to communicate with a user, such as via webpages supported by user area 304 , for purposes of registering the user with mobile community platform 202 and verifying the user for billing of transactions related to a product offered through a third party provider, as also discussed in more detail below.
- intermediary billing interface 306 also includes local database 310 which is used by intermediary billing interface 306 to store customer identification codes, third party provider identification codes, and other information for implementing the present invention.
- third party providers 231 , 232 and 233 can interact with all users of the mobile community platform 202 whereby billable transactions with users 212 , 214 , 216 are automatically billed to the users via the billing systems of their mobile carriers 204 , 206 , 208 .
- this capability is available to the third party providers without requiring them to negotiate or contract with any of the mobile carriers for billing arrangements, or to worry about how to communicate with a particular mobile carrier's systems and resources.
- the third party providers seamlessly take advantage of the unified set of connectivity and billing arrangements that exist between mobile community platform 202 and the mobile carriers 204 , 206 , 208 . As a result, the third party providers may conduct transactions with users/subscribers of any of a variety of different mobile carriers without easily and efficiently through mobile community platform 202 .
- FIG. 4 is a flowchart that provides an exemplary depiction of the registration and activation of a customer for transaction billing in one embodiment of the invention.
- the process starts in FIG. 4 and proceeds to step 40 I in which it is determined whether the customer (e.g. one of users 212 , 214 and 216 ) is initiating a transaction for a product at a third party provider, such as one of third party providers 231 , 232 and 233 , or is initiating a transaction for a product offered by the third party provider at mobile community platform 202 , which acts as the intermediary billing system in either case. If the customer is initiating the transaction at mobile community platform 202 , then the process proceeds to step 405 which is discussed further below.
- a third party provider such as one of third party providers 231 , 232 and 233
- step 402 the third party provider determines if the customer is already registered as a customer with the third party provider. If the customer is already registered with the third party provider, then the process proceeds to step 404 . If not, then the process proceeds to step 403 in which the customer registers with the third party provider, such as by providing the customer's name and contact information, and in which the third party provider generates a unique customer identification code corresponding to that customer.
- the third party provider can use any form of registration process and may not necessarily require the customer to provide any specific information, in which case the third party provider simply generates and assigns a unique customer identification code to that customer.
- the third party provider maintains a database of its registered customers, and their corresponding customer identification numbers and information.
- the customer identification number will be used in the invention for common tracking of the same customer between the third party provider and the intermediary billing system of mobile community platform 202 .
- step 404 the third party provider directs the customer to mobile community platform 202 along with a registration request to register and activate the customer, the request including the customer identification code for the customer.
- step 405 the registration and activation steps for the customer begin by the mobile community platform 202 (intermediary billing system) determining if the customer is already registered as a member of mobile community platform 202 . If the customer is already registered with mobile community platform 202 , then the process proceeds to step 407 . If not, then the process proceeds to step 406 in which the customer registers with mobile community platform 202 , such as by providing the customer's name and contact information, including the customer's mobile phone number, which is used by mobile community platform 202 in the invention to bill the customer for the transaction.
- mobile community platform 202 If it was determined in step 401 that the customer is originating the transaction at mobile community platform 202 , then mobile community platform 202 also generates a unique customer identification code for the customer. Also in the registration process, mobile community platform 202 stores the customer identification code for the customer in a database of registered customers, along with related information, maintained in mobile community platform 202 , and activates the customer's mobile phone number for transaction billing as described below.
- the mobile community platform 202 generates a verification code for the registration/activation of the customer, and directs the customer back to the third party provider along with the verification code, the customer identification code, and possibly other information, in step 407 .
- the third party provider sends a verification code validation request to mobile community platform 202 , the request including the verification code for the customer, to make sure that the third party provider and mobile community platform 202 are in agreement on the customer identification code to be used for the customer, and that the customer is registered and activated for the transaction in both the third party provider and the mobile community platform 202 .
- the term “activated” means that the mobile community platform 202 has enabled the customer associated with the assigned customer identification code to be billed for transactions, such as through the customer's mobile phone number, or through some other external billing mechanism used by mobile community platform 202 .
- mobile community platform 202 determines whether the verification code received in the verification code validation request from the third party provider is valid by comparing it to the verification code stored in the database of mobile community platform 202 for that customer identification code. If the two codes match, then the verification code is valid, and mobile community platform 202 sends a confirmation reply to the third party provider in step 411 to confirm that the verification code is valid. If the two codes do not match, then the verification code is not valid, and mobile community platform 202 sends an error reply to the third party provider in step 410 to advise that the verification code is not valid. The registration and activation process for the customer between the third party provider and mobile community platform 202 is then complete and ends.
- HTTP and XML are used to communicate between the third party provider and intermediary billing system of mobile community platform 202 in the steps described above.
- the registration request in step 404 is implemented with an HTTP POST, and can be passed with the following parameters:
- step 407 in which mobile community platform 202 directs the customer back to the third party provider along with the verification code, and the same parameter fields as discussed above.
- the URL to which the customer is directed back to is specified by the third party provider.
- An example of HTML for the redirect of step 407 is shown below in Table 2:
- the confirmation request of the verification code in step 408 is sent from the third party provider using an HTTP POST or an HTTP GET directly between the third party provider and mobile community platform 202 , without involving the customer's browser.
- the parameter for ActionCode is set to “2” for customer confirmation.
- An example of HTML for the confirmation request of step 408 is shown below in Table 3:
- the result for the confirmation request is written by mobile community platform 202 as plain text to the output stream, and the possible return values for the result of the confirmation request are:
- FIG. 5 is a flowchart that depicts the processing of a billing request for a transaction according to an exemplary embodiment, after the registration and activation process described above has been completed successfully.
- the process starts and proceeds to step 501 in which the customer initiates a billing event by requesting the product, such as premium content or services, for which the third party was registered and/or activated as described above with respect to FIG. 4 .
- the third party provider generates a billing request that includes the customer identification code, a product identification code for the product that is the subject of the transaction, and a provider identification code of the third party provider. Other parameters may also be included in the billing request.
- mobile community platform 202 receives the billing request described above and then performs validation of the billing request in step 504 .
- the validation of the billing request is performed by determining whether the customer identification code in the billing request corresponds to a customer in the database of mobile community platform 202 , and by determining whether the provider identification code in the billing request corresponds to a valid third party provider in the database of mobile community platform 202 . If it is determined in step 505 that the billing request validation result is not valid, then the process proceeds to step 506 in which mobile community platform 202 sends an error reply to the third party provider, upon which the third party provider may refuse access to the product by the customer.
- step 505 determines whether the billing request validation result is valid. If it is determined in step 505 that the billing request validation result is valid, then the process proceeds to step 507 in which mobile community platform 202 sends at least one message, such as a premium SMS or other type of billable message, to the mobile phone number associated with the customer identification code in the database of mobile community platform 202 .
- the message is sent from mobile community platform 202 through the carrier for the customer's mobile phone number, so that a billable amount associated with the message is billed to the customer's account with the carrier. In this manner, the transaction for a product between the customer and the third party provider is easily supported by mobile community platform 202 through the use of billable messages sent to the customer.
- the billing request from the third party provider may include a message text string which is then included in the message sent from mobile community platform 202 to the customer's mobile phone number.
- a text string may be used by the third party provider to thank the customer for the purchase, and possibly to confirm the details of the purchase, such as the product identification, the transaction price, etc.
- step 508 mobile community platform 202 sends a confirmation to the third party provider that the customer was billed, upon which the third party provider may enable access to the product by the customer.
- the billing process of FIG. 5 then ends.
- the billing request of the invention may be formatted as XML and transmitted via an HTTP POST to a target URL set by mobile community platform 202 .
- the POST parameter name is AMU, which is an XML string that contains the following fields:
- the possible response code for the billing request include the error reply of step 506 and the confirmation of step 508 in FIG. 5 .
- the response codes are indicated of these replies are indicated by a “1” for success, and a “0” for failure (error).
- the response of “0” for failure can also include a failure message that provides a brief explanation of why the billing request failed.
- FIG. 6 is a flowchart which provides another exemplary embodiment of processing a billing transaction according to the invention.
- the process starts and proceeds to step 601 in which a customer initiates a billing event by selecting a product, such as premium content or services, offered through the third party provider.
- the third party provider directs the customer to mobile community platform 202 (intermediary billing system), along with a provider identification code for the third party provider and a product identification code for the product.
- the customer is directed to mobile community platform 202 through the use of a hyperlink.
- step 603 mobile community platform 202 determines whether the customer needs to login, and register if not already registered. The customer does not need to login if the customer is registered and has previously been successfully through this process for the same product. If the login or registration is required, the process proceeds to step 605 . On the other hand, if the login or registration is required, the process proceeds to step 604 in which the customer logs in to mobile community platform 202 , or registers with mobile community platform 202 as described above in the embodiment of FIG. 4 . Next, in step 605 , mobile community platform 202 prompts the customer for a confirmation of an instruction to proceed with the transaction, and displays a description of the product (service or content) along with the price and possibly other information.
- step 606 mobile community platform 202 generates an encrypted cookie that indicates the customer has “opted in” (purchased) the product, and can therefore skip steps 603 to 606 in the future for transactions involving this particular product.
- the encrypted cookie is then placed in the customer's browser application.
- mobile community platform 202 bills the customer for the product by sending a premium message to the mobile phone number associated with the customer identification code for this customer in the database of mobile community platform 202 .
- the billing value of the premium message corresponds to the transaction price for the product.
- mobile community platform 202 easily handles the billing, which may often be a micro-transaction, for third party provider through the use of premium messages and the existing relationships between various mobile carrier systems and mobile community platform 202 .
- mobile community platform 202 generates a verification code that indicates the customer has been billed for the transaction, encrypts the verification code, and places the encrypted verification code in a cookie on the customer's browser application.
- the verification code is also stored in the database of mobile community platform 202 in association with the customer identification code for this customer. Then customer is then directed back to the third party provider location (such as a website page) associated with the product of the transaction (this URL is specified by the third party provider).
- the third party provider location such as a website page
- mobile community platform 202 accesses the cookie from the customer's browser application and obtains the encrypted verification code.
- mobile community platform 202 receives a validation request from the third party provider, the validation request including a returned encrypted verification code that the third party provider obtained from the cookie in the user's browser, along with the customer identification code for this customer.
- mobile community platform 202 performs validation on the returned encrypted verification code by decrypting it and comparing it against the encrypted verification code that was previously generated by mobile community platform 202 for this transaction, and confirming that the customer has been successfully billed for this transaction. If the verification code is validated by mobile community platform 202 , then flow passes to step 612 in which mobile community platform 202 sends a valid response to the third party provider.
- step 611 mobile community platform 202 sends an error response to the third party provider.
- the third party provider determines whether to provide the customer with access to the product based on the validation response received from mobile community platform 202 (intermediary billing system). The process of FIG. 6 then ends.
- FIG. 7 depicts a billing process according to another embodiment of the invention, in which the intermediary billing system may be standalone and can process transaction requests from any source for a customer and transaction amount, by using various types of external billing mechanisms and billing event triggers.
- the process begins at step 701 in which mobile community platform 202 (intermediary billing system) receives a transaction request, from any source internal or external to mobile community platform 202 , that is associated with a customer identification code and a predetermined transaction amount.
- Mobile community platform 202 then performs validation of the transaction request in step 702 .
- the validation of the transaction request is performed by determining whether the customer identification code in the transaction request corresponds to a previously-registered and activated customer in the database of mobile community platform 202 . If it is determined in step 703 that the transaction request validation result is not valid, then the process proceeds to step 704 in which mobile community platform 202 denies the transaction request, the customer is not billed, and the process ends.
- step 703 determines whether the transaction request validation result is valid. If it is determined in step 703 that the transaction request validation result is valid, then the process proceeds to step 705 in which mobile community platform 202 sends a billing event trigger to an external billing mechanism in order to effectuate billing of the customer for the transaction amount.
- the billing event trigger is associated with the customer identification code, and may actually contain the customer identification code, so that the external billing mechanism bills the correct customer for the transaction amount.
- the external billing mechanism can be any type of mechanism or system for billing the customer, such as the billing system of a mobile carrier for the customer's mobile phone (as discussed above), a credit card billing system, a prepaid card billing system, a web-based payment system, a bank account billing system, or any other billing system or mechanism to which mobile community platform 202 can interface and direct a billing event trigger for a customer.
- Mobile community platform 202 can simultaneously use several different external billing mechanisms, and may use one or several of them for each customer depending on the type of third party providers with which the customer conducts transactions.
- mobile community platform 202 acts as a virtual point-of-sale for third party providers to enable the payment for transactions through the use of one or more external billing mechanisms with which mobile community platform 202 has a pre-existing relationship for authorized use of the external billing mechanisms.
- the billing event trigger can be one of many different types and formats, depending on the external billing mechanism to which the billing event trigger is sent for the customer, and the pre-existing arrangement (if any) that mobile community platform 202 has with the external billing mechanism.
- the billing event trigger can be a message, such as a premium SMS, MMS, or other type of billable message, that is sent from mobile community platform 202 to the customer's mobile phone number through the mobile carrier.
- other types of billing event triggers can be used with the external billing mechanism.
- the billing event trigger sent to the mobile carrier billing system can be a billing record file which contains the transactions for a customer that will then be added to the customer's carrier bill by the mobile carrier billing system.
- other types and forms of billing event triggers that can be used by mobile community platform 202 include messages such as SMS, MMS, email, file transfers, XML, HTTP, billing record transfers, or any other type of communication supported by the internet, encrypted or unencrypted.
- the transaction request from the third party provider may include a message text string which is then included in the message sent from mobile community platform 202 to the customer's mobile phone number. Such a text string may be used to thank the customer for the purchase, and possibly to confirm the details of the purchase, such as the product identification, the transaction price, etc.
- the process of FIG. 7 then ends. It can be appreciated that the general billing system depicted in FIG. 7 provides a powerful, efficient and convenient way with which to bill customers for various types of transactions by using an existing interface between mobile community platform 202 and one or more external billing mechanisms.
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Development Economics (AREA)
- Signal Processing (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Marketing (AREA)
- Computer Security & Cryptography (AREA)
- Technology Law (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Mobile Radio Communication Systems (AREA)
- Meter Arrangements (AREA)
- Control Of Vending Devices And Auxiliary Devices For Vending Devices (AREA)
Abstract
Billing a customer through an intermediary billing system for a transaction by receiving, at the intermediary billing system, a transaction request associated with a transaction amount and a customer identification code, validating, in the intermediary billing system, the transaction request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and sending, in the case that the transaction request is valid, a billing event trigger associated with the customer identification code to an external billing mechanism, the billing event trigger representing the transaction amount.
Description
- This present application claims the benefit of priority as a Continuation under 35 U.S.C. §120 of U.S. patent application Ser. No. 11/446,973, filed Jun. 6, 2006 and entitled “BILLING SYSTEM AND METHOD FOR MICRO-TRANSACTIONS,” which in turn claims the benefit of priority under 35 U.S.C. §119 from U.S. Provisional Patent Application Ser. No. 60/687,663 entitled “METHOD AND SYSTEM BY WHICH MICRO TRANSACTIONS ARE PROCESSED,” filed on Jun. 6, 2005, and U.S. Provisional Patent Application Ser. No. 60/689,641 entitled “METHOD AND SYSTEM BY WHICH MICRO PAYMENT TRANSACTIONS OCCUR VIA A WIRELESS DEVICE AND/OR INTERNET PORTAL,” filed on Jun. 10, 2005, all of which are incorporated herein by reference in their entirety for all purposes.
- The present invention concerns the automated processing of transactions, including small transactions known as micro-transactions. In particular, the invention concerns the use of an intermediate billing system that acts on behalf of third party providers of content or services by interacting with various external billing mechanisms to effectuate transactions between such third party providers and their customers.
- While credit card use and automatic credit card billing is a common way to conduct business transactions in many countries, they are not necessarily the best way in some situations. In particular, there are many users of the internet that do not have access to a credit card or do not want to use their credit card for an internet based transaction out of security concerns. Many such users most likely have a mobile phone or mobile device, and it would be more easy and efficient to have a mechanism for billing the user for transactions through the user's pre-existing account with the mobile carrier associated with the user's mobile phone number. In addition, the use of a credit card is economically viable only if the transaction amount, or a volume of such transactions, exceeds a particular amount that depends on the underlying efficiency of the billing and collecting system implemented by the merchant and by the credit card provider. Currently, mobile phone carriers routinely bill users for small transactional amounts, such as a one minute call, or portion thereof, and are able to bill and collect for these small transactions while making a profit. These small transactions are referred to as micro-transactions and, in terms of U.S. currency, can be as small as a few pennies, although larger transactions occur as well.
- Retailers or vendors, such as internet commercial websites, may desire to provide their respective content or services to mobile phone users via the internet or directly through the user's mobile phone, and bill the user for such content or services as micro-transactions. Currently, a retailer or vendor will find it very difficult and inefficient to bill and collect for such a micro-transaction because the retailer/vendor would need to negotiate and enter into a contractual relationship with the mobile phone carrier in order to bill the mobile phone user subscribed to that carrier. The process is further complicated by the fact that the universe of customers with mobile phones use different mobile phone carriers. Accordingly, the retailer/vendor would need to enter into contractual relationships with many different mobile phone carriers in order to be able to provide a mobile phone based micro-transaction billing option to the desired global market of mobile phone users. A retailer or vendor can try to use billing mechanisms other than mobile carriers, such as prepaid card services, web-based payment services, bank account and credit card billing services, and other such external billing mechanisms to support customer transactions. However, in such examples, the same problem still exists for the vendor/retailer because they would still need to have pre-existing relationships with all of the various external billing mechanisms that their various customers wish to use for payment of transactions.
- Thus, there exists a need for a system and method that allows retailers/vendors to easily conduct transactions, many of which may be micro-transactions, with a global market of customers, where the transactions are easily billable through a single intermediate billing system which can effectuate the transaction through a wide variety of external billing mechanisms on behalf of the retailer/vendor, thereby eliminating the need for the retailer/vendor to individually establish a pre-existing relationship with each of the wide variety of external billing mechanisms.
- The present invention solves the foregoing problems by providing a method and system that uses a single intermediate billing system to effectuate transactions between retailers/vendors and their customers through a wide variety of external billing mechanisms, without the need for the retailer/vendor to individually establish a pre-existing relationship with each of the wide variety of external billing mechanisms.
- In one embodiment, the invention is directed to a method and system for billing a customer through an intermediary billing system for a transaction, by receiving, at the intermediary billing system, a transaction request associated with a transaction amount and a customer identification code, validating, in the intermediary billing system, the transaction request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and sending, in the case that the transaction request is valid, a billing event trigger associated with the customer identification code to an external billing mechanism, the billing event trigger representing the transaction amount.
- In another embodiment, the invention is directed to a method and system for billing a customer through an intermediary billing system for a transaction between the customer and a third party provider, by receiving, at the intermediary billing system, a registration request to register the customer, registering the customer in the intermediary billing system by providing a mobile phone number of the customer to the intermediary billing system, assigning a customer identification code to the customer, the customer identification code being shared with the third party provider, and associating the mobile phone number of the customer with the customer identification code assigned to the customer, receiving, at the intermediary billing system, a billing request from the third party provider, the billing request including a product identification code corresponding to a product associated with the transaction between the customer and the third party provider, a customer identification code assigned to the customer and a provider identification code corresponding to the third party provider, validating, in the intermediary billing system, the billing request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and by determining whether the provider identification code corresponds to a valid third party provider, and sending, in the case that the billing request is validated, at least one message from the intermediary billing system to a mobile phone number associated with the customer identification code, the at least one message representing a billing value that corresponds to the product identification code.
- In another embodiment of the invention, a method and system is provided for billing a customer through an intermediary billing system for a transaction between the customer and a third party provider, by receiving, at the intermediary billing system, a transaction activation request from the third party provider to activate a customer for the transaction associated with a product offered by the third party provider, the customer being automatically directed from the third party provider to the intermediary billing system, prompting, by the intermediary billing system, the customer to confirm an instruction to proceed with the transaction, sending, in the case that the customer confirms the instruction to proceed with the transaction, at least one message from the intermediary billing system to a mobile phone number associated with a customer identification code for the customer, the at least one message representing a billing value that corresponds to the product, generating, in the intermediary billing system, an encrypted verification code in association with the customer identification code for the customer, installing the encrypted verification code on a web browser application of the customer (for browsing web pages on the internet), and automatically directing the customer from the intermediary billing system to the third party provider, receiving, at the intermediary billing system, a verification code validation request containing a returned encrypted verification code and a customer identification code from the third party provider, and validating, in the intermediary billing system, whether the returned encrypted verification code is the same as the encrypted verification code sent from the intermediary billing system to the third party provider for that customer identification code, and sending, from the intermediary billing system, a validation response to the third party provider, the validation response containing an error code in the case that the returned encrypted verification code is not valid, and containing a valid confirmation code in the case that the returned encrypted verification code is valid, wherein the third party provider enables the customer to access the product on the basis of the validation response received by from the intermediary billing system.
- In this manner, the present invention provides that an efficient and timely billing system that utilizes mobile text messages to bill customers for transactions between the customers and third-party providers of content or services, without the need for a third-party provider to have any relationship or interaction with the mobile phone carrier of the customer.
- This brief summary has been provided so that the general nature of the invention may be understood quickly. A more complete understanding of the invention can be obtained by reference to the following detailed description thereof in connection with the attached drawings. It is to be understood that embodiments of the invention other than that provided in the description below and the accompanying drawings may be utilized and that changes may be made without departing from the scope of the present invention.
-
FIG. 1 is a block diagram of a computer system with which the present invention may be practiced, according to one embodiment of the invention; -
FIG. 2 is a block diagram of a mobile community environment in which the invention may be practiced, according to one embodiment of the invention; -
FIG. 3 is a block diagram providing a detailed view of the mobile community platform shown inFIG. 2 ; -
FIG. 4 is a flowchart for explaining the registration and activation of a customer for transaction billing, according to one embodiment of the invention; -
FIG. 5 is a flowchart for explaining the processing of a billing request for a transaction, according to one embodiment of the invention; -
FIG. 6 is a flowchart for explaining the processing of a transaction, according to another embodiment of the invention; and -
FIG. 7 is a flowchart for explaining the processing of a billing request for a transaction, according to another embodiment of the invention. - As mentioned above, the present invention is a method and system that utilizes an intermediary billing system in conjunction with one or more external billing mechanisms for supporting transactions between customers and third-party providers of content or services, without the need for a third-party provider to have a relationship or interaction with any of the external billing mechanisms.
-
FIG. 1 is a block diagram of an exemplary computer system with which one embodiment of the present invention may be practiced. As seen inFIG. 1 ,computer system 100 includes abus 102 or other communication mechanism for communicating information, and aprocessor 104 coupled withbus 102 for processing information.Computer system 100 also includes amain memory 106, such as a random access memory (RAM) or other dynamic storage device, coupled tobus 102 for storing information and instructions to be executed byprocessor 104.Main memory 106 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed byprocessor 104.Computer system 100 further includes a read only memory (ROM) 108 or other static storage device coupled tobus 102 for storing static information and instructions forprocessor 104. Astorage device 110, such as a magnetic disk or optical disk, is provided and coupled tobus 102 for storing information and instructions. -
Computer system 100 may be coupled viabus 102 to adisplay 112, such as a cathode ray tube (CRT), for displaying information to a computer user. Aninput device 114, including alphanumeric and other keys, is coupled tobus 102 for communicating information and command selections toprocessor 104. Another type of user input device iscursor control 116, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections toprocessor 104 and for controlling cursor movement ondisplay 112. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane. -
Computer system 100 operates in response toprocessor 104 executing one or more sequences of one or more instructions contained inmain memory 106. Such instructions may be read intomain memory 106 from another computer-readable medium, such asstorage device 110. Execution of the sequences of instructions contained inmain memory 106 causesprocessor 104 to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software. - The term “computer-readable medium” as used herein refers to any medium that participates in providing instructions to
processor 104 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such asstorage device 110. Volatile media includes dynamic memory, such asmain memory 106. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprisebus 102. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. - Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
- Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 104 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to
computer system 100 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infra-red detector can receive the data carried in the infra-red signal and appropriate circuitry can place the data onbus 102.Bus 102 carries the data tomain memory 106, from whichprocessor 104 retrieves and executes the instructions. The instructions received bymain memory 106 may optionally be stored onstorage device 110 either before or after execution byprocessor 104. -
Computer system 100 also includes acommunication interface 118 coupled tobus 102.Communication interface 118 provides a two-way data communication coupling to anetwork link 120 that is connected to alocal network 122. For example,communication interface 118 may be an integrated services digital network (ISDN) card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example,communication interface 118 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation,communication interface 118 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information. - Network link 120 typically provides data communication through one or more networks to other data devices. For example,
network link 120 may provide a connection throughlocal network 122 to ahost computer 124 or to data equipment operated by an Internet Service Provider (ISP) 126.ISP 126 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 128.Local network 122 andInternet 128 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals onnetwork link 120 and throughcommunication interface 118, which carry the digital data to and fromcomputer system 100, are exemplary forms of carrier waves transporting the information. -
Computer system 100 can send messages and receive data, including program code, through the network(s),network link 120 andcommunication interface 118. In the Internet example, aserver 130 might transmit a requested code for an application program throughInternet 128,ISP 126,local network 122 andcommunication interface 118. The received code may be executed byprocessor 104 as it is received, and/or stored instorage device 110, or other non-volatile storage for later execution. In this manner,computer system 100 may obtain application code in the form of a carrier wave. Of course, other forms of computing systems may be used to implement the present invention. -
FIG. 2 is a block diagram of a mobile community environment in which the invention may be practiced according to an exemplary embodiment.FIG. 2 depicts a block diagram of a computer-basedmobile community platform 202.Mobile community platform 202 can be implemented in the computing system show inFIG. 1 , or some other form of computing system. As seen inFIG. 2 ,users mobile community platform 202 via a network orsimilar communications channel 210. In an exemplary embodiment,network 210 is the internet by whichusers third party providers third party providers third party providers -
Third party providers FIG. 1 , or other known types of networked computing environments, such as a server, or combination of computers and servers. By means of the connection withmobile community platform 202, a user (e.g., 212) may create a profile page or “home page” supported and maintained bymobile community platform 202 that the user can personalize. This profile page can include various files and content that the user wants to share with other members of themobile community platform 202. - The user's profile page may include a hierarchy of pages, some of which are for public view and some of which have restrictions on viewing. For example, the
mobile community platform 202 can be logically organized into neighborhoods such as “friends”, “family”, “workplace”, “dog owners”, etc.Users - As seen in
FIG. 2 ,mobile community platform 202 connects with variousmobile carrier systems mobile carrier systems Users mobile community platform 202 are also subscribers of one or more of the various mobile carriers, which support the mobile phones, or other mobile devices, ofusers users mobile community platform 202 can access other users' profile pages through the computer-based platform ofmobile community platform 202, and they can also access thesubscribers mobile carrier systems mobile community platform 202. - A significant benefit of the architecture depicted in
FIG. 2 , is that themobile community platform 202 has pre-existing contractual relationships with the variousmobile carrier systems mobile community platform 202. As is known in the art, themobile carrier systems - When
mobile community platform 202 sends a message via a mobile carrier system (e.g., 204), it is billing the subscriber-recipient of the message using the existing billing system of that mobile carrier. The billing event is often a micro-transaction of a small monetary amount (e.g., less than one dollar). Thus, a user (e.g., 212) of the mobile community platform may purchase a service or content withinmobile community platform 202 and be billed for those transactions through that user's mobile carrier service account. The present invention provides for such micro-transaction billing support throughmobile community platform 202 for a transaction between a user (e.g., 212) and a third party provider (e.g., 231) which is external tomobile community platform 202. In this manner, a third party provider need only communicate withmobile community platform 202 to conduct transactions with users, and does not require any affiliation or agreement with the various mobile carrier systems of the users. -
FIG. 3 depicts a more detailed view ofmobile community platform 202. As mentioned above,mobile community platform 202 can be used to conduct micro-transactions in which a mobile carrier's billing system is used bymobile community platform 202 to automatically bill the user for each micro-transactions with a third party provider, without the need for a negotiation or contract between the third party provider and the mobile carrier. An example of this feature is a third party provider that operates a website which offers sports score updates to users ofmobile community platform 202 for a predetermined price, while taking advantage of the billing arrangements already in place betweenmobile community platform 202 and themobile carriers mobile community platform 202. - Turning to
FIG. 3 ,mobile community platform 202 includesmultimedia messaging system 302,user area 304, which supports content, community and commerce functions for the users, including website interface for users tomobile community platform 202, andintermediary billing interface 306. The details of these different components are more fully explained below. - As noted earlier,
users user area 304 ofmobile community platform 202 in order to participate in an online-based community of users that includes various communication, content and commerce opportunities. The user accesses a website ofuser area 304 through the user's web browser that may be hosted on a laptop or desktop computer, or, in the alternative, even on the user's mobile device such as a PDA or mobile phone. In this regard,user area 304 includes a web server that communicates withusers mobile community platform 202 is able to present a profile page (“home page”) to a user (e.g., 212) that reflects a set of content, information and products associated with, and desired by, that particular user. This set of content, information and products is not maintained on the local computer being used by theuser 212 but, rather, is maintained and managed by the computing environment ofmobile community platform 202. Although not explicitly depicted inFIG. 3 , one of ordinary skill will recognize that there are numerous functionally equivalent techniques to create, manage, store and serve user information, user profiles, user content, software tools and other resources within theuser area 304. Included in these techniques are methods to ensure security, data integrity, data availability and quality of service metrics. - Multimedia messaging system (MMS) 302 includes applications for connecting with and communicating with the multiple different
mobile carriers mobile community platform 202.MMS 302 is configured to generate message requests in the appropriate format for each of themobile carriers mobile carriers mobile community platform 202 uses the mobile carriers to bill user/subscribers of the mobile carriers for transactions conducted throughmobile community platform 202. - The
MMS 302 communicates with theuser area 304, such that users ofmobile community platform 202 can advantageously use the connectivity betweenMMS 302 and themobile carriers mobile carriers -
Intermediary billing interface 306 provides an interface betweenthird party providers mobile community platform 202 for enabling transactions between such third party providers andusers intermediary billing interface 306 is accessed by the third party providers via network connection 210 (internet). As seen inFIG. 3 ,intermediary billing interface 306 is in communication withuser area 304, both of which are in communication withMMS 302. Accordingly,intermediary billing interface 306 can access user information fromuser area 304, such as whether the user is registered and verified for billing through their mobile phone number, as discussed more fully below.Intermediary billing interface 306 can interface withuser area 304 to communicate with a user, such as via webpages supported byuser area 304, for purposes of registering the user withmobile community platform 202 and verifying the user for billing of transactions related to a product offered through a third party provider, as also discussed in more detail below. - As seen in
FIG. 3 ,intermediary billing interface 306 also includeslocal database 310 which is used byintermediary billing interface 306 to store customer identification codes, third party provider identification codes, and other information for implementing the present invention. Accordingly,third party providers mobile community platform 202 whereby billable transactions withusers mobile carriers mobile community platform 202 and themobile carriers mobile community platform 202. -
FIG. 4 is a flowchart that provides an exemplary depiction of the registration and activation of a customer for transaction billing in one embodiment of the invention. The process starts inFIG. 4 and proceeds to step 40 I in which it is determined whether the customer (e.g. one ofusers third party providers mobile community platform 202, which acts as the intermediary billing system in either case. If the customer is initiating the transaction atmobile community platform 202, then the process proceeds to step 405 which is discussed further below. On the other hand, if the customer is initiating the transaction at the third party provider, then the process proceeds to step 402 in which the third party provider determines if the customer is already registered as a customer with the third party provider. If the customer is already registered with the third party provider, then the process proceeds to step 404. If not, then the process proceeds to step 403 in which the customer registers with the third party provider, such as by providing the customer's name and contact information, and in which the third party provider generates a unique customer identification code corresponding to that customer. Of course, it should be appreciated that the third party provider can use any form of registration process and may not necessarily require the customer to provide any specific information, in which case the third party provider simply generates and assigns a unique customer identification code to that customer. In this regard, the third party provider maintains a database of its registered customers, and their corresponding customer identification numbers and information. The customer identification number will be used in the invention for common tracking of the same customer between the third party provider and the intermediary billing system ofmobile community platform 202. - In
step 404, the third party provider directs the customer tomobile community platform 202 along with a registration request to register and activate the customer, the request including the customer identification code for the customer. Next, instep 405, the registration and activation steps for the customer begin by the mobile community platform 202 (intermediary billing system) determining if the customer is already registered as a member ofmobile community platform 202. If the customer is already registered withmobile community platform 202, then the process proceeds to step 407. If not, then the process proceeds to step 406 in which the customer registers withmobile community platform 202, such as by providing the customer's name and contact information, including the customer's mobile phone number, which is used bymobile community platform 202 in the invention to bill the customer for the transaction. - If it was determined in
step 401 that the customer is originating the transaction atmobile community platform 202, thenmobile community platform 202 also generates a unique customer identification code for the customer. Also in the registration process,mobile community platform 202 stores the customer identification code for the customer in a database of registered customers, along with related information, maintained inmobile community platform 202, and activates the customer's mobile phone number for transaction billing as described below. - Continuing with the registration and activation process, the
mobile community platform 202 generates a verification code for the registration/activation of the customer, and directs the customer back to the third party provider along with the verification code, the customer identification code, and possibly other information, instep 407. Next, instep 408, the third party provider sends a verification code validation request tomobile community platform 202, the request including the verification code for the customer, to make sure that the third party provider andmobile community platform 202 are in agreement on the customer identification code to be used for the customer, and that the customer is registered and activated for the transaction in both the third party provider and themobile community platform 202. In this regard, the term “activated” means that themobile community platform 202 has enabled the customer associated with the assigned customer identification code to be billed for transactions, such as through the customer's mobile phone number, or through some other external billing mechanism used bymobile community platform 202. - In
step 409,mobile community platform 202 determines whether the verification code received in the verification code validation request from the third party provider is valid by comparing it to the verification code stored in the database ofmobile community platform 202 for that customer identification code. If the two codes match, then the verification code is valid, andmobile community platform 202 sends a confirmation reply to the third party provider instep 411 to confirm that the verification code is valid. If the two codes do not match, then the verification code is not valid, andmobile community platform 202 sends an error reply to the third party provider instep 410 to advise that the verification code is not valid. The registration and activation process for the customer between the third party provider andmobile community platform 202 is then complete and ends. - In an exemplary embodiment of the invention, HTTP and XML are used to communicate between the third party provider and intermediary billing system of
mobile community platform 202 in the steps described above. In particular, the registration request instep 404 is implemented with an HTTP POST, and can be passed with the following parameters: -
- ActionCode: 1 means to activate the customer;
- 2 means to confirm the verification code;
- PartnerID: Assigned by mobile community platform to uniquely identify the third party provider (partner);
- ProductID: Assigned by mobile community platform to uniquely identify the particular product involved in the transaction;
- CustomerID: Customer identification code for the customer;
- FirstName: First name of customer;
- LastName: Last name of customer;
- EmailAddress: Email address of customer;
- Birthdate: Birthdate of customer;
- Gender: Gender of customer;
Preferably, the ActionCode, PartnerID, ProductID, and CustomerID are required parameters.
- ActionCode: 1 means to activate the customer;
- An example of HTML for the registration request is shown below in Table 1:
-
TABLE 1 <html> <head> <script type=“text/javascript”> function frmSubmit( ) {window.document.form1.submit( );} </script> </head> <!-- Auto submit when body loads. --> <body LANGUAGE=“JavaScript” onload=“return frmSubmit( )”> <form id=“form1” name=“form1” action=“http://www.sms.ac/Directory/ppcoptin.aspx” method=“POST”> <input type=“hidden” name=“action” value=“1”> <input type=“hidden” name=“PartnerId” value=“1234”> <input type=“hidden” name=“ProductId” value=“5678”> <input type=“hidden” name=“CustomerId” value=“test_user_01”> <input type=“hidden” name=“FirstName” value=“John”> <input type=“hidden” name=“LastName” value=“Smith”> <input type=“hidden” name=“EmailAddress” value=“js@ExampleEmail.com”> <input type=“hidden” name=“BirthDate” value=“05/21/1977”> <input type=“hidden” name=“Gender” value=“M”> </form> </body> </html> - Similarly, an HTTP POST is used in
step 407 in whichmobile community platform 202 directs the customer back to the third party provider along with the verification code, and the same parameter fields as discussed above. The URL to which the customer is directed back to is specified by the third party provider. An example of HTML for the redirect ofstep 407 is shown below in Table 2: -
TABLE 2 <html> <head> <script type=“text/javascript”> function frmSubmit( ) {window.document.form1.submit( );} </script> </head> <!-- Auto submit when body loads. --> <body LANGUAGE=“JavaScript” onload=“return frmSubmit( )”> <form id=“form1” name=“form1” action= “http://www.MobilePartner.com/CustomeLandingPage.html” method=“POST”> <input type=“hidden” name=“VC” value= “EXAMPLE_VERIFICATION_CODE”> <input type=“hidden” name=“PartnerId” value=“1234”> <input type=“hidden” name=“ProductId” value=“5678”> <input type=“hidden” name=“CustomerId” value=“test_user_01”> <input type=“hidden” name=“FirstName” value=“John”> <input type=“hidden” name=“LastName” value=“Smith”> <input type=“hidden” name=“EmailAddress” value=“js@ExampleEmail.com”> <input type=“hidden” name=“BirthDate” value=“05/21/1977”> <input type=“hidden” name=“Gender” value=“M”> </form> </body> </html> - In the same manner, the confirmation request of the verification code in
step 408 is sent from the third party provider using an HTTP POST or an HTTP GET directly between the third party provider andmobile community platform 202, without involving the customer's browser. The parameter for ActionCode is set to “2” for customer confirmation. An example of HTML for the confirmation request ofstep 408 is shown below in Table 3: -
TABLE 3 <html> <head> <script type=“text/javascript”> function frmSubmit( ) {window.document.form1.submit( );} </script> </head> <!-- Auto submit when body loads. --> <body LANGUAGE=“JavaScript” onload=“return frmSubmit( )”> <form id=“form1” name=“form1” action=“http://www.sms.ac/Directory/ppcoptin.aspx” method=“POST”> <input type=“hidden” name=“action” value=“2”> <input type=“hidden” name=“vc” value=“EXAMPLE_VERIFICATION_CODE”> <input type=“hidden” name=“PartnerId” value=“1234”> <input type=“hidden” name=“CustomerId” value=“test_user_01”> </form> </body> </html> - In this regard, the result for the confirmation request is written by
mobile community platform 202 as plain text to the output stream, and the possible return values for the result of the confirmation request are: -
- “Success: #CustomerID# has been verified”
- “Error: bad ‘CustomerID’: #CID#”
- “Error: bad ‘vc’: #VC#”
- “Error: bad PartnerID': #PID#”
- “Error: could not verify ‘CustomerID’: #CID#” or ‘PartnerID’: #PID#”
-
FIG. 5 is a flowchart that depicts the processing of a billing request for a transaction according to an exemplary embodiment, after the registration and activation process described above has been completed successfully. InFIG. 5 , the process starts and proceeds to step 501 in which the customer initiates a billing event by requesting the product, such as premium content or services, for which the third party was registered and/or activated as described above with respect toFIG. 4 . Instep 502, the third party provider generates a billing request that includes the customer identification code, a product identification code for the product that is the subject of the transaction, and a provider identification code of the third party provider. Other parameters may also be included in the billing request. - Next, in
step 503, mobile community platform 202 (intermediary billing system) receives the billing request described above and then performs validation of the billing request instep 504. The validation of the billing request is performed by determining whether the customer identification code in the billing request corresponds to a customer in the database ofmobile community platform 202, and by determining whether the provider identification code in the billing request corresponds to a valid third party provider in the database ofmobile community platform 202. If it is determined instep 505 that the billing request validation result is not valid, then the process proceeds to step 506 in whichmobile community platform 202 sends an error reply to the third party provider, upon which the third party provider may refuse access to the product by the customer. - On the other hand, if it is determined in
step 505 that the billing request validation result is valid, then the process proceeds to step 507 in whichmobile community platform 202 sends at least one message, such as a premium SMS or other type of billable message, to the mobile phone number associated with the customer identification code in the database ofmobile community platform 202. The message is sent frommobile community platform 202 through the carrier for the customer's mobile phone number, so that a billable amount associated with the message is billed to the customer's account with the carrier. In this manner, the transaction for a product between the customer and the third party provider is easily supported bymobile community platform 202 through the use of billable messages sent to the customer. The billing request from the third party provider may include a message text string which is then included in the message sent frommobile community platform 202 to the customer's mobile phone number. Such a text string may be used by the third party provider to thank the customer for the purchase, and possibly to confirm the details of the purchase, such as the product identification, the transaction price, etc. - In
step 508,mobile community platform 202 sends a confirmation to the third party provider that the customer was billed, upon which the third party provider may enable access to the product by the customer. The billing process ofFIG. 5 then ends. - Similar to the registration and activation process, the billing request of the invention may be formatted as XML and transmitted via an HTTP POST to a target URL set by
mobile community platform 202. The POST parameter name is AMU, which is an XML string that contains the following fields: -
- CommunityID: Root XML tag;
- Authentication: Tag denotes the authentication section of the document;
- TransmissionID: Unique identifier for the transmission;
- PartnerID: Unique identifier for the third party provider (partner);
- UserID: Community member name;
- Password: Password of community member;
- ProductID: Unique identifier for the product;
- MessageText: Text to be included in premium message; and
- CustomerID: Customer identification code for the customer.
- Preferably, all of the above fields are required. An example of the XML for the billing request is shown below in Table 4:
-
TABLE 4 <?xml version=“1.0” encoding=“utf-16”?> <SMSac xmlns=“http://tempuri.org/SMSacXMLSample.xsd”> <TransmissionId>234032832</TransmissionId> <Authentication> <MobilePartnerId>TestMPID</MobilePartnerId> <!--Required; Mobile Partner Username --> <UserId>TestUserID</UserId> <!--Required; SMS.ac Member Name --> <Password>Password1</Password> <!--Required; Password of your sms.ac account --> </Authentication> <UserOriginatedMessages> <UserOriginatedMessage> <ProductId>5678</ProductId> <!--Required; The ID of the Mobile Product --> <MessageText> Thank you for using www.MobilePartner.com </MessageText> <!--Required; The Text of the Message --> <CustomerId>test_user_01</CustomerId> <!--Required; The Customer that is to be charged --> </UserOriginatedMessage> </UserOriginatedMessages> </SMSac>
and an example XSD for the request is shown below in Table 5: -
TABLE 5 <?xml version=“1.0”?> <xs:schema id=“NewDataSet” targetNamespace=“sms.ac” xmlns:mstns=“sms.ac” xmlns=“sms.ac” xmlns:xs=“http://www.w3.org/2001/XMLSchema” xmlns:msdata=“urn:schemas-microsoft-com:xml-msdata” attributeFormDefault=“qualified” elementFormDefault=“qualified”> <xs:element name=“SMSac”> <xs:complexType> <xs:sequence> <xs:element name=“TransmissionId” type=“xs:int” minOccurs=“1” maxOccurs=“1”/> <xs:element name=“Authentication” minOccurs=“1” maxOccurs=“1”> <xs:complexType> <xs:sequence> <xs:element name=“MobilePartnerId” type=“xs:int” minOccurs=“1” maxOccurs=“1” /> <xs:element name=“UserId” type=“xs:string” minOccurs=“1” maxOccurs=“1” /> <xs:element name=“Password” type=“xs:string” minOccurs=“1” maxOccurs=“1” /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=“UserOriginatedMessages” minOccurs=“0” maxOccurs=“1”> <xs:complexType> <xs:sequence> <xs:element name=“UserOriginatedMessage” minOccurs=“0” maxOccurs=“unbounded”> <xs:complexType> <xs:sequence> <xs:element name=“ProductId” type=“xs:int” minOccurs=“1” /> <xs:element name=“MessageText” type=“xs:string” minOccurs=“1” /> <xs:element name=“CustomerId” type=“xs:string” minOccurs=“1” /> <xs:element name=“ChargeType” default=“Premium”> <xs:simpleType> <xs:restriction base=“xs:string”> <xs:enumeration value=“Premium”/> <xs:enumeration value=“Standard”/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name=“NewDataSet” msdata:IsDataSet=“true” msdata:EnforceConstraints=“False”> <xs:complexType> <xs:choice maxOccurs=“unbounded”> <xs:element ref=“SMSac” /> </xs:choice> </xs:complexType> </xs:element> </xs:schema> - The possible response code for the billing request, include the error reply of
step 506 and the confirmation ofstep 508 inFIG. 5 . In this regard, the response codes are indicated of these replies are indicated by a “1” for success, and a “0” for failure (error). The response of “0” for failure can also include a failure message that provides a brief explanation of why the billing request failed. -
FIG. 6 is a flowchart which provides another exemplary embodiment of processing a billing transaction according to the invention. As seen inFIG. 6 , the process starts and proceeds to step 601 in which a customer initiates a billing event by selecting a product, such as premium content or services, offered through the third party provider. Then, instep 602, the third party provider directs the customer to mobile community platform 202 (intermediary billing system), along with a provider identification code for the third party provider and a product identification code for the product. This initiates the transaction activation process. In a particular embodiment, the customer is directed tomobile community platform 202 through the use of a hyperlink. - In
step 603,mobile community platform 202 determines whether the customer needs to login, and register if not already registered. The customer does not need to login if the customer is registered and has previously been successfully through this process for the same product. If the login or registration is required, the process proceeds to step 605. On the other hand, if the login or registration is required, the process proceeds to step 604 in which the customer logs in tomobile community platform 202, or registers withmobile community platform 202 as described above in the embodiment ofFIG. 4 . Next, instep 605,mobile community platform 202 prompts the customer for a confirmation of an instruction to proceed with the transaction, and displays a description of the product (service or content) along with the price and possibly other information. Assuming the customer confirms the transaction, the process proceeds to step 606, in whichmobile community platform 202 generates an encrypted cookie that indicates the customer has “opted in” (purchased) the product, and can therefore skipsteps 603 to 606 in the future for transactions involving this particular product. The encrypted cookie is then placed in the customer's browser application. - In
step 607,mobile community platform 202 bills the customer for the product by sending a premium message to the mobile phone number associated with the customer identification code for this customer in the database ofmobile community platform 202. The billing value of the premium message corresponds to the transaction price for the product. In this manner,mobile community platform 202 easily handles the billing, which may often be a micro-transaction, for third party provider through the use of premium messages and the existing relationships between various mobile carrier systems andmobile community platform 202. Next, instep 608,mobile community platform 202 generates a verification code that indicates the customer has been billed for the transaction, encrypts the verification code, and places the encrypted verification code in a cookie on the customer's browser application. The verification code is also stored in the database ofmobile community platform 202 in association with the customer identification code for this customer. Then customer is then directed back to the third party provider location (such as a website page) associated with the product of the transaction (this URL is specified by the third party provider). - The third party provider then accesses the cookie from the customer's browser application and obtains the encrypted verification code. In
step 609,mobile community platform 202 receives a validation request from the third party provider, the validation request including a returned encrypted verification code that the third party provider obtained from the cookie in the user's browser, along with the customer identification code for this customer. Then, instep 610,mobile community platform 202 performs validation on the returned encrypted verification code by decrypting it and comparing it against the encrypted verification code that was previously generated bymobile community platform 202 for this transaction, and confirming that the customer has been successfully billed for this transaction. If the verification code is validated bymobile community platform 202, then flow passes to step 612 in whichmobile community platform 202 sends a valid response to the third party provider. If, on the other hand, the verification code is not validated bymobile community platform 202, then flow passes to step 611 in whichmobile community platform 202 sends an error response to the third party provider. The third party provider then determines whether to provide the customer with access to the product based on the validation response received from mobile community platform 202 (intermediary billing system). The process ofFIG. 6 then ends. - It can be appreciated that the invention may be carried out in various embodiments, in which some of the above described aspects may not be included. In this regard,
FIG. 7 depicts a billing process according to another embodiment of the invention, in which the intermediary billing system may be standalone and can process transaction requests from any source for a customer and transaction amount, by using various types of external billing mechanisms and billing event triggers. InFIG. 7 , the process begins atstep 701 in which mobile community platform 202 (intermediary billing system) receives a transaction request, from any source internal or external tomobile community platform 202, that is associated with a customer identification code and a predetermined transaction amount.Mobile community platform 202 then performs validation of the transaction request instep 702. The validation of the transaction request is performed by determining whether the customer identification code in the transaction request corresponds to a previously-registered and activated customer in the database ofmobile community platform 202. If it is determined instep 703 that the transaction request validation result is not valid, then the process proceeds to step 704 in whichmobile community platform 202 denies the transaction request, the customer is not billed, and the process ends. - On the other hand, if it is determined in
step 703 that the transaction request validation result is valid, then the process proceeds to step 705 in whichmobile community platform 202 sends a billing event trigger to an external billing mechanism in order to effectuate billing of the customer for the transaction amount. The billing event trigger is associated with the customer identification code, and may actually contain the customer identification code, so that the external billing mechanism bills the correct customer for the transaction amount. The external billing mechanism can be any type of mechanism or system for billing the customer, such as the billing system of a mobile carrier for the customer's mobile phone (as discussed above), a credit card billing system, a prepaid card billing system, a web-based payment system, a bank account billing system, or any other billing system or mechanism to whichmobile community platform 202 can interface and direct a billing event trigger for a customer.Mobile community platform 202 can simultaneously use several different external billing mechanisms, and may use one or several of them for each customer depending on the type of third party providers with which the customer conducts transactions. Accordingly,mobile community platform 202 acts as a virtual point-of-sale for third party providers to enable the payment for transactions through the use of one or more external billing mechanisms with whichmobile community platform 202 has a pre-existing relationship for authorized use of the external billing mechanisms. - Similarly, the billing event trigger can be one of many different types and formats, depending on the external billing mechanism to which the billing event trigger is sent for the customer, and the pre-existing arrangement (if any) that
mobile community platform 202 has with the external billing mechanism. For example, in the case that the external billing mechanism is the billing system of the mobile carrier corresponding to the customer's mobile phone number, then the billing event trigger can be a message, such as a premium SMS, MMS, or other type of billable message, that is sent frommobile community platform 202 to the customer's mobile phone number through the mobile carrier. In the alternative, other types of billing event triggers can be used with the external billing mechanism. For example, the billing event trigger sent to the mobile carrier billing system can be a billing record file which contains the transactions for a customer that will then be added to the customer's carrier bill by the mobile carrier billing system. As mentioned above, other types and forms of billing event triggers that can be used bymobile community platform 202 include messages such as SMS, MMS, email, file transfers, XML, HTTP, billing record transfers, or any other type of communication supported by the internet, encrypted or unencrypted. - The transaction request from the third party provider may include a message text string which is then included in the message sent from
mobile community platform 202 to the customer's mobile phone number. Such a text string may be used to thank the customer for the purchase, and possibly to confirm the details of the purchase, such as the product identification, the transaction price, etc. The process ofFIG. 7 then ends. It can be appreciated that the general billing system depicted inFIG. 7 provides a powerful, efficient and convenient way with which to bill customers for various types of transactions by using an existing interface betweenmobile community platform 202 and one or more external billing mechanisms. - While the present invention has been particularly described above with reference to the various figures and embodiments, it should be understood that the invention is not limited to the above-described embodiments. Various changes and modifications may be made to the invention by those of ordinary skill in the art without departing from the spirit and scope of the invention.
Claims (1)
1. A method for billing a customer for a transaction between the customer and a third party provider, the method including:
a registration request receipt step of receiving, at the intermediary billing system, a registration request to register the customer;
a customer registration step of registering the customer in the intermediary billing system by providing a mobile phone number of the customer to the intermediary billing system, assigning a customer identification code to the customer, the customer identification code being shared with the third party provider, and associating the mobile phone number of the customer with the customer identification code assigned to the customer;
a billing request receipt step of receiving, at the intermediary billing system, a billing request from the third party provider, the billing request including a product identification code corresponding to a product associated with the transaction between the customer and the third party provider, a customer identification code assigned to the customer and a provider identification code corresponding to the third party provider;
a billing validation step of validating, in the intermediary billing system, the billing request by determining whether the customer identification code corresponds to a customer that is registered with the intermediary billing system, and by determining whether the provider identification code corresponds to a valid third party provider; and
a billing step of sending, in the case that the billing request is validated, at least one billable message from the intermediary billing system to a mobile phone number associated with the customer identification code, the at least one message representing a billing value that corresponds to the product identification code.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/312,944 US20120143737A1 (en) | 2005-06-06 | 2011-12-06 | Billing system and method for micro-transactions |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US68766305P | 2005-06-06 | 2005-06-06 | |
US68964105P | 2005-06-10 | 2005-06-10 | |
US11/446,973 US8073774B2 (en) | 2005-06-06 | 2006-06-06 | Billing system and method for micro-transactions |
US13/312,944 US20120143737A1 (en) | 2005-06-06 | 2011-12-06 | Billing system and method for micro-transactions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/446,973 Continuation US8073774B2 (en) | 2005-06-06 | 2006-06-06 | Billing system and method for micro-transactions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120143737A1 true US20120143737A1 (en) | 2012-06-07 |
Family
ID=37499031
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/446,973 Expired - Fee Related US8073774B2 (en) | 2005-06-06 | 2006-06-06 | Billing system and method for micro-transactions |
US13/312,944 Abandoned US20120143737A1 (en) | 2005-06-06 | 2011-12-06 | Billing system and method for micro-transactions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/446,973 Expired - Fee Related US8073774B2 (en) | 2005-06-06 | 2006-06-06 | Billing system and method for micro-transactions |
Country Status (5)
Country | Link |
---|---|
US (2) | US8073774B2 (en) |
EP (1) | EP1902414A2 (en) |
AU (1) | AU2006255078A1 (en) |
CA (1) | CA2610216A1 (en) |
WO (1) | WO2006133141A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107104806A (en) * | 2017-04-13 | 2017-08-29 | 中国联合网络通信集团有限公司 | Call bill processing method, apparatus and system |
US10762505B1 (en) | 2016-06-13 | 2020-09-01 | Wells Fargo Bank, N.A. | Authentication transaction |
Families Citing this family (120)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7640211B2 (en) * | 2004-03-12 | 2009-12-29 | Sybase 365, Inc. | System and method for billing augmentation |
US8346593B2 (en) | 2004-06-30 | 2013-01-01 | Experian Marketing Solutions, Inc. | System, method, and software for prediction of attitudinal and message responsiveness |
US8732004B1 (en) | 2004-09-22 | 2014-05-20 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
CA2610216A1 (en) | 2005-06-06 | 2006-12-14 | Sms.Ac, Inc. | Billing system and method for micro-transactions |
EP1922883A2 (en) * | 2005-09-07 | 2008-05-21 | SMS. AC, Inc. | Automated billing and distribution platform for application providers |
US8874477B2 (en) | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
EP2667344A3 (en) | 2005-10-06 | 2014-08-27 | C-Sam, Inc. | Transactional services |
US20130332343A1 (en) | 2005-10-06 | 2013-12-12 | C-Sam, Inc. | Multi-tiered, secure mobile transactions ecosystem enabling platform comprising a personalization tier, a service tier, and an enabling tier |
US7826421B2 (en) * | 2006-03-20 | 2010-11-02 | Sms.Ac, Inc. | Application pod integration with automated mobile phone billing and distribution platform |
US20080287095A1 (en) * | 2006-03-20 | 2008-11-20 | Sms.Ac | Systems and methods for generation, registration and mobile phone billing of a network-enabled application with one-time opt-in |
US20080052373A1 (en) * | 2006-05-01 | 2008-02-28 | Sms.Ac | Systems and methods for a community-based user interface |
US7835720B2 (en) * | 2006-05-19 | 2010-11-16 | Sms.Ac, Inc. | Systems and methods for automatic generation, registration and mobile phone billing of a pod using third party web page content |
US9094257B2 (en) | 2006-06-30 | 2015-07-28 | Centurylink Intellectual Property Llc | System and method for selecting a content delivery network |
US8717911B2 (en) | 2006-06-30 | 2014-05-06 | Centurylink Intellectual Property Llc | System and method for collecting network performance information |
US8289965B2 (en) | 2006-10-19 | 2012-10-16 | Embarq Holdings Company, Llc | System and method for establishing a communications session with an end-user based on the state of a network connection |
US8477614B2 (en) | 2006-06-30 | 2013-07-02 | Centurylink Intellectual Property Llc | System and method for routing calls if potential call paths are impaired or congested |
US8488447B2 (en) | 2006-06-30 | 2013-07-16 | Centurylink Intellectual Property Llc | System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance |
US7843831B2 (en) | 2006-08-22 | 2010-11-30 | Embarq Holdings Company Llc | System and method for routing data on a packet network |
US8537695B2 (en) | 2006-08-22 | 2013-09-17 | Centurylink Intellectual Property Llc | System and method for establishing a call being received by a trunk on a packet network |
US8549405B2 (en) | 2006-08-22 | 2013-10-01 | Centurylink Intellectual Property Llc | System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally |
US8407765B2 (en) | 2006-08-22 | 2013-03-26 | Centurylink Intellectual Property Llc | System and method for restricting access to network performance information tables |
US8274905B2 (en) | 2006-08-22 | 2012-09-25 | Embarq Holdings Company, Llc | System and method for displaying a graph representative of network performance over a time period |
US8228791B2 (en) | 2006-08-22 | 2012-07-24 | Embarq Holdings Company, Llc | System and method for routing communications between packet networks based on intercarrier agreements |
US8576722B2 (en) | 2006-08-22 | 2013-11-05 | Centurylink Intellectual Property Llc | System and method for modifying connectivity fault management packets |
US8531954B2 (en) | 2006-08-22 | 2013-09-10 | Centurylink Intellectual Property Llc | System and method for handling reservation requests with a connection admission control engine |
US8750158B2 (en) | 2006-08-22 | 2014-06-10 | Centurylink Intellectual Property Llc | System and method for differentiated billing |
US8619600B2 (en) | 2006-08-22 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for establishing calls over a call path having best path metrics |
US8224255B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for managing radio frequency windows |
US8223655B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for provisioning resources of a packet network based on collected network performance information |
US8064391B2 (en) | 2006-08-22 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for monitoring and optimizing network performance to a wireless device |
US8743703B2 (en) | 2006-08-22 | 2014-06-03 | Centurylink Intellectual Property Llc | System and method for tracking application resource usage |
US8307065B2 (en) | 2006-08-22 | 2012-11-06 | Centurylink Intellectual Property Llc | System and method for remotely controlling network operators |
US8130793B2 (en) | 2006-08-22 | 2012-03-06 | Embarq Holdings Company, Llc | System and method for enabling reciprocal billing for different types of communications over a packet network |
US8189468B2 (en) | 2006-10-25 | 2012-05-29 | Embarq Holdings, Company, LLC | System and method for regulating messages between networks |
US8144587B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for load balancing network resources using a connection admission control engine |
US8238253B2 (en) | 2006-08-22 | 2012-08-07 | Embarq Holdings Company, Llc | System and method for monitoring interlayer devices and optimizing network performance |
US9479341B2 (en) | 2006-08-22 | 2016-10-25 | Centurylink Intellectual Property Llc | System and method for initiating diagnostics on a packet network node |
US8015294B2 (en) | 2006-08-22 | 2011-09-06 | Embarq Holdings Company, LP | Pin-hole firewall for communicating data packets on a packet network |
US7684332B2 (en) | 2006-08-22 | 2010-03-23 | Embarq Holdings Company, Llc | System and method for adjusting the window size of a TCP packet through network elements |
US8199653B2 (en) | 2006-08-22 | 2012-06-12 | Embarq Holdings Company, Llc | System and method for communicating network performance information over a packet network |
US8457630B2 (en) * | 2006-08-25 | 2013-06-04 | Research In Motion Limited | System and method for transferring a device between mobile carriers |
US20090024614A1 (en) * | 2006-09-06 | 2009-01-22 | Sms.Ac | Systems and methods for online content searching |
US8036979B1 (en) | 2006-10-05 | 2011-10-11 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
US8073117B2 (en) * | 2006-11-10 | 2011-12-06 | At&T Intellectual Property I, L.P. | Rating communications and special communities |
US20100017884A1 (en) * | 2006-11-13 | 2010-01-21 | M-Biz Global Company Limited | Method for allowing full version content embedded in mobile device and system thereof |
US8285656B1 (en) | 2007-03-30 | 2012-10-09 | Consumerinfo.Com, Inc. | Systems and methods for data verification |
US20080294540A1 (en) | 2007-05-25 | 2008-11-27 | Celka Christopher J | System and method for automated detection of never-pay data sets |
WO2008148180A1 (en) * | 2007-06-04 | 2008-12-11 | Bce Inc. | Methods and systems for validating online transactions using location information |
GB2450193A (en) * | 2007-06-12 | 2008-12-17 | Cvon Innovations Ltd | Method and system for managing credits via a mobile device |
US8768778B2 (en) | 2007-06-29 | 2014-07-01 | Boku, Inc. | Effecting an electronic payment |
US20090320050A1 (en) * | 2007-08-17 | 2009-12-24 | Sms.Ac | Mobile Network Community Platform Desktop API |
US20090063178A1 (en) * | 2007-08-17 | 2009-03-05 | Sms.Ac | Systems and methods for a mobile, community-based user interface |
US8301500B2 (en) * | 2008-04-02 | 2012-10-30 | Global 1 Enterprises | Ghosting payment account data in a mobile telephone payment transaction system |
US8068425B2 (en) | 2008-04-09 | 2011-11-29 | Embarq Holdings Company, Llc | System and method for using network performance information to determine improved measures of path states |
GB0809382D0 (en) * | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Funds transfer electronically |
GB0809381D0 (en) * | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Funds transfer electronically |
EP2300978A4 (en) * | 2008-05-23 | 2011-08-10 | Boku | Supplier funds reception electronically |
GB0809386D0 (en) * | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Transferring funds electronically |
GB0809383D0 (en) | 2008-05-23 | 2008-07-02 | Vidicom Ltd | Customer to supplier funds transfer |
US8312033B1 (en) | 2008-06-26 | 2012-11-13 | Experian Marketing Solutions, Inc. | Systems and methods for providing an integrated identifier |
WO2010039101A1 (en) * | 2008-09-30 | 2010-04-08 | Network For Electronic Transfers (Singapore) Pte Ltd | Mobile payments |
US9652761B2 (en) | 2009-01-23 | 2017-05-16 | Boku, Inc. | Systems and methods to facilitate electronic payments |
US8041639B2 (en) * | 2009-01-23 | 2011-10-18 | Vidicom Limited | Systems and methods to facilitate online transactions |
US8116730B2 (en) * | 2009-01-23 | 2012-02-14 | Vidicom Limited | Systems and methods to control online transactions |
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 |
US9164700B2 (en) * | 2009-03-05 | 2015-10-20 | Sandisk Il Ltd | System for optimizing the transfer of stored content in response to a triggering event |
US8700530B2 (en) | 2009-03-10 | 2014-04-15 | Boku, Inc. | Systems and methods to process user initiated transactions |
US8160943B2 (en) * | 2009-03-27 | 2012-04-17 | Boku, Inc. | Systems and methods to process transactions based on social networking |
US8224727B2 (en) * | 2009-05-27 | 2012-07-17 | Boku, Inc. | Systems and methods to process transactions based on social networking |
US20100262506A1 (en) * | 2009-04-08 | 2010-10-14 | Microsoft Corporation | Mobile content delivery on a mobile network |
US8131258B2 (en) | 2009-04-20 | 2012-03-06 | Boku, Inc. | Systems and methods to process transaction requests |
WO2010132492A2 (en) | 2009-05-11 | 2010-11-18 | Experian Marketing Solutions, Inc. | Systems and methods for providing anonymized user profile data |
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 |
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 |
US8355987B2 (en) | 2010-05-06 | 2013-01-15 | Boku, Inc. | Systems and methods to manage information |
WO2012021716A2 (en) | 2010-08-11 | 2012-02-16 | Boku, Inc. | Systems and methods to identify carrier information for transmission of premium messages |
US9152727B1 (en) | 2010-08-23 | 2015-10-06 | Experian Marketing Solutions, Inc. | Systems and methods for processing consumer information for targeted marketing applications |
US9147042B1 (en) | 2010-11-22 | 2015-09-29 | Experian Information Solutions, Inc. | Systems and methods for data verification |
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 |
CA2828107C (en) * | 2011-02-25 | 2015-09-08 | Store Financial Services, Llc | Method and system for activation and funding of prepaid card accounts within a restricted authorization network |
WO2012148842A1 (en) | 2011-04-26 | 2012-11-01 | 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 |
WO2012151325A1 (en) * | 2011-05-05 | 2012-11-08 | Boku, Inc. | Systems and methods to suggest prices |
EP2767110A4 (en) | 2011-10-12 | 2015-01-28 | C Sam Inc | A multi-tiered secure mobile transactions enabling platform |
KR101844304B1 (en) * | 2011-12-06 | 2018-05-15 | 삼성전자주식회사 | Method based on ims mobile communication system for sponsored service |
US20140156528A1 (en) * | 2012-11-30 | 2014-06-05 | Stephen Frechette | Method and system for secure mobile payment of a vendor or service provider via a demand draft |
US9697263B1 (en) | 2013-03-04 | 2017-07-04 | Experian Information Solutions, Inc. | Consumer data request fulfillment system |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US10102536B1 (en) | 2013-11-15 | 2018-10-16 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US9529851B1 (en) | 2013-12-02 | 2016-12-27 | Experian Information Solutions, Inc. | Server architecture for electronic data quality processing |
US10262362B1 (en) | 2014-02-14 | 2019-04-16 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
US9576030B1 (en) | 2014-05-07 | 2017-02-21 | Consumerinfo.Com, Inc. | Keeping up with the joneses |
US11257117B1 (en) | 2014-06-25 | 2022-02-22 | Experian Information Solutions, Inc. | Mobile device sighting location analytics and profiling system |
WO2016061077A1 (en) * | 2014-10-13 | 2016-04-21 | Mastercard International Incorporated | Method and system for direct carrier billing |
US10242019B1 (en) | 2014-12-19 | 2019-03-26 | Experian Information Solutions, Inc. | User behavior segmentation using latent topic detection |
US9767309B1 (en) | 2015-11-23 | 2017-09-19 | Experian Information Solutions, Inc. | Access control system for implementing access restrictions of regulated database records while identifying and providing indicators of regulated database records matching validation criteria |
WO2018039377A1 (en) | 2016-08-24 | 2018-03-01 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
US10164977B2 (en) * | 2016-11-17 | 2018-12-25 | Avaya Inc. | Mobile caller authentication for contact centers |
WO2018144612A1 (en) | 2017-01-31 | 2018-08-09 | Experian Information Solutions, Inc. | Massive scale heterogeneous data ingestion and user resolution |
US10511454B2 (en) * | 2017-03-09 | 2019-12-17 | Facebook, Inc. | Methods and systems for implementing differential pricing configurations |
US10769618B2 (en) | 2018-07-10 | 2020-09-08 | Capital One Services, Llc | Systems and methods for temporarily activating a payment account for fraud prevention |
US20200074541A1 (en) | 2018-09-05 | 2020-03-05 | Consumerinfo.Com, Inc. | Generation of data structures based on categories of matched data items |
US10963434B1 (en) | 2018-09-07 | 2021-03-30 | Experian Information Solutions, Inc. | Data architecture for supporting multiple search models |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
US11682041B1 (en) | 2020-01-13 | 2023-06-20 | Experian Marketing Solutions, Llc | Systems and methods of a tracking analytics platform |
US11880377B1 (en) | 2021-03-26 | 2024-01-23 | Experian Information Solutions, Inc. | Systems and methods for entity resolution |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060253335A1 (en) * | 2003-01-22 | 2006-11-09 | Gerard Keena | Cash based purchasing using mobile communication |
US20060276171A1 (en) * | 2005-06-06 | 2006-12-07 | Sms.Ac, Inc. | Billing system and method for micro-transactions |
US20070067297A1 (en) * | 2004-04-30 | 2007-03-22 | Kublickis Peter J | System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users |
US7440922B1 (en) * | 2001-05-04 | 2008-10-21 | West Corporation | System, method, and business method for settling micropayment transactions to a pre-paid instrument |
US7512548B1 (en) * | 1997-06-27 | 2009-03-31 | Amazon.Com, Inc. | Use of shopping cart to collect and purchase items selected from multiple web sites |
US7778890B1 (en) * | 1999-11-19 | 2010-08-17 | Amazon Technologies, Inc. | Methods and systems for distributing information within a dynamically defined community |
Family Cites Families (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0736203A1 (en) * | 1993-12-23 | 1996-10-09 | Diacom Technologies, Inc. | Method and apparatus for implementing user feedback |
US7120606B1 (en) * | 2000-02-10 | 2006-10-10 | Jove Corporation | System and method for secure electronic fund transfers |
US7725385B2 (en) * | 2000-03-29 | 2010-05-25 | American Express Travel Related Services Company, Inc. | System and method for facilitating the handling of a dispute using disparate architectures |
US8046256B2 (en) * | 2000-04-14 | 2011-10-25 | American Express Travel Related Services Company, Inc. | System and method for using loyalty rewards as currency |
US6957199B1 (en) * | 2000-08-30 | 2005-10-18 | Douglas Fisher | Method, system and service for conducting authenticated business transactions |
JPWO2002021266A1 (en) * | 2000-09-07 | 2004-01-15 | テックファーム株式会社 | Information distribution server system, information distribution method, and recording medium |
FR2815745B1 (en) * | 2000-10-25 | 2003-01-10 | Cedric Remy | SECURE TELEMATICS PAYMENT METHOD |
US20020107706A1 (en) * | 2001-02-02 | 2002-08-08 | Oliver Mitchell B. | Virtual negotiation |
US20020143634A1 (en) * | 2001-03-30 | 2002-10-03 | Kumar K. Anand | Wireless payment system |
US20020194126A1 (en) * | 2001-04-30 | 2002-12-19 | Randell Wayne L. | Method and system for handling invoices |
US20020198830A1 (en) * | 2001-05-01 | 2002-12-26 | Randell Wayne L. | Method and system for handling disputes in an electronic invoice management system |
US7017162B2 (en) * | 2001-07-10 | 2006-03-21 | Microsoft Corporation | Application program interface for network software platform |
SE0200490L (en) * | 2002-02-19 | 2003-08-20 | Tds Todos Data System Ab | Electronic micro payment system |
US7707120B2 (en) * | 2002-04-17 | 2010-04-27 | Visa International Service Association | Mobile account authentication service |
US7283981B2 (en) * | 2002-04-30 | 2007-10-16 | Deluxe Corporation | Browser-based system for ordering financial products |
US20040043753A1 (en) * | 2002-08-30 | 2004-03-04 | Wake Susan L. | System and method for third party application sales and services to wireless devices |
JP4217455B2 (en) * | 2002-10-15 | 2009-02-04 | キヤノン株式会社 | Peripheral device, information processing method, and control program |
US9232077B2 (en) * | 2003-03-12 | 2016-01-05 | Qualcomm Incorporated | Automatic subscription system for applications and services provided to wireless devices |
BRPI0409120A (en) * | 2003-04-09 | 2006-03-28 | Gtech Corp | methods for increasing credit on one account, processing transactions and facilitating credit transactions, system for facilitating credit transactions, method for transferring credit between multiple accounts, mobile device, system for facilitating wireless transactions, and method for facilitating non-credit transactions. wires to a lottery account |
US8352360B2 (en) * | 2003-06-30 | 2013-01-08 | Toshiba Global Commerce Solutions Holdings Corporation | Method and system for secured transactions over a wireless network |
US7870199B2 (en) * | 2003-10-06 | 2011-01-11 | Aol Inc. | System and method for seamlessly bringing external services into instant messaging session |
US20050289047A1 (en) * | 2004-06-28 | 2005-12-29 | Oliver Mitchell B | Virtual marketplace for wireless device applications and services with integrated multi-party settlement |
US8027918B2 (en) * | 2004-08-30 | 2011-09-27 | Google Inc. | Micro-payment system architecture |
US20070288370A1 (en) * | 2004-11-12 | 2007-12-13 | Konja Dolor J | Proprietary point of purchase resource system |
JP4590282B2 (en) * | 2005-02-24 | 2010-12-01 | キヤノン株式会社 | License management apparatus, control method, and program |
US20060258397A1 (en) * | 2005-05-10 | 2006-11-16 | Kaplan Mark M | Integrated mobile application server and communication gateway |
US7283816B2 (en) * | 2005-04-14 | 2007-10-16 | Qualcomm Incorporated | Apparatus and process for a universal diagnostic monitor module on a wireless device |
US8996423B2 (en) * | 2005-04-19 | 2015-03-31 | Microsoft Corporation | Authentication for a commercial transaction using a mobile module |
US20070255653A1 (en) * | 2006-03-30 | 2007-11-01 | Obopay Inc. | Mobile Person-to-Person Payment System |
US20070244811A1 (en) * | 2006-03-30 | 2007-10-18 | Obopay Inc. | Mobile Client Application for Mobile Payments |
-
2006
- 2006-06-06 CA CA002610216A patent/CA2610216A1/en not_active Abandoned
- 2006-06-06 AU AU2006255078A patent/AU2006255078A1/en not_active Abandoned
- 2006-06-06 US US11/446,973 patent/US8073774B2/en not_active Expired - Fee Related
- 2006-06-06 WO PCT/US2006/021836 patent/WO2006133141A2/en active Application Filing
- 2006-06-06 EP EP06772228A patent/EP1902414A2/en not_active Withdrawn
-
2011
- 2011-12-06 US US13/312,944 patent/US20120143737A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7512548B1 (en) * | 1997-06-27 | 2009-03-31 | Amazon.Com, Inc. | Use of shopping cart to collect and purchase items selected from multiple web sites |
US7778890B1 (en) * | 1999-11-19 | 2010-08-17 | Amazon Technologies, Inc. | Methods and systems for distributing information within a dynamically defined community |
US7440922B1 (en) * | 2001-05-04 | 2008-10-21 | West Corporation | System, method, and business method for settling micropayment transactions to a pre-paid instrument |
US20060253335A1 (en) * | 2003-01-22 | 2006-11-09 | Gerard Keena | Cash based purchasing using mobile communication |
US20070067297A1 (en) * | 2004-04-30 | 2007-03-22 | Kublickis Peter J | System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users |
US20060276171A1 (en) * | 2005-06-06 | 2006-12-07 | Sms.Ac, Inc. | Billing system and method for micro-transactions |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10762505B1 (en) | 2016-06-13 | 2020-09-01 | Wells Fargo Bank, N.A. | Authentication transaction |
US11694203B1 (en) | 2016-06-13 | 2023-07-04 | Wells Fargo Bank, N.A. | Authentication transaction |
CN107104806A (en) * | 2017-04-13 | 2017-08-29 | 中国联合网络通信集团有限公司 | Call bill processing method, apparatus and system |
Also Published As
Publication number | Publication date |
---|---|
US8073774B2 (en) | 2011-12-06 |
WO2006133141A3 (en) | 2007-10-11 |
EP1902414A2 (en) | 2008-03-26 |
WO2006133141A2 (en) | 2006-12-14 |
CA2610216A1 (en) | 2006-12-14 |
AU2006255078A1 (en) | 2006-12-14 |
US20060276171A1 (en) | 2006-12-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8073774B2 (en) | Billing system and method for micro-transactions | |
US20070260556A1 (en) | System and method for verification of identity for transactions | |
US7826829B2 (en) | Automated billing and distribution platform for application providers | |
US7848736B2 (en) | Package billing for micro-transactions | |
US7860484B2 (en) | Automated billing and distribution platform for application providers | |
US8606247B2 (en) | Systems and methods for billing for a network enabled application through a network platform regardless of whether the network enabled application is hosted by the platform | |
US20120296823A1 (en) | Content owner verification and digital rights management for automated distribution and billing platforms | |
US20090106119A1 (en) | System and method for online commerce | |
US20110092184A1 (en) | Systems and methods for automatic generation, registration and mobile phone billing of a pod using third party web page content | |
JP2001512872A (en) | How to Retail on a Wide Area Network | |
MXPA04010350A (en) | Payment system and method. | |
WO2007084593A2 (en) | Package billing for micro-transactions | |
JP2004164598A (en) | Methods for maintaining prepaid account information and for supporting transactions in an e-commerce system | |
US9483783B1 (en) | Purchase system using a computing device | |
WO2008051982A2 (en) | Content owner verification and digital rights management for automated distribution and billing platforms | |
WO2008036685A2 (en) | Billing for network enabled application through a network platform | |
KR20080022259A (en) | System for lending(or receipt of money in advance) and program recording medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |