CA2371820A1 - Method and apparatus for conducting commerce between individuals - Google Patents
Method and apparatus for conducting commerce between individuals Download PDFInfo
- Publication number
- CA2371820A1 CA2371820A1 CA002371820A CA2371820A CA2371820A1 CA 2371820 A1 CA2371820 A1 CA 2371820A1 CA 002371820 A CA002371820 A CA 002371820A CA 2371820 A CA2371820 A CA 2371820A CA 2371820 A1 CA2371820 A1 CA 2371820A1
- Authority
- CA
- Canada
- Prior art keywords
- account
- transaction
- individual
- payment
- transaction server
- 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
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/403—Solvency checks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/08—Auctions
-
- 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
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
-
- 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/12—Accounting
Abstract
A system and method for receiving payment includes the establishment, at a first server (210), of a transaction record (244, FIG. 6B) including information identifying a payment amount, a first account to be credited by the payment amount, and a second account to be debited by a debit amount. A
financial authorization network (220) performs an authorization analysis on at least the second account (242, FIG. 6A). The second account is debited if the authorization analysis is successfully completed, and the first account is directly credited by the payment amount to conclude the transaction.
financial authorization network (220) performs an authorization analysis on at least the second account (242, FIG. 6A). The second account is debited if the authorization analysis is successfully completed, and the first account is directly credited by the payment amount to conclude the transaction.
Description
METHOD AND APPARATUS FOR CONDUCTING COMMERCE BETWEEN
INDIVIDUALS
BACKGROUND OF THE INVENTION
The present invention relates to electronic commerce and more particularly to systems and methods for conducting electronic commerce between individuals.
Consumers today have a large number of payment choices when purchasing goods or services in person at merchant storefront locations or in mail-order or telephone commerce (referred to herein as "physical world" transactions). For example, most merchants in these transactions accept cash, checks, travelers checks, money orders, and a variety of payment cards, including debit cards, credit cards, and even smart cards. Most consumers have one or more payment cards in their wallet as well as cash and checks. With access to these forms of payment, a consumer can purchase almost any good or service from any merchant.
Consumers also have a large number of choices of how to purchase goods from other individuals in the physical world. For example, at a garage sale, a consumer can choose to hand a seller cash. a personal check, a travelers check, or a money order for goods being sold at the garage sale. The seller can choose to accept or not to accept the purchaser's check based on information available to the seller at the time of purchase. Individuals who are not merchants are not able to accept payment cards for purchases because of payment rules established by banks and card associations which, essentially, limit payment card acceptance to qualified merchants.
Many existing forms of payments in the physical world depend upon the seller's ability to trust, or to verify the buyer's identity. For example, a merchant may require a form of identification before accepting a consumer's check for payment. A catalog merchant may wait until a consumer's check has cleared or a payment card transaction has been authorized before shipping the goods to the consumer. A person selling goods to another individual (e.g,. at a garage sale, etc.), may require an even greater number of forms of identification from a prospective buyer who chooses to use a check or may simply insist on cash as the only accepted form of payment. Consumers have learned to accept and live with these limitations in the physical world, partly because of the benefits they provide (e.g., greater convenience in form and mode of payment, etc.). The reduced fraud losses made possible by the use of existing payment systems directly benefits banks and merchants and indirectly benefits consumers in the form of reduced transaction costs.
Another aspect of buying and selling goods in the physical world is the consumer's ability to inspect the goods before paying for them. For example, a consumer interested in buying a used television at a garage sale may inspect it before purchasing it. If, upon inspection, it turns out that the television does not work properly, the purchaser can choose not to buy it or to offer the seller a lower price.
Recently, advances in technology have opened up new marketplaces. In particular, the Internet has developed into a new means by which consumers can access and purchase information, communicate and pay for services, and acquire and pay for goods. Because of the anonymous nature of communication networks, new methods and systems must be developed to substitute for existing procedures used in physical world transactions.
A number of new technologies have been developed to allow payments over the Internet. For example, the Secure Electronic Transaction (SET) specification has been developed to allow customers to make payment card transactions securely over the Internet. The SET protocol, however, is intended for use between consumers and merchants. Other protocols and tools have also been developed to enable transactions to be conducted over the Internet, but these methods are again limited to transactions conducted between consumers and merchants.
None of these existing systems are designed to permit transactions to be conducted between individuals. So-called "stored value" smart card systems have been developed which may be used to conduct commerce between individuals, such as the Net 1 system described in U. S.
Patent No. 5,175,416. In general, these smart card systems utilize electronic purses which contain tokens representing value which may be passed from one consumer to another.
However, these chip card-based stored value smart card systems are not yet in widespread use in the U.S. or in other countries around the world. Therefore. it would be desirable to provide a
INDIVIDUALS
BACKGROUND OF THE INVENTION
The present invention relates to electronic commerce and more particularly to systems and methods for conducting electronic commerce between individuals.
Consumers today have a large number of payment choices when purchasing goods or services in person at merchant storefront locations or in mail-order or telephone commerce (referred to herein as "physical world" transactions). For example, most merchants in these transactions accept cash, checks, travelers checks, money orders, and a variety of payment cards, including debit cards, credit cards, and even smart cards. Most consumers have one or more payment cards in their wallet as well as cash and checks. With access to these forms of payment, a consumer can purchase almost any good or service from any merchant.
Consumers also have a large number of choices of how to purchase goods from other individuals in the physical world. For example, at a garage sale, a consumer can choose to hand a seller cash. a personal check, a travelers check, or a money order for goods being sold at the garage sale. The seller can choose to accept or not to accept the purchaser's check based on information available to the seller at the time of purchase. Individuals who are not merchants are not able to accept payment cards for purchases because of payment rules established by banks and card associations which, essentially, limit payment card acceptance to qualified merchants.
Many existing forms of payments in the physical world depend upon the seller's ability to trust, or to verify the buyer's identity. For example, a merchant may require a form of identification before accepting a consumer's check for payment. A catalog merchant may wait until a consumer's check has cleared or a payment card transaction has been authorized before shipping the goods to the consumer. A person selling goods to another individual (e.g,. at a garage sale, etc.), may require an even greater number of forms of identification from a prospective buyer who chooses to use a check or may simply insist on cash as the only accepted form of payment. Consumers have learned to accept and live with these limitations in the physical world, partly because of the benefits they provide (e.g., greater convenience in form and mode of payment, etc.). The reduced fraud losses made possible by the use of existing payment systems directly benefits banks and merchants and indirectly benefits consumers in the form of reduced transaction costs.
Another aspect of buying and selling goods in the physical world is the consumer's ability to inspect the goods before paying for them. For example, a consumer interested in buying a used television at a garage sale may inspect it before purchasing it. If, upon inspection, it turns out that the television does not work properly, the purchaser can choose not to buy it or to offer the seller a lower price.
Recently, advances in technology have opened up new marketplaces. In particular, the Internet has developed into a new means by which consumers can access and purchase information, communicate and pay for services, and acquire and pay for goods. Because of the anonymous nature of communication networks, new methods and systems must be developed to substitute for existing procedures used in physical world transactions.
A number of new technologies have been developed to allow payments over the Internet. For example, the Secure Electronic Transaction (SET) specification has been developed to allow customers to make payment card transactions securely over the Internet. The SET protocol, however, is intended for use between consumers and merchants. Other protocols and tools have also been developed to enable transactions to be conducted over the Internet, but these methods are again limited to transactions conducted between consumers and merchants.
None of these existing systems are designed to permit transactions to be conducted between individuals. So-called "stored value" smart card systems have been developed which may be used to conduct commerce between individuals, such as the Net 1 system described in U. S.
Patent No. 5,175,416. In general, these smart card systems utilize electronic purses which contain tokens representing value which may be passed from one consumer to another.
However, these chip card-based stored value smart card systems are not yet in widespread use in the U.S. or in other countries around the world. Therefore. it would be desirable to provide a
2 method and system which allows individuals to conduct transactions with other individuals using existing payment cards.
This need increases as new trading places develop on the Internet. A recent phenomenon is the development of auction sites and classified ad sites where individuals can sell goods to other individuals over the Internet. Unfortunately, there is no widely-available payment scheme that is well-suited for these types of transactions. Most auction or classified ad sites require that a money order or cashiers check be delivered to the seller before the seller needs to ship the product. This places a great risk of loss on the buyer who has little or no recourse if the goods are damaged or not even shipped. Unlike the garage sale buyer in the physical world who has a chance to inspect and test the merchandise on before paying for it, the auction site or classified ad site buyer in the Internet world must currently proceed on faith that the seller has honestly and accurately represented the quality and state of the goods to be purchased. Further, it is inconvenient, slow and costly for the buyer to purchase goods using a cashier's check or money order. It would be desirable to provide a method and system allowing a consumer to purchase goods from another non-merchant individual without needing to go through the process of obtaining a cashier's check or money order or waiting for the payment to be mailed to the seller.
At least one company, recognizing this problem, has developed an "escrow"
service designed to facilitate payment between individuals for Internet transactions (see, e.g., the system described at www.iescrow.com). In these escrow type systems, the buyer pays the escrow company the amount agreed-upon between the buyer and seller. After the seller has shipped the goods to the buyer and the buyer has had a reasonable chance to inspect the item(s), the escrow company pays the seller (minus a commission). Unfortunately, however, this form of an escrow service introduces new problems and complexity into the purchase process: the escrow service provider is actually the entity being paid for the goods; the escrow company is a third party to the transaction and is a company that is generally not known to the buyer and seller; or the escrow company may be paid by the buyer yet somehow fail to pay the seller.
Further, the escrow service provider typically pays the seller using a check or money order.
This can be an inconvenient and slow process for the seller, who would like to be paid quickly and conveniently. The commission charged by the escrow service, which can be relatively
This need increases as new trading places develop on the Internet. A recent phenomenon is the development of auction sites and classified ad sites where individuals can sell goods to other individuals over the Internet. Unfortunately, there is no widely-available payment scheme that is well-suited for these types of transactions. Most auction or classified ad sites require that a money order or cashiers check be delivered to the seller before the seller needs to ship the product. This places a great risk of loss on the buyer who has little or no recourse if the goods are damaged or not even shipped. Unlike the garage sale buyer in the physical world who has a chance to inspect and test the merchandise on before paying for it, the auction site or classified ad site buyer in the Internet world must currently proceed on faith that the seller has honestly and accurately represented the quality and state of the goods to be purchased. Further, it is inconvenient, slow and costly for the buyer to purchase goods using a cashier's check or money order. It would be desirable to provide a method and system allowing a consumer to purchase goods from another non-merchant individual without needing to go through the process of obtaining a cashier's check or money order or waiting for the payment to be mailed to the seller.
At least one company, recognizing this problem, has developed an "escrow"
service designed to facilitate payment between individuals for Internet transactions (see, e.g., the system described at www.iescrow.com). In these escrow type systems, the buyer pays the escrow company the amount agreed-upon between the buyer and seller. After the seller has shipped the goods to the buyer and the buyer has had a reasonable chance to inspect the item(s), the escrow company pays the seller (minus a commission). Unfortunately, however, this form of an escrow service introduces new problems and complexity into the purchase process: the escrow service provider is actually the entity being paid for the goods; the escrow company is a third party to the transaction and is a company that is generally not known to the buyer and seller; or the escrow company may be paid by the buyer yet somehow fail to pay the seller.
Further, the escrow service provider typically pays the seller using a check or money order.
This can be an inconvenient and slow process for the seller, who would like to be paid quickly and conveniently. The commission charged by the escrow service, which can be relatively
3
4 PCT/US00/04348 large, is a deterrent to many buyers and sellers, especially where the transaction involves a small dollar amount (e.g,. less than $20). Commissions and shipping can add 50% or more to the cost of purchasing an item. One reason that these escrow services charge such a high commission is the relatively high overhead expense required to receive and generate payments via checks and money orders.
Accordingly, it would be desirable to provide a system and method for allowing individual consumers to advertise and sell their goods to other individual consumers which allows the efficient use of existing payment cards to facilitate the transaction.
Further, it is desirable to allow the purchase amount to be directly credited to a seller's payment card account. The system should be easily integrated into Internet commerce and package shipping web sites.
SUMMARY OF THE INVENTION
Accordingly, a payment system and method is described which allows individuals who have current and valid payment cards to make payment to and receive payment from other individuals who have current and valid payment cards.
According to an embodiment of the invention, a transaction server is provided which is coupled to a financial authorization network. Individual participants in the payment system register with the transaction server by providing information regarding at least one payment card account. Successful registration requires that the payment card account be valid. In addition, other risk reduction analyses may be performed at the time of registration to provide an enhanced level of security and/or to reduce the risk of fraud or credit loss. Once registered, participants are given at least an account identifier (ID) to reference and access the established account record.
Participants may negotiate the terms of purchases over the Internet or in the physical world.
Once a sale price and terms have been established, one party contacts the transaction server and provides details regarding the transaction, including the party's account ID.
A transaction record is created by the transaction server for the current transaction. The other party to the transaction then confirms details regarding the transaction and provides his or her account ID.
This information is added to the transaction record, and authorization and other risk analyses are performed on the transaction.
If the transaction is authorized, the buyer's payment card account is debited.
The amount debited may either be directly credited to the seller's payment card account or may be held in an escrow account for a period of time. Preferably, if an escrow account is used, the escrow period is established to allow the buyer to receive and inspect the goods.
Upon successful completion of the escrow period, the payment amount is directly credited to the seller's payment card account.
In alternative embodiments, shipping terms may also be negotiated and paid for directly from the buyer's payment card account or the escrow account. Further, transaction fees may also be directly deducted from the buyer's payment card account or the escrow account.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent to one skilled in the art, however, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail in order not to unnecessarily obscure the present invention.
A further understanding of the nature and advantages of the invention may be realized by reference to the remaining portions of the specification and the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a block diagram depicting a network environment implementing an embodiment of the present invention;
Fig. 2 is a block diagram depicting a network payment environment implementing a specific embodiment of the present invention;
Fig. 3 is a flow diagram depicting a seller and a buyer registration process according to an embodiment of the present invention;
Accordingly, it would be desirable to provide a system and method for allowing individual consumers to advertise and sell their goods to other individual consumers which allows the efficient use of existing payment cards to facilitate the transaction.
Further, it is desirable to allow the purchase amount to be directly credited to a seller's payment card account. The system should be easily integrated into Internet commerce and package shipping web sites.
SUMMARY OF THE INVENTION
Accordingly, a payment system and method is described which allows individuals who have current and valid payment cards to make payment to and receive payment from other individuals who have current and valid payment cards.
According to an embodiment of the invention, a transaction server is provided which is coupled to a financial authorization network. Individual participants in the payment system register with the transaction server by providing information regarding at least one payment card account. Successful registration requires that the payment card account be valid. In addition, other risk reduction analyses may be performed at the time of registration to provide an enhanced level of security and/or to reduce the risk of fraud or credit loss. Once registered, participants are given at least an account identifier (ID) to reference and access the established account record.
Participants may negotiate the terms of purchases over the Internet or in the physical world.
Once a sale price and terms have been established, one party contacts the transaction server and provides details regarding the transaction, including the party's account ID.
A transaction record is created by the transaction server for the current transaction. The other party to the transaction then confirms details regarding the transaction and provides his or her account ID.
This information is added to the transaction record, and authorization and other risk analyses are performed on the transaction.
If the transaction is authorized, the buyer's payment card account is debited.
The amount debited may either be directly credited to the seller's payment card account or may be held in an escrow account for a period of time. Preferably, if an escrow account is used, the escrow period is established to allow the buyer to receive and inspect the goods.
Upon successful completion of the escrow period, the payment amount is directly credited to the seller's payment card account.
In alternative embodiments, shipping terms may also be negotiated and paid for directly from the buyer's payment card account or the escrow account. Further, transaction fees may also be directly deducted from the buyer's payment card account or the escrow account.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent to one skilled in the art, however, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail in order not to unnecessarily obscure the present invention.
A further understanding of the nature and advantages of the invention may be realized by reference to the remaining portions of the specification and the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a block diagram depicting a network environment implementing an embodiment of the present invention;
Fig. 2 is a block diagram depicting a network payment environment implementing a specific embodiment of the present invention;
Fig. 3 is a flow diagram depicting a seller and a buyer registration process according to an embodiment of the present invention;
5 Fig. 4 is a flow diagram depicting a purchase process according to an embodiment of the present invention;
Fig. 5 is a block diagram depicting a transaction server according to an embodiment of the present invention; and Fig. 6A and 6B are schematic illustrations of databases of Fig. 5.
DESCRIPTION OF SPECIFIC EMBODIMENTS
Features of embodiments of the present invention will now be described by referring first to Fig. l, where a payment system 100 according to the invention is shown.
Payment system 100 is shown implemented across a network 102. Network 102, in a particular embodiment, is the world-wide network of networks known as the "Internet". Upon reading this disclosure, those skilled in the art will recognize that other network and communication infrastructures may also be used in the implementation of the present invention. Further, variations of the present invention may be implemented without reliance on the Internet or other networks. Although embodiments of the invention may be implemented using other networks, the Internet is currently preferred because of its accessibility from around the world using common interfaces and protocols. These common interfaces and protocols are well-known in the art. For example, the Internet uses a communication protocol referred to as the "Transmission Control Protocol/Internet Protocol" (TCP/IP). The Internet also makes use of a number of common information transport protocols, including basic file transfer protocols (FTP). Other, more interactive, protocols have also been developed for use on the Internet.
In the past several years, a graphically-interactive information transport protocol has been widely accepted on the Internet. This protocol, called the "Hyper Text Transfer Protocol"
(HTTP) enables use of a distributed information system known as the "world wide web" (the "web" or "WWW") which follows a conventional client-server model. The web allows client computers to use browser software to view and interact with documents residing in servers across the Internet. Web clients and servers communicate using the HTTP
protocol to transfer both textual and graphical information in a coordinated manner. An HTTP
session is established between a client browser and a server based on a request initiated by the client browser. This request typically involves the client browser's specification of a Uniform Resource Locator (URL) of the desired server. The request typically follows the format:
Fig. 5 is a block diagram depicting a transaction server according to an embodiment of the present invention; and Fig. 6A and 6B are schematic illustrations of databases of Fig. 5.
DESCRIPTION OF SPECIFIC EMBODIMENTS
Features of embodiments of the present invention will now be described by referring first to Fig. l, where a payment system 100 according to the invention is shown.
Payment system 100 is shown implemented across a network 102. Network 102, in a particular embodiment, is the world-wide network of networks known as the "Internet". Upon reading this disclosure, those skilled in the art will recognize that other network and communication infrastructures may also be used in the implementation of the present invention. Further, variations of the present invention may be implemented without reliance on the Internet or other networks. Although embodiments of the invention may be implemented using other networks, the Internet is currently preferred because of its accessibility from around the world using common interfaces and protocols. These common interfaces and protocols are well-known in the art. For example, the Internet uses a communication protocol referred to as the "Transmission Control Protocol/Internet Protocol" (TCP/IP). The Internet also makes use of a number of common information transport protocols, including basic file transfer protocols (FTP). Other, more interactive, protocols have also been developed for use on the Internet.
In the past several years, a graphically-interactive information transport protocol has been widely accepted on the Internet. This protocol, called the "Hyper Text Transfer Protocol"
(HTTP) enables use of a distributed information system known as the "world wide web" (the "web" or "WWW") which follows a conventional client-server model. The web allows client computers to use browser software to view and interact with documents residing in servers across the Internet. Web clients and servers communicate using the HTTP
protocol to transfer both textual and graphical information in a coordinated manner. An HTTP
session is established between a client browser and a server based on a request initiated by the client browser. This request typically involves the client browser's specification of a Uniform Resource Locator (URL) of the desired server. The request typically follows the format:
6 <protocol identifier>://<protocol server address>/<qualifier>, where the protocol may include, e.g., HTTP, FTP, etc. The development and proliferation of web servers providing information via the WWW has led to an explosion of Internet commerce applications, including the development of auction and classified ad sites.
For the purposes of this disclosure, examples will be given referring to Internet sites and resources which utilize the HTTP protocol. Those skilled in the art will recognize that other network interfaces and protocols may be used. For example, network 102 may be a public or private X.25 network using SNA or ATM protocols, etc.
Payment system 100 includes a number of terminals 108a-108n and a number of servers 104a-n. In general, terminals 108a-n are small computers or "personal computers" or workstations operated by human operators to retrieve, browse, or interact with information and service providers across the Internet. Servers 104a-n, in general, are larger computers or workstations configured and used to store data and information for retrieval over the Internet. In this simplified scenario, terminals 108a-108n are clients and servers 104a-n are the servers in the client-server relationship. Because of the design of the Internet and the web, roles of the computers can be reversed in any given transaction, for example, the smaller computers may also act as "servers" by providing information to the larger computers.
The web uses the client-server model to communicate information between clients and servers.
Web servers are coupled to the Internet and respond to requests from web clients.
Terminals 108a-n and servers 104a-n may be implemented using any of a number of computing platforms, such as desktop personal computers, laptops, personal digital assistants, screen phones, workstations, etc., running an operating system such as Windows, DOS, UNIX, OS/2, NT, or the like.
Fig. 2 shows an embodiment of a payment system 200 according to the invention in more detail, and includes a number of terminals 208a-n connected to a network 203.
For simplicity, these terminals are shown as being directly coupled to network 203. Those skilled in the art will recognize that terminals 208 may also be coupled to network 203 through, e.g., Internet Service Providers (ISPs), through corporate networks, or the like.
For the purposes of this disclosure, examples will be given referring to Internet sites and resources which utilize the HTTP protocol. Those skilled in the art will recognize that other network interfaces and protocols may be used. For example, network 102 may be a public or private X.25 network using SNA or ATM protocols, etc.
Payment system 100 includes a number of terminals 108a-108n and a number of servers 104a-n. In general, terminals 108a-n are small computers or "personal computers" or workstations operated by human operators to retrieve, browse, or interact with information and service providers across the Internet. Servers 104a-n, in general, are larger computers or workstations configured and used to store data and information for retrieval over the Internet. In this simplified scenario, terminals 108a-108n are clients and servers 104a-n are the servers in the client-server relationship. Because of the design of the Internet and the web, roles of the computers can be reversed in any given transaction, for example, the smaller computers may also act as "servers" by providing information to the larger computers.
The web uses the client-server model to communicate information between clients and servers.
Web servers are coupled to the Internet and respond to requests from web clients.
Terminals 108a-n and servers 104a-n may be implemented using any of a number of computing platforms, such as desktop personal computers, laptops, personal digital assistants, screen phones, workstations, etc., running an operating system such as Windows, DOS, UNIX, OS/2, NT, or the like.
Fig. 2 shows an embodiment of a payment system 200 according to the invention in more detail, and includes a number of terminals 208a-n connected to a network 203.
For simplicity, these terminals are shown as being directly coupled to network 203. Those skilled in the art will recognize that terminals 208 may also be coupled to network 203 through, e.g., Internet Service Providers (ISPs), through corporate networks, or the like.
7 A transaction server 210 is also shown connected to network 203. Transaction server 210 is coupled to a transaction server storage device 212 and is also coupled to a financial network 220. In one specific embodiment, transaction server 210 is operated and managed on behalf of a financial institution or a payment card association,-such as Visa, and follows established risk control procedures and management rules. Transaction server 210 is configured to send and receive financial messages to financial network 220 which, in one specific embodiment, is the VisaNet~ network. Preferably, financial network 220 is a network which permits transaction server 210 to send authorization requests and inquiries to payment card issuing institutions, to receive authorization and inquiry responses, and to cause funds clearing and settlement functions to take place in a manner to be described below.
A host server 202 is also shown connected to network 203, and is configured to store and manage a number of classified advertisements posted by a number of sellers, including a seller operating terminal 208n. Posted classified advertisements are stored in host server storage device 204 for viewing by potential buyers, including a buyer operating terminal 208a. For example, a potential buyer may view classified advertisements by directing a web browser running on terminal 208a to the IP address of host server 202 (e.g., htt~//www.hostname.com~, and by following any HTTP menus or links established by the operator of host server 202. This host server 202 may be a server operated by (or on behalf of) a newspaper, a so-called "Portal"
site, a company in the business of facilitating commerce between individuals, or any other entity interested in providing a capability allowing individual sellers to sell new or used goods or services to individual buyers.
A shipping server 214 is also shown connected to network 203. Shipping server 214 may be any site established or run by or on behalf of a company or agency in the business of shipping goods (e.g., DHL, Federal Express, US Post Office, etc.).
Further details regarding an embodiment of transaction server 210 are shown in Fig. 5.
Transaction server 210 includes a processor 230, such as a conventional Intel microprocessor or the like. Processor 230 is in communication with storage device 212 which may be an appropriate combination of magnetic, optical and/or semiconductor memory.
Processor 230 and storage device 212 may each be located within a single computer or other computing
A host server 202 is also shown connected to network 203, and is configured to store and manage a number of classified advertisements posted by a number of sellers, including a seller operating terminal 208n. Posted classified advertisements are stored in host server storage device 204 for viewing by potential buyers, including a buyer operating terminal 208a. For example, a potential buyer may view classified advertisements by directing a web browser running on terminal 208a to the IP address of host server 202 (e.g., htt~//www.hostname.com~, and by following any HTTP menus or links established by the operator of host server 202. This host server 202 may be a server operated by (or on behalf of) a newspaper, a so-called "Portal"
site, a company in the business of facilitating commerce between individuals, or any other entity interested in providing a capability allowing individual sellers to sell new or used goods or services to individual buyers.
A shipping server 214 is also shown connected to network 203. Shipping server 214 may be any site established or run by or on behalf of a company or agency in the business of shipping goods (e.g., DHL, Federal Express, US Post Office, etc.).
Further details regarding an embodiment of transaction server 210 are shown in Fig. 5.
Transaction server 210 includes a processor 230, such as a conventional Intel microprocessor or the like. Processor 230 is in communication with storage device 212 which may be an appropriate combination of magnetic, optical and/or semiconductor memory.
Processor 230 and storage device 212 may each be located within a single computer or other computing
8 device. Alternatively, or in addition, they may be connected to each other via a remote communication medium (e.g., a serial port, telephone line, or RF transceiver).
Processor 230 is operatively coupled to an input device 232, which may include a keyboard or keypad for transmitting input or control signals to processor 230. A display device 236 is preferably a video monitor for displaying information from processor 230, while output device 238 may be a printer for printing hardcopy output from processor 230. A large number of types of input devices, display devices, and output devices are known to those skilled in the art, and need not be described in detail herein.
Communication device 234 is preferably a telephone or cable modem allowing communication between transaction server 210 and network 203 (of Fig. 2). Alternatively, communication device 234 may be a network adapter, or any of a number of different types of communication devices known in the art.
Storage device 212 stores a program 240 for controlling processor 230.
Processor 230 performs instructions of program 240, and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein. Program 240 further includes program elements that may be necessary, such as an operating system and "device drivers" for allowing processor 230 to interface with components coupled to processor 230 (e.g., input device 232, etc.). Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
Storage device 212 further stores databases or datastores, including an account database 242 and a transaction database 244. Account database 242 and transaction database 244 and data stored therein are described in more detail below. As will be understood by those skilled in the art, the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A
number of alternative arrangements may be employed other than the databases and tables shown herein.
Similarly, the illustrated entries and data elements represent exemplary information, but those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
Processor 230 is operatively coupled to an input device 232, which may include a keyboard or keypad for transmitting input or control signals to processor 230. A display device 236 is preferably a video monitor for displaying information from processor 230, while output device 238 may be a printer for printing hardcopy output from processor 230. A large number of types of input devices, display devices, and output devices are known to those skilled in the art, and need not be described in detail herein.
Communication device 234 is preferably a telephone or cable modem allowing communication between transaction server 210 and network 203 (of Fig. 2). Alternatively, communication device 234 may be a network adapter, or any of a number of different types of communication devices known in the art.
Storage device 212 stores a program 240 for controlling processor 230.
Processor 230 performs instructions of program 240, and thereby operates in accordance with the present invention, and particularly in accordance with the methods described in detail herein. Program 240 further includes program elements that may be necessary, such as an operating system and "device drivers" for allowing processor 230 to interface with components coupled to processor 230 (e.g., input device 232, etc.). Appropriate device drivers and other necessary program elements are known to those skilled in the art, and need not be described in detail herein.
Storage device 212 further stores databases or datastores, including an account database 242 and a transaction database 244. Account database 242 and transaction database 244 and data stored therein are described in more detail below. As will be understood by those skilled in the art, the schematic illustrations and accompanying descriptions of the databases presented herein are exemplary arrangements for stored representations of information. A
number of alternative arrangements may be employed other than the databases and tables shown herein.
Similarly, the illustrated entries and data elements represent exemplary information, but those skilled in the art will understand that the number and content of the entries can be different from those illustrated herein.
9 These components, when implemented according to features of the present invention as described below, interact to permit participating individuals to purchase goods or services from other participating individuals using payment cards or other types of accounts, such as checking or savings accounts, money market accounts, etc.
Referring again to Fig. 2, in one specific embodiment, payment system 200 is configured to enable a first participant operating terminal 208a to purchase goods or services from a second participant operating terminal 208n. In this particular embodiment, payment system 200 may be used to support any type of transaction between participants, including, for example: a purchase of goods offered by one participant at a garage sale; a purchase of goods offered by a participant in a traditional newspaper classified ad; a purchase of goods over the Internet via, e.g., an auction or classified ad site; a purchase of services provided by one participant to another; and any other similar transaction between participants.
This first embodiment will be described by first referring to Fig. 3, where a registration process 250 is depicted. In describing this embodiment, reference will also be made to components of Fig. 2. In this embodiment, registration process 250 is generally the same for all participants and allows registrants to act as a buyer, a seller or both. Once registered, a participant will be given a unique identifier, or "account ID" which he or she can communicate to other individuals to let them know that the participant is able to pay or receive payment using the payment methods of the present invention. Alternatively, as discussed below in conjunction with Fig. 4, participants may register at the time of completing a transaction.
Registration process 250 begins when a participant contacts transaction server 210 (step 252).
A participant may contact transaction server 210 in a number of ways. For example, a participant may contact the server over network 203 by directing a web browser running on terminal 208 to the IP address of transaction server 210 (e.g., http~J/www transactionserver.coml, and by following any HTTP menus or links established by the operator of the transaction server. Alternatively, a participant may register by contacting transaction server 210 using electronic mail or other messaging services. As a further alternative, a participant may contact an operator of transaction server 210 by interacting with a sales agent or voice response unit over a telephone or in person.
Once a participant has contacted transaction server 210 and has indicated a desire (e.g., by following menu instructions, etc.) to register for participation in the payment service, a set of payment rules and regulations may be presented to the participant by transaction server 210 (step 254). These rules are provided to each participant to ensure that he or she fully understands the terms under which payment may be made using a payment card and the terms under which payment may be credited to a payment card account from a buyer's payment card account. In one embodiment, the payment rules may be provided to participants in the form of a so-called "click-wrap" contract which must be completed and agreed to by each participant before further processing can occur (step 256). If a participant refuses to agree to the rules, the registration process aborts (step 258). A participant refusing to provide required cardholder information will also cause the registration process to abort.
If the participant agrees to the rules, registration processing continues at step 260 where the participant is prompted to enter specific account and cardholder information.
At this step, the participant is asked to provide detailed account information such as:
cardholder name; address;
e-mail address; telephone number; payment card account number; the expiration date of the payment card to be registered; etc. Preferably, this information is entered in a secure session between terminal 208 and transaction server 210. For example, a secure session may be established using secure HTTP (SHTTP) or secure socket layer (SSL) techniques.
Other security techniques may also be used, so long as the confidentiality of the entered information is preserved. In addition, techniques may be used to authenticate the identity of the participant.
For example, the participant may be identified using a public key certificate or other techniques known in the art. Details regarding security techniques to preserve the confidentiality of information or to authenticate the identity of participants is described in Applied Cryp~yraphy, Schneier 2d Ed. 1997, the contents of which are hereby incorporated by reference for all purposes.
After transaction server 210 receives all required cardholder information, an account check may be performed (step 262). An account check is any check or verification process performed to verify the authenticity and validity of the account information provided in step 260 and may comprise the generation of a balance inquiry message or other authorization check of the account information through financial network 220. For example, if the Visa~
VisaNet system is used, transaction server 210 may generate a balance inquiry message to request the balance of a cardholder's checking, savings, credit card, or other account information provided in step 260. For checking, savings, or accounts other than credit card accounts, the financial institution either returns the account ledger balance or the account available balance. For credit card accounts, the payment card issuer returns either the amount of credit remaining to buyer 208 or buyer's credit limit. Alternatively, a status check request may be generated which is an authorization request for one unit of currency (e.g., 1 U.S. dollar). In response, an authorization message will be returned to transaction server 210. Transaction server 210, depending upon the response received, may allow the registration process to proceed or may terminate the registration in step 264 (e.g., where the participant's account has no available funds remaining or where the account is no longer valid). The type of check performed at step 262 may depend upon, e.g., whether a participant is registering to be a buyer, a seller, or both (e.g., if a participant is registering only to be a seller, information regarding her account balance would probably not be required).
Additional checks may also be performed at this step 262. For example, an address verification check may be performed to verify that the cardholder address provided at step 260 is accurate and matches cardholder address records maintained by the payment card issuer.
Alternatively, or in addition, the entered payment card information may be checked against hot card lists to determine if the card has been reported as being lost or stolen. Other verification and status checks may also be performed at this stage. For example, transaction server 210 and/or financial network 220 may perform a risk analysis for each card registration, taking into account data elements for the present registration, such as: the past history of the participant attempting to register; frequency of attempts at registration; other activity on the payment card accounts being registered; nature of the participant's e-mail addresses (e.g., are they anonymous e-mail addresses which do not verify the identity of the participant?); Internet dial-in location; etc. Risk techniques known in the art may be used to assess a risk variable to each transaction based on an analysis of these variables. In the event that a particular registration appears to carry a high probability of fraud, the registration should be aborted without generating a cardholder account record or confirmation message. For example, neural network or rule based fraud analysis and detection techniques may be used to analyze the account and to predict or detect fraudulent or risky activity.
In some circumstances, if the account check or status check fails at step 263, the participant may be given an opportunity to re-register using an alternative payment card (step 265). In general, the opportunity to re-register should not be given if a risk analysis performed at step 262 indicated that the registration involved a risk of fraud (e.g., the participant had attempted to register a lost or stolen card, etc.).
If, after performing a successful status or other account check, transaction server 210 determines that registration may continue, a cardholder account record is generated for the participant (step 268). This cardholder account record contains information identifying the participant and includes information input at step 260 and may also include other information provided by transaction server 210, such as: a unique identifier of the participant, referred to herein as an "account ID"; an expiration date for the registration;
information from the authorization request, status check and/or other fraud checks that were performed; etc. The account ID is generated uniquely for each participant and is used as a record locator to retrieve the cardholder account record. Those skilled in the art will recognize that the account ID may be generated in a number of ways, for example, it may simply be a counter incremented as each new participant registers or it may be a more complex unique number such as a random number or a digital signature based on registration information provided by the cardholder.
Once a cardholder account record is generated for the participant and a unique account ID has been generated and assigned to the cardholder account record, the information is stored in transaction server storage device 212. Preferably, the information is securely stored using techniques to prevent tampering, theft or other misuse of the information.
Transaction server 210 may then prompt the participant to select a password for use in making or accepting payments using the service (step 270). The use of this password, in conjunction with the unique account ID, will allow the participant to act as a buyer or seller of goods using the payment techniques of the present invention without needing to re-enter personal information and payment card information for each transaction. Instead, as will be discussed, the participant will only need to enter a limited amount of identifying information, such as his or her password and account ID to make or receive payment using the system.
Alternatively, or in addition, other authentication techniques may be used to further prevent fraudulent or unauthorized access to account information. For example, virtual or physical authentication tokens containing certificates may be used to authenticate the identity of the participant when the participant attempts to present an account ID.
Upon successful generation and storage of a cardholder account record, a confirmation message is transmitted to the participant, signaling completion of the registration process (step 272). This confirmation message may be transmitted from transaction server 210 to terminal 208 via network 203 as an electronic mail message or may be otherwise communicated to the participant (e.g., via regular mail, telephone, etc.). Preferably, the confirmation message will include the unique account ID and/or some other information that will allow the participant to uniquely and securely identify the cardholder account record.
At this point, transaction server 210 may give the participant an option of registering further payment cards for use with the service (step 274).
Registration process 250 is repeated for each individual who wants the ability to pay or to receive payment from other individuals using the payment techniques of the present invention.
Any number of individual participants may register for the service. Further, although only a single transaction server 210 is shown in Fig. 3, those skilled in the art will recognize that any number of transaction servers 210 may be used to accommodate participants. For example, different transaction servers may be used to comply with or support different regional or national laws or other requirements, e.g., a transaction server in the U.S.
may perform certain risk, fraud, or other checks that are not necessary or relevant for a transaction server located in France.
An example payment process 300 will now be described by referring to Fig. 4.
Payment process 300 occurs when two participants, for example, a buyer operating terminal 208a and a seller operating terminal 208n wish to conduct a purchase transaction. The two participants first negotiate terms of the transaction (step 302). This negotiation process may occur over network 203 or may be accomplished in the physical world. For example, the negotiation process may involve one participant answering a newspaper classified ad of the other participant and the two participants agreeing on a sale price and delivery terms. The negotiation between a service provider (e.g., a gardener) and a customer (e.g.homeowner) may involve the oral establishment of a price for the services with the agreement that the service provider will be paid once services are performed. In an example negotiation process over network 203, the selling participant may have advertised goods for sale on an Internet classified ad or auction site, and the buying participant may have seen the advertised goods on the Internet, made an electronic offer via e-mail or other form of communication, and had the offer accepted by the seller. The negotiation process, whether conducted in the physical world or over the Internet, will generally involve the participants reaching agreement as to price, delivery, and nature of the goods or services being purchased.
The negotiation process will also result in the participants agreeing on a payment method. If the two parties agree (step 304) to use the payment method according to the present invention, processing continues to step 308 where one of the two participants to the transaction contacts transaction server 210 via the Internet or using some other form of communication (e.g., telephone, mail, etc.). In one embodiment, the seller of the goods or services is the first party to contact transaction server 210, although either participant may contact the server to initiate the purchase. The following paragraphs provide a discussion of a transaction where a seller of goods is the first party to contact transaction server 210 and the buyer of goods is the second party to contact the server. Those skilled in the art, upon reading this disclosure, will recognize that a similar flow and techniques may be used in a transaction where the buyer contacts transaction server 210 before the seller.
When contacting transaction server 210, the seller (if already registered with transaction server 210), provides his or her account ID and password (or other authenticating information). If the seller has not previously registered for the service, he or she is given the opportunity to register (step 312). If the seller is unable to successfully register for the service (e.g., does not have a valid payment card, etc.) processing stops and the two participants to the transaction must find some other payment method to consummate the purchase transaction (step 306).
Once the seller has been successfully registered with transaction server 210 and this has been confirmed (step 310), a transaction record is generated for the current purchase transaction (step 314). Generation of the transaction record involves receiving certain details about the transaction from the parties. Where the seller is the party to first contact transaction server, the transaction record generated at step 314 will include all details regarding the transaction as supplied by the seller, including: the account ID of the seller; the date and time of the transaction; the agreed-upon purchase amount; the agreed-upon shipping terms;
escrow terms;
and buyer contact information (such as an e-mail address of the buyer or other information which will allow the transaction server 210 or an operator to contact the buyer). Where the payment techniques of the present invention are used to purchase services, details regarding the performance of the services may be provided in the transaction record rather than details regarding shipping.
Where goods are purchased using techniques of the present invention, the function of shipping the goods may be an integral part of the purchase process. The transaction record generated at step 314 preferably contains detailed information which will be used to ship the goods (e.g., product weight and dimensions). A buyer will then have the ability to select the preferred mode of delivery and receive an actual or estimated price from the selected shipper.
Alternatively, the seller may dictate the terms of shipping (e.g., by insisting that one mode of delivery, such as Federal Express, be used). In this case, the seller will enter sufficient details regarding the shipping so that a total shipping cost may be calculated.
Further details regarding the integration of the shipping function and the establishment of the transaction record are provided below.
Other information which may be provided to establish a transaction record at step 314 includes details regarding an optional escrow period which may be set by transaction server 210 or agreed-upon by the parties. This optional escrow period may be used to ensure that goods are shipped and received in good order before the seller is paid for the goods.
Further details regarding the optional escrow process are provided below.
The transaction record generated at step 314 may also include a detailed description of the goods or services being sold to assist in dispute resolution. For example, the seller may choose to include a digital photograph of the goods being sold.
Once the transaction record is completed with information provided by the seller, transaction server 210 assigns a unique transaction ID to the transaction record. This transaction ID is used to uniquely identify the transaction record and may be used by the buyer and the seller to reference the current transaction. The transaction ID may simply be a sequentially-assigned number identifying the transaction or it may be a more complex digital signature uniquely generated based on transaction information. This transaction ID is used to uniquely associate the buyer with the seller and with the specific transaction. The transaction ID may appear on the buyer and seller payment card statements, for example.
At this time, an optional status request or account check may be performed by sending a message from transaction server 210 to financial networks 220. This status request or account check may be generated to determine if the seller's payment card or account which will be credited for the amount of the purchase is still valid. Preferably, however, this status request or account check is done in conjunction with step 330 below.
Once a transaction record is generated for the current transaction, transaction server 210 generates a confirmation message (step 318). This confirmation message will include a reference to the transaction ID and may also include a period of validity (e.g., the confirmation may be good for a short period, such as 12 hours, etc.). If a period of validity is established, the transaction must be completed (goods shipped, received and accepted, or services rendered and accepted) within that period.
Transaction server 210 (or an operator of transaction server 210) preferably sends the confirmation message to both the seller and the buyer (step 320), e.g., by sending an e-mail message to the buyer or by otherwise contacting the parties. To simplify this communication, an e-mail confirmation message sent to the buyer may include a URL pointer to a web page established on transaction server 210 for the specific transaction. The buyer can then access transaction server 210 (step 322) by simply pointing his or her web browser to the provided URL address to complete the transaction.
When contacting transaction server 210, the buyer provides the transaction ID
and his or her account ID and password. Alternatively, or in addition, other authentication techniques may also be employed to more securely authenticate the buyer's identity. If the buyer has not yet registered (e.g., does not have an account ID and password), the registration process of Fig. 3 is completed (step 326). Once transaction server 210 has confirmed that the buyer is registered, the buyer is prompted to enter information to complete the transaction record accessed by the transaction ID (step 328). The buyer is prompted to enter information including, for example:
his or her account ID; information regarding shipping; etc.
Embodiments of the present invention may be implemented such that shipping of a good is integrated with the purchase transaction. This has several benefits, for example: it simplifies the overall transaction between the buyer and seller; shipping and confirmed delivery of the goods may be used to trigger the transfer of funds to the seller's account;
and it simplifies the debiting of the buyer's payment card account by allowing a single debit for both the cost of shipping and the purchase price of the goods.
The buyer may enter specific information regarding shipment of the goods to be purchased. For example, if the seller has provided information regarding the dimensions and weight of the good (at step 314), the buyer can finalize details of shipping by selecting a mode of delivery.
For example, the buyer may select the shipper (e.g., Federal Express; UPS;
etc.), the mode of shipment (e.g., overnight delivery; same day service; etc.), and delivery information. Shipping information provided in step 328 may result in transaction server 210 linking to shipping server 214 to retrieve or share information regarding shipping terms and conditions.
Alternatively, the seller may establish certain shipping details (e.g., such as requiring that the good only be shipped via Federal express next day delivery, etc.).
As an example, if Federal Express delivery of the goods has been selected, transaction server 210 may connect to a shipping server operated by or on behalf of Federal Express and forward information regarding the goods to be shipped, including the shipping weight and dimensions and delivery details. Shipping server 214 may then generate a tracking number and calculate the shipping price for the goods. This information may then be returned to transaction server 210 for entry into the transaction record. Preferably, this interaction between shipping server 214 and transaction server 210 is transparent to the participants. Transaction server 210 may now track or monitor the status of the goods by reference to the shipping tracking number.
Before completing the transaction, the buyer may be given the opportunity to review all details regarding the transaction, including the information entered by the seller regarding the condition and description of the goods to be sold. The buyer can choose to modify the information, cancel the purchase, or approve the transaction.
If the buyer chooses to approve the transaction, the transaction record is completed by transaction server 210 (step 328) and an authorization request is then sent from transaction server 210 to financial networks 220 (step 330). This authorization request is generated to determine if the buyer's payment card or account which is to be used to make the purchase has sufficient funds or credit limit available to cover the cost of the transaction. If shipping, handling, and other transaction fees are to be included in the total transaction price, the authorization request may be generated to determine if the payment card or account has sufficient funds to cover the total amount. If the authorization request is declined (e.g., the identified account has insufficient funds, or is otherwise invalid), purchase transaction 300 aborts and the buyer and seller will need to arrange for some other form of payment to be used (e.g., the buyer may be given a chance to use another payment card by repeating the above process). Additionally, a status request or account check may be performed on seller's account by sending a message from transaction server 210 to financial networks 220.
This status request or account check may be generated to determine if the seller's payment card or account which will be credited for the amount of the purchase is still valid.
To further reduce the risk of fraudulent transactions (e.g., use of stolen buyer account numbers or buyer/seller collusion) the seller's account, the buyer's account and details regarding the present transaction may be subjected to further analysis in addition to the authorization request.
For example, transaction server 210 and/or financial network 220 may perform a risk analysis for each transaction taking into account data elements for each transaction such as: the past history of the buyer and seller as participants; the amount of the transaction; the type of item being purchased; frequency of purchases; time of the transaction; other activity on the payment card accounts; nature of the participant's e-mail addresses (are they anonymous e-mail addresses which do not verify the identity of the participant?); Internet dial-in location; etc.
Risk techniques known in the art may be used to assess a risk variable to each transaction based on an analysis of these variables. In the event that a particular transaction appears to carry a high probability of fraud or an unreasonably high risk of loss, the transaction should be aborted without generating an authorization at step 330. Other transaction checking procedures may also be performed as discussed in conjunction with Fig. 3 at step 262 discussed above.
In one embodiment, the actual debit of the buyer's account does not occur until either the goods have been shipped or the goods have been delivered. This can be tracked if a shipping service such as Federal Express~ has been used which tracks and reports the pickup and delivery of packages. For example, if buyer (at step 328) has indicated that he or she would like to receive the goods using Federal Express next day delivery, shipping server 214 (in this case operated by or on behalf of Federal Express) may establish a unique tracking number for the package. This unique shipping tracking number is associated with the transaction ID
generated above. Shipping server 214 may notify transaction server 210 when the goods have been picked up from seller and when they have been delivered to buyer. This notification is preferably done by referring to the unique shipping tracking number. Once the goods have been confirmed as having been either picked up or delivered, transaction server 210 may take the necessary steps to ensure the buyer's account is debited for the transaction price.
The buyer's account is debited using a debit message which is sent by transaction server 210 to financial networks 220. This debit message identifies the buyers account information and the debit amount (the total amount of the transaction). For example, if a purchase price of $50.00 was agreed upon, and a $10.00 Federal Express delivery was agreed upon, a debit message for the total amount of the transaction ($60.00) will be generated. In some embodiments, depending upon the type of messaging used by financial networks 220, the authorization request and the debit message may be combined into a single message.
The amount debited from the buyer's account may then be placed in an optional escrow account (step 334), or may be directly credited to any accounts as established in the transaction record generated at step 328. For example, a $50.00 payment may be made to the seller's payment card account while a $10.00 payment may be made directly to Federal Express to pay for the cost of shipping the goods. The amount of the purchase is directly credited to seller's designated payment card account (i.e., the payment card account that the seller registered with transaction server 210 in the registration process of Fig. 3). To credit the seller's payment card account, transaction server 210 will generate a credit message which includes information including the credit amount, a source of funds, and the seller's payment card account number to be credited. This credit message will be forwarded from transaction server 210 to financial networks 220 for processing. The source of funds for the credit message will be either the buyer's payment card account number or the escrow account (if the optional escrow account is used).
If the optional escrow account (of step 334) is used, the funds debited from the buyer's account may be held in the escrow account until transaction server 210 receives some notification that the buyer properly received the purchased product in good shape and as advertised. A set escrow period may be established by transaction server 210 (e.g., all purchases processed by a given transaction server may be given a 5 day escrow period) or may be established by agreement among the participants to a transaction. In one alternative embodiment, the escrow period may be triggered by transaction server 210 receiving some indication from shipping server 214 that the goods have been shipped or received. If the escrow period lapses without dispute by the buyer, the seller's account is credited with the purchase price (step 336) and the payment process is completed (step 338). If the optional escrow account is used, the credit message to credit the seller's payment card account will only be generated after the escrow period has successfully ended. The buyer will have a "chargeback" right during the escrow period (that is, the seller's account will not be credited during the escrow period).
Alternatively, or in addition, the buyer can signal to server 210 that the transaction is completed to his or her satisfaction, thereby terminating the escrow period.
Referring now to Fig. 6, example database structures for account database 242 and transaction database 244 are shown (in Figs. 6A and 6B respectively). The entries of these example databases illustrate various pieces of information that may be entered into and tracked by each database. For example, in Fig. 6A, account database 242 may include a number of entries, each keyed by an account ID 402. Account ID 402 identifies a particular participant, by including data describing the participants card number 404, it's expiration data 406, cardholder information 408, an e-mail address 410, and a registration date 412. This information will be obtained when a participant registers (either through the process of Fig. 3 or the process of Fig.
4). Only the account ID need be communicated to other participants, ensuring that cardholder information is protected by transaction server 210.
In Fig. 6B, an example format of transaction database 244 is shown.
Transaction database 244 may include a number of entries, including, for example: a transaction ID 414;
a buyer account ID 416; a seller account ID 418; a price term 420; a description of goods or services to be sold 422; a shipping field 424; a transaction date 426; and an escrow close 428.
This information is generated and obtained as described in conjunction with the process of Fig. 4 above. Those skilled in the art will recognize that other data elements and information may be provided in transaction database 244 and account database 242.
Those skilled in the art will now recognize that embodiments of payment system 200 may be used to facilitate different types of transactions between individuals. For example, payment system 200 can be used to facilitate classified ad or auction-style purchases in the physical world or over the Internet. Both buyer and seller need to have (or be able to acquire) account IDs from transaction server 210 to complete a transaction according to the invention. Payment system 200 may also be used to facilitate the purchase of services. For example, a babysitter may receive payment to his or her payment card account from a parent's payment card account for babysitting services if both the babysitter and the parent have registered their respective payment cards with the service (eg., by following the registration steps of Fig. 3). The parent may authorize payment by simply dialing a voice response unit associated with transaction server 210 to authorize debiting of the parent's account and crediting of the babysitter's account once services have been rendered. The result is a simple, efficient, and cost effective system for making and receiving payments between individuals. While the above is a complete description of the preferred embodiments of the invention, various alternatives, modifications, and equivalents may also be used. Therefore, the above description should not be taken as limiting the scope of the invention which is defined by the appended claims.
Referring again to Fig. 2, in one specific embodiment, payment system 200 is configured to enable a first participant operating terminal 208a to purchase goods or services from a second participant operating terminal 208n. In this particular embodiment, payment system 200 may be used to support any type of transaction between participants, including, for example: a purchase of goods offered by one participant at a garage sale; a purchase of goods offered by a participant in a traditional newspaper classified ad; a purchase of goods over the Internet via, e.g., an auction or classified ad site; a purchase of services provided by one participant to another; and any other similar transaction between participants.
This first embodiment will be described by first referring to Fig. 3, where a registration process 250 is depicted. In describing this embodiment, reference will also be made to components of Fig. 2. In this embodiment, registration process 250 is generally the same for all participants and allows registrants to act as a buyer, a seller or both. Once registered, a participant will be given a unique identifier, or "account ID" which he or she can communicate to other individuals to let them know that the participant is able to pay or receive payment using the payment methods of the present invention. Alternatively, as discussed below in conjunction with Fig. 4, participants may register at the time of completing a transaction.
Registration process 250 begins when a participant contacts transaction server 210 (step 252).
A participant may contact transaction server 210 in a number of ways. For example, a participant may contact the server over network 203 by directing a web browser running on terminal 208 to the IP address of transaction server 210 (e.g., http~J/www transactionserver.coml, and by following any HTTP menus or links established by the operator of the transaction server. Alternatively, a participant may register by contacting transaction server 210 using electronic mail or other messaging services. As a further alternative, a participant may contact an operator of transaction server 210 by interacting with a sales agent or voice response unit over a telephone or in person.
Once a participant has contacted transaction server 210 and has indicated a desire (e.g., by following menu instructions, etc.) to register for participation in the payment service, a set of payment rules and regulations may be presented to the participant by transaction server 210 (step 254). These rules are provided to each participant to ensure that he or she fully understands the terms under which payment may be made using a payment card and the terms under which payment may be credited to a payment card account from a buyer's payment card account. In one embodiment, the payment rules may be provided to participants in the form of a so-called "click-wrap" contract which must be completed and agreed to by each participant before further processing can occur (step 256). If a participant refuses to agree to the rules, the registration process aborts (step 258). A participant refusing to provide required cardholder information will also cause the registration process to abort.
If the participant agrees to the rules, registration processing continues at step 260 where the participant is prompted to enter specific account and cardholder information.
At this step, the participant is asked to provide detailed account information such as:
cardholder name; address;
e-mail address; telephone number; payment card account number; the expiration date of the payment card to be registered; etc. Preferably, this information is entered in a secure session between terminal 208 and transaction server 210. For example, a secure session may be established using secure HTTP (SHTTP) or secure socket layer (SSL) techniques.
Other security techniques may also be used, so long as the confidentiality of the entered information is preserved. In addition, techniques may be used to authenticate the identity of the participant.
For example, the participant may be identified using a public key certificate or other techniques known in the art. Details regarding security techniques to preserve the confidentiality of information or to authenticate the identity of participants is described in Applied Cryp~yraphy, Schneier 2d Ed. 1997, the contents of which are hereby incorporated by reference for all purposes.
After transaction server 210 receives all required cardholder information, an account check may be performed (step 262). An account check is any check or verification process performed to verify the authenticity and validity of the account information provided in step 260 and may comprise the generation of a balance inquiry message or other authorization check of the account information through financial network 220. For example, if the Visa~
VisaNet system is used, transaction server 210 may generate a balance inquiry message to request the balance of a cardholder's checking, savings, credit card, or other account information provided in step 260. For checking, savings, or accounts other than credit card accounts, the financial institution either returns the account ledger balance or the account available balance. For credit card accounts, the payment card issuer returns either the amount of credit remaining to buyer 208 or buyer's credit limit. Alternatively, a status check request may be generated which is an authorization request for one unit of currency (e.g., 1 U.S. dollar). In response, an authorization message will be returned to transaction server 210. Transaction server 210, depending upon the response received, may allow the registration process to proceed or may terminate the registration in step 264 (e.g., where the participant's account has no available funds remaining or where the account is no longer valid). The type of check performed at step 262 may depend upon, e.g., whether a participant is registering to be a buyer, a seller, or both (e.g., if a participant is registering only to be a seller, information regarding her account balance would probably not be required).
Additional checks may also be performed at this step 262. For example, an address verification check may be performed to verify that the cardholder address provided at step 260 is accurate and matches cardholder address records maintained by the payment card issuer.
Alternatively, or in addition, the entered payment card information may be checked against hot card lists to determine if the card has been reported as being lost or stolen. Other verification and status checks may also be performed at this stage. For example, transaction server 210 and/or financial network 220 may perform a risk analysis for each card registration, taking into account data elements for the present registration, such as: the past history of the participant attempting to register; frequency of attempts at registration; other activity on the payment card accounts being registered; nature of the participant's e-mail addresses (e.g., are they anonymous e-mail addresses which do not verify the identity of the participant?); Internet dial-in location; etc. Risk techniques known in the art may be used to assess a risk variable to each transaction based on an analysis of these variables. In the event that a particular registration appears to carry a high probability of fraud, the registration should be aborted without generating a cardholder account record or confirmation message. For example, neural network or rule based fraud analysis and detection techniques may be used to analyze the account and to predict or detect fraudulent or risky activity.
In some circumstances, if the account check or status check fails at step 263, the participant may be given an opportunity to re-register using an alternative payment card (step 265). In general, the opportunity to re-register should not be given if a risk analysis performed at step 262 indicated that the registration involved a risk of fraud (e.g., the participant had attempted to register a lost or stolen card, etc.).
If, after performing a successful status or other account check, transaction server 210 determines that registration may continue, a cardholder account record is generated for the participant (step 268). This cardholder account record contains information identifying the participant and includes information input at step 260 and may also include other information provided by transaction server 210, such as: a unique identifier of the participant, referred to herein as an "account ID"; an expiration date for the registration;
information from the authorization request, status check and/or other fraud checks that were performed; etc. The account ID is generated uniquely for each participant and is used as a record locator to retrieve the cardholder account record. Those skilled in the art will recognize that the account ID may be generated in a number of ways, for example, it may simply be a counter incremented as each new participant registers or it may be a more complex unique number such as a random number or a digital signature based on registration information provided by the cardholder.
Once a cardholder account record is generated for the participant and a unique account ID has been generated and assigned to the cardholder account record, the information is stored in transaction server storage device 212. Preferably, the information is securely stored using techniques to prevent tampering, theft or other misuse of the information.
Transaction server 210 may then prompt the participant to select a password for use in making or accepting payments using the service (step 270). The use of this password, in conjunction with the unique account ID, will allow the participant to act as a buyer or seller of goods using the payment techniques of the present invention without needing to re-enter personal information and payment card information for each transaction. Instead, as will be discussed, the participant will only need to enter a limited amount of identifying information, such as his or her password and account ID to make or receive payment using the system.
Alternatively, or in addition, other authentication techniques may be used to further prevent fraudulent or unauthorized access to account information. For example, virtual or physical authentication tokens containing certificates may be used to authenticate the identity of the participant when the participant attempts to present an account ID.
Upon successful generation and storage of a cardholder account record, a confirmation message is transmitted to the participant, signaling completion of the registration process (step 272). This confirmation message may be transmitted from transaction server 210 to terminal 208 via network 203 as an electronic mail message or may be otherwise communicated to the participant (e.g., via regular mail, telephone, etc.). Preferably, the confirmation message will include the unique account ID and/or some other information that will allow the participant to uniquely and securely identify the cardholder account record.
At this point, transaction server 210 may give the participant an option of registering further payment cards for use with the service (step 274).
Registration process 250 is repeated for each individual who wants the ability to pay or to receive payment from other individuals using the payment techniques of the present invention.
Any number of individual participants may register for the service. Further, although only a single transaction server 210 is shown in Fig. 3, those skilled in the art will recognize that any number of transaction servers 210 may be used to accommodate participants. For example, different transaction servers may be used to comply with or support different regional or national laws or other requirements, e.g., a transaction server in the U.S.
may perform certain risk, fraud, or other checks that are not necessary or relevant for a transaction server located in France.
An example payment process 300 will now be described by referring to Fig. 4.
Payment process 300 occurs when two participants, for example, a buyer operating terminal 208a and a seller operating terminal 208n wish to conduct a purchase transaction. The two participants first negotiate terms of the transaction (step 302). This negotiation process may occur over network 203 or may be accomplished in the physical world. For example, the negotiation process may involve one participant answering a newspaper classified ad of the other participant and the two participants agreeing on a sale price and delivery terms. The negotiation between a service provider (e.g., a gardener) and a customer (e.g.homeowner) may involve the oral establishment of a price for the services with the agreement that the service provider will be paid once services are performed. In an example negotiation process over network 203, the selling participant may have advertised goods for sale on an Internet classified ad or auction site, and the buying participant may have seen the advertised goods on the Internet, made an electronic offer via e-mail or other form of communication, and had the offer accepted by the seller. The negotiation process, whether conducted in the physical world or over the Internet, will generally involve the participants reaching agreement as to price, delivery, and nature of the goods or services being purchased.
The negotiation process will also result in the participants agreeing on a payment method. If the two parties agree (step 304) to use the payment method according to the present invention, processing continues to step 308 where one of the two participants to the transaction contacts transaction server 210 via the Internet or using some other form of communication (e.g., telephone, mail, etc.). In one embodiment, the seller of the goods or services is the first party to contact transaction server 210, although either participant may contact the server to initiate the purchase. The following paragraphs provide a discussion of a transaction where a seller of goods is the first party to contact transaction server 210 and the buyer of goods is the second party to contact the server. Those skilled in the art, upon reading this disclosure, will recognize that a similar flow and techniques may be used in a transaction where the buyer contacts transaction server 210 before the seller.
When contacting transaction server 210, the seller (if already registered with transaction server 210), provides his or her account ID and password (or other authenticating information). If the seller has not previously registered for the service, he or she is given the opportunity to register (step 312). If the seller is unable to successfully register for the service (e.g., does not have a valid payment card, etc.) processing stops and the two participants to the transaction must find some other payment method to consummate the purchase transaction (step 306).
Once the seller has been successfully registered with transaction server 210 and this has been confirmed (step 310), a transaction record is generated for the current purchase transaction (step 314). Generation of the transaction record involves receiving certain details about the transaction from the parties. Where the seller is the party to first contact transaction server, the transaction record generated at step 314 will include all details regarding the transaction as supplied by the seller, including: the account ID of the seller; the date and time of the transaction; the agreed-upon purchase amount; the agreed-upon shipping terms;
escrow terms;
and buyer contact information (such as an e-mail address of the buyer or other information which will allow the transaction server 210 or an operator to contact the buyer). Where the payment techniques of the present invention are used to purchase services, details regarding the performance of the services may be provided in the transaction record rather than details regarding shipping.
Where goods are purchased using techniques of the present invention, the function of shipping the goods may be an integral part of the purchase process. The transaction record generated at step 314 preferably contains detailed information which will be used to ship the goods (e.g., product weight and dimensions). A buyer will then have the ability to select the preferred mode of delivery and receive an actual or estimated price from the selected shipper.
Alternatively, the seller may dictate the terms of shipping (e.g., by insisting that one mode of delivery, such as Federal Express, be used). In this case, the seller will enter sufficient details regarding the shipping so that a total shipping cost may be calculated.
Further details regarding the integration of the shipping function and the establishment of the transaction record are provided below.
Other information which may be provided to establish a transaction record at step 314 includes details regarding an optional escrow period which may be set by transaction server 210 or agreed-upon by the parties. This optional escrow period may be used to ensure that goods are shipped and received in good order before the seller is paid for the goods.
Further details regarding the optional escrow process are provided below.
The transaction record generated at step 314 may also include a detailed description of the goods or services being sold to assist in dispute resolution. For example, the seller may choose to include a digital photograph of the goods being sold.
Once the transaction record is completed with information provided by the seller, transaction server 210 assigns a unique transaction ID to the transaction record. This transaction ID is used to uniquely identify the transaction record and may be used by the buyer and the seller to reference the current transaction. The transaction ID may simply be a sequentially-assigned number identifying the transaction or it may be a more complex digital signature uniquely generated based on transaction information. This transaction ID is used to uniquely associate the buyer with the seller and with the specific transaction. The transaction ID may appear on the buyer and seller payment card statements, for example.
At this time, an optional status request or account check may be performed by sending a message from transaction server 210 to financial networks 220. This status request or account check may be generated to determine if the seller's payment card or account which will be credited for the amount of the purchase is still valid. Preferably, however, this status request or account check is done in conjunction with step 330 below.
Once a transaction record is generated for the current transaction, transaction server 210 generates a confirmation message (step 318). This confirmation message will include a reference to the transaction ID and may also include a period of validity (e.g., the confirmation may be good for a short period, such as 12 hours, etc.). If a period of validity is established, the transaction must be completed (goods shipped, received and accepted, or services rendered and accepted) within that period.
Transaction server 210 (or an operator of transaction server 210) preferably sends the confirmation message to both the seller and the buyer (step 320), e.g., by sending an e-mail message to the buyer or by otherwise contacting the parties. To simplify this communication, an e-mail confirmation message sent to the buyer may include a URL pointer to a web page established on transaction server 210 for the specific transaction. The buyer can then access transaction server 210 (step 322) by simply pointing his or her web browser to the provided URL address to complete the transaction.
When contacting transaction server 210, the buyer provides the transaction ID
and his or her account ID and password. Alternatively, or in addition, other authentication techniques may also be employed to more securely authenticate the buyer's identity. If the buyer has not yet registered (e.g., does not have an account ID and password), the registration process of Fig. 3 is completed (step 326). Once transaction server 210 has confirmed that the buyer is registered, the buyer is prompted to enter information to complete the transaction record accessed by the transaction ID (step 328). The buyer is prompted to enter information including, for example:
his or her account ID; information regarding shipping; etc.
Embodiments of the present invention may be implemented such that shipping of a good is integrated with the purchase transaction. This has several benefits, for example: it simplifies the overall transaction between the buyer and seller; shipping and confirmed delivery of the goods may be used to trigger the transfer of funds to the seller's account;
and it simplifies the debiting of the buyer's payment card account by allowing a single debit for both the cost of shipping and the purchase price of the goods.
The buyer may enter specific information regarding shipment of the goods to be purchased. For example, if the seller has provided information regarding the dimensions and weight of the good (at step 314), the buyer can finalize details of shipping by selecting a mode of delivery.
For example, the buyer may select the shipper (e.g., Federal Express; UPS;
etc.), the mode of shipment (e.g., overnight delivery; same day service; etc.), and delivery information. Shipping information provided in step 328 may result in transaction server 210 linking to shipping server 214 to retrieve or share information regarding shipping terms and conditions.
Alternatively, the seller may establish certain shipping details (e.g., such as requiring that the good only be shipped via Federal express next day delivery, etc.).
As an example, if Federal Express delivery of the goods has been selected, transaction server 210 may connect to a shipping server operated by or on behalf of Federal Express and forward information regarding the goods to be shipped, including the shipping weight and dimensions and delivery details. Shipping server 214 may then generate a tracking number and calculate the shipping price for the goods. This information may then be returned to transaction server 210 for entry into the transaction record. Preferably, this interaction between shipping server 214 and transaction server 210 is transparent to the participants. Transaction server 210 may now track or monitor the status of the goods by reference to the shipping tracking number.
Before completing the transaction, the buyer may be given the opportunity to review all details regarding the transaction, including the information entered by the seller regarding the condition and description of the goods to be sold. The buyer can choose to modify the information, cancel the purchase, or approve the transaction.
If the buyer chooses to approve the transaction, the transaction record is completed by transaction server 210 (step 328) and an authorization request is then sent from transaction server 210 to financial networks 220 (step 330). This authorization request is generated to determine if the buyer's payment card or account which is to be used to make the purchase has sufficient funds or credit limit available to cover the cost of the transaction. If shipping, handling, and other transaction fees are to be included in the total transaction price, the authorization request may be generated to determine if the payment card or account has sufficient funds to cover the total amount. If the authorization request is declined (e.g., the identified account has insufficient funds, or is otherwise invalid), purchase transaction 300 aborts and the buyer and seller will need to arrange for some other form of payment to be used (e.g., the buyer may be given a chance to use another payment card by repeating the above process). Additionally, a status request or account check may be performed on seller's account by sending a message from transaction server 210 to financial networks 220.
This status request or account check may be generated to determine if the seller's payment card or account which will be credited for the amount of the purchase is still valid.
To further reduce the risk of fraudulent transactions (e.g., use of stolen buyer account numbers or buyer/seller collusion) the seller's account, the buyer's account and details regarding the present transaction may be subjected to further analysis in addition to the authorization request.
For example, transaction server 210 and/or financial network 220 may perform a risk analysis for each transaction taking into account data elements for each transaction such as: the past history of the buyer and seller as participants; the amount of the transaction; the type of item being purchased; frequency of purchases; time of the transaction; other activity on the payment card accounts; nature of the participant's e-mail addresses (are they anonymous e-mail addresses which do not verify the identity of the participant?); Internet dial-in location; etc.
Risk techniques known in the art may be used to assess a risk variable to each transaction based on an analysis of these variables. In the event that a particular transaction appears to carry a high probability of fraud or an unreasonably high risk of loss, the transaction should be aborted without generating an authorization at step 330. Other transaction checking procedures may also be performed as discussed in conjunction with Fig. 3 at step 262 discussed above.
In one embodiment, the actual debit of the buyer's account does not occur until either the goods have been shipped or the goods have been delivered. This can be tracked if a shipping service such as Federal Express~ has been used which tracks and reports the pickup and delivery of packages. For example, if buyer (at step 328) has indicated that he or she would like to receive the goods using Federal Express next day delivery, shipping server 214 (in this case operated by or on behalf of Federal Express) may establish a unique tracking number for the package. This unique shipping tracking number is associated with the transaction ID
generated above. Shipping server 214 may notify transaction server 210 when the goods have been picked up from seller and when they have been delivered to buyer. This notification is preferably done by referring to the unique shipping tracking number. Once the goods have been confirmed as having been either picked up or delivered, transaction server 210 may take the necessary steps to ensure the buyer's account is debited for the transaction price.
The buyer's account is debited using a debit message which is sent by transaction server 210 to financial networks 220. This debit message identifies the buyers account information and the debit amount (the total amount of the transaction). For example, if a purchase price of $50.00 was agreed upon, and a $10.00 Federal Express delivery was agreed upon, a debit message for the total amount of the transaction ($60.00) will be generated. In some embodiments, depending upon the type of messaging used by financial networks 220, the authorization request and the debit message may be combined into a single message.
The amount debited from the buyer's account may then be placed in an optional escrow account (step 334), or may be directly credited to any accounts as established in the transaction record generated at step 328. For example, a $50.00 payment may be made to the seller's payment card account while a $10.00 payment may be made directly to Federal Express to pay for the cost of shipping the goods. The amount of the purchase is directly credited to seller's designated payment card account (i.e., the payment card account that the seller registered with transaction server 210 in the registration process of Fig. 3). To credit the seller's payment card account, transaction server 210 will generate a credit message which includes information including the credit amount, a source of funds, and the seller's payment card account number to be credited. This credit message will be forwarded from transaction server 210 to financial networks 220 for processing. The source of funds for the credit message will be either the buyer's payment card account number or the escrow account (if the optional escrow account is used).
If the optional escrow account (of step 334) is used, the funds debited from the buyer's account may be held in the escrow account until transaction server 210 receives some notification that the buyer properly received the purchased product in good shape and as advertised. A set escrow period may be established by transaction server 210 (e.g., all purchases processed by a given transaction server may be given a 5 day escrow period) or may be established by agreement among the participants to a transaction. In one alternative embodiment, the escrow period may be triggered by transaction server 210 receiving some indication from shipping server 214 that the goods have been shipped or received. If the escrow period lapses without dispute by the buyer, the seller's account is credited with the purchase price (step 336) and the payment process is completed (step 338). If the optional escrow account is used, the credit message to credit the seller's payment card account will only be generated after the escrow period has successfully ended. The buyer will have a "chargeback" right during the escrow period (that is, the seller's account will not be credited during the escrow period).
Alternatively, or in addition, the buyer can signal to server 210 that the transaction is completed to his or her satisfaction, thereby terminating the escrow period.
Referring now to Fig. 6, example database structures for account database 242 and transaction database 244 are shown (in Figs. 6A and 6B respectively). The entries of these example databases illustrate various pieces of information that may be entered into and tracked by each database. For example, in Fig. 6A, account database 242 may include a number of entries, each keyed by an account ID 402. Account ID 402 identifies a particular participant, by including data describing the participants card number 404, it's expiration data 406, cardholder information 408, an e-mail address 410, and a registration date 412. This information will be obtained when a participant registers (either through the process of Fig. 3 or the process of Fig.
4). Only the account ID need be communicated to other participants, ensuring that cardholder information is protected by transaction server 210.
In Fig. 6B, an example format of transaction database 244 is shown.
Transaction database 244 may include a number of entries, including, for example: a transaction ID 414;
a buyer account ID 416; a seller account ID 418; a price term 420; a description of goods or services to be sold 422; a shipping field 424; a transaction date 426; and an escrow close 428.
This information is generated and obtained as described in conjunction with the process of Fig. 4 above. Those skilled in the art will recognize that other data elements and information may be provided in transaction database 244 and account database 242.
Those skilled in the art will now recognize that embodiments of payment system 200 may be used to facilitate different types of transactions between individuals. For example, payment system 200 can be used to facilitate classified ad or auction-style purchases in the physical world or over the Internet. Both buyer and seller need to have (or be able to acquire) account IDs from transaction server 210 to complete a transaction according to the invention. Payment system 200 may also be used to facilitate the purchase of services. For example, a babysitter may receive payment to his or her payment card account from a parent's payment card account for babysitting services if both the babysitter and the parent have registered their respective payment cards with the service (eg., by following the registration steps of Fig. 3). The parent may authorize payment by simply dialing a voice response unit associated with transaction server 210 to authorize debiting of the parent's account and crediting of the babysitter's account once services have been rendered. The result is a simple, efficient, and cost effective system for making and receiving payments between individuals. While the above is a complete description of the preferred embodiments of the invention, various alternatives, modifications, and equivalents may also be used. Therefore, the above description should not be taken as limiting the scope of the invention which is defined by the appended claims.
Claims (15)
1. A method for facilitating a transaction between a first individual having a first account and a second individual having a second account, the method comprising the steps of:
establishing, at a transaction server, a transaction record for said transaction, said transaction record including information identifying a payment amount, information identifying said first account to be credited by said payment amount, and information identifying said second account to be debited by a debit amount;
performing, using a financial authorization network, an authorization analysis on at least said second account;
debiting said second account if said authorization analysis is successfully completed;
and directly crediting said first account by said payment amount.
establishing, at a transaction server, a transaction record for said transaction, said transaction record including information identifying a payment amount, information identifying said first account to be credited by said payment amount, and information identifying said second account to be debited by a debit amount;
performing, using a financial authorization network, an authorization analysis on at least said second account;
debiting said second account if said authorization analysis is successfully completed;
and directly crediting said first account by said payment amount.
2. The method of claim 1, further comprising the step of registering said first individual, said step comprising:
contacting said transaction server;
providing information regarding said first individual including information identifying said first account;
performing an analysis on said first account to determine if said account is valid;
generating an account ID if said account is valid; and communicating said account ID to said first individual.
contacting said transaction server;
providing information regarding said first individual including information identifying said first account;
performing an analysis on said first account to determine if said account is valid;
generating an account ID if said account is valid; and communicating said account ID to said first individual.
3. The method of claim 2, wherein said step of communicating said account ID
to said first individual comprises generating an electronic mail message containing said account ID
and transmitting said electronic mail message to said first individual over the Internet.
to said first individual comprises generating an electronic mail message containing said account ID
and transmitting said electronic mail message to said first individual over the Internet.
4. The method of claim 2 further comprising the step of registering said second individual, said step comprising:
contacting said transaction server;
providing information regarding said second individual including information identifying said second account;
performing an analysis on said second account to determine if said account is valid;
generating a second account ID if said account is valid; and communicating said second account ID to said second individual.
contacting said transaction server;
providing information regarding said second individual including information identifying said second account;
performing an analysis on said second account to determine if said account is valid;
generating a second account ID if said account is valid; and communicating said second account ID to said second individual.
5. The method of claim 1, further comprising the steps of:
after said step of debiting said second account, establishing an escrow account to hold said debit amount debited from said second account; and holding said debit amount in said escrow account until an escrow period has passed without a dispute.
after said step of debiting said second account, establishing an escrow account to hold said debit amount debited from said second account; and holding said debit amount in said escrow account until an escrow period has passed without a dispute.
6. The method of claim 5, further comprising the step of:
directly crediting said first account by a payment amount.
directly crediting said first account by a payment amount.
7. The method of claim 1, further comprising:
establishing a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount.
establishing a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount.
8. The method of claim 6 further comprising the steps of:
establishing a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount; and directly crediting said shipping price to a shipping account.
establishing a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount; and directly crediting said shipping price to a shipping account.
9. The method of claim 2 wherein said account ID is used by said transaction server to access stored information identifying said first individual, including information regarding said first account of said first individual.
10. The method of claim 4, wherein said second account ID is used by said transaction server to access information identifying said second individual, including information regarding said second account of said second individual.
11. A transaction server for conducting a transaction between a first participant and a second participant, comprising:
a storage device; and a processor connected to said storage device;
said storage device storing a program for controlling said processor; and said processor operative with said program to:
establish a transaction record for said transaction, said transaction record including information identifying: payment amount, a first account to be credited by said payment amount; and a second account to be debited by a debit amount;
forward an authorization request to a financial authorization network to determine if at least said second account is valid and has sufficient funds to cover said debit amount;
if said second account is valid and has sufficient funds, cause said second account to be debited by said debit amount; and cause said first account to be directly credited by said payment amount.
a storage device; and a processor connected to said storage device;
said storage device storing a program for controlling said processor; and said processor operative with said program to:
establish a transaction record for said transaction, said transaction record including information identifying: payment amount, a first account to be credited by said payment amount; and a second account to be debited by a debit amount;
forward an authorization request to a financial authorization network to determine if at least said second account is valid and has sufficient funds to cover said debit amount;
if said second account is valid and has sufficient funds, cause said second account to be debited by said debit amount; and cause said first account to be directly credited by said payment amount.
12. The transaction server of claim 11, wherein said program is further operative to cause said processor to:
receive registration information from said first individual, said registration information including information identifying: said first individual, and said first payment card;
perform an analysis on said first account to determine if said first account is valid;
generate an account ID if said first account is valid; and communicate said account ID to said first individual.
receive registration information from said first individual, said registration information including information identifying: said first individual, and said first payment card;
perform an analysis on said first account to determine if said first account is valid;
generate an account ID if said first account is valid; and communicate said account ID to said first individual.
13. The transaction server of claim 12, wherein said program is further operative to cause said processor to:
receive registration information from said second individual, said registration information including information identifying: said second individual, and said second payment card;
perform an analysis on said second account to determine if said second account is valid;
generate a second account ID if said second account is valid; and communicate said second account ID to said second individual.
receive registration information from said second individual, said registration information including information identifying: said second individual, and said second payment card;
perform an analysis on said second account to determine if said second account is valid;
generate a second account ID if said second account is valid; and communicate said second account ID to said second individual.
14. The transaction server of claim 11, wherein said program is further operative to cause said processor to:
after causing the debit of said second account, create an escrow account to hold said debit amount debited from said second account;
hold said debit amount in said escrow account; and transfer said payment amount to said first account once an escrow period has passed without a dispute.
after causing the debit of said second account, create an escrow account to hold said debit amount debited from said second account;
hold said debit amount in said escrow account; and transfer said payment amount to said first account once an escrow period has passed without a dispute.
15. The transaction server of claim 14, wherein said program is further operative to cause said processor to:
establish a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount; and directly credit said shipping price to a shipping account.
establish a shipping price, wherein said debit amount is equal to said shipping price plus said payment amount; and directly credit said shipping price to a shipping account.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US13510399P | 1999-02-19 | 1999-02-19 | |
| US60/135,103 | 1999-02-19 | ||
| US09/352,468 US7451114B1 (en) | 1999-02-19 | 1999-07-14 | Conducting commerce between individuals |
| US09/352,468 | 1999-07-14 | ||
| PCT/US2000/004348 WO2000049554A2 (en) | 1999-02-19 | 2000-02-18 | Method and apparatus for conducting commerce between individuals |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2371820A1 true CA2371820A1 (en) | 2000-08-24 |
Family
ID=26832990
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002371820A Abandoned CA2371820A1 (en) | 1999-02-19 | 2000-02-18 | Method and apparatus for conducting commerce between individuals |
Country Status (5)
| Country | Link |
|---|---|
| US (8) | US7451114B1 (en) |
| EP (1) | EP1272947A2 (en) |
| AU (2) | AU779188B2 (en) |
| CA (1) | CA2371820A1 (en) |
| WO (1) | WO2000049554A2 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002091249A1 (en) * | 2001-05-09 | 2002-11-14 | Flurosolutions Pty Ltd | A payment system |
Families Citing this family (211)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7693748B1 (en) | 1991-06-03 | 2010-04-06 | Ewinwin, Inc. | Method and system for configuring a set of information including a price and volume schedule for a product |
| US7818212B1 (en) | 1999-10-22 | 2010-10-19 | Ewinwin, Inc. | Multiple criteria buying and selling model |
| US6760746B1 (en) * | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
| IL127569A0 (en) | 1998-09-16 | 1999-10-28 | Comsense Technologies Ltd | Interactive toys |
| US6607136B1 (en) | 1998-09-16 | 2003-08-19 | Beepcard Inc. | Physical presence digital authentication system |
| US7334735B1 (en) | 1998-10-02 | 2008-02-26 | Beepcard Ltd. | Card for interaction with a computer |
| US7451114B1 (en) | 1999-02-19 | 2008-11-11 | Visa International Service Association | Conducting commerce between individuals |
| US7539628B2 (en) | 2000-03-21 | 2009-05-26 | Bennett James D | Online purchasing system supporting buyer affordability screening |
| CA2910997A1 (en) * | 1999-04-30 | 2000-11-09 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
| US20120209739A1 (en) * | 1999-05-12 | 2012-08-16 | Mesaros Gregory J | Multiple Criteria Buying and Selling Model |
| US20120035999A1 (en) * | 1999-05-12 | 2012-02-09 | Ewinwin, Inc. | e-COMMERCE VOLUME PRICING |
| US7593871B1 (en) * | 2004-06-14 | 2009-09-22 | Ewinwin, Inc. | Multiple price curves and attributes |
| US8732018B2 (en) | 1999-05-12 | 2014-05-20 | Ewinwin, Inc. | Real-time offers and dynamic price adjustments presented to mobile devices |
| US7249055B1 (en) * | 1999-07-09 | 2007-07-24 | Citicorp Credit Services, Inc. | Method and system for managing and conducting a network auction |
| US7308426B1 (en) * | 1999-08-11 | 2007-12-11 | C-Sam, Inc. | System and methods for servicing electronic transactions |
| US7889052B2 (en) | 2001-07-10 | 2011-02-15 | Xatra Fund Mx, Llc | Authorizing payment subsequent to RF transactions |
| US7239226B2 (en) | 2001-07-10 | 2007-07-03 | American Express Travel Related Services Company, Inc. | System and method for payment using radio frequency identification in contact and contactless transactions |
| US7837116B2 (en) | 1999-09-07 | 2010-11-23 | American Express Travel Related Services Company, Inc. | Transaction card |
| US8019609B2 (en) | 1999-10-04 | 2011-09-13 | Dialware Inc. | Sonic/ultrasonic authentication method |
| US8131651B1 (en) | 1999-10-06 | 2012-03-06 | Stamps.Com Inc. | Apparatus, systems and methods for online, multi-carrier, multi-service parcel shipping management featuring shipping rate and delivery schedule comparison for multiple carriers |
| US8103584B2 (en) * | 1999-11-05 | 2012-01-24 | American Express Travel Related Services Company, Inc. | Systems and methods for authorizing an allocation of an amount between transaction accounts |
| US7925585B2 (en) * | 1999-11-05 | 2011-04-12 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating transactions with different account issuers |
| US20090048885A1 (en) * | 1999-11-05 | 2009-02-19 | American Express Travel Related Services Company, Inc. | Systems and Methods for Facilitating Cost-Splitting Transactions |
| US20090048887A1 (en) * | 1999-11-05 | 2009-02-19 | American Express Travel Related Services Company, Inc. | Systems and Methods for Facilitating Transactions Involving an Intermediary |
| US7962408B2 (en) * | 1999-11-05 | 2011-06-14 | American Express Travel Related Services Company, Inc. | Systems and methods for establishing an allocation of an amount between transaction accounts |
| US7899744B2 (en) * | 1999-11-05 | 2011-03-01 | American Express Travel Related Services Company, Inc. | Systems and methods for approval of an allocation |
| US8596527B2 (en) | 1999-11-05 | 2013-12-03 | Lead Core Fund, L.L.C. | Methods for locating a payment system utilizing a point of sale device |
| US8820633B2 (en) | 1999-11-05 | 2014-09-02 | Lead Core Fund, L.L.C. | Methods for a third party biller to receive an allocated payment authorization request |
| US8275704B2 (en) * | 1999-11-05 | 2012-09-25 | Lead Core Fund, L.L.C. | Systems and methods for authorizing an allocation of an amount between transaction accounts |
| US8190514B2 (en) | 1999-11-05 | 2012-05-29 | Lead Core Fund, L.L.C. | Systems and methods for transaction processing based upon an overdraft scenario |
| US7904385B2 (en) * | 1999-11-05 | 2011-03-08 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating budgeting transactions |
| US20090048886A1 (en) * | 1999-11-05 | 2009-02-19 | American Express Travel Related Services Company, Inc. | Systems and Methods for Facilitating Gifting Transactions |
| US7962407B2 (en) * | 1999-11-05 | 2011-06-14 | American Express Travel Related Services Company, Inc. | Systems and methods for allocating an amount between transaction accounts |
| US8195565B2 (en) | 1999-11-05 | 2012-06-05 | Lead Core Fund, L.L.C. | Systems and methods for point of interaction based policy routing of transactions |
| US7996307B2 (en) * | 1999-11-05 | 2011-08-09 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating transactions between different financial accounts |
| US7941367B2 (en) * | 1999-11-05 | 2011-05-10 | American Express Travel Related Services Company, Inc. | Systems and methods for allocating an amount between sub-accounts |
| US8814039B2 (en) | 1999-11-05 | 2014-08-26 | Lead Core Fund, L.L.C. | Methods for processing a payment authorization request utilizing a network of point of sale devices |
| US7941372B2 (en) * | 1999-11-05 | 2011-05-10 | American Express Travel Related Services Company, Inc. | Systems and methods for receiving an allocation of an amount between transaction accounts |
| US8794509B2 (en) * | 1999-11-05 | 2014-08-05 | Lead Core Fund, L.L.C. | Systems and methods for processing a payment authorization request over disparate payment networks |
| US20090265241A1 (en) * | 1999-11-05 | 2009-10-22 | American Express Travel Related Services Company, Inc. | Systems and methods for determining a rewards account to fund a transaction |
| US8234212B2 (en) * | 1999-11-05 | 2012-07-31 | Lead Core Fund, L.L.C. | Systems and methods for facilitating transactions with interest |
| US8073772B2 (en) | 1999-11-05 | 2011-12-06 | American Express Travel Related Services Company, Inc. | Systems and methods for processing transactions using multiple budgets |
| WO2001033522A1 (en) * | 1999-11-05 | 2001-05-10 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating commercial transactions between parties residing at remote locations |
| US8875990B2 (en) | 1999-11-05 | 2014-11-04 | Lead Core Fund, L.L.C. | Systems and methods for allocating a payment authorization request to a payment processor |
| US8180706B2 (en) | 1999-11-05 | 2012-05-15 | Lead Core Fund, L.L.C. | Systems and methods for maximizing a rewards accumulation strategy during transaction processing |
| US7877325B2 (en) * | 1999-11-05 | 2011-01-25 | American Express Travel Related Services Company, Inc. | Systems and methods for settling an allocation of an amount between transaction accounts |
| US8458086B2 (en) * | 1999-11-05 | 2013-06-04 | Lead Core Fund, L.L.C. | Allocating partial payment of a transaction amount using an allocation rule |
| US7908214B2 (en) * | 1999-11-05 | 2011-03-15 | American Express Travel Related Services Company, Inc. | Systems and methods for adjusting loan amounts to facilitate transactions |
| US7962406B2 (en) * | 1999-11-05 | 2011-06-14 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating transactions |
| US8103585B2 (en) * | 1999-11-05 | 2012-01-24 | American Express Travel Related Services Company, Inc. | Systems and methods for suggesting an allocation |
| US7979349B2 (en) * | 1999-11-05 | 2011-07-12 | American Express Travel Related Services Company, Inc. | Systems and methods for adjusting crediting limits to facilitate transactions |
| US8646685B2 (en) | 1999-11-05 | 2014-02-11 | Lead Core Fund, L.L.C. | Device for allocating a payment authorization request to a payment processor |
| US7373312B1 (en) * | 1999-12-03 | 2008-05-13 | Ebay Inc. | Method and apparatus for facilitating user registration in an on-line auction environment |
| US7172112B2 (en) | 2000-01-21 | 2007-02-06 | American Express Travel Related Services Company, Inc. | Public/private dual card system and method |
| US8543423B2 (en) | 2002-07-16 | 2013-09-24 | American Express Travel Related Services Company, Inc. | Method and apparatus for enrolling with multiple transaction environments |
| US8429041B2 (en) | 2003-05-09 | 2013-04-23 | American Express Travel Related Services Company, Inc. | Systems and methods for managing account information lifecycles |
| WO2001059569A2 (en) * | 2000-02-09 | 2001-08-16 | Apriva, Inc. | Communication systems, components, and methods with programmable wireless devices |
| US8706627B2 (en) * | 2000-02-10 | 2014-04-22 | Jon Shore | Apparatus, systems and methods for wirelessly transacting financial transfers , electronically recordable authorization transfers, and other information transfers |
| WO2001067355A2 (en) | 2000-03-07 | 2001-09-13 | American Express Travel Related Services Company, Inc. | System for facilitating a transaction |
| US20030105710A1 (en) * | 2000-07-11 | 2003-06-05 | Ellen Barbara | Method and system for on-line payments |
| US8452704B2 (en) * | 2000-07-11 | 2013-05-28 | Citicorp Credit Services, Inc. | Method and system for on-line payments |
| US7610216B1 (en) * | 2000-07-13 | 2009-10-27 | Ebay Inc. | Method and system for detecting fraud |
| US7146338B2 (en) | 2001-06-28 | 2006-12-05 | Checkfree Services Corporation | Inter-network financial service |
| AU2001287089A1 (en) * | 2000-09-07 | 2002-03-22 | United States Postal Service | Systems and methods for providing item sales and delivery service |
| CN1409847A (en) * | 2000-09-14 | 2003-04-09 | 株式会社东芝 | Escrow trade agency system |
| US20020059100A1 (en) * | 2000-09-22 | 2002-05-16 | Jon Shore | Apparatus, systems and methods for customer specific receipt advertising |
| US20020038224A1 (en) * | 2000-09-25 | 2002-03-28 | United Parcel Service Of America, Inc. | Systems and associated methods for notification of package delivery services |
| US20040078326A1 (en) * | 2000-11-06 | 2004-04-22 | Strydom Johan Lamprecht Theron | Data processing system |
| EP1237108A3 (en) * | 2001-02-23 | 2003-08-13 | Navaho Networks Inc. | Secure electronic commerce |
| US8069105B2 (en) | 2001-03-20 | 2011-11-29 | Goldman Sachs & Co. | Hedge fund risk management |
| US8121937B2 (en) | 2001-03-20 | 2012-02-21 | Goldman Sachs & Co. | Gaming industry risk management clearinghouse |
| US7676426B2 (en) * | 2001-03-20 | 2010-03-09 | Goldman Sachs & Co. | Biometric risk management |
| US7899722B1 (en) | 2001-03-20 | 2011-03-01 | Goldman Sachs & Co. | Correspondent bank registry |
| US8140415B2 (en) * | 2001-03-20 | 2012-03-20 | Goldman Sachs & Co. | Automated global risk management |
| US7958027B2 (en) | 2001-03-20 | 2011-06-07 | Goldman, Sachs & Co. | Systems and methods for managing risk associated with a geo-political area |
| US8209246B2 (en) | 2001-03-20 | 2012-06-26 | Goldman, Sachs & Co. | Proprietary risk management clearinghouse |
| US9219708B2 (en) | 2001-03-22 | 2015-12-22 | DialwareInc. | Method and system for remotely authenticating identification devices |
| US20020147690A1 (en) * | 2001-04-04 | 2002-10-10 | Tam Richard K. | E-commerce using an identifier |
| US7725427B2 (en) | 2001-05-25 | 2010-05-25 | Fred Bishop | Recurrent billing maintenance with radio frequency payment devices |
| US7650314B1 (en) | 2001-05-25 | 2010-01-19 | American Express Travel Related Services Company, Inc. | System and method for securing a recurrent billing transaction |
| US9024719B1 (en) | 2001-07-10 | 2015-05-05 | Xatra Fund Mx, Llc | RF transaction system and method for storing user personal data |
| US8548927B2 (en) | 2001-07-10 | 2013-10-01 | Xatra Fund Mx, Llc | Biometric registration for facilitating an RF transaction |
| US7303120B2 (en) | 2001-07-10 | 2007-12-04 | American Express Travel Related Services Company, Inc. | System for biometric security using a FOB |
| US8960535B2 (en) | 2001-07-10 | 2015-02-24 | Iii Holdings 1, Llc | Method and system for resource management and evaluation |
| US7249112B2 (en) | 2002-07-09 | 2007-07-24 | American Express Travel Related Services Company, Inc. | System and method for assigning a funding source for a radio frequency identification device |
| US9454752B2 (en) | 2001-07-10 | 2016-09-27 | Chartoleaux Kg Limited Liability Company | Reload protocol at a transaction processing entity |
| US7360689B2 (en) | 2001-07-10 | 2008-04-22 | American Express Travel Related Services Company, Inc. | Method and system for proffering multiple biometrics for use with a FOB |
| US8538863B1 (en) | 2001-07-10 | 2013-09-17 | American Express Travel Related Services Company, Inc. | System and method for facilitating a transaction using a revolving use account associated with a primary account |
| US20040236699A1 (en) | 2001-07-10 | 2004-11-25 | American Express Travel Related Services Company, Inc. | Method and system for hand geometry recognition biometrics on a fob |
| US9031880B2 (en) | 2001-07-10 | 2015-05-12 | Iii Holdings 1, Llc | Systems and methods for non-traditional payment using biometric data |
| US7996324B2 (en) | 2001-07-10 | 2011-08-09 | American Express Travel Related Services Company, Inc. | Systems and methods for managing multiple accounts on a RF transaction device using secondary identification indicia |
| US7762457B2 (en) | 2001-07-10 | 2010-07-27 | American Express Travel Related Services Company, Inc. | System and method for dynamic fob synchronization and personalization |
| US8635131B1 (en) | 2001-07-10 | 2014-01-21 | American Express Travel Related Services Company, Inc. | System and method for managing a transaction protocol |
| US7805378B2 (en) | 2001-07-10 | 2010-09-28 | American Express Travel Related Servicex Company, Inc. | System and method for encoding information in magnetic stripe format for use in radio frequency identification transactions |
| US7827106B2 (en) | 2001-07-10 | 2010-11-02 | American Express Travel Related Services Company, Inc. | System and method for manufacturing a punch-out RFID transaction device |
| US7119659B2 (en) | 2001-07-10 | 2006-10-10 | American Express Travel Related Services Company, Inc. | Systems and methods for providing a RF transaction device for use in a private label transaction |
| US8001054B1 (en) | 2001-07-10 | 2011-08-16 | American Express Travel Related Services Company, Inc. | System and method for generating an unpredictable number using a seeded algorithm |
| US8294552B2 (en) | 2001-07-10 | 2012-10-23 | Xatra Fund Mx, Llc | Facial scan biometrics on a payment device |
| US7493288B2 (en) | 2001-07-10 | 2009-02-17 | Xatra Fund Mx, Llc | RF payment via a mobile device |
| US7503480B2 (en) | 2001-07-10 | 2009-03-17 | American Express Travel Related Services Company, Inc. | Method and system for tracking user performance |
| US7705732B2 (en) | 2001-07-10 | 2010-04-27 | Fred Bishop | Authenticating an RF transaction using a transaction counter |
| US8284025B2 (en) | 2001-07-10 | 2012-10-09 | Xatra Fund Mx, Llc | Method and system for auditory recognition biometrics on a FOB |
| US7668750B2 (en) | 2001-07-10 | 2010-02-23 | David S Bonalle | Securing RF transactions using a transactions counter |
| US7925535B2 (en) | 2001-07-10 | 2011-04-12 | American Express Travel Related Services Company, Inc. | System and method for securing RF transactions using a radio frequency identification device including a random number generator |
| US7746215B1 (en) | 2001-07-10 | 2010-06-29 | Fred Bishop | RF transactions using a wireless reader grid |
| JP4082028B2 (en) * | 2001-12-28 | 2008-04-30 | ソニー株式会社 | Information processing apparatus, information processing method, and program |
| US6970855B2 (en) * | 2002-01-29 | 2005-11-29 | Pitney Bowes Inc. | Method and system for enterprise-level unassisted customer shipping |
| US20040012567A1 (en) * | 2002-02-08 | 2004-01-22 | Ashton Jason A. | Secure input device |
| US9569797B1 (en) | 2002-05-30 | 2017-02-14 | Consumerinfo.Com, Inc. | Systems and methods of presenting simulated credit score information |
| US7899707B1 (en) | 2002-06-18 | 2011-03-01 | Ewinwin, Inc. | DAS predictive modeling and reporting function |
| US7689463B1 (en) | 2002-08-28 | 2010-03-30 | Ewinwin, Inc. | Multiple supplier system and method for transacting business |
| US6805287B2 (en) | 2002-09-12 | 2004-10-19 | American Express Travel Related Services Company, Inc. | System and method for converting a stored value card to a credit card |
| US20040125077A1 (en) * | 2002-10-03 | 2004-07-01 | Ashton Jason A. | Remote control for secure transactions |
| WO2004091170A2 (en) | 2003-03-31 | 2004-10-21 | Visa U.S.A. Inc. | Method and system for secure authentication |
| US7364086B2 (en) | 2003-06-16 | 2008-04-29 | Ewinwin, Inc. | Dynamic discount card tied to price curves and group discounts |
| US8590785B1 (en) | 2004-06-15 | 2013-11-26 | Ewinwin, Inc. | Discounts in a mobile device |
| US7318550B2 (en) | 2004-07-01 | 2008-01-15 | American Express Travel Related Services Company, Inc. | Biometric safeguard method for use with a smartcard |
| US8996481B2 (en) | 2004-07-02 | 2015-03-31 | Goldman, Sach & Co. | Method, system, apparatus, program code and means for identifying and extracting information |
| US8762191B2 (en) | 2004-07-02 | 2014-06-24 | Goldman, Sachs & Co. | Systems, methods, apparatus, and schema for storing, managing and retrieving information |
| US8442953B2 (en) | 2004-07-02 | 2013-05-14 | Goldman, Sachs & Co. | Method, system, apparatus, program code and means for determining a redundancy of information |
| US8510300B2 (en) | 2004-07-02 | 2013-08-13 | Goldman, Sachs & Co. | Systems and methods for managing information associated with legal, compliance and regulatory risk |
| JP2008511085A (en) * | 2004-08-25 | 2008-04-10 | マスターカード インターナシヨナル インコーポレーテツド | Method and system for automated payment authentication and settlement |
| US8732004B1 (en) | 2004-09-22 | 2014-05-20 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
| CN1828658A (en) * | 2005-03-31 | 2006-09-06 | 阿里巴巴公司 | Self-possessed resource interacting method and electronic transaction information processing method |
| ITTO20050069U1 (en) * | 2005-05-27 | 2006-11-28 | Candis Srl | PLASTIC MATERIAL SPATULA FOR THE APPLICATION OF WALL AND SIMILAR COATING SUBSTANCES |
| US20060287941A1 (en) * | 2005-06-16 | 2006-12-21 | Microsoft Corporation | Unified service for auctions and classified advertisements |
| EP1915734A4 (en) * | 2005-07-25 | 2011-02-02 | Cardinalcommerce Corp | Method and system for extending payment system via text messaging |
| US7588181B2 (en) * | 2005-09-07 | 2009-09-15 | Ty Shipman | Method and apparatus for verifying the legitamacy of a financial instrument |
| EP2667344A3 (en) | 2005-10-06 | 2014-08-27 | C-Sam, Inc. | Transactional services |
| US7711636B2 (en) | 2006-03-10 | 2010-05-04 | Experian Information Solutions, Inc. | Systems and methods for analyzing data |
| EP2365468A1 (en) * | 2006-04-25 | 2011-09-14 | UC Group Ltd. | Systems and methods for conducting financial transactions over a network |
| US20070250441A1 (en) | 2006-04-25 | 2007-10-25 | Uc Group Limited | Systems and methods for determining regulations governing financial transactions conducted over a network |
| US7937331B2 (en) * | 2006-06-23 | 2011-05-03 | United Parcel Service Of America, Inc. | Systems and methods for international dutiable returns |
| US8577744B2 (en) * | 2006-12-27 | 2013-11-05 | Datascape, Inc. | System and method for effecting auction item payments through a network portal |
| BRPI0806457A2 (en) | 2007-01-09 | 2011-09-06 | Visa Usa Inc | Method mobile phone and system |
| US7866551B2 (en) * | 2007-02-15 | 2011-01-11 | Visa U.S.A. Inc. | Dynamic payment device characteristics |
| US20080288400A1 (en) | 2007-04-27 | 2008-11-20 | Cashedge, Inc. | Centralized Payment Method and System for Online and Offline Transactions |
| US20080275771A1 (en) * | 2007-05-01 | 2008-11-06 | Visa U.S.A. Inc. | Merchant transaction based advertising |
| WO2008137540A1 (en) * | 2007-05-03 | 2008-11-13 | Mastercard International Incorporated | Method and system for controlling risk in a payment transaction |
| US11257080B2 (en) | 2007-05-04 | 2022-02-22 | Michael Sasha John | Fraud deterrence for secure transactions |
| US9122867B2 (en) * | 2007-06-08 | 2015-09-01 | International Business Machines Corporation | Techniques for presenting password feedback to a computer system user |
| US20090063334A1 (en) * | 2007-08-28 | 2009-03-05 | Alistair Duncan | Business-to-business transaction processing utilizing electronic payment network |
| US9690820B1 (en) | 2007-09-27 | 2017-06-27 | Experian Information Solutions, Inc. | Database system for triggering event notifications based on updates to database records |
| US20090112767A1 (en) | 2007-10-25 | 2009-04-30 | Ayman Hammad | Escrow system and method |
| US10008067B2 (en) | 2008-06-16 | 2018-06-26 | Visa U.S.A. Inc. | System and method for authorizing financial transactions with online merchants |
| US8707319B2 (en) * | 2008-06-26 | 2014-04-22 | Visa International Service Association | Resource location verification by comparing and updating resource location with a location of a consumer device after a threshold of location mismatches is exceeded |
| US8412625B2 (en) * | 2008-08-25 | 2013-04-02 | Bruno Pilo' & Associates, Llc | System and methods for a multi-channel payment platform |
| US20100174638A1 (en) | 2009-01-06 | 2010-07-08 | ConsumerInfo.com | Report existence monitoring |
| US20100280914A1 (en) * | 2009-05-04 | 2010-11-04 | Mark Carlson | Security system and method including alert messages |
| US8554631B1 (en) * | 2010-07-02 | 2013-10-08 | Jpmorgan Chase Bank, N.A. | Method and system for determining point of sale authorization |
| US20120078780A1 (en) * | 2010-09-28 | 2012-03-29 | Bank Of America Corporation | Transactional savings and investments |
| US20120166230A1 (en) * | 2010-12-28 | 2012-06-28 | Stubhub, Inc. | Dynamic item creation at point of sale |
| US9286608B1 (en) * | 2010-12-29 | 2016-03-15 | Amazon Technologies, Inc. | System and method for predictive payment authorizations |
| US20120203666A1 (en) * | 2011-02-09 | 2012-08-09 | Tycoon Unlimited, Inc. | Contactless wireless transaction processing system |
| US9558519B1 (en) | 2011-04-29 | 2017-01-31 | Consumerinfo.Com, Inc. | Exposing reporting cycle information |
| CA2835734A1 (en) | 2011-05-11 | 2012-11-15 | Mark Itwaru | Split mobile payment system |
| US9734498B2 (en) | 2011-05-11 | 2017-08-15 | Riavera Corp | Mobile image payment system using short codes |
| US9721243B2 (en) | 2011-05-11 | 2017-08-01 | Riavera Corp. | Mobile payment system using subaccounts of account holder |
| US10223674B2 (en) | 2011-05-11 | 2019-03-05 | Riavera Corp. | Customized transaction flow for multiple transaction types using encoded image representation of transaction information |
| US8616453B2 (en) | 2012-02-15 | 2013-12-31 | Mark Itwaru | System and method for processing funds transfer between entities based on received optical machine readable image information |
| US9547861B2 (en) | 2011-05-11 | 2017-01-17 | Mark Itwaru | System and method for wireless communication with an IC chip for submission of pin data |
| US9785935B2 (en) | 2011-05-11 | 2017-10-10 | Riavera Corp. | Split mobile payment system |
| US9715704B2 (en) | 2011-05-11 | 2017-07-25 | Riavera Corp | Merchant ordering system using optical machine readable image representation of invoice information |
| CN103688526B (en) | 2011-06-03 | 2015-12-23 | Uc集团有限公司 | By the system and method for the registration of multiple websites, checking and supervisory user |
| JP2015501467A (en) * | 2011-10-06 | 2015-01-15 | インターコンチネンタル グレート ブランズ エルエルシー | Method and system for facilitating face-to-face exchange |
| US11138573B2 (en) * | 2011-10-25 | 2021-10-05 | Isi Corporation | Electronic money transfer payment method and system for same |
| US10339525B2 (en) | 2011-10-27 | 2019-07-02 | Boom! Payments, Inc. | Confirming local marketplace transaction consummation for online payment consummation |
| US8271394B1 (en) * | 2011-10-27 | 2012-09-18 | Bogaard Erik T | Confirming local marketplace transaction consummation for online payment consummation |
| CN103177388B (en) * | 2011-12-22 | 2016-12-07 | 中国银联股份有限公司 | For authoring system and for authorization method |
| US20130204776A1 (en) * | 2012-02-08 | 2013-08-08 | F. Charles King | E-commerce Payment and Delivery System and Method |
| US10395247B2 (en) | 2012-03-07 | 2019-08-27 | Early Warning Services, Llc | Systems and methods for facilitating a secure transaction at a non-financial institution system |
| US9691056B2 (en) | 2012-03-07 | 2017-06-27 | Clearxchange, Llc | System and method for transferring funds |
| US10395223B2 (en) | 2012-03-07 | 2019-08-27 | Early Warning Services, Llc | System and method for transferring funds |
| US10318936B2 (en) | 2012-03-07 | 2019-06-11 | Early Warning Services, Llc | System and method for transferring funds |
| US11593800B2 (en) | 2012-03-07 | 2023-02-28 | Early Warning Services, Llc | System and method for transferring funds |
| US10970688B2 (en) | 2012-03-07 | 2021-04-06 | Early Warning Services, Llc | System and method for transferring funds |
| US8401923B1 (en) | 2012-05-04 | 2013-03-19 | Transengine Technologies, LLC | Method for a ticket exchange across different systems of record |
| US20130346173A1 (en) * | 2012-06-25 | 2013-12-26 | Ebay, Inc. | Driving New User Acquisition from Payment Transactions |
| US8918341B2 (en) * | 2013-03-06 | 2014-12-23 | United States Postal Service | System and method for international merchandise return service |
| US20140279451A1 (en) * | 2013-03-15 | 2014-09-18 | Fedbid, Inc. | Escrow Payment System for Transactions |
| US10325258B2 (en) | 2013-07-03 | 2019-06-18 | Mastercard International Incorporated | Systems and methods for account processing validation |
| US9852391B2 (en) * | 2014-02-22 | 2017-12-26 | Mena360 Dwc-Llc | System and method for logistics network utilizing mobile device location information |
| US10504121B2 (en) | 2014-06-13 | 2019-12-10 | Mastercard International Incorporated | Systems and methods for transmitting messages through personal communication networks |
| US10839359B2 (en) | 2015-03-23 | 2020-11-17 | Early Warning Services, Llc | Payment real-time funds availability |
| US10832246B2 (en) | 2015-03-23 | 2020-11-10 | Early Warning Services, Llc | Payment real-time funds availability |
| US10878387B2 (en) | 2015-03-23 | 2020-12-29 | Early Warning Services, Llc | Real-time determination of funds availability for checks and ACH items |
| US10769606B2 (en) | 2015-03-23 | 2020-09-08 | Early Warning Services, Llc | Payment real-time funds availability |
| US10748127B2 (en) | 2015-03-23 | 2020-08-18 | Early Warning Services, Llc | Payment real-time funds availability |
| CN108140159B (en) | 2015-05-04 | 2023-06-06 | 美国邮政管理局 | System and method for handling internationally distributed items |
| US11037121B2 (en) | 2015-07-21 | 2021-06-15 | Early Warning Services, Llc | Secure real-time transactions |
| US11037122B2 (en) | 2015-07-21 | 2021-06-15 | Early Warning Services, Llc | Secure real-time transactions |
| US10438175B2 (en) | 2015-07-21 | 2019-10-08 | Early Warning Services, Llc | Secure real-time payment transactions |
| US10970695B2 (en) | 2015-07-21 | 2021-04-06 | Early Warning Services, Llc | Secure real-time transactions |
| US10963856B2 (en) | 2015-07-21 | 2021-03-30 | Early Warning Services, Llc | Secure real-time transactions |
| US11151522B2 (en) | 2015-07-21 | 2021-10-19 | Early Warning Services, Llc | Secure transactions with offline device |
| US11386410B2 (en) | 2015-07-21 | 2022-07-12 | Early Warning Services, Llc | Secure transactions with offline device |
| US11062290B2 (en) | 2015-07-21 | 2021-07-13 | Early Warning Services, Llc | Secure real-time transactions |
| US10956888B2 (en) | 2015-07-21 | 2021-03-23 | Early Warning Services, Llc | Secure real-time transactions |
| US11157884B2 (en) | 2015-07-21 | 2021-10-26 | Early Warning Services, Llc | Secure transactions with offline device |
| US11151523B2 (en) | 2015-07-21 | 2021-10-19 | Early Warning Services, Llc | Secure transactions with offline device |
| US11410230B1 (en) | 2015-11-17 | 2022-08-09 | Consumerinfo.Com, Inc. | Realtime access and control of secure regulated data |
| US10757154B1 (en) | 2015-11-24 | 2020-08-25 | Experian Information Solutions, Inc. | Real-time event-based notification system |
| US11151566B2 (en) | 2016-09-19 | 2021-10-19 | Early Warning Services, Llc | Authentication and fraud prevention in provisioning a mobile wallet |
| US10896422B2 (en) * | 2016-12-01 | 2021-01-19 | Mastercard International Incorporated | Systems and methods for detecting collusion between merchants and cardholders |
| US10713657B2 (en) * | 2017-08-01 | 2020-07-14 | Capital One Services, Llc | Systems and methods for estimating authenticity of local network of device initiating remote transaction |
| US11030620B1 (en) * | 2017-08-01 | 2021-06-08 | Wells Fargo Bank, N.A. | Cash reconciliation bots systems |
| WO2019083890A1 (en) * | 2017-10-25 | 2019-05-02 | Klearexpress Corporation | Delivering international shipped items |
| US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
| US11138839B1 (en) | 2019-09-09 | 2021-10-05 | Vigzero Holdings, Llc | Method for automated peer-to-peer wager facilitation system |
| US11336587B1 (en) | 2021-03-11 | 2022-05-17 | Bank Of America Corporation | Electronic system for generation and management of controlled-use resources |
| CN113114541B (en) * | 2021-06-15 | 2021-09-14 | 上海兴容信息技术有限公司 | Method and system for judging whether network connection can be established between network nodes |
Family Cites Families (112)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4341951A (en) * | 1980-07-02 | 1982-07-27 | Benton William M | Electronic funds transfer and voucher issue system |
| US4755872A (en) * | 1985-07-29 | 1988-07-05 | Zenith Electronics Corporation | Impulse pay per view system and method |
| US4799156A (en) | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
| US5053607A (en) * | 1986-10-06 | 1991-10-01 | Carlson Steven R | Point-of-sale device particularly adapted for processing checks |
| US5023904A (en) * | 1987-08-04 | 1991-06-11 | Science Dynamics Corporation | Direct telephone dial ordering service |
| ZA907106B (en) * | 1989-10-06 | 1991-09-25 | Net 1 Products Pty Ltd | Funds transfer system |
| US5008930A (en) * | 1989-10-24 | 1991-04-16 | At&T Bell Laboratories | Customer definable integrated voice/data call transfer technique |
| US5220501A (en) * | 1989-12-08 | 1993-06-15 | Online Resources, Ltd. | Method and system for remote delivery of retail banking services |
| USRE36788E (en) * | 1990-09-06 | 2000-07-25 | Visa International Service Association | Funds transfer system |
| US5383113A (en) * | 1991-07-25 | 1995-01-17 | Checkfree Corporation | System and method for electronically providing customer services including payment of bills, financial analysis and loans |
| GB9121995D0 (en) | 1991-10-16 | 1991-11-27 | Jonhig Ltd | Value transfer system |
| US5453601A (en) | 1991-11-15 | 1995-09-26 | Citibank, N.A. | Electronic-monetary system |
| US5310997A (en) | 1992-09-10 | 1994-05-10 | Tandy Corporation | Automated order and delivery system |
| CA2100134C (en) * | 1992-09-29 | 1999-06-22 | Raymond Otto Colbert | Secure credit/debit card authorization |
| IL105432A (en) * | 1993-04-16 | 1999-10-28 | New Datacom Res Ltd | Methods and systems for non-program applications for subscriber television |
| US5794207A (en) * | 1996-09-04 | 1998-08-11 | Walker Asset Management Limited Partnership | Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers |
| US5465206B1 (en) * | 1993-11-01 | 1998-04-21 | Visa Int Service Ass | Electronic bill pay system |
| WO1995022113A1 (en) * | 1994-02-14 | 1995-08-17 | Telepay, Inc. | Automated interactive bill payment system |
| US5826241A (en) | 1994-09-16 | 1998-10-20 | First Virtual Holdings Incorporated | Computerized system for making payments and authenticating transactions over the internet |
| CA2592534C (en) | 1994-09-16 | 2014-05-20 | Paypal Inc. | Computerized payment system for purchasing information products by electronic transfer on the internet |
| US5717989A (en) | 1994-10-13 | 1998-02-10 | Full Service Trade System Ltd. | Full service trade system |
| FI100137B (en) | 1994-10-28 | 1997-09-30 | Vazvan Simin | Real-time wireless telecom payment system |
| US5679938A (en) | 1994-12-02 | 1997-10-21 | Telecheck International, Inc. | Methods and systems for interactive check authorizations |
| US5732400A (en) | 1995-01-04 | 1998-03-24 | Citibank N.A. | System and method for a risk-based purchase of goods |
| US5591949A (en) * | 1995-01-06 | 1997-01-07 | Bernstein; Robert J. | Automatic portable account controller for remotely arranging for payment of debt to a vendor |
| US5650604A (en) * | 1995-02-22 | 1997-07-22 | Electronic Data Systems Corporation | System and method for electronic transfer of funds using an automated teller machine to dispense the transferred funds |
| US5745886A (en) * | 1995-06-07 | 1998-04-28 | Citibank, N.A. | Trusted agents for open distribution of electronic money |
| US5664115A (en) | 1995-06-07 | 1997-09-02 | Fraser; Richard | Interactive computer system to match buyers and sellers of real estate, businesses and other property using the internet |
| US5790677A (en) | 1995-06-29 | 1998-08-04 | Microsoft Corporation | System and method for secure electronic commerce transactions |
| WO1997002539A1 (en) * | 1995-07-06 | 1997-01-23 | Hitachi, Ltd. | Electronic money sending system |
| US5659165A (en) * | 1995-07-24 | 1997-08-19 | Citibank. N.A. | Customer-directed, automated process for transferring funds between accounts via a communications network |
| US5825003A (en) * | 1995-07-24 | 1998-10-20 | Citicorp Development Center | Customer-directed, automated process for transferring funds between accounts using a holding account and local processing |
| US5710887A (en) | 1995-08-29 | 1998-01-20 | Broadvision | Computer system and method for electronic commerce |
| US5699528A (en) * | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
| US5757917A (en) * | 1995-11-01 | 1998-05-26 | First Virtual Holdings Incorporated | Computerized payment system for purchasing goods and services on the internet |
| US5796832A (en) * | 1995-11-13 | 1998-08-18 | Transaction Technology, Inc. | Wireless transaction and information system |
| US5778313A (en) * | 1995-12-08 | 1998-07-07 | Cellexis International, Inc. | Pre-paid cellular telephone system |
| US5794210A (en) * | 1995-12-11 | 1998-08-11 | Cybergold, Inc. | Attention brokerage |
| US5729460A (en) * | 1995-12-14 | 1998-03-17 | Francotyp-Postalia Ag & Co. | Method for payment of the recrediting of an electronic postage meter and arrangement for the operation of a data central |
| US6138107A (en) * | 1996-01-04 | 2000-10-24 | Netscape Communications Corporation | Method and apparatus for providing electronic accounts over a public network |
| US5787159A (en) * | 1996-02-27 | 1998-07-28 | Hamilton; Chris | Use of caller ID information |
| CA2197930A1 (en) * | 1996-02-29 | 1997-08-29 | Masayuki Ohki | Electronic wallet and method for operating the same |
| US5815657A (en) | 1996-04-26 | 1998-09-29 | Verifone, Inc. | System, method and article of manufacture for network electronic authorization utilizing an authorization instrument |
| US5897621A (en) * | 1996-06-14 | 1999-04-27 | Cybercash, Inc. | System and method for multi-currency transactions |
| US6026379A (en) * | 1996-06-17 | 2000-02-15 | Verifone, Inc. | System, method and article of manufacture for managing transactions in a high availability system |
| US6047264A (en) | 1996-08-08 | 2000-04-04 | Onsale, Inc. | Method for supplying automatic status updates using electronic mail |
| US6240396B1 (en) * | 1996-09-04 | 2001-05-29 | Priceline.Com Incorporated | Conditional purchase offer management system for event tickets |
| US5991749A (en) * | 1996-09-11 | 1999-11-23 | Morrill, Jr.; Paul H. | Wireless telephony for collecting tolls, conducting financial transactions, and authorizing other activities |
| US6029150A (en) | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
| US6058373A (en) | 1996-10-16 | 2000-05-02 | Microsoft Corporation | System and method for processing electronic order forms |
| US5910896A (en) | 1996-11-12 | 1999-06-08 | Hahn-Carlson; Dean W. | Shipment transaction system and an arrangement thereof |
| US5937396A (en) * | 1996-12-04 | 1999-08-10 | Konya; Arpad | System for ATM/ATM transfers |
| US5991748A (en) * | 1996-12-06 | 1999-11-23 | American Express Travel Related Services Company, Inc. | Methods and apparatus for regenerating a prepaid transaction account |
| US6430305B1 (en) * | 1996-12-20 | 2002-08-06 | Synaptics, Incorporated | Identity verification methods |
| US5903721A (en) | 1997-03-13 | 1999-05-11 | cha|Technologies Services, Inc. | Method and system for secure online transaction processing |
| US6341353B1 (en) * | 1997-04-11 | 2002-01-22 | The Brodia Group | Smart electronic receipt system |
| US6868391B1 (en) * | 1997-04-15 | 2005-03-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Tele/datacommunications payment method and apparatus |
| US5949044A (en) * | 1997-06-13 | 1999-09-07 | Walker Asset Management Limited Partnership | Method and apparatus for funds and credit line transfers |
| US20020174016A1 (en) * | 1997-06-16 | 2002-11-21 | Vincent Cuervo | Multiple accounts and purposes card method and system |
| US6295522B1 (en) * | 1997-07-11 | 2001-09-25 | Cybercash, Inc. | Stored-value card value acquisition method and apparatus |
| US5899980A (en) | 1997-08-11 | 1999-05-04 | Trivnet Ltd. | Retail method over a wide area network |
| EP0917119A3 (en) | 1997-11-12 | 2001-01-10 | Citicorp Development Center, Inc. | Distributed network based electronic wallet |
| US5860068A (en) | 1997-12-04 | 1999-01-12 | Petabyte Corporation | Method and system for custom manufacture and delivery of a data product |
| US7668782B1 (en) * | 1998-04-01 | 2010-02-23 | Soverain Software Llc | Electronic commerce system for offer and acceptance negotiation with encryption |
| WO1999056495A1 (en) * | 1998-04-27 | 1999-11-04 | Aurora Wireless Technologies, Ltd. | System and method for detecting high credit risk customers |
| US6173272B1 (en) * | 1998-04-27 | 2001-01-09 | The Clearing House Service Company L.L.C. | Electronic funds transfer method and system and bill presentment method and system |
| US6206283B1 (en) * | 1998-12-23 | 2001-03-27 | At&T Corp. | Method and apparatus for transferring money via a telephone call |
| US6418420B1 (en) * | 1998-06-30 | 2002-07-09 | Sun Microsystems, Inc. | Distributed budgeting and accounting system with secure token device access |
| US6067532A (en) * | 1998-07-14 | 2000-05-23 | American Express Travel Related Services Company Inc. | Ticket redistribution system |
| US6092053A (en) * | 1998-10-07 | 2000-07-18 | Cybercash, Inc. | System and method for merchant invoked electronic commerce |
| US7533064B1 (en) * | 1998-10-07 | 2009-05-12 | Paypal Inc. | E-mail invoked electronic commerce |
| US6169974B1 (en) * | 1998-10-08 | 2001-01-02 | Paymentech, Inc. | Method for closed loop processing of transactions utilizing bank card association |
| US6263317B1 (en) | 1998-12-01 | 2001-07-17 | Fogdog, Inc. | Web sales channel conflict resolution system |
| EP1006469A1 (en) | 1998-12-02 | 2000-06-07 | Koninklijke KPN N.V. | System for secure transactions |
| DK1181655T3 (en) | 1999-02-08 | 2004-02-02 | United Parcel Service Inc | Package Shipment Systems and Methods Using the Internet |
| US7451114B1 (en) * | 1999-02-19 | 2008-11-11 | Visa International Service Association | Conducting commerce between individuals |
| CA2910997A1 (en) * | 1999-04-30 | 2000-11-09 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
| US6609113B1 (en) * | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
| US7194437B1 (en) * | 1999-05-14 | 2007-03-20 | Amazon.Com, Inc. | Computer-based funds transfer system |
| US7249093B1 (en) * | 1999-09-07 | 2007-07-24 | Rysix Holdings, Llc | Method of and system for making purchases over a computer network |
| US6704717B1 (en) * | 1999-09-29 | 2004-03-09 | Ncr Corporation | Analytic algorithm for enhanced back-propagation neural network processing |
| US6394343B1 (en) * | 1999-10-14 | 2002-05-28 | Jon N. Berg | System for card to card transfer of monetary values |
| US7664703B2 (en) * | 1999-10-26 | 2010-02-16 | The Western Union Company | Value transfer systems and methods |
| US6814282B2 (en) * | 1999-10-26 | 2004-11-09 | First Data Corporation | Systems and methods of introducing and receiving information across a computer network |
| US6502747B1 (en) * | 1999-10-26 | 2003-01-07 | First Data Corporation | System and method for performing money transfer transaction using TCP/IP |
| US6994251B2 (en) * | 1999-10-26 | 2006-02-07 | First Data Corporation | Cash payment for remote transactions |
| US6488203B1 (en) * | 1999-10-26 | 2002-12-03 | First Data Corporation | Method and system for performing money transfer transactions |
| US7395241B1 (en) * | 2000-01-19 | 2008-07-01 | Intuit Inc. | Consumer-directed financial transfers using automated clearinghouse networks |
| US20030083042A1 (en) * | 2000-02-11 | 2003-05-01 | Maher Abuhamdeh | Remote rechargeable prepaid cellular service peripheral device |
| US6612487B2 (en) * | 2000-02-14 | 2003-09-02 | Mas Inco Corporation | Method and system for account activation |
| US20030105710A1 (en) * | 2000-07-11 | 2003-06-05 | Ellen Barbara | Method and system for on-line payments |
| US20020152168A1 (en) * | 2000-07-11 | 2002-10-17 | First Data Corporation | Automated transfer with stored value fund |
| US6769605B1 (en) * | 2000-07-21 | 2004-08-03 | Jason P. Magness | Money transfer system |
| US7031939B1 (en) * | 2000-08-15 | 2006-04-18 | Yahoo! Inc. | Systems and methods for implementing person-to-person money exchange |
| US7415442B1 (en) * | 2000-09-26 | 2008-08-19 | Integrated Technological Systems, Inc. | Integrated technology money transfer system |
| US6993507B2 (en) * | 2000-12-14 | 2006-01-31 | Pacific Payment Systems, Inc. | Bar coded bill payment system and method |
| US8498932B2 (en) * | 2001-05-24 | 2013-07-30 | Daniel W. Davis | Card based transfer account |
| US7742984B2 (en) * | 2001-07-06 | 2010-06-22 | Hossein Mohsenzadeh | Secure authentication and payment system |
| US7225156B2 (en) * | 2001-07-11 | 2007-05-29 | Fisher Douglas C | Persistent dynamic payment service |
| KR100424432B1 (en) * | 2001-12-15 | 2004-03-30 | 한양이엔지(주) | Ionized Cleaning Apparatus for Plastic Bottles |
| CA2488730A1 (en) * | 2002-06-11 | 2003-12-18 | First Data Corporation | Value processing network and methods |
| US7003493B2 (en) * | 2003-01-22 | 2006-02-21 | First Data Corporation | Direct payment with token |
| US20040188515A1 (en) * | 2003-03-26 | 2004-09-30 | Ivan Jimenez | Pre-paid internet credit card |
| US20050080697A1 (en) * | 2003-10-14 | 2005-04-14 | Foss Sheldon H. | System, method and apparatus for providing financial services |
| US7447663B1 (en) * | 2003-09-10 | 2008-11-04 | Ameriprise Financial, Inc. | Method for on-line client set-up and authorization of automatic electronic funds transfers |
| US7711638B2 (en) * | 2004-03-17 | 2010-05-04 | The Western Union Company | System and method for transferring money |
| US7373239B2 (en) * | 2005-07-06 | 2008-05-13 | Komatsu, Ltd. | Engine control device of work vehicle |
| US7494056B2 (en) * | 2005-08-23 | 2009-02-24 | Kenneth Sturm | Retail package for prepaid debit cards and method for debit card distribution |
| WO2007033071A2 (en) * | 2005-09-13 | 2007-03-22 | Billetel, Llc | Calling card with intergrated banking functions |
| US20070094132A1 (en) * | 2005-10-25 | 2007-04-26 | Waterson Vincent A | System and method for person to person electronic fund transfer using video payphones |
| US8510223B2 (en) * | 2006-08-03 | 2013-08-13 | The Western Union Company | Money transfer transactions via pre-paid wireless communication devices |
| US20080120231A1 (en) * | 2006-11-16 | 2008-05-22 | Charles Megwa | Money refillable credit card |
-
1999
- 1999-07-14 US US09/352,468 patent/US7451114B1/en not_active Expired - Fee Related
-
2000
- 2000-02-18 WO PCT/US2000/004348 patent/WO2000049554A2/en active IP Right Grant
- 2000-02-18 EP EP00911887A patent/EP1272947A2/en not_active Ceased
- 2000-02-18 AU AU33709/00A patent/AU779188B2/en not_active Expired
- 2000-02-18 CA CA002371820A patent/CA2371820A1/en not_active Abandoned
-
2003
- 2003-05-05 US US10/429,440 patent/US7499886B2/en not_active Expired - Fee Related
-
2005
- 2005-04-13 AU AU2005201681A patent/AU2005201681B2/en not_active Expired
-
2008
- 2008-08-12 US US12/190,130 patent/US7921038B2/en not_active Expired - Fee Related
-
2010
- 2010-09-28 US US12/892,807 patent/US8473353B2/en not_active Expired - Lifetime
-
2012
- 2012-04-18 US US13/450,235 patent/US20120203699A1/en not_active Abandoned
- 2012-04-18 US US13/450,153 patent/US9665862B2/en not_active Expired - Lifetime
- 2012-04-18 US US13/450,298 patent/US9665863B2/en not_active Expired - Lifetime
- 2012-04-18 US US13/449,715 patent/US20120203652A1/en not_active Abandoned
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002091249A1 (en) * | 2001-05-09 | 2002-11-14 | Flurosolutions Pty Ltd | A payment system |
Also Published As
| Publication number | Publication date |
|---|---|
| US7921038B2 (en) | 2011-04-05 |
| US9665863B2 (en) | 2017-05-30 |
| US20120203654A1 (en) | 2012-08-09 |
| US20030195843A1 (en) | 2003-10-16 |
| AU2005201681A1 (en) | 2005-05-12 |
| US7499886B2 (en) | 2009-03-03 |
| US20110087528A1 (en) | 2011-04-14 |
| WO2000049554A8 (en) | 2002-10-31 |
| AU3370900A (en) | 2000-09-04 |
| US20120203699A1 (en) | 2012-08-09 |
| US20120203653A1 (en) | 2012-08-09 |
| WO2000049554A2 (en) | 2000-08-24 |
| US20120203652A1 (en) | 2012-08-09 |
| AU779188B2 (en) | 2005-01-13 |
| US8473353B2 (en) | 2013-06-25 |
| US20090037304A1 (en) | 2009-02-05 |
| EP1272947A2 (en) | 2003-01-08 |
| US7451114B1 (en) | 2008-11-11 |
| US9665862B2 (en) | 2017-05-30 |
| AU2005201681B2 (en) | 2008-07-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9665863B2 (en) | Conducting commerce between individuals | |
| US7499889B2 (en) | Transaction system | |
| US7483858B2 (en) | Network-based system | |
| US7720760B1 (en) | Consumer-directed financial transfers using automated clearinghouse networks | |
| US20050177437A1 (en) | E-commerce system | |
| EP1020824A2 (en) | Technique for conducting secure transactions over a network | |
| US20020152160A1 (en) | Online funds transfer method | |
| EP1421732B1 (en) | Transaction system | |
| KR20010034629A (en) | A method for using a telephone calling card for business transactions | |
| KR20010000531A (en) | pay-broker server system and pay-broking method thereof | |
| EP1744518A2 (en) | Transaction system | |
| CA2592534A1 (en) | Computerized payment system for purchasing information products by electronic transfer on the internet | |
| WO2000070512A1 (en) | Direct payment through internet bank at electronic shopping | |
| JP2002157534A (en) | Safe payment method by credit card | |
| WO2000067170A1 (en) | Payment by card at electronic shopping | |
| KR20020034643A (en) | Service system executing as proxy for affirmation of receipt without bankbook in internet business and the method for the service | |
| ZA200309142B (en) | A transaction facilitation system. | |
| KR20020034642A (en) | Autmatic system for the affirmation of receipt without bankbook using internet and the method for the affirmation | |
| NZ505512A (en) | Ordering and delivery of goods using web (internet) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |
Effective date: 20200218 |