US8566231B2 - Method and system for providing buyer bank payable discounting aggregation services - Google Patents

Method and system for providing buyer bank payable discounting aggregation services Download PDF

Info

Publication number
US8566231B2
US8566231B2 US11/131,679 US13167905A US8566231B2 US 8566231 B2 US8566231 B2 US 8566231B2 US 13167905 A US13167905 A US 13167905A US 8566231 B2 US8566231 B2 US 8566231B2
Authority
US
United States
Prior art keywords
buyer
seller
payment
transaction
bank
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.)
Active, expires
Application number
US11/131,679
Other versions
US20050283432A1 (en
Inventor
William Reid
Craig Swackhammer
Kerry Lynch
Johnson Lau
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Visa International Service Association
Original Assignee
Visa International Service Association
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Visa International Service Association filed Critical Visa International Service Association
Priority to US11/131,679 priority Critical patent/US8566231B2/en
Assigned to VISA INTERNATIONAL SERVICE ASSOCATION reassignment VISA INTERNATIONAL SERVICE ASSOCATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LYNCH, KERRY, REID, WILLIAM, SWACKHAMMER, CRAIG, LAU, JOHNSON
Priority to PCT/US2005/021049 priority patent/WO2006009710A2/en
Priority to KR1020077001223A priority patent/KR20070050038A/en
Priority to CA002571331A priority patent/CA2571331A1/en
Priority to EP05759359A priority patent/EP1782254A4/en
Publication of US20050283432A1 publication Critical patent/US20050283432A1/en
Application granted granted Critical
Publication of US8566231B2 publication Critical patent/US8566231B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/02Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/08Insurance

Definitions

  • the present invention generally relates to assurance and financing services, and more specifically, to a method and system for providing assurance and financing services to buyers and sellers involved in commercial 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.
  • 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.
  • the transaction processing system further includes a number of additional features including, for example, buyer payment assurance, buyer bank payment assurance, buyer bank payable discounting, buyer bank payable discount aggregation, seller/receivable financing and seller bank receivable discount aggregation.
  • 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.
  • this enables the buyer 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 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. These ranges can be established by the parties involved.
  • 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.
  • 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.
  • the transaction processing system 10 further includes a number of additional features including, for example, buyer payment assurance, buyer bank payment assurance, buyer bank payable discounting, buyer bank payable discount aggregation, seller/receivable financing and seller bank receivable discount aggregation, each of which will be further described below.
  • the transaction processing system 10 also allows interactions and participation by other entities including, for example, a buyer bank and a seller bank.
  • the transaction processing system 10 provides buyer payment assurance in that a buyer 12 has the ability to provide unconditional, irrevocable assurance (guarantee) that a payment will be made on a specified date with certainty.
  • the transaction processing system 10 provides the opportunity to a buyer 12 to approve a payment instruction. During this approval process, the buyer 12 has the option to specify that s/he desires to assure payment.
  • Terms and conditions relating to payment assurance are pre-negotiated and stored in the transaction processing system 10 .
  • a buyer 12 may agree to assure payment using a funding source, such as, a checking account maintained at a buyer bank.
  • the buyer bank and the issuer 16 may be the same entity maintaining both a checking account and a credit card account for the buyer 12 .
  • Information relating to the funding source can be provided and maintained in the transaction processing system 10 .
  • the buyer 12 may also specify a date in connection with the payment assurance indicating that payment will be made on or before the specified date.
  • the transaction processing system 10 informs the buyer 12 of settlement timeframes. For example, the buyer 12 can be informed that payments that are settled in U.S. dollars will post to a seller bank clearing account within one (1) business day of the payment due date and non-U.S. dollar transactions will post to a seller bank clearing account within two (2) business days of the payment due date.
  • the transaction processing system 10 Upon the buyer 12 indicating that a transaction is to be buyer-assured, the transaction processing system 10 “locks down” that particular transaction and its corresponding payment instruction, i.e., information relating to the transaction and the corresponding payment instruction is protected against any subsequent modifications.
  • optional notification can be provided by the transaction processing system 10 to the buyer 12 , the seller 14 , the buyer bank and the seller bank regarding the buyer-assured status of the transaction. Should it be subsequently decided that the transaction is to be reversed, the reversal process is performed outside of the transaction processing system 10 .
  • the transaction processing system 10 further allows transactions with buyer-assured status to be identified.
  • Information relating to such transactions can then be provided to the seller 14 and/or the seller bank for reporting purposes.
  • Such information can then be used by the seller bank to provide financing services.
  • the seller bank is able to flag transactions that it has provided factoring for. This enables the seller bank to recognize which transactions are financed so that credit for these transactions will not be passed onto the seller. Use of this information will be further described below.
  • the transaction processing system 10 enables a buyer 12 to request and/or obtain buyer bank assurance from a buyer bank.
  • Buyer bank assurance means that the buyer bank has agreed to guarantee payment for the transaction.
  • the buyer 12 is able to issue a request for buyer bank assurance.
  • Terms and conditions relating to the buyer bank assurance are pre-negotiated between the buyer 12 and the buyer bank. In one embodiment, such terms and conditions are stored in and used by the transaction processing system 10 to process the request.
  • the request is forwarded by the transaction processing system 10 to the buyer bank for processing. The decision made by the buyer bank is then relayed to the transaction processing system 10 .
  • the transaction and its corresponding payment instruction are locked down against subsequent modification and assigned a bank-assured status.
  • Optional notification may also be provided to the buyer 12 , the seller 14 , the buyer bank and the seller bank.
  • the transaction and its corresponding payment instruction are assigned a bank-assurance-rejected status and the transaction is put on hold.
  • Optional notification may also be provided to the buyer 12 , the seller 14 , the buyer bank and the seller bank.
  • information relating to transactions that have a bank-assured status and for which payments are payable to the seller 14 can be provided by the transaction processing system 10 to the seller bank. Such information can then be used by the seller bank to provide financing services as will be further described below. This enables the seller bank to recognize which transactions are financed and guaranteed by the buyer bank so that credit for these transactions will not be passed to the seller.
  • the transaction processing system 10 provides the ability to allow a buyer bank to offer and handle advance payment to a seller 14 at a discount; this is alternatively called “buyer bank payable discounting” (“BBPD”).
  • BBPD buyer bank payable discounting
  • This capability is designed to allow the buyer bank to offer and provide payable discounting to the seller for those future payments that the buyer bank has provided buyer bank payment assurance for.
  • the buyer bank since the buyer bank has already guaranteed payment for certain payments payable to the seller 14 as described above, the buyer bank may wish to make such payments to the seller 14 at a discount in advance of the payment due dates. This allows the seller 14 to receive any owed account receivables at an earlier time prior to their due dates.
  • the transaction processing system 10 provides a graphical user interface (GUI) to allow the seller 14 to display and review all its transactions that qualify for BBPD from the buyer bank.
  • Qualified transactions include, for example, transactions have been granted a bank-assured status by the buyer bank.
  • the buyer bank may also indicate whether the transaction qualifies for BBPD.
  • the buyer bank may disqualify a transaction for BBPD even though the bank-assured status is given.
  • the seller 14 can then select one or more qualified transactions that it would like to request for BBPD from the buyer bank.
  • Requests pertaining to selected transactions are then forwarded by the transaction processing system 10 to the buyer bank.
  • a status of the “BBPD Requested” may be assigned to each selected transaction.
  • the transaction processing system 10 allows the buyer bank to identify transactions that qualify for BBPD and forward information relating to any identified transactions to the seller 14 for consideration.
  • the seller 14 can then use the transaction processing system 10 to request BBPD for selected transactions.
  • the transaction processing system 10 may also forward the selected transactions to the buyer bank.
  • the buyer bank may interact with the transaction processing system 10 to review and approve or reject the requests.
  • the BBPD approval is based on at least two (2) levels according to the value of payment associated with the transaction.
  • the buyer bank After approving a transaction, the buyer bank then uses the GUI to provide additional information, such as, BBPD or lending terms to the transaction processing system 10 .
  • additional information such as, BBPD or lending terms to the transaction processing system 10 .
  • These terms include, for example, lender's name, discount rate, start date, end date, total duration, total discount amount, handling fee, net process amount (i.e., original payment amount minus discount rate minus handling fee).
  • the transaction processing system 10 After the transaction has been approved by the buyer bank, the transaction processing system 10 notifies the seller 14 of the approval. A status of “BBPD Approved” may then be assigned to the approved transaction. The seller 14 can then use the transaction processing system 10 to review the approved transaction and the associated BBPD terms. The seller 14 can then either accept or decline the approved transaction. If the approved transaction is accepted by the seller 14 , the transaction processing system 10 displays a formal agreement for final approval.
  • the formal agreement includes various types of information including, for example, the BBPD terms for the approved transaction and any other appropriate legal verbiage. In one implementation, some or all of the information contained in the formal agreement is specific to the buyer bank.
  • the transaction processing system 10 provides the ability for the buyer bank to provide and amend its information in the formal agreement.
  • the transaction processing system 10 notifies the buyer bank and updates all records relating to the approved transaction accordingly. For example, a status of “BBPD Buyer Bank Financed/Seller Accepted” is assigned to the approved transaction. The approved transaction and associated information is then forwarded to the buyer bank for additional processing.
  • BBPD Rejected a status of “BBPD Rejected” may be assigned to the rejected transaction.
  • a transaction may be assigned one of a number of statuses.
  • the transaction processing system 10 provides the ability to allow different parties, e.g., the seller 14 and the buyer bank, to sort transactions based on status.
  • a seller 14 may be working with a number of buyer banks; in another instance, a buyer bank may be working with a number of sellers 14 .
  • the transaction processing system 10 provides the ability to monitor future payables to individual sellers. This enables buyer banks to develop tranches to be used for lines of credit to sellers 14 .
  • a tranche is an aggregation of payables which represents a line of credit that can be offered to a seller 14 .
  • the payables in a tranche are several related securities but need not be so. Tranches usually have different, risk, reward and/or maturity characteristics. This is alternatively called “buyer bank payable discounting aggregation” (“BBPDA”).
  • the transaction processing system 10 keeps track of information relating to payables for transactions based on the buyer 12 , the seller 14 and the buyer bank.
  • payables for transactions can be identified as “secured” or “unsecured” by the transaction processing system 10 .
  • a payable or payment is secured if it is bank-assured (e.g., a buyer bank has guaranteed payment) or otherwise secured by other assets.
  • the transaction processing system 10 allows the buyer bank to develop tranches using the available payable information.
  • tranches can be identified based on a mix of secured/unsecured payables, such as, a 30-day tranche having 60% secured payables and 40% unsecured payables.
  • Criteria for a tranche can be specified to the transaction processing system 10 by the buyer bank via, for example, a graphical user interface.
  • the buyer bank can specify that a tranche needs to have $1 million due between fifteen (15) and thirty (30) days with at least 70% of payables secured.
  • the transaction processing system 10 monitors the payable information and builds the desired tranche. When sufficient payables are identified that satisfy the foregoing criteria, the transaction processing system 10 builds the corresponding tranche. All identified payables are then associated with the corresponding tranche. It should be noted that once a payable is used to build a first tranche, it cannot be used in another tranche as long as that payable is associated with that first tranche. However, a payable can be made to associate with another tranche. For example, if a payable no longer qualifies for association with the first tranche, it can then be associated with another tranche.
  • the buyer bank is notified by the transaction processing system 10 that the desired tranche is available.
  • the buyer bank can then offer the tranche to the seller 14 as a line of credit.
  • the line of credit may be subject to certain terms and conditions set by the buyer bank. For example, the buyer bank may discount one or more future payables in the tranche.
  • the transaction processing system 10 can relay the tranche offer and the associated terms and conditions to the seller 14 .
  • a tranche corresponds to only one buyer bank and payables associated therewith belong to only one seller 14 .
  • the transaction processing system 10 allows a buyer bank to build a tranche using its payables that belong to a particular seller 14 .
  • the transaction processing system 10 allows a seller 14 to request BBPDA.
  • the request may include information, such as, identification of one or more buyer banks and terms and conditions desired by the seller 14 .
  • the transaction processing system 10 identifies payables that are owed to the seller 14 and informs one or more buyer banks that have outstanding payables owed to the seller 14 of the issuance of the BBPDA request by the seller 14 .
  • the one or more buyer banks may then use the transaction processing system 10 to create an appropriate tranche and respond to the seller 14 . If a particular buyer bank is specified, then the transaction processing system 10 accordingly contacts the specified buyer bank.
  • the transaction processing system 10 monitors and manages the activities relating to the tranche, for example, the seller 14 drawing against the tranche.
  • the transaction processing system 10 also provides the ability for the seller 14 to push a credit back to the buyer bank for any funds due the buyer bank (e.g., balance of line of credit and/or additional interest).
  • the transaction processing system 10 monitors payables in the tranche that have been paid by a buyer 12 .
  • the transaction processing system 10 notifies the buyer bank when a payment for payable associated with the tranche is made by the buyer 12 .
  • the buyer bank uses the transaction processing system 10 to send a message to the seller 14 letting the seller 14 know how to close the corresponding transaction on its system.
  • the transaction processing system 10 provides the ability for a seller bank to provide financing to a seller 14 for a given payment. This is similar to BBPD described above.
  • the transaction processing system 10 allows the seller bank to monitor receivables that the seller bank is going to receive on behalf of the seller 14 . As a result, the seller bank is able to use the transaction processing system 10 to create an advance loan against a future payment/receivable.
  • the transaction processing system 10 allows the seller bank to proactively search for transactions that the seller may wish to receive financing.
  • the transaction processing system 10 notifies the seller bank when a transaction is assigned a buyer-assured and/or bank-assured status.
  • the transaction processing system 10 may provide functionality to allow the seller bank to search for qualified transactions using different criteria. Such criteria include, for example, specific sellers, sellers that are willing to consider financing, and transaction status, payment total, payment date, etc.
  • the transaction processing system 10 allows the seller 14 to identify and select transactions that it wishes to obtain financing. Information relating to the selected transactions is then forwarded to the seller bank. The seller bank then determines which of the transactions selected by the seller 14 are to be offered financing.
  • the transaction processing system 10 Upon the seller bank identifying the qualified transactions, the transaction processing system 10 assigns a status of “Seller Financing Offered” to these transactions. Optionally, the transaction processing system 10 allows the seller bank to provide financing terms and conditions associated with these transactions. Information relating to these transactions and corresponding financing terms and conditions are then forwarded to the seller 14 for review and selection.
  • the seller 14 can then accept or reject each of the offered transactions.
  • the transaction processing system 10 accordingly assigns the appropriate status to each transaction, such as, “Seller Financing Accepted” or “Seller Financing Rejected”.
  • the transaction processing system 10 then collects the relevant information and forwards such information to the seller bank for further processing.
  • the transaction processing system 10 may display a formal agreement for approval by the seller 14 .
  • the formal agreement includes various types of information, such as, terms and conditions and other legal verbiage associated with the financing offer.
  • the transaction processing system 10 provides the ability to monitor future receivables to individual sellers. This is similar to BBPDA described above. This enables seller banks to develop tranches to be used for lines of credit to sellers 14 .
  • a tranche is an aggregation of receivables which represents a line of credit that can be offered to a seller 14 .
  • the receivables in a tranche are several related securities but need not be so. Tranches usually have different, risk, reward and/or maturity characteristics. This is alternatively called “seller bank receivable discounting aggregation” (“SBRDA”).
  • the transaction processing system 10 keeps track of information relating to receivables for transactions based on the buyer 12 , the seller 14 and the seller bank.
  • receivables for transactions can be identified as “secured” or “unsecured” by the transaction processing system 10 .
  • a receivable is secured if it is bank-assured (e.g., a buyer bank has guaranteed payment) or otherwise secured by other assets.
  • the transaction processing system 10 allows the seller bank to develop tranches using the available receivable information.
  • tranches can be identified based on a mix of secured/unsecured receivables, such as, a 30-day tranche having 60% secured receivables and 40% unsecured receivables.
  • Criteria for a tranche can be specified to the transaction processing system 10 by the seller bank.
  • the seller bank can specify that a tranche needs to have $1 million due between fifteen (15) and thirty (30) days with at least 70% of receivables secured.
  • the transaction processing system 10 monitors the receivable information and builds the desired tranche. When sufficient receivables are identified that satisfy the foregoing criteria, the transaction processing system 10 builds the corresponding tranche. All identified receivables are then associated with the corresponding tranche. It should be noted that once a receivable is used to build a first tranche, it cannot be used in another tranche as long as that receivable is associated with that first tranche. However, a receivable can be made to associate with another tranche. For example, if a receivable no longer qualifies for association with the first tranche, it can then be associated with another tranche.
  • the seller bank is notified by the transaction processing system 10 that the desired tranche is available.
  • the seller bank can then offer the tranche to the seller 14 as a line of credit.
  • the line of credit may be subject to certain terms and conditions set by the seller bank. For example, the seller bank may discount one or more future receivables in the tranche.
  • the transaction processing system 10 can relay the tranche offer and the associated terms and conditions to the seller 14 .
  • a tranche corresponds to only one seller bank and receivables associated therewith belong to only one seller 14 .
  • the transaction processing system 10 allows a seller bank to build a tranche using its receivables that belong to a particular seller 14 .
  • the transaction processing system 10 allows a seller 14 to request SBRDA.
  • the request may include information, such as, identification of one or more seller banks and terms and conditions desired by the seller 14 .
  • the transaction processing system 10 identifies receivables that are owed to the seller 14 and informs one or more seller banks that have outstanding receivables owed to the seller 14 of the issuance of the SBRDA request by the seller 14 .
  • the one or more seller banks may then use the transaction processing system 10 to create an appropriate tranche and respond to the seller 14 . If a particular seller bank is specified, then the transaction processing system 10 accordingly contacts the specified seller bank.
  • the transaction processing system 10 monitors and manages the activities relating to the tranche, for example, the seller 14 drawing against the tranche.
  • the transaction processing system 10 also provides the ability for the seller 14 to push a credit back to the seller bank for any funds due the seller bank (e.g., balance of line of credit and/or additional interest).
  • the transaction processing system 10 monitors receivables in the tranche that have been received from a buyer 12 .
  • the transaction processing system 10 notifies the seller bank when a payment for receivable associated with the tranche is made by the buyer 12 .
  • the seller bank uses the transaction processing system 10 to send a message to the seller 14 letting the seller 14 know how to close the corresponding transaction on its system.
  • the transaction processing system 10 further includes reporting mechanisms which generate reports for various parties for a number of purposes. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate how to generate various types of reports using the present invention.

Abstract

A system for conducting commercial transactions between buyers and sellers is disclosed. The system includes a transaction processing system for facilitating payment for transactions between buyers and the sellers. In addition to the buyer and the seller, the transaction processing system also interacts with issuers and acquirers. The transaction processing system monitors and manages payment information relating to transactions conducted between buyers and sellers. Using such information, the transaction processing system further offers a number of additional financing services including, for example, buyer payment assurance, buyer bank payment assurance, buyer bank payable discounting, buyer bank payable discount aggregation, seller/receivable financing and seller bank receivable discount aggregation.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application claiming benefit under 35 U.S.C. 119(e) of U.S. Provisional Patent Application No. 60/581,021 filed Jun. 17, 2004 entitled METHOD AND SYSTEM FOR PROVIDING ASSURANCE AND FINANCING SERVICES which is hereby incorporated by reference, as if set forth in full in this document, for all purposes.
BACKGROUND OF THE INVENTION
The present invention generally relates to assurance and financing services, and more specifically, to a method and system for providing assurance and financing services to buyers and sellers involved in commercial transactions.
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 transsection. 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.
SUMMARY OF THE INVENTION
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.
In one exemplary embodiment, the transaction processing system further includes a number of additional features including, for example, buyer payment assurance, buyer bank payment assurance, buyer bank payable discounting, buyer bank payable discount aggregation, seller/receivable financing and seller bank receivable discount aggregation.
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.
BRIEF DESCRIPTION OF THE DRAWINGS
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.
DETAILED DESCRIPTION OF THE INVENTION
The present invention in the form of one or more exemplary embodiments will now be described. Referring to FIG. 1, there is shown the process interaction of an exemplary embodiment of the present invention. According to this exemplary embodiment, 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.
Similarly, 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. For example, 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.
Similarly, 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. Furthermore, 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.
Generally, 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.
Furthermore, 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. As 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. Upon receiving the purchase order, the seller 14 then ships the ordered goods or provides a service to the buyer 12.
Referring now to FIG. 1, after receiving the purchase order, 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. In an exemplary embodiment, 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.
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.
After the payment instruction is created, 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. Alternatively, the approval can be supplied by a third party system on behalf of the buyer 12. Upon approval of the payment instruction by the buyer 12, the transaction 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 the buyer 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 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. Furthermore, 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.
Using 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.
Once the authorization request is approved by the issuer 14, an authorization response is sent by the issuer 14 to 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).
After the settlement file is received by the acquirer 18, 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.
As shown in FIG. 1, in an exemplary embodiment, 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. As previously mentioned, an example of the data transport and processing network 20 is VisaNet.
Referring to FIG. 2, there is shown an exemplary embodiment of the transaction processing system 10. According to this exemplary embodiment, 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. 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. 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.
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 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.
In any event, the invoice pre-processor 22 generates a standardized invoice file which is then forwarded to the payment manager 24. In an exemplary implementation, 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. 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 the buyer 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 the payment manager 24 may contain default sets of terms and conditions for various different buyers 12, sellers 14, issuers 16 and acquirers 18.
After the payment instruction is created, 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. In any event, upon approval of the payment instruction by 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. Finally, 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.
With respect to the buyer 12, 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.
With respect to the seller 14, the payment manager 24 allows the seller 14 to create invoices and view the status of relevant invoices and payments.
With respect to the acquirer 18, the payment manager 24 allows the acquirer 18 to create accounts for sellers 14 and their respective users.
With respect to the issuer 16, 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.
As mentioned above, on the scheduled day of payment, 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. 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. For example, 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. As shown in FIG. 3, for example, Transaction Fee Term #3 applies to every payment transaction for Issuer #9012. For Issuer #1234, Transaction Fee Term #1 only applies if a payment transaction is made between Buyer #95 and Seller #22 using account #121212. For Issuer #5678, since no account is specified, 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. 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, 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. At 40, the issuer pricing engine 26 receives the payment instruction corresponding to the payment transaction to be processed from the payment manager 24. At 42, 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. 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 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.
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 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.
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 the transaction 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 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.
In one exemplary embodiment, the transaction processing system 10 further includes a number of additional features including, for example, buyer payment assurance, buyer bank payment assurance, buyer bank payable discounting, buyer bank payable discount aggregation, seller/receivable financing and seller bank receivable discount aggregation, each of which will be further described below. In connection with some of these additional features, the transaction processing system 10 also allows interactions and participation by other entities including, for example, a buyer bank and a seller bank.
In one exemplary aspect, the transaction processing system 10 provides buyer payment assurance in that a buyer 12 has the ability to provide unconditional, irrevocable assurance (guarantee) that a payment will be made on a specified date with certainty. As described above, the transaction processing system 10 provides the opportunity to a buyer 12 to approve a payment instruction. During this approval process, the buyer 12 has the option to specify that s/he desires to assure payment. Terms and conditions relating to payment assurance are pre-negotiated and stored in the transaction processing system 10. For example, a buyer 12 may agree to assure payment using a funding source, such as, a checking account maintained at a buyer bank. In one situation, the buyer bank and the issuer 16 may be the same entity maintaining both a checking account and a credit card account for the buyer 12. Information relating to the funding source can be provided and maintained in the transaction processing system 10.
Optionally, the buyer 12 may also specify a date in connection with the payment assurance indicating that payment will be made on or before the specified date. Upon providing a specified date, the transaction processing system 10 informs the buyer 12 of settlement timeframes. For example, the buyer 12 can be informed that payments that are settled in U.S. dollars will post to a seller bank clearing account within one (1) business day of the payment due date and non-U.S. dollar transactions will post to a seller bank clearing account within two (2) business days of the payment due date.
Upon the buyer 12 indicating that a transaction is to be buyer-assured, the transaction processing system 10 “locks down” that particular transaction and its corresponding payment instruction, i.e., information relating to the transaction and the corresponding payment instruction is protected against any subsequent modifications. In addition, optional notification can be provided by the transaction processing system 10 to the buyer 12, the seller 14, the buyer bank and the seller bank regarding the buyer-assured status of the transaction. Should it be subsequently decided that the transaction is to be reversed, the reversal process is performed outside of the transaction processing system 10.
The transaction processing system 10 further allows transactions with buyer-assured status to be identified. Information relating to such transactions can then be provided to the seller 14 and/or the seller bank for reporting purposes. Such information can then be used by the seller bank to provide financing services. For example, using the information, the seller bank is able to flag transactions that it has provided factoring for. This enables the seller bank to recognize which transactions are financed so that credit for these transactions will not be passed onto the seller. Use of this information will be further described below.
In one exemplary aspect, the transaction processing system 10 enables a buyer 12 to request and/or obtain buyer bank assurance from a buyer bank. Buyer bank assurance means that the buyer bank has agreed to guarantee payment for the transaction. During the payment instruction approval process, the buyer 12 is able to issue a request for buyer bank assurance. Terms and conditions relating to the buyer bank assurance are pre-negotiated between the buyer 12 and the buyer bank. In one embodiment, such terms and conditions are stored in and used by the transaction processing system 10 to process the request. Alternatively, the request is forwarded by the transaction processing system 10 to the buyer bank for processing. The decision made by the buyer bank is then relayed to the transaction processing system 10.
In the case where the request is approved, the transaction and its corresponding payment instruction are locked down against subsequent modification and assigned a bank-assured status. Optional notification may also be provided to the buyer 12, the seller 14, the buyer bank and the seller bank.
In the case where the request is rejected, the transaction and its corresponding payment instruction are assigned a bank-assurance-rejected status and the transaction is put on hold. Optional notification may also be provided to the buyer 12, the seller 14, the buyer bank and the seller bank.
Similarly, information relating to transactions that have a bank-assured status and for which payments are payable to the seller 14 can be provided by the transaction processing system 10 to the seller bank. Such information can then be used by the seller bank to provide financing services as will be further described below. This enables the seller bank to recognize which transactions are financed and guaranteed by the buyer bank so that credit for these transactions will not be passed to the seller.
In another exemplary aspect, the transaction processing system 10 provides the ability to allow a buyer bank to offer and handle advance payment to a seller 14 at a discount; this is alternatively called “buyer bank payable discounting” (“BBPD”). This capability is designed to allow the buyer bank to offer and provide payable discounting to the seller for those future payments that the buyer bank has provided buyer bank payment assurance for. In other words, since the buyer bank has already guaranteed payment for certain payments payable to the seller 14 as described above, the buyer bank may wish to make such payments to the seller 14 at a discount in advance of the payment due dates. This allows the seller 14 to receive any owed account receivables at an earlier time prior to their due dates.
To provide the foregoing functionality, the transaction processing system 10 provides a graphical user interface (GUI) to allow the seller 14 to display and review all its transactions that qualify for BBPD from the buyer bank. Qualified transactions include, for example, transactions have been granted a bank-assured status by the buyer bank. Optionally, when the buyer bank determines the bank-assured status of a transaction, the buyer bank may also indicate whether the transaction qualifies for BBPD. In some instances, the buyer bank may disqualify a transaction for BBPD even though the bank-assured status is given. Using the GUI, the seller 14 can then select one or more qualified transactions that it would like to request for BBPD from the buyer bank. Requests pertaining to selected transactions are then forwarded by the transaction processing system 10 to the buyer bank. A status of the “BBPD Requested” may be assigned to each selected transaction. Alternatively, the transaction processing system 10 allows the buyer bank to identify transactions that qualify for BBPD and forward information relating to any identified transactions to the seller 14 for consideration. Similarly, the seller 14 can then use the transaction processing system 10 to request BBPD for selected transactions.
In addition to the requests, the transaction processing system 10 may also forward the selected transactions to the buyer bank. Using a GUI, the buyer bank may interact with the transaction processing system 10 to review and approve or reject the requests. In one implementation, the BBPD approval is based on at least two (2) levels according to the value of payment associated with the transaction.
After approving a transaction, the buyer bank then uses the GUI to provide additional information, such as, BBPD or lending terms to the transaction processing system 10. These terms include, for example, lender's name, discount rate, start date, end date, total duration, total discount amount, handling fee, net process amount (i.e., original payment amount minus discount rate minus handling fee).
After the transaction has been approved by the buyer bank, the transaction processing system 10 notifies the seller 14 of the approval. A status of “BBPD Approved” may then be assigned to the approved transaction. The seller 14 can then use the transaction processing system 10 to review the approved transaction and the associated BBPD terms. The seller 14 can then either accept or decline the approved transaction. If the approved transaction is accepted by the seller 14, the transaction processing system 10 displays a formal agreement for final approval. The formal agreement includes various types of information including, for example, the BBPD terms for the approved transaction and any other appropriate legal verbiage. In one implementation, some or all of the information contained in the formal agreement is specific to the buyer bank. The transaction processing system 10 provides the ability for the buyer bank to provide and amend its information in the formal agreement.
Once the formal agreement is accepted by the seller 14, the transaction processing system 10 notifies the buyer bank and updates all records relating to the approved transaction accordingly. For example, a status of “BBPD Buyer Bank Financed/Seller Accepted” is assigned to the approved transaction. The approved transaction and associated information is then forwarded to the buyer bank for additional processing.
In the event that the buyer bank rejects a selected transaction for which BBPD is requested, a status of “BBPD Rejected” may be assigned to the rejected transaction.
As described above, a transaction may be assigned one of a number of statuses. The transaction processing system 10 provides the ability to allow different parties, e.g., the seller 14 and the buyer bank, to sort transactions based on status.
While the foregoing describes primarily interactions between a seller 14 and a buyer bank with respect to BBPD, it should be understood that the transaction processing system 10 is able to handle a number of sellers 14 and buyer banks working with each other at the same time. In one instance, a seller 14 may be working with a number of buyer banks; in another instance, a buyer bank may be working with a number of sellers 14.
In yet another exemplary aspect, the transaction processing system 10 provides the ability to monitor future payables to individual sellers. This enables buyer banks to develop tranches to be used for lines of credit to sellers 14. A tranche is an aggregation of payables which represents a line of credit that can be offered to a seller 14. Typically, the payables in a tranche are several related securities but need not be so. Tranches usually have different, risk, reward and/or maturity characteristics. This is alternatively called “buyer bank payable discounting aggregation” (“BBPDA”).
As described above, the transaction processing system 10 keeps track of information relating to payables for transactions based on the buyer 12, the seller 14 and the buyer bank. In addition, payables for transactions can be identified as “secured” or “unsecured” by the transaction processing system 10. A payable or payment is secured if it is bank-assured (e.g., a buyer bank has guaranteed payment) or otherwise secured by other assets.
The transaction processing system 10 allows the buyer bank to develop tranches using the available payable information. For example, tranches can be identified based on a mix of secured/unsecured payables, such as, a 30-day tranche having 60% secured payables and 40% unsecured payables.
Criteria for a tranche can be specified to the transaction processing system 10 by the buyer bank via, for example, a graphical user interface. For example, the buyer bank can specify that a tranche needs to have $1 million due between fifteen (15) and thirty (30) days with at least 70% of payables secured. Using the specified criteria, the transaction processing system 10 monitors the payable information and builds the desired tranche. When sufficient payables are identified that satisfy the foregoing criteria, the transaction processing system 10 builds the corresponding tranche. All identified payables are then associated with the corresponding tranche. It should be noted that once a payable is used to build a first tranche, it cannot be used in another tranche as long as that payable is associated with that first tranche. However, a payable can be made to associate with another tranche. For example, if a payable no longer qualifies for association with the first tranche, it can then be associated with another tranche.
Once a tranche is built, the buyer bank is notified by the transaction processing system 10 that the desired tranche is available. The buyer bank can then offer the tranche to the seller 14 as a line of credit. The line of credit may be subject to certain terms and conditions set by the buyer bank. For example, the buyer bank may discount one or more future payables in the tranche. The transaction processing system 10 can relay the tranche offer and the associated terms and conditions to the seller 14.
In one implementation, a tranche corresponds to only one buyer bank and payables associated therewith belong to only one seller 14. In other words, the transaction processing system 10 allows a buyer bank to build a tranche using its payables that belong to a particular seller 14.
In addition, the transaction processing system 10 allows a seller 14 to request BBPDA. The request may include information, such as, identification of one or more buyer banks and terms and conditions desired by the seller 14. Once the request is received and if no buyer bank is specified, the transaction processing system 10 identifies payables that are owed to the seller 14 and informs one or more buyer banks that have outstanding payables owed to the seller 14 of the issuance of the BBPDA request by the seller 14. The one or more buyer banks may then use the transaction processing system 10 to create an appropriate tranche and respond to the seller 14. If a particular buyer bank is specified, then the transaction processing system 10 accordingly contacts the specified buyer bank.
Once a tranche is made available to the seller 14, the transaction processing system 10 monitors and manages the activities relating to the tranche, for example, the seller 14 drawing against the tranche. The transaction processing system 10 also provides the ability for the seller 14 to push a credit back to the buyer bank for any funds due the buyer bank (e.g., balance of line of credit and/or additional interest).
In addition, the transaction processing system 10 monitors payables in the tranche that have been paid by a buyer 12. The transaction processing system 10 notifies the buyer bank when a payment for payable associated with the tranche is made by the buyer 12. When the buyer bank receives the payment, the buyer bank uses the transaction processing system 10 to send a message to the seller 14 letting the seller 14 know how to close the corresponding transaction on its system.
In one exemplary aspect, the transaction processing system 10 provides the ability for a seller bank to provide financing to a seller 14 for a given payment. This is similar to BBPD described above. The transaction processing system 10 allows the seller bank to monitor receivables that the seller bank is going to receive on behalf of the seller 14. As a result, the seller bank is able to use the transaction processing system 10 to create an advance loan against a future payment/receivable.
In one scenario, the transaction processing system 10 allows the seller bank to proactively search for transactions that the seller may wish to receive financing. Optionally, to facilitate the search and identify qualified transactions, the transaction processing system 10 notifies the seller bank when a transaction is assigned a buyer-assured and/or bank-assured status. In addition, the transaction processing system 10 may provide functionality to allow the seller bank to search for qualified transactions using different criteria. Such criteria include, for example, specific sellers, sellers that are willing to consider financing, and transaction status, payment total, payment date, etc. Alternatively, the transaction processing system 10 allows the seller 14 to identify and select transactions that it wishes to obtain financing. Information relating to the selected transactions is then forwarded to the seller bank. The seller bank then determines which of the transactions selected by the seller 14 are to be offered financing.
Upon the seller bank identifying the qualified transactions, the transaction processing system 10 assigns a status of “Seller Financing Offered” to these transactions. Optionally, the transaction processing system 10 allows the seller bank to provide financing terms and conditions associated with these transactions. Information relating to these transactions and corresponding financing terms and conditions are then forwarded to the seller 14 for review and selection.
The seller 14 can then accept or reject each of the offered transactions. The transaction processing system 10 accordingly assigns the appropriate status to each transaction, such as, “Seller Financing Accepted” or “Seller Financing Rejected”.
If a financing offer is accepted, the transaction processing system 10 then collects the relevant information and forwards such information to the seller bank for further processing. Optionally, when a financing offer is accepted, the transaction processing system 10 may display a formal agreement for approval by the seller 14. The formal agreement includes various types of information, such as, terms and conditions and other legal verbiage associated with the financing offer.
In one exemplary embodiment, the transaction processing system 10 provides the ability to monitor future receivables to individual sellers. This is similar to BBPDA described above. This enables seller banks to develop tranches to be used for lines of credit to sellers 14. A tranche is an aggregation of receivables which represents a line of credit that can be offered to a seller 14. Typically, the receivables in a tranche are several related securities but need not be so. Tranches usually have different, risk, reward and/or maturity characteristics. This is alternatively called “seller bank receivable discounting aggregation” (“SBRDA”).
As described above, the transaction processing system 10 keeps track of information relating to receivables for transactions based on the buyer 12, the seller 14 and the seller bank. In addition, receivables for transactions can be identified as “secured” or “unsecured” by the transaction processing system 10. A receivable is secured if it is bank-assured (e.g., a buyer bank has guaranteed payment) or otherwise secured by other assets.
The transaction processing system 10 allows the seller bank to develop tranches using the available receivable information. For example, tranches can be identified based on a mix of secured/unsecured receivables, such as, a 30-day tranche having 60% secured receivables and 40% unsecured receivables.
Criteria for a tranche can be specified to the transaction processing system 10 by the seller bank. For example, the seller bank can specify that a tranche needs to have $1 million due between fifteen (15) and thirty (30) days with at least 70% of receivables secured. Using the specified criteria, the transaction processing system 10 monitors the receivable information and builds the desired tranche. When sufficient receivables are identified that satisfy the foregoing criteria, the transaction processing system 10 builds the corresponding tranche. All identified receivables are then associated with the corresponding tranche. It should be noted that once a receivable is used to build a first tranche, it cannot be used in another tranche as long as that receivable is associated with that first tranche. However, a receivable can be made to associate with another tranche. For example, if a receivable no longer qualifies for association with the first tranche, it can then be associated with another tranche.
Once a tranche is built, the seller bank is notified by the transaction processing system 10 that the desired tranche is available. The seller bank can then offer the tranche to the seller 14 as a line of credit. The line of credit may be subject to certain terms and conditions set by the seller bank. For example, the seller bank may discount one or more future receivables in the tranche. The transaction processing system 10 can relay the tranche offer and the associated terms and conditions to the seller 14.
In one implementation, a tranche corresponds to only one seller bank and receivables associated therewith belong to only one seller 14. In other words, the transaction processing system 10 allows a seller bank to build a tranche using its receivables that belong to a particular seller 14.
In addition, the transaction processing system 10 allows a seller 14 to request SBRDA. The request may include information, such as, identification of one or more seller banks and terms and conditions desired by the seller 14. Once the request is received and if no buyer bank is specified, the transaction processing system 10 identifies receivables that are owed to the seller 14 and informs one or more seller banks that have outstanding receivables owed to the seller 14 of the issuance of the SBRDA request by the seller 14. The one or more seller banks may then use the transaction processing system 10 to create an appropriate tranche and respond to the seller 14. If a particular seller bank is specified, then the transaction processing system 10 accordingly contacts the specified seller bank.
Once a tranche is made available to the seller 14, the transaction processing system 10 monitors and manages the activities relating to the tranche, for example, the seller 14 drawing against the tranche. The transaction processing system 10 also provides the ability for the seller 14 to push a credit back to the seller bank for any funds due the seller bank (e.g., balance of line of credit and/or additional interest).
In addition, the transaction processing system 10 monitors receivables in the tranche that have been received from a buyer 12. The transaction processing system 10 notifies the seller bank when a payment for receivable associated with the tranche is made by the buyer 12. When the seller bank receives the payment, the seller bank uses the transaction processing system 10 to send a message to the seller 14 letting the seller 14 know how to close the corresponding transaction on its system.
The transaction processing system 10 further includes reporting mechanisms which generate reports for various parties for a number of purposes. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate how to generate various types of reports using the present invention.
It should be understood that the present invention can be implemented in the form of control logic, in a modular or integrated manner, using software, hardware or a combination of both. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the present invention.
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 (30)

What is claimed is:
1. A system comprising a server and a computer readable medium stored on the server, wherein the server executes:
control logic on the computer readable medium for monitoring a plurality of transactions between a buyer and a seller, wherein for each transaction in the plurality of transactions, a payment is owed by the buyer to the seller;
control logic on the computer readable medium for allowing a buyer bank to offer buyer bank payable discounting aggregation (BBPDA) to the seller using information collected from monitoring the plurality of transactions;
wherein the buyer bank handles processing of payables for the plurality of transactions on behalf of the buyer;
wherein the control logic configured to allow the buyer bank to offer buyer bank payable discounting aggregation (BBPDA) to the seller further comprises
control logic on the computer readable medium for building a tranche based on a set of criteria specified by the buyer bank, wherein the tranche is associated with one or more payables corresponding to one or more of the plurality of transactions, wherein at least one of the one or more payables is unsecured; and
control logic on the computer readable medium for presenting the tranche as a line of credit to the seller, and wherein the system further comprises
control logic on the computer readable medium for informing the buyer bank once the tranche has been built according to the set of criteria.
2. The system of claim 1 wherein at least one of the one or more payables is secured, wherein the one or more secured payables are payables that the buyer bank guarantees that the buyer bank will pay.
3. The system of claim 1 further comprising:
control logic on the computer readable medium for maintaining terms and conditions relating to the line of credit, wherein the terms and conditions relating to the line of credit are provided by the buyer bank; and
control logic on the computer readable medium for presenting the terms and conditions relating to the line of credit to the seller.
4. The system of claim 3 wherein the terms and conditions relating to the line of credit are modifiable by the buyer bank.
5. The system of claim 1 further comprising:
control logic on the computer readable medium for monitoring activities incurred with respect to the tranche.
6. The system of claim 5 further comprising:
control logic on the computer readable medium for modifying the tranche in response to the monitored activities.
7. The system of claim 1 further comprising:
control logic on the computer readable medium for allowing the seller to issue a BBPDA request; and
control logic on the computer readable medium for forwarding the BBPDA request to the buyer bank;
wherein the set of criteria specified by the buyer bank is based on the BBPDA request.
8. The system of claim 1 further comprising:
control logic on the computer readable medium for monitoring the one or more payables associated with the tranche to ensure that the set of criteria is satisfied.
9. The system of claim 1 wherein the control logic for allowing the buyer bank to specify the set of criteria includes a graphical user interface.
10. The system of claim 1 further comprising:
an invoice pre-processor configured to receive a plurality of invoices in an electronic format and generate standard invoice files for the plurality of invoices;
a payment manager coupled to the invoice pre-processor and configured to receive the standard invoices files, wherein the payment manager is further configured to generate payment instructions for the standard invoice files;
a pricing engine coupled to the payment manager, wherein the pricing engine is configured to receive the payment instructions and determine transaction fees associated with the payment instructions, wherein the transaction fees are based on terms and conditions stored in a database coupled to the pricing engine; and
an authorization and settlement interface coupled to the pricing engine and configured to communicate with a data transport and processing network.
11. The system of claim 1, wherein each of the buyer and the seller have multiple transaction accounts from which the payment can be debited or credited.
12. The system of claim 1, further comprising:
control logic on the computer readable medium for sending a payment instruction to the buyer for one or more transactions in the plurality of transactions; and
control logic on the computer readable medium for receiving an approval of the payment instruction and a request from the buyer for buyer assurance from a buyer bank for the one or more transactions in the plurality of transactions.
13. The system of claim 12, wherein the approval of the payment instruction can be supplied by a third party system on behalf of the buyer.
14. A system for providing payable discounting aggregation services in connection with a plurality of buyers, a plurality of sellers, a plurality of buyer banks handling payable processing for the plurality of buyers, and a plurality of seller banks handling receivable processing for the plurality of sellers, comprising:
means for monitoring a plurality of transactions conducted between the plurality of buyers and the plurality of sellers;
means for allowing one or more buyer banks to offer buyer bank payable discounting aggregation (BBPDA) to one or more of the plurality of sellers respectively using information collected from monitoring the plurality of transactions;
means for building one or more tranches based respectively on sets of criteria specified by the one or more buyer banks, wherein each tranche is associated with a buyer bank and includes one or more payables corresponding to one or more of the plurality of transactions, the one or more payables being handled by the associated buyer bank, wherein at least one of the one or more payables is unsecured;
means for presenting the one or more tranches respectively to the one or more of the plurality of sellers as lines of credit; and
means for monitoring the payables in the tranche to ensure that a set of criteria associated with that tranche is satisfied and informing the one or more buyer banks when the set of criteria of the tranche is satisfied.
15. The system of claim 14 wherein at least one of the one or more payables is secured, wherein the one or more secured payables are payables that the buyer bank guarantees that the buyer bank will pay.
16. The system of claim 14 wherein the system further comprises:
means for maintaining terms and conditions relating to the lines of credit, wherein the terms and conditions relating to the lines of credit are provided respectively by the one or more buyer banks; and
means for presenting the terms and conditions relating to the lines of credit respectively to the one or more of the plurality of sellers.
17. The system of claim 16 wherein the terms and conditions relating to the lines of credit are modifiable by the one or more buyer banks.
18. The system of claim 14 wherein the system further comprises:
means for monitoring activities incurred with respect to the one or more tranches; and
means for modifying the one or more tranches in response to the monitored activities.
19. The system of claim 14 wherein the system further comprises:
means for allowing one or more of the plurality of sellers to issue BBPDA requests; and
means for forwarding the BBPDA requests respectively to one or more buyer banks;
wherein the sets of criteria specified by the one or more buyer banks are based respectively on the BBPDA requests.
20. The system of claim 19 wherein the system further comprises:
means for identifying the one or more buyer banks to which the BBPDA requests are to be forwarded.
21. The system of claim 14 further comprising:
an invoice pre-processor configured to receive a plurality of invoices in an electronic format and generate standard invoice files for the plurality of invoices;
a payment manager coupled to the invoice pre-processor and configured to receive the standard invoices files, wherein the payment manager is further configured to generate payment instructions for the standard invoice files;
a pricing engine coupled to the payment manager, wherein the pricing engine is configured to receive the payment instructions and determine transaction fees associated with the payment instructions, wherein the transaction fees are based on terms and conditions stored in a database coupled to the pricing engine; and
an authorization and settlement interface coupled to the pricing engine and configured to communicate with a data transport and processing network.
22. The system of claim 14, wherein each of the plurality of buyers and the plurality of sellers have multiple transaction accounts from which a payment can be debited or credited.
23. The system of claim 14, further comprising:
means for sending a payment instruction to the plurality of buyer for one or more transactions in the plurality of transactions; and
means for receiving an approval of the payment instruction and a request from the plurality of buyers for buyer assurance from a buyer bank for the one or more transactions in the plurality of transactions.
24. The system of claim 23, wherein the approval of the payment instruction can be supplied by a third party system on behalf of the plurality of buyers.
25. A transaction processing system comprising:
control logic on a computer readable medium configured to collect payable information relating to a plurality of transactions between a plurality of buyers and a plurality of sellers, wherein the payable information includes information relating to payables due to be paid out by a plurality of buyer banks to the plurality of sellers on behalf of the plurality of buyers;
control logic on the computer readable medium configured to allow the plurality of buyer banks to utilize the collected payable information to offer buyer bank payable discounting aggregation (BBPDA) to the plurality of sellers respectively;
control logic on the computer readable medium configured for receiving a BBPDA request from a seller in the plurality of sellers;
control logic on the computer readable medium configured to identify one or more buyer banks that can potentially fulfill the BBPDA request, wherein the one or more buyer banks are in charge of making payments on one or more transactions respectively on behalf of the corresponding buyers to the seller;
control logic on the computer readable medium configured to build one or more tranches based on respective sets of criteria specified by the one or more buyer banks in response to the BBPDA request;
control logic on the computer readable medium configured to build the one or more tranches using the collected payable information; and
control logic on the computer readable medium configured to allow the one or more buyer banks to respectively present the one or more tranches to the seller as lines of credit.
26. The transaction processing system of claim 25 further comprising:
control logic on the computer readable medium configured to allow the one or more buyer banks to respectively specify terms and conditions associated with the one or more tranches.
27. The transaction processing system of claim 26 further comprising:
control logic on the computer readable medium configured to allow the seller to select one of the one or more tranches for use as a line of credit; and
control logic on the computer readable medium configured to display the terms and conditions associated with the tranche selected by the seller.
28. The transaction processing system of claim 25 further comprising:
control logic on the computer readable medium configured to inform a seller of one or more buyer bank BBPDA offers made respectively by the one or more buyer banks, wherein each buyer bank BBPDA offer includes offering a tranche associated with a corresponding buyer bank as a line of credit; and
control logic on the computer readable medium configured to allow the seller to accept or reject the one or more buyer bank BBPDA offers.
29. The transaction processing system of claim 25 further comprising:
control logic on the computer readable medium configured to monitor activities with respect to a tranche in the one or more tranches to ensure that a set of criteria associated with that tranche is satisfied.
30. The transaction processing system of claim 25 further comprising:
an invoice pre-processor configured to receive a plurality of invoices in an electronic format and generate standard invoice files for the plurality of invoices;
a payment manager coupled to the invoice pre-processor and configured to receive the standard invoices files, wherein the payment manager is further configured to generate payment instructions for the standard invoice files;
a pricing engine coupled to the payment manager, wherein the pricing engine is configured to receive the payment instructions and determine transaction fees associated with the payment instructions, wherein the transaction fees are based on terms and conditions stored in a database coupled to the pricing engine; and
an authorization and settlement interface coupled to the pricing engine and configured to communicate with a data transport and processing network.
US11/131,679 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting aggregation services Active 2030-05-24 US8566231B2 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US11/131,679 US8566231B2 (en) 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting aggregation services
PCT/US2005/021049 WO2006009710A2 (en) 2004-06-17 2005-06-14 Method and system for providing assurance and financing services
KR1020077001223A KR20070050038A (en) 2004-06-17 2005-06-14 Method and system for providing assurance and financing services
CA002571331A CA2571331A1 (en) 2004-06-17 2005-06-14 Method and system for providing assurance and financing services
EP05759359A EP1782254A4 (en) 2004-06-17 2005-06-14 Method and system for providing assurance and financing services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US58102104P 2004-06-17 2004-06-17
US11/131,679 US8566231B2 (en) 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting aggregation services

Publications (2)

Publication Number Publication Date
US20050283432A1 US20050283432A1 (en) 2005-12-22
US8566231B2 true US8566231B2 (en) 2013-10-22

Family

ID=38727248

Family Applications (5)

Application Number Title Priority Date Filing Date
US11/131,605 Active 2030-05-29 US8571977B2 (en) 2004-06-17 2005-05-17 Method and system for providing seller bank receivable discounting aggregation services
US11/132,102 Abandoned US20050283433A1 (en) 2004-06-17 2005-05-17 Method and system for providing seller bank receivable discounting services
US11/131,679 Active 2030-05-24 US8566231B2 (en) 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting aggregation services
US11/131,602 Active 2030-07-14 US8606697B2 (en) 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting services
US11/132,067 Active 2030-08-07 US8571978B2 (en) 2004-06-17 2005-05-17 Method and system for providing assurance and financing services

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US11/131,605 Active 2030-05-29 US8571977B2 (en) 2004-06-17 2005-05-17 Method and system for providing seller bank receivable discounting aggregation services
US11/132,102 Abandoned US20050283433A1 (en) 2004-06-17 2005-05-17 Method and system for providing seller bank receivable discounting services

Family Applications After (2)

Application Number Title Priority Date Filing Date
US11/131,602 Active 2030-07-14 US8606697B2 (en) 2004-06-17 2005-05-17 Method and system for providing buyer bank payable discounting services
US11/132,067 Active 2030-08-07 US8571978B2 (en) 2004-06-17 2005-05-17 Method and system for providing assurance and financing services

Country Status (2)

Country Link
US (5) US8571977B2 (en)
CN (1) CN101019109A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150081522A1 (en) * 2013-08-01 2015-03-19 Fundbox, Ltd. System and method for automatically providing a/r-based lines of credit to businesses
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
US10430760B2 (en) 2015-11-24 2019-10-01 Bank Of America Corporation Enhancing communications based on physical trade documents

Families Citing this family (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004091170A2 (en) 2003-03-31 2004-10-21 Visa U.S.A. Inc. Method and system for secure authentication
US8571977B2 (en) * 2004-06-17 2013-10-29 Visa International Service Association Method and system for providing seller bank receivable discounting aggregation services
US8016185B2 (en) * 2004-07-06 2011-09-13 Visa International Service Association Money transfer service with authentication
US7870071B2 (en) * 2004-09-08 2011-01-11 American Express Travel Related Services Company, Inc. Systems, methods, and devices for combined credit card and stored value transaction accounts
US7711639B2 (en) 2005-01-12 2010-05-04 Visa International Pre-funding system and method
US7482925B2 (en) 2005-06-24 2009-01-27 Visa U.S.A. Apparatus and method to electromagnetically shield portable consumer devices
US7967194B2 (en) * 2006-05-17 2011-06-28 Mastercard International Incorporated Centralized issuer hub for transaction card customization
JP4218769B2 (en) * 2006-07-14 2009-02-04 インターナショナル・ビジネス・マシーンズ・コーポレーション System and method for managing workflow
US8799116B2 (en) * 2006-09-29 2014-08-05 The Dun & Bradstreet Corporation Process and system for automated collection of business information from a business entity's accounting system
US8041634B2 (en) * 2006-11-14 2011-10-18 Visa U.S.A. Inc. Payment processing system debt conversion notification
US10346837B2 (en) * 2006-11-16 2019-07-09 Visa U.S.A. Inc. Adaptive authentication options
US8504451B2 (en) 2006-11-16 2013-08-06 Visa U.S.A. Inc. Method and system using candidate dynamic data elements
US8175961B2 (en) * 2006-11-17 2012-05-08 Visa International Service Association Method and system for using payment history for conducting commercial transactions
CN101647040A (en) 2006-12-26 2010-02-10 维萨美国股份有限公司 Mobile payment system and method using alias
US8615426B2 (en) 2006-12-26 2013-12-24 Visa U.S.A. Inc. Coupon offers from multiple entities
US9940627B2 (en) 2006-12-26 2018-04-10 Visa U.S.A. Inc. Mobile coupon method and system
EP2118837A4 (en) 2007-01-09 2012-07-11 Visa Usa Inc Mobile phone payment process including threshold indicator
CA2582495A1 (en) * 2007-02-14 2008-08-14 Visa International Service Association Rewards program manager
US8146806B2 (en) * 2007-06-04 2012-04-03 Visa U.S.A. Inc. Prepaid negative balance fee processing and fee diversion
US7809637B2 (en) * 2007-06-04 2010-10-05 Visa U.S.A. Inc. Portability of financial tokens
US20080300895A1 (en) * 2007-06-04 2008-12-04 Monk Justin T Method and system for handling returned payment card account statements
US7860790B2 (en) * 2007-06-04 2010-12-28 Visa U.S.A. Inc. Systems and methods for automatic migration of a consumer between financial accounts
US8165938B2 (en) 2007-06-04 2012-04-24 Visa U.S.A. Inc. Prepaid card fraud and risk management
US8290832B2 (en) 2007-06-04 2012-10-16 Visa U.S.A. Inc. Method and system for handling returned prepaid payment cards
US7627522B2 (en) * 2007-06-04 2009-12-01 Visa U.S.A. Inc. System, apparatus and methods for comparing fraud parameters for application during prepaid card enrollment and transactions
US8604995B2 (en) 2007-06-11 2013-12-10 Visa U.S.A. Inc. Shielding of portable consumer device
US20090063334A1 (en) * 2007-08-28 2009-03-05 Alistair Duncan Business-to-business transaction processing utilizing electronic payment network
US8170527B2 (en) 2007-09-26 2012-05-01 Visa U.S.A. Inc. Real-time balance on a mobile phone
US8038068B2 (en) 2007-11-28 2011-10-18 Visa U.S.A. Inc. Multifunction removable cover for portable payment device
US8380624B2 (en) * 2007-12-19 2013-02-19 Ebay Inc. Person-to-person payments: contextual spending
CN101556671A (en) * 2008-04-07 2009-10-14 永丰商业银行股份有限公司 On-line financing management method
US9715709B2 (en) 2008-05-09 2017-07-25 Visa International Services Association Communication device including multi-part alias identifier
US9542687B2 (en) 2008-06-26 2017-01-10 Visa International Service Association Systems and methods for visual representation of offers
US9824355B2 (en) 2008-09-22 2017-11-21 Visa International Service Association Method of performing transactions with contactless payment devices using pre-tap and two-tap operations
US8977567B2 (en) 2008-09-22 2015-03-10 Visa International Service Association Recordation of electronic payment transaction information
US10706402B2 (en) 2008-09-22 2020-07-07 Visa International Service Association Over the air update of payment transaction data stored in secure memory
US20100145855A1 (en) * 2008-12-06 2010-06-10 Fordyce Iii Edward W Payment account processing which conveys non purchase related data exchanges
US8725642B2 (en) * 2009-04-27 2014-05-13 Visa International Service Association Delayed settlement transactions
US20110264483A1 (en) * 2010-04-27 2011-10-27 Hamid Reza Motahari Nezhad Dynamic collaborative adaptation of a business activity in a business activity management system
US9633332B2 (en) 2010-07-13 2017-04-25 Hewlett Packard Enterprise Development Lp Generating machine-understandable representations of content
US20120095872A1 (en) * 2010-10-19 2012-04-19 Jonty Hurwitz Many-to-one transaction fulfilment system
WO2012161808A2 (en) 2011-02-25 2012-11-29 Visa International Service Association Direct connection systems and methods
CN103077454A (en) * 2012-11-23 2013-05-01 雷桂斌 Synchronous payment system
CN103996139A (en) * 2013-02-20 2014-08-20 深圳市亿商屋广告传媒有限公司 Credit self-guarantee platform web server, and credit self-guarantee system and method
WO2015145215A1 (en) * 2014-03-28 2015-10-01 Yogesh Chunilal Rathod Providing and consuming lines of credit and offers of provider(s) for making payments and purchasing products and/or services
US10373157B1 (en) 2015-07-30 2019-08-06 Payability, LLC Computer system for accelerating resource transfers based on non-finalized operation information
CN107067262A (en) * 2015-09-30 2017-08-18 阿里巴巴集团控股有限公司 Method for processing business, system and user terminal
DE102016107072A1 (en) * 2016-04-15 2017-10-19 Traxpay Ag Method for automatically financing invoices
WO2018122820A1 (en) * 2016-12-28 2018-07-05 Arora Inderpal Singh System and method for assuring payments and receivables
US11062322B2 (en) * 2017-12-21 2021-07-13 Mastercard International Incorporated Server and method for hosting a ledger
CN109639779B (en) * 2018-11-29 2021-09-17 贵州航天云网科技有限公司 Dynamic integration system based on block chain manufacturing service
US20210133732A1 (en) * 2019-11-01 2021-05-06 Walmart Apollo, Llc Systems and methods for guest payment
US11836793B2 (en) * 2020-12-11 2023-12-05 International Business Machines Corporation Invoice deferral recommendation

Citations (248)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3990558A (en) 1973-10-08 1976-11-09 Gretag Aktiengesellschaft Method and apparatus for preparing and assessing payment documents
US4001568A (en) 1973-12-29 1977-01-04 Glory Kogyo Kabushiki Kaisha Monetary receipt and payment managing apparatus
US4116469A (en) 1977-08-08 1978-09-26 Harriman Russell H Combined payment and receipt form and method of using
US4280037A (en) 1979-01-31 1981-07-21 Lgz Landis & Gyr Zug Ag Apparatus for cashless payment of merchandise or services
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
US4360727A (en) 1981-04-09 1982-11-23 Compagnie Generale d'Automatise Societe Anonyme dite Payment voucher
US4370649A (en) 1981-05-19 1983-01-25 Fuerle Gerard A Payment responsive data display network
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
US4545475A (en) 1980-06-11 1985-10-08 Flonic S.A. Secure coin collection device for pre-payment machine
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
US4607335A (en) 1982-12-14 1986-08-19 Omron Tateisi Electronics Co. Apparatus for performing transactions with verification of remittance through comparison with logical payment patterns
US4675515A (en) 1986-03-04 1987-06-23 Lucero James L Drive-through credit card payment device
USD290954S (en) 1985-07-05 1987-07-21 Northern Telecom Limited Housing for credit card payment telephone
US4713761A (en) 1985-07-18 1987-12-15 Pitney Bowes, Inc. System for centralized processing of accounting and payment functions
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
US4858121A (en) 1986-12-12 1989-08-15 Medical Payment Systems, Incorporated Medical payment system
US4860946A (en) 1988-06-29 1989-08-29 Moore Business Forms, Inc. Invoice form with card and envelope
US4864110A (en) 1986-10-16 1989-09-05 Etat Francis/Telediffusion De France Electronic payment process using a smart card
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
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
US4939351A (en) 1987-03-30 1990-07-03 Crouzet Automatic payment machine delivering a voucher
US4947028A (en) 1988-07-19 1990-08-07 Arbor International, Inc. Automated order and payment system
US4972463A (en) 1986-09-15 1990-11-20 Norand Corporation In-store multiple device communications unit and centralized data system utilizing same
US4974878A (en) 1988-04-20 1990-12-04 Remittance Technology Corporation Financial data processing system using payment coupons
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
US5055657A (en) 1988-12-05 1991-10-08 Scheidt & Bachmann Gesellschaft Mit Beschrankter Haftung Vending type machine dispensing a redeemable credit voucher upon payment interrupt
US5056645A (en) 1988-05-31 1991-10-15 Jofemar, S.A. Coin operated telephone payment device
US5134656A (en) 1989-02-22 1992-07-28 Kudelski S.A. Fabrique D'enregistruers Nagra Pre-payment television system using a memory card associated with a decoder
US5136632A (en) 1990-04-05 1992-08-04 Alain Bernard Telephone service payment system using a sound emitting token
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
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
US5216620A (en) 1991-09-23 1993-06-01 Pitney Bowes Inc. Requesting, reporting and verification system and method for mail carrier payment
US5222018A (en) 1985-07-18 1993-06-22 Pitney Bowes Inc. System for centralized processing of accounting and payment functions
US5225977A (en) 1991-03-18 1993-07-06 Hooper John B Card payment system for service dispensing devices
US5237159A (en) 1991-07-17 1993-08-17 J. D. Carreker And Associates Electronic check presentment 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
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
US5269521A (en) 1990-08-22 1993-12-14 Rossides Michael T Expected value payment method and system for reducing the expected per unit costs of paying and/or receiving a given amount of a commodity
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
US5289923A (en) 1992-11-23 1994-03-01 Atlantic Richfield Company Stacker for electronic payment system key pad and printer
US5291304A (en) 1989-04-18 1994-03-01 Murata Kikai Kabushiki Kaisha Facsimile apparatus having invoice sentence preparation function
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
US5315511A (en) 1989-04-21 1994-05-24 Hitachi, Ltd. Method of determining the acceptability of a request to preengage receipt and/or payment of money in an ATM system using the same
US5336870A (en) 1992-05-26 1994-08-09 Hughes Thomas S System for remote purchase payment transactions and remote bill payments
US5359509A (en) 1991-10-31 1994-10-25 United Healthcare Corporation Health care payment adjudication and review system
US5359183A (en) 1992-04-06 1994-10-25 Rafael Skodlar Payment card with display
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
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
US5403025A (en) 1994-03-03 1995-04-04 Shanley; Thomas M. Partially preprinted, service invoice record forms, having piggyback vinyl status
US5412191A (en) 1990-09-21 1995-05-02 Siemens Nixdorf Informationssysteme Aktiengesellschaft Service desk for the registration, booking and/or payment of goods, vouchers and the like
US5412886A (en) 1993-03-24 1995-05-09 Quinn; Maureen T. Calendar oriented monthly bill payment sorter
US5424938A (en) * 1992-10-13 1995-06-13 First Chicago Corporation Method and apparatus for providing access to a plurality of payment networks
US5472116A (en) 1993-05-19 1995-12-05 Schlumberger Industries Apparatus for selecting and dispensing a service against payment
US5479510A (en) 1994-11-15 1995-12-26 Olsen; Kurt B. Automated data card payment verification method
US5478993A (en) 1993-01-18 1995-12-26 Ascom Autelca Ag. Process as safety concept against unauthorized use of a payment instrument in cashless payment at payment sites
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
US5532920A (en) 1992-04-29 1996-07-02 International Business Machines Corporation Data processing system and method to enforce payment of royalties when copying softcopy books
US5536923A (en) 1993-09-02 1996-07-16 Gemplus Card International Payment memory medium and method of use thereof
US5575374A (en) 1993-10-18 1996-11-19 Gemplus Card International Games machine with electronic payment mechanism
US5580310A (en) 1994-03-16 1996-12-03 Gemplus Card International Games machine with mechanical counters as laid down by regulations, and with electronic payment mechanism
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
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
US5590197A (en) 1995-04-04 1996-12-31 V-One Corporation Electronic payment system and method
US5590196A (en) 1994-10-06 1996-12-31 Connotech Experts Conseils Inc. Secure payment method using facsimile
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
US5635695A (en) 1994-08-31 1997-06-03 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
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
US5637848A (en) 1993-06-04 1997-06-10 Jean-Claude Decaux Payment installation for a transport network
US5652786A (en) 1994-02-14 1997-07-29 Telepay Automated interactive bill payment system
US5655023A (en) 1994-05-13 1997-08-05 Pitney Bowes Inc. Advanced postage payment system employing pre-computed digital tokens and with enhanced security
US5671364A (en) 1993-02-10 1997-09-23 Turk; James J. Method and system for commodity-based currency for payment of accounts and elimination of payment risk
US5675650A (en) 1995-05-02 1997-10-07 Pitney Bowes Inc. Controlled acceptance mail payment and evidencing system
USD385304S (en) 1996-09-16 1997-10-21 Griffin Peter B Invoice file clip
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
USD386882S (en) 1996-07-25 1997-11-25 Smith Ervin M Island payment terminal
US5699528A (en) 1995-10-31 1997-12-16 Mastercard International, Inc. System and method for bill delivery and payment over a communications network
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
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
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
US5748908A (en) 1995-06-07 1998-05-05 Yu; Mason K. Automated, classified expenditure data card recording system
US5754655A (en) 1992-05-26 1998-05-19 Hughes; Thomas S. System for remote purchase payment and remote bill payment transactions
US5757917A (en) 1995-11-01 1998-05-26 First Virtual Holdings Incorporated Computerized payment system for purchasing goods and services on the internet
US5761308A (en) 1995-09-01 1998-06-02 Fujitsu Limited System for refunding payment for software
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
US5778067A (en) 1990-04-12 1998-07-07 Mondex International Limited Value transfer system
US5783808A (en) 1996-01-11 1998-07-21 J. D. Carreker And Associates, Inc. Electronic check presentment system having transaction level reconciliation capability
US5808723A (en) 1996-05-21 1998-09-15 Eastman Kodak Company Photofinishing system having customized customer order payment feature
USD398446S (en) 1996-10-03 1998-09-22 Hosea Darlene L Payment booklet holder
US5812945A (en) 1995-12-22 1998-09-22 Pitney Bowes Inc. Metered payment cellular telephone communication system
US5819239A (en) 1996-12-30 1998-10-06 Pitney Bowes Inc. Method of verifying proper payment of postage
US5816174A (en) 1996-07-25 1998-10-06 Smith; Ervin M. Island payment terminal mounting 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
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
US5826241A (en) 1994-09-16 1998-10-20 First Virtual Holdings Incorporated Computerized system for making payments and authenticating transactions over the internet
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
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
US5842183A (en) 1995-11-21 1998-11-24 International Billings Services, Inc. Dynamically updated payment due date 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
US5890137A (en) 1995-12-15 1999-03-30 Kabushiki Kaisha N.K. Kikaku On-line shopping system and the method of payment settlement
US5893902A (en) 1996-02-15 1999-04-13 Intelidata Technologies Corp. Voice recognition bill payment system with speaker verification and confirmation
US5893907A (en) 1995-10-26 1999-04-13 Ukuda; Shuko Apparatus and system for managing a card number
US5903880A (en) 1996-07-19 1999-05-11 Biffar; Peter C. Self-contained payment system with circulating digital vouchers
US5905976A (en) 1995-07-19 1999-05-18 France Telecom System of secured payment by the transfer of electronic money through an interbank network
US5907832A (en) 1995-11-15 1999-05-25 Koninklijke Ptt Nederland N.V. Method of debiting an electronic payment means
US5909492A (en) 1994-10-24 1999-06-01 Open Market, Incorporated Network sales system
US5914472A (en) 1997-09-23 1999-06-22 At&T Corp Credit card spending authorization control system
WO1999033016A1 (en) 1997-12-22 1999-07-01 Charles Wong Integrated business-to-business web commerce and business automation system
US5924084A (en) 1995-07-06 1999-07-13 De Rooij; Peter Jacobus Nicolaas Method for tracing payment data in an anonymous 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
US5936219A (en) 1995-03-13 1999-08-10 Kabushiki Kaisha Toshiba Electronic payment system using check identifier and issue time for illegal acts detection
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
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
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
US5963925A (en) 1996-10-09 1999-10-05 Visa International Service Association Electronic statement presentment system
US5966698A (en) 1992-10-15 1999-10-12 Pollin; Robert E. Automated payment system and method
US5970475A (en) 1997-10-10 1999-10-19 Intelisys Electronic Commerce, Llc Electronic procurement system and method for trading partners
US5974146A (en) 1997-07-30 1999-10-26 Huntington Bancshares Incorporated Real time bank-centric universal payment system
US5974145A (en) 1995-10-26 1999-10-26 Koninklijke Kpn N.V. Method for cancelling a transaction of an electronic payment means, as well as payment means for application of the method
US5973619A (en) 1997-06-10 1999-10-26 Paredes; Alexis Automated vehicle dispatch and payment honoring system
US5978780A (en) 1997-11-21 1999-11-02 Craig Michael Watson Integrated bill consolidation, payment aggregation, and settlement system
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
WO1999056193A2 (en) 1998-04-30 1999-11-04 Ec Cubed, Inc. Method and system for routing data based on a business rule stored in a relational database
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
US5983207A (en) 1993-02-10 1999-11-09 Turk; James J. Electronic cash eliminating payment risk
US5987140A (en) 1996-04-26 1999-11-16 Verifone, Inc. System, method and article of manufacture for secure network electronic payment and credit collection
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
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
US5991412A (en) 1995-12-08 1999-11-23 Koninklijke Kpn N.V. Method for protectedly debiting an electronic payment means
US5995626A (en) 1995-08-04 1999-11-30 Hitachi, Ltd. Electronic shopping method, electronic shopping system and document authenticating method relating thereto
US5999625A (en) 1997-02-27 1999-12-07 International Business Machines Corporation Method for electronic payment system with issuer control
US6006199A (en) 1991-12-31 1999-12-21 International Business Machines Corporation Method and system for automated payment within a computer integrated manufacturing 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
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
US6038547A (en) 1998-01-07 2000-03-14 Casto; Robin L. Construction tracking and payment method and system
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
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
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
US6058382A (en) 1996-09-12 2000-05-02 Hitachi, Ltd. Electronic money holding device utilizing an automatic payment method
US6058380A (en) 1995-12-08 2000-05-02 Mellon Bank, N.A. System and method for electronically processing invoice information
US6056322A (en) 1998-08-03 2000-05-02 Lupi; Louis A. Combination sample medication payment check and medication prescription device
US6061665A (en) 1997-06-06 2000-05-09 Verifone, Inc. System, method and article of manufacture for dynamic negotiation of a network payment framework
US6062472A (en) 1996-12-23 2000-05-16 Koninklijke Ptt Nederland N.V. System and method for increasing a value of an electronic payment card including performing a restore transaction in response to interruption of a value increase transaction
US6065675A (en) 1997-06-30 2000-05-23 Cardis Enterprise International N.V. Processing system and method for a heterogeneous electronic cash environment
US6070148A (en) 1997-03-25 2000-05-30 Hitachi, Ltd. Electronic commerce system and method for providing commercial information in electronic commerce system
US6070150A (en) 1996-10-18 2000-05-30 Microsoft Corporation Electronic bill presentment and payment system
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
US6073113A (en) 1998-06-29 2000-06-06 Sun Microsystems, Inc. Compatibility checking between instruments, operations and protocols in electronic commerce
US6070798A (en) 1997-02-21 2000-06-06 Nethery; Kee Purchaser generated transaction recording and negotiable instrument payment system
US6073104A (en) 1994-11-09 2000-06-06 Field; Richard G. System for invoice record management and asset-backed commercial paper program management
US6073125A (en) 1997-06-26 2000-06-06 Pitney Bowes Inc. Token key distribution system controlled acceptance mail payment and evidencing system
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
US6076074A (en) 1998-05-05 2000-06-13 The Clearing House Service Company L.L.C. System and method for intraday netting payment finality
US6081790A (en) 1998-03-20 2000-06-27 Citibank, N.A. System and method for secure presentment and payment over open networks
US6085169A (en) 1996-09-04 2000-07-04 Priceline.Com Incorporated Conditional purchase offer management system
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
US6108644A (en) 1998-02-19 2000-08-22 At&T Corp. System and method for electronic transactions
US6108531A (en) 1994-09-20 2000-08-22 Ne-Products Oy Terminal equipment providing payment data in a cellular radio system
US6109837A (en) 1995-06-01 2000-08-29 Snef Cote D'azur (S.A.) Pneumatic conveyor for small metallic pieces, particularly coins, for payment points
US6115601A (en) 1996-10-23 2000-09-05 U.S. Philips Corporation Payment scheme for a mobile communication service
US6122625A (en) 1991-11-15 2000-09-19 Citibank, N.A. Apparatus and method for secure transacting
US6125354A (en) 1997-03-31 2000-09-26 Bellsouth Intellectual Property Corporation System and method for generating an invoice to rebill charges to the elements of an organization
US6135261A (en) 1998-10-23 2000-10-24 Robert E. Noell, Jr. Payment-receiving enclosure for a vending machine
US6138907A (en) 1996-12-02 2000-10-31 Oki Electric Industry Co., Ltd. Electronic transaction processing system and method for operating same
US6148405A (en) * 1997-11-10 2000-11-14 Phone.Com, Inc. Method and system for secure lightweight transactions in wireless data networks
US6163771A (en) 1997-08-28 2000-12-19 Walker Digital, Llc Method and device for generating a single-use financial account number
US6167385A (en) 1998-11-30 2000-12-26 The Chase Manhattan Bank Supply chain financing system and method
US6167378A (en) 1997-01-21 2000-12-26 Webber, Jr.; Donald Gary Automated back office transaction method and system
US6169974B1 (en) 1998-10-08 2001-01-02 Paymentech, Inc. Method for closed loop processing of transactions utilizing bank card association
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
US6173269B1 (en) 1998-12-16 2001-01-09 Zowi.Com, Inc Method and apparatus for executing electronic commercial transactions with minors
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
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
US6216115B1 (en) 1998-09-28 2001-04-10 Benedicto Barrameda Method for multi-directional consumer purchasing, selling, and transaction management
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
US6230148B1 (en) 1994-11-28 2001-05-08 Veristar Corporation Tokenless biometric electric check transaction
US6227447B1 (en) 1999-05-10 2001-05-08 First Usa Bank, Na Cardless payment system
WO2001033522A1 (en) 1999-11-05 2001-05-10 American Express Travel Related Services Company, Inc. Systems and methods for facilitating commercial transactions between parties residing at remote locations
US6233565B1 (en) 1998-02-13 2001-05-15 Saranac Software, Inc. Methods and apparatus for internet based financial transactions with evidence of payment
US20010011255A1 (en) 1996-12-13 2001-08-02 Alan Asay Reliance management for electronic transaction system
WO2001057770A1 (en) 2000-02-04 2001-08-09 Kuo James S Process and method for secure online transactions with calculated risk
US6304858B1 (en) * 1998-02-13 2001-10-16 Adams, Viner And Mosler, Ltd. Method, system, and computer program product for trading interest rate swaps
US6324525B1 (en) 1996-06-17 2001-11-27 Hewlett-Packard Company Settlement of aggregated electronic transactions over a network
US20010047273A1 (en) 2000-03-17 2001-11-29 Greer Edward Cooper Electronic transaction clearing system
US20020038277A1 (en) * 2000-02-22 2002-03-28 Yuan Frank S. Innovative financing method and system therefor
US20020095355A1 (en) * 2001-01-18 2002-07-18 Doreen A. Labit Computer-implemented international trade system
US20020161704A1 (en) * 1993-11-01 2002-10-31 Visa International Service Association Method and apparatus for paying bills electronically using machine readable information from an invoice
WO2003038553A2 (en) 2001-10-29 2003-05-08 Visa International Service Association Method and system for conducting a commercial transaction between a buyer and a seller
US20030093367A1 (en) * 2001-11-15 2003-05-15 First Data Corporation Online incremental payment method
US20030126075A1 (en) * 2001-11-15 2003-07-03 First Data Corporation Online funds transfer method
US20030130959A1 (en) 2001-02-15 2003-07-10 Walter Rosenbaum Closed loop electronic factoring
KR20030070348A (en) * 2002-02-25 2003-08-30 (주)베스텍컴 payment system using a credit card for trade and method thereof
US20040010463A1 (en) 1996-11-12 2004-01-15 Hahn-Carlson Dean W. Automated transaction processing system and approach
US20040015436A1 (en) * 2000-09-06 2004-01-22 Norman Understein Interbank process
US6721716B1 (en) * 1999-06-17 2004-04-13 Mobius Management Systems, Inc. Payment certification string and related electronic payment system and method
US20040078328A1 (en) * 2002-02-07 2004-04-22 Talbert Vincent W. Method and system for completing a transaction between a customer and a merchant
US20040088245A1 (en) * 2002-11-04 2004-05-06 Manoj Narayan Systems and methods for producing documentary credit and conforming shipping documents
US20040128240A1 (en) * 2002-10-07 2004-07-01 Yusin Wendy E. Method and system for managing financial transactions
US20050027654A1 (en) * 2003-07-28 2005-02-03 Adrian Alexandra J. System and method for a business payment connection
US20050144130A1 (en) * 2003-12-31 2005-06-30 Staniar Jud C. Method and apparatus for automatically processing invoiced payments with selectable payment terms
US20050283433A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing seller bank receivable discounting services
US20070106604A1 (en) * 2000-01-28 2007-05-10 Fundamo (Proprietary) Limited System for conducting commercial transactions
US20070174191A1 (en) * 2000-09-05 2007-07-26 Keaton G D Factoring system and method
US20080010194A1 (en) * 2006-07-10 2008-01-10 Automated Payment Highway, Inc. Method and apparatus for financing community expenses

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US500585A (en) * 1893-07-04 Josef klieber
GB2178012B (en) * 1985-07-09 1989-10-11 Konishiroku Photo Ind Sheet conveyance apparatus
SE8504501D0 (en) * 1985-09-30 1985-09-30 Astra Meditec Ab METHOD OF FORMING AN IMPROVED HYDROPHILIC COATING ON A POLYMER SURFACE
US5135856A (en) * 1987-06-24 1992-08-04 Arch Development Corp. Production of autocrine growth factors
US4822121A (en) * 1987-10-31 1989-04-18 Santa Barbara Research Center Angular scan drive system having means for selectively extending the range thereof
JPH0757540B2 (en) * 1989-02-17 1995-06-21 チッソ株式会社 Flexible printed circuit board manufacturing method
US5222620A (en) * 1991-10-29 1993-06-29 Russell-Stanley Corporation Drum liner locking and locating assembly
US5655085A (en) * 1992-08-17 1997-08-05 The Ryan Evalulife Systems, Inc. Computer system for automated comparing of universal life insurance policies based on selectable criteria
US7155409B1 (en) * 1999-03-05 2006-12-26 Trade Finance Service Corporation Trade financing method, instruments and systems
US6315511B1 (en) * 1999-07-15 2001-11-13 William L. Taube Method and apparatus for coining end panels of containers
US7069234B1 (en) * 1999-12-22 2006-06-27 Accenture Llp Initiating an agreement in an e-commerce environment
US7881962B2 (en) * 2000-03-14 2011-02-01 Verizon Business Global Llc Early-payment discount for E-billing system
US20040024692A1 (en) * 2001-02-27 2004-02-05 Turbeville Wallace C. Counterparty credit risk system
US20030115111A1 (en) 2001-08-25 2003-06-19 Fisher Douglas C. Mediated order management agent
US7249069B2 (en) * 2001-08-27 2007-07-24 United Parcel Service Of America, Inc. International cash-on-delivery system and method
US8249963B1 (en) * 2003-10-03 2012-08-21 Blowers Alden J Method for providing comprehensive ACH vendor services
US20060095374A1 (en) * 2004-11-01 2006-05-04 Jp Morgan Chase System and method for supply chain financing
US7822682B2 (en) * 2005-06-08 2010-10-26 Jpmorgan Chase Bank, N.A. System and method for enhancing supply chain transactions

Patent Citations (271)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3990558A (en) 1973-10-08 1976-11-09 Gretag Aktiengesellschaft Method and apparatus for preparing and assessing payment documents
US4001568A (en) 1973-12-29 1977-01-04 Glory Kogyo Kabushiki Kaisha Monetary receipt and payment managing apparatus
US4116469A (en) 1977-08-08 1978-09-26 Harriman Russell H Combined payment and receipt form and method of using
US4280037A (en) 1979-01-31 1981-07-21 Lgz Landis & Gyr Zug Ag Apparatus for cashless payment of merchandise or services
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
US4545475A (en) 1980-06-11 1985-10-08 Flonic S.A. Secure coin collection device for pre-payment 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
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
US4607335A (en) 1982-12-14 1986-08-19 Omron Tateisi Electronics Co. Apparatus for performing transactions with verification of remittance through comparison with logical payment patterns
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
USD290954S (en) 1985-07-05 1987-07-21 Northern Telecom Limited Housing for credit card payment telephone
US4713761A (en) 1985-07-18 1987-12-15 Pitney Bowes, Inc. System for centralized processing of accounting and payment functions
US5222018A (en) 1985-07-18 1993-06-22 Pitney Bowes Inc. System for centralized processing of accounting and payment functions
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
US4675515A (en) 1986-03-04 1987-06-23 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
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
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
US4972463A (en) 1986-09-15 1990-11-20 Norand Corporation In-store multiple device communications unit and centralized data system utilizing same
US4799156A (en) * 1986-10-01 1989-01-17 Strategic Processing Corporation Interactive market management system
US4864110A (en) 1986-10-16 1989-09-05 Etat Francis/Telediffusion De France Electronic payment process using a smart card
US4797540A (en) 1986-11-06 1989-01-10 Omron Tateisi Electronics Co. Payment making terminal device
US4858121A (en) 1986-12-12 1989-08-15 Medical Payment Systems, Incorporated Medical payment system
US4920256A (en) 1987-03-02 1990-04-24 Crouzet Universal electronic payment terminal base including memory card programming voltage booster
US4939351A (en) 1987-03-30 1990-07-03 Crouzet Automatic payment machine delivering a voucher
USD304725S (en) 1987-12-16 1989-11-21 GEC Plessy Telecommunications Ltd. Public pay telephone stand with alternative payment means
US5963921A (en) 1988-01-21 1999-10-05 Beneficial Financial Corporation 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
US4890228A (en) 1988-01-21 1989-12-26 Beneficial Management Corporation Of America Electronic income tax refund early payment system
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
US4974878A (en) 1988-04-20 1990-12-04 Remittance Technology Corporation Financial data processing system using payment coupons
US5056645A (en) 1988-05-31 1991-10-15 Jofemar, S.A. 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
US4947028B1 (en) 1988-07-19 1993-06-08 U S Order Inc
US4947028A (en) 1988-07-19 1990-08-07 Arbor International, Inc. Automated order and payment system
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
US5055657A (en) 1988-12-05 1991-10-08 Scheidt & Bachmann Gesellschaft Mit Beschrankter Haftung Vending type machine dispensing a redeemable credit voucher upon payment interrupt
US5134656A (en) 1989-02-22 1992-07-28 Kudelski S.A. Fabrique D'enregistruers Nagra Pre-payment television system using a memory card associated with a decoder
US5291304A (en) 1989-04-18 1994-03-01 Murata Kikai Kabushiki Kaisha Facsimile apparatus having invoice sentence preparation function
US5315511A (en) 1989-04-21 1994-05-24 Hitachi, Ltd. Method of determining the acceptability of a request to preengage receipt and/or payment of money in an ATM system using the same
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
US5136632A (en) 1990-04-05 1992-08-04 Alain Bernard Telephone service payment system using a sound emitting token
US5778067A (en) 1990-04-12 1998-07-07 Mondex International Limited Value transfer system
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
US5269521A (en) 1990-08-22 1993-12-14 Rossides Michael T Expected value payment method and system for reducing the expected per unit costs of paying and/or receiving a given amount of a commodity
US5412191A (en) 1990-09-21 1995-05-02 Siemens Nixdorf Informationssysteme Aktiengesellschaft Service desk for the registration, booking and/or payment of goods, vouchers and the like
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
US5225977A (en) 1991-03-18 1993-07-06 Hooper John B Card payment system for service dispensing devices
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
US5237159A (en) 1991-07-17 1993-08-17 J. D. Carreker And Associates Electronic check presentment system
US5412190A (en) 1991-07-17 1995-05-02 J. D. Carreker & Associates, Inc. Electronic check presentment system having a return item notification system incorporated therein
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
US5532464A (en) 1991-07-17 1996-07-02 J. D. Carreker & Associates, Inc. Electronic check presentment system having a return item notification system incorporated therein
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
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
US6122625A (en) 1991-11-15 2000-09-19 Citibank, N.A. Apparatus and method for secure transacting
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
US5285883A (en) 1992-03-11 1994-02-15 Atoll Technology Automatic payment device and method for recognizing coins
US5359183A (en) 1992-04-06 1994-10-25 Rafael Skodlar Payment card with display
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
US5532920A (en) 1992-04-29 1996-07-02 International Business Machines Corporation Data processing system and method to enforce payment of royalties when copying softcopy books
US5754655A (en) 1992-05-26 1998-05-19 Hughes; Thomas S. System for remote purchase payment and remote bill payment transactions
US5336870A (en) 1992-05-26 1994-08-09 Hughes Thomas S System for remote purchase payment transactions and remote bill payments
US5491325A (en) 1992-08-25 1996-02-13 Huang; Dorge O. Method and system for payment and payment verification
US5424938A (en) * 1992-10-13 1995-06-13 First Chicago Corporation Method and apparatus for providing access to a plurality of payment networks
US5504677A (en) 1992-10-15 1996-04-02 Pollin; Robert E. Automated payment system
US6041315A (en) 1992-10-15 2000-03-21 Autoscribe Corporation Automated payment system and method
US5727249A (en) 1992-10-15 1998-03-10 Pollin; Robert E. Automated payment system and method
US5966698A (en) 1992-10-15 1999-10-12 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
US5478993A (en) 1993-01-18 1995-12-26 Ascom Autelca Ag. Process as safety concept against unauthorized use of a payment instrument in cashless payment at payment sites
US5671364A (en) 1993-02-10 1997-09-23 Turk; James J. Method and system for commodity-based currency for payment of accounts and elimination of payment risk
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
US5472116A (en) 1993-05-19 1995-12-05 Schlumberger Industries Apparatus for selecting and dispensing a service against payment
US5492212A (en) 1993-06-02 1996-02-20 Schlumberger Industries Device for sorting and storing objects inserted by way of payment in a dispenser
US5637848A (en) 1993-06-04 1997-06-10 Jean-Claude Decaux Payment installation for a transport network
US5536923A (en) 1993-09-02 1996-07-16 Gemplus Card International Payment memory medium and method of use thereof
US5697482A (en) 1993-10-18 1997-12-16 Gemplus Card International Games machine with electronic payment mechanism
US5575374A (en) 1993-10-18 1996-11-19 Gemplus Card International Games machine with electronic payment mechanism
US5706925A (en) 1993-10-18 1998-01-13 Gemplus Card International Games machine with electronic payment mechanism
US20020161704A1 (en) * 1993-11-01 2002-10-31 Visa International Service Association Method and apparatus for paying bills electronically using machine readable information from an invoice
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
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
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
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
US5857152A (en) 1994-02-01 1999-01-05 Mondex International Limited Electronic toll payment
US5652786A (en) 1994-02-14 1997-07-29 Telepay Automated interactive bill payment system
US5403025A (en) 1994-03-03 1995-04-04 Shanley; Thomas M. Partially preprinted, service invoice record forms, having piggyback vinyl status
US5580310A (en) 1994-03-16 1996-12-03 Gemplus Card International Games machine with mechanical counters as laid down by regulations, and with electronic payment mechanism
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
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
US5635695A (en) 1994-08-31 1997-06-03 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
US5826241A (en) 1994-09-16 1998-10-20 First Virtual Holdings Incorporated Computerized system for making payments and authenticating transactions over the internet
US6108531A (en) 1994-09-20 2000-08-22 Ne-Products Oy Terminal equipment providing payment data in a cellular radio system
US5590196A (en) 1994-10-06 1996-12-31 Connotech Experts Conseils Inc. Secure payment method using facsimile
US6151588A (en) * 1994-10-13 2000-11-21 Tradecard, Inc. Full service trade system
US5717989A (en) * 1994-10-13 1998-02-10 Full Service Trade System Ltd. Full service trade system
US5909492A (en) 1994-10-24 1999-06-01 Open Market, Incorporated 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
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
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
US5717868A (en) 1995-03-07 1998-02-10 Huntington Bancshares Inc. Electronic payment interchange concentrator
US6129272A (en) 1995-03-13 2000-10-10 Kabushiki Kaisha Toshiba Electronic payment system using check identifier and issue time for illegal acts detection
US5936219A (en) 1995-03-13 1999-08-10 Kabushiki Kaisha Toshiba Electronic payment system using check identifier and issue time for illegal acts detection
US5590197A (en) 1995-04-04 1996-12-31 V-One Corporation Electronic payment system and method
US5614892A (en) 1995-04-24 1997-03-25 Pom, Inc. Payment slot communicating apparatus for vendng prices
US5675650A (en) 1995-05-02 1997-10-07 Pitney Bowes Inc. Controlled acceptance mail payment and evidencing system
US5880454A (en) 1995-05-11 1999-03-09 Schlumberger Industries Electronic payment card with an interchangeable module
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
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
US6109837A (en) 1995-06-01 2000-08-29 Snef Cote D'azur (S.A.) Pneumatic conveyor for small metallic pieces, particularly coins, for payment points
US5832460A (en) 1995-06-02 1998-11-03 International Business Machines Corporation Method and system for bill presentation and payment reconciliation
US5748908A (en) 1995-06-07 1998-05-05 Yu; Mason K. Automated, classified expenditure data card recording system
US5832089A (en) 1995-06-07 1998-11-03 Sandia Corporation Off-line compatible electronic cash method and system
US6014646A (en) 1995-06-08 2000-01-11 France Telecom Process for making a payment using an account manager
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
US5924084A (en) 1995-07-06 1999-07-13 De Rooij; Peter Jacobus Nicolaas Method for tracing payment data in an anonymous payment system
US5905976A (en) 1995-07-19 1999-05-18 France Telecom System of secured payment by the transfer of electronic money through an interbank network
US5995626A (en) 1995-08-04 1999-11-30 Hitachi, Ltd. Electronic shopping method, electronic shopping system and document authenticating method relating thereto
US5761308A (en) 1995-09-01 1998-06-02 Fujitsu Limited System for refunding payment for software
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
US5893907A (en) 1995-10-26 1999-04-13 Ukuda; Shuko Apparatus and system for managing a card number
US5974145A (en) 1995-10-26 1999-10-26 Koninklijke Kpn N.V. Method for cancelling a transaction of an electronic payment means, as well as payment means for application of the method
US5699528A (en) 1995-10-31 1997-12-16 Mastercard International, Inc. System and method for bill delivery and payment over a communications network
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
US5757917A (en) 1995-11-01 1998-05-26 First Virtual Holdings Incorporated Computerized payment system for purchasing goods and services on the internet
US6076073A (en) 1995-11-15 2000-06-13 Koninklijke Kpn N.V. Method of debiting an electronic payment means
US5907832A (en) 1995-11-15 1999-05-25 Koninklijke Ptt Nederland N.V. Method of debiting an electronic payment means
USD378219S (en) 1995-11-21 1997-02-25 Marshlack Dane G Invoice holder
US5842183A (en) 1995-11-21 1998-11-24 International Billings Services, Inc. Dynamically updated payment due date system
US6058380A (en) 1995-12-08 2000-05-02 Mellon Bank, N.A. System and method for electronically processing invoice information
US5991412A (en) 1995-12-08 1999-11-23 Koninklijke Kpn N.V. Method for protectedly debiting an electronic payment means
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
US5812945A (en) 1995-12-22 1998-09-22 Pitney Bowes Inc. Metered payment cellular telephone communication system
US5740247A (en) 1995-12-22 1998-04-14 Pitney Bowes Inc. Authorized cellular telephone communication payment refill system
US5783808A (en) 1996-01-11 1998-07-21 J. D. Carreker And Associates, Inc. Electronic check presentment system having transaction level reconciliation capability
US5893902A (en) 1996-02-15 1999-04-13 Intelidata Technologies Corp. Voice recognition bill payment system with speaker verification and confirmation
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
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
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
US5987140A (en) 1996-04-26 1999-11-16 Verifone, Inc. System, method and article of manufacture for secure network electronic payment and credit collection
US5715298A (en) 1996-05-16 1998-02-03 Telepay Automated interactive bill payment system using debit cards
US5808723A (en) 1996-05-21 1998-09-15 Eastman Kodak Company Photofinishing system having customized customer order payment feature
US6205433B1 (en) 1996-06-14 2001-03-20 Cybercash, Inc. System and method for multi-currency transactions
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
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
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
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
US6324525B1 (en) 1996-06-17 2001-11-27 Hewlett-Packard Company Settlement of aggregated electronic transactions over a network
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
US5884288A (en) 1996-07-01 1999-03-16 Sun Microsystems, Inc. Method and system for electronic bill payment
US6205435B1 (en) 1996-07-19 2001-03-20 Peter Biffar Self-contained payment system with circulating digital vouchers
US5903880A (en) 1996-07-19 1999-05-11 Biffar; Peter C. Self-contained payment system with circulating digital vouchers
US6047269A (en) 1996-07-19 2000-04-04 Peter Biffar Self-contained payment system with circulating digital vouchers
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
US6085169A (en) 1996-09-04 2000-07-04 Priceline.Com Incorporated Conditional purchase offer management 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
US6058382A (en) 1996-09-12 2000-05-02 Hitachi, Ltd. Electronic money holding device utilizing an automatic payment method
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
US6206285B1 (en) 1996-10-01 2001-03-27 Siemens Nixdorf Informationssysteme Aktiengesellschaft Peripheral assembly kit for the workstation of a goods invoicing system
USD398446S (en) 1996-10-03 1998-09-22 Hosea Darlene L Payment booklet holder
US6029150A (en) 1996-10-04 2000-02-22 Certco, Llc Payment and transactions in electronic commerce system
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
US6021943A (en) 1996-10-09 2000-02-08 Chastain; Robert H. Process for executing payment transactions
US5963925A (en) 1996-10-09 1999-10-05 Visa International Service Association Electronic statement presentment system
US6070150A (en) 1996-10-18 2000-05-30 Microsoft Corporation Electronic bill presentment and payment system
US6115601A (en) 1996-10-23 2000-09-05 U.S. Philips Corporation Payment scheme for a mobile communication service
US20040010463A1 (en) 1996-11-12 2004-01-15 Hahn-Carlson Dean W. Automated transaction processing system and approach
US6138907A (en) 1996-12-02 2000-10-31 Oki Electric Industry Co., Ltd. Electronic transaction processing system and method for operating same
US20010011255A1 (en) 1996-12-13 2001-08-02 Alan Asay Reliance management for electronic transaction system
US6062472A (en) 1996-12-23 2000-05-16 Koninklijke Ptt Nederland N.V. System and method for increasing a value of an electronic payment card including performing a restore transaction in response to interruption of a value increase transaction
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
US5870456A (en) 1997-01-22 1999-02-09 Telepay, Inc. Automated interactive bill payment system using debit cards
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
US6070148A (en) 1997-03-25 2000-05-30 Hitachi, Ltd. Electronic commerce system and method for providing commercial information in electronic commerce system
US6125354A (en) 1997-03-31 2000-09-26 Bellsouth Intellectual Property Corporation System and method for generating an invoice to rebill charges to the elements of an organization
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
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
US6065675A (en) 1997-06-30 2000-05-23 Cardis Enterprise International N.V. Processing system and method for a heterogeneous electronic cash environment
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
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
US6044362A (en) 1997-09-08 2000-03-28 Neely; R. Alan Electronic invoicing and payment system
US5914472A (en) 1997-09-23 1999-06-22 At&T Corp Credit card spending authorization control system
US5883810A (en) 1997-09-24 1999-03-16 Microsoft Corporation Electronic online commerce card with transactionproxy number for online transactions
US6119107A (en) 1997-09-30 2000-09-12 Lockheed Martin Corporation Method and apparatus for payment processing using debit-based electronic funds transfer and disbursement processing using addendum-based electronic data interchange
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
USD406574S (en) 1997-10-06 1999-03-09 Verifone, Inc. Payment instrument
US5970475A (en) 1997-10-10 1999-10-19 Intelisys Electronic Commerce, Llc Electronic procurement system and method for trading partners
US6148405A (en) * 1997-11-10 2000-11-14 Phone.Com, Inc. Method and system for secure lightweight transactions in wireless data networks
US5978780A (en) 1997-11-21 1999-11-02 Craig Michael Watson Integrated bill consolidation, payment aggregation, and settlement system
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
US6052671A (en) 1997-12-03 2000-04-18 Avista Advantage, Inc. Computerized bill consolidation, billing and payment authorization with remote access to the billing information
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
WO1999033016A1 (en) 1997-12-22 1999-07-01 Charles Wong Integrated business-to-business web commerce and business automation system
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
US6304858B1 (en) * 1998-02-13 2001-10-16 Adams, Viner And Mosler, Ltd. Method, system, and computer program product for trading interest rate swaps
US6108644A (en) 1998-02-19 2000-08-22 At&T Corp. System and method for electronic transactions
US6081790A (en) 1998-03-20 2000-06-27 Citibank, N.A. System and method for secure presentment and payment over open networks
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
WO1999056193A2 (en) 1998-04-30 1999-11-04 Ec Cubed, Inc. Method and system for routing data based on a business rule stored in a relational database
US6076074A (en) 1998-05-05 2000-06-13 The Clearing House Service Company L.L.C. System and method for intraday netting payment finality
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
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
US6199107B1 (en) 1998-07-22 2001-03-06 Microsoft Corporation Partial file caching and read range resume system and method
US6012740A (en) 1998-08-03 2000-01-11 Lupi; L. Anthony Combination sample medication payment check and medication prescription device
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
US6169974B1 (en) 1998-10-08 2001-01-02 Paymentech, Inc. Method for closed loop processing of transactions utilizing bank card association
US6135261A (en) 1998-10-23 2000-10-24 Robert E. Noell, Jr. Payment-receiving enclosure for a vending machine
US6185545B1 (en) 1998-11-17 2001-02-06 Prenet Corporation Electronic payment system utilizing intermediary account
US6167385A (en) 1998-11-30 2000-12-26 The Chase Manhattan Bank Supply chain financing system and method
US6173269B1 (en) 1998-12-16 2001-01-09 Zowi.Com, Inc Method and apparatus for executing electronic commercial transactions with minors
US6227447B1 (en) 1999-05-10 2001-05-08 First Usa Bank, Na Cardless payment system
US6721716B1 (en) * 1999-06-17 2004-04-13 Mobius Management Systems, Inc. Payment certification string and related electronic payment system and method
WO2001033522A1 (en) 1999-11-05 2001-05-10 American Express Travel Related Services Company, Inc. Systems and methods for facilitating commercial transactions between parties residing at remote locations
US20070106604A1 (en) * 2000-01-28 2007-05-10 Fundamo (Proprietary) Limited System for conducting commercial transactions
WO2001057770A1 (en) 2000-02-04 2001-08-09 Kuo James S Process and method for secure online transactions with calculated risk
US20020038277A1 (en) * 2000-02-22 2002-03-28 Yuan Frank S. Innovative financing method and system therefor
US20010047273A1 (en) 2000-03-17 2001-11-29 Greer Edward Cooper Electronic transaction clearing system
US20070174191A1 (en) * 2000-09-05 2007-07-26 Keaton G D Factoring system and method
US20040015436A1 (en) * 2000-09-06 2004-01-22 Norman Understein Interbank process
US20020095355A1 (en) * 2001-01-18 2002-07-18 Doreen A. Labit Computer-implemented international trade system
US20030130959A1 (en) 2001-02-15 2003-07-10 Walter Rosenbaum Closed loop electronic factoring
WO2003038553A2 (en) 2001-10-29 2003-05-08 Visa International Service Association Method and system for conducting a commercial transaction between a buyer and a seller
US20030093367A1 (en) * 2001-11-15 2003-05-15 First Data Corporation Online incremental payment method
US20030126075A1 (en) * 2001-11-15 2003-07-03 First Data Corporation Online funds transfer method
US20040078328A1 (en) * 2002-02-07 2004-04-22 Talbert Vincent W. Method and system for completing a transaction between a customer and a merchant
KR20030070348A (en) * 2002-02-25 2003-08-30 (주)베스텍컴 payment system using a credit card for trade and method thereof
US20040128240A1 (en) * 2002-10-07 2004-07-01 Yusin Wendy E. Method and system for managing financial transactions
US20040088245A1 (en) * 2002-11-04 2004-05-06 Manoj Narayan Systems and methods for producing documentary credit and conforming shipping documents
US20050027654A1 (en) * 2003-07-28 2005-02-03 Adrian Alexandra J. System and method for a business payment connection
US20050144130A1 (en) * 2003-12-31 2005-06-30 Staniar Jud C. Method and apparatus for automatically processing invoiced payments with selectable payment terms
US20050283432A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing buyer bank payable discounting aggregation services
US20050283416A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing assurance and financing services
US20050283431A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing seller bank receivable discounting aggregation services
US20050283430A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing buyer bank payable discounting services
US20050283433A1 (en) * 2004-06-17 2005-12-22 Visa International Service Association Method and system for providing seller bank receivable discounting services
US20080010194A1 (en) * 2006-07-10 2008-01-10 Automated Payment Highway, Inc. Method and apparatus for financing community expenses

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
U.S. Appl. No. 10/020,466, Vaux et al.
U.S. Appl. No. 11/034,667, Reid et al.
U.S. Appl. No. 11/131,602, Reid et al.
U.S. Appl. No. 11/131,605, Reid et al.
U.S. Appl. No. 11/132,067, Reid et al.
U.S. Appl. No. 11/132,102, Reid et al.
US 5,351,994, 10/1994, Pollin (withdrawn)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150081522A1 (en) * 2013-08-01 2015-03-19 Fundbox, Ltd. System and method for automatically providing a/r-based lines of credit to businesses
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
US10430760B2 (en) 2015-11-24 2019-10-01 Bank Of America Corporation Enhancing communications based on physical trade documents

Also Published As

Publication number Publication date
US20050283431A1 (en) 2005-12-22
US20050283433A1 (en) 2005-12-22
US8571978B2 (en) 2013-10-29
US8606697B2 (en) 2013-12-10
US8571977B2 (en) 2013-10-29
US20050283416A1 (en) 2005-12-22
CN101019109A (en) 2007-08-15
US20050283430A1 (en) 2005-12-22
US20050283432A1 (en) 2005-12-22

Similar Documents

Publication Publication Date Title
US8566231B2 (en) Method and system for providing buyer bank payable discounting aggregation services
US11741513B2 (en) Supply chain finance system
AU2009200961B2 (en) Method and system for conducting a commercial transaction between a buyer and a seller
CA2483348C (en) System and method for varying electronic settlements between buyers and suppliers with dynamic discount terms
US8458086B2 (en) Allocating partial payment of a transaction amount using an allocation rule
US20070156584A1 (en) Supply Chain Financing Systems and Methods
US20070282744A1 (en) Supply chain financing and credit memo systems and methods
US20080249934A1 (en) Computer-based payment transaction system and repository
AU2002340294A1 (en) Method and system for conducting a commercial transaction between a buyer and a seller
EP1782254A2 (en) Method and system for providing assurance and financing services

Legal Events

Date Code Title Description
AS Assignment

Owner name: VISA INTERNATIONAL SERVICE ASSOCATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:REID, WILLIAM;SWACKHAMMER, CRAIG;LYNCH, KERRY;AND OTHERS;SIGNING DATES FROM 20050412 TO 20050418;REEL/FRAME:016582/0664

Owner name: VISA INTERNATIONAL SERVICE ASSOCATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:REID, WILLIAM;SWACKHAMMER, CRAIG;LYNCH, KERRY;AND OTHERS;REEL/FRAME:016582/0664;SIGNING DATES FROM 20050412 TO 20050418

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8