CA2392391A1 - Transaction processing using intermediate server architecture - Google Patents
Transaction processing using intermediate server architecture Download PDFInfo
- Publication number
- CA2392391A1 CA2392391A1 CA002392391A CA2392391A CA2392391A1 CA 2392391 A1 CA2392391 A1 CA 2392391A1 CA 002392391 A CA002392391 A CA 002392391A CA 2392391 A CA2392391 A CA 2392391A CA 2392391 A1 CA2392391 A1 CA 2392391A1
- Authority
- CA
- Canada
- Prior art keywords
- transaction
- server
- format
- terminal
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/42—Confirmation, e.g. check or permission by the legal debtor of payment
- G06Q20/425—Confirmation, e.g. check or permission by the legal debtor of payment using two different networks, one for transaction and one for security confirmation
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/0873—Details of the card reader
- G07F7/088—Details of the card reader the card reader being part of the point of sale [POS] terminal or electronic cash register [ECR] itself
- G07F7/0886—Details of the card reader the card reader being part of the point of sale [POS] terminal or electronic cash register [ECR] itself the card reader being portable for interacting with a POS or ECR in realizing a payment transaction
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
A transaction processing network that includes multiple transaction terminals having a wireless data communication device, a server, a first network linking the multiple transaction terminals to the server and a second network linking the server to multiple destinations. A first and second protocol are used for the first and second network, respectively, wherein the first protocol has lower overhead than the second protocol. The method of transaction processing by using the transaction processing network.
Description
TRANSACTION PROCESSING USING
INTERMEDIATE SERVER ARCHITECTURE
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates to transaction processing.
2. State of the Art Transaction processing using a point-of-sale (POS) terminal is well-known.
Other types of transactions may be non-financial. In the area of physical security, for example, terminals may be used by patrolmen to check in, producing evidence of their having been in the required place at the required time. Terminals may also be used in the healthcare industry, for example, to produce a record of what medi-cal personnel have attended a patient at what times, or for myriad other purposes.
Transaction processing is used generally herein to refer to the use of a transaction terminal to read, and possibly to write, a record-bearing medium such as a credit card, an ID card, a smart card, etc. The transaction terminal may use a contact or a contactless reading mechanism. In the case of smart cards, for example, a contact-less radio interface of a type known in the art may be used.
The present invention will be described largely in terms of POS transac-tions, since this type of transaction is most familiar.
The approval and "settlement" process for POS transactions involves vari-ous parties and various steps. Briefly, the transaction terminal receives card data and purchase amount data and sends it through a communications network to a transaction processing center ("transaction processor," "front-end processor,"
or "processor"). The transaction processing center switches the transaction to an association (e.g., Visa, Mastercard, etc.) acting on behalf of an issuing bank.
Assuming that the transaction is authorized by or on behalf of the issuing bank, an authorization message is sent back through the transaction processing center and the communications network to the transaction terminal. If the transaction is authorized, "capture" follows in which information from the successful authoriza-tion is used to charge the authorized amount of money to the card. If goods are returned after the transaction has been captured, a "credit" is generated.
Settlement involves a merchant bank and an acquiring bank. The merchant bank has contracted with the merchant to enable the merchant to accept card trans-actions. The acquiring bank processes merchants's card transactions through the financial network on behalf of merchant banks (although in some instances the acquiring bank and the merchant bank may be the same). During settlement, cap-tures and credits, usually accumulated into a "batch," are submitted from the mer-chant to the transaction processing center and on to the issuing and acquiring banks. As part of the settlement process, a "direction letter" may be sent to the U.S: Federal Reserve's Automated Clearing House (ACH) network, advising it as to what debits and credits need to occur in order to complete the transactions in the batch. The card issuer is debited the amount of the sale and the merchant's acquir-ing bank is credited a like amount. The merchant's acquiring bank then credits the merchant's checking account for the amount of the sale less any fees the merchant has agreed to pay for such service.
Referring to Figure l, in the past, transaction terminals have typically been connected through a dial-up connection, through the PSTN (public switched tele-phone network) to a packet switched data network (e.g., an X.25 network) to a transaction processor. The transaction processor is connected in turn to various issuers (e.g., Visa, Mastercard, Discover, etc.) and to various acquiring banks.
Recently, a transaction terminal has been introduced that has a wireless modem-in particular a CDPD (cellular digital packet data) modem-that may be used to establish a connection to a CDPD network, bypassing the PSTN with its accompanying delays and charges. Such an arrangement is shown in Figure 2. The transaction terminal connects wirelessly to a wireless network such as a CDPD
network. The CDPD network includes multiple Mobile Data Base Stations (MDBS) connected to a Mobile Data Intermediate Station (MDIS). The MDIS is connected to a transaction processor via a Frame Relay connection. Frame Relay is used because it is much faster than an X.25 connection.
The system of Figure 2 suffers various disadvantages. In general, the sys-tem does not scale well to meet the needs of "distributed commerce" (or "mobile commerce"). Distributed commerce may be distinguished from e-commerce by a greater element of human involvement. Hence, whereas in e-commerce goods or services are ordered and paid for on-line, in distributed commerce, goods or ser-vices may be ordered in person and paid for by tender of a credit card or other non-cash payment medium, as opposed to the submission by the consumer (e.g., Web submission) of credit card information or the like. Examples of distributed com-merce include such things as flagging a cab and, at the desired destination, paying by credit card, or phoning in an order for pizza and, at the time of delivery, paying by credit card. Other examples of distributed commerce include quick service res-taurants, taxi and limousine services, delivery-based businesses, stadium conces-sions, stand-alone kiosks, and mobile businesses generally.
Like e-commerce, underlying characteristics of distributed commerce should be user convenience, greater satisfaction of demand, and vendor efficiency.
However, various impediments hamper distributed commerce. Whereas the "plumbing" for e-commerce (i.e., the Web) has become almost universally estab-lished, the plumbing for distributed commerce remains ad hoc. A vendor must invest in terminal equipment and terminal softwarelfirmware, enter into a sub-scription agreement with a wireless carrier, and, perhaps most importantly, ensure that a transaction processor is capable of receiving transactions through the wire-less infrastructure, or is willing to invest to create such wireless capability. In the prior art system of Figure 2, for example, transaction processors are typically not equipped to handle Frame Relay traffic, requiring that a new "front end" be pro-vided. ' Furthermore, a vendor's equipment, representing a substantial investment, may rapidly become obsolete. That is, in Figure 2, because intelligence is "hard-wired" into the transaction terminals, the transaction terminals themselves must be replaced, retrofitted or reprogrammed to accommodate new technologies (to accommodate ATM cards in addition to credit cards, to cite a historical example).
Also, in prior art systems, terminal management is cumbersome and labor-intensive. Activating or deactivating a terminal is typically a laborious paper-based process that takes days or weeks. Keeping transaction terminals up and running is also problematic. The only way for a malfunctioning terminal to be identified and fixed is for it to be reported by the merchant, in response to which a service call is scheduled. Except in the most trivial cases, service usually entails replacing the transaction terminal and sending the faulty unit to a service center.
Moreover, in prior art systems, reporting is paper-based at intervals (e.g., monthly) in a fixed (not customizable) format.
Furthermore, today's hard-wired transaction terminals are relatively ineffi-cient in their use of bandwidth.
Hence, although distributed commerce, like e-commerce, should be char-acterized by efficiency, flexibility and adaptability to rapid change, presently it is not.
What is needed, then, is a flexible distributed commerce system architec-ture that is highly efficient, that readily allows for new services to be offered, and that accommodates the existing transaction processor infrastructure.
SUMMARY OF THE INVENTION
The present invention, generally speaking, provides a scalable distributed commerce system architecture for transaction processing. The distributed com-merce system takes advantage of the wireless infrastructure and the Web infra-structure to provide the capabilities of distributed (mobile) commerce along with many of the benefits of e-commerce. Preferably, the system is based on open stan-dards, making possible ubiquitous "any-to-any-to-any" transaction processing in which any compliant transaction terminal can communicate over any suitable wireless carrier and engage any transaction processor to successfully complete a wireless transaction. With the proliferation of wireless technologies, wireless transaction processing is expected to offer high-speed, reliable data transport, lower terminal costs, and lower wireless service costs (as compared to land-line charges). An important feature of the system is that an intermediate server receives data from a transaction terminal and processes the data. The processed data may then be forwarded to a transaction processor. The intermediate server may perform various types of processing, for example data format conversion, protocol conver-sion, etc. The server also makes possible various "value added services,"
e.g., ATM services, e-mail advertising services, customer attrition prevention services, customized reporting services, frequency and loyalty programs, etc. By linking the server to the Web, distributed commerce is able to incorporate the defining attributes of e-commerce, i.e., user convenience, greater satisfaction of demand, vendor efficiency and massive scalability. Parties using the system are able to obtain desired information in real time and take action (e.g., activate and deacti-vate terminals) in near-real time. The intermediate server makes possible the use of a "soft" transaction terminal, i.e., a "thin-client" (or pseudo thin-client) transaction terminal whose characteristics are determined in large part by the server.
Tools are provided to effectively and efficiently manage provisioning, diagnostics, and reporting via a Web browser, enabling merchant acquires and card processors a fast and easy way to offer and manage a wireless transaction processing program with no systems development.
BRIEF DESCRIPTION OF THE DRAWING
The present invention may be further understood from the following description in conjunction with the appended drawing. In the drawing:
Figure 1 is a block diagram of a conventional transaction processing net-work;
Figure 2 is a block diagram of a known transaction processing network using a wireless access point;
Figure 3 is a block diagram of a transaction processing network using a wireless access point and an intermediate server in accordance with one embodiment of the present invention;
Figure 4 is a screen display showing a transaction reporting feature of the system of Figure 3; and Figure 5 is a diagram illustrating a card processor software architecture that may be used in the system of Figure 3.
DETAILED DESCRIPITON OF THE PREFERRED EMBODIMENTS
Referring now to Figure 3, a block diagram is shown of a distributed com-merce system in accordance with one embodiment of the present invention. The distributed commerce system is exemplified by the Wireless Express Payment Ser-vice (WEPSTN') network of the present assignee.
The WEPS network links together wireless terminals, WEPS servers, and transaction processor servers via established transport providers. WEPS
servers are in turn linked to customers (e.g., acquirers, processor, and merchants) via the Internet. Collectively, the WEPS servers function as a value added translation gate-way, enabling any supported terminal to engage in a transaction with any sup-ported transaction processor.
The WEPS network is device neutral and supports all (or at least the most popular) wireless terminals (e.g., Intellect 9770, Lipman 2090, Keycorp K78, Tranz Enabler, etc.). Wireless terminals communicate via wireless networks, e.g., CDPD networks (AT&T, BAM, GTE, Ameritech, etc.), the American Mobile ARDIS network, BellSouth, etc. Currently, different wireless networks lead the market in different regions of the U.S. However, with the proliferation of wireless technologies, options for wireless communication will continue to multiply.
The WEPS network is carrier neutral--i.e., a wireless terminal can use any desired wireless network to communicate to the WEPS servers through the established Wide Area Network communications infrastructure. Wireless coverage may be of world-wide scope using satellite communications. In Figure 3 therefore, a satellite is illustrated as communicating with a satellite Network Operations Center (NOC) which in turn communicates with the established Wide Area Network communica-tions infrastructure.
Although not illustrated in Figure 3, wired transaction terminals may also access the WEPS network through an Internet Service Provider (ISP) or through any or various means, e.g., Internet telephony, etc. In this manner, merchant having wired transaction terminals obtain the benefit of value added services offered by WEPS.
Referring still to Figure 3, wireless networks communicate with WEPS
servers via established transport providers. WEPS servers communicate in turn with various transaction processors, again via established transport providers. As described in relation to the prior art, transaction processors are connected in turn to various issuers (e.g., Visa, Mastercard, Discover, etc.) and to various acquiring banks. In an exemplary embodiment, wired communications is provided between wireless networks, WEPS servers, and transaction processors using Frame Relay technology. Of course, the WAN "backbone" need not be wired (including optical) but, conceivably, may also be wireless.
Just as the WEPS network is device neutral and carrier neutral, the WEPS
network is also transaction processor neutral--i.e., a transaction can be routed to any desired transaction processor, e.g., Paymentech, Nova, Maverick, Lynk Sys-tems, First Data, Global/NDC, Buypass/EPS, etc. A suite of connectivity programs is used to perform format and protocol conversion as necessary between any sup-ported terminal and any supported processor.
WEPS servers are situated at one or more data centers and, at each site, may reside on a Ethernet LAN or other local area network, forming an intranet.
The WEPS system may be based on any suitable intranet architecture may be two-tier, three-tier, etc. The servers are connected to a relational database management system (RDBMS) such as Oracle, for example. The database stores information for individual transaction terminals, identifying the type of terminal, the processor for that terminal, an appropriate connectivity program for enabling communication between the terminal and the transaction processor, etc. This information consti-tutes a terminal "profile." As described more fully hereinafter, the database also stores for transaction terminals thin-client "source programming," e.g., menu prompts, information to be printed, etc.
In addition to translation gateway services (i.e., any necessary message reformatting and protocol conversion), the WEPS servers perform other value added services such as terminal activation (IP activation in the case of CDPD, Radio ID activation in the case of ARDIS), remote diagnostics, transaction report-ing, signature capture, e-mail, etc. Much of the power of the WEPS systems derives from databasing transaction processing information and, in a secure man-ner, making that information available to the "owners" of that information in real time via the Web, and from providing terminal deployment and management capa-bilities via the Web. These purposes are accomplished by connecting the WEPS
servers to the Internet and providing a suite of database-driven Web.tools.
These tools may be custom tools, commercially-available tools, or a combination of both.
To provide custom reporting capabilities, for example, a commercially-available tool, Crystal Reports, available from Seagate Software, may be used. Internet access allows acquirers, processors and merchants to manage terminals, obtain transaction reporting information, perform terminal diagnostics, etc. Figure 4 shows an exemplary screen display illustrating the transaction reporting feature.
In the WEPS system currently, terminal activation and deactivation typi-cally require manual intervention by the wireless network operator. The WEPS
server provides expedited messaging from the customer to the wireless network operator. In the future, tighter integration is expected to eliminate manual interven-tion entirely, resulting in entirely automated activation and deactivation.
Signature capture services enables the WEPS system to improve the chargeback and retrieval request management process that occurs when a card-holder disputes a charge on their statement by capturing and verifying signatures on wireless transactions. E-mail advertising provides a way for a merchant acquirer to quickly and effectively broadcast to merchants promotions about the acquirer's new products and supplies. The range of value added services that may be offered is unlimited.
Additional examples of WEPS value added services include ATM services, customer attrition prevention, and frequency and loyalty programs. Through ATM
services, WEPS servers can provide transaction processing benefits and services to wireless ATM machines. In the case of customer attrition prevention, this service would require the merchant to contact their current acquirer in order to obtain cer-tain password information that would allow the terminal to be switched to another processor. This authorization feature would notify the current acquirer about an unhappy merchant and give the acquirer the opportunity to resolve any problems.
Given the intranet/Internet architecture of the WEPS system, incentive programs can be easily implemented at the POS terminal and processed by the WEPS system in order to encourage additional wireless transactions.
Apart from POS applications, the WEPS system has the capability to han-dle any transaction-based data from any wireless network. Thus, the system can accommodate non-payment applications such as medical claims processing, col-lecting and processing telemetry data for oil, gas and other meter reading applica-tions, coupling dispatch and "panic button" communications with in-vehicle payment processing applications, etc.
In operation of the system of Figure 3, in the case of POS transactions, a WEPS-certified wireless POS terminal transmits card data, merchant data and transaction amount data to the wireless network. The wireless network then for-wards the data packets to a WEPS server, via frame relay for example. The WEPS
server "looks" at the transaction (based on the terminal profile) and determines if protocol conversion, message reformatting, or any other data manipulation is required. If the data needs to be manipulated, the WEPS server performs such functions and then sends the resulting data to the designated transaction processor, again via frame relay for example. If no manipulation is required, the data is merely passed through the WEPS server "as is" in store-and-forward fashion.
Whether the transaction needs manipulation or not, pertinent data is "stripped" and sent to the WEPS database, where real-time reports are created for the acquirer/merchant. These reports can be accessed on a real-time basis via any Web browser.
The transaction processor receives the transaction from WEPS, via frame relay for example, and switches it to the appropriate card issuer for authorization.
Once authorized, the data packet (which now includes an authorization code) is sent back to the transaction processor, which then forwards it back to the WEPS
server. If needed, the protocol conversion/reformatting manipulation process is reversed. The authorization code is added to the WEPS database, and the com-pleted transaction data is sent back to the wireless terminal via frame relay (or other suitable transport mechanism) and the wireless network.
The amount of data manipulation required by the WEPS system is depen-dent on the type of transaction terminal and the identity of the transaction proces-sor. In the simplest case, as in Figure 2, the transaction terminal and the transaction processor are capable of communicating "directly" with one another, i.e., through the combination of wireless and wired transport mechanism but without any trans-lation. In this instance, the WEPS system simply operates in store-and-forward mode. A more difficult case is presented where the transaction terminal assumes one format (e.g., Global) but the transaction is to be routed to a transaction proces-sor that uses a different format (e.g., Maverick). The Global and Maverick formats are described in Appendix A and Appendix B, respectively. In this instance, a first connectivity module (e.g., Global receive module) "parses" the incoming message into its constituent elements. A second connectivity module (e.g., Maverick send module) reassembles some or all of those elements, and possibly other elements stored in the WEPS database, into the appropriate format to send to the transaction processor for that transaction as indicated in the terminal profile stored in the WEPS database.
Message formatting by the server allows for low latency and fast response time. For example, the UDP communications protocol may be used on a network segment between the transaction terminal and the server. The UDP protocol is low overhead and therefore faster than more complex protocols such as X.25 or TCP
In addition, the server may store information about the various transaction termi-nals and use this information to "fill in" various information fields prior to trans-mission to the transaction processor across the second network segment. These fields need not be transmitted on the first network segment from the transaction processor to the server, resulting in higher-speed operation.
Because of the low latency between the transaction terminal and the server, the transaction terminal and the server can function as client/server.
CliendServer is primarily a relationship between processes running on separate machines.
The server process is a provider of services. The client is a consumer of services. In essence, client/server provides a clean separation of function based on the idea of service.
In the context of a transaction processing system, adherence to a cli-ent/server model provides several important advantages. The transaction terminal, instead of being a fairly sophisticated computer, can instead be a relatively "dumb"
terminal, relying on the server for "transaction intelligence." A great economy is therefore achieved. Of perhaps even more importance, adaptability is achieved.
Changes to transaction intelligence can be deployed in one place, on the server, without requiring field modifications to an installed base of transaction terminals.
"Thin client," in one sense, implies a dumb terminal that operates in request/reply mode. In the case of a transaction terminal, data representing hard-ware inputs would be mapped to corresponding replies. For example, in response to an initial card swipe (request), the reply from the server might be "ENTER
AMOUNT," and so forth. In the case of a transaction terminal running off of line power, such an arrangement would be satisfactory (assuming communications latency were sufficiently low to avoid user irritation). In the case of a battery-power transaction terminal, however, such a true thin-client mode of operation consumes excessive power.
In an exemplary embodiment, a thin-client specification for WEPS compli-ant terminal devices is provided. Terminal devices manufacturers desiring to take advantage of the powerful features of the WEPS system can do so by making their terminal equipment WEPS compliant. The specification standardizes the terminal device message format, and over time (as the proportion of WEPS compliant ter-minals increases) is expected to greatly simplify the translation function required to be performed by the WEPS server.
The WEPS thin-client specification provides for one or both of a "pseudo"
thin-client mode of operation and a true thin-client mode of operation. Where both modes are provided, two separate "menus" are defined, mapping hardware inputs to corresponding replies. A first menu governs operation in pseudo thin-client mode. In this mode, replies are downloaded from the server in advance and stored locally in the transaction terminal. Hence, in response to a card being swiped, instead of transmitting card data immediately to the server and waiting for the server's reply, such as "ENTER AMOUNT," the terminal device retrieves the reply (previously downloaded from the server) from its own local memory. This manner of operation preserves the battery life of the transaction terminal.
The "reply" may be output to a display, output to a printer, used to control some aspect of terminal operation, etc.
Despite the menu and replies being stored in the transaction terminal, no loss of flexibility is suffered--the menu can be changed at any time by the server establishing a connection with the terminal and sending new menu information.
A
routine within the terminal parses the new menu information and stores various menu elements in appropriate locations within a non-volatile (NV) memory (e.g., flash memory) of the terminal. Note that menu information is defined on a per ter-minal basis. Thus, in the case of a large merchant having a large number of termi-nals within different departments, the terminals may all be of the same type--(or may be of different types)-- but the programs of those terminals may vary from department to department, for example.
A second (presumably less-used) menu governs operation in true thin-cli-ent mode. In this mode, responses are not stored locally but are sent through the network from the server. This arrangement avoids incurring the cost of local NV
storage for lesser-used options.
Referring to Figure 5, the architecture of card processor software that may be used in the system of Figure 3 is shown. In an exemplary embodiment, the soft-ware is service-based. A socket listener service listens for messages from terminal devices. When the service is begun, database information is stored in memory to enable rapid processing. Changes in the data cause the database to be updated.
When a message is received (DATA ARRIVAL), an execution thread is begun (BEGIN THREAD), causing objects (in this example, COM objects) to be instantiated for the purpose of processing the message. First, the IP
address/ter-minial ID (TID) is validated against the database information stored in memory. If the IP/'TID is not valid, then the packet is dropped. Otherwise, an object is invoked to perform conversion of the data to the appropriate format based on the terminal profile.Depending on which transaction processor is designated, a corresponding conversion object is invoked In the illustrated example, Paymentech is assumed to be the transaction processor of choice. Therefore, the incoming data is converted to Paymentech format and sent to Paymentech. A card validation process ensues, involving, e.g., Paymentech and one or more other downstream processors (e.g., Visa).
If validation fails, then error processing ensues in which an entry is created in an error log. The error log may be set up to send email notification of critical events.
If validation succeeds, an object is invoked to send back to the terminal a validation response in the appropriate format. Latency is reduced by saving response information to the database only after the response has been sent to the terminal. The execution thread is then killed.
If an error occurs during the course of sending the response back to the ter-minal, then error information is returned and logged in the event log.
As has been detailed in the foregoing description, the present transaction processing system provides for ubiquitous "any-to-any-to-any" wireless (as well as wired) transaction processing capability, enabling penetration of new markets such as fast food, mobile merchants, transportation, etc. The resulting mobility and flexibility allows business to be conducted anywhere, with fast transaction times and savings in communication costs. Wireless access may occur through any wire-less data network. The system inter-operates with an unlimited variety of wireless terminal equipment, including handheld units, countertop units, mobile units and new high speed terminal devices. Application flexibility is provided through the use of a thin-client or pseudo thin-client application in the terminal devices. 'Web accessibility allows for easy terminal set-up, on-line activation and provisioning, remote diagnostic capabilities, and real-time transaction reporting, in addition to myriad other value added card services. The system is always on-line, allowing for real-time, up-to-the-minute reporting capability.
It will be appreciated by those of ordinary skill in the art that the invention can be embodied in other specific forms without departing from the spirit or essen-tial character thereof. The presently disclosed embodiments are therefore consid-ered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than the foregoing description, and all changes which come within the meaning and range of equivalents thereof are intended to be embraced therein.
APPENDIX A:
Global Payment Systems--Host Authorization and ECD Message Specification The message contains the following information:
ST1SMSG ~ DT I 8A fD: FS
ID VERSION T FS l CH
~ ~ NG IIC
I
~
R
~~ DA I ID
T D
A
F9 ENTRY FS SWIPE: FS AMOUNT FS
TRACK I, DATA
MODE MANUAL: 1 ACCT
E
FS
ii EXP
DATE
A?fODN? FS ACQ FS AVS FS 19CTF6 REF
DATA INFO DATA
S ~5 CLERK FS M T7C LRC
~ ~~ R ~~
E
ID ~
E
P
.. . ~~
STX Start of Text Ind'~cator. Required for dial-up. Not used on leased 1(nes.
Message ID Required. Always' (literal').
Version Required. Level version of the message (02).
Routing Data Optional user-definable data Echoed in Global's response unaltered.
FS Field Separator Bank ID Required Identifies &digit Bank ID assigned by Global.
Merchant ID Required. Unique numt~er identiffying merchant device.
FS Field Separator Temwrel Type Required. Global-assigned code ir~cating type of POS device.
Proving Code Required. Code that designates processing instrtx0ons.
FS Field Separator POS Entry Mode Required. Code indicating POS device characteristics.
FS Field Separator Swipe: Track Data Conditional. Required if swiped. The data encoded on Track 1 or Track 2.
Manual: Account Conditional. Required it manually keyed.
Number The account nrunber.
Manual: FS Conditional. Required it manually keyed Field Separator ..,ManuaL.Expiration.DateConditional. The expiration date. Present "'..'.'--'..-. on keyed transactions ('rf available).
FS Feid Separator Field . Description Amount 1 Required. The total amount of the transaction, induding Amount 2.
FS Field Separator Amount 2 Optional. Additional amount already mduded in Amount t. Forreporting purposes.
(example, tip amount) FS Field Separator ' Acquirer ReferenceConditional. Data varies by card type and Data market I~~A~-FS Field Separator AVS Information Conditional. 9 character ap and 20 character street address.
FS Field Separator Market Data Conditional for non-signature capture transactions.
Defined by market ~11~
Required for signature rapture transactions.
Sub-field y contains the Transaction Reference Number, which is used to identify signature capture data throughout the life cycle of the transaction.
FS Field Separator Shift ID Optional. Shift ID number.
FS Feid Separator Clerk ID Optional. Clerk i0 number.
FS Fcekl Separator Merchant Type Optional. Merchant Category Code.
ETX. End of Text Indcator. Required for dial-up.
Not used on leased lines.
LRC Longitudinal Redundancy Check Character.
Required for dal-up. Not used on leased fines.
Global HOST AUTHORIZATION AND EDC MESSAGE SPECIFICATIONS, Ver 2. 7, Rel 5,197 Copyright o f997 Globar Payment systems WO 01/39072 ~ 8 PCT/US00/31656 APPENDIX B:
Maverick International--Maverick Protocol Authorization requests using Maverick's proprietary authorization request record "M" will receive the standard Visa 2"~ generation "L° response record. Terminals using Maverick's "M" authorization requtst format will capture the Authorization Code (field 9) and the Retrizval Reference Number (field l~i) for settlement, but may capture other fields as necessary (such as the Transaction ID and Validation Code) for pzrforming incremental authorizations.
Field name descriptions are e:cplained by section in this document. Data format designations: A=
Alphanumeric, N=Numeric.
Field Fleld Natne Data Data SeMionTxampte iYumber Format Length .
' 1 Record FormatA 1 4.1 M
2 Application A I 4.2 0 Type 3 Message DelimiterA 1 4.3 d Acquirer N 6 4.4 "123456"
Bin Terminal N 10 4.5 "9999999901"
Number 6 Field SeparatorA I 4.6 <FS> or HEX 1 C
7 Transaction N 4 4.7- 0001 ~
Sequence Number 8 Transaction A 2 4.8 "54"
Code 9 Cardholder A 1 4.9 "~"
ID Code l0 Account DataA 1 4.10 D
Source t Code ;
1 l Customer A 1-80 ~l.1 JOHNSMITH
Data Field I
12 Field SeparatorA I 4.6 <FS> or HEX 1 C
13 Address VerificationSee SectionSee 4.12 1234MAINST'REET123456789 ~ 4.13 Section OR
OR 4.12 123456 (Auth Code) Authorization Code ~
I4.1 Field SeparatorA 1 4.6 <FS> or HEX 1C
14.? Transaction A 0 to 4.13 Processing 4 Indicators l5 Field SeparatorA 1 4.6 <FS> or HEX 1 C
16 Transaction N 0 to 4.14 Amount 12 17 Field SeparatorA 1 4.6 <FS> or HEX 1 C
18 . Secondary N 0 to 4.15 Amount 12 19 Field SeparatorA 1 4.6 <FS> or HEX 1C
20 Market S A 0 or 4.16 ecific Data 4 t .
31 I Field Separator 1 ~l.b <FS> or HEX 1C
' A
22 ( lnfotmational 0-60 Data ~ A . 4.
l7 23 Field Separator I ~ <FS> or HEX 1 C
A d.6 24 Original 0 or Reference 12 t N ~ =1.18 Number 25 Field Separator 1 I <FS> or HEX 1C
A 4.6 26 I Purchasing 0-17 I Card I A ( x.19 Data 27 Field Separator 1 4.6 <FS> or HEX 1C
A
28 ! Free Form 0-45 Data A 4?0 29 Field Separator 1 -4.6 <FS> or HEX 1C
A
ttuv. D trsi99.1:.~D Phl Nlavcrivl: Protocol V2? Paga 8 of 39 ~D 1y99 'lavcrick tnternationa!
INTERMEDIATE SERVER ARCHITECTURE
BACKGROUND OF THE INVENTION
1. Field of the Invention The present invention relates to transaction processing.
2. State of the Art Transaction processing using a point-of-sale (POS) terminal is well-known.
Other types of transactions may be non-financial. In the area of physical security, for example, terminals may be used by patrolmen to check in, producing evidence of their having been in the required place at the required time. Terminals may also be used in the healthcare industry, for example, to produce a record of what medi-cal personnel have attended a patient at what times, or for myriad other purposes.
Transaction processing is used generally herein to refer to the use of a transaction terminal to read, and possibly to write, a record-bearing medium such as a credit card, an ID card, a smart card, etc. The transaction terminal may use a contact or a contactless reading mechanism. In the case of smart cards, for example, a contact-less radio interface of a type known in the art may be used.
The present invention will be described largely in terms of POS transac-tions, since this type of transaction is most familiar.
The approval and "settlement" process for POS transactions involves vari-ous parties and various steps. Briefly, the transaction terminal receives card data and purchase amount data and sends it through a communications network to a transaction processing center ("transaction processor," "front-end processor,"
or "processor"). The transaction processing center switches the transaction to an association (e.g., Visa, Mastercard, etc.) acting on behalf of an issuing bank.
Assuming that the transaction is authorized by or on behalf of the issuing bank, an authorization message is sent back through the transaction processing center and the communications network to the transaction terminal. If the transaction is authorized, "capture" follows in which information from the successful authoriza-tion is used to charge the authorized amount of money to the card. If goods are returned after the transaction has been captured, a "credit" is generated.
Settlement involves a merchant bank and an acquiring bank. The merchant bank has contracted with the merchant to enable the merchant to accept card trans-actions. The acquiring bank processes merchants's card transactions through the financial network on behalf of merchant banks (although in some instances the acquiring bank and the merchant bank may be the same). During settlement, cap-tures and credits, usually accumulated into a "batch," are submitted from the mer-chant to the transaction processing center and on to the issuing and acquiring banks. As part of the settlement process, a "direction letter" may be sent to the U.S: Federal Reserve's Automated Clearing House (ACH) network, advising it as to what debits and credits need to occur in order to complete the transactions in the batch. The card issuer is debited the amount of the sale and the merchant's acquir-ing bank is credited a like amount. The merchant's acquiring bank then credits the merchant's checking account for the amount of the sale less any fees the merchant has agreed to pay for such service.
Referring to Figure l, in the past, transaction terminals have typically been connected through a dial-up connection, through the PSTN (public switched tele-phone network) to a packet switched data network (e.g., an X.25 network) to a transaction processor. The transaction processor is connected in turn to various issuers (e.g., Visa, Mastercard, Discover, etc.) and to various acquiring banks.
Recently, a transaction terminal has been introduced that has a wireless modem-in particular a CDPD (cellular digital packet data) modem-that may be used to establish a connection to a CDPD network, bypassing the PSTN with its accompanying delays and charges. Such an arrangement is shown in Figure 2. The transaction terminal connects wirelessly to a wireless network such as a CDPD
network. The CDPD network includes multiple Mobile Data Base Stations (MDBS) connected to a Mobile Data Intermediate Station (MDIS). The MDIS is connected to a transaction processor via a Frame Relay connection. Frame Relay is used because it is much faster than an X.25 connection.
The system of Figure 2 suffers various disadvantages. In general, the sys-tem does not scale well to meet the needs of "distributed commerce" (or "mobile commerce"). Distributed commerce may be distinguished from e-commerce by a greater element of human involvement. Hence, whereas in e-commerce goods or services are ordered and paid for on-line, in distributed commerce, goods or ser-vices may be ordered in person and paid for by tender of a credit card or other non-cash payment medium, as opposed to the submission by the consumer (e.g., Web submission) of credit card information or the like. Examples of distributed com-merce include such things as flagging a cab and, at the desired destination, paying by credit card, or phoning in an order for pizza and, at the time of delivery, paying by credit card. Other examples of distributed commerce include quick service res-taurants, taxi and limousine services, delivery-based businesses, stadium conces-sions, stand-alone kiosks, and mobile businesses generally.
Like e-commerce, underlying characteristics of distributed commerce should be user convenience, greater satisfaction of demand, and vendor efficiency.
However, various impediments hamper distributed commerce. Whereas the "plumbing" for e-commerce (i.e., the Web) has become almost universally estab-lished, the plumbing for distributed commerce remains ad hoc. A vendor must invest in terminal equipment and terminal softwarelfirmware, enter into a sub-scription agreement with a wireless carrier, and, perhaps most importantly, ensure that a transaction processor is capable of receiving transactions through the wire-less infrastructure, or is willing to invest to create such wireless capability. In the prior art system of Figure 2, for example, transaction processors are typically not equipped to handle Frame Relay traffic, requiring that a new "front end" be pro-vided. ' Furthermore, a vendor's equipment, representing a substantial investment, may rapidly become obsolete. That is, in Figure 2, because intelligence is "hard-wired" into the transaction terminals, the transaction terminals themselves must be replaced, retrofitted or reprogrammed to accommodate new technologies (to accommodate ATM cards in addition to credit cards, to cite a historical example).
Also, in prior art systems, terminal management is cumbersome and labor-intensive. Activating or deactivating a terminal is typically a laborious paper-based process that takes days or weeks. Keeping transaction terminals up and running is also problematic. The only way for a malfunctioning terminal to be identified and fixed is for it to be reported by the merchant, in response to which a service call is scheduled. Except in the most trivial cases, service usually entails replacing the transaction terminal and sending the faulty unit to a service center.
Moreover, in prior art systems, reporting is paper-based at intervals (e.g., monthly) in a fixed (not customizable) format.
Furthermore, today's hard-wired transaction terminals are relatively ineffi-cient in their use of bandwidth.
Hence, although distributed commerce, like e-commerce, should be char-acterized by efficiency, flexibility and adaptability to rapid change, presently it is not.
What is needed, then, is a flexible distributed commerce system architec-ture that is highly efficient, that readily allows for new services to be offered, and that accommodates the existing transaction processor infrastructure.
SUMMARY OF THE INVENTION
The present invention, generally speaking, provides a scalable distributed commerce system architecture for transaction processing. The distributed com-merce system takes advantage of the wireless infrastructure and the Web infra-structure to provide the capabilities of distributed (mobile) commerce along with many of the benefits of e-commerce. Preferably, the system is based on open stan-dards, making possible ubiquitous "any-to-any-to-any" transaction processing in which any compliant transaction terminal can communicate over any suitable wireless carrier and engage any transaction processor to successfully complete a wireless transaction. With the proliferation of wireless technologies, wireless transaction processing is expected to offer high-speed, reliable data transport, lower terminal costs, and lower wireless service costs (as compared to land-line charges). An important feature of the system is that an intermediate server receives data from a transaction terminal and processes the data. The processed data may then be forwarded to a transaction processor. The intermediate server may perform various types of processing, for example data format conversion, protocol conver-sion, etc. The server also makes possible various "value added services,"
e.g., ATM services, e-mail advertising services, customer attrition prevention services, customized reporting services, frequency and loyalty programs, etc. By linking the server to the Web, distributed commerce is able to incorporate the defining attributes of e-commerce, i.e., user convenience, greater satisfaction of demand, vendor efficiency and massive scalability. Parties using the system are able to obtain desired information in real time and take action (e.g., activate and deacti-vate terminals) in near-real time. The intermediate server makes possible the use of a "soft" transaction terminal, i.e., a "thin-client" (or pseudo thin-client) transaction terminal whose characteristics are determined in large part by the server.
Tools are provided to effectively and efficiently manage provisioning, diagnostics, and reporting via a Web browser, enabling merchant acquires and card processors a fast and easy way to offer and manage a wireless transaction processing program with no systems development.
BRIEF DESCRIPTION OF THE DRAWING
The present invention may be further understood from the following description in conjunction with the appended drawing. In the drawing:
Figure 1 is a block diagram of a conventional transaction processing net-work;
Figure 2 is a block diagram of a known transaction processing network using a wireless access point;
Figure 3 is a block diagram of a transaction processing network using a wireless access point and an intermediate server in accordance with one embodiment of the present invention;
Figure 4 is a screen display showing a transaction reporting feature of the system of Figure 3; and Figure 5 is a diagram illustrating a card processor software architecture that may be used in the system of Figure 3.
DETAILED DESCRIPITON OF THE PREFERRED EMBODIMENTS
Referring now to Figure 3, a block diagram is shown of a distributed com-merce system in accordance with one embodiment of the present invention. The distributed commerce system is exemplified by the Wireless Express Payment Ser-vice (WEPSTN') network of the present assignee.
The WEPS network links together wireless terminals, WEPS servers, and transaction processor servers via established transport providers. WEPS
servers are in turn linked to customers (e.g., acquirers, processor, and merchants) via the Internet. Collectively, the WEPS servers function as a value added translation gate-way, enabling any supported terminal to engage in a transaction with any sup-ported transaction processor.
The WEPS network is device neutral and supports all (or at least the most popular) wireless terminals (e.g., Intellect 9770, Lipman 2090, Keycorp K78, Tranz Enabler, etc.). Wireless terminals communicate via wireless networks, e.g., CDPD networks (AT&T, BAM, GTE, Ameritech, etc.), the American Mobile ARDIS network, BellSouth, etc. Currently, different wireless networks lead the market in different regions of the U.S. However, with the proliferation of wireless technologies, options for wireless communication will continue to multiply.
The WEPS network is carrier neutral--i.e., a wireless terminal can use any desired wireless network to communicate to the WEPS servers through the established Wide Area Network communications infrastructure. Wireless coverage may be of world-wide scope using satellite communications. In Figure 3 therefore, a satellite is illustrated as communicating with a satellite Network Operations Center (NOC) which in turn communicates with the established Wide Area Network communica-tions infrastructure.
Although not illustrated in Figure 3, wired transaction terminals may also access the WEPS network through an Internet Service Provider (ISP) or through any or various means, e.g., Internet telephony, etc. In this manner, merchant having wired transaction terminals obtain the benefit of value added services offered by WEPS.
Referring still to Figure 3, wireless networks communicate with WEPS
servers via established transport providers. WEPS servers communicate in turn with various transaction processors, again via established transport providers. As described in relation to the prior art, transaction processors are connected in turn to various issuers (e.g., Visa, Mastercard, Discover, etc.) and to various acquiring banks. In an exemplary embodiment, wired communications is provided between wireless networks, WEPS servers, and transaction processors using Frame Relay technology. Of course, the WAN "backbone" need not be wired (including optical) but, conceivably, may also be wireless.
Just as the WEPS network is device neutral and carrier neutral, the WEPS
network is also transaction processor neutral--i.e., a transaction can be routed to any desired transaction processor, e.g., Paymentech, Nova, Maverick, Lynk Sys-tems, First Data, Global/NDC, Buypass/EPS, etc. A suite of connectivity programs is used to perform format and protocol conversion as necessary between any sup-ported terminal and any supported processor.
WEPS servers are situated at one or more data centers and, at each site, may reside on a Ethernet LAN or other local area network, forming an intranet.
The WEPS system may be based on any suitable intranet architecture may be two-tier, three-tier, etc. The servers are connected to a relational database management system (RDBMS) such as Oracle, for example. The database stores information for individual transaction terminals, identifying the type of terminal, the processor for that terminal, an appropriate connectivity program for enabling communication between the terminal and the transaction processor, etc. This information consti-tutes a terminal "profile." As described more fully hereinafter, the database also stores for transaction terminals thin-client "source programming," e.g., menu prompts, information to be printed, etc.
In addition to translation gateway services (i.e., any necessary message reformatting and protocol conversion), the WEPS servers perform other value added services such as terminal activation (IP activation in the case of CDPD, Radio ID activation in the case of ARDIS), remote diagnostics, transaction report-ing, signature capture, e-mail, etc. Much of the power of the WEPS systems derives from databasing transaction processing information and, in a secure man-ner, making that information available to the "owners" of that information in real time via the Web, and from providing terminal deployment and management capa-bilities via the Web. These purposes are accomplished by connecting the WEPS
servers to the Internet and providing a suite of database-driven Web.tools.
These tools may be custom tools, commercially-available tools, or a combination of both.
To provide custom reporting capabilities, for example, a commercially-available tool, Crystal Reports, available from Seagate Software, may be used. Internet access allows acquirers, processors and merchants to manage terminals, obtain transaction reporting information, perform terminal diagnostics, etc. Figure 4 shows an exemplary screen display illustrating the transaction reporting feature.
In the WEPS system currently, terminal activation and deactivation typi-cally require manual intervention by the wireless network operator. The WEPS
server provides expedited messaging from the customer to the wireless network operator. In the future, tighter integration is expected to eliminate manual interven-tion entirely, resulting in entirely automated activation and deactivation.
Signature capture services enables the WEPS system to improve the chargeback and retrieval request management process that occurs when a card-holder disputes a charge on their statement by capturing and verifying signatures on wireless transactions. E-mail advertising provides a way for a merchant acquirer to quickly and effectively broadcast to merchants promotions about the acquirer's new products and supplies. The range of value added services that may be offered is unlimited.
Additional examples of WEPS value added services include ATM services, customer attrition prevention, and frequency and loyalty programs. Through ATM
services, WEPS servers can provide transaction processing benefits and services to wireless ATM machines. In the case of customer attrition prevention, this service would require the merchant to contact their current acquirer in order to obtain cer-tain password information that would allow the terminal to be switched to another processor. This authorization feature would notify the current acquirer about an unhappy merchant and give the acquirer the opportunity to resolve any problems.
Given the intranet/Internet architecture of the WEPS system, incentive programs can be easily implemented at the POS terminal and processed by the WEPS system in order to encourage additional wireless transactions.
Apart from POS applications, the WEPS system has the capability to han-dle any transaction-based data from any wireless network. Thus, the system can accommodate non-payment applications such as medical claims processing, col-lecting and processing telemetry data for oil, gas and other meter reading applica-tions, coupling dispatch and "panic button" communications with in-vehicle payment processing applications, etc.
In operation of the system of Figure 3, in the case of POS transactions, a WEPS-certified wireless POS terminal transmits card data, merchant data and transaction amount data to the wireless network. The wireless network then for-wards the data packets to a WEPS server, via frame relay for example. The WEPS
server "looks" at the transaction (based on the terminal profile) and determines if protocol conversion, message reformatting, or any other data manipulation is required. If the data needs to be manipulated, the WEPS server performs such functions and then sends the resulting data to the designated transaction processor, again via frame relay for example. If no manipulation is required, the data is merely passed through the WEPS server "as is" in store-and-forward fashion.
Whether the transaction needs manipulation or not, pertinent data is "stripped" and sent to the WEPS database, where real-time reports are created for the acquirer/merchant. These reports can be accessed on a real-time basis via any Web browser.
The transaction processor receives the transaction from WEPS, via frame relay for example, and switches it to the appropriate card issuer for authorization.
Once authorized, the data packet (which now includes an authorization code) is sent back to the transaction processor, which then forwards it back to the WEPS
server. If needed, the protocol conversion/reformatting manipulation process is reversed. The authorization code is added to the WEPS database, and the com-pleted transaction data is sent back to the wireless terminal via frame relay (or other suitable transport mechanism) and the wireless network.
The amount of data manipulation required by the WEPS system is depen-dent on the type of transaction terminal and the identity of the transaction proces-sor. In the simplest case, as in Figure 2, the transaction terminal and the transaction processor are capable of communicating "directly" with one another, i.e., through the combination of wireless and wired transport mechanism but without any trans-lation. In this instance, the WEPS system simply operates in store-and-forward mode. A more difficult case is presented where the transaction terminal assumes one format (e.g., Global) but the transaction is to be routed to a transaction proces-sor that uses a different format (e.g., Maverick). The Global and Maverick formats are described in Appendix A and Appendix B, respectively. In this instance, a first connectivity module (e.g., Global receive module) "parses" the incoming message into its constituent elements. A second connectivity module (e.g., Maverick send module) reassembles some or all of those elements, and possibly other elements stored in the WEPS database, into the appropriate format to send to the transaction processor for that transaction as indicated in the terminal profile stored in the WEPS database.
Message formatting by the server allows for low latency and fast response time. For example, the UDP communications protocol may be used on a network segment between the transaction terminal and the server. The UDP protocol is low overhead and therefore faster than more complex protocols such as X.25 or TCP
In addition, the server may store information about the various transaction termi-nals and use this information to "fill in" various information fields prior to trans-mission to the transaction processor across the second network segment. These fields need not be transmitted on the first network segment from the transaction processor to the server, resulting in higher-speed operation.
Because of the low latency between the transaction terminal and the server, the transaction terminal and the server can function as client/server.
CliendServer is primarily a relationship between processes running on separate machines.
The server process is a provider of services. The client is a consumer of services. In essence, client/server provides a clean separation of function based on the idea of service.
In the context of a transaction processing system, adherence to a cli-ent/server model provides several important advantages. The transaction terminal, instead of being a fairly sophisticated computer, can instead be a relatively "dumb"
terminal, relying on the server for "transaction intelligence." A great economy is therefore achieved. Of perhaps even more importance, adaptability is achieved.
Changes to transaction intelligence can be deployed in one place, on the server, without requiring field modifications to an installed base of transaction terminals.
"Thin client," in one sense, implies a dumb terminal that operates in request/reply mode. In the case of a transaction terminal, data representing hard-ware inputs would be mapped to corresponding replies. For example, in response to an initial card swipe (request), the reply from the server might be "ENTER
AMOUNT," and so forth. In the case of a transaction terminal running off of line power, such an arrangement would be satisfactory (assuming communications latency were sufficiently low to avoid user irritation). In the case of a battery-power transaction terminal, however, such a true thin-client mode of operation consumes excessive power.
In an exemplary embodiment, a thin-client specification for WEPS compli-ant terminal devices is provided. Terminal devices manufacturers desiring to take advantage of the powerful features of the WEPS system can do so by making their terminal equipment WEPS compliant. The specification standardizes the terminal device message format, and over time (as the proportion of WEPS compliant ter-minals increases) is expected to greatly simplify the translation function required to be performed by the WEPS server.
The WEPS thin-client specification provides for one or both of a "pseudo"
thin-client mode of operation and a true thin-client mode of operation. Where both modes are provided, two separate "menus" are defined, mapping hardware inputs to corresponding replies. A first menu governs operation in pseudo thin-client mode. In this mode, replies are downloaded from the server in advance and stored locally in the transaction terminal. Hence, in response to a card being swiped, instead of transmitting card data immediately to the server and waiting for the server's reply, such as "ENTER AMOUNT," the terminal device retrieves the reply (previously downloaded from the server) from its own local memory. This manner of operation preserves the battery life of the transaction terminal.
The "reply" may be output to a display, output to a printer, used to control some aspect of terminal operation, etc.
Despite the menu and replies being stored in the transaction terminal, no loss of flexibility is suffered--the menu can be changed at any time by the server establishing a connection with the terminal and sending new menu information.
A
routine within the terminal parses the new menu information and stores various menu elements in appropriate locations within a non-volatile (NV) memory (e.g., flash memory) of the terminal. Note that menu information is defined on a per ter-minal basis. Thus, in the case of a large merchant having a large number of termi-nals within different departments, the terminals may all be of the same type--(or may be of different types)-- but the programs of those terminals may vary from department to department, for example.
A second (presumably less-used) menu governs operation in true thin-cli-ent mode. In this mode, responses are not stored locally but are sent through the network from the server. This arrangement avoids incurring the cost of local NV
storage for lesser-used options.
Referring to Figure 5, the architecture of card processor software that may be used in the system of Figure 3 is shown. In an exemplary embodiment, the soft-ware is service-based. A socket listener service listens for messages from terminal devices. When the service is begun, database information is stored in memory to enable rapid processing. Changes in the data cause the database to be updated.
When a message is received (DATA ARRIVAL), an execution thread is begun (BEGIN THREAD), causing objects (in this example, COM objects) to be instantiated for the purpose of processing the message. First, the IP
address/ter-minial ID (TID) is validated against the database information stored in memory. If the IP/'TID is not valid, then the packet is dropped. Otherwise, an object is invoked to perform conversion of the data to the appropriate format based on the terminal profile.Depending on which transaction processor is designated, a corresponding conversion object is invoked In the illustrated example, Paymentech is assumed to be the transaction processor of choice. Therefore, the incoming data is converted to Paymentech format and sent to Paymentech. A card validation process ensues, involving, e.g., Paymentech and one or more other downstream processors (e.g., Visa).
If validation fails, then error processing ensues in which an entry is created in an error log. The error log may be set up to send email notification of critical events.
If validation succeeds, an object is invoked to send back to the terminal a validation response in the appropriate format. Latency is reduced by saving response information to the database only after the response has been sent to the terminal. The execution thread is then killed.
If an error occurs during the course of sending the response back to the ter-minal, then error information is returned and logged in the event log.
As has been detailed in the foregoing description, the present transaction processing system provides for ubiquitous "any-to-any-to-any" wireless (as well as wired) transaction processing capability, enabling penetration of new markets such as fast food, mobile merchants, transportation, etc. The resulting mobility and flexibility allows business to be conducted anywhere, with fast transaction times and savings in communication costs. Wireless access may occur through any wire-less data network. The system inter-operates with an unlimited variety of wireless terminal equipment, including handheld units, countertop units, mobile units and new high speed terminal devices. Application flexibility is provided through the use of a thin-client or pseudo thin-client application in the terminal devices. 'Web accessibility allows for easy terminal set-up, on-line activation and provisioning, remote diagnostic capabilities, and real-time transaction reporting, in addition to myriad other value added card services. The system is always on-line, allowing for real-time, up-to-the-minute reporting capability.
It will be appreciated by those of ordinary skill in the art that the invention can be embodied in other specific forms without departing from the spirit or essen-tial character thereof. The presently disclosed embodiments are therefore consid-ered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than the foregoing description, and all changes which come within the meaning and range of equivalents thereof are intended to be embraced therein.
APPENDIX A:
Global Payment Systems--Host Authorization and ECD Message Specification The message contains the following information:
ST1SMSG ~ DT I 8A fD: FS
ID VERSION T FS l CH
~ ~ NG IIC
I
~
R
~~ DA I ID
T D
A
F9 ENTRY FS SWIPE: FS AMOUNT FS
TRACK I, DATA
MODE MANUAL: 1 ACCT
E
FS
ii EXP
DATE
A?fODN? FS ACQ FS AVS FS 19CTF6 REF
DATA INFO DATA
S ~5 CLERK FS M T7C LRC
~ ~~ R ~~
E
ID ~
E
P
.. . ~~
STX Start of Text Ind'~cator. Required for dial-up. Not used on leased 1(nes.
Message ID Required. Always' (literal').
Version Required. Level version of the message (02).
Routing Data Optional user-definable data Echoed in Global's response unaltered.
FS Field Separator Bank ID Required Identifies &digit Bank ID assigned by Global.
Merchant ID Required. Unique numt~er identiffying merchant device.
FS Field Separator Temwrel Type Required. Global-assigned code ir~cating type of POS device.
Proving Code Required. Code that designates processing instrtx0ons.
FS Field Separator POS Entry Mode Required. Code indicating POS device characteristics.
FS Field Separator Swipe: Track Data Conditional. Required if swiped. The data encoded on Track 1 or Track 2.
Manual: Account Conditional. Required it manually keyed.
Number The account nrunber.
Manual: FS Conditional. Required it manually keyed Field Separator ..,ManuaL.Expiration.DateConditional. The expiration date. Present "'..'.'--'..-. on keyed transactions ('rf available).
FS Feid Separator Field . Description Amount 1 Required. The total amount of the transaction, induding Amount 2.
FS Field Separator Amount 2 Optional. Additional amount already mduded in Amount t. Forreporting purposes.
(example, tip amount) FS Field Separator ' Acquirer ReferenceConditional. Data varies by card type and Data market I~~A~-FS Field Separator AVS Information Conditional. 9 character ap and 20 character street address.
FS Field Separator Market Data Conditional for non-signature capture transactions.
Defined by market ~11~
Required for signature rapture transactions.
Sub-field y contains the Transaction Reference Number, which is used to identify signature capture data throughout the life cycle of the transaction.
FS Field Separator Shift ID Optional. Shift ID number.
FS Feid Separator Clerk ID Optional. Clerk i0 number.
FS Fcekl Separator Merchant Type Optional. Merchant Category Code.
ETX. End of Text Indcator. Required for dial-up.
Not used on leased lines.
LRC Longitudinal Redundancy Check Character.
Required for dal-up. Not used on leased fines.
Global HOST AUTHORIZATION AND EDC MESSAGE SPECIFICATIONS, Ver 2. 7, Rel 5,197 Copyright o f997 Globar Payment systems WO 01/39072 ~ 8 PCT/US00/31656 APPENDIX B:
Maverick International--Maverick Protocol Authorization requests using Maverick's proprietary authorization request record "M" will receive the standard Visa 2"~ generation "L° response record. Terminals using Maverick's "M" authorization requtst format will capture the Authorization Code (field 9) and the Retrizval Reference Number (field l~i) for settlement, but may capture other fields as necessary (such as the Transaction ID and Validation Code) for pzrforming incremental authorizations.
Field name descriptions are e:cplained by section in this document. Data format designations: A=
Alphanumeric, N=Numeric.
Field Fleld Natne Data Data SeMionTxampte iYumber Format Length .
' 1 Record FormatA 1 4.1 M
2 Application A I 4.2 0 Type 3 Message DelimiterA 1 4.3 d Acquirer N 6 4.4 "123456"
Bin Terminal N 10 4.5 "9999999901"
Number 6 Field SeparatorA I 4.6 <FS> or HEX 1 C
7 Transaction N 4 4.7- 0001 ~
Sequence Number 8 Transaction A 2 4.8 "54"
Code 9 Cardholder A 1 4.9 "~"
ID Code l0 Account DataA 1 4.10 D
Source t Code ;
1 l Customer A 1-80 ~l.1 JOHNSMITH
Data Field I
12 Field SeparatorA I 4.6 <FS> or HEX 1 C
13 Address VerificationSee SectionSee 4.12 1234MAINST'REET123456789 ~ 4.13 Section OR
OR 4.12 123456 (Auth Code) Authorization Code ~
I4.1 Field SeparatorA 1 4.6 <FS> or HEX 1C
14.? Transaction A 0 to 4.13 Processing 4 Indicators l5 Field SeparatorA 1 4.6 <FS> or HEX 1 C
16 Transaction N 0 to 4.14 Amount 12 17 Field SeparatorA 1 4.6 <FS> or HEX 1 C
18 . Secondary N 0 to 4.15 Amount 12 19 Field SeparatorA 1 4.6 <FS> or HEX 1C
20 Market S A 0 or 4.16 ecific Data 4 t .
31 I Field Separator 1 ~l.b <FS> or HEX 1C
' A
22 ( lnfotmational 0-60 Data ~ A . 4.
l7 23 Field Separator I ~ <FS> or HEX 1 C
A d.6 24 Original 0 or Reference 12 t N ~ =1.18 Number 25 Field Separator 1 I <FS> or HEX 1C
A 4.6 26 I Purchasing 0-17 I Card I A ( x.19 Data 27 Field Separator 1 4.6 <FS> or HEX 1C
A
28 ! Free Form 0-45 Data A 4?0 29 Field Separator 1 -4.6 <FS> or HEX 1C
A
ttuv. D trsi99.1:.~D Phl Nlavcrivl: Protocol V2? Paga 8 of 39 ~D 1y99 'lavcrick tnternationa!
Claims (26)
1. A method of transaction processing, comprising:
a user bringing a record-bearing medium in operational proximity to a transaction terminal to allow the transaction terminal to receive infor-mation from the record-bearing medium;
the transaction terminal accessing a communications network and sending first transaction information across the communications network;
receiving and processing the first transaction information at a server; and the server sending second transaction information to a further desti-nation.
a user bringing a record-bearing medium in operational proximity to a transaction terminal to allow the transaction terminal to receive infor-mation from the record-bearing medium;
the transaction terminal accessing a communications network and sending first transaction information across the communications network;
receiving and processing the first transaction information at a server; and the server sending second transaction information to a further desti-nation.
2. The method of Claim 1, wherein the further destination is a transac-tion processor installation.
3. The method of Claim 1, wherein the transaction terminal wirelessly accesses the communications network.
4. The method of Claim 1, wherein the transaction terminal includes an output device, and the server controls presentation of information to a user through the output device.
5. The method of Claim 4, wherein the output device is a display.
6. The method of Claim 1, wherein the first transaction information is transported using a first protocol, and the second transaction information is trans-ported using a second different protocol.
7. The method of Claim 6, wherein the first protocol has lower over-head than the second protocol.
8. The method of Claim 1, wherein the first transaction information is in a first format, and the second transaction information is in a second different format, further comprising the server reformatting the transaction information from the first format to the second format.
9. The method of Claim 8, wherein the first format is more compact than the second format.
10. The method of Claim 9, wherein the server stores locally informa-tion about various transaction terminals and uses this information to reformat the transaction information from the first format to the second format.
11. The method of Claim 1, further comprising the server capturing and storing transaction information.
12. The method of Claim 11, further comprising providing customers secure access to their respective transaction information via a Web browser.
13. The method of Claim 12, wherein transaction information is made available to customers in real time as it is captured and stored by the server.
14. The method of Claim 1, further comprising:
a customer communicating via the Web to the server a desired action with respect to a transaction terminal; and the server communicating with one of a wireless network and a transaction terminal to carry out the desired action.
a customer communicating via the Web to the server a desired action with respect to a transaction terminal; and the server communicating with one of a wireless network and a transaction terminal to carry out the desired action.
15. The method of Claim 14, wherein the desired action is terminal activation/deactivation.
16. The method of Claim 14, wherein the desired action is terminal diagnostics.
17. A transaction processing network, comprising:
multiple transaction terminals wherein a user bringing a record-bearing medium in operational proximity to a transaction terminal to allow the transaction terminal to receive information from the record-bearing medium;
a server;
a first network segment linking multiple transaction terminals to the server; and a second network segment linking the server to multiple further destinations.
multiple transaction terminals wherein a user bringing a record-bearing medium in operational proximity to a transaction terminal to allow the transaction terminal to receive information from the record-bearing medium;
a server;
a first network segment linking multiple transaction terminals to the server; and a second network segment linking the server to multiple further destinations.
18. The apparatus of Claim 17, wherein at least one of the further desti-nations is a transaction processor installation.
19. The apparatus of Claim 17, wherein the transaction terminal com-prises a wireless data communications device.
20. The apparatus of Claim 17, wherein the transaction terminal includes an output device, and the server controls presentation of information to a user through the output device.
21. The apparatus of Claim 20, wherein the output device is a display.
22. The apparatus of Claim 17, wherein first transaction information is transported across the first network segment using a first protocol, and second dif-ferent transaction information is transported across the second network segment using a second different protocol.
23. The apparatus of Claim 22, wherein the first protocol has lower overhead than the second protocol.
24. The apparatus of Claim 22, wherein the first transaction informa-tion is in a first format, and the second transaction information is in a second dif-ferent format, and the server reformats the transaction information from the first format to the second format.
25. The apparatus of Claim 24, wherein the first format is more com-pact than the second format.
26. The method of Claim 25, wherein the server stores in a local store information about various transaction terminals and uses this information to refor-mat the transaction information from the first format to the second format.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US16755299P | 1999-11-23 | 1999-11-23 | |
| US60/167,552 | 1999-11-23 | ||
| US09/495,898 US7353208B1 (en) | 2000-02-02 | 2000-02-02 | Transaction processing using intermediate server architecture |
| US09/495,898 | 2000-02-02 | ||
| PCT/US2000/031656 WO2001039072A1 (en) | 1999-11-23 | 2000-11-20 | Transaction processing using intermediate server architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2392391A1 true CA2392391A1 (en) | 2001-05-31 |
Family
ID=26863266
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002392391A Abandoned CA2392391A1 (en) | 1999-11-23 | 2000-11-20 | Transaction processing using intermediate server architecture |
Country Status (5)
| Country | Link |
|---|---|
| EP (1) | EP1240610A4 (en) |
| AU (1) | AU1921501A (en) |
| CA (1) | CA2392391A1 (en) |
| MX (1) | MXPA02005228A (en) |
| WO (1) | WO2001039072A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR3010215B1 (en) * | 2013-08-29 | 2016-12-30 | Compagnie Ind Et Financiere Dingenierie Ingenico | METHOD FOR PROCESSING TRANSACTIONAL DATA, DEVICES AND CORRESPONDING COMPUTER PROGRAMS. |
| US9603019B1 (en) | 2014-03-28 | 2017-03-21 | Confia Systems, Inc. | Secure and anonymized authentication |
| US10484359B2 (en) | 2015-07-25 | 2019-11-19 | Confia Systems, Inc. | Device-level authentication with unique device identifiers |
| US9602292B2 (en) | 2015-07-25 | 2017-03-21 | Confia Systems, Inc. | Device-level authentication with unique device identifiers |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5387784A (en) * | 1990-10-30 | 1995-02-07 | Societe D'applications Generales D'electricite Et De Mecanique Sagem | Portable payment terminals and network for such terminals |
| US5920847A (en) * | 1993-11-01 | 1999-07-06 | Visa International Service Association | Electronic bill pay system |
| US5870723A (en) * | 1994-11-28 | 1999-02-09 | Pare, Jr.; David Ferrin | Tokenless biometric transaction authorization method and system |
| US5696909A (en) * | 1995-01-27 | 1997-12-09 | Hypercom, Inc. | Virtual POS terminal |
| US5930767A (en) * | 1997-05-28 | 1999-07-27 | Motorola, Inc. | Transaction methods systems and devices |
| US6075796A (en) * | 1997-03-17 | 2000-06-13 | At&T | Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony |
-
2000
- 2000-11-20 EP EP00982148A patent/EP1240610A4/en not_active Withdrawn
- 2000-11-20 CA CA002392391A patent/CA2392391A1/en not_active Abandoned
- 2000-11-20 MX MXPA02005228A patent/MXPA02005228A/en unknown
- 2000-11-20 AU AU19215/01A patent/AU1921501A/en not_active Abandoned
- 2000-11-20 WO PCT/US2000/031656 patent/WO2001039072A1/en not_active Application Discontinuation
Also Published As
| Publication number | Publication date |
|---|---|
| WO2001039072A1 (en) | 2001-05-31 |
| MXPA02005228A (en) | 2003-09-25 |
| EP1240610A4 (en) | 2006-03-22 |
| EP1240610A1 (en) | 2002-09-18 |
| AU1921501A (en) | 2001-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7353208B1 (en) | Transaction processing using intermediate server architecture | |
| US7487126B2 (en) | Computer network method for conducting payment over a network by debiting and crediting utilities accounts | |
| US8086530B2 (en) | Electronic payment system utilizing intermediary account | |
| US20020055907A1 (en) | Electronic payment system and method | |
| US8286861B2 (en) | Cash payment for remote transactions | |
| US20020025796A1 (en) | System and method conducting cellular POS transactions | |
| US20130185202A1 (en) | System and method for mobile payment transactions | |
| US20020103753A1 (en) | Charge splitter application | |
| US20120197801A1 (en) | Merchant payment system and method for mobile phones | |
| JP2001525571A (en) | Multipurpose trading network method | |
| CN101116090A (en) | Pre-paid activation and replenishment on a point-of-sale device | |
| CA2295667A1 (en) | Multifunction card system | |
| US7428507B2 (en) | System and arrangement for processing payments for purchases through a payment server | |
| JP2007503046A (en) | Payment processing system and method | |
| AU2008232465B2 (en) | Bill payment system | |
| CA2392391A1 (en) | Transaction processing using intermediate server architecture | |
| GB2339625A (en) | Mobile phone prepayment system | |
| KR100914662B1 (en) | Method for Providing Cash-back Correspond to Medical Supplies Purchasing | |
| KR100885167B1 (en) | Total Limit Loan Data Processing Method and System and Program Record Medium | |
| KR100876596B1 (en) | Card terminal | |
| JP2003016363A (en) | System and method for shortening payment period of approved credit transaction | |
| KR20080096637A (en) | Payment processing method and system | |
| KR20090060241A (en) | Method for processing loan for purchasing medical supplies | |
| KR20090000798A (en) | Method and system for payment of goods in chain stores and recording medium therefor | |
| JP2001250060A (en) | Electronic commercial transaction system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |