WO2001071633A2 - Procedes et systemes de gestion de transactions - Google Patents

Procedes et systemes de gestion de transactions Download PDF

Info

Publication number
WO2001071633A2
WO2001071633A2 PCT/US2001/009452 US0109452W WO0171633A2 WO 2001071633 A2 WO2001071633 A2 WO 2001071633A2 US 0109452 W US0109452 W US 0109452W WO 0171633 A2 WO0171633 A2 WO 0171633A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
transaction
aural
communication
accepting
Prior art date
Application number
PCT/US2001/009452
Other languages
English (en)
Other versions
WO2001071633A8 (fr
Inventor
Roni Koren
Original Assignee
Codial Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Codial Inc. filed Critical Codial Inc.
Priority to IL15187601A priority Critical patent/IL151876A0/xx
Priority to EP01922640A priority patent/EP1269380A2/fr
Priority to NZ521530A priority patent/NZ521530A/en
Priority to CA002404142A priority patent/CA2404142A1/fr
Priority to AU2001249418A priority patent/AU2001249418A1/en
Publication of WO2001071633A2 publication Critical patent/WO2001071633A2/fr
Publication of WO2001071633A8 publication Critical patent/WO2001071633A8/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • 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
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • the present invention relates to electronic transaction processing systems and methods and particularly to systems and methods for executing transaction orders using a telephone or other communications terminals.
  • Print or displayed matter may continue to be used as a method of communication among businesses and users. These media may be likely to continue to be used by users who do not have computer or Internet access, users who do not have sufficient knowledge of computers and the Internet, and also by users who have access to and experience in computers and the Internet .
  • executing a transaction using a computer network is not optimal or non-applicable to the situation involved or to the user involved.
  • a user will have move to the location of a computer, power the computer to turn the computer on, implement browser software, enter an address for a Web site, etc.
  • Executing transactions e.g., buying a product or paying a bill
  • printed or displayed media content e.g., a magazine advertisement
  • One known method that is commonly used involves a user making a telephone call to a telephone number and talking to a human agent. The conversation includes the user giving the agent his or her information (e.g., name, credit card number, mailing address, etc.) and the desired transaction information (e.g., the magazine advertisement details, the desired product, the advertised price, etc.).
  • a human-agent-operated service involves high cost for the operating business in providing salaries for the agents, providing office space, and paying high telephone bills.
  • the security of an executed transaction may be problematic because a stolen or lost credit card can be used by an impostor for performing the transaction. Furthermore, in such situations the impostor may ask that the goods be sent to any address causing an irreversible financial damage to the vendor and/or to the credit card company.
  • potential customers can be reluctant to use this method because customers may not want to give private information such as name and credit card number over the telephone because of security reasons . This reluctance may be especially true when a user is performing a transaction over a cellular telephone, or at a public telephone.
  • Some potential customers may not finish executing a transaction using the above method because it may not be quick enough for the customer. Customers may not finish the transaction due to busy telephone lines, the relatively long durations of conversations with a human agent, etc.
  • the number of simultaneous transactions a vendor using a human-operated call center can handle using the above method is limited by the number of agents and by the relatively long duration of human telephone conversations between agents and users.
  • Another existing method for executing similar transactions involves using voice menu systems that guide the user through voice menus to enter his or her information (e.g., name, credit card number, etc.) and to specify the desired transaction (e.g., product, price, etc.) using additional voice menus.
  • This method is deficient in that the user is burdened to dial many different numbers (for example, a 16 digit credit card number may have to be entered) and the user may be burdened to go through many different voice menus in order to define and execute the desired transaction.
  • These burdens may deter potential users from using this method. Some users may start a transaction, but may abort the process before completing the transaction because of the burdens described.
  • SMS Short Messaging Service
  • a transaction handling system and method are provided that handle transactions quickly.
  • the transaction handling system is adapted to receive simple instructions (e.g., a communication comprising instructions) from users and to quickly complete transactions based on the instructions.
  • the transaction handling system may register available transactions and assign a transaction code to each available registered transaction. Registration may include recording vendor information, product information, pricing information, information for receiving bill payments, etc. A particular available transaction and assigned transaction code may be publicized to inform users of the availability of the transaction on the system. In some embodiments, the transaction code may contain fewer than ten characters.
  • Users may be registered and may be assigned an identification code or number. Registration may involve recording one or more communications addresses from which the user may access the system, recording billing information of a user, recording shipping information of a user, etc. If desired, unique identification codes may be assigned to allow the system to identify the user and the user's account based on the identification code. In some embodiments, the identification code may not be a unique code in the system. In such situation, an identification code may be used in combination with other parameters to identify the user and the user's account. Other parameters may include the user's Social Security number, the user's telephone numbers, etc. Other parameters may also include voice recognition, the recognition of a spoken word, the determination that user access is from a communications address that the user registered with the system, etc. Combinations of such parameters may also be used.
  • the identification code may be a personal identification code (e.g., a code that is personal to the registered user) .
  • An identification code may be assigned to a user by the system when the user registers with the system.
  • the user may be permitted to select a desired identification code and the system may assign the desired identification code to the user.
  • a user may initially be assigned a provisional identification code to be able to initially access the system.
  • the provisional identification code may be replaced with a permanent identification code when a user selects a desired identification code and the system assigns an identification code to the user based on the desired identification code (e.g., assigns the desired identification code to the user as the user's permanent identification code) .
  • the system may include precautions that may prohibit users from selecting certain codes that are commonly used (e.g., the code "1111" may be prohibited) .
  • the transaction handling system may accept a communication comprising the transaction code and the identification code sent by a user to pursue a transaction. Acceptance may involve identifying that the user is a legitimate user of the system by checking the database of registration information. The system may identify the user and the user's account based on the identification code. Other parameters may also be used individually, in combination with the identification codes, or in any suitable combination to identify a user. If desired, the system may determine the communications address from which the communication was sent to compare that address to the registration information of users. The system may use a detected address and an identification code to identify the user and the user's account. The system may confirm that the user desires that particular transaction by for example, prompting the user to select a number (e.g., dial "1") .
  • a number e.g., dial "1"
  • the system may allow the user to simply hang up or disconnect .
  • the system may arrange for the transaction to be completed when the communication is accepted.
  • the system may communicate with a vendor, a financial institution facility, or both to arrange a transaction to be completed.
  • the system may communicate with the vendor or financial institution using any suitable form of communication such as electronic communications, paper communications, voice communications, etc.
  • Communications with vendors may comprise sufficient information to allow the vendor to execute the transaction (e.g., allow the vendor to identify the goods or services, ship the goods, provide the services, etc.).
  • Communications with financial institutions may comprise sufficient information to allow a financial institution to execute the responsibilities of the financial institution in the transaction (e.g., clear the transaction for completion, transfer payment from a user's account to a vendor's account, etc.).
  • the system may arrange transactions without the system having to communicate with a financial institution.
  • information for executing the responsibilities of a financial institution may be communicated to a vendor and the vendor may forward such information to a financial institution.
  • Information for a financial institution may include information on a user's account (e.g., user's account registered for making payments), user's name, the vendor's account (e.g., vendor's account registered for receiving payments), vendor's name, etc.
  • the system may complete the transaction when the communication is accepted.
  • the system may bill the financial account of the user based on information in the database and may ship or provide the products or services for the transaction based on the shipping information of the user.
  • the system may also be a system that the vendor is providing to customers to allow the vendor's goods or services to be available to customers (e.g., directly available from a vendor).
  • the user may be permitted to register transactions that are available from the user. Available transactions from the user may each be assigned a transaction code.
  • the system may allow a registered user to request to complete a registered transaction on the system and allow a registered user to register transactions that are available from the user.
  • a vendor may register with the system. Once a vendor is registered, the registered vendor may complete transactions that are requested by registered users and may request to complete registered transactions on the system that are available from the system. To allow a vendor, to request registered transaction, information that is substantially the same that is information that is recorded for the users who seek to use the system may be recorded.
  • the system may comprise a plurality of functional blocks for handling transactions (e.g., automatically handling transactions) .
  • the system may comprise a registration processor for assigning codes and registering transactions and users, a transaction processor for accepting communications that order transactions and for arranging the completion of transactions.
  • the system may further comprise any or all of a user communications interface, a vendor communications interface, a communications utility handler, a database, a voice analyzer, a financial institution communications interface, a user locator, etc .
  • the system may be provided on a number of platforms such as a personal computer, a workstation, a server, a portable computer, etc.
  • the transaction handling system and method may enable quick and easy generation of transaction orders from practically any type of user terminal such as a telephone (cellular, landline, DTMF, etc.), computers, PDA, etc. Transactions may be requested using user terminals when a user is reading or watching a display such as printed or displayed matter on newspapers, magazines, public signs, TV screens or other visual presentations.
  • the printed or displayed matter may include dedicated transaction codes, each code defining a specific transaction that may be executed.
  • transaction codes that each define a specific transaction have to be made available on printed or displayed matter to allow user to be informed of the availability of transactions.
  • a user may input a communications address for accessing the system (e.g., a telephone access number) and enter a specific-transaction code and a personal identi ication code or personal identification number (PIN) to request the transaction.
  • a communications address for accessing the system
  • PIN personal identification number
  • a user may efficiently and rapidly obtain execution of a specific transaction order with no need for human agent interaction and no need for the user to select from tedious menus or enter many keystrokes on a telephone or keyboard.
  • the user input of an access number, a specific-transaction code and a PIN, as well as any other input may be entered by keying, dialing, scanning, recognizing a user's voice or by another suitable data entry method.
  • a user may be required to register to be eligible to use such transaction handling systems and methods.
  • the process may start with a user reading a printed matter (for example, a user may be reading a magazine advertising a specific product) .
  • the user may enter the system by dialing an access number, which may be included on the printed matter.
  • An advantage of this system using telephonic communications is that a user reading printed media may order a transaction simply by reaching for a telephone. This alleviates the user from the cumbersome procedures that may be involved in using a computer to execute transactions (e.g., move to the location of a computer, turn on computer, etc.) .
  • the user is connected to the transaction handling system, which may also be sometimes referred to as a transaction code handling system.
  • the system may then prompt the user to enter (e.g., dial) the desired transaction code appearing on the printed or displayed matter and be prompted to enter (e.g., dial) his PIN.
  • the user may be required to use a data entry key such as a particular key of a telephone (e.g., "#" key) to indicate to the system that the user has completed entering a code or PIN.
  • the transaction code and corresponding transaction (for example, code 246 for buying the advertised product for a certain price) may be provided in the printed or displayed matter.
  • the system hardware and software may identify the user by the caller identification ("Caller ID” or automatic number identification "ANI”) of the telephone number that he called from (which is stored in the system's database when the users registers with the service) and by his pre-assigned PIN.
  • Caller ID or automatic number identification "ANI”
  • ANI automatic number identification
  • a user may be required to enter additional information such as the user's home telephone number or Social Security number.
  • the system may identify the desired transaction by the dialed transaction code.
  • the system may send the user a voice message or a displayed alphanumeric message depending on the type of user terminal to confirm that the user was identified and that the desired transaction order was identified and will be executed after the user's approval or confirmation (e.g., by dialing 1 for example) .
  • the user By approving or confirming the order, the user initiates the execution of the transaction order.
  • the system may generate a specific transaction order that may include the user's details, the vendor's details and the transaction details.
  • the specific transaction order may be sent by the system (via the Internet or via another communications system or by mail) to the vendor of the goods or service (for example, a product retailer) who may also be registered with the system.
  • the specific transaction order may be a document that is sent on paper or electronic media to an appropriate vendor. If desired, the order may also be sent to a financial institution for transferring payment and if desired, the order may be sent to a user to possibly confirm the transaction.
  • the sequence in which the transaction handling process occurs may vary to suit different communications configurations (e.g., in some systems, the user's transaction order comprising a communication may be entered first before connecting or accessing the system) . These variations are all embodiments within the scope of the present invention.
  • the vendor may send the goods or data to the user's registered address that was recorded by the system when the user registered with the system. If desired, there may be more than one shipping address and a user may select one of the addresses for shipping .
  • the system may be compatible with a number of different user terminals, compatible with a number of different communications networks from which a user requests transactions, compatible with a number of different communications protocols in communications networks from which communications are sent, etc.. For example, the system may receive and process a communication from a registered user that uses a cellular telephone in a cellular communications network that uses a cellular communications network and receive and process another communication from another registered user that uses a landline telephone in a public switched telephone network that uses a public switched telephone network communications protocol.
  • the system receive the communications through another communications network in between, or may have a substantially direct connection to each of those communications networks that may each use a different communications protocol .
  • the payment method for transactions for a user may be pre-defined. The payment method may be defined when a user registers to use the system. In one embodiment, payment may be provided using the user's assigned credit card. Information for the transaction may be transferred to the credit card company via the Internet. In other embodiments, dedicated computer networks or some other type of network may be used to transfer payments.
  • payment can be made by other billing systems (e.g., a cellular provider), financial institutions (e.g., the user's bank) or a combination thereof (e.g., small amount transactions are paid through a communications provider and larger transactions through a credit card company) .
  • billing systems e.g., a cellular provider
  • financial institutions e.g., the user's bank
  • a combination thereof e.g., small amount transactions are paid through a communications provider and larger transactions through a credit card company
  • the billing can be done outside of the system using the payment information sent by the user to the vendor.
  • the vendor may then communicate with the financial institution using dedicated methods and systems (e.g., when payment transfer is being conducted external to the transaction handling system) .
  • the system may receive a user's spoken voice that provides a transaction code and user identification code.
  • the system may identify the user based on recognizing the user identification code when a user speaks in a voice communication to communicate with the system to request a transaction (e.g., recognize the identification code using techniques that do not rely on the characteristics of a particular user's voice.
  • a signature e.g., a voice signature
  • a user identification code spoken later may be compared to recorded signatures and a user may be identified based on the comparison.
  • the system may automatically arrange to complete the transaction based on identifying the user to be a legitimate user and based on a transaction code that may have been spoken or entered using key entry.
  • the system may register a voice signature of a user that may comprise a particular word selected by the user at registration. For example, the user may select his or her name.
  • the user may speak that word in a communication with the system.
  • the system may compare the spoken word with registered voice signatures to recognize the user. In some embodiments, the system may use both the user's voice and a spoken word to identify the user.
  • the system may use the recognition of a spoken identification code (e.g., recognition of a spoken identification code irrespective of a particular user is speaking) the recognition of a particular user's voice (e.g., voice signature), or combinations thereof to recognize or identify a user. Special mechanisms may be provided within the system for voice recognition and voice signature.
  • Transaction codes may be re-used in different locations when the system is capable of determining the location from which a user is accessing the system. The location in which a user is located may be determined for example, by using information from a cellular network when the user is using a cellular telephone, by using GPS information, etc. Re-use of the transaction codes will allow for shorter codes to be used in identifying transactions. For example, the system may use the same transaction codes for two different products in two different areas, and may identify which product is being ordered based on determining where the user is located. The above method and system enables quick and easy connection between printed or displayed matter and computer networks .
  • FIG. 1 is a flow chart of illustrative steps involved in making transactions available to user in accordance with the present invention
  • FIG. 2 is a flow chart of illustrative steps involved in completing a transaction in accordance with the present invention
  • FIG. 3 is a flow chart of illustrative steps involved in a transaction from a user's perspective in accordance with the present invention
  • FIG.. 4 is a flow chart of illustrative steps involved in accepting a transaction from a user in accordance with the present invention
  • FIG. 5 is an illustrative block diagram of a telephone transaction handling system in accordance with the present invention.
  • FIG. 6 is a schematic diagram of a paper magazine advertisement containing two specific- transaction codes in accordance with the present invention
  • FIG. 7 is a flow chart of illustrative steps involved in a transaction from a registered user's point of view in accordance with the present invention
  • FIG. 8 is a flow chart of illustrative steps involved in multiple transactions from a registered user ' s point of view in accordance with the present invention.
  • FIG. 9 is a schematic diagram of an example of a paper bill of payment containing a specific transaction-code in accordance with the present invention.
  • FIG. 10 is a schematic diagram of an example of a paper invoice containing two specific-transaction codes in accordance with the present invention
  • FIG. 11 is a flow chart of illustrative steps involved in a transaction process in accordance with the present invention.
  • FIG. 12 is a flow chart of illustrative steps involved in assigning an identification code in accordance with the present invention.
  • FIG. 13 are charts of illustrative structures for a part of database for processing transactions in accordance with the present invention.
  • FIG. 14 is a diagram of an illustrative transaction handling system in accordance with the present invention.
  • FIG. 15 is an illustrative functional block diagram of an illustrative transaction handling system in accordance with the present invention
  • FIG. 16 is a diagram of an illustrative system having hardware and software for handling transactions in accordance with the present invention
  • FIG. 17 is a diagram of illustrative transactions handling system having different user and vendor terminals in accordance with the present invention. Skilled artisans will appreciate that some elements in certain FIGS, are illustrated for simplicity and clarity and have not necessarily been drawn to scale.
  • Vendors and users may interact with a transaction handling system to quickly and efficiently complete transactions. Access to particular transactions may be provided using codes that automate the transaction handling processes.
  • a database of vendor and user information may be used to direct a transaction to an appropriate vendor and to identify users. Acceptance of a transaction • code for a particular transaction and a user identification code for a user may be sufficient to place an order.
  • additional security measures may be used such as using detection techniques to determine whether a user is accessing the system from a telephone number that is known by the system to be related to the user. Other security measures such as user entry of particular information is discussed below. The use of additional security measures may allow the system to assign user identification codes that are short and easy to remember.
  • the transaction code and the identifica ion code may be sent using simple key-entry. Users may be informed of available transactions by publicizing registered transactions.
  • a transaction handling system may register a transaction that is to be made available to users. Registration may involve recording transaction information such as vendor name, product, service, vendor address, accepted forms of payment, etc.
  • the system may assign a transaction code to the registered transaction.
  • the transaction code may be a numeric code that is uniquely assigned by the system for that particular transaction.
  • the transaction and the transaction code may be publicized to inform users of the availability of that transaction in the transaction handling system.
  • the system may publicize the transaction code and the transaction together on a publicly viewable display (e.g., billboards, magazine, newspapers, etc.).
  • a publicly viewable display e.g., billboards, magazine, newspapers, etc.
  • the transaction code and the transaction may be displayed in a way that allows users to recognize that the two are related. Additional examples and techniques for registering, assigning a transaction code, and publicizing are illustratively described below.
  • a registered transaction may be completed by a user that is registered to use the system.
  • the transaction handling system may register a user who desires to make transactions on the system. Registering a user may involve recording user information such as name, shipping address, billing information, communications addresses, etc.
  • the system may assign a user identification code to the registered user. If desired, an identification code may be uniquely assigned to identify the user.
  • a user may select a code that the system may receive and assign to the user. Initially, the system may assign a user a provisional or temporary identification code that may later be changed with the assistance of the user.
  • the identification code may be a personal identification number or may comprise alphanumeric characters.
  • the transaction handling system may accept a communication comprising a transaction code for a particular transaction and an identification code.
  • the transaction handling system may arrange to complete that particular transaction when the transaction code and the user identification code have been accepted.
  • the completion of the transaction may be arranged automatically in response to the acceptance of the transaction code and the user identification code.
  • Arranging the transaction may involve communicating with a vendor, a financial institution, or both to arrange a transaction to be completed.
  • the system may communicate with the vendor or financial institution using any suitable form of communication such as electronic communications, paper communications, voice communications, etc.
  • Communications with vendors may comprise sufficient information to allow the vendor to execute the transaction (e.g., allow the vendor to identify the goods or services, ship the goods, provide the services, etc.).
  • Communications with financial institutions may comprise sufficient information to allow a financial institution to execute the responsibilities of the financial institution in the transaction (e.g., clear the transaction for completion, transfer payment from a user's account to a vendor's account, etc.) .
  • the system may arrange transactions without the system having to communicate with a financial institution. For example, information for executing the responsibilities of a financial institution may be communicated to a vendor and the vendor may forward such information to a financial institution.
  • Information for a financial institution may include information on a user's account (e.g., user's account registered for making payments), user's name, the vendor's account (e.g., vendor's account registered for receiving payments), vendor's name, etc.
  • transactions may be completed. Completing the transaction may involve billing the user, shipping a product to the user, providing a commercial service to the user, etc. If desired, in some embodiments, the system will complete the transaction by for example, billing users, transferring payments, shipping products, providing services, etc.
  • a transaction handling system may operate to interact with individual users in providing transactions to users. With reference now to FIG. 3, at step 22, the transaction handling system may interact with a user to register a user to make transactions on the system. At step 24, a registered user may receive a user identification code from the transaction handling system. At step 26, a publicized transaction and transaction code may be viewed by a user.
  • a user may send a communication to the transaction handling system that comprises the transaction code and the identification code.
  • the communication may be telephonic.
  • the communication may be an aural communication (e.g., spoken voice, DTMF, touch tone, etc.) .
  • the communication may be an aural communication that is sent to be received through a public switched telephone network by the system.
  • the communication may be a communication that is from a plurality of communications networks that may use different communications protocols and/or different user terminal platforms.
  • the identification code and the transaction code may be entered by the user to be sent to the transaction handling system using key entry on a telephone or on some other user terminal (e.g., a personal digital assistant, a computer, a pager, etc.).
  • the user terminal may simply include a way of allowing the user to enter the transaction code and the identification code one communication transmission to the transaction handling system (e.g., DTMF signals be used to enter an identification code and a transaction code as one number) .
  • the user may receive the benefit of the transaction.
  • a user may receive a product, a service, etc.
  • a transaction may involve providing (e.g., transferring) goods or services between a vendor and a user for a predefined price.
  • a transaction may sometimes involve transferring the payment between the user and the vendor (e.g., transferring payment from the user's registered account on the system to the vendor's register account by a financial institution) .
  • Commercial transactions may also have an assigned price of $0.00.
  • Such transactions may be transactions (e.g., providing a catalog may be priced at $0.00) that are in pursuit of a future commercial transaction that involves a price that is greater than $0.00. Additional examples or techniques for interacting with a user are illustratively described below.
  • the transaction handling system may receive a communication comprising a transaction code and a user identification code of a user.
  • the communication may have been received through a public switched telephone network.
  • the communication may be from a wireless communications network (e.g., a wireless communications network that uses protocols such as TDMA, GSM, CDMA, etc.), a landline communications networks (e.g., a public switched telephone network, a private branch exchange), etc.
  • the communication may be a sequence of dual-tone/multi-frequency entries ("DTMF" entries), a public switched telephone network communication, , an analog communication, a digital communication, aural communication, etc.
  • the communication may be received by the transaction handling system on a shared or direct line with the user terminal of the user.
  • the transaction handling system may detect a communications address from which the communication was sent. For example, the transaction handling system may determine the telephone number from which a telephonic communication was sent. Other communications addresses such as a computer network address may also be determined. Techniques for detecting communications addresses are known to those skilled in the art (e.g., caller identification techniques such as Caller ID and ANI) .
  • the transaction handling system may identify a user account. The system may compare the sending communications address to a database containing information on the communications addresses of registered users. The communications addresses may have been recorded in the database when the user registered with the system. The transaction handling system may determine whether the user identification code matches the registered account having the sending communications address.
  • step 34 may be omitted and the user account may be identified based on the user identification code that is in the communication. Other criteria such as those that are discussed herein may also be used to identify a user account.
  • the transaction handling system may confirm that the user desires to complete the transaction. The user may be prompted to confirm the transaction. For example, in telephonic communications, the transaction handling system may prompt the user to confirm the transaction and if desired, provide the specifics of the transaction to the user. As described in connection with FIG. 5, the system may be a system that has sufficient hardware and/or software to automatically accept a communication (e.g., the system may have automated to receive a communication comprising a personal identification code and transaction code) . Additional examples of or techniques for receiving a communication, detecting a communication, identifying a user account, and confirming the transaction are illustratively described below.
  • FIG. 5 illustrates a block diagram of one telephonic embodiment of the present invention method and system.
  • Users 104A-104N and 108A-108N may be users who are reading printed matter 102A-102N and 106A-106N. The printed matter may contain specific-transaction codes.
  • Users 104A-104N may use landline telephone terminals. These telephone terminals can be of any commercially available tone-dial type (e.g., DTMF telephones) , with or without alphanumeric displays and with or without scanning devices.
  • Users 108A-108N may use wireless communications terminals of any commercial type with an interface to the public telephone network, with or without alphanumeric displays and with or without scanning devices.
  • the wireless communications devices can be devices such as cellular telephones of any commercially available type or wireless PDA (Personal Digital Assistants) .
  • Each one of users 104A- 104N may have a user terminal that is in a different communications network and may each operate based on different communications protocols (e.g., landline communications protocols, wireless communications protocols, etc.).
  • One or more transaction-code handling systems e.g., one or more transaction-code handling systems
  • telephone network 110 may be a public switched telephone network through which systems 112 receive a communication for ordering transactions from users or may be some other type of communications network.
  • systems 112 may contain an intelligent network, a computer network server computer, and dedicated software. Examples of hardware, software, and end functional system blocks of systems 112 are illustratively described in connection with FIGS. 14-16.
  • Transaction-code handling systems 112 may also be connected to vendor client-computers 114A-114N via communication link 118.
  • Communication link 118 refers to any type of wire or wireless link between computers such as communication links in LANs, WANs or a combination of computer networks.
  • communications link 118 can be a network such as the Internet.
  • a vendor client computer 114 can be any type of computing device (e.g., a personal computer, server, dedicated application computer, etc.) with an interface to communications link 118.
  • One or more credit card companies and/or other financial institutions such as banks may have client computers 116 that may also be connected to communications link 118 for possible data exchange with transaction-code ordering systems 112.
  • paper magazine advertisement 90 contains two specific-transaction codes 92 and 94. At the bottom of advertisement 90 the following note is printed: "CODIAL 1-200-9876543 & 246 TO BUY NOW FOR ONLY $49.99"
  • the term “Codial” indicates to the users that the following numbers, when dialed, will be used to generate a transaction order.
  • the 1-200-9876-543 is the access number a user has to dial to enter a transaction code or to enter an address in the system for the product vendor (California Watches Inc.).
  • Transaction code 92 that includes the number "246" may correspond to a specific transaction order for buying the advertised watch for $49.99. Users may be aware of this advertising format and may know that the specific-transaction code will follow the "&" sign after the access number.
  • the format for the access number and specific- transaction codes including can vary and may not necessarily be identical to the ones shown herein.
  • the code may include digits to specify the number of identical items to be ordered.
  • the access number may include digits, letters, or combinations thereof to enable long-distance and/or international transactions.
  • the format for presenting the access number and specific-transaction code can be of various forms and may not necessarily be limited to the ones shown herein. However, typically, each specific-transaction may be represented by a combination of an access number and a specific-transaction code and is sufficiently defined in the printed or displayed matter to have one code combination represent one defined transaction. Since the transaction is defined by the access number and specific-transaction code, the user does not need to ask questions or to go through tedious menus. Moreover, the automatic identification of users such as those described herein generates transactions that are very efficient and comfortable for users.
  • FIG. 7 is a flow chart illustration of an illustrative transaction process from a registered user's point of view in a telephonic embodiment of the present invention.
  • the transaction process begins in this illustration with a user who reads an advertisement printed in a magazine (such as for example, FIG. 6) .
  • the user may have previously been instructed on how to use the transaction handling system.
  • the user may have previously entered into an agreement to become a user of the system.
  • the user may want to buy the advertised item (e.g., a watch) and may use his telephone to dial the access number printed on the advertisement.
  • the advertised item e.g., a watch
  • the user is then entered into the transaction code handling system, which prompts him to enter (e.g., using aural communication) the specific-transaction code and his PIN (246-6382 in the example) .
  • Some public telephone switching networks allow longer numbers to be dialed so that the access number and the specific-transaction code and PIN could be dialed all at once (e.g., by dialing 1-200-9876543-246-6382 from the above example all at once) .
  • a registered user may communicate an identification code, a transaction code, or both using a voice communications.
  • Specific pre-registered telephone numbers may be specified by the user at registration for use in transactions on the system.
  • the telephone numbers may be telephone numbers that a user may place telephone calls from, such as, the user's cellular telephone number, home telephone number, office telephone number, etc. These numbers are stored in the transaction code handling system database and may be used in conjunction with the PIN to identify the calling user. If desired, the PIN or user identification code may be uniquely assigned to allow for user identification without additional information. If desired, transactions may also be ordered from telephone numbers that are not pre-registered. In this case the user will have to identify himself by dialing additional identification numbers besides the PIN (for example, his Social Security number or his home telephone number may be entered) .
  • the system may determine whether legitimate data has been entered by the user. If the dialed specific-transaction code and PIN are identified by the system, the system may determine that the entered data is legitimate. The system may identify the registered user and match the dialed symbols for the transaction code with the transaction information in the system's database. At step 208, the user may hear a voice message informing him of his personal information (e.g., name, mailing address, etc.) that were identified by the system and a description of the transaction details as understood by the system (in the above example, buying a watch for $49.99) . The system can also compute shipping and handling fees based on the user's address, the vendor's address, and other predefined parameters.
  • the system can also compute shipping and handling fees based on the user's address, the vendor's address, and other predefined parameters.
  • a voice message is played that asks the user to approve or cancel the described transaction by dialing a specified number. If the user notes that his data and the desired transaction data were correctly recognized by the system, he can approve the transaction (step 210).
  • the system may then confirm that the desired transaction was accepted and may give the user a confirmation number (e.g., a reference number) for that transaction. In some embodiments, the system will not generate the transaction if at step 210 the user hangs up or disconnects from the system.
  • the system may tell the user that the transaction could not be processed and may clear the call when the system determines at step 204 that the data entered by the user is not legitimate.
  • the above described illustrative transaction deals with buying a product.
  • the methods and systems illustratively described herein can also be used for many other transaction types between users and vendors that involve printed or displayed matter that is used in connection with a computer network.
  • Transaction types such as services for transferring information or paying a bill may be provided as described below.
  • the system may describe by voice message the transaction details to the user so that the user can be informed of the exact transaction that is about to be performed. The system may also let the user know that he was correctly identified.
  • FIG. 8 is a flow chart illustration of an illustrative transaction process that includes continuing transactions.
  • the system may accept additional transactions after a first transaction.
  • the system may ask the user whether the user would like to make an additional transaction and may inform the user that additional transaction codes may be entered at this time.
  • the system may accept the transaction without requiring re-entry of the PIN or without requiring the dialing of an access number. The user then hears a voice message telling the user the description of the additional transaction as understood by the system.
  • the transaction name "XXX" and confirmation number "YYYYY" of step 212 may change for each specific-transaction. When the user stops dialing additional specific-transaction codes the process may be terminated by the system.
  • FIG. 9 is a schematic example of paper bill 93 containing specific-transaction code 95.
  • This figure illustrates an example of another application of the present invention.
  • a user receives printed electricity bill 93.
  • the electric company may be a registered vendor in the transaction handling system.
  • the vendor may have printed specific- transaction code 95 as "487" along with an access number on bill 93 to enable a registered user to efficiently pay the bill by dialing specific-transaction code 95 using his telephone.
  • the transaction may be handled by the transaction-code handling system to pay the bill for the user.
  • the specific data of the user's bill is retrieved from the system's database and a voice message is generated that reads to the user the bill's data (e.g., bill issuer, dollar amount, date, etc.) .
  • the user may be asked to confirm the payment and may receive a confirmation number.
  • a vendor may be required to execute an agreement to be registered on the system. Paper invoice 97 schematically shown in FIG.
  • FIG. 10 includes two specific-transaction codes 91 and 94.
  • FIG. 10 illustrates another example of an application of transaction handling systems and methods in business-to- business environments.
  • a sending business the vendor in this example
  • the receiving business employee uses his telephone to dial the appropriate specific- transaction code in order to report the status of the received goods to the computer network of his business and to the computer network of the sending business.
  • the transaction may be handled by the transaction code handling system in a similar way as that described above in connection with FIGS. 1-4 and 5-8, but in this example the transaction involves an information exchange and not a goods and/or monetary exchange .
  • the above process can also be used to execute transactions between individuals who are connected to a computer network and registered to the system. For example a family (who may be the vendor in this case) can post a message in a bulletin board with a specific- transaction code for selling their house. A user who calls the posted access number and dials that specific- transaction code may receive (by e-mail in this example) more data on the specific house for sale.
  • An illustrative flow chart for telephonically completing transactions automatically is shown in FIG. 11. The process may begin with a user's call for entering a communications network of the system when a user dials an access number at step 402.
  • the communication network may be an intelligent network that is further discussed below.
  • the system's network may have a number of access numbers that may have been selected as a function of the number of vendors and users that the system is planned to handle.
  • the network may be capable of handling communications utilities such as identifying the calling telephone number or communication address and may provide that number into the system's computer software (further discussed below) .
  • Identification of a calling telephone number or communications address is usually available in communications networks in which the user has not selected to block identification.
  • the telephone operator systems will enable selective-programmable identification blocking. In these systems, a user can ask a telephone or communications provider to have the blocking removed when he calls the system's access numbers and the blocking to be active when he calls other numbers.
  • Step 402 might be divided for user convenience into two steps one for entering the PIN and one for entering the transaction code.
  • PINs Personal Identification Numbers
  • the first one may be a provisional PIN.
  • This PIN could be a -digit number (in other embodiments it may have a different number of digits or letters) .
  • the user may receive the provisional PIN personally or by mail or e-mail prior to the user using the system.
  • This provisional PIN can be for example the number 6382 for a certain user.
  • the provisional PIN will enable the user to enter the system for the first time and be identified but it will not enable him to generate transaction orders.
  • the second type of PIN may be a permanent PIN.
  • the permanent PIN could be assigned by the system when a user selects a particular number for the PIN.
  • the user may select a particular number when the user enters the system for the first time.
  • the system may assign the selected number to be the PIN for that user.
  • the permanent PIN enables the user to execute transaction orders using the system.
  • the system e.g., the software of the system
  • the user data may include several fields.
  • the user data may include assigned telephone numbers of the user (for example 1-217-1234-567) .
  • One or several telephone numbers or communications addresses of the user could have been selected at registration for enabling the execution of transactions by the system. These numbers can be for example the user's cellular telephone number, his home telephone number, and his office telephone number. These numbers are used for security reasons so that in conjunction with a short PIN the calling user can be identified and traceable.
  • the system may enable the user to execute transaction orders from any telephone number, but in these situations, the system would be less user- friendly, because for security reasons, the user will have to dial a pre-assigned identification number (e.g., the user's Social Security, home telephone number, etc.) in addition to his PIN for a safe identification .
  • a pre-assigned identification number e.g., the user's Social Security, home telephone number, etc.
  • step 406 the system may check a database of registration information to determine whether the user dialed his permanent PIN. If the user has entered a provisional PIN, the process may continue to steps 410-412 involving the permanent PIN assignment process (described in FIG. 12) . If the permanent PIN for that user has been entered, the system may retrieve the vendor data and , product data (e.g., data on goods or services) from the database and may compute shipping and handling fees at step 408. The fees may be based on the user's address, the vendor's address, and possibly on additional parameters. In step 414, the system may check whether the specific-transaction code entered by the user was legitimate (e.g., by matching the code to the database) .
  • product data e.g., data on goods or services
  • the system may generate a voice message (see FIG. 7 step 208) and ask the user to confirm the transaction at step 416. If the code is not legitimate, the system may generate a voice message telling the user that the transaction could't be processed and may clear the call at step 418.
  • the system may check whether the user approved the transaction. If the transaction is not approved, the system may generate a "thank you" message at step 424 and may clear the call. If the transaction was approved, the system may create a specific transaction order file, which may contain all the needed transaction data (see FIG. 13) , and may send the file to the vendor by e-mail via the Internet at step 422. The document may be sent to the vendor in other ways such as using regular mail, a dedicated communications connection, etc.
  • FIG. 12 is an illustrative flow chart showing an illustrative PIN assignment process.
  • the user may be provided with a provisional PIN personally (or by secure mail) on registration with the system at step 600.
  • the provisional PIN may enable the user to enter the system by dialing an access number (step 602) , but may not enable the user to make transactions.
  • the system may identify the calling telephone number at step 604 and ask the user using for example, a voice message to enter the provisional PIN (step 606) , and may compare the PIN to the PIN stored in the database (step 608) . If the PINs do not match the system may notify the user to contact a customer service telephone number and may clear the call at step 610.
  • the system may ask the identified user to select and enter a new PIN, which will be the user's permanent PIN, at step 612. For verification the system may ask the user to again enter his PIN at step 614 until the two inputs match (step 616) . After a match, the user can continue to make transactions using the system (step 408 FIG. 11) .
  • FIG. 13 illustrates a part of the system's database.
  • the database may contain, among other things, the essential data needed for the execution of a specific transaction.
  • the data may be the user's data that was recorded at the user's registration (e.g., assigned telephone numbers, name, mailing address for goods and documents, assigned credit card type, credit card number, expiration date, and a provisional PIN, etc . ) .
  • the permanent PIN can be entered into the database on the first use of the system by the user.
  • the database may also contain vendor's data 603 (e.g., name, address, assigned bank account, etc.).
  • the transaction data may contain all the transaction descriptions enabled to be executed with this vendor, the assigned transaction codes for the transactions, and prices.
  • FIG. 14 illustrates a block diagram of the components of one embodiment of the transaction handling system.
  • System 1116 may contain two major subsystems comprising intelligent network 1114 and computer-network server computer 1118 (which may be an Internet server) .
  • Intelligent network 1114 which may contain dedicated software 1126 may handle the telephone network functions and utilities of the system (switching, voice messages generation, calling number identification, etc.).
  • Intelligent network 1114 may be connected to telephone network 1110 via telephone network link 1112.
  • Intelligent network 1114 may be connected via a data communications link to server 1118.
  • Server 1118 may generate the transaction-orders and may send them via computer network 1120 to the vendors (and in some embodiments also to other computers, for example to the financial institution's computer).
  • Server 1118 may contain a dedicated server software 1124 and database 1128 for the user's data, vendors data and financial institutions data.
  • the server 1118 may be connected to the network 1120 (e.g., the Internet) via a computer network link 1122.
  • Telephone network 1110 may be a public switched telephone network or some other communications network.
  • Intelligent network 1114 may handle communications network functions and utilities of the system
  • the transaction handling system may comprise a plurality of functional blocks that may each comprise hardware, software, or a combination thereof.
  • the transaction handling system may comprise database 40, registration processor 42, transaction processor 43, communications utility handler 44, financial institution communications interface 45, voice analyzer 41, user locator 47, vendor communications interface 46, and user communications interface 48.
  • Database 40 may store information (e.g., see FIG. 13) that is recorded when registering vendors and users.
  • Database 40 may also contain other information such as the user identification codes for each user account and the transaction codes for available transactions.
  • Database 40 may be accessed to retrieve desired information.
  • Vendor communication interface 46 may be a communications interface that handles communications with vendors.
  • Vendor communications interface 46 may receive and transmit communications between the transaction handling system and the vendors. For example, vendor communications interface 46 may send a specific transaction order to a vendor in response to transaction processor 43 accepting a transaction code. Vendor communications interface 46 may be for providing communications via telephony, via a computer network, via e-mails, etc.
  • User communications interface 48 may be a communications interface that handles communications with users. User communications interface 48 may receive or transmit communications between the transaction handling system and users. User communications interface 48 may be for providing communications via telephone, via a computer network, via e-mails, etc. User communications interface 48 may be part of intelligent network 1114 of FIG. 14. Financial institution communications interface
  • Financial institution communications interface 45 may be a communications interface that handles communications with financial institutions.
  • Financial institution communications interface 45 may receive and transmit communications between the transaction handling system and the financial institutions.
  • financial institution communications interface 45 may send a specific communication (e.g., a payment transfer request) to a financial institution in response to transaction processor 43 accepting a transaction code.
  • Financial institution communications interface 45 may be for providing communications via telephony, via a computer network, via e-mails, etc.
  • Communications utility handler 44 may be a utility that handles communications tasks that are beyond the capabilities of user communications interface 48 or vendor communications interface 46.
  • communications utility handler 44 may detect the communications address that is sending a communication (e.g., user Caller ID to detect a telephone number) .
  • Other examples may involve handling a plurality of simultaneous communications, switching communications, etc .
  • vendor communications interface 45 may be a communications interface that handles communications with financial institutions.
  • vendor communications interface 45 may receive and transmit communications between the transaction handling system and the financial institutions.
  • financial institution communications interface 45 may send
  • Registration processor 42 may communicate with database 40, with communications utility handler 44, with vendor communications interface 46, and with user communications address 48.
  • registration processor 43 may make transactions available to users on the system.
  • Registration processor 43 may register vendors, transactions, and users, which may involve obtaining information on transactions, vendors, or users (e.g., user billing and shipping information) and recording the information to database 40.
  • Registration processor 42 may assign a transaction code to every transaction that is registered and may assign a user identification code to every user that is registered. If desired, registration processor 42 may record information about a user's voice during registration to allow the identification of the user based at least partly on his voice (e.g.
  • Transaction processor 43 may communicate with database 40, with financial institution communications interface 45, with voice analyzer 41, with user locator 47, with communications utility handler 44, with vendor communications interface 46, and with user communications interface 48. In operation, transaction processor 43 may handle activity for completing transactions between a user and a vendor.
  • Transaction processor 43 may perform steps illustratively described above for arranging to complete transactions such as accepting a communication comprising a transaction code and a unique identification number, arranging that the transaction be completed for the user, comparing a communications address to information in database 40, comparing a user identification number to identification numbers in database 40, billing users for transactions, having products shipped to. users based on shipping information in database 40, etc. If desired, transaction processor 43 may accept a communication consisting only of a personal identification code and a transaction code and in response transaction processor 43 may arrange the transaction.
  • the system may include user locator 47.
  • User locator 47 may communicate with user communications interface 48, transaction processor 43, and database 40.
  • User locator 47 may determine the location of a user who is accessing the system. User location may be determined in a variety of ways. For example, user location may be determined from a wireless telephone network from which a user may be accessing the system, from a GPS system, etc. User locator 47 may provide information about the location of the user to transaction processor 43.
  • transaction processor 43 may use the location information from user locator 47 to determine which one of the transaction a user desires.
  • User locator 40 may access information in database 40 in locating users.
  • the system may include voice analyzer 41.
  • Voice analyzer 41 may communicate with user communications interface 48, transaction processor 43, and database 40.
  • Voice analyzer 41 may receive voice communications of a user who is accessing the system from user communications interface 48.
  • Voice analyzer 48 may access database 40 to obtain information about the voices of registered users and/or the identification codes of users.
  • Voice analyzer 41 may identify a calling user's voice based on information in database 40.
  • voice analyzer 41, or transaction processor 43 in cooperation with voice analyzer 41 may identify a registered user that is accessing the system based on the user's voice, a word that a user has selected to be used as a user identification code at registration, the caller ID of the calling party, any other suitable resource, or using any suitable combination thereof.
  • voice analyzer 41 may recognize an identification code using voice recognition techniques to match the spoken identification code with the user's assigned identification code in identifying the user.
  • Voice analyzer 41 may be provided with information for use in identifying users from transaction processor 43, database 40, user communications interface 48, etc. If desired, voice analyzer 41 may compare a voice communication from a user that comprises a spoken user identification code with voice signatures that may have been recorded during registrations of users. A user may be identified based on the comparison. It is to be understood, that the configuration and connections of FIG. 15 are illustrative and that variations in the configurations and connections may be made .
  • Platform 50 may be a computer, a personal computer, a server, a workstation, two or more network computers (e.g., the system shown in FIG. 14) , dedicated telecommunications equipment, etc.
  • Platform 50 may comprise hardware 52 and software 54.
  • Hardware 52 may comprise processor 56 that processes logical operations, communications handler 58 that is a communications interface (e.g., a modem, an ethernet connection interface, interfaces for a plurality of wireless or landline communications, etc.), storage 62 that is temporary storage, long-term storage, or both (e.g., RAM, ROM, a hard drive, floppy drive, optical disc, tape, etc.), peripherals 62 (e.g., printers, scanners, etc.), input/output interface 14 such as, a keyboard, mouse, monitor, scanner, etc.) .
  • communications handler 58 that is a communications interface (e.g., a modem, an ethernet connection interface, interfaces for a plurality of wireless or landline communications, etc.), storage 62 that is temporary storage, long-term storage, or both (e.g., RAM, ROM, a hard drive, floppy drive, optical disc, tape, etc.), peripherals 62 (e.g., printers, scanners, etc
  • Software 54 may comprise drivers 66 for driving components of hardware 52 (e.g., driving communications handler 58, peripherals 62, interface 64), operating system 68, transaction handling application 70 for implementing some or all of the methods discussed herein, communications utilities 72 for performing communications utilities such as detecting a source of a communication. Communications utilities 72 may comprise features for providing secure connections (e.g., for providing firewalls).
  • platform 50 may operate using hardware 52 and software 54 to provide registration processor 42, transaction processor 43, communications utility handler 44, vendor communications interface 46, user communications interface 48, database 40, etc.
  • transaction handling system 74 may have sufficient hardware and software to communicate and handle transaction orders from a plurality of different user terminal platforms.
  • transactions handling system 74 may receive a communication (e.g., an aural communication) comprising a transaction code and a user identification code from a telephone platform (e.g., telephone 76), a PDA platform (e.g., PDA 78), and a personal computer platform (personal computer 80) .
  • a communication e.g., an aural communication
  • a communication comprising a transaction code and a user identification code from a telephone platform (e.g., telephone 76), a PDA platform (e.g., PDA 78), and a personal computer platform (personal computer 80) .
  • PDA platform e.g., PDA 78
  • personal computer 80 personal computer 80
  • Transaction handling system 74 may also communicate with a plurality of vendor terminals 82, 84, and 86 that may each be for a different vendor and may comprise different types of communications terminals (e.g. different types of terminal platforms) .
  • Transaction handling system 74 may have a communications connection with financial institution 88 for handling payments between vendors and users.
  • Financial institution 78 e.g., a bank, credit card company, debit card company, etc.
  • Financial institution 78 may be assigned by a registered user to transfer payments for transactions from the user's account to the account of the vendor. Information about the financial institution 78 may have been recorded when users registered to use transaction handling system 74.
  • System 74 may communication with a plurality of financial institutions, credit card company 81, bank 88, that may each have different types of terminals for communicating with system 74.
  • a scanning device may be used for entry of a personal identification code and/or transaction code in user terminals such as telephone 76, PDA 78, and personal computer 80. The scanning device may allow entry of such communication information for transmission to the system.
  • Each user terminal may be in a different communications network that may each use a different communications protocol for communicating with user terminals in that communications network.
  • PDA 78 may communicate with a communications network of a communications provider using a TDMA communications protocol and telephone 76 may be a wireless telephone that may communicate with a communications network of a communications provider using a CDMA communications protocol.
  • An advantage of this is that the system is compatible with a number of different communications networks, compatible with communications that are from networks using different protocols, etc. This flexibility allows the system to operate without being dependent on what type of user terminal , user terminal platform, originating communications protocol, etc. is used.
  • the system may give the user a chance to enter a dollar amount for the transaction. For example, the user may enter a dollar amount after entering a personal identification code.
  • a personal identification code and a transaction code are provided to or received by the system using aural communications.
  • Any form of aural communications technique may be used to provide such communications (e.g., telephone, voice over IP, etc. ) .
  • a system that overcomes the deficiencies in known transaction handling systems and quickly completes transactions for users. Moreover, the system may handle many simultaneous transactions at a cost that is much lower than known techniques such as human-operated call centers.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Telephonic Communication Services (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention se rapporte à un système de gestion automatique de transactions qui exécute automatiquement des transactions pour des utilisateurs. Ce système comprend une base de données d'informations relatives aux utilisateurs qui sont enregistrés auprès du système et d'informations relatives aux transactions enregistrées auprès dudit système. Ce système peut affecter un code de transaction à des transactions enregistrées et il peut affecter un code d'identification d'utilisateur à des utilisateurs enregistrés. Un utilisateur peut demander l'exécution d'une transaction en envoyant au système une communication qui contient un code de transaction et le code d'identification de l'utilisateur.
PCT/US2001/009452 2000-03-23 2001-03-23 Procedes et systemes de gestion de transactions WO2001071633A2 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
IL15187601A IL151876A0 (en) 2000-03-23 2001-03-23 Transaction handling methods and systems
EP01922640A EP1269380A2 (fr) 2000-03-23 2001-03-23 Procedes et systemes de gestion de transactions
NZ521530A NZ521530A (en) 2000-03-23 2001-03-23 Transaction handling methods and systems
CA002404142A CA2404142A1 (fr) 2000-03-23 2001-03-23 Procedes et systemes de gestion de transactions
AU2001249418A AU2001249418A1 (en) 2000-03-23 2001-03-23 Transaction handling methods and systems

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US19145400P 2000-03-23 2000-03-23
US60/191,454 2000-03-23

Publications (2)

Publication Number Publication Date
WO2001071633A2 true WO2001071633A2 (fr) 2001-09-27
WO2001071633A8 WO2001071633A8 (fr) 2002-08-01

Family

ID=22705557

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/009452 WO2001071633A2 (fr) 2000-03-23 2001-03-23 Procedes et systemes de gestion de transactions

Country Status (6)

Country Link
EP (1) EP1269380A2 (fr)
AU (1) AU2001249418A1 (fr)
CA (1) CA2404142A1 (fr)
IL (1) IL151876A0 (fr)
NZ (1) NZ521530A (fr)
WO (1) WO2001071633A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2833127A1 (fr) * 2001-12-05 2003-06-06 Mobileway Procede d'echange de donnees relatives a une transaction electrique

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
No Search *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2833127A1 (fr) * 2001-12-05 2003-06-06 Mobileway Procede d'echange de donnees relatives a une transaction electrique
WO2003048984A2 (fr) * 2001-12-05 2003-06-12 Mobileway Procede d'echange de donnees relatives a une transaction electronique
WO2003048984A3 (fr) * 2001-12-05 2004-02-19 Mobileway Procede d'echange de donnees relatives a une transaction electronique
US8359242B2 (en) 2001-12-05 2013-01-22 Sybase 368, Inc. Method for exchanging data concerning an electronic transaction
US8712865B2 (en) 2001-12-05 2014-04-29 Sybase 365, Inc. Method for exchanging data concerning an electronic transaction

Also Published As

Publication number Publication date
CA2404142A1 (fr) 2001-09-27
IL151876A0 (en) 2003-04-10
AU2001249418A1 (en) 2001-10-03
WO2001071633A8 (fr) 2002-08-01
NZ521530A (en) 2006-09-29
EP1269380A2 (fr) 2003-01-02

Similar Documents

Publication Publication Date Title
US20030069844A1 (en) Transaction handling methods and systems
US9177309B2 (en) Electronic settlement method, system, server and program thereof
US8917825B2 (en) Telephone-based commerce system
US8065226B2 (en) Method and system for performing a cash transaction with a self-service financial transaction terminal
US7555458B1 (en) Method of billing a purchase made over a computer network
US7685068B2 (en) Arrangement and method for tele-commerce with client profiles
US20020143634A1 (en) Wireless payment system
US20090049529A1 (en) Method Of Billing A Purchase Made Over A Computer Network
US20100169182A1 (en) Mobile payment method and system using the same
KR20000056546A (ko) 이동통신단말기를 이용한 물품대금 결제방법
JP2008204448A (ja) 請求者に予め関係付けられた勘定支払カードを使用する価値の挿入
EP1301912A1 (fr) Systeme de gestion de transactions
EP2465081A2 (fr) Systèmes et procédés pour traiter des transactions d'achat entre des téléphones mobiles
WO2001033520A1 (fr) Procede de facturation d'un achat effectue sur un reseau informatique
KR100325684B1 (ko) 이동통신단말기를 이용한 물품대금 결제방법
AU2020102380A4 (en) IMT-Voice Based Mobile Banking: INTELLIGENTMONEY TRANSFER USING VOICE BASED MOBILE BANKING
US8953754B1 (en) Pre-authentication system and method for outgoing communication
AU2001249418A1 (en) Transaction handling methods and systems
JP4938930B2 (ja) カード決済装置、カード決済方法、カード決済プログラム、およびカード決済プログラムを記録したコンピュータ読み取り可能な記録媒体
KR100328577B1 (ko) 물품대금 결제방법
KR100612825B1 (ko) 발신자 번호와 일회용 암호를 이용한 전화 쇼핑 서비스제공 시스템 및 방법
KR20010048787A (ko) 이동통신단말기를 이용한 물품대금 결제방법
JP2001250074A (ja) 入金確認システム、企業センタ、支払受付装置及び入金確認方法
EP1385131A1 (fr) Procédé pour la communication d'un numéro de référence à travers un réseau non-sécurisé
KR20020080527A (ko) 전화 단말기를 이용한 이체 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: C1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: C1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

D17 Declaration under article 17(2)a
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWE Wipo information: entry into national phase

Ref document number: 2404142

Country of ref document: CA

Ref document number: 2001249418

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 151876

Country of ref document: IL

Ref document number: 521530

Country of ref document: NZ

WWE Wipo information: entry into national phase

Ref document number: 2001922640

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2001922640

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP