EP1049057A2 - Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière - Google Patents

Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière Download PDF

Info

Publication number
EP1049057A2
EP1049057A2 EP00108096A EP00108096A EP1049057A2 EP 1049057 A2 EP1049057 A2 EP 1049057A2 EP 00108096 A EP00108096 A EP 00108096A EP 00108096 A EP00108096 A EP 00108096A EP 1049057 A2 EP1049057 A2 EP 1049057A2
Authority
EP
European Patent Office
Prior art keywords
data
customer
home
transaction
remote
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.)
Withdrawn
Application number
EP00108096A
Other languages
German (de)
English (en)
Other versions
EP1049057A3 (fr
Inventor
Gordon W. Zahorik
John Downing
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Citibank NA
Citishare Corp
Original Assignee
Citibank NA
Citishare Corp
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 Citibank NA, Citishare Corp filed Critical Citibank NA
Publication of EP1049057A2 publication Critical patent/EP1049057A2/fr
Publication of EP1049057A3 publication Critical patent/EP1049057A3/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • 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

Definitions

  • the present invention relates to Electronic Funds Transfer (EFT) and related transactions.
  • EFT Electronic Funds Transfer
  • the present invention relates to tunneling messages related to financial transactions through EFT routing and settlement systems such that a remote terminal interface may operate according to the home bank terminal interface of a customer or such that private data may be passed between a financial institution and a customer during an internet transaction with a web merchant.
  • a first automatic teller machine (ATM) of a bank in one country provides a certain interface, for example a certain graphical interface, options, button placement, and order of script.
  • An ATM of the bank in a different country may provide a different interface.
  • the graphical interface, options, button placement, language used, order of script, and other aspects may be different from that of the first ATM.
  • the customer of a first bank uses an ATM provided by a second bank, the customer must use the interface provided by the second bank.
  • a bank's customers generally become accustomed to a particular interface provided by the bank, and may not be familiar with the interface provided in another location or by another bank. As a result, an unfamiliar interface makes it more difficult for the customer to carry out transactions. Also, the customer's unfamiliarity with an interface increases the chance that the customer will undertake an erroneous transaction.
  • the transaction takes more time, in that the customer must familiarize himself or herself with the unfamiliar interface during the transaction.
  • the resulting unfamiliarity causes the customer to purposefully slow the customer's transaction.
  • This delay is disadvantageous to the customer in that the customer wishes to complete the transaction as quickly as possible in order to spend time on other activities.
  • the delay is also disadvantageous to the institution providing the unfamiliar terminal in that the customer's delay causes other of the institution's customers to wait longer in line and otherwise delays other persons.
  • the resulting increase in erroneous transactions causes the customer and person(s) associated with the bank(s) to spend time and resources correcting such erroneous transactions.
  • conventional systems do not provide an effective and efficient means for transmitting encrypted, private data between a customer of a financial institution and the financial institution in association with a internet transaction at a web merchant site such that the web merchant site does not have access to the private data.
  • conventional systems do not provide such means that may be easily employed with existing routing systems (e.g., existing EFT infrastructure).
  • Embodiments of the present invention include methods and systems for communicating private data in a financial network.
  • a financial transaction message comprising a financial transaction data field and a private data field, which includes private customer information, is transmitted through a routing system of a financial institution.
  • routing systems includes a routing and settlement system of a financial institution and electronic funds transfer (EFT) infrastructure.
  • EFT electronic funds transfer
  • Embodiments also include a financial transaction message comprising a financial transaction data field and a private data field, wherein the private data field comprises customer information.
  • the message may comprise an ISO 8583 standard format message, and the private data field may comprise an extended field of the message.
  • Embodiments of the present invention also include methods and systems for tunneling messages through routing and settlement systems of a financial institution.
  • the invention provides a method for providing a customer of a home bank with a home bank terminal interface experience at a remote transaction terminal.
  • a remote transaction terminal is an ATM that is geographically remote from the home bank.
  • An embodiment of the present invention may include receiving home bank customer identification data at a remote transaction terminal, such as an ATM. Such receiving may be accomplished by reading the customer's ATM card, for example. Next, a home bank server associated with the customer identification data is determined by, for example, consulting a database having home bank server address data. Home transaction terminal interface data is then requested from the home bank server, which sends such data. Embodiments of such data may include data describing the graphical user interface of the home bank terminal interface, such as a home bank ATM interface. In an embodiment, the home transaction terminal interface data may be included in a private field of an ISO 8583 message, along with financial transaction data in another field. Such home transaction terminal interface data may also include biometrics data associated with the home bank customer. Such data may also include data regarding menu options, button placement, language used, order and content of script, and other aspects of terminal interface.
  • the request and sending of such data may comprise communicating with the home bank server through a routing and settlement system of a financial institution.
  • the request, the data itself, or both, may be encrypted.
  • the home transaction terminal interface data is received, and an interface according to the home terminal interface data is provided to a customer at the remote terminal.
  • Another embodiment of the present invention comprises a method for communicating messages for a customer between a remote transaction terminal and a home data center of a financial institution.
  • customer information from the customer at the remote transaction terminal may be received, and then used to automatically identify the customer and a location of a home data center storing data relating to a home transaction terminal interface for the customer.
  • the identifying information for the customer from the remote transaction terminal is automatically transported to the home data center through a routing and settlement system of the financial institution.
  • the server or other system associated with the home data center then automatically transports a message relating to the home transaction terminal interface data for the customer from the home data center to the remote transaction terminal through the routing and settlement system, wherein the message includes financial data and generic data for the customer.
  • the automatic transporting of a message relating to the home transaction terminal interface data for the customer from the home data center to the remote transaction terminal through the routing and settlement system may employ an ISO 8583 protocol containing a private data field.
  • the message protocol may be used to transport the financial data, and the private data field used to transport the generic data.
  • a financial institution provides a control applet to a web merchant site and provides a means for providing internet payments capable of communicating with a computer network (such as the internet) to a customer of the financial institution.
  • the means for providing internet payments may comprise a wide variety of hardware capable of carrying out such a function. Examples include a smart card, smart card reader, personal computer, ATM card, and ATM card reader.
  • the customer visits the web merchant site and the web site merchant provides the control applet to the customer's internet browser.
  • the control applet prompts the customer for payment and other customer information when the customer indicates the customer has selected goods or services for purchase from the merchant site is ready to finalize payment.
  • the customer sends the customer information, in an encrypted state, to the merchant site.
  • the merchant site does not have the means to un-encrypt the customer information.
  • the merchant site sends the customer information to the financial institution through EFT infrastructure using an ISO 8583 standard message that includes a private data field containing the customer information.
  • the financial institution receives the message from the web merchant site.
  • the financial institution has the means to un-encrypt the customer data in the private data field.
  • Embodiments of the present invention provide various desirable features and advantages.
  • Embodiments of the present invention provide methods and systems for providing a customer of a home bank with a home bank terminal interface experience at a remote transaction terminal.
  • One feature of embodiments of the present invention is that users (e.g., bank customers) are provided with a familiar interface at remote terminals.
  • transactions at the remote terminal are easier for the customer to carry out than with unfamiliar interfaces.
  • due to this familiarity the chance that the customer will undertake an erroneous transaction at the remote terminal is decreased.
  • Another advantage is that transactions at remote terminals are accomplished more quickly because, for example, the customer does not need to familiarize himself or herself with the remote terminal's interface during the transaction.
  • the reduction of delay due to unfamiliarity is advantageous to the customer in that the customer wishes to complete the transaction as quickly as possible in order to spend time on other activities, and is advantageous to the institution operating the remote terminal in that others do not have to wait as long for the customer to familiarize himself or herself with the terminal.
  • the lessening of erroneous transactions due to unfamiliarity with the interface causes the customer, the customer's home institution, and the operator of the remote terminal to spend less time and resources correcting erroneous transactions.
  • a touch point to the customer's institution e.g., a bank
  • remote terminals that has the same look and feel to the bank's customers as the customers' home terminals.
  • Such embodiments help to build loyalty, and provide a continuous and familiar experience to the customer when conducting transactions.
  • a further feature of embodiments according to the present invention is that messages may be tunneled through routing and settlements systems throughout the world.
  • customers may be provided with a familiar interface (e.g., with the same language, scripting, and look and feel as the interface normally used by the customer) at interfaces throughout the world.
  • transaction protocols may be used to lessen data transfer overhead.
  • biometric and similar data may be communicated to the remote terminal, and the data provided may be encrypted.
  • embodiments of the present invention allows companies is that embodiments allow institutions, such as financial institutions, to quickly introduce new products that require communication with the institution using existing communications infrastructure. Another advantage is that embodiments of the present invention may be used without altering the existing communications infrastructure use to transport information.
  • embodiments of the present invention facilitates secure payments and communication by customers to a financial institution and promotes confidence in such payments and communication.
  • a related advantage of the present invention is that embodiments may be used to authenticate customers, merchants, and financial institutions in order to prevent fraud.
  • Another advantage of the present invention is that embodiments may used in association with a variety of media, including the internet.
  • a still further advantage of the present invention is that, in embodiments, existing EFT infrastructure can be used to transport private customer data relating to a customer of a financial institution that is unique to the customer and the financial institution and that is accessible only by the customer and the financial institution.
  • Another advantage of the present invention is that embodiments allow a private and secure conversation between a financial institution and a customer of the financial institution to take place via existing EFT infrastructure in various settings, such as during customer's transaction with a merchant site.
  • Such advantage allows various financial institutions to implement various customer dialogs as desired or needed by the financial institution (and their products) while sharing a common EFT infrastructure.
  • Embodiments of the present invention include methods and systems for tunneling messages through routing and settlement systems of a financial institution.
  • Embodiments of the present invention include methods and systems for providing a customer of a home bank with a home bank terminal interface experience at a remote transaction terminal by tunneling messages though a routing and settlement system of a financial institution. Further description of embodiments of the present invention is provided below by way of example embodiments with reference to the figures provided.
  • the embodiment includes a remote transaction terminal 4 in Singapore.
  • the remote terminal 4 comprises an ATM.
  • Other types of transaction terminals such as a telephone or a personal computer terminal, may be used in accordance with the present invention as well.
  • a home transaction terminal 10 in Germany is also shown.
  • the home terminal 10 is an ATM.
  • the home terminal 10 is associated with a home bank of a customer 2 (such as the customer's local branch bank). It is also associated with a home data center 8, which is also associated with the customer's home bank.
  • the home terminal 10 shown is the ATM which the home bank customer 2 normally uses while at home in Germany, but other terminals may be designated the home terminal associated with the customer if desired, and this designation may be made by the home bank, the customer 2, or other person or entity.
  • a remote terminal is generally a terminal that is different from the home terminal of the bank customer.
  • the remote terminal includes a card reader for reading data from bank cards and the like.
  • the remote terminal may be geographically distant from the home terminal of the bank customer, whether of great geographic distance as is the embodiment shown in FIG. 1 (Germany and Singapore) or relatively little geographic distance, such as in the same town or city.
  • the remote terminal 4 is associated with the home bank in that it is part of the same, global financial institution. In other embodiments, however, the remote terminal 4 may be associated with a different institution.
  • the home data center 8 shown in FIG. 1 is the data center associated with the home bank of the customer 2.
  • Data regarding the home terminal, the home bank customer, and related data is housed at the data center 8.
  • Data housed at the data center 8 includes data regarding the interface of the home terminal 10 (home transaction terminal interface data), such as data indicating matters such as the text of the various screens available, configuration of the response buttons, graphical layout of an ATM screen, the order of questions, the questions themselves, the buttons pushed to answer the questions, the script, order of questions, and organization of the screens.
  • the home transaction terminal interface data is associated with certain customer identification data.
  • the customer identification data e.g., account number
  • Data regarding the home bank customer 2 also includes account information (e.g., account numbers) as well as biometrics data about the customer.
  • Biometrics data includes data regarding the physical characteristics of the customer. Examples include retinal scan data, finger print data, and related data.
  • the center 8 shown includes a data server and a database for managing, communicating, and storing data.
  • the home data center 8 shown like the home terminal 10, is located in Germany, but the home terminal and home data center in other embodiments may be more geographically distinct if desired.
  • the home data center 8 is in communication with the home terminal 10, and provides the home terminal 10 with the data needed to provide an interface to customers.
  • the embodiment shown comprises portions of a global bank.
  • the portions may be part of separate banks, and communication may take place using the separate banks' routing and settlement systems or using other communications means.
  • the home terminal 10 may be associated with a first bank and the remote terminal 4 associated with a second, unrelated bank.
  • the bank's routing and settlement system 6 is shown in FIG. 1.
  • the system comprises a computerized communication network, and manages debits and credits for the bank, including settling transactions.
  • the routing and settlement system 6 is the system used by the home bank to route data regarding financial transactions and other matters, and to settle transactions.
  • the routing and settlement system 6 of a financial institution is just one example of a data communication system that may be used in accordance with the present invention. Other systems, such as the internet, may be used.
  • the home data center 8 and the remote terminal 4 are in communication with the bank's routing and settlement system 6. Communication, such as data transfer, may pass through the bank's routing and settlement system between the remote terminal 4 and the home data center 8 by way of messages or other means.
  • FIG. 3 An example of steps undertaken by the system shown in FIG. 1 in accordance with the present invention is shown in FIG. 3 and discussed herein with reference to FIG. 3 and to FIG. 1. Those of ordinary skill in the art will recognize that FIG. 3 and the discussion herein provides an example of steps, and that other steps and configurations may be used in accordance with the present invention.
  • the customer 2 provides the remote ATM system 4 with the customer's bank card.
  • the ATM 4 receives the bank card of the home bank customer 20.
  • the bank card includes home bank customer information, such as home bank customer identification data. Examples of home bank customer identification data include a bank card number.
  • the ATM system 4 automatically detects and receives the home bank customer identification data from the bank card 22.
  • customer information may be input at the remote terminal 4 by the customer or another person.
  • the ATM system 4 automatically (without, for example, further prompting by the customer or other prompting) identifies the location of a home data center having data relating to a home transaction terminal interface for the customer.
  • the ATM system 4 does so by accessing and querying a database 5 associated with the ATM 4.
  • the database 5 includes home bank server addresses associated with customer identification data.
  • the database 5 includes the home bank server address associated with the customer identification data of the customer 2.
  • the system determines the address (or location) of a home bank server associated with the customer identification data 24.
  • the determination of the address of a home data center associated with a customer is carried out by bank's routing and settlement system 6 when provided with customer identification data by the ATM system 4.
  • the ATM system 4 requests home transaction terminal interface data from the home bank server 8 associated with the home bank customer 2 through routing and settlement system 6 of the bank 26. In doing so, the ATM system 4 sends (or transports or transmits) the request along with the customer identification data received from the inserted bank card.
  • This transmittal of data is encrypted, as is, preferably, all transmittal of data through the routing and settlement system 6 when using embodiments of the present invention.
  • the home bank center 8 includes a home data server.
  • the server 8 determines the home transaction terminal interface data associated with the home bank customer 2 by, for example, querying a database (not shown) associated with the server that includes home transaction terminal interface data correlated with customer identification data. For example, after receiving the customer identification data from the ATM system 4, the server uses the customer identification data to query a database to determine the home transaction terminal interface data associated with that particular customer identification data.
  • such home transaction terminal interface data includes data for displaying German-language ATM screens identical to those displayed on the home ATM associated with the customer 2.
  • the home transaction terminal interface data associated with the customer 2 is sent to the ATM system 4 in Singapore via the bank's routing and settlement system 6, where it is received 28.
  • the ATM system 4 provides an interface to the customer 2 according to the data 30.
  • the ATM system 4 in Singapore uses the home transaction terminal interface data to display to the customer 2 German-language ATM screens identical to those displayed on the home ATM associated with the customer on the graphical user interface of the ATM system 4 in Singapore.
  • the system 4 displays an interface identical to the look and feel of the interface with which the customer 2 has become accustomed, the interface of the customer's home terminal 10.
  • the ATM system 4 continues requesting and receiving home transaction terminal interface data (i.e., a conversation) from the home bank server 8 through the bank's routing and settlement system 6 during the transaction by the customer 2 at the remote terminal 32.
  • home transaction terminal interface data i.e., a conversation
  • the ATM system 4 may request and receive further ATM-screen data, button-location data, and other home transaction terminal interface data. account balance data, previous-transaction data.
  • the home transaction terminal interface data is included, or embedded, in a in a private data field of a financial transaction message using the ISO8583 message protocol.
  • FIG. 4 An example is shown in FIG. 4.
  • the financial transaction message 40 shown is in the ISO8583 message protocol and includes financial transaction data 42 and private data 44.
  • a private message (or private data) field 44 that is, for example, 4000 bytes, is included in the message 40.
  • the private data field 44 in the embodiment shown is a field in which data (such as data describing the graphical user interface normally used by the customer) may be placed that may not be necessary for the financial transaction itself.
  • the private data field includes home transaction terminal interface data.
  • the home transaction terminal interface data may be included as part of the messages sent between the ATM system 4 and the home bank systems in relation to the home bank customer's transaction or in relation to other transactions.
  • the financial transaction field 42 includes data relating to the financial transaction itself (e.g., customer identification, requested transaction, account balance).
  • the private data field 44 allows data, such as home transaction terminal interface data, to be tunneled to the remote terminal for use.
  • the private data field comprises an extension of the standard ISO 8583 protocol (e.g., a 4000 byte extension).
  • the home terminal interface data and other data may be sent separate from the financial transaction data.
  • other types of data may be included in the private data field, such as biometrics data.
  • the home transaction terminal interface data may be sent separately from the financial transaction data.
  • generic data is used to reflect the interface. That is, data reflecting the make-up of the interface with a customer in a standard display language is used, which allows a system to construct a graphical interface
  • An example of such a standard in embodiments includes HTML.
  • the interface data may include the graphical images themselves for use in an interface.
  • other data regarding the home bank customer 2 is transported in the private field as well.
  • Biometrics data may be transported to the ATM system 4 in the private data field. Such data would allow the ATM system to examine the biometrics data of the person representing themselves as the customer in relation to the data recorded by the customer's home bank.
  • the ATM system 4 may request and receive data regarding a retinal scan of the customer, and compare that data with a retinal scan of the person representing themselves as the customer 2.
  • FIG. 2 shows a remote terminal 14 in the form of an ATM in New York, New York.
  • the remote terminal 14 is associated with a database 15, and the remote terminal 14 is capable of carrying out smart card transactions.
  • the remote terminal 14 is in communication with a bank routing and settlement system 6, which is in turn in communication with a home data system 16 in Denver, Colorado.
  • the home data system 16 is in communication with a home terminal 18 in Denver, in this case an ATM capable of carrying out smart card transactions.
  • a smart card having a microchip sufficient to record a stored value may be used with embodiments of the present invention.
  • a customer 12 provides the customer's smart card to a remote terminal 14, such as one in New York
  • the terminal 14 reads the customer identification on the smart card and communicates with the home data system 16 associated with the customer through the bank's routing and settlement system 6, requesting and receiving home transaction terminal interface data substantially as described above.
  • home transaction terminal interface data may be provided in the private data field which allows a remote terminal to interact with the customer 12 in the same manner that the home terminal associated with the customer 18 (e.g., in Denver) interacts with the customer 12 in relation to the customer's smart card.
  • interface data is provided in the private data field that allows for the loading of data representing value onto the smart-card microchip in communication with the remote terminal in exactly the same way that would be done by the customer's home terminal 18.
  • FIG. 5 shows another embodiment of the present invention.
  • a bank customer's personal computer (PC) 58 which includes a web browser such as Microsoft Internet Explorer or Netscape Navigator, is connected to the internet 56.
  • a web merchant site 54 (or web merchant server) is also connected to the Internet 56. Although not shown, many merchant sites are connected to the internet.
  • the web merchant site 54 shown comprises an Internet site at which the merchant offers goods and services for sale and accepts orders and payments for those goods and services from Internet users who access the site 54 via the internet 56.
  • the merchant site includes multiple web pages displaying goods and services for sale.
  • the web merchant site 54 is also in communication with the Electronic Funds Transfer (EFT) infrastructure 52 associated with a bank 50.
  • EFT Electronic Funds Transfer
  • the bank 50 is in communication with the EFT infrastructure 52 as well.
  • the bank 50 provides a customer 62 with a means for providing internet payments 64.
  • means for providing internet payments include secure tokens and secure token systems, such as a smart card and smart-card reader, computer, ATM card and ATM card reader, or other, similar hardware.
  • the means for providing internet payments is a smart card.
  • This means for providing internet payments 64 is in communication with the customer's PC 58.
  • the PC 58 shown includes a smart-card reader (not shown), which receives the smart card 64.
  • the bank 50 also creates a control applet.
  • the control applet described herein comprises an application program that is relatively small in size and that is sent to a user, and is often sent along with a web page.
  • the applet is designed to be executed from within another application (e.g., a web browser).
  • An applet is generally capable of performing interactive animations, immediate calculations, and other tasks, generally without having to send a user request back to a server. It is written in a language such as Java.
  • the control applet used in the embodiment shown in FIG. 5 is designed to control the dialogue between the merchant site 54 and the customer 62 through the customer's browser on the customer's PC 58 via the internet 56.
  • the control applet is programmed to communicate with the means for providing Internet payments 64 in communication with the customer's PC 58.
  • the bank 50 provides the control applet to the merchant site 54. Indeed, the bank 50 may provide the applet to all merchant sites that wish to sell products or services (or provide products or services) to the customer 62 and other customers of the bank 50. The bank 50 does so with the appropriate controls, such as encryption and confidentiality guarantees.
  • the customer 62 uses the internet browser on the customer's PC 58 to visit the merchant site 54 by typing in the merchant site's web address into the address line of the browser or by otherwise pointing the user's browser to the merchant site (such as by activating a link).
  • the customer 62 uses the customer's browser to select goods and services offered for sale by the merchant on the merchant site 54. For example, the customer 62 may use an electronic shopping cart to select goods and services for purchase.
  • the customer indicates to the merchant site 54 that the customer is ready to complete payment. For example, the customer 62 may activate a "Ready to Check Out" button displayed on a web page associated with the merchant site 54.
  • the merchant site determines that the customer 50 is associated with the bank 50 by, for example, detecting a cookie on the customer's PC 58 that so indicates.
  • the merchant site 54 identifies the customer 50 as a customer of the bank 50 by requesting a user name and password which so indicates, by asking the customer to indicate whether or not the customer is a customer of the bank, or by other means.
  • the merchant site 54 When the merchant site 54 detects that the customer 62 is ready to complete payment, the merchant site 54 sends the control applet to the customer's PC 58 to interact with (or run within) the internet browser residing on the customer's PC 58. In other embodiments, the control applet may be sent to the customer's PC beforehand.
  • the control applet has been programmed by the bank 50 to, when executed, allow the customer 62 to provide private customer information using the customer's browser that will be given to the bank 50, but not to the merchant site 54. Examples of such customer information includes the customer's credit card number, debit card number, bank account number, PIN number, and account balance.
  • the applet requests and receives private customer information from the smart card 64.
  • the smart card 64 includes private customer information in the form of a smart-card account number and current balance available thereon.
  • private customer information may be provided by the customer 62 by typing in such information into a web-based form, requesting and receiving such information from the customer's electronic wallet, requesting and receiving such information from hardware provided to the customer 62 by the bank 50 that is in communication with the customer's PC 58, or by other means.
  • the private customer information is secured (e.g., encrypted) and transmitted to the merchant site 54 via the internet 56 as part of the purchase transaction by function of the applet.
  • the merchant site 54 is unable to read the private customer information received by it.
  • a variety of encryption standards may be used to encrypt the private customer information for transmittal to the merchant site 54.
  • SSL Secure Sockets Layer
  • the merchant site 54 is not provided with the key or other means to read the private customer data sent to it.
  • the merchant site 54 After the merchant site 54 receives the private customer information and the other data associated with the transaction (e.g., the customer's shipping address, identification number of the goods and services ordered, and the customer's e-mail address), the merchant processes the payment using the EFT infrastructure 52 to which the merchant site 54 is connected. For example, the merchant uses the EFT infrastructure 52 to request payment from the smart card account of the customer 62 maintained by the bank 50.
  • the EFT infrastructure 52 comprises the existing, conventional EFT infrastructure used to carry out payment processes.
  • the financial transaction message 40 sent by the merchant site 54 to the bank 50 comprises an ISO 8583 message with financial transaction data 42 and private data 44.
  • the private data 44 comprises the private customer information from the smart card 64.
  • the financial transaction data 42 comprises the standard data needed to carry out the request to the bank 50 for payment and the receipt from the bank of payment to the merchant.
  • the bank 50 receives the financial transaction message 40 and completes the payment transaction based on both the usual EFT data provided in the financial transaction data field 42 and the private customer information provided in the private data field 44.
  • the bank 50 has a key or other means to un-encrypt and otherwise read the customer information in the private data field.
  • the bank 50 may transmit private data to the customer 62 by sending a message that includes private data in the private data field to the merchant site 54 through the EFT infrastructure 52 with embedded instructions to transmit the message to the customer's PC 58.
  • the message is encrypted such that the merchant site 54 cannot read the private data.
  • the customer's PC includes a key sufficient to un-encrypt the private data.
  • the merchant web site 54 does not possess such a key.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
EP00108096A 1999-04-26 2000-04-26 Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière Withdrawn EP1049057A3 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US13106699P 1999-04-26 1999-04-26
US131066P 1999-04-26

Publications (2)

Publication Number Publication Date
EP1049057A2 true EP1049057A2 (fr) 2000-11-02
EP1049057A3 EP1049057A3 (fr) 2004-05-06

Family

ID=22447703

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00108096A Withdrawn EP1049057A3 (fr) 1999-04-26 2000-04-26 Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière

Country Status (2)

Country Link
EP (1) EP1049057A3 (fr)
JP (1) JP2000348106A (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005008608A1 (fr) * 2003-07-11 2005-01-27 Rene Lehmann Systeme de paiement, terminal de systeme de paiement et procede pour realiser un paiement electronique

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997041498A2 (fr) * 1996-04-18 1997-11-06 Citibank, N.A. Procede et systeme ameliores permettant d'effectuer des transactions bancaires meme a domicile
WO1998019278A2 (fr) * 1996-10-31 1998-05-07 Citicorp Development Center Systeme et procede offrant des services financiers
WO1998024041A1 (fr) * 1996-11-27 1998-06-04 Diebold, Incorporated Appareil et systeme de guichet automatique bancaire
WO2001041090A1 (fr) * 1999-12-03 2001-06-07 Ncr International. Inc. Terminal libre-service

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997041498A2 (fr) * 1996-04-18 1997-11-06 Citibank, N.A. Procede et systeme ameliores permettant d'effectuer des transactions bancaires meme a domicile
WO1998019278A2 (fr) * 1996-10-31 1998-05-07 Citicorp Development Center Systeme et procede offrant des services financiers
WO1998024041A1 (fr) * 1996-11-27 1998-06-04 Diebold, Incorporated Appareil et systeme de guichet automatique bancaire
WO2001041090A1 (fr) * 1999-12-03 2001-06-07 Ncr International. Inc. Terminal libre-service

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005008608A1 (fr) * 2003-07-11 2005-01-27 Rene Lehmann Systeme de paiement, terminal de systeme de paiement et procede pour realiser un paiement electronique

Also Published As

Publication number Publication date
EP1049057A3 (fr) 2004-05-06
JP2000348106A (ja) 2000-12-15

Similar Documents

Publication Publication Date Title
US7319978B2 (en) Net shopping method, system therefor, and automatic payment transfer device
KR101015341B1 (ko) 온라인 지불인 인증 서비스
US7599859B2 (en) Communications network interface for user friendly interactive access to online services
US8051003B2 (en) Systems and methods of introducing and receiving information across a computer network
US6980970B2 (en) Secure networked transaction system
US7155411B1 (en) Integrating payment accounts and an electronic wallet
AU2004250269B2 (en) A system and method for facilitating on-line payment
US20080270246A1 (en) Global electronic payment system
US7546274B2 (en) System and method for facilitating electronic commerce transactions at an automatic teller machine
US20060242058A1 (en) Transaction system
CZ2002744A3 (cs) Způsoby a zařízení pro vedení elektronických transakcí
KR20020007973A (ko) 이동전화 단말기를 이용한 이체 방법
AU2001241977A1 (en) Multifunctional mobile banking system
EP1316035A1 (fr) Systeme bancaire mobile multifonctions
US20150278782A1 (en) Depositing and withdrawing funds
WO2001050391A1 (fr) Procede de gestion de transactions sur l'internet au moyen de proxy et avec des instruments financiers uniservice
JP2004240687A (ja) 現金引出しシステム、移動体通信端末、店舗端末、方法、及びプログラム
EP1049057A2 (fr) Méthode et système pour transmission-tunnel de messages via des systèmes de routage et de réglement d'une institution financière
WO2002011477A1 (fr) Systeme et procede d'acces et de stockage de donnees sur la carte a puce d'un telephone portable
JP2000011069A (ja) 携帯端末装置、ウォレット・システム、ウォレット・システムにおける決済方法および記録媒体
WO2002005159A1 (fr) Procede et systeme de reglement
JP2003016361A (ja) 決済処理方法及び決済処理システム
WO2001069914A2 (fr) PROCEDES DE GESTION DE TRANSACTIONS SUR L'INTERNET AVEC ADRESSES D'EXPEDITION ANONYMES
JP2001043295A (ja) 支払システム、携帯端末、支払センタ及び記録媒体
JP2002042039A (ja) 決済手段変換方法、決済手段変換サーバ、及び決済手段変換システム

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL PAYMENT 20000512;LT PAYMENT 20000512;LV PAYMENT 20000512;MK PAYMENT 20000512;RO PAYMENT 20000512;SI PAYMENT 20000512

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

17P Request for examination filed

Effective date: 20041028

AKX Designation fees paid

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AXX Extension fees paid

Extension state: SI

Payment date: 20000512

Extension state: RO

Payment date: 20000512

Extension state: MK

Payment date: 20000512

Extension state: LV

Payment date: 20000512

Extension state: LT

Payment date: 20000512

Extension state: AL

Payment date: 20000512

17Q First examination report despatched

Effective date: 20050310

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20050921