US20110004552A1 - Method and system for conducting a commercial transaction between a buyer and a seller - Google Patents
Method and system for conducting a commercial transaction between a buyer and a seller Download PDFInfo
- Publication number
- US20110004552A1 US20110004552A1 US12/882,677 US88267710A US2011004552A1 US 20110004552 A1 US20110004552 A1 US 20110004552A1 US 88267710 A US88267710 A US 88267710A US 2011004552 A1 US2011004552 A1 US 2011004552A1
- Authority
- US
- United States
- Prior art keywords
- payment
- buyer
- seller
- transaction
- issuer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- 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
- 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/22—Payment schemes or models
- G06Q20/24—Credit schemes, i.e. "pay after"
-
- 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
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/03—Credit; Loans; Processing thereof
Definitions
- the present invention generally relates to commercial transactions, and more specifically, to a method and system for conducting a commercial transaction between a buyer and a seller.
- buyers and sellers can establish relationships with one another in a number of different ways. For example, when the transactional volume and/or amount reaches a certain level, a buyer and a seller typically enter into a sales agreement to minimize the risks of exposure and breach by either party. In addition, when a buyer and a seller wish to establish a long-term relationship with one another, they also typically enter into a sales agreement which includes the terms and conditions which govern the rights and obligations of the parties whenever they deal with each other, thereby avoiding the need to negotiate terms and conditions for each transaction on an ad hoc basis.
- a buyer and a seller may have more than one sales agreement between the parties.
- various types of sales agreements often exist and apply to different types of transactions between the parties. Manually reviewing these various types of sales agreements to determine which specific sale agreement applies to a particular transaction is obviously inefficient. Therefore, it would also be desirable to have a system which is capable of collectively storing and maintaining terms and conditions of sales agreements between a buyer and a seller.
- a transaction between a buyer and a seller is typically completed in the following manner.
- a buyer usually issues a purchase order to a seller for goods and/or services which the buyer wishes to purchase.
- the seller Upon receipt of the purchase order, the seller ships the goods to the buyer.
- the seller generally simultaneously forwards an invoice for the amount due when the goods are shipped. It is up to the buyer to honor that invoice and pay within an agreed upon period of time.
- Payment by the buyer is typically made via check or money transfer. Alternatively, payment can also be made via credit cards or similar credit arrangements.
- a normal credit card transaction involves a number of parties, including a buyer who possesses a credit card, a seller, an acquirer, an issuer and a credit card association such as Visa or Mastercard.
- the acquirer is a business entity, e.g., a commercial bank, that has a business relationship with the seller and receives all the credit card transactions from that seller.
- the issuer is a business entity which issues the credit card to the buyer.
- the credit card association such as Visa maintains a network of processing applications, e.g., VisaNet, which facilitates issuance of credit cards and processing of credit card transactions.
- a typical credit card transaction involves the following steps. First, the seller calculates the amount of the transaction or purchase and seeks payment from the buyer. The buyer then presents the seller with his/her credit card. The seller then runs the credit card through a point of sale terminal. The point of sale terminal captures credit card and sales information and sends such information together with an authorization request to the acquirer. The acquirer, in turn, processes the information received from the point of sale terminal and forwards any relevant information and the authorization request to the issuer. The issuer processes the relevant information and the authorization request to determine whether the transaction should be authorized. The issuer then sends an approval or denial code back to the acquirer. The acquirer relays the approval or denial code to the point of sale terminal for use by the seller.
- the buyer is allowed to consummate the transaction with the seller.
- the accounts maintained by the issuer and the acquirer are settled and reconciled.
- the issuer transfers the transaction amount minus a fee to the acquirer.
- the acquirer then deducts a fee from the amount received from the issuer.
- the remaining amount is then transferred by the acquirer to the seller's account.
- a separate fee is charged by the credit card association for use of its network to facilitate the transaction.
- Cards transactions are generally well accepted. Computer systems have been developed to process these transactions in a reliable and secure manner.
- One such computer system known as VisaNet is developed by Visa to process credit card transactions. Therefore, it would be desirable to have a system which is capable of taking advantage of currently available computing resources thereby further expediting and facilitating transactions between buyers and sellers.
- a system for conducting a commercial transaction between a buyer and a seller includes a transaction processing system for facilitating payment for a transaction between the buyer and the seller.
- the transaction processing system also interacts with an issuer, an acquirer and a credit card association, such as Visa (via VisaNet).
- the issuer issues and manages an account for the buyer.
- the acquirer manages an account for the seller.
- the transaction processing system Before the transaction processing system is used to process transactions between the buyer and the seller, certain information is obtained from the buyer, the seller, the issuer and the acquirer and stored on the system. Each buyer and seller are registered in the system. Upon registration, the pre-negotiated terms and conditions which are to be used to govern the transactions between the buyer and the seller are collected and stored on the system. Such terms and conditions are obtained, for example, from a sales agreement between the buyer and the seller. In addition, the system also stores pre-negotiated terms and conditions agreed to amongst the buyer, the seller, the issuer and the acquirer.
- the transaction processing system handles a transaction between a buyer and a seller in the following exemplary manner.
- An electronic invoice is first posted to the system by the seller or another system.
- the system Upon accepting the electronic invoice, the system creates one or more payment instructions.
- Each payment instruction corresponds to a payment transaction.
- one invoice represents one payment transaction, and hence, one payment instruction is created.
- multiple payment instructions may be created from a single invoice because a single invoice may represent multiple payment transactions.
- the buyer can cause the system to create a payment instruction without a corresponding electronic invoice.
- the system applies some or all of the previously stored pre-negotiated payment terms and conditions between the buyer and the seller to the payment instruction. For example, if terms for a given buyer-seller contract state that payment is due 45 days from invoice date, that information would be included in the payment instruction when the payment instruction is created.
- the system seeks approval from the buyer.
- the approval can be provided by the buyer through an interface to the system. Alternatively, the approval can be supplied by a third party system on behalf of the buyer.
- the system schedules the payment for the specified date in the payment instruction.
- the system calculates one or more fees, such as a transaction fee, for that particular payment transaction according to a pre-defined variable pricing matrix, which is determined based on the set of pre-negotiated terms and conditions agreed to by the issuer, the acquirer, the seller and the buyer.
- the transaction fee is an amount used by the issuer and the acquirer to compensate each other for processing the payment transaction on behalf of the buyer and the seller.
- the respective portions of the transaction fee to be received by the issuer and the acquirer may vary.
- the transaction fee may be shared by the issuer and the acquirer equally or based on some pre-determined percentage, or alternatively, the transaction fee may belong solely to the issuer.
- information relating to the transaction fee and the payment instruction is formatted into a proper message format(s) and submitted for authorization, clearing and settlement.
- the issuer and the acquirer then communicate with one another directly or indirectly to settle the funds. Additionally, the system provides transaction and activity reports to all relevant parties as well as access to status information for invoices and payments.
- a system for executing a payment transaction between a buyer and a seller comprises: a first interface configured to allow invoices to be submitted for payment; a second interface configured to allow the buyer to receive and approve invoices and create and approve payment instructions; and a transaction processing module configured to handle buyer account(s) and seller account(s) respectively, the transaction processing module is further configured to store a plurality of conditions relating to the buyer, the seller, an issuer and an acquirer; and wherein the transaction processing module enables the issuer and the acquirer to process the invoices in accordance with the plurality of conditions.
- a method for processing a payment transaction between a buyer and a seller comprises: maintaining a buyer account and a seller account for the buyer and the seller respectively; maintaining a plurality of terms and conditions relating to the buyer, the seller, an issuer and an acquirer; approving the payment transaction for payment out of the buyer account; determining a transaction fee for the payment transaction based on the plurality of terms and conditions; calculating a net amount using the transaction fee; obtaining payment authorization for the payment transaction from the issuer; and settling the payment transaction between the issuer and the acquirer.
- FIG. 1 is a simplified schematic diagram illustrating the process interaction of an exemplary embodiment of the present invention
- FIG. 2 is a simplified schematic diagram illustrating an exemplary embodiment of the transaction processing system in accordance with the present invention
- FIG. 3 is a diagram illustrating examples of the Transaction Fee Terms and Conditions.
- FIG. 4 is a flow diagram illustrating how the net amount for each transaction is calculated in accordance with am exemplary embodiment of the present invention.
- a transaction processing system 10 is designed to interact with a number of different parties involved in a transaction including, a buyer 12 , a seller 14 , an issuer 16 , an acquirer 18 and a credit card association, such as Visa (via VisaNet).
- the buyer 12 can be a person or business entity which has contracted with the seller 14 to purchase goods and/or services.
- the seller 14 can be a person or business entity which has established a relationship with the buyer 12 to provide goods and/or services to the buyer 12 .
- Such relationship is typically established via a written contract or agreement.
- the buyer 12 may enter into a contract with the seller 14 on a long-term basis to have the seller 12 be the exclusive provider of office supplies or other commodities for the buyer 12 .
- the relationship between the buyer 12 and the seller 14 will be explained further below.
- the issuer 16 can be a business entity which typically is a financial institution such as a bank.
- the issuer 16 issues one or more transaction accounts to the buyer 12 and is responsible for maintaining and handling the transaction account activities of the buyer 12 in cooperation with the transaction processing system 10 . It should be noted that the issuer 16 may issue and maintain transaction accounts for multiple buyers 12 .
- the acquirer 18 can also be a business entity which typically is a financial institution such as a bank.
- the acquirer 18 is contracted with the seller 14 to accept seller sales drafts and instructions relating to the transaction accounts issued by issuer 16 .
- the acquirer 18 also maintains one or more transaction accounts for the seller 14 and is responsible for maintaining and handling the transaction account activities of the supplier 14 in cooperation with the transaction processing system 10 .
- the acquirer 18 may also maintain similar accounts for multiple sellers 14 .
- the transaction processing system 10 stores and manages transaction accounts for buyers 12 and sellers 14 respectively. It should be understood that a single buyer 12 or seller 14 may have multiple transaction accounts from which payment can be debited and/or credited. In addition, the transaction processing system 10 stores and maintains terms and conditions relating to those transaction accounts. These terms and conditions are usually provided to the transaction processing system 10 at the time of registration of the buyer 12 and/or the seller 14 . These terms and conditions include, for example, pre-negotiated payment terms and conditions between the buyer 12 and the seller 14 , which are to be used to govern transactions between the parties and can be obtained from various sources, such as a sales agreement between the buyer 12 and the seller 14 . As will be further explained below, these terms and conditions are selectively used to process the transactions between the buyer 12 and the seller 14 .
- the transaction processing system 10 also provides the capability to store information relating to the issuers 16 and the acquirers 18 . Such information can be used to determine the appropriate amount of transaction fee to be used by the issuer 16 and the acquirer 18 to compensate each other.
- the transaction processing system 10 also allows the issuer 16 and the acquirer 18 to create and maintain buyer and seller transaction accounts respectively. In order for the transaction processing system 10 to handle a transaction for the buyer 12 and the seller 14 , both the buyer 12 and the seller 14 need to be registered or otherwise have their respective transaction accounts established with the transaction processing system 10 . Additional details of the transaction processing system 10 will be further explained below.
- the transaction processing system 10 operates in the following exemplary manner. The processing of a single invoice is illustrated below. However, it should be understood that multiple invoices can be processed by the transaction processing system 10 at the same time.
- a preliminary step (not shown in FIG. 1 ) when the buyer 12 decides to purchase goods and/or services from the seller 14 , the buyer 12 typically issues a purchase order, or via some other means communicates the purchase order, to the seller 14 .
- the seller 14 Upon receiving the purchase order, the seller 14 then ships the ordered goods or provides a service to the buyer 12 .
- the seller 14 issues an electronic invoice either directly or indirectly through a complementary system (e.g., an e-procurement system) to the transaction processing system 10 .
- a complementary system e.g., an e-procurement system
- the transaction processing system 10 includes an interface which allows invoices to be posted directly by the seller 14 to the transaction processing system 10 .
- the transaction processing system 10 Upon accepting the invoice, the transaction processing system 10 , in turn, creates one or more payment instructions. Each payment instruction corresponds to a payment transaction. Typically, one invoice represents one payment transaction, and hence, one payment instruction is usually created for each invoice. However, it should be understood that multiple payment instructions may be created from a single invoice because a single invoice may represent multiple payment transactions.
- the payment instruction includes payment terms and conditions between the buyer 12 and the seller 14 which are previously stored on the transaction processing system 10 and relevant to that particular payment transaction. Alternatively, the buyer 12 can cause a payment instruction to be generated by the transaction processing system 10 without any accompanying invoice.
- the transaction processing system 10 seeks approval for that payment instruction from the buyer 12 .
- the approval can be provided by the buyer 12 through an interface to the transaction processing system 10 .
- the approval can be supplied by a third party system on behalf of the buyer 12 .
- the transaction processing system 10 schedules the payment for the specified date in the payment instruction.
- the transaction processing system 10 initiates processing of a payment from a transaction account belonging to the buyer 12 pursuant to the payment instruction.
- the transaction processing system 10 Upon initiation of processing of the approved payment instruction, the transaction processing system 10 first determines one or more fees, such as a transaction fee, for that particular payment transaction.
- the transaction fee is an amount used by the issuer 16 and the acquirer 18 to compensate each other for processing the payment transaction.
- the amount of the transaction fee is determined based on terms and conditions previously agreed to amongst the buyer 12 , the seller 14 , the issuer 16 and the acquirer 18 .
- the respective portions of the transaction fee to be received by the issuer 16 and the acquirer 18 may vary depending on the arrangement agreed to between the issuer 16 and the acquirer 18 . Determination of the transaction fee and these terms and conditions will be further explained below.
- the transaction processing system 10 uses the transaction fee and other specified fees, if any, the transaction processing system 10 then calculates the net amount to be received by the seller 14 for the payment transaction being processed. Calculation of the net amount will be further described below.
- the transaction processing system 10 also prepares an authorization request which is forwarded to the issuer 14 via a data transport and processing network 20 , such as VisaNet.
- a data transport and processing network 20 such as VisaNet.
- an authorization response is sent by the issuer 14 to the transaction processing system 10 .
- the transaction processing system 10 Upon receipt of the authorization response, the transaction processing system 10 forwards a settlement file to the acquirer 18 via the data transport and processing network 20 .
- the settlement file includes, among other information, the invoice amount (gross amount), the transaction fee and the net amount (the gross amount minus the transaction fee and other specified fees, if any).
- the acquirer 18 issues a request for the transfer of funds.
- the settlement of funds is then sent from the issuer 16 to the acquirer 18 .
- This settlement of funds between the issuer 16 and the acquirer 18 typically occurs within the data transport and processing network 20 .
- the settlement of funds also occurs between the buyer 12 and the issuer 16 and between the seller 14 and the acquirer 18 . More specifically, the buyer 12 forwards or credits the payment amount (or consolidated payments) to the issuer 16 to cover for payment and processing of the payment transaction by the issuer 16 and the acquirer 18 credits the net amount to the seller 14 .
- the settlement of funds between the buyer 12 and the issuer 16 and between the seller 14 and the acquirer 18 occurs outside of the transaction processing system 10 .
- the transaction processing system 10 interacts with the data transport and processing network 20 in order to carry out certain payment processing, authorization and/or settlement functions.
- the data transport and processing network 20 globally connects the processing systems for all participating issuers 16 and acquirers 18 .
- an example of the data transport and processing network 20 is VisaNet.
- the transaction processing system 10 includes five components, namely, an invoice pre-processor 22 , a payment manager 24 , an issuer pricing engine 26 , an authorization and settlement interface 28 and a payment results manager 30 .
- these five components are implemented in a modular manner; however, it should be understood that they can be implemented in an integral manner as well.
- the transaction processing system 10 may include any number of components which collectively provide the functionality described herein.
- the invoice pre-processor 22 manages input of seller invoices and consolidates these invoices into a standard file format.
- the invoice pre-processor 22 is capable of accepting seller invoices in an electronic format. Alternatively, the invoice pre-processor 22 may receive invoice data which is manually inputted.
- invoice includes a typical invoice and any payment request pursuant to which an amount is to be paid from the buyer 12 to the seller 14 .
- An invoice does not necessarily need to originate from the seller 14 but may be originated from a third party system which issues the invoice on behalf of the seller 14 .
- the buyer 12 cannot create an invoice, but can cause a payment instruction to be created without having received an invoice.
- the invoice pre-processor 22 generates a standardized invoice file which is then forwarded to the payment manager 24 .
- the invoice pre-processor 22 combines all seller invoices into one standard file to be delivered as input into the payment manager 24 .
- the payment manager 24 receives the standardized invoice file from the invoice pre-processor 22 and processes the standardized seller invoices. For each invoice, the payment manager 24 creates a corresponding payment instruction.
- the payment instruction includes certain pre-negotiated payment terms and conditions, if any, between the buyer 12 and the seller 14 which are relevant to the corresponding payment transaction. Alternatively, the buyer 12 can cause a payment instruction to be generated without any accompanying invoice.
- the pre-negotiated payment terms and conditions may include payment timing information such as 2/10/net 30, etc. Other information can also be included to indicate that payments over a certain amount must be paid faster, or certain types of goods can be paid over a longer period of time, etc. In other words, this enables the buyer 12 to reference important contract terms that do not relate directly to calculating the transaction fee.
- a default set of terms and conditions may be used. It should be noted that the payment manager 24 may contain default sets of terms and conditions for various different buyers 12 , sellers 14 , issuers 16 and acquirers 18 .
- the payment manager 24 seeks approval for that payment instruction from the buyer 12 .
- the approval can be provided by the buyer 12 via an interface to the payment manager 24 , or alternatively, the approval can be supplied by a third party system on behalf of the buyer 12 .
- the payment manager 24 schedules the payment for the specified date in the payment instruction. On the scheduled day of payment, the payment manager 24 invokes the issuer pricing engine 26 to process the payment transaction, as will be described further below.
- the payment manager 24 keeps track of the status of each invoice or payment transaction. Each invoice or payment transaction may assume one of a number of status.
- a “scheduled” invoice is an invoice which is scheduled for payment on a particular due date.
- a “pending” invoice is an invoice for which an authorization request has already been issued.
- a “declined” invoice is an invoice which has been refused by the issuer 16 .
- An “authorized” invoice is an invoice which has been approved by the issuer 16 .
- a “settled” invoice is an invoice for which settlement fund has already taken place.
- the payment manager 24 cooperates with the payment results processor 30 to update the status of each pending invoice or payment transaction.
- the payment manager 24 further provides various functions and services to the buyer 12 , the seller 14 , the issuer 16 and the acquirer 18 .
- the payment manager 24 allows the buyer 12 to perform a number of tasks, including, for example, (1) administering users belonging to the buyer 12 , such as controlling user access levels and roles with identity authentication; (2) viewing and printing a listing of open invoices; (3) viewing payment terms and conditions for sellers presenting the invoices; (4) approving or rejecting invoices; (5) selecting invoices to pay from list of open invoices; (6) viewing payment status of invoices; (6) creating a payment for a seller if there is no associated invoice; (8) entering or selecting payment variables, such as amount, disbursement account and date, including scheduling in advance for deferred settlement; (9) defining and enforcing payment approval process and authorization levels; (10) placing payments on hold or canceling payments; (11) viewing historical invoice or payment transactions; and (12) downloading invoice or payment data.
- administering users belonging to the buyer 12 such as controlling user access levels and roles with identity authentication
- viewing and printing a listing of open invoices such as viewing payment terms and conditions for sellers presenting the invoices; (4) approving or rejecting
- the payment manager 24 allows the seller 14 to create invoices and view the status of relevant invoices and payments.
- the payment manager 24 allows the acquirer 18 to create accounts for sellers 14 and their respective users.
- the payment manager 24 permits the issuer 16 to perform the following exemplary functions, including, for example, (1) entering payment account information for each buyer 12 ; (2) providing customer service to the buyer 12 ; and (3) creating accounts for additional buyers 12 and their respective users.
- the payment manager 24 invokes the issuer pricing engine 26 to process the payment transactions. More specifically, the issuer pricing engine 26 is invoked to determine one or more fees, such as a transaction fee, associated with each payment transaction. These fees may be pre-negotiated amongst and/or between the various parties including the issuer 16 , the acquirer 18 , the buyer 12 and the seller 14 . For example, the transaction fee is based on several parameters defined among the issuer 16 , the acquirer 18 , the buyer 12 and the seller 14 . These parameters are collectively known as the “Transaction Fee Terms and Conditions.” The transaction fee is used by the acquirer 18 and the issuer 16 to compensate each other for each payment transaction.
- a transaction fee such as a transaction fee
- the respective portions of the transaction fee to be received by the issuer 16 and the acquirer 18 may vary depending on the arrangement agreed to between the issuer 16 and the acquirer 18 .
- the issuer 16 and the acquirer 18 may agree with each other to split the transaction fee based on a pre-negotiated percentage, such as 50-50; alternatively, the issuer 16 may be entitled to receive the entire transaction fee.
- the Transaction Fee Terms and Conditions are negotiated between several parties, including, for example, (1) the buyer 12 and the seller 14 ; (2) the issuer 16 and the buyer 12 ; (3) the acquirer 18 and the seller 14 ; and (4) the issuer 16 and the acquirer 18 .
- the issuer 16 is preferably responsible for defining, entering and maintaining the Transaction Fee Terms and Conditions using the payment manager 24 .
- the Transaction Fee Terms and Conditions are stored in the issuer pricing engine 26 or another database and are accessible to the relevant parties.
- FIG. 3 is a diagram illustrating examples of the Transaction Fee Terms and Conditions.
- Transaction Fee Term # 3 applies to every payment transaction for Issuer # 9012 .
- Transaction Fee Term # 1 only applies if a payment transaction is made between Buyer # 95 and Seller # 22 using account # 121212 .
- Transaction Fee Term # 2 applies to every payment transaction between Buyer # 18 and Seller # 22 .
- Other examples of the Transaction Fee and Terms and Conditions include a set of five transaction size ranges that apply to a hierarchy of relationships. The set of transaction size ranges may be payments between $0-$500, $501-$1000, $1001-$5000, etc.
- the net amount for each payment transaction is then calculated by subtracting the transaction fee from a gross amount.
- the gross amount represents the payment amount which is to be paid by the buyer 12 for the payment transaction being processed.
- additional fees may be deducted from the net amount.
- the acquirer 18 may require the seller 14 to pay other fees in order for the acquirer 18 to handle certain payment transactions on behalf of the seller 14 .
- FIG. 4 is a flow diagram illustrating how the issuer pricing engine 26 calculates the net amount for each payment transaction.
- the issuer pricing engine 26 receives the payment instruction corresponding to the payment transaction to be processed from the payment manager 24 .
- the issuer pricing engine 26 attempts to retrieve a specific set of terms and conditions associated with that particular payment transaction for use in calculating the transaction fee.
- a specific set of terms and conditions does not exist, a default set of terms and conditions may be retrieved at 46 .
- the set of terms and conditions include information, such as pricing parameters, which is used to calculate the transaction fee.
- the transaction size ranges and their associated pricing factors are obtained from within the retrieved set of terms and conditions.
- Each range may have different pricing factors.
- the pricing factor for the range of $0-$500 may be a basis rate which is based purely on percent calculation, such as 1.5% of the gross amount; the pricing factor for the range of $501 to $632 may be 1% of the gross amount plus a flat fee of $5; the pricing factor for the range of $633 to $999 may be purely a flat fee, etc.
- the transaction fee is calculated by applying the appropriate pricing factor against the gross amount.
- the pricing factor may include a basis rate or percentage only, flat fee only or combination of the two with specific and defined values. It should be understood that other formulations or criteria may be used as the appropriate pricing factor.
- the issuer pricing engine 26 determines whether the transaction fee is less than a minimum fee.
- the minimum fee is part of the negotiated fees in the variable pricing negotiation between issuers, acquirers, etc.
- the minimum fee is used as the transaction fee.
- the issuer pricing engine 26 further determines whether the transaction fee exceeds a maximum fee.
- the maximum fee is also part of the negotiated fees in the variable pricing negotiation between issuers, acquirers, etc. If the transaction fee exceeds the maximum fee, then, at 58 , the maximum fee is used as the transaction fee.
- the net amount is calculated by subtracting the transaction fee from the gross amount. For each payment transaction, the gross amount is the payment amount to be paid by the buyer 12 , the transaction fee is the amount used by the acquirer 18 and the issuer 16 to compensate each other. The net amount is the amount to be received by the seller 14 . Optionally, other fees may be deducted from the net amount. For example, the acquirer 18 may require the seller 14 to pay additional fees for processing of certain specified payment transactions.
- the relevant amounts such as the transaction fee and the net amount, they are consolidated with other information into a calculated payment file for delivery to the authorization and settlement interface 28 .
- the calculated payment file is stored on an archive database or other storage medium for archival and reporting purposes.
- the authorization and settlement interface 28 is responsible for transmitting and receiving payment transaction authorization and/or settlement information to and from the data transport and processing network 20 . For each payment transaction, the data transport and processing network 20 determines whether such transaction is authorized (by the issuer 16 ). Authorization and/or settlement results are then provided to the authorization and settlement interface 28 .
- the payment results manager 30 then receives the authorization and/or settlement results from the authorization and settlement interface 28 and further processes the results. The processed results are then passed back to the payment manager 24 . The payment manager 24 then updates the status of the invoices or payment transactions and allows users to see whether payments for invoices have been settled or have been declined.
- the transaction processing system 10 is implemented on a server which is accessible via a computer network, such as the Internet. Based on the disclosure provided herein, a person of ordinary skill in the art will know of ways and methods to implement the transaction processing system 10 on a server or other configuration.
- the transaction processing system 10 also includes a number of user interfaces.
- the user interfaces allow different users to view and/or modify different information or data residing on the transaction processing system 10 depending on the access authority of such users. For example, an issuer 16 via a user interface may be able to view and modify certain Transaction Fee Terms and Conditions relating to its buyers 12 . A buyer 12 via another user interface may be able to view invoices issued by its sellers 14 .
- a person of ordinary skill in the art will know of other ways and methods to implement user interfaces via a computer network which allow information and data to be accessed.
Abstract
A system for conducting a commercial transaction between a buyer and a seller is disclosed. The system includes a transaction processing system for facilitating payment for a transaction between the buyer and the seller. In addition to the buyer and the seller, the transaction processing system also interacts with an issuer and an acquirer. The issuer issues and manages an account for the buyer. The acquirer manages an account for the seller. The transaction processing system operates as follows. An electronic invoice relating to the transaction is first posted to the system by the seller or another system. Upon accepting the electronic invoice, the system creates a payment instruction. Each time a payment instruction is created, the system applies certain pre-negotiated payment terms and conditions between the buyer and the seller to the payment instruction. After the payment instruction is created, the system seeks approval from the buyer. Upon approval of the payment instruction by the buyer, the system schedules the payment for the specified date in the payment instruction. On the scheduled day of payment, the system calculates one or more fees, such as a transaction fee, for the transaction according to a pre-defined variable pricing matrix, which is determined based on a set of pre-negotiated conditions agreed to by the issuer, the acquirer, the seller and the buyer. For example, the transaction fee is an amount used by the issuer and the acquirer to compensate each other for processing the payment on behalf of the buyer and the seller. After the transaction fee is calculated, information relating to the transaction fee and the payment instruction is formatted into a proper message format(s) and submitted for authorization, clearing and settlement. The issuer and the acquirer then communicate with one another directly or indirectly to settle the funds. Additionally, the system provides transaction and activity reports to all relevant parties as well as access to status information for invoices and payments.
Description
- The present invention generally relates to commercial transactions, and more specifically, to a method and system for conducting a commercial transaction between a buyer and a seller.
- In business-to-business transactions, buyers and sellers can establish relationships with one another in a number of different ways. For example, when the transactional volume and/or amount reaches a certain level, a buyer and a seller typically enter into a sales agreement to minimize the risks of exposure and breach by either party. In addition, when a buyer and a seller wish to establish a long-term relationship with one another, they also typically enter into a sales agreement which includes the terms and conditions which govern the rights and obligations of the parties whenever they deal with each other, thereby avoiding the need to negotiate terms and conditions for each transaction on an ad hoc basis.
- While sales agreements are routinely used by buyers and sellers to establish contractual relationships with one another, the terms and conditions of a sales agreement typically still need to be reviewed and applied to each transaction manually. In other words, even when a buyer and a seller have established a long-term contractual relationship via execution of a sales agreement, whenever a transaction is to be completed between the parties, both parties still need to manually ensure that the transaction is compliant with the terms and conditions of the sales agreement. The examination of the terms and conditions of the sales agreement is usually done by a human being on an individual basis for each transaction. This manual examination process is often tedious, time-consuming and prone to errors. Therefore, it would be desirable to have a system which is capable of storing and applying in an automated manner the terms and conditions of a sales agreement between a buyer and a seller for transactions conducted between the parties.
- Furthermore, a buyer and a seller may have more than one sales agreement between the parties. In fact, as between a buyer and a seller who have a long-term relationship, various types of sales agreements often exist and apply to different types of transactions between the parties. Manually reviewing these various types of sales agreements to determine which specific sale agreement applies to a particular transaction is obviously inefficient. Therefore, it would also be desirable to have a system which is capable of collectively storing and maintaining terms and conditions of sales agreements between a buyer and a seller.
- A transaction between a buyer and a seller is typically completed in the following manner. A buyer usually issues a purchase order to a seller for goods and/or services which the buyer wishes to purchase. Upon receipt of the purchase order, the seller ships the goods to the buyer. The seller generally simultaneously forwards an invoice for the amount due when the goods are shipped. It is up to the buyer to honor that invoice and pay within an agreed upon period of time. Payment by the buyer is typically made via check or money transfer. Alternatively, payment can also be made via credit cards or similar credit arrangements.
- A normal credit card transaction involves a number of parties, including a buyer who possesses a credit card, a seller, an acquirer, an issuer and a credit card association such as Visa or Mastercard. The acquirer is a business entity, e.g., a commercial bank, that has a business relationship with the seller and receives all the credit card transactions from that seller. The issuer is a business entity which issues the credit card to the buyer. The credit card association such as Visa maintains a network of processing applications, e.g., VisaNet, which facilitates issuance of credit cards and processing of credit card transactions.
- A typical credit card transaction involves the following steps. First, the seller calculates the amount of the transaction or purchase and seeks payment from the buyer. The buyer then presents the seller with his/her credit card. The seller then runs the credit card through a point of sale terminal. The point of sale terminal captures credit card and sales information and sends such information together with an authorization request to the acquirer. The acquirer, in turn, processes the information received from the point of sale terminal and forwards any relevant information and the authorization request to the issuer. The issuer processes the relevant information and the authorization request to determine whether the transaction should be authorized. The issuer then sends an approval or denial code back to the acquirer. The acquirer relays the approval or denial code to the point of sale terminal for use by the seller. If the transaction is authorized, the buyer is allowed to consummate the transaction with the seller. Typically, at a later time, the accounts maintained by the issuer and the acquirer are settled and reconciled. The issuer transfers the transaction amount minus a fee to the acquirer. The acquirer then deducts a fee from the amount received from the issuer. The remaining amount is then transferred by the acquirer to the seller's account. A separate fee is charged by the credit card association for use of its network to facilitate the transaction.
- Credit card transactions are generally well accepted. Computer systems have been developed to process these transactions in a reliable and secure manner. One such computer system known as VisaNet is developed by Visa to process credit card transactions. Therefore, it would be desirable to have a system which is capable of taking advantage of currently available computing resources thereby further expediting and facilitating transactions between buyers and sellers.
- A system for conducting a commercial transaction between a buyer and a seller is disclosed. The system includes a transaction processing system for facilitating payment for a transaction between the buyer and the seller. In addition to the buyer and the seller, the transaction processing system also interacts with an issuer, an acquirer and a credit card association, such as Visa (via VisaNet). The issuer issues and manages an account for the buyer. The acquirer manages an account for the seller.
- Before the transaction processing system is used to process transactions between the buyer and the seller, certain information is obtained from the buyer, the seller, the issuer and the acquirer and stored on the system. Each buyer and seller are registered in the system. Upon registration, the pre-negotiated terms and conditions which are to be used to govern the transactions between the buyer and the seller are collected and stored on the system. Such terms and conditions are obtained, for example, from a sales agreement between the buyer and the seller. In addition, the system also stores pre-negotiated terms and conditions agreed to amongst the buyer, the seller, the issuer and the acquirer.
- The transaction processing system handles a transaction between a buyer and a seller in the following exemplary manner. An electronic invoice is first posted to the system by the seller or another system. Upon accepting the electronic invoice, the system creates one or more payment instructions. Each payment instruction corresponds to a payment transaction. Typically, one invoice represents one payment transaction, and hence, one payment instruction is created. However, it should be understood that multiple payment instructions may be created from a single invoice because a single invoice may represent multiple payment transactions. Alternatively, the buyer can cause the system to create a payment instruction without a corresponding electronic invoice.
- Each time a payment instruction is created, the system applies some or all of the previously stored pre-negotiated payment terms and conditions between the buyer and the seller to the payment instruction. For example, if terms for a given buyer-seller contract state that payment is due 45 days from invoice date, that information would be included in the payment instruction when the payment instruction is created.
- After a payment instruction is created, the system seeks approval from the buyer. The approval can be provided by the buyer through an interface to the system. Alternatively, the approval can be supplied by a third party system on behalf of the buyer. Upon approval of a payment instruction by the buyer, the system schedules the payment for the specified date in the payment instruction. On the scheduled day of payment, the system calculates one or more fees, such as a transaction fee, for that particular payment transaction according to a pre-defined variable pricing matrix, which is determined based on the set of pre-negotiated terms and conditions agreed to by the issuer, the acquirer, the seller and the buyer.
- The transaction fee is an amount used by the issuer and the acquirer to compensate each other for processing the payment transaction on behalf of the buyer and the seller. The respective portions of the transaction fee to be received by the issuer and the acquirer may vary. For example, the transaction fee may be shared by the issuer and the acquirer equally or based on some pre-determined percentage, or alternatively, the transaction fee may belong solely to the issuer. After the transaction fee is calculated, information relating to the transaction fee and the payment instruction is formatted into a proper message format(s) and submitted for authorization, clearing and settlement. The issuer and the acquirer then communicate with one another directly or indirectly to settle the funds. Additionally, the system provides transaction and activity reports to all relevant parties as well as access to status information for invoices and payments.
- Accordingly, in an exemplary embodiment, a system for executing a payment transaction between a buyer and a seller, comprises: a first interface configured to allow invoices to be submitted for payment; a second interface configured to allow the buyer to receive and approve invoices and create and approve payment instructions; and a transaction processing module configured to handle buyer account(s) and seller account(s) respectively, the transaction processing module is further configured to store a plurality of conditions relating to the buyer, the seller, an issuer and an acquirer; and wherein the transaction processing module enables the issuer and the acquirer to process the invoices in accordance with the plurality of conditions.
- Accordingly, in another exemplary embodiment, a method for processing a payment transaction between a buyer and a seller, comprises: maintaining a buyer account and a seller account for the buyer and the seller respectively; maintaining a plurality of terms and conditions relating to the buyer, the seller, an issuer and an acquirer; approving the payment transaction for payment out of the buyer account; determining a transaction fee for the payment transaction based on the plurality of terms and conditions; calculating a net amount using the transaction fee; obtaining payment authorization for the payment transaction from the issuer; and settling the payment transaction between the issuer and the acquirer.
- Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to accompanying drawings, like reference numbers indicate identical or functionally similar elements.
-
FIG. 1 is a simplified schematic diagram illustrating the process interaction of an exemplary embodiment of the present invention; -
FIG. 2 is a simplified schematic diagram illustrating an exemplary embodiment of the transaction processing system in accordance with the present invention; -
FIG. 3 is a diagram illustrating examples of the Transaction Fee Terms and Conditions; and -
FIG. 4 is a flow diagram illustrating how the net amount for each transaction is calculated in accordance with am exemplary embodiment of the present invention. - Referring to
FIG. 1 , there is shown the process interaction of an exemplary embodiment of the present invention. According to this exemplary embodiment, atransaction processing system 10 is designed to interact with a number of different parties involved in a transaction including, abuyer 12, aseller 14, anissuer 16, anacquirer 18 and a credit card association, such as Visa (via VisaNet). Thebuyer 12 can be a person or business entity which has contracted with theseller 14 to purchase goods and/or services. - Similarly, the
seller 14 can be a person or business entity which has established a relationship with thebuyer 12 to provide goods and/or services to thebuyer 12. Such relationship is typically established via a written contract or agreement. For example, thebuyer 12 may enter into a contract with theseller 14 on a long-term basis to have theseller 12 be the exclusive provider of office supplies or other commodities for thebuyer 12. The relationship between thebuyer 12 and theseller 14 will be explained further below. - The
issuer 16 can be a business entity which typically is a financial institution such as a bank. Theissuer 16 issues one or more transaction accounts to thebuyer 12 and is responsible for maintaining and handling the transaction account activities of thebuyer 12 in cooperation with thetransaction processing system 10. It should be noted that theissuer 16 may issue and maintain transaction accounts formultiple buyers 12. - Similarly, the
acquirer 18 can also be a business entity which typically is a financial institution such as a bank. Theacquirer 18 is contracted with theseller 14 to accept seller sales drafts and instructions relating to the transaction accounts issued byissuer 16. Furthermore, theacquirer 18 also maintains one or more transaction accounts for theseller 14 and is responsible for maintaining and handling the transaction account activities of thesupplier 14 in cooperation with thetransaction processing system 10. Theacquirer 18 may also maintain similar accounts formultiple sellers 14. - Generally, the
transaction processing system 10 stores and manages transaction accounts forbuyers 12 andsellers 14 respectively. It should be understood that asingle buyer 12 orseller 14 may have multiple transaction accounts from which payment can be debited and/or credited. In addition, thetransaction processing system 10 stores and maintains terms and conditions relating to those transaction accounts. These terms and conditions are usually provided to thetransaction processing system 10 at the time of registration of thebuyer 12 and/or theseller 14. These terms and conditions include, for example, pre-negotiated payment terms and conditions between thebuyer 12 and theseller 14, which are to be used to govern transactions between the parties and can be obtained from various sources, such as a sales agreement between thebuyer 12 and theseller 14. As will be further explained below, these terms and conditions are selectively used to process the transactions between thebuyer 12 and theseller 14. - The
transaction processing system 10 also provides the capability to store information relating to theissuers 16 and theacquirers 18. Such information can be used to determine the appropriate amount of transaction fee to be used by theissuer 16 and theacquirer 18 to compensate each other. - Furthermore, the
transaction processing system 10 also allows theissuer 16 and theacquirer 18 to create and maintain buyer and seller transaction accounts respectively. In order for thetransaction processing system 10 to handle a transaction for thebuyer 12 and theseller 14, both thebuyer 12 and theseller 14 need to be registered or otherwise have their respective transaction accounts established with thetransaction processing system 10. Additional details of thetransaction processing system 10 will be further explained below. - The
transaction processing system 10 operates in the following exemplary manner. The processing of a single invoice is illustrated below. However, it should be understood that multiple invoices can be processed by thetransaction processing system 10 at the same time. As a preliminary step (not shown inFIG. 1 ), when thebuyer 12 decides to purchase goods and/or services from theseller 14, thebuyer 12 typically issues a purchase order, or via some other means communicates the purchase order, to theseller 14. Upon receiving the purchase order, theseller 14 then ships the ordered goods or provides a service to thebuyer 12. - Referring now to
FIG. 1 , after receiving the purchase order, theseller 14 issues an electronic invoice either directly or indirectly through a complementary system (e.g., an e-procurement system) to thetransaction processing system 10. In an exemplary embodiment, thetransaction processing system 10 includes an interface which allows invoices to be posted directly by theseller 14 to thetransaction processing system 10. - Upon accepting the invoice, the
transaction processing system 10, in turn, creates one or more payment instructions. Each payment instruction corresponds to a payment transaction. Typically, one invoice represents one payment transaction, and hence, one payment instruction is usually created for each invoice. However, it should be understood that multiple payment instructions may be created from a single invoice because a single invoice may represent multiple payment transactions. The payment instruction includes payment terms and conditions between thebuyer 12 and theseller 14 which are previously stored on thetransaction processing system 10 and relevant to that particular payment transaction. Alternatively, thebuyer 12 can cause a payment instruction to be generated by thetransaction processing system 10 without any accompanying invoice. - After the payment instruction is created, the
transaction processing system 10 seeks approval for that payment instruction from thebuyer 12. The approval can be provided by thebuyer 12 through an interface to thetransaction processing system 10. Alternatively, the approval can be supplied by a third party system on behalf of thebuyer 12. Upon approval of the payment instruction by thebuyer 12, thetransaction processing system 10 schedules the payment for the specified date in the payment instruction. - On the scheduled day of payment, the
transaction processing system 10 initiates processing of a payment from a transaction account belonging to thebuyer 12 pursuant to the payment instruction. - Upon initiation of processing of the approved payment instruction, the
transaction processing system 10 first determines one or more fees, such as a transaction fee, for that particular payment transaction. The transaction fee is an amount used by theissuer 16 and theacquirer 18 to compensate each other for processing the payment transaction. The amount of the transaction fee is determined based on terms and conditions previously agreed to amongst thebuyer 12, theseller 14, theissuer 16 and theacquirer 18. Furthermore, the respective portions of the transaction fee to be received by theissuer 16 and theacquirer 18 may vary depending on the arrangement agreed to between theissuer 16 and theacquirer 18. Determination of the transaction fee and these terms and conditions will be further explained below. - Using the transaction fee and other specified fees, if any, the
transaction processing system 10 then calculates the net amount to be received by theseller 14 for the payment transaction being processed. Calculation of the net amount will be further described below. - The
transaction processing system 10 also prepares an authorization request which is forwarded to theissuer 14 via a data transport andprocessing network 20, such as VisaNet. - Once the authorization request is approved by the
issuer 14, an authorization response is sent by theissuer 14 to thetransaction processing system 10. Upon receipt of the authorization response, thetransaction processing system 10 forwards a settlement file to theacquirer 18 via the data transport andprocessing network 20. The settlement file includes, among other information, the invoice amount (gross amount), the transaction fee and the net amount (the gross amount minus the transaction fee and other specified fees, if any). - After the settlement file is received by the
acquirer 18, theacquirer 18 issues a request for the transfer of funds. The settlement of funds is then sent from theissuer 16 to theacquirer 18. This settlement of funds between theissuer 16 and theacquirer 18 typically occurs within the data transport andprocessing network 20. The settlement of funds also occurs between thebuyer 12 and theissuer 16 and between theseller 14 and theacquirer 18. More specifically, thebuyer 12 forwards or credits the payment amount (or consolidated payments) to theissuer 16 to cover for payment and processing of the payment transaction by theissuer 16 and theacquirer 18 credits the net amount to theseller 14. The settlement of funds between thebuyer 12 and theissuer 16 and between theseller 14 and theacquirer 18 occurs outside of thetransaction processing system 10. - As shown in
FIG. 1 , in an exemplary embodiment, thetransaction processing system 10 interacts with the data transport andprocessing network 20 in order to carry out certain payment processing, authorization and/or settlement functions. The data transport andprocessing network 20 globally connects the processing systems for all participatingissuers 16 andacquirers 18. As previously mentioned, an example of the data transport andprocessing network 20 is VisaNet. - Referring to
FIG. 2 , there is shown an exemplary embodiment of thetransaction processing system 10. According to this exemplary embodiment, thetransaction processing system 10 includes five components, namely, aninvoice pre-processor 22, apayment manager 24, anissuer pricing engine 26, an authorization andsettlement interface 28 and apayment results manager 30. Preferably, these five components are implemented in a modular manner; however, it should be understood that they can be implemented in an integral manner as well. - It should also be understood that these five components are provided for illustrative purposes only. The
transaction processing system 10 may include any number of components which collectively provide the functionality described herein. - The
invoice pre-processor 22 manages input of seller invoices and consolidates these invoices into a standard file format. Theinvoice pre-processor 22 is capable of accepting seller invoices in an electronic format. Alternatively, theinvoice pre-processor 22 may receive invoice data which is manually inputted. - In addition, it should be understood that the term “invoice” as used herein includes a typical invoice and any payment request pursuant to which an amount is to be paid from the
buyer 12 to theseller 14. An invoice does not necessarily need to originate from theseller 14 but may be originated from a third party system which issues the invoice on behalf of theseller 14. Thebuyer 12 cannot create an invoice, but can cause a payment instruction to be created without having received an invoice. - In any event, the
invoice pre-processor 22 generates a standardized invoice file which is then forwarded to thepayment manager 24. In an exemplary implementation, theinvoice pre-processor 22 combines all seller invoices into one standard file to be delivered as input into thepayment manager 24. - The
payment manager 24 receives the standardized invoice file from theinvoice pre-processor 22 and processes the standardized seller invoices. For each invoice, thepayment manager 24 creates a corresponding payment instruction. The payment instruction includes certain pre-negotiated payment terms and conditions, if any, between thebuyer 12 and theseller 14 which are relevant to the corresponding payment transaction. Alternatively, thebuyer 12 can cause a payment instruction to be generated without any accompanying invoice. For example, the pre-negotiated payment terms and conditions may include payment timing information such as 2/10/net 30, etc. Other information can also be included to indicate that payments over a certain amount must be paid faster, or certain types of goods can be paid over a longer period of time, etc. In other words, this enables thebuyer 12 to reference important contract terms that do not relate directly to calculating the transaction fee. If no specific set of terms or conditions exists for that particular invoice or payment transaction, then a default set of terms and conditions may be used. It should be noted that thepayment manager 24 may contain default sets of terms and conditions for variousdifferent buyers 12,sellers 14,issuers 16 andacquirers 18. - After the payment instruction is created, the
payment manager 24 seeks approval for that payment instruction from thebuyer 12. The approval can be provided by thebuyer 12 via an interface to thepayment manager 24, or alternatively, the approval can be supplied by a third party system on behalf of thebuyer 12. In any event, upon approval of the payment instruction by thebuyer 12, thepayment manager 24 schedules the payment for the specified date in the payment instruction. On the scheduled day of payment, thepayment manager 24 invokes theissuer pricing engine 26 to process the payment transaction, as will be described further below. - The
payment manager 24 keeps track of the status of each invoice or payment transaction. Each invoice or payment transaction may assume one of a number of status. A “scheduled” invoice is an invoice which is scheduled for payment on a particular due date. A “pending” invoice is an invoice for which an authorization request has already been issued. A “declined” invoice is an invoice which has been refused by theissuer 16. An “authorized” invoice is an invoice which has been approved by theissuer 16. Finally, a “settled” invoice is an invoice for which settlement fund has already taken place. Thepayment manager 24 cooperates with thepayment results processor 30 to update the status of each pending invoice or payment transaction. - The
payment manager 24 further provides various functions and services to thebuyer 12, theseller 14, theissuer 16 and theacquirer 18. - With respect to the
buyer 12, thepayment manager 24 allows thebuyer 12 to perform a number of tasks, including, for example, (1) administering users belonging to thebuyer 12, such as controlling user access levels and roles with identity authentication; (2) viewing and printing a listing of open invoices; (3) viewing payment terms and conditions for sellers presenting the invoices; (4) approving or rejecting invoices; (5) selecting invoices to pay from list of open invoices; (6) viewing payment status of invoices; (6) creating a payment for a seller if there is no associated invoice; (8) entering or selecting payment variables, such as amount, disbursement account and date, including scheduling in advance for deferred settlement; (9) defining and enforcing payment approval process and authorization levels; (10) placing payments on hold or canceling payments; (11) viewing historical invoice or payment transactions; and (12) downloading invoice or payment data. - With respect to the
seller 14, thepayment manager 24 allows theseller 14 to create invoices and view the status of relevant invoices and payments. - With respect to the
acquirer 18, thepayment manager 24 allows theacquirer 18 to create accounts forsellers 14 and their respective users. - With respect to the
issuer 16, thepayment manager 24 permits theissuer 16 to perform the following exemplary functions, including, for example, (1) entering payment account information for eachbuyer 12; (2) providing customer service to thebuyer 12; and (3) creating accounts foradditional buyers 12 and their respective users. - As mentioned above, on the scheduled day of payment, the
payment manager 24 invokes theissuer pricing engine 26 to process the payment transactions. More specifically, theissuer pricing engine 26 is invoked to determine one or more fees, such as a transaction fee, associated with each payment transaction. These fees may be pre-negotiated amongst and/or between the various parties including theissuer 16, theacquirer 18, thebuyer 12 and theseller 14. For example, the transaction fee is based on several parameters defined among theissuer 16, theacquirer 18, thebuyer 12 and theseller 14. These parameters are collectively known as the “Transaction Fee Terms and Conditions.” The transaction fee is used by theacquirer 18 and theissuer 16 to compensate each other for each payment transaction. The respective portions of the transaction fee to be received by theissuer 16 and theacquirer 18 may vary depending on the arrangement agreed to between theissuer 16 and theacquirer 18. For example, theissuer 16 and theacquirer 18 may agree with each other to split the transaction fee based on a pre-negotiated percentage, such as 50-50; alternatively, theissuer 16 may be entitled to receive the entire transaction fee. - The Transaction Fee Terms and Conditions are negotiated between several parties, including, for example, (1) the
buyer 12 and theseller 14; (2) theissuer 16 and thebuyer 12; (3) theacquirer 18 and theseller 14; and (4) theissuer 16 and theacquirer 18. Theissuer 16 is preferably responsible for defining, entering and maintaining the Transaction Fee Terms and Conditions using thepayment manager 24. The Transaction Fee Terms and Conditions are stored in theissuer pricing engine 26 or another database and are accessible to the relevant parties. -
FIG. 3 is a diagram illustrating examples of the Transaction Fee Terms and Conditions. As shown inFIG. 3 , for example, TransactionFee Term # 3 applies to every payment transaction forIssuer # 9012. ForIssuer # 1234, TransactionFee Term # 1 only applies if a payment transaction is made betweenBuyer # 95 andSeller # 22 usingaccount # 121212. ForIssuer # 5678, since no account is specified, TransactionFee Term # 2 applies to every payment transaction betweenBuyer # 18 andSeller # 22. Other examples of the Transaction Fee and Terms and Conditions include a set of five transaction size ranges that apply to a hierarchy of relationships. The set of transaction size ranges may be payments between $0-$500, $501-$1000, $1001-$5000, etc. These ranges can be established by the parties involved. For example, an individual matrix can be established for (1) each buyer and seller relationship, (2) for all sellers to a certain buyer, (3) for all sellers with a relationship to a certain acquirer, etc. Other Transaction Fee and Terms and Conditions may include additional fees for new value added services such as guaranteed payment. - The net amount for each payment transaction is then calculated by subtracting the transaction fee from a gross amount. The gross amount represents the payment amount which is to be paid by the
buyer 12 for the payment transaction being processed. Optionally, additional fees may be deducted from the net amount. For example, theacquirer 18 may require theseller 14 to pay other fees in order for theacquirer 18 to handle certain payment transactions on behalf of theseller 14. -
FIG. 4 is a flow diagram illustrating how theissuer pricing engine 26 calculates the net amount for each payment transaction. At 40, theissuer pricing engine 26 receives the payment instruction corresponding to the payment transaction to be processed from thepayment manager 24. At 42, theissuer pricing engine 26 attempts to retrieve a specific set of terms and conditions associated with that particular payment transaction for use in calculating the transaction fee. At 44, if a specific set of terms and conditions does not exist, a default set of terms and conditions may be retrieved at 46. In any event, the set of terms and conditions include information, such as pricing parameters, which is used to calculate the transaction fee. - At 48, for example, the transaction size ranges and their associated pricing factors are obtained from within the retrieved set of terms and conditions. Each range may have different pricing factors. For example, the pricing factor for the range of $0-$500 may be a basis rate which is based purely on percent calculation, such as 1.5% of the gross amount; the pricing factor for the range of $501 to $632 may be 1% of the gross amount plus a flat fee of $5; the pricing factor for the range of $633 to $999 may be purely a flat fee, etc. At 50, the transaction fee is calculated by applying the appropriate pricing factor against the gross amount. As described above, the pricing factor may include a basis rate or percentage only, flat fee only or combination of the two with specific and defined values. It should be understood that other formulations or criteria may be used as the appropriate pricing factor.
- At 52, the
issuer pricing engine 26 determines whether the transaction fee is less than a minimum fee. The minimum fee is part of the negotiated fees in the variable pricing negotiation between issuers, acquirers, etc. At 54, if it is determined that the transaction fee is less than the minimum fee, then the minimum fee is used as the transaction fee. - At 56, the
issuer pricing engine 26 further determines whether the transaction fee exceeds a maximum fee. The maximum fee is also part of the negotiated fees in the variable pricing negotiation between issuers, acquirers, etc. If the transaction fee exceeds the maximum fee, then, at 58, the maximum fee is used as the transaction fee. At 60, the net amount is calculated by subtracting the transaction fee from the gross amount. For each payment transaction, the gross amount is the payment amount to be paid by thebuyer 12, the transaction fee is the amount used by theacquirer 18 and theissuer 16 to compensate each other. The net amount is the amount to be received by theseller 14. Optionally, other fees may be deducted from the net amount. For example, theacquirer 18 may require theseller 14 to pay additional fees for processing of certain specified payment transactions. - Once the relevant amounts, such as the transaction fee and the net amount, are calculated, they are consolidated with other information into a calculated payment file for delivery to the authorization and
settlement interface 28. The calculated payment file is stored on an archive database or other storage medium for archival and reporting purposes. - The authorization and
settlement interface 28 is responsible for transmitting and receiving payment transaction authorization and/or settlement information to and from the data transport andprocessing network 20. For each payment transaction, the data transport andprocessing network 20 determines whether such transaction is authorized (by the issuer 16). Authorization and/or settlement results are then provided to the authorization andsettlement interface 28. - The
payment results manager 30 then receives the authorization and/or settlement results from the authorization andsettlement interface 28 and further processes the results. The processed results are then passed back to thepayment manager 24. Thepayment manager 24 then updates the status of the invoices or payment transactions and allows users to see whether payments for invoices have been settled or have been declined. - In an exemplary embodiment, the
transaction processing system 10 is implemented on a server which is accessible via a computer network, such as the Internet. Based on the disclosure provided herein, a person of ordinary skill in the art will know of ways and methods to implement thetransaction processing system 10 on a server or other configuration. - Furthermore, in order to facilitate access by various users, the
transaction processing system 10 also includes a number of user interfaces. The user interfaces allow different users to view and/or modify different information or data residing on thetransaction processing system 10 depending on the access authority of such users. For example, anissuer 16 via a user interface may be able to view and modify certain Transaction Fee Terms and Conditions relating to itsbuyers 12. Abuyer 12 via another user interface may be able to view invoices issued by itssellers 14. A person of ordinary skill in the art will know of other ways and methods to implement user interfaces via a computer network which allow information and data to be accessed. - It is understood that the examples and embodiments described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims. All publications, patents, and patent applications cited herein are hereby incorporated by reference for all purposes in their entirety.
Claims (21)
1.-42. (canceled)
43. A method comprising:
sending, by a seller, an electronic invoice to a transaction processing system comprising a server, wherein the server in the transaction processing system thereafter creates one or more payment instructions after accepting the electronic invoice, seeks approval for the one or more payment instructions from a buyer, initiates processing of a payment from a transaction account belonging to the buyer pursuant to the one or more payment instructions, determines one or more fees based on terms and conditions previously agreed to amongst at least the buyer, the seller, and an issuer, calculates a net amount to be received by the seller, and prepares an authorization request to be forwarded to the issuer via a data transport and processing network; and
receiving a credit for the net amount.
44. The method of claim 43 wherein the terms and conditions are previously agreed to amongst the buyer, the seller, the issuer, and an acquirer.
45. The method of claim 43 wherein the server includes an invoice pre-processor that generates a standardized invoice file.
46. The method of claim 43 wherein the invoice pre-processor combines all seller invoices into a standard file to be delivered as input into a payment manager.
47. The method of claim 46 wherein the payment manager keeps track of the status of the invoice and the payment.
48. The method of claim 47 wherein the payment manager allows the buyer to administer users belonging to the buyer.
49. The method of claim 47 wherein the payment manager allows the buyer to create a payment for the seller if there is no associated invoice.
50. The method of claim 47 wherein the server further comprises an issuer pricing engine coupled to the payment manager.
51. The method of claim 43 wherein the transaction processing system includes an interface through which the electronic invoice is sent.
52. The method of claim 50 wherein the issuer pricing engine stores the terms and conditions.
53. A method comprising:
receiving one or more payment instructions from a transaction processing system comprising a server, wherein the server in the transaction processing system is configured to receive an electronic invoice from a seller and the creates one or more payment instructions associated with a transaction amount after accepting the electronic invoice, seek approval for the one or more payment instructions from a buyer, initiate processing of a payment from a transaction account belonging to the buyer pursuant to the one or more payment instructions, determine one or more fees based on terms and conditions previously agreed amongst at least the buyer, the seller, and an issuer, calculates a net amount to be received by the seller, and prepare an authorization request to be forwarded to the issuer via a data transport and processing network; and
receiving a debit for the transaction amount.
54. The method of claim 53 wherein the terms and conditions are previously agreed to amongst the buyer, the seller, the issuer, and an acquirer.
55. The method of claim 53 wherein the server includes an invoice pre-processor that generates a standardized invoice file.
56. The method of claim 53 wherein the invoice pre-processor combines all seller invoices into a standard file to be delivered as input into a payment manager.
57. The method of claim 56 wherein the payment manager keeps track of the status of the invoice and the payment.
58. The method of claim 57 wherein the payment manager allows the buyer to administer users belonging to the buyer.
59. The method of claim 57 wherein the payment manager allows the buyer to create a payment for the seller if there is no associated invoice.
60. The method of claim 57 wherein the server further comprises an issuer pricing engine coupled to the payment manager.
61. The method of claim 53 wherein the transaction processing system includes an interface through which the electronic invoice is sent.
62. The method of claim 57 wherein the issuer pricing engine stores the terms and conditions.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/882,677 US20110004552A1 (en) | 2001-10-29 | 2010-09-15 | Method and system for conducting a commercial transaction between a buyer and a seller |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/020,466 US7822679B1 (en) | 2001-10-29 | 2001-10-29 | Method and system for conducting a commercial transaction between a buyer and a seller |
US12/882,677 US20110004552A1 (en) | 2001-10-29 | 2010-09-15 | Method and system for conducting a commercial transaction between a buyer and a seller |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/020,466 Continuation US7822679B1 (en) | 2001-10-29 | 2001-10-29 | Method and system for conducting a commercial transaction between a buyer and a seller |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110004552A1 true US20110004552A1 (en) | 2011-01-06 |
Family
ID=21798761
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/020,466 Active 2027-07-14 US7822679B1 (en) | 2001-10-29 | 2001-10-29 | Method and system for conducting a commercial transaction between a buyer and a seller |
US12/881,831 Abandoned US20110004548A1 (en) | 2001-10-29 | 2010-09-14 | Method and system for conducting a commercial transaction between a buyer and a seller |
US12/882,677 Abandoned US20110004552A1 (en) | 2001-10-29 | 2010-09-15 | Method and system for conducting a commercial transaction between a buyer and a seller |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/020,466 Active 2027-07-14 US7822679B1 (en) | 2001-10-29 | 2001-10-29 | Method and system for conducting a commercial transaction between a buyer and a seller |
US12/881,831 Abandoned US20110004548A1 (en) | 2001-10-29 | 2010-09-14 | Method and system for conducting a commercial transaction between a buyer and a seller |
Country Status (6)
Country | Link |
---|---|
US (3) | US7822679B1 (en) |
EP (1) | EP1454277A4 (en) |
AU (2) | AU2002340294C1 (en) |
CA (1) | CA2465564A1 (en) |
DE (1) | DE20221741U1 (en) |
WO (1) | WO2003038553A2 (en) |
Families Citing this family (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2003287248A1 (en) * | 2002-11-12 | 2004-06-03 | Pharmacia And Upjohn Company | Combination therapy for postmenopausal female sexual dysfunction comprising an androgen, an estrogen and an antimuscarinic |
US20050004919A1 (en) * | 2003-07-03 | 2005-01-06 | Sabre, Inc. | Systems, methods, and computer program products providing a generalized inventory system |
US20050283433A1 (en) | 2004-06-17 | 2005-12-22 | Visa International Service Association | Method and system for providing seller bank receivable discounting services |
US7711639B2 (en) | 2005-01-12 | 2010-05-04 | Visa International | Pre-funding system and method |
US8175961B2 (en) | 2006-11-17 | 2012-05-08 | Visa International Service Association | Method and system for using payment history for conducting commercial transactions |
US20080162295A1 (en) * | 2006-12-29 | 2008-07-03 | Ebay Inc. | Method and system for payment authentication |
US7904389B2 (en) * | 2007-05-30 | 2011-03-08 | Visa U.S.A. Inc. | Real time account update |
US9292850B2 (en) * | 2007-09-10 | 2016-03-22 | Visa U.S.A. Inc. | Host capture |
US8219489B2 (en) | 2008-07-29 | 2012-07-10 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
WO2012149455A2 (en) | 2011-04-29 | 2012-11-01 | Visa International Service Association | Vertical network computing integration, analytics, and automation |
US8788353B2 (en) | 2012-12-03 | 2014-07-22 | Hardison Holding Company, LLC | System and method for presenting a financing instrument at a point of sale |
US10380564B1 (en) | 2013-12-05 | 2019-08-13 | Square, Inc. | Merchant performed banking-type transactions |
US10430760B2 (en) | 2015-11-24 | 2019-10-01 | Bank Of America Corporation | Enhancing communications based on physical trade documents |
US10127209B2 (en) | 2015-11-24 | 2018-11-13 | Bank Of America Corporation | Transforming unstructured documents |
US10319025B2 (en) | 2015-11-24 | 2019-06-11 | Bank Of America Corporation | Executing terms of physical trade documents |
US10410168B2 (en) | 2015-11-24 | 2019-09-10 | Bank Of America Corporation | Preventing restricted trades using physical documents |
WO2017212339A1 (en) * | 2016-06-10 | 2017-12-14 | International Consulting Services FZ LLE | System and method of communicating requests and responses using a communications network |
US11023873B1 (en) * | 2017-03-31 | 2021-06-01 | Square, Inc. | Resources for peer-to-peer messaging |
US10453056B2 (en) | 2017-06-29 | 2019-10-22 | Square, Inc. | Secure account creation |
CN109034797B (en) * | 2018-06-26 | 2021-09-17 | 东莞市大易产业链服务有限公司 | Bill voucher payment method based on block chain technology |
US11410246B2 (en) * | 2019-06-06 | 2022-08-09 | Salus Finance, LLC | System and method for consolidation, reconciliation and payment management |
US11237869B2 (en) | 2019-09-16 | 2022-02-01 | Bank Of America Corporation | System for intelligent routing of resources associated with resource entities |
CN111667259B (en) * | 2020-04-22 | 2021-12-24 | 网联清算有限公司 | Payment method, device and system |
Citations (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4001568A (en) * | 1973-12-29 | 1977-01-04 | Glory Kogyo Kabushiki Kaisha | Monetary receipt and payment managing apparatus |
USD263638S (en) * | 1979-05-14 | 1982-03-30 | American Payment Centers, Inc. | Payment deposit cabinet |
US4325277A (en) * | 1979-05-25 | 1982-04-20 | Laurel Bank Machine Co., Ltd. | Dispenser for making payment of pre-packed paper sheets |
US4370649A (en) * | 1981-05-19 | 1983-01-25 | Fuerle Gerard A | Payment responsive data display network |
US4577061A (en) * | 1982-09-07 | 1986-03-18 | Kurt Katzeff | Arrangement for a pay telephone payment system utilizing a payment card within the telecommunication system |
US4585936A (en) * | 1983-02-10 | 1986-04-29 | Mecelec | Optical process for determining the dimensions of an object in relative movement, and more particularly of a coin in a pre-payment apparatus |
US4796193A (en) * | 1986-07-07 | 1989-01-03 | Pitney Bowes Inc. | Postage payment system where accounting for postage payment occurs at a time subsequent to the printing of the postage and employing a visual marking imprinted on the mailpiece to show that accounting has occurred |
US4797540A (en) * | 1986-11-06 | 1989-01-10 | Omron Tateisi Electronics Co. | Payment making terminal device |
US4799156A (en) * | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
US4822984A (en) * | 1985-12-02 | 1989-04-18 | Patrick Remery | Process for electronic payment using a memory |
US4893237A (en) * | 1986-03-27 | 1990-01-09 | Tokyo Electric Co., Ltd. | Interconnected sales data registration and payment settlement system |
US4906826A (en) * | 1988-09-19 | 1990-03-06 | Visa International Service Association | Usage promotion method for payment card transaction system |
US4920256A (en) * | 1987-03-02 | 1990-04-24 | Crouzet | Universal electronic payment terminal base including memory card programming voltage booster |
US5003585A (en) * | 1986-07-18 | 1991-03-26 | Louis Richer | System for the payment of telephone calls in a private self-switching unit |
US5007084A (en) * | 1988-08-29 | 1991-04-09 | Richard H. Materna | Payment Authorization and Information Device |
US5191193A (en) * | 1989-10-13 | 1993-03-02 | Gemplus Card International | System of payment or information transfer by money card with electronic memory |
US5193057A (en) * | 1988-01-21 | 1993-03-09 | Beneficial Franchise Company Inc. | Electronic income tax refund early payment system with means for creating of a new deposit account for receipt of an electronically transferred refund from the irs |
US5192855A (en) * | 1989-12-06 | 1993-03-09 | Modul-Elektronik Ab | Improvements in cash payment machines enabling acceptance of credit card payment |
US5284253A (en) * | 1992-11-25 | 1994-02-08 | Atlantic Richfield Company | Stacker for electronic payment system key pads |
US5285883A (en) * | 1992-03-11 | 1994-02-15 | Atoll Technology | Automatic payment device and method for recognizing coins |
US5291304A (en) * | 1989-04-18 | 1994-03-01 | Murata Kikai Kabushiki Kaisha | Facsimile apparatus having invoice sentence preparation function |
US5289923A (en) * | 1992-11-23 | 1994-03-01 | Atlantic Richfield Company | Stacker for electronic payment system key pad and printer |
US5297030A (en) * | 1992-04-08 | 1994-03-22 | Ncr Corporation | Method using bill and coin images on a touch screen for processing payment for merchandise items |
US5297674A (en) * | 1992-11-04 | 1994-03-29 | Fellowes Manufacturing Company | Molded bill payment center container with removable trays |
US5305383A (en) * | 1991-04-03 | 1994-04-19 | France Telecom, Telediffusion De France S.A. | Method of electronic payment by chip card by means of numbered tokens allowing the detection of fraud |
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 |
US5387784A (en) * | 1990-10-30 | 1995-02-07 | Societe D'applications Generales D'electricite Et De Mecanique Sagem | Portable payment terminals and network for such terminals |
USRE34872E (en) * | 1986-03-04 | 1995-03-14 | Lucero; James L. | Drive-through credit card payment device |
US5403025A (en) * | 1994-03-03 | 1995-04-04 | Shanley; Thomas M. | Partially preprinted, service invoice record forms, having piggyback vinyl status |
US5491325A (en) * | 1992-08-25 | 1996-02-13 | Huang; Dorge O. | Method and system for payment and payment verification |
US5492212A (en) * | 1993-06-02 | 1996-02-20 | Schlumberger Industries | Device for sorting and storing objects inserted by way of payment in a dispenser |
US5504677A (en) * | 1992-10-15 | 1996-04-02 | Pollin; Robert E. | Automated payment system |
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 |
USD378219S (en) * | 1995-11-21 | 1997-02-25 | Marshlack Dane G | Invoice holder |
US5614892A (en) * | 1995-04-24 | 1997-03-25 | Pom, Inc. | Payment slot communicating apparatus for vendng prices |
US5620182A (en) * | 1990-08-22 | 1997-04-15 | Rossides; Michael T. | Expected value payment method and system for reducing the expected per unit costs of paying and/or receiving a given ammount of a commodity |
US5706925A (en) * | 1993-10-18 | 1998-01-13 | Gemplus Card International | Games machine with electronic payment mechanism |
US5715298A (en) * | 1996-05-16 | 1998-02-03 | Telepay | Automated interactive bill payment system using debit cards |
US5717868A (en) * | 1995-03-07 | 1998-02-10 | Huntington Bancshares Inc. | Electronic payment interchange concentrator |
US5717989A (en) * | 1994-10-13 | 1998-02-10 | Full Service Trade System Ltd. | Full service trade system |
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 |
US5732400A (en) * | 1995-01-04 | 1998-03-24 | Citibank N.A. | System and method for a risk-based purchase of goods |
US5739511A (en) * | 1995-05-11 | 1998-04-14 | Koninklijke Ptt Nederland N.V. | Method for effecting an electronic payment transaction having a variable number of payment units, as well as payment means and system for applying the method |
US5740247A (en) * | 1995-12-22 | 1998-04-14 | Pitney Bowes Inc. | Authorized cellular telephone communication payment refill system |
USD403667S (en) * | 1996-09-12 | 1999-01-05 | Oki Electric Industry Co., Ltd. | Pocket-sized electronic payment and financial transaction terminal including IC card reader |
US5857152A (en) * | 1994-02-01 | 1999-01-05 | Mondex International Limited | Electronic toll payment |
US5870456A (en) * | 1997-01-22 | 1999-02-09 | Telepay, Inc. | Automated interactive bill payment system using debit cards |
US5880454A (en) * | 1995-05-11 | 1999-03-09 | Schlumberger Industries | Electronic payment card with an interchangeable module |
USD406574S (en) * | 1997-10-06 | 1999-03-09 | Verifone, Inc. | Payment instrument |
US5884288A (en) * | 1996-07-01 | 1999-03-16 | Sun Microsystems, Inc. | Method and system for electronic bill payment |
US5883810A (en) * | 1997-09-24 | 1999-03-16 | Microsoft Corporation | Electronic online commerce card with transactionproxy number for online transactions |
US5890140A (en) * | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
US5890137A (en) * | 1995-12-15 | 1999-03-30 | Kabushiki Kaisha N.K. Kikaku | On-line shopping system and the method of payment settlement |
US5893080A (en) * | 1995-07-25 | 1999-04-06 | Bottomline Technologies, Inc. | Disbursement system and method |
US5893907A (en) * | 1995-10-26 | 1999-04-13 | Ukuda; Shuko | Apparatus and system for managing a card number |
US5893902A (en) * | 1996-02-15 | 1999-04-13 | Intelidata Technologies Corp. | Voice recognition bill payment system with speaker verification and confirmation |
US6012048A (en) * | 1997-05-30 | 2000-01-04 | Capital Security Systems, Inc. | Automated banking system for dispensing money orders, wire transfer and bill payment |
US6012740A (en) * | 1998-08-03 | 2000-01-11 | Lupi; L. Anthony | Combination sample medication payment check and medication prescription device |
US6014646A (en) * | 1995-06-08 | 2000-01-11 | France Telecom | Process for making a payment using an account manager |
US6016484A (en) * | 1996-04-26 | 2000-01-18 | Verifone, Inc. | System, method and article of manufacture for network electronic payment instrument and certification of payment and credit collection utilizing a payment |
US6016955A (en) * | 1995-05-12 | 2000-01-25 | Koninklijke Kpn N.V. | Electronic payment method and system having several calculation units and electronic payment devices |
US6021943A (en) * | 1996-10-09 | 2000-02-08 | Chastain; Robert H. | Process for executing payment transactions |
US6029150A (en) * | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
US6038647A (en) * | 1995-12-06 | 2000-03-14 | Fujitsu Limited | Cache memory device and method for providing concurrent independent multiple accesses to different subsets within the device |
US6038548A (en) * | 1997-11-26 | 2000-03-14 | International Business Machines Corporation | System and method for conducting electronic commerce in a computer network using a cashier desk payment framework |
US6044362A (en) * | 1997-09-08 | 2000-03-28 | Neely; R. Alan | Electronic invoicing and payment system |
US6047269A (en) * | 1996-07-19 | 2000-04-04 | Peter Biffar | Self-contained payment system with circulating digital vouchers |
US6047267A (en) * | 1997-05-14 | 2000-04-04 | Portal Software, Inc. | Method and apparatus for tracking multiple payment resources and charging transactions to payment resources in on line transaction processing system |
US6049785A (en) * | 1993-12-16 | 2000-04-11 | Open Market, Inc. | Open network payment system for providing for authentication of payment orders based on a confirmation electronic mail message |
US6049786A (en) * | 1997-07-22 | 2000-04-11 | Unisys Corporation | Electronic bill presentment and payment system which deters cheating by employing hashes and digital signatures |
WO2000058876A1 (en) * | 1999-03-26 | 2000-10-05 | Rdm Corporation | Electronic invoice payment system |
WO2000079451A1 (en) * | 1999-06-17 | 2000-12-28 | Mobius Management Systems, Inc. | Electronic statement, bill presentment and payment system and method |
US6169974B1 (en) * | 1998-10-08 | 2001-01-02 | Paymentech, Inc. | Method for closed loop processing of transactions utilizing bank card association |
US6173269B1 (en) * | 1998-12-16 | 2001-01-09 | Zowi.Com, Inc | Method and apparatus for executing electronic commercial transactions with minors |
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 |
US6178409B1 (en) * | 1996-06-17 | 2001-01-23 | Verifone, Inc. | System, method and article of manufacture for multiple-entry point virtual point of sale architecture |
US6181361B1 (en) * | 1998-07-22 | 2001-01-30 | Dassault Automatismes Et Telecommunications | Device for thermal printing of a rolled paper strip, in particular for a plug-in or cordless portable payment terminal |
US6185545B1 (en) * | 1998-11-17 | 2001-02-06 | Prenet Corporation | Electronic payment system utilizing intermediary account |
US6193152B1 (en) * | 1997-05-09 | 2001-02-27 | Receiptcity.Com, Inc. | Modular signature and data-capture system and point of transaction payment and reward system |
USRE37067E1 (en) * | 1994-08-31 | 2001-02-27 | Koninklijke Ptt Nederland N.V. | Chip card based payment system having an on-card flag for specifying proper completion of a prior card balance replenishment session |
US6199107B1 (en) * | 1998-07-22 | 2001-03-06 | Microsoft Corporation | Partial file caching and read range resume system and method |
US6202054B1 (en) * | 1989-12-08 | 2001-03-13 | Online Resources & Communications Corp. | Method and system for remote delivery of retail banking services |
US6202052B1 (en) * | 1997-05-08 | 2001-03-13 | Simplification, Llc | Fully-automated system for tax reporting, payment and refund |
US6205433B1 (en) * | 1996-06-14 | 2001-03-20 | Cybercash, Inc. | System and method for multi-currency transactions |
US6206285B1 (en) * | 1996-10-01 | 2001-03-27 | Siemens Nixdorf Informationssysteme Aktiengesellschaft | Peripheral assembly kit for the workstation of a goods invoicing system |
US20040010463A1 (en) * | 1996-11-12 | 2004-01-15 | Hahn-Carlson Dean W. | Automated transaction processing system and approach |
US6697702B1 (en) * | 1999-03-12 | 2004-02-24 | U.S. Bancorp | Shipment transaction system and an arrangement thereof |
US6704612B1 (en) * | 1996-11-12 | 2004-03-09 | U.S. Bancorp | Transaction validation system for auditing and method |
US20050033671A1 (en) * | 1996-11-12 | 2005-02-10 | U.S. Bancorp | Automated transaction processing system and approach |
US6856970B1 (en) * | 2000-09-26 | 2005-02-15 | Bottomline Technologies | Electronic financial transaction system |
US20060015455A1 (en) * | 2004-06-09 | 2006-01-19 | Hahn-Carlson Dean W | Order-resource fulfillment and management system and approach |
US20060015454A1 (en) * | 2004-06-09 | 2006-01-19 | Hahn-Carlson Dean W | Distributor-based transaction processing arrangement and approach |
US20070055582A1 (en) * | 1996-11-12 | 2007-03-08 | Hahn-Carlson Dean W | Transaction processing with core and distributor processor implementations |
US7319986B2 (en) * | 1999-09-28 | 2008-01-15 | Bank Of America Corporation | Dynamic payment cards and related management systems and associated methods |
US7336698B2 (en) * | 2002-04-24 | 2008-02-26 | Nokia Corporation | Interference cancellation in receiver of radio system |
US7340433B1 (en) * | 1999-07-30 | 2008-03-04 | Orbian Management Limited | System and method of transaction settlement using trade credit |
Family Cites Families (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE2350418A1 (en) | 1973-10-08 | 1975-04-10 | Gretag Ag | PROCEDURE AND EQUIPMENT FOR CREATING AND EVALUATING FALSE-PROOF MACHINELY READABLE PAYMENT RECEIPTS |
US4116469A (en) | 1977-08-08 | 1978-09-26 | Harriman Russell H | Combined payment and receipt form and method of using |
CH640649A5 (en) | 1979-01-31 | 1984-01-13 | Landis & Gyr Ag | Device for cash payment lots of goods or services. |
FR2484674A1 (en) | 1980-06-11 | 1981-12-18 | Flonic Sa | PREPAIDING MACHINE AND ASSOCIATED DEVICE FOR COLLECTING THE CURRENCY COLLECTED BY THIS MACHINE |
US4480737A (en) | 1981-03-12 | 1984-11-06 | Ara Services, Inc. | Apparatus for recognizing, crushing separating, weighing and making payment for, used metal items, particularly aluminum cans |
US4360727A (en) | 1981-04-09 | 1982-11-23 | Compagnie Generale d'Automatise Societe Anonyme dite | Payment voucher |
JPS59109972A (en) | 1982-12-14 | 1984-06-25 | Omron Tateisi Electronics Co | Transaction processing device |
US5222018A (en) | 1985-07-18 | 1993-06-22 | Pitney Bowes Inc. | System for centralized processing of accounting and payment functions |
US4713761A (en) | 1985-07-18 | 1987-12-15 | Pitney Bowes, Inc. | System for centralized processing of accounting and payment functions |
US5375172A (en) | 1986-07-07 | 1994-12-20 | Chrosny; Wojciech M. | Postage payment system employing encryption techniques and accounting for postage payment at a time subsequent to the printing of postage |
US4972463A (en) | 1986-09-15 | 1990-11-20 | Norand Corporation | In-store multiple device communications unit and centralized data system utilizing same |
FR2605431B1 (en) | 1986-10-16 | 1988-12-02 | France Etat | ELECTRONIC PAYMENT METHOD USING A MEMORY CARD |
US4858121A (en) | 1986-12-12 | 1989-08-15 | Medical Payment Systems, Incorporated | Medical payment system |
FR2613511B1 (en) | 1987-03-30 | 1991-04-05 | Crouzet Sa | PAYMENT MACHINE ISSUING A PROOF |
USD304725S (en) | 1987-12-16 | 1989-11-21 | GEC Plessy Telecommunications Ltd. | Public pay telephone stand with alternative payment means |
US4890228A (en) | 1988-01-21 | 1989-12-26 | Beneficial Management Corporation Of America | Electronic income tax refund early payment system |
US4974878A (en) | 1988-04-20 | 1990-12-04 | Remittance Technology Corporation | Financial data processing system using payment coupons |
ES2009608A6 (en) | 1988-05-31 | 1989-10-01 | Jofemar Sa | Coin operated telephone payment device |
US4860946A (en) | 1988-06-29 | 1989-08-29 | Moore Business Forms, Inc. | Invoice form with card and envelope |
US5258906A (en) | 1988-07-13 | 1993-11-02 | Vital Heart Systems, Inc. | System for remotely authorizing operation of a device and for automatically generating an invoice based on device usage |
US4947028A (en) | 1988-07-19 | 1990-08-07 | Arbor International, Inc. | Automated order and payment system |
EP0372103A1 (en) | 1988-12-05 | 1990-06-13 | Scheidt & Bachmann Gmbh | Method for actuating product and/or service vending machines, and matching vending machine |
FR2643529B1 (en) | 1989-02-22 | 1991-06-07 | Kudelski Sa Fabr Enregistr Nag | PAID TELEVISION SYSTEM USING A MEMORY CARD ASSOCIATED WITH A DECODER |
JP2890452B2 (en) | 1989-04-21 | 1999-05-17 | 株式会社日立製作所 | Deposit and withdrawal reservation system and equipment for it |
FR2660771B1 (en) | 1990-04-05 | 1992-07-24 | Bernard Alain | TELEPHONE PAYMENT SYSTEM. |
US5623547A (en) | 1990-04-12 | 1997-04-22 | Jonhig Limited | Value transfer system |
US5085435A (en) | 1990-08-22 | 1992-02-04 | Rossides Michael T | Method of using a random number supplier for the purpose of reducing currency handling |
DE9013392U1 (en) | 1990-09-21 | 1991-04-25 | Siemens Nixdorf Informationssysteme Ag, 4790 Paderborn, De | |
US5225977A (en) | 1991-03-18 | 1993-07-06 | Hooper John B | Card payment system for service dispensing devices |
US5783808A (en) | 1996-01-11 | 1998-07-21 | J. D. Carreker And Associates, Inc. | Electronic check presentment system having transaction level reconciliation capability |
US5237159A (en) | 1991-07-17 | 1993-08-17 | J. D. Carreker And Associates | Electronic check presentment system |
US5691524A (en) | 1991-07-17 | 1997-11-25 | J.D. Carreker And Associates, Inc. | Electronic check presentment system having a non-ECP exceptions notification system incorporated therein |
US5216620A (en) | 1991-09-23 | 1993-06-01 | Pitney Bowes Inc. | Requesting, reporting and verification system and method for mail carrier payment |
US5359509A (en) | 1991-10-31 | 1994-10-25 | United Healthcare Corporation | Health care payment adjudication and review system |
US5453601A (en) | 1991-11-15 | 1995-09-26 | Citibank, N.A. | Electronic-monetary system |
US6006199A (en) | 1991-12-31 | 1999-12-21 | International Business Machines Corporation | Method and system for automated payment within a computer integrated manufacturing system |
US5255182A (en) | 1992-01-31 | 1993-10-19 | Visa International Service Association | Payment card point-of-sale service quality monitoring system, apparatus, and method |
US5359183A (en) | 1992-04-06 | 1994-10-25 | Rafael Skodlar | Payment card with display |
JP2659896B2 (en) | 1992-04-29 | 1997-09-30 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Structured document copy management method and structured document copy management device |
US5336870A (en) | 1992-05-26 | 1994-08-09 | Hughes Thomas S | System for remote purchase payment transactions and remote bill payments |
US5754655A (en) | 1992-05-26 | 1998-05-19 | Hughes; Thomas S. | System for remote purchase payment and remote bill payment transactions |
US5424938A (en) | 1992-10-13 | 1995-06-13 | First Chicago Corporation | Method and apparatus for providing access to a plurality of payment networks |
US5966698A (en) | 1992-10-15 | 1999-10-12 | Pollin; Robert E. | Automated payment system and method |
CH685891A5 (en) | 1993-01-18 | 1995-10-31 | Ascom Autelca Ag | A method as security concept to prevent unauthorized use of a payment instrument for cashless settling on imprest |
WO1994018640A1 (en) | 1993-02-10 | 1994-08-18 | Turk James J | Method and system for commodity-based currency for payment of accounts |
US5983207A (en) | 1993-02-10 | 1999-11-09 | Turk; James J. | Electronic cash eliminating payment risk |
US5412886A (en) | 1993-03-24 | 1995-05-09 | Quinn; Maureen T. | Calendar oriented monthly bill payment sorter |
US5637846A (en) | 1993-05-14 | 1997-06-10 | Ahold Retail Services Ag | Method and apparatus for electronic payment by a client in a self-service store |
FR2705481B1 (en) | 1993-05-19 | 1995-06-30 | Schlumberger Ind Sa | Device for the selection and delivery of a service against payment. |
FR2706056B1 (en) | 1993-06-04 | 1995-08-11 | Decaux Jean Claude | Payment system for transport network. |
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 |
FR2709582B1 (en) | 1993-09-02 | 1995-09-29 | Gemplus Card Int | Electronic payment method, in particular by means of a smart card. |
US5583759A (en) | 1993-11-22 | 1996-12-10 | Huntington Bancshares, Inc. | Mechanism for expediting the deposit, transport and submission of checks into the payment system |
US5930778A (en) | 1993-11-22 | 1999-07-27 | Huntington Bancshares Incorporated | System for expediting the clearing of financial instruments and coordinating the same with invoice processing at the point of receipt |
CA2137167C (en) * | 1993-12-22 | 1999-09-21 | Tony J. Brice | Data management method and architecture |
US5550734A (en) * | 1993-12-23 | 1996-08-27 | The Pharmacy Fund, Inc. | Computerized healthcare accounts receivable purchasing collections securitization and management system |
WO1995022113A1 (en) | 1994-02-14 | 1995-08-17 | Telepay, Inc. | Automated interactive bill payment system |
FR2717597B1 (en) | 1994-03-16 | 1996-04-12 | Gemplus Card Int | Game machine with statutory mechanical counters and electronic coin operated. |
US5655023A (en) | 1994-05-13 | 1997-08-05 | Pitney Bowes Inc. | Advanced postage payment system employing pre-computed digital tokens and with enhanced security |
US5586036A (en) | 1994-07-05 | 1996-12-17 | Pitney Bowes Inc. | Postage payment system with security for sensitive mailer data and enhanced carrier data functionality |
US5826241A (en) | 1994-09-16 | 1998-10-20 | First Virtual Holdings Incorporated | Computerized system for making payments and authenticating transactions over the internet |
FI100083B (en) | 1994-09-20 | 1997-09-15 | Nokia Mobile Phones Ltd | The terminal |
US5590196A (en) | 1994-10-06 | 1996-12-31 | Connotech Experts Conseils Inc. | Secure payment method using facsimile |
US5715314A (en) | 1994-10-24 | 1998-02-03 | Open Market, Inc. | Network sales system |
US6073104A (en) | 1994-11-09 | 2000-06-06 | Field; Richard G. | System for invoice record management and asset-backed commercial paper program management |
US5479510A (en) | 1994-11-15 | 1995-12-26 | Olsen; Kurt B. | Automated data card payment verification method |
US6230148B1 (en) | 1994-11-28 | 2001-05-08 | Veristar Corporation | Tokenless biometric electric check transaction |
US5704045A (en) | 1995-01-09 | 1997-12-30 | King; Douglas L. | System and method of risk transfer and risk diversification including means to assure with assurance of timely payment and segregation of the interests of capital |
JP3343771B2 (en) | 1995-03-13 | 2002-11-11 | 株式会社東芝 | Electronic payment device and electronic payment determination method |
US5590197A (en) | 1995-04-04 | 1996-12-31 | V-One Corporation | Electronic payment system and method |
US5675650A (en) | 1995-05-02 | 1997-10-07 | Pitney Bowes Inc. | Controlled acceptance mail payment and evidencing system |
US5826247A (en) | 1996-04-09 | 1998-10-20 | Pitney Bowes Inc. | Closed loop transaction based mail accounting and payment system with carrier payment through a third party initiated by mailing information release |
FR2734800B1 (en) | 1995-06-01 | 1997-08-01 | Snef Cote D Azur Sa | PNEUMATIC CONVEYOR FOR SMALL METAL PARTS, ESPECIALLY COINS, FOR CASH TERMINALS |
US5832460A (en) | 1995-06-02 | 1998-11-03 | International Business Machines Corporation | Method and system for bill presentation and payment reconciliation |
US5832089A (en) | 1995-06-07 | 1998-11-03 | Sandia Corporation | Off-line compatible electronic cash method and system |
US5748908A (en) | 1995-06-07 | 1998-05-05 | Yu; Mason K. | Automated, classified expenditure data card recording system |
US5819236A (en) | 1995-06-12 | 1998-10-06 | Carreker-Antinori, Inc. | System and method for providing advance notification of potential presentment returns due to account restrictions |
NL1000741C2 (en) | 1995-07-06 | 1997-01-08 | Nederland Ptt | Method for tracking payment data in an anonymous payment system, as well as a payment system in which the method is applied |
FR2737032B1 (en) | 1995-07-19 | 1997-09-26 | France Telecom | SECURE PAYMENT SYSTEM BY ELECTRONIC CURRENCY TRANSFER THROUGH AN INTERBANKING NETWORK |
US6223168B1 (en) * | 1995-07-25 | 2001-04-24 | Bottomline Technologies, Inc. | Automatic remittance delivery system |
JPH0950465A (en) | 1995-08-04 | 1997-02-18 | Hitachi Ltd | Electronic shopping method, electronic shopping system and document authentication method |
JP3710172B2 (en) | 1995-09-01 | 2005-10-26 | 富士通株式会社 | User terminal and center for software price refund |
US6076075A (en) | 1995-09-25 | 2000-06-13 | Cardis Enterprise International N.V. | Retail unit and a payment unit for serving a customer on a purchase and method for executing the same |
NL1001509C2 (en) | 1995-10-26 | 1997-05-02 | Nederland Ptt | Method for canceling a transaction with an electronic payment method, as well as a payment method for applying the method. |
US5819228A (en) | 1995-10-31 | 1998-10-06 | Utilimed, Inc. | Health care payment system utilizing an intensity adjustment factor applied to provider episodes of care |
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 |
NL1001659C2 (en) | 1995-11-15 | 1997-05-21 | Nederland Ptt | Method for writing down an electronic payment method. |
US5842183A (en) | 1995-11-21 | 1998-11-24 | International Billings Services, Inc. | Dynamically updated payment due date system |
NL1001863C2 (en) | 1995-12-08 | 1997-06-10 | Nederland Ptt | Method for securely writing down an electronic payment method, as well as payment method for implementing the method. |
US6058380A (en) | 1995-12-08 | 2000-05-02 | Mellon Bank, N.A. | System and method for electronically processing invoice information |
US5812945A (en) | 1995-12-22 | 1998-09-22 | Pitney Bowes Inc. | Metered payment cellular telephone communication system |
US5987140A (en) | 1996-04-26 | 1999-11-16 | Verifone, Inc. | System, method and article of manufacture for secure network electronic payment and credit collection |
US5963924A (en) | 1996-04-26 | 1999-10-05 | Verifone, Inc. | System, method and article of manufacture for the use of payment instrument holders and payment instruments in network electronic commerce |
US5808723A (en) | 1996-05-21 | 1998-09-15 | Eastman Kodak Company | Photofinishing system having customized customer order payment feature |
US5983208A (en) | 1996-06-17 | 1999-11-09 | Verifone, Inc. | System, method and article of manufacture for handling transaction results in a gateway payment architecture utilizing a multichannel, extensible, flexible architecture |
US5768132A (en) | 1996-06-17 | 1998-06-16 | Pitney Bowes Inc. | Controlled acceptance mail system securely enabling reuse of digital token initially generated for a mailpiece on a subsequently prepared different mailpiece to authenticate payment of postage |
US6072870A (en) | 1996-06-17 | 2000-06-06 | Verifone Inc. | System, method and article of manufacture for a gateway payment architecture utilizing a multichannel, extensible, flexible architecture |
US5987132A (en) | 1996-06-17 | 1999-11-16 | Verifone, Inc. | System, method and article of manufacture for conditionally accepting a payment method utilizing an extensible, flexible architecture |
USD386882S (en) | 1996-07-25 | 1997-11-25 | Smith Ervin M | Island payment terminal |
US5816174A (en) | 1996-07-25 | 1998-10-06 | Smith; Ervin M. | Island payment terminal mounting system |
JP3387330B2 (en) | 1996-09-12 | 2003-03-17 | 株式会社日立製作所 | Electronic money holding device and electronic money payment method using the same |
USD385304S (en) | 1996-09-16 | 1997-10-21 | Griffin Peter B | Invoice file clip |
US5978840A (en) | 1996-09-26 | 1999-11-02 | Verifone, Inc. | System, method and article of manufacture for a payment gateway system architecture for processing encrypted payment transactions utilizing a multichannel, extensible, flexible architecture |
USD398446S (en) | 1996-10-03 | 1998-09-22 | Hosea Darlene L | Payment booklet holder |
US5991411A (en) | 1996-10-08 | 1999-11-23 | International Business Machines Corporation | Method and means for limiting adverse use of counterfeit credit cards, access badges, electronic accounts or the like |
AU745141B2 (en) | 1996-10-09 | 2002-03-14 | Visa International Service Association | Electronic statement presentment system |
US6070150A (en) | 1996-10-18 | 2000-05-30 | Microsoft Corporation | Electronic bill presentment and payment system |
KR19990076696A (en) | 1996-10-23 | 1999-10-15 | 요트.게.아. 롤페즈 | Mobile communication service payment system |
US7110959B2 (en) * | 1996-11-12 | 2006-09-19 | Hahn-Carlson Dean W | Processing and management of transaction timing characteristics |
US20050165699A1 (en) * | 1996-11-12 | 2005-07-28 | Hahn-Carlson Dean W. | Processing and management of transaction timing characteristics |
JPH10162089A (en) | 1996-12-02 | 1998-06-19 | Oki Electric Ind Co Ltd | Electronic transaction system |
EP0851396A1 (en) | 1996-12-23 | 1998-07-01 | Koninklijke KPN N.V. | System for increasing a value of an electronic payment card |
US5819239A (en) | 1996-12-30 | 1998-10-06 | Pitney Bowes Inc. | Method of verifying proper payment of postage |
US6167378A (en) | 1997-01-21 | 2000-12-26 | Webber, Jr.; Donald Gary | Automated back office transaction method and system |
US6070798A (en) | 1997-02-21 | 2000-06-06 | Nethery; Kee | Purchaser generated transaction recording and negotiable instrument payment system |
US5999625A (en) | 1997-02-27 | 1999-12-07 | International Business Machines Corporation | Method for electronic payment system with issuer control |
US6006205A (en) * | 1997-02-28 | 1999-12-21 | Walker Asset Management Limited Partnership | Credit card billing method and system |
CA2285190A1 (en) | 1997-03-31 | 1998-10-08 | Bellsouth Intellectual Property Corporation | A system and method for generating an invoice to rebill charges to the elements of an organization |
US6061665A (en) | 1997-06-06 | 2000-05-09 | Verifone, Inc. | System, method and article of manufacture for dynamic negotiation of a network payment framework |
US5973619A (en) | 1997-06-10 | 1999-10-26 | Paredes; Alexis | Automated vehicle dispatch and payment honoring system |
US6073125A (en) | 1997-06-26 | 2000-06-06 | Pitney Bowes Inc. | Token key distribution system controlled acceptance mail payment and evidencing system |
IL121192A0 (en) | 1997-06-30 | 1997-11-20 | Ultimus Ltd | Processing system and method for a heterogeneous electronic cash environment |
US5950178A (en) * | 1997-07-29 | 1999-09-07 | Borgato; Sergio | Data processing system and method for facilitating transactions in diamonds |
US5974146A (en) | 1997-07-30 | 1999-10-26 | Huntington Bancshares Incorporated | Real time bank-centric universal payment system |
US6163771A (en) | 1997-08-28 | 2000-12-19 | Walker Digital, Llc | Method and device for generating a single-use financial account number |
US5914472A (en) | 1997-09-23 | 1999-06-22 | At&T Corp | Credit card spending authorization control system |
US5946669A (en) | 1997-09-30 | 1999-08-31 | Lockheed Martin Corporation | Method and apparatus for payment processing using debit-based electronic funds transfer and disbursement processing using addendum-based electronic data interchange |
US5978780A (en) | 1997-11-21 | 1999-11-02 | Craig Michael Watson | Integrated bill consolidation, payment aggregation, and settlement system |
US5943656A (en) | 1997-12-03 | 1999-08-24 | Avista Advantage, Inc. | Methods and systems for computerized bill consolidating, billing and payment authorization, computerized utility bill consolidating, utility billing access and payment and utility provider consolidated billing systems |
US6052674A (en) | 1997-12-23 | 2000-04-18 | Information Retrieval Consultants (Europe, Middle East, Africa ) Limited | Electronic invoicing and collection system and method with charity donations |
US6038547A (en) | 1998-01-07 | 2000-03-14 | Casto; Robin L. | Construction tracking and payment method and system |
US6233565B1 (en) | 1998-02-13 | 2001-05-15 | Saranac Software, Inc. | Methods and apparatus for internet based financial transactions with evidence of payment |
US6081790A (en) | 1998-03-20 | 2000-06-27 | Citibank, N.A. | System and method for secure presentment and payment over open networks |
JP3847560B2 (en) | 1998-05-05 | 2006-11-22 | ザ クリアリング ハウス サーヴィス カンパニー エル.エル.シー. | System and method for one day netting payment settlement |
US6102287A (en) | 1998-05-15 | 2000-08-15 | International Business Machines Corporation | Method and apparatus for providing product survey information in an electronic payment system |
US6073113A (en) | 1998-06-29 | 2000-06-06 | Sun Microsystems, Inc. | Compatibility checking between instruments, operations and protocols in electronic commerce |
US6056322A (en) | 1998-08-03 | 2000-05-02 | Lupi; Louis A. | Combination sample medication payment check and medication prescription device |
US6222914B1 (en) | 1998-09-02 | 2001-04-24 | Mcmullin John L. | System and method for administration of an incentive award system having a delayed award payment using a credit instrument |
US6216115B1 (en) | 1998-09-28 | 2001-04-10 | Benedicto Barrameda | Method for multi-directional consumer purchasing, selling, and transaction management |
US6135261A (en) | 1998-10-23 | 2000-10-24 | Robert E. Noell, Jr. | Payment-receiving enclosure for a vending machine |
US6167385A (en) | 1998-11-30 | 2000-12-26 | The Chase Manhattan Bank | Supply chain financing system and method |
US6772131B1 (en) * | 1999-02-01 | 2004-08-03 | American Management Systems, Inc. | Distributed, object oriented global trade finance system with imbedded imaging and work flow and reference data |
US6227447B1 (en) | 1999-05-10 | 2001-05-08 | First Usa Bank, Na | Cardless payment system |
CA2272723A1 (en) * | 1999-05-25 | 2000-11-25 | Rdm Corporation | Digital signature server |
US6934692B1 (en) * | 1999-07-06 | 2005-08-23 | Dana B. Duncan | On-line interactive system and method for transacting business |
US6944762B1 (en) * | 1999-09-03 | 2005-09-13 | Harbor Payments Corporation | System and method for encrypting data messages |
AU7123300A (en) * | 1999-09-10 | 2001-04-10 | William C. Rodgers | Web-based system to facilitate purchase, pick-up, and delivery of, and escrow and payment for, merchandise |
US7047219B1 (en) * | 1999-10-04 | 2006-05-16 | Trade Finance Systems, Inc. | Trade finance automation system |
US7426492B1 (en) | 1999-11-05 | 2008-09-16 | American Express Travel Related Services Company, Inc. | Systems and methods for facilitating commercial transactions between parties residing at remote locations |
US6847953B2 (en) | 2000-02-04 | 2005-01-25 | Kuo James Shaw-Han | Process and method for secure online transactions with calculated risk and against fraud |
US6883004B2 (en) * | 2000-08-04 | 2005-04-19 | Bottomline Technologies (De), Inc. | Automated invoice receipt and management system |
WO2002015098A2 (en) * | 2000-08-11 | 2002-02-21 | Loy John J | Trade receivable processing method and apparatus |
US20030220858A1 (en) * | 2002-05-24 | 2003-11-27 | Duc Lam | Method and system for collaborative vendor reconciliation |
US20030220863A1 (en) * | 2002-05-24 | 2003-11-27 | Don Holm | System and method for varying electronic settlements between buyers and suppliers with dynamic discount terms |
US7437327B2 (en) * | 2002-05-24 | 2008-10-14 | Jp Morgan Chase Bank | Method and system for buyer centric dispute resolution in electronic payment system |
US7689482B2 (en) * | 2002-05-24 | 2010-03-30 | Jp Morgan Chase Bank, N.A. | System and method for payer (buyer) defined electronic invoice exchange |
US7519560B2 (en) * | 2002-05-24 | 2009-04-14 | Jpmorgan Chase Bank, N.A. | System and method for electronic authorization of batch checks |
US20030220875A1 (en) * | 2002-05-24 | 2003-11-27 | Duc Lam | Method and system for invoice routing and approval in electronic payment system |
US7133844B2 (en) * | 2002-06-04 | 2006-11-07 | Bottomline Technologies (De) Inc. | System and method for producing and verifying secure negotiable instruments |
US7058612B2 (en) * | 2002-06-04 | 2006-06-06 | Bottomline Technologies, (De) Inc. | System and method for producing and verifying secure negotiable instruments |
US7089213B2 (en) * | 2002-06-04 | 2006-08-08 | Bottomline Technologies | System and method for producing and verifying secure negotiable instruments |
US20070271160A1 (en) * | 2002-09-12 | 2007-11-22 | The Pnc Financial Services Group, Inc. | Accounts payable process |
US7236957B2 (en) * | 2004-02-10 | 2007-06-26 | Bottomline Technologies (De) Inc. | Method for remotely authorizing a payment transaction file over an open network |
US20060167792A1 (en) * | 2004-12-29 | 2006-07-27 | Hahn-Carlson Dean W | Multi-supplier transaction and payment programmed processing system and approach |
-
2001
- 2001-10-29 US US10/020,466 patent/US7822679B1/en active Active
-
2002
- 2002-10-25 CA CA002465564A patent/CA2465564A1/en not_active Abandoned
- 2002-10-25 WO PCT/US2002/034362 patent/WO2003038553A2/en not_active Application Discontinuation
- 2002-10-25 AU AU2002340294A patent/AU2002340294C1/en not_active Expired
- 2002-10-25 DE DE20221741U patent/DE20221741U1/en not_active Expired - Lifetime
- 2002-10-25 EP EP02778643A patent/EP1454277A4/en not_active Ceased
-
2009
- 2009-03-11 AU AU2009200961A patent/AU2009200961B2/en not_active Expired
-
2010
- 2010-09-14 US US12/881,831 patent/US20110004548A1/en not_active Abandoned
- 2010-09-15 US US12/882,677 patent/US20110004552A1/en not_active Abandoned
Patent Citations (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4001568A (en) * | 1973-12-29 | 1977-01-04 | Glory Kogyo Kabushiki Kaisha | Monetary receipt and payment managing apparatus |
USD263638S (en) * | 1979-05-14 | 1982-03-30 | American Payment Centers, Inc. | Payment deposit cabinet |
US4325277A (en) * | 1979-05-25 | 1982-04-20 | Laurel Bank Machine Co., Ltd. | Dispenser for making payment of pre-packed paper sheets |
US4370649A (en) * | 1981-05-19 | 1983-01-25 | Fuerle Gerard A | Payment responsive data display network |
US4577061A (en) * | 1982-09-07 | 1986-03-18 | Kurt Katzeff | Arrangement for a pay telephone payment system utilizing a payment card within the telecommunication system |
US4585936A (en) * | 1983-02-10 | 1986-04-29 | Mecelec | Optical process for determining the dimensions of an object in relative movement, and more particularly of a coin in a pre-payment apparatus |
US4822984A (en) * | 1985-12-02 | 1989-04-18 | Patrick Remery | Process for electronic payment using a memory |
USRE34872E (en) * | 1986-03-04 | 1995-03-14 | Lucero; James L. | Drive-through credit card payment device |
US4893237A (en) * | 1986-03-27 | 1990-01-09 | Tokyo Electric Co., Ltd. | Interconnected sales data registration and payment settlement system |
US4796193A (en) * | 1986-07-07 | 1989-01-03 | Pitney Bowes Inc. | Postage payment system where accounting for postage payment occurs at a time subsequent to the printing of the postage and employing a visual marking imprinted on the mailpiece to show that accounting has occurred |
US5003585A (en) * | 1986-07-18 | 1991-03-26 | Louis Richer | System for the payment of telephone calls in a private self-switching unit |
US4799156A (en) * | 1986-10-01 | 1989-01-17 | Strategic Processing Corporation | Interactive market management system |
US4797540A (en) * | 1986-11-06 | 1989-01-10 | Omron Tateisi Electronics Co. | Payment making terminal device |
US4920256A (en) * | 1987-03-02 | 1990-04-24 | Crouzet | Universal electronic payment terminal base including memory card programming voltage booster |
US5193057A (en) * | 1988-01-21 | 1993-03-09 | Beneficial Franchise Company Inc. | Electronic income tax refund early payment system with means for creating of a new deposit account for receipt of an electronically transferred refund from the irs |
US5007084A (en) * | 1988-08-29 | 1991-04-09 | Richard H. Materna | Payment Authorization and Information Device |
US4906826A (en) * | 1988-09-19 | 1990-03-06 | Visa International Service Association | Usage promotion method for payment card transaction system |
US5291304A (en) * | 1989-04-18 | 1994-03-01 | Murata Kikai Kabushiki Kaisha | Facsimile apparatus having invoice sentence preparation function |
US5191193A (en) * | 1989-10-13 | 1993-03-02 | Gemplus Card International | System of payment or information transfer by money card with electronic memory |
US5192855A (en) * | 1989-12-06 | 1993-03-09 | Modul-Elektronik Ab | Improvements in cash payment machines enabling acceptance of credit card payment |
US6202054B1 (en) * | 1989-12-08 | 2001-03-13 | Online Resources & Communications Corp. | Method and system for remote delivery of retail banking services |
US5620182A (en) * | 1990-08-22 | 1997-04-15 | Rossides; Michael T. | Expected value payment method and system for reducing the expected per unit costs of paying and/or receiving a given ammount of a commodity |
US5387784A (en) * | 1990-10-30 | 1995-02-07 | Societe D'applications Generales D'electricite Et De Mecanique Sagem | Portable payment terminals and network for such terminals |
US5305383A (en) * | 1991-04-03 | 1994-04-19 | France Telecom, Telediffusion De France S.A. | Method of electronic payment by chip card by means of numbered tokens allowing the detection of fraud |
US5873072A (en) * | 1991-07-25 | 1999-02-16 | Checkfree Corporation | System and method for electronically providing customer services including payment of bills, financial analysis and loans |
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 |
US5285883A (en) * | 1992-03-11 | 1994-02-15 | Atoll Technology | Automatic payment device and method for recognizing coins |
US5297030A (en) * | 1992-04-08 | 1994-03-22 | Ncr Corporation | Method using bill and coin images on a touch screen for processing payment for merchandise items |
US5491325A (en) * | 1992-08-25 | 1996-02-13 | Huang; Dorge O. | Method and system for payment and payment verification |
US6041315A (en) * | 1992-10-15 | 2000-03-21 | Autoscribe Corporation | Automated payment system and method |
US5504677A (en) * | 1992-10-15 | 1996-04-02 | Pollin; Robert E. | Automated payment system |
US5727249A (en) * | 1992-10-15 | 1998-03-10 | Pollin; Robert E. | Automated payment system and method |
US5297674A (en) * | 1992-11-04 | 1994-03-29 | Fellowes Manufacturing Company | Molded bill payment center container with removable trays |
US5289923A (en) * | 1992-11-23 | 1994-03-01 | Atlantic Richfield Company | Stacker for electronic payment system key pad and printer |
US5284253A (en) * | 1992-11-25 | 1994-02-08 | Atlantic Richfield Company | Stacker for electronic payment system key pads |
US5492212A (en) * | 1993-06-02 | 1996-02-20 | Schlumberger Industries | Device for sorting and storing objects inserted by way of payment in a dispenser |
US5706925A (en) * | 1993-10-18 | 1998-01-13 | Gemplus Card International | Games machine with electronic payment mechanism |
US6205437B1 (en) * | 1993-12-16 | 2001-03-20 | Open Market, Inc. | Open network payment system for providing for real-time authorization of payment and purchase transactions |
US6049785A (en) * | 1993-12-16 | 2000-04-11 | Open Market, Inc. | Open network payment system for providing for authentication of payment orders based on a confirmation electronic mail message |
US5857152A (en) * | 1994-02-01 | 1999-01-05 | Mondex International Limited | Electronic toll payment |
US5403025A (en) * | 1994-03-03 | 1995-04-04 | Shanley; Thomas M. | Partially preprinted, service invoice record forms, having piggyback vinyl status |
USRE37067E1 (en) * | 1994-08-31 | 2001-02-27 | Koninklijke Ptt Nederland N.V. | Chip card based payment system having an on-card flag for specifying proper completion of a prior card balance replenishment session |
US5717989A (en) * | 1994-10-13 | 1998-02-10 | Full Service Trade System Ltd. | Full service trade system |
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 |
US5890140A (en) * | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
US5717868A (en) * | 1995-03-07 | 1998-02-10 | Huntington Bancshares Inc. | Electronic payment interchange concentrator |
US5614892A (en) * | 1995-04-24 | 1997-03-25 | Pom, Inc. | Payment slot communicating apparatus for vendng prices |
US5739511A (en) * | 1995-05-11 | 1998-04-14 | Koninklijke Ptt Nederland N.V. | Method for effecting an electronic payment transaction having a variable number of payment units, as well as payment means and system for applying the method |
US5880454A (en) * | 1995-05-11 | 1999-03-09 | Schlumberger Industries | Electronic payment card with an interchangeable module |
US6016955A (en) * | 1995-05-12 | 2000-01-25 | Koninklijke Kpn N.V. | Electronic payment method and system having several calculation units and electronic payment devices |
US6014646A (en) * | 1995-06-08 | 2000-01-11 | France Telecom | Process for making a payment using an account manager |
US5893080A (en) * | 1995-07-25 | 1999-04-06 | Bottomline Technologies, Inc. | Disbursement system and method |
US5893907A (en) * | 1995-10-26 | 1999-04-13 | Ukuda; Shuko | Apparatus and system for managing a card number |
USD378219S (en) * | 1995-11-21 | 1997-02-25 | Marshlack Dane G | Invoice holder |
US6038647A (en) * | 1995-12-06 | 2000-03-14 | Fujitsu Limited | Cache memory device and method for providing concurrent independent multiple accesses to different subsets within the device |
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 |
US5890137A (en) * | 1995-12-15 | 1999-03-30 | Kabushiki Kaisha N.K. Kikaku | On-line shopping system and the method of payment settlement |
US5740247A (en) * | 1995-12-22 | 1998-04-14 | Pitney Bowes Inc. | Authorized cellular telephone communication payment refill system |
US5893902A (en) * | 1996-02-15 | 1999-04-13 | Intelidata Technologies Corp. | Voice recognition bill payment system with speaker verification and confirmation |
US6016484A (en) * | 1996-04-26 | 2000-01-18 | Verifone, Inc. | System, method and article of manufacture for network electronic payment instrument and certification of payment and credit collection utilizing a payment |
US5715298A (en) * | 1996-05-16 | 1998-02-03 | Telepay | Automated interactive bill payment system using debit cards |
US6205433B1 (en) * | 1996-06-14 | 2001-03-20 | Cybercash, Inc. | System and method for multi-currency transactions |
US6178409B1 (en) * | 1996-06-17 | 2001-01-23 | Verifone, Inc. | System, method and article of manufacture for multiple-entry point virtual point of sale architecture |
US5884288A (en) * | 1996-07-01 | 1999-03-16 | Sun Microsystems, Inc. | Method and system for electronic bill payment |
US6047269A (en) * | 1996-07-19 | 2000-04-04 | Peter Biffar | Self-contained payment system with circulating digital vouchers |
US6205435B1 (en) * | 1996-07-19 | 2001-03-20 | Peter Biffar | Self-contained payment system with circulating digital vouchers |
USD403667S (en) * | 1996-09-12 | 1999-01-05 | Oki Electric Industry Co., Ltd. | Pocket-sized electronic payment and financial transaction terminal including IC card reader |
US6206285B1 (en) * | 1996-10-01 | 2001-03-27 | Siemens Nixdorf Informationssysteme Aktiengesellschaft | Peripheral assembly kit for the workstation of a goods invoicing system |
US6029150A (en) * | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
US6021943A (en) * | 1996-10-09 | 2000-02-08 | Chastain; Robert H. | Process for executing payment transactions |
US20040010463A1 (en) * | 1996-11-12 | 2004-01-15 | Hahn-Carlson Dean W. | Automated transaction processing system and approach |
US20050033671A1 (en) * | 1996-11-12 | 2005-02-10 | U.S. Bancorp | Automated transaction processing system and approach |
US6704612B1 (en) * | 1996-11-12 | 2004-03-09 | U.S. Bancorp | Transaction validation system for auditing and method |
US20070055582A1 (en) * | 1996-11-12 | 2007-03-08 | Hahn-Carlson Dean W | Transaction processing with core and distributor processor implementations |
US5870456A (en) * | 1997-01-22 | 1999-02-09 | Telepay, Inc. | Automated interactive bill payment system using debit cards |
US6202052B1 (en) * | 1997-05-08 | 2001-03-13 | Simplification, Llc | Fully-automated system for tax reporting, payment and refund |
US6193152B1 (en) * | 1997-05-09 | 2001-02-27 | Receiptcity.Com, Inc. | Modular signature and data-capture system and point of transaction payment and reward system |
US6047267A (en) * | 1997-05-14 | 2000-04-04 | Portal Software, Inc. | Method and apparatus for tracking multiple payment resources and charging transactions to payment resources in on line transaction processing system |
US6012048A (en) * | 1997-05-30 | 2000-01-04 | Capital Security Systems, Inc. | Automated banking system for dispensing money orders, wire transfer and bill payment |
US6049786A (en) * | 1997-07-22 | 2000-04-11 | Unisys Corporation | Electronic bill presentment and payment system which deters cheating by employing hashes and digital signatures |
US6044362A (en) * | 1997-09-08 | 2000-03-28 | Neely; R. Alan | Electronic invoicing and payment system |
US5883810A (en) * | 1997-09-24 | 1999-03-16 | Microsoft Corporation | Electronic online commerce card with transactionproxy number for online transactions |
USD406574S (en) * | 1997-10-06 | 1999-03-09 | Verifone, Inc. | Payment instrument |
US6038548A (en) * | 1997-11-26 | 2000-03-14 | International Business Machines Corporation | System and method for conducting electronic commerce in a computer network using a cashier desk payment framework |
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 |
US6199107B1 (en) * | 1998-07-22 | 2001-03-06 | Microsoft Corporation | Partial file caching and read range resume system and method |
US6181361B1 (en) * | 1998-07-22 | 2001-01-30 | Dassault Automatismes Et Telecommunications | Device for thermal printing of a rolled paper strip, in particular for a plug-in or cordless portable payment terminal |
US6012740A (en) * | 1998-08-03 | 2000-01-11 | Lupi; L. Anthony | Combination sample medication payment check and medication prescription device |
US6169974B1 (en) * | 1998-10-08 | 2001-01-02 | Paymentech, Inc. | Method for closed loop processing of transactions utilizing bank card association |
US6185545B1 (en) * | 1998-11-17 | 2001-02-06 | Prenet Corporation | Electronic payment system utilizing intermediary account |
US6173269B1 (en) * | 1998-12-16 | 2001-01-09 | Zowi.Com, Inc | Method and apparatus for executing electronic commercial transactions with minors |
US6697702B1 (en) * | 1999-03-12 | 2004-02-24 | U.S. Bancorp | Shipment transaction system and an arrangement thereof |
WO2000058876A1 (en) * | 1999-03-26 | 2000-10-05 | Rdm Corporation | Electronic invoice payment system |
WO2000079451A1 (en) * | 1999-06-17 | 2000-12-28 | Mobius Management Systems, Inc. | Electronic statement, bill presentment and payment system and method |
US7340433B1 (en) * | 1999-07-30 | 2008-03-04 | Orbian Management Limited | System and method of transaction settlement using trade credit |
US7319986B2 (en) * | 1999-09-28 | 2008-01-15 | Bank Of America Corporation | Dynamic payment cards and related management systems and associated methods |
US6856970B1 (en) * | 2000-09-26 | 2005-02-15 | Bottomline Technologies | Electronic financial transaction system |
US7336698B2 (en) * | 2002-04-24 | 2008-02-26 | Nokia Corporation | Interference cancellation in receiver of radio system |
US20060015455A1 (en) * | 2004-06-09 | 2006-01-19 | Hahn-Carlson Dean W | Order-resource fulfillment and management system and approach |
US20060015454A1 (en) * | 2004-06-09 | 2006-01-19 | Hahn-Carlson Dean W | Distributor-based transaction processing arrangement and approach |
Also Published As
Publication number | Publication date |
---|---|
CA2465564A1 (en) | 2003-05-08 |
DE20221741U1 (en) | 2007-06-14 |
AU2002340294B2 (en) | 2008-12-11 |
WO2003038553A2 (en) | 2003-05-08 |
US7822679B1 (en) | 2010-10-26 |
AU2002340294C1 (en) | 2009-05-28 |
EP1454277A2 (en) | 2004-09-08 |
WO2003038553A3 (en) | 2003-10-02 |
AU2009200961A1 (en) | 2009-04-02 |
EP1454277A4 (en) | 2004-12-15 |
AU2009200961B2 (en) | 2012-11-01 |
US20110004548A1 (en) | 2011-01-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU2009200961B2 (en) | Method and system for conducting a commercial transaction between a buyer and a seller | |
US8571978B2 (en) | Method and system for providing assurance and financing services | |
CA2483348C (en) | System and method for varying electronic settlements between buyers and suppliers with dynamic discount terms | |
AU2002340294A1 (en) | Method and system for conducting a commercial transaction between a buyer and a seller | |
US20080270304A1 (en) | Funds transfer system and method | |
US20040111370A1 (en) | Single source money management system | |
US20160328705A1 (en) | Mediated conversion of cryptographic currency and other funding sources to gold | |
US20070038523A1 (en) | System and method for transactional hedging | |
KR20020029857A (en) | Method and system for providing a store with credit and managing the credit on the basis of credit card sales of the store | |
EP1782254A2 (en) | Method and system for providing assurance and financing services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |