USRE41619E1 - System and method for multicurrency transactions - Google Patents

System and method for multicurrency transactions Download PDF

Info

Publication number
USRE41619E1
USRE41619E1 US10/390,540 US39054003A USRE41619E US RE41619 E1 USRE41619 E1 US RE41619E1 US 39054003 A US39054003 A US 39054003A US RE41619 E USRE41619 E US RE41619E
Authority
US
United States
Prior art keywords
currency
customer
merchant
server
balance
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.)
Expired - Lifetime
Application number
US10/390,540
Inventor
Brian Paul Boesch
Stephen David Crocker
Donald Eggleston Eastlake, III
Alden Sherburne Hart, Jr.
Andrew Jackson
Robert A. Lindenberg
Denise Marie Paredes
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.)
PayPal International Ltd
PayPal Inc
Original Assignee
PayPal International Ltd
PayPal Inc
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 PayPal International Ltd, PayPal Inc filed Critical PayPal International Ltd
Priority to US10/390,540 priority Critical patent/USRE41619E1/en
Assigned to PAYPAL, INC., PAYPAL INTERNATIONAL LIMITED reassignment PAYPAL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VERISIGN, INC.
Assigned to PAYPAL, INC., PAYPAL INTERNATIONAL LIMITED reassignment PAYPAL, INC. CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR AND ASSIGNEE NAMES PREVIOUSLY RECORDED ON REEL 019019 FRAME 0170. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT FROM VERISIGN, INC. TO PAYPAL, INC. AND PAYPAL INTERNATIONAL LIMITED. Assignors: VERISIGN, INC.
Priority to US12/855,603 priority patent/USRE44502E1/en
Application granted granted Critical
Publication of USRE41619E1 publication Critical patent/USRE41619E1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

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/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • 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
    • 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
    • G06Q20/108Remote banking, e.g. home banking
    • 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
    • G06Q20/108Remote banking, e.g. home banking
    • G06Q20/1085Remote banking, e.g. home banking involving automatic teller machines [ATMs]
    • 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/12Payment architectures specially adapted for electronic shopping 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
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/381Currency conversion
    • 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
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0633Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635Processing of requisition or of purchase orders
    • G06Q30/0637Approvals
    • 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
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0641Shopping interfaces
    • 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/03Credit; Loans; Processing thereof
    • 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/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • the present invention generally relates to a system and method for approving a transaction over a communications network between a merchant and a customer. More specifically, the present invention is directed to a system and method for approving a transaction between a merchant and a customer, wherein the transaction occurs over an electronic network (such as the Internet) and wherein the customer pays for a product using electronic cash in one currency and the merchant receives electronic cash for the product in a different currency.
  • an electronic network such as the Internet
  • currency includes, but is not limited to, denominations of script and coin that are issued by government authorities as a medium of exchange.
  • a “currency” also may include a privately issued token that can be exchanged for another privately issued token or government script.
  • a company might create tokens in various denominations. This company issued “money” could be used by employees to purchase goods from merchants. In this case, an exchange rate might be provided to convert the company currency into currencies which are acceptable to merchants.
  • currency conversion represents a significant economic risk to both buyers and sellers in international commerce. For example, assume a customer desires to buy a product from a merchant. Further consider the scenario where the customer pays his credit card bills in U.S. dollars and the merchant only accepts French francs for the products he sells. The customer uses his credit card to pay the merchant for the product. The merchant receives French francs.
  • the company issuing the credit card would bill an amount to the customer in U.S. dollars.
  • the amount billed to the customer is determined by an exchange rate used at the time the credit card company settles the transaction. This settlement is often at an indeterminate time and could be on the date of purchase or several days or weeks later. The time of this settlement is at the credit card company's discretion.
  • the risk to the credit card company is minimal because the credit card company can settle the transaction when exchange rates are favorable. Thus, in this case, it is the customer who bears the risk that the value of the customer's currency will decline prior to this settlement.
  • the described post sale methods of currency exchange may impart significant risk upon the customer and the merchant.
  • Risk is typically on the side of whoever commits to the currency conversion.
  • the customer bears the risk when currency is converted prior to purchasing a product.
  • the merchant sustains the risk when he converts the customer's currency into his own currency.
  • the cost of currency conversion may be greater than the currency is worth.
  • the individual desires to purchase an item in a third currency which differs from the native and second currencies, he must undertake at least one additional currency conversion (converting either his native currency to the third currency, the second currency to the third currency, or a combination of both). In this case, the customer assumes an additional risk.
  • the present invention recognizes that international commerce over electronic networks, such as the Internet, cannot reach potential unless customer and merchant obligations relating to transactions are fixed at the time of the transaction so that the risk to these parties associated with currency exchange is minimized.
  • a system and method that offers a means of eliminating the uncertainty associated with multi-currency transactions.
  • One aspect of the present invention is the shift of the risk associated with currency exchange from both the merchant and customer to a third party (e.g., a server) in real time. This server may assume the risk itself or may choose to subsequently pass on the risk to a fourth party (e.g., a bank or other financial institution).
  • the present invention is directed to a system for determining approval of a transaction between a merchant and a customer.
  • the system comprises a customer device (e.g., a computer) associated with the customer.
  • the customer device has a first set of data including an amount in a first currency.
  • the system also has a merchant device (e.g., a computer) associated with the merchant.
  • the merchant device has a second set of data including a product price in a second currency.
  • the system further has a server device connected to both the customer device and the merchant device for receiving the first and second sets of data and for approving the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
  • Another aspect of the present invention is directed to a system for determining approval of a transaction between a customer and a merchant where the product price is known by the customer.
  • the transaction includes the merchant providing a product price in a second currency.
  • the system comprises a customer device (e.g., a computer) associated with the customer.
  • the customer device has a first set of data including an amount in a first currency.
  • the system also includes a server connected to the customer device. The server is able to access the product price in the second currency, receive the first set of data from the customer device, and can approve the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
  • Still another aspect of the present invention is directed to a method for determining approval of a transaction between a customer having a customer device (e.g., a computer) and a merchant having a merchant device (e.g., a computer).
  • the customer device and the merchant device are connected to a server.
  • the customer device has a first set of data including an amount in a first currency.
  • the method comprises transmitting a second set of data from the merchant device to the customer device which receives the second set of data from the merchant device.
  • the second set of data includes the product price in a second currency.
  • the method further includes transmitting the first and the second sets of data by the customer device to the server and the server receiving the transmitted first and second sets of data.
  • the server is for approving the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
  • FIG. 1 is a diagrammatic representation of one aspect of the present invention.
  • FIG. 2 is a diagrammatic representation of another aspect of the present invention.
  • FIG. 1 shows three entities: a server 100 , a customer computer 200 , and a merchant computer 300 , connected to each other via a network 50 .
  • Network 50 can be a private, public, secure, or an insecure network, such as the Internet, an intranet, and/or a Local Area Network (LAN).
  • an insecure network such as, the Internet is used.
  • the connections to network 50 are identified by lines 105 , 205 , and 305 , respectively, and are well known in the art.
  • Merchant computer 300 represents the computer of an individual, for example, merchant user 303 , who sells products via network 50 .
  • a “product” can include goods, services, information, data, and the like.
  • Customer computer 200 represents the computer of an individual, for example, a customer user 203 , who wants to buy a product (or products) from merchant user 303 over network 50 .
  • the mechanism of delivery of the product is not a part of this patent. Product delivery could be coincident with payment, before payment, or after payment.
  • Server 100 represents a computer of an entity who processes transactions between customer user 203 and merchant user 303 .
  • Server 100 has a database which includes at least one customer account in a first currency associated with customer user 203 and at least one merchant account in a second currency associated with merchant user 303 .
  • the first currency differs from the second currency.
  • the accounts store electronic funds of the parties, for example, electronic cash.
  • the electronic funds are a representation of funds (real cash, credit, and the like).
  • Server 100 also has its own server accounts.
  • the server accounts are in currencies corresponding to the currencies of the customer and merchant accounts.
  • the server accounts represent real cash, credit, and the like.
  • the server accounts correspond to the electronic funds stored in the customer and merchant accounts.
  • local accounts are maintained at customer computer 200 and merchant computer 300 .
  • the local accounts represent the electronic funds in the customer account and the merchant account maintained at server 100 , respectively.
  • the local accounts of the customer and the merchant are sometimes referred in the art as “wallets” and “cash registers,” respectively.
  • the server accounts may be arranged with a bank or other financial institution.
  • Server 100 includes a customer account in U.S. dollars and a merchant account in French francs.
  • Server 100 which processes the transactions between these parties, further includes two electronic accounts representing all user accounts whose currencies are in dollars and all user accounts whose currencies are in francs.
  • Server 100 also includes two accounts in a bank with one server account in U.S. dollars and the other server account in French francs.
  • a session is an opportunity (or window) in which customer user 203 may purchase a product from merchant user 303 over the network 50 or which merchant user 303 sells a product to customer user 203 over network 50 .
  • a merchant can securely communicate with a customer over an insecure network.
  • Customer user 203 and merchant user 303 each have their own independent sessions. Sessions are of limited duration which is governed by predetermined parameters. In the preferred embodiment, these parameters are set by customer user 203 and merchant user 303 . However, server 100 can set or limit values of such parameters.
  • the parameters relating to the session of customer user 203 limit an amount of electronic funds (“session amount”), a maximum amount of time that the session can last, and a maximum number of transactions that can be conducted.
  • the session amount is the maximum amount of electronic funds that customer user 203 can spend during the customer's session.
  • the session of merchant user 303 is limited by a maximum amount of time that the merchant's session can last and a maximum number of transactions that merchant user 303 can conduct.
  • a first session associated with customer user 203 is created.
  • the first session has first use parameters for limiting the duration that the first session can be used and a set of customer data.
  • the first use parameters and the set of customer data are identifiable by server 100 .
  • a second session associated with merchant user 303 is also created.
  • the second session has second use parameters for limiting the duration that the second session can be used and a set of merchant data.
  • the second use parameters and the set of merchant data are identifiable by server 100 .
  • Over the insecure network a portion of the first session and a portion of the second session are linked.
  • the portion of the first session includes the set of customer data and the first use parameters.
  • the set of customer data may include a customer identification string which identifies customer user 203 .
  • the portion of the second session includes the set of merchant data and the second use parameters.
  • the set of merchant data may include a merchant identification string which identifies merchant user 303 .
  • Server 100 verifies customer user 203 and merchant user 303 based upon at least portions of the set of customer data and the set of merchant data and determines that the first and second sessions can be used. In this manner, confidential details of the payment between customer user 203 and merchant user 303 are assured of being communicated securely.
  • This procedure of establishing secure communication is more fully set forth in co-pending U.S. patent application, Ser. No. 08/572,425, filed on Dec. 14, 1995, and entitled “Electronic Transfer and Method” which is incorporated herein by reference. Of course, other methods and systems for establishing secure communication over an insecure network may be used to use the invention set forth herein.
  • Merchant user 303 and customer user 203 endeavor ultimately to effect a “transaction,” that is, the purchase of a product by customer user 203 from merchant user 303 .
  • Merchant user 303 and customer user 203 do not require any prior existing relationship to transact business. This is so because merchant user 303 and customer user 203 each have a preestablished relationship with server 100 prior to transacting business.
  • customer user 203 provides information using customer computer 200 to server 100 .
  • Such information can include the name of customer user 203 and the currency in which he intends to purchase products.
  • this information can include the name of merchant user 303 and the currency in which merchant user 303 intends to ultimately receive for providing products.
  • Other information can be provided as deemed necessary by server 100 .
  • This relationship may be either direct or indirect.
  • An indirect relationship would include the situation where one or more entities, previously known to server 100 , vouch for merchant user 303 and/or customer user 203 .
  • Public key cryptographic systems are generally used in this type of vouching process and are well known to those skilled in the art.
  • the process of using public key cryptographic systems as such is known in the art as “certificate management.”
  • vouching entities are known as “certificate authorities.” Certificates, certificate management, and certificate authorities are well known in the art and are used by but are not the subject of the present invention.
  • the present invention is directed toward “approval” of a multi-currency transaction in which customer user 203 pays in a first currency and merchant user 303 accepts the payment in a second currency which differs from the first currency, rather than the completed transaction itself.
  • approval commits customer user 203 and merchant user 303 to the terms of the transaction and commits server 100 to perform virtual settlement of the transaction.
  • “virtual settlement” of the transaction represents at least the movement of electronic funds to a merchant account of merchant user 303 held by server 100 . It can also represent the movement of electronic funds from a customer account of customer user 203 held by server 100 . This is to be distinguished from actual settlement of the transaction.
  • “actual settlement” of the transaction includes at least converting real funds in an amount equal to the amount in the first currency into real funds in the second currency.
  • the parties are committed because of pre-existing bilateral contractual obligation between customer user 203 and the operator of server 100 and between merchant user 303 and the operator of server 100 .
  • the contractual obligations are preferably formed during the commencement of service relationship between server 100 and customer user 203 and merchant user 303 respectively.
  • the obligations can include the agreement of customer user 203 and merchant user 303 to permit server 100 to perform virtual settlement of the transaction.
  • server 100 can agree to incur the risks associated with currency exchange when it performs actual settlement of the transaction.
  • customer user 203 and merchant user 303 agree to allow server 100 (on behalf of the operator of server 100 ) to maintain accounts and balances of funds managed by server 100 .
  • the movement of funds between those accounts is coincident with the transaction.
  • customer user 203 knows substantially the amount in the currency customer user 203 will pay for the product.
  • merchant user 303 knows substantially the price in the currency merchant user 303 will receive for the product.
  • Customer user 203 and merchant user 303 do not bear the above-described risks associated with currency exchange.
  • the amount customer user 203 knows and the price merchant user 303 knows is substantially the respective amount and price because there may be minor factors that affect these actual values. Such factors will be discussed in terms of risk factors.
  • the entity charged with performing actual settlement of the transaction bears such risks when the transaction is actually settled.
  • the present invention is directed to approval of multi-currency transactions in which customer user 203 pays in one currency and merchant user 303 accepts the payment in another currency.
  • customer user 203 shops over network 50 among merchant users 303 who also have been permitted by server 100 to transact business (which may be, for example, those who have merchant sessions).
  • server 100 to transact business (which may be, for example, those who have merchant sessions).
  • customer user 203 and a merchant user 303 agree on a product to be purchased at a particular price and in a particular currency.
  • merchant user 303 will accept a price and receive payment for the product sold to customer user 203 .
  • the price for the product is in a currency accepted by merchant user 303 , referenced herein as the “product price in the second currency.”
  • Customer user 203 will pay an amount to merchant user 303 for a selected product.
  • the amount will be paid in a currency selected by customer user 203 , referenced herein as the “amount in the first currency.”
  • the currency (second) selected by merchant user 303 is different than the currency (first) selected by customer user 203 .
  • currency exchange is used to approve the transaction contemplated by the present invention.
  • server 100 is used to approve the transaction between customer user 203 and merchant user 303 . As stated previously, approval commits customer user 203 and merchant user 303 to the terms of the transaction and commits server 100 to perform virtual settlement of the transaction.
  • customer user 203 and merchant user 303 have established and agreed upon a product to be purchased at a price merchant user 303 will accept.
  • This product and price are referred to herein as the “agreed product” and the “agreed price,” respectively.
  • customer computer 200 transmits a first set of data to server 100 .
  • This first set of data includes the amount in a first currency that customer user 203 is willing to pay for the agreed product.
  • the transmitted amount is in the customer selected currency which is in a first currency.
  • Other information may be transmitted by customer computer 200 as needed by server 100 , for example, a requested payment range (described later), information identifying customer user 203 , the product to be purchased, account information, and the like.
  • merchant computer 300 transmits a second set of data to server 100 .
  • This second set of data includes the agreed price in a second currency that merchant user 303 is willing to receive for his product.
  • the transmitted agreed price is in the merchant accepted currency which is in a second currency.
  • Other information may be transmitted by the merchant computer 300 as needed by server 100 , for example, information identifying merchant user 303 , the product to be purchased, account information, and the like.
  • the customer selected currency (first currency) is different than the merchant accepted currency (second currency).
  • customer computer 200 along with providing the amount in the first currency, customer computer 200 also transmits the agreed price in the second currency to server 100 . This assures that customer user 203 and merchant user 303 have actually reached agreement on the terms of the transaction and precludes either party from denying such agreement.
  • the system does not require that merchant user 303 know or approve the customer selected currency, that is, the currency in which customer user 203 will pay. There is no requirement that customer user 203 approve the merchant accepted currency, that is, the currency which merchant user 303 will receive. What is required is that server 100 be able to convert one such currency into the other.
  • the first and second sets of data transmitted to server 100 need not come directly from customer computer 200 and merchant computer 300 .
  • This information may be transmitted via alternative routes.
  • customer computer 200 transmits the first set of data to the merchant computer 300 .
  • merchant computer 300 Upon receipt of the first set of data, merchant computer 300 transmits at least the amount in the first currency and the second set of data including the product price in the second currency to server 100 for approval of the transaction.
  • the first set of data may be protected to prevent the merchant from altering it.
  • server 100 can approve the transaction.
  • the approval process performed by server 100 is based upon the relative value of the amount in the first currency in terms of the product price in the second currency.
  • This relative value may be established by the operator of server 100 , a third party, or in other aspects of the present invention, customer user 203 or merchant user 303 .
  • This preferably includes a rate of exchange at which the amount in the first currency can be converted into a converted amount in the second currency.
  • this information may include a rate at which the merchant accepted currency can be converted into the customer selected currency.
  • Approval of the transaction occurs when the amount in the first currency is sufficient to pay merchant user 303 the product price in the second currency.
  • the sufficiency determination process preferably includes converting the amount in the first currency into a converted amount in the second currency, referenced herein as the “converted amount in the second currency,” using a current exchange rate.
  • the frequency that the current exchange rate data is updated depends upon the level of risk that the approving entity may be willing to accept and the availability of updates from currency brokerage services.
  • server 100 when server 100 is the approving entity, server 100 receives updates to the exchange rate data on-line from one or more currency brokers. Frequency and timing of updates are based on business rules agreed between the operator of server 100 and the currency broker or brokers. This manages the risk of a significant change between the current exchange rate and the exchange rate used when the transaction is actually settled.
  • Approval of the transaction by server 100 is preferably based upon predetermined criteria. These criteria may be established by any of the parties to the transaction or a third party. For example, in the preferred embodiment server 100 approves the transaction if the converted amount in the second currency equals or exceeds the product price in the second currency.
  • server 100 could approve the transaction if the converted amount in the second currency is less than the product price in the second currency.
  • server 100 may absorb differentials (as where the cost associated with disapproving the transaction and reprocessing it exceeds the differential). Acceptable differentials may be dependent upon the credit worthiness of customer user 203 or merchant user 303 , the acceptable deficit balance that customer user 203 or merchant user 303 are allowed to incur, or other market conditions such as, for example, fluctuations in exchange rates. These acceptable differentials are referred to with respect to each party of the transaction as a “risk range.”
  • server 100 could record the differentials as they occur and collect them from customer user 203 at a later time.
  • This range is contemplated as being a small range and is referred to herein as the “payment range.”
  • the payment range may be predetermined by customer user 203 or preferably, by server 100 .
  • the amount in the first currency is equal to the amount in the first currency plus or minus the payment range. The payment range thus defines the amount of conversion error permitted in the transaction.
  • Approval of the transaction may also be contingent upon customer user 203 having access to electronic funds in an amount equal to or exceeding the amount in the customer selected currency (ACSC). These funds maybe stored or represented in a customer account associated with customer user 203 .
  • server 100 approves the transaction when the converted amount in the second currency meets the predetermined criteria described above and the customer account contains electronic funds in an amount at least equal to the amount in the first currency. Using any of the above methods for approval, alone or in combination, server 100 approves the transaction.
  • the session amount is an amount known by server 100 to which the customer has access when customer user 203 is permitted to shop.
  • the limited amount is reduced as customer user 203 purchases products over network 50 .
  • Customer computer 200 temporarily prohibits customer user 203 from transmitting an amount exceeding the session amount to server 100 to be considered for sufficiency until more electronic funds are added to the session in which case the session amount has been increased.
  • the existing session will automatically close and a new session will be opened with funds at least sufficient to complete the transaction.
  • the transaction may be approved.
  • server 100 determines that customer user 203 does not have enough funds available to it to open a subsequent session of sufficient value, the transaction may be refused by server 100 altogether or server 100 may approve the transaction as described herein.
  • the funds that are available to customer user 203 during the session and the funds received by merchant user 303 during the session be maintained to two decimal positions to the right of the minor unit of a currency.
  • the present invention preferably would carry the value of session funds to one hundredth of a penny to assure that rounding errors are minimized during a session, thus decreasing rounding errors during currency conversion of small transactions.
  • the balance in the session is adjusted to whole minor currency units (this adjustment may be rounding or truncation).
  • customer user 203 and merchant user 303 are committed to the terms of the transaction. Specifically, customer user 203 is committed to pay the amount in the first currency. Similarly, merchant user 303 is committed to accept the product price in the second currency for the product. The parties are committed as such through the contractual arrangement previously described.
  • server 100 is committed to perform virtual settlement of the transaction. Therefore, according to this aspect of the present invention, a customer account may be maintained for customer user 203 and a merchant account may be maintained for merchant user 303 .
  • the customer accounts and merchant accounts are preferably maintained by server 100 . However, one or both of the accounts may be maintained by a party other than server 100 .
  • the customer account and merchant account maybe debit or credit accounts.
  • the customer account is a debit account and the merchant account is a credit account and each such account represent funds in the form of electronic funds.
  • other types of accounts may be used as known by those skilled in the art.
  • server 100 may transmit data to the party to enable virtual settlement. For example, if the other party maintains the customer account and the merchant account, server 100 may transmit data identifying the customer account and the amount in the first currency to be debited, and the merchant account and the product price in the second currency to be credited. Then, the party would debit the customer account and credit the merchant account accordingly.
  • the customer account upon approval of the transaction, the customer account is debited by the amount in the first currency.
  • the merchant account is credited with the agreed price in the second currency. This amount and price were known by and agreed to by customer user 203 and merchant user 303 . Thus, there is ho uncertainty as to the amount or currency to be paid by customer user 203 or the price or currency to be received by merchant user 303 .
  • the currency used in the first currency may be selected by customer user 203 (or server 100 ) from a plurality of currencies, referred to herein as “customer currencies.”
  • the currency used in the merchant accepted currency may be selected by customer user 203 from a plurality of currencies, referred to herein as “merchant currencies.” A description of these variations is now provided.
  • a customer user 203 may have access to amounts in a plurality of customer currencies.
  • a customer user 203 may have accounts containing amounts in U.S. dollars, French francs, and Japanese yen.
  • Customer user 203 can purchase products using amounts from any of these accounts.
  • customer computer 200 presents an amount in each of the plurality of customer currencies to customer user 203 . This is done using exchange rate data for each customer currency to convert the merchant accepted currency into amounts in each of the customer currencies.
  • the exchange rate data is provided to customer computer 200 by server 100 at various times. Other mechanisms for obtaining such data include the use of brokers.
  • Customer user 203 selects an amount in one of the plurality of customer currencies in which the customer user 203 will spend for the product. This selected amount represents the amount in the first currency described previously and is referred herein as the “selected currency.”
  • customer computer 200 determines the amount of customer currency to pay for a purchase in the merchant computer 300 's currency. While there are a number of ways to enable this conversion, in the preferred embodiment, prior to the inception of the customer computer 200 's session, customer computer 200 requests exchange rate data. This data will contain at least conversion rates from the session currency to other convertible currencies, it may also contain additional data such as anticipated expiration of the exchange rates. These rates are used by customer computer 200 to estimate the amount of customer currency to pay for a purchase in merchant currency. As conversion rates may change rapidly, in the preferred embodiment, this data is advisory only. Server 100 can send updated data to customer computer 200 during any communication between them. The implication of this decision is that if customer computer 200 pays insufficient funds to convert, it is viewed as a natural error due to obsolete data, not an attempt to defraud.
  • This aspect of the present invention can further include an optimization feature.
  • the optimization feature is preferably executed by customer computer 200 to determine whether it is advantageous for customer user 203 to pay in one customer currency over another.
  • customer computer 200 determines the agreed price in the merchant accepted currency corresponding to the amount in each of the plurality of customer currencies. For example, assume merchant user 303 will receive a price in currency C for the product and customer user 203 has two customer currencies A and B available to pay merchant user 303 . Customer computer 200 determines amounts in currencies A and B which equate to the product price in currency C. These amounts may be compared by converting them to a reference currency of the customer computer 200 's choice. Customer user 203 can choose (or customer computer 200 can be programmed to choose) to pay the agreed price in the currency (A or B) which corresponds to the lesser amount in the reference currency. The amount in the chosen currency represents the amount in the first currency and is referred herein as the “selected currency.”
  • customer computer 200 can also determine whether it is less expensive to first convert currency A into currency B, and then to convert currency B into currency C. In any case, customer user 203 pays using the optimal payment currency. This preferred mode reduces complexity of currency exchange to customer user 203 without reducing the options available to customer user 203 .
  • server 100 can execute an optimization feature.
  • server 100 may include the plurality of customer currencies available to customer user 203 .
  • data indicating the plurality of customer currencies may be transmitted in the first set of data from customer computer 200 to server 100 in lieu of the amount in the first currency.
  • server 100 determines the agreed amount in the second currency for each of the plurality of customer currencies.
  • Server 100 then chooses an amount in one of the customer currencies corresponding to the amount in the merchant accepted currency which is the least when converted to the reference currency. The amount in the chosen currency represents the amount in the first currency.
  • a merchant user 303 may desire to transact business in more than one currency. Therefore, merchant user 303 will accept a price for the product in one of a plurality of merchant currencies.
  • Merchant computer 300 communicates the agreed price for the product in each of the merchant currencies to customer computer 200 .
  • Customer computer 200 presents the agreed price in each of the merchant currencies to customer user 203 .
  • Customer user 203 selects the agreed price in one of the merchant currencies that merchant user 303 will accept. This selected currency maybe recommended by the optimization procedure described above. This selected price represents the product price in the merchant accepted currency (PMAC), although it is actually selected by customer user 203 .
  • PMAC merchant accepted currency
  • customer computer 200 may also determine which customer currency - merchant currency pair represents the best value to customer user 203 . This is accomplished by customer computer 200 using exchange rate data to convert the price of the product in each merchant accepted currency into each of the customer currencies and selecting the lowest value among the results. For example, if customer user 203 has access to currencies A, B, C and merchant user 203 is willing to accept currencies y and z, customer computer 200 will determine the cost of the products as quoted in merchant accepted currencies y and z in terms of customer accepted currency A. Whichever of these conversions yields the lowest cost to customer user 203 is the optimal customer currency merchant currency pair for customer currency A. This process is repeated until an optimal currency pair is computed for each customer currency. For example, this process may yield the following results: A to y, B to y, and C to z.
  • the next step is to decide which of these currency pairs represents the best value to customer user 203 .
  • this is accomplished by converting each customer currency to a single reference currency. The conversion that yields the smaller number is identified as the “best” choice and is displayed to customer user 203 .
  • Other approaches to determining the optimum currency can be devised by those skilled in the art.
  • FIG. 2 Another embodiment of the present invention, as shown in FIG. 2 , again uses server 100 to approve the transaction between customer user 203 and merchant user 303 .
  • the merchant computer need not be connected to network 50 according to this aspect of the invention.
  • customer user 203 has knowledge about the product that merchant user 303 is providing and the price in the merchant selected currency for the product before submitting the first set of data to server 100 .
  • This knowledge need not be gained while customer user 203 shops over network 50 .
  • merchant user 303 can have distributed catalogs to customer user 203 (via regular mail, email, etc.) illustrating products, prices, and currencies therefor.
  • Server 100 would receive the same information, that is, data representing the same products, prices and currencies from merchant user 303 .
  • This data may be received by server 100 electronically over network 50 or by some other means.
  • merchant user 303 might provide the data representing the products, prices and currencies therefor via a network to which customer computer 200 is not connected or by mail on a diskette. However received, this data would be accessible by server 100 .
  • customer user 203 may purchase a product over network 50 .
  • customer computer 200 transmits to server 100 a description of a desired product (e.g., model number) and an amount in the first currency for the desired product.
  • Server 100 thus has access to data indicating the amount in the first currency which customer user 203 is willing to pay for a product and the product price in the second currency which merchant user 303 is willing to accept for the product. With this data, server 100 approves the transaction as indicated above.
  • notice of approval of the transaction may be provided by server 100 to customer user 203 and merchant user 303
  • server 100 may transmit data indicating approval to the merchant computer 300 .
  • merchant computer 300 may transmit at least a portion of the data indicating approval to customer computer 200 .
  • data indicating approval may be communicated from server 100 to customer computer 200 , which, in turn, would forward this data to merchant computer 300 . In this manner, customer user 203 and merchant user 303 may be informed that the transaction was approved.
  • server 100 may separately transmit data indicating approval to customer computer 200 and merchant computer 300 .
  • the absence of notice from server 100 maybe deemed as affirmative notice that the transaction was approved. According to any of these procedures, or other preestablished procedures, notice may be provided to the participants in the transaction. Further, once notice of approval is provided, the product which is the subject of the transaction may be provided to customer user 203 and the payment of the funds corresponding to the agreed price will be received by merchant user 303 in the merchant accepted currency.
  • Actual settlement may occur contemporaneously with the approval of the transaction or it may be deferred. As is described below, it is the entity charged with performing the actual settlement who bears the risk.
  • server 100 performs actual settlement of the transaction. Therefore, according to this aspect of the present invention, server 100 also has its own server accounts. Server accounts are in currencies corresponding to the currencies of the customer and merchant accounts. Server accounts represent real cash, credit, and the like, corresponding to the electronic funds stored in the customer and merchant accounts.
  • server 100 may transmit data to a currency broker, bank or financial institution to enable actual settlement.
  • server 100 may transmit data identifying server account and the amount in the first currency so that the entity can convert real funds in an amount equal to the amount in the customer selected currency into real funds in the second currency.
  • server 100 aggregates the amounts in each currency before settling. This may decrease the number of actual conversions that must be made from possibly hundreds per second to a few times per hour (or day). The frequency may vary depending on the volatility of the currency exchange market and on the relative currency balances in server 100 's various currency accounts.
  • server 100 is bound even if the later currency exchange rates are or become unfavorable to server 100 as compared to the current exchange rates used during the virtual settlement. By eliminating the risk to customer user 203 and merchant user 303 , such risk is passed to server 100 .
  • measures are taken to manage the risk associated with the currency exchange to server 100 .
  • server 100 can have a preestablished agreement with the bank or financial institution.
  • the terms of such an agreement might include a commitment on the part of server 100 to settle transactions within a predetermined amount, time, and/or within a predetermined currency rate deviation.
  • the predetermined amount of time may be on the order of several seconds or minutes.
  • server 100 aggregates transactions and submits them in batch for exchange.
  • the entity may offer server 100 a favorable currency exchange rate.
  • the parties to a multi-currency transaction authorize an approving entity to settle the transaction.
  • Authorization is granted by virtue of customer user 203 and merchant user 303 setting up their respective accounts, knowing that transactions will be submitted and processed.
  • the parties transmit data representing the transaction to the approving authority. This data includes an amount in a first currency that a customer user 203 is willing to pay for a product and a product price in a different second currency which a merchant user 303 is willing to accept for the product.
  • the approving entity approves the transaction.
  • the approving entity may actually settle the transaction at its discretion thereby bearing the risk associated with currency exchange.
  • the parties incur no risk.
  • Customer user 203 will pay the amount in the first currency and merchant user 303 will receive the product price in the second currency.
  • server 100 may choose to withdraw a currency or currencies from the list of convertible currencies.

Abstract

A system and method for determining approval of a multi-currency transaction between a customer and a merchant over a network. The system includes a customer computer which is connected to a communication network, a merchant computer which is connected to the communication network, and a server connected to both the customer computer via the communication network and to the merchant computer via the communication network. The customer computer includes a first set of data which contains an amount the customer is willing to pay the merchant for a product in a first currency. The merchant computer includes a second set of data which contains a product price at which the merchant agrees to sell the product in a second currency. The server receives the first set of data and the second set of data. The server then converts the amount in the first currency into a converted amount in the second currency. The server approves the transaction if the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates. Once the transaction is approved, the approving entity may settle the transaction at its discretion thereby bearing the risk associated with currency exchange. The parties, however, incur no risk. The customer will pay the amount in the first currency and the merchant will receive the price in the second currency. These are values known and agreed to by the parties at the time of the transaction.

Description

This application is a continuation of patent application Ser. No. 08/663,896, filed Jun. 14, 1996, now allowed, the disclosure of which is incorporated by reference herein, in its entirety.
BACKGROUND OF THE INVENTION
1. Field of Invention
The present invention generally relates to a system and method for approving a transaction over a communications network between a merchant and a customer. More specifically, the present invention is directed to a system and method for approving a transaction between a merchant and a customer, wherein the transaction occurs over an electronic network (such as the Internet) and wherein the customer pays for a product using electronic cash in one currency and the merchant receives electronic cash for the product in a different currency.
2. Description of the Prior Art
Soon, international commerce may be a common experience for almost everyone. This is due, in large measure, to computer networks, including the Internet, which link individuals, consumers, businesses, financial institutions, educational institutions, and government facilities. In fact, the growth in international commerce appears limitless given the forecasts relating to the commercial use of the Internet and the like.
There is a problem, however, inherent in international commerce, electronic or otherwise. The problem exists, for the most part, because monetary systems differ from country to country. That is, money is generally expressed in different currencies in different countries and the value of the different currencies vary greatly. Currency conversion is widely used to convert money from one currency into money of a different currency.
As used herein, the term “currency” includes, but is not limited to, denominations of script and coin that are issued by government authorities as a medium of exchange. A “currency” also may include a privately issued token that can be exchanged for another privately issued token or government script. For example, a company might create tokens in various denominations. This company issued “money” could be used by employees to purchase goods from merchants. In this case, an exchange rate might be provided to convert the company currency into currencies which are acceptable to merchants.
In each instance, currency conversion represents a significant economic risk to both buyers and sellers in international commerce. For example, assume a customer desires to buy a product from a merchant. Further consider the scenario where the customer pays his credit card bills in U.S. dollars and the merchant only accepts French francs for the products he sells. The customer uses his credit card to pay the merchant for the product. The merchant receives French francs.
Typically, at an undetermined later date, the company issuing the credit card would bill an amount to the customer in U.S. dollars. The amount billed to the customer is determined by an exchange rate used at the time the credit card company settles the transaction. This settlement is often at an indeterminate time and could be on the date of purchase or several days or weeks later. The time of this settlement is at the credit card company's discretion. The risk to the credit card company is minimal because the credit card company can settle the transaction when exchange rates are favorable. Thus, in this case, it is the customer who bears the risk that the value of the customer's currency will decline prior to this settlement.
As another example, consider a cash transaction where a merchant accepts a currency other than that of his country's currency. In this case, the merchant sells the currency to a currency trader, usually at a discount. The price the merchant charges to the customer who pays cash reflects both the cost of currency conversion (the discount) and the risk that the rate used to establish the price of the product in a particular currency may have changed. This results in the customer paying a higher price for the product and the merchant incurring risk due to a possible change in currency exchange rates.
Thus, the described post sale methods of currency exchange may impart significant risk upon the customer and the merchant. Risk is typically on the side of whoever commits to the currency conversion. Specifically, in a cash transaction, the customer bears the risk when currency is converted prior to purchasing a product. The merchant sustains the risk when he converts the customer's currency into his own currency. Also, in the case of transactions on the scale of a few cents, the cost of currency conversion may be greater than the currency is worth.
As yet another example, consider the risks that an individual assumes when he converts from the currency of his country (“native currency”) to a different second currency. In this case, the individual can purchase goods at a price in the second currency, but cannot be certain of the value of the second currency relative to his native currency. In this case, the currency exchange has occurred pre-sale. Thus, the individual assumes the risk of devaluation of the second currency against the first currency. Further, the customer bears the risk that the second currency may cease to be convertible into his native currency.
It is noted that if the individual desires to purchase an item in a third currency which differs from the native and second currencies, he must undertake at least one additional currency conversion (converting either his native currency to the third currency, the second currency to the third currency, or a combination of both). In this case, the customer assumes an additional risk.
The present invention recognizes that international commerce over electronic networks, such as the Internet, cannot reach potential unless customer and merchant obligations relating to transactions are fixed at the time of the transaction so that the risk to these parties associated with currency exchange is minimized. Thus, what is needed to encourage the development of international commerce over such networks is a system and method that offers a means of eliminating the uncertainty associated with multi-currency transactions. One aspect of the present invention is the shift of the risk associated with currency exchange from both the merchant and customer to a third party (e.g., a server) in real time. This server may assume the risk itself or may choose to subsequently pass on the risk to a fourth party (e.g., a bank or other financial institution).
SUMMARY OF INVENTION
The present invention is directed to a system for determining approval of a transaction between a merchant and a customer. The system comprises a customer device (e.g., a computer) associated with the customer. The customer device has a first set of data including an amount in a first currency. The system also has a merchant device (e.g., a computer) associated with the merchant. The merchant device has a second set of data including a product price in a second currency. The system further has a server device connected to both the customer device and the merchant device for receiving the first and second sets of data and for approving the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
Another aspect of the present invention is directed to a system for determining approval of a transaction between a customer and a merchant where the product price is known by the customer. The transaction includes the merchant providing a product price in a second currency. The system comprises a customer device (e.g., a computer) associated with the customer. The customer device has a first set of data including an amount in a first currency. The system also includes a server connected to the customer device. The server is able to access the product price in the second currency, receive the first set of data from the customer device, and can approve the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
Still another aspect of the present invention is directed to a method for determining approval of a transaction between a customer having a customer device (e.g., a computer) and a merchant having a merchant device (e.g., a computer). The customer device and the merchant device are connected to a server. The customer device has a first set of data including an amount in a first currency. The method comprises transmitting a second set of data from the merchant device to the customer device which receives the second set of data from the merchant device. The second set of data includes the product price in a second currency. The method further includes transmitting the first and the second sets of data by the customer device to the server and the server receiving the transmitted first and second sets of data. The server is for approving the transaction when the amount in the first currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
BRIEF DESCRIPTION OF DRAWINGS
Representative embodiments of the present invention will be described with reference to the following drawings:
FIG. 1 is a diagrammatic representation of one aspect of the present invention.
FIG. 2 is a diagrammatic representation of another aspect of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Reference is now made to the figures for the purpose of describing, in detail, the preferred embodiments of the present invention. The figures and accompanying detailed description are not intended to limit the scope of the claims appended hereto.
The preferred architecture of the present invention is generally depicted in FIG. 1. FIG. 1 shows three entities: a server 100, a customer computer 200, and a merchant computer 300, connected to each other via a network 50. Network 50 can be a private, public, secure, or an insecure network, such as the Internet, an intranet, and/or a Local Area Network (LAN). In the preferred embodiment, an insecure network, such as, the Internet is used. The connections to network 50 are identified by lines 105, 205, and 305, respectively, and are well known in the art.
Merchant computer 300 represents the computer of an individual, for example, merchant user 303, who sells products via network 50. A “product” can include goods, services, information, data, and the like. Customer computer 200 represents the computer of an individual, for example, a customer user 203, who wants to buy a product (or products) from merchant user 303 over network 50. The mechanism of delivery of the product is not a part of this patent. Product delivery could be coincident with payment, before payment, or after payment.
Server 100 represents a computer of an entity who processes transactions between customer user 203 and merchant user 303. Server 100 has a database which includes at least one customer account in a first currency associated with customer user 203 and at least one merchant account in a second currency associated with merchant user 303. The first currency differs from the second currency.
In the preferred embodiment, the accounts store electronic funds of the parties, for example, electronic cash. The electronic funds are a representation of funds (real cash, credit, and the like).
Server 100 also has its own server accounts. The server accounts are in currencies corresponding to the currencies of the customer and merchant accounts. The server accounts represent real cash, credit, and the like. The server accounts correspond to the electronic funds stored in the customer and merchant accounts.
In the preferred embodiment, local accounts are maintained at customer computer 200 and merchant computer 300. The local accounts represent the electronic funds in the customer account and the merchant account maintained at server 100, respectively. The local accounts of the customer and the merchant are sometimes referred in the art as “wallets” and “cash registers,” respectively. The server accounts may be arranged with a bank or other financial institution.
The following example is used to illustrate how these accounts can be set up: customer user 203 lives in the U.S. and purchases products using U.S. dollars (first currency) and merchant user 303 is located in France and conducts his operations in French francs (second currency). Server 100 includes a customer account in U.S. dollars and a merchant account in French francs. Server 100, which processes the transactions between these parties, further includes two electronic accounts representing all user accounts whose currencies are in dollars and all user accounts whose currencies are in francs. Server 100 also includes two accounts in a bank with one server account in U.S. dollars and the other server account in French francs.
Although the system can operate using an unsecured network 50, in the preferred embodiment, if network 50 is insecure, measures are taken to assure that server 100, customer computer 200, and merchant computer 300 can communicate securely over network 50. Central to achieving such security while maintaining a high performance payment system is the use of “sessions.” A session is an opportunity (or window) in which customer user 203 may purchase a product from merchant user 303 over the network 50 or which merchant user 303 sells a product to customer user 203 over network 50. By using a session, a merchant can securely communicate with a customer over an insecure network. Customer user 203 and merchant user 303 each have their own independent sessions. Sessions are of limited duration which is governed by predetermined parameters. In the preferred embodiment, these parameters are set by customer user 203 and merchant user 303. However, server 100 can set or limit values of such parameters.
In the preferred embodiment, the parameters relating to the session of customer user 203 limit an amount of electronic funds (“session amount”), a maximum amount of time that the session can last, and a maximum number of transactions that can be conducted. The session amount is the maximum amount of electronic funds that customer user 203 can spend during the customer's session. Also in the preferred embodiment, the session of merchant user 303 is limited by a maximum amount of time that the merchant's session can last and a maximum number of transactions that merchant user 303 can conduct.
To accomplish such secure communication over the insecure network, a first session associated with customer user 203 is created. The first session has first use parameters for limiting the duration that the first session can be used and a set of customer data. The first use parameters and the set of customer data are identifiable by server 100. A second session associated with merchant user 303 is also created. The second session has second use parameters for limiting the duration that the second session can be used and a set of merchant data. The second use parameters and the set of merchant data are identifiable by server 100. Over the insecure network, a portion of the first session and a portion of the second session are linked. The portion of the first session includes the set of customer data and the first use parameters. The set of customer data may include a customer identification string which identifies customer user 203. The portion of the second session includes the set of merchant data and the second use parameters. The set of merchant data may include a merchant identification string which identifies merchant user 303. Server 100 verifies customer user 203 and merchant user 303 based upon at least portions of the set of customer data and the set of merchant data and determines that the first and second sessions can be used. In this manner, confidential details of the payment between customer user 203 and merchant user 303 are assured of being communicated securely. This procedure of establishing secure communication is more fully set forth in co-pending U.S. patent application, Ser. No. 08/572,425, filed on Dec. 14, 1995, and entitled “Electronic Transfer and Method” which is incorporated herein by reference. Of course, other methods and systems for establishing secure communication over an insecure network may be used to use the invention set forth herein.
Merchant user 303 and customer user 203 endeavor ultimately to effect a “transaction,” that is, the purchase of a product by customer user 203 from merchant user 303. Merchant user 303 and customer user 203 do not require any prior existing relationship to transact business. This is so because merchant user 303 and customer user 203 each have a preestablished relationship with server 100 prior to transacting business.
How the parties form this relationship is not part of the present invention. Rather, what is important is that the customer and merchant accounts, described above, exist within server 100. In the preferred embodiment, to form the relationship, customer user 203 provides information using customer computer 200 to server 100. Such information can include the name of customer user 203 and the currency in which he intends to purchase products. In the case of merchant user 303, this information can include the name of merchant user 303 and the currency in which merchant user 303 intends to ultimately receive for providing products. Other information can be provided as deemed necessary by server 100.
This relationship may be either direct or indirect. An indirect relationship, for example, would include the situation where one or more entities, previously known to server 100, vouch for merchant user 303 and/or customer user 203. Public key cryptographic systems are generally used in this type of vouching process and are well known to those skilled in the art. The process of using public key cryptographic systems as such is known in the art as “certificate management.” In this case, vouching entities are known as “certificate authorities.” Certificates, certificate management, and certificate authorities are well known in the art and are used by but are not the subject of the present invention.
The present invention is directed toward “approval” of a multi-currency transaction in which customer user 203 pays in a first currency and merchant user 303 accepts the payment in a second currency which differs from the first currency, rather than the completed transaction itself. As will be described below, approval commits customer user 203 and merchant user 303 to the terms of the transaction and commits server 100 to perform virtual settlement of the transaction.
As used herein, “virtual settlement” of the transaction represents at least the movement of electronic funds to a merchant account of merchant user 303 held by server 100. It can also represent the movement of electronic funds from a customer account of customer user 203 held by server 100. This is to be distinguished from actual settlement of the transaction. As used herein, “actual settlement” of the transaction includes at least converting real funds in an amount equal to the amount in the first currency into real funds in the second currency.
The parties are committed because of pre-existing bilateral contractual obligation between customer user 203 and the operator of server 100 and between merchant user 303 and the operator of server 100. The contractual obligations are preferably formed during the commencement of service relationship between server 100 and customer user 203 and merchant user 303 respectively.
The obligations can include the agreement of customer user 203 and merchant user 303 to permit server 100 to perform virtual settlement of the transaction. In return, server 100 can agree to incur the risks associated with currency exchange when it performs actual settlement of the transaction. In the preferred embodiment, customer user 203 and merchant user 303 agree to allow server 100 (on behalf of the operator of server 100) to maintain accounts and balances of funds managed by server 100. In addition, in the preferred embodiment, the movement of funds between those accounts is coincident with the transaction.
In this way, customer user 203 knows substantially the amount in the currency customer user 203 will pay for the product. Similarly, merchant user 303 knows substantially the price in the currency merchant user 303 will receive for the product. Customer user 203 and merchant user 303 do not bear the above-described risks associated with currency exchange. The amount customer user 203 knows and the price merchant user 303 knows is substantially the respective amount and price because there may be minor factors that affect these actual values. Such factors will be discussed in terms of risk factors. The entity charged with performing actual settlement of the transaction bears such risks when the transaction is actually settled.
The present invention is directed to approval of multi-currency transactions in which customer user 203 pays in one currency and merchant user 303 accepts the payment in another currency. To transact business, customer user 203 shops over network 50 among merchant users 303 who also have been permitted by server 100 to transact business (which may be, for example, those who have merchant sessions). Using well known techniques, customer user 203 and a merchant user 303 agree on a product to be purchased at a particular price and in a particular currency.
Thus, merchant user 303 will accept a price and receive payment for the product sold to customer user 203. The price for the product is in a currency accepted by merchant user 303, referenced herein as the “product price in the second currency.” Customer user 203 will pay an amount to merchant user 303 for a selected product. The amount will be paid in a currency selected by customer user 203, referenced herein as the “amount in the first currency.” The currency (second) selected by merchant user 303 is different than the currency (first) selected by customer user 203. Hence, currency exchange is used to approve the transaction contemplated by the present invention.
In a first embodiment of the present invention, server 100 is used to approve the transaction between customer user 203 and merchant user 303. As stated previously, approval commits customer user 203 and merchant user 303 to the terms of the transaction and commits server 100 to perform virtual settlement of the transaction.
In this embodiment, customer user 203 and merchant user 303 have established and agreed upon a product to be purchased at a price merchant user 303 will accept. This product and price are referred to herein as the “agreed product” and the “agreed price,” respectively.
Having agreed upon the product and the price, customer computer 200 transmits a first set of data to server 100. This first set of data includes the amount in a first currency that customer user 203 is willing to pay for the agreed product. The transmitted amount is in the customer selected currency which is in a first currency. Other information may be transmitted by customer computer 200 as needed by server 100, for example, a requested payment range (described later), information identifying customer user 203, the product to be purchased, account information, and the like.
Having agreed upon the product and the price, merchant computer 300 transmits a second set of data to server 100. This second set of data includes the agreed price in a second currency that merchant user 303 is willing to receive for his product. The transmitted agreed price is in the merchant accepted currency which is in a second currency. Other information may be transmitted by the merchant computer 300 as needed by server 100, for example, information identifying merchant user 303, the product to be purchased, account information, and the like. As previously stated, the customer selected currency (first currency) is different than the merchant accepted currency (second currency).
In a further aspect of the preferred embodiment, along with providing the amount in the first currency, customer computer 200 also transmits the agreed price in the second currency to server 100. This assures that customer user 203 and merchant user 303 have actually reached agreement on the terms of the transaction and precludes either party from denying such agreement.
The system does not require that merchant user 303 know or approve the customer selected currency, that is, the currency in which customer user 203 will pay. There is no requirement that customer user 203 approve the merchant accepted currency, that is, the currency which merchant user 303 will receive. What is required is that server 100 be able to convert one such currency into the other.
However, it is noted that by not requiring “approval” of a currency by merchant user 303 and/or customer user 203 is distinguishable from the approval of a “transaction” by server 100. Approval of a currency would be, for example, where customer user 203 would need the permission of merchant user 303 to pay in a given customer selected currency. Approval of transaction, on the other hand, commits customer user 203 and merchant user 303 to the terms of the transaction and commits server 100 to perform virtual settlement of the transaction. The present invention does not require approval of a currency.
The first and second sets of data transmitted to server 100 need not come directly from customer computer 200 and merchant computer 300. This information may be transmitted via alternative routes. For example, in the preferred embodiment, customer computer 200 transmits the first set of data to the merchant computer 300. Upon receipt of the first set of data, merchant computer 300 transmits at least the amount in the first currency and the second set of data including the product price in the second currency to server 100 for approval of the transaction. In this case, the first set of data may be protected to prevent the merchant from altering it.
Upon receiving the amount in the first currency and the product price in the second currency, server 100 can approve the transaction. The approval process performed by server 100 is based upon the relative value of the amount in the first currency in terms of the product price in the second currency. This relative value may be established by the operator of server 100, a third party, or in other aspects of the present invention, customer user 203 or merchant user 303. This preferably includes a rate of exchange at which the amount in the first currency can be converted into a converted amount in the second currency. Alternatively, or in addition, this information may include a rate at which the merchant accepted currency can be converted into the customer selected currency.
Approval of the transaction occurs when the amount in the first currency is sufficient to pay merchant user 303 the product price in the second currency. The sufficiency determination process preferably includes converting the amount in the first currency into a converted amount in the second currency, referenced herein as the “converted amount in the second currency,” using a current exchange rate.
In the preferred embodiment, the current exchange rate data is maintained by the entity charged with approving the transaction. Thus, in this embodiment, server 100 may obtain the exchange rate from a currency broker or bank. In a further aspect of this embodiment, the approving entity may decide to buy and sell currencies and establish the approving entity's own exchange rates. In addition, as server 100 has the opportunity to aggregate transactions prior to committing to actually exchange currency with an external agency, the approving entity may obtain preferential exchange rates by converting money in relatively large units.
The frequency that the current exchange rate data is updated depends upon the level of risk that the approving entity may be willing to accept and the availability of updates from currency brokerage services. In the preferred embodiment, when server 100 is the approving entity, server 100 receives updates to the exchange rate data on-line from one or more currency brokers. Frequency and timing of updates are based on business rules agreed between the operator of server 100 and the currency broker or brokers. This manages the risk of a significant change between the current exchange rate and the exchange rate used when the transaction is actually settled.
Approval of the transaction by server 100 is preferably based upon predetermined criteria. These criteria may be established by any of the parties to the transaction or a third party. For example, in the preferred embodiment server 100 approves the transaction if the converted amount in the second currency equals or exceeds the product price in the second currency.
Alternatively, server 100 could approve the transaction if the converted amount in the second currency is less than the product price in the second currency. In this instance, server 100 may absorb differentials (as where the cost associated with disapproving the transaction and reprocessing it exceeds the differential). Acceptable differentials may be dependent upon the credit worthiness of customer user 203 or merchant user 303, the acceptable deficit balance that customer user 203 or merchant user 303 are allowed to incur, or other market conditions such as, for example, fluctuations in exchange rates. These acceptable differentials are referred to with respect to each party of the transaction as a “risk range.”
Also, in the case where the converted amount in the second currency is less than the product price in the second currency, but within a predetermined range, server 100 could record the differentials as they occur and collect them from customer user 203 at a later time. This range is contemplated as being a small range and is referred to herein as the “payment range.” The payment range may be predetermined by customer user 203 or preferably, by server 100. For the purpose of this application, the amount in the first currency is equal to the amount in the first currency plus or minus the payment range. The payment range thus defines the amount of conversion error permitted in the transaction.
Approval of the transaction may also be contingent upon customer user 203 having access to electronic funds in an amount equal to or exceeding the amount in the customer selected currency (ACSC). These funds maybe stored or represented in a customer account associated with customer user 203. In this case, server 100 approves the transaction when the converted amount in the second currency meets the predetermined criteria described above and the customer account contains electronic funds in an amount at least equal to the amount in the first currency. Using any of the above methods for approval, alone or in combination, server 100 approves the transaction.
In order to avoid having to access the customer account of customer user 203 and for security reasons, it is preferred to limit the amount in the first set of data that a customer user 203 can transmit to server 100 by the session amount. The session amount is an amount known by server 100 to which the customer has access when customer user 203 is permitted to shop. The limited amount is reduced as customer user 203 purchases products over network 50. Customer computer 200 temporarily prohibits customer user 203 from transmitting an amount exceeding the session amount to server 100 to be considered for sufficiency until more electronic funds are added to the session in which case the session amount has been increased.
In the preferred embodiment, under such circumstances, the existing session will automatically close and a new session will be opened with funds at least sufficient to complete the transaction. Once the subsequent session is opened, the transaction may be approved. Of course, if server 100 determines that customer user 203 does not have enough funds available to it to open a subsequent session of sufficient value, the transaction may be refused by server 100 altogether or server 100 may approve the transaction as described herein.
In the preferred embodiment, the funds that are available to customer user 203 during the session and the funds received by merchant user 303 during the session be maintained to two decimal positions to the right of the minor unit of a currency. For example, in the case of U.S. dollars, the present invention preferably would carry the value of session funds to one hundredth of a penny to assure that rounding errors are minimized during a session, thus decreasing rounding errors during currency conversion of small transactions. When a session closes, the balance in the session is adjusted to whole minor currency units (this adjustment may be rounding or truncation).
Once the transaction is approved, customer user 203 and merchant user 303 are committed to the terms of the transaction. Specifically, customer user 203 is committed to pay the amount in the first currency. Similarly, merchant user 303 is committed to accept the product price in the second currency for the product. The parties are committed as such through the contractual arrangement previously described.
By the contractual obligations described above, server 100 is committed to perform virtual settlement of the transaction. Therefore, according to this aspect of the present invention, a customer account may be maintained for customer user 203 and a merchant account may be maintained for merchant user 303. The customer accounts and merchant accounts are preferably maintained by server 100. However, one or both of the accounts may be maintained by a party other than server 100.
The customer account and merchant account maybe debit or credit accounts. In the preferred embodiment, the customer account is a debit account and the merchant account is a credit account and each such account represent funds in the form of electronic funds. However, other types of accounts may be used as known by those skilled in the art.
In the case where a party other than server 100 maintains a merchant account and/or a customer account, server 100 may transmit data to the party to enable virtual settlement. For example, if the other party maintains the customer account and the merchant account, server 100 may transmit data identifying the customer account and the amount in the first currency to be debited, and the merchant account and the product price in the second currency to be credited. Then, the party would debit the customer account and credit the merchant account accordingly.
In this process, upon approval of the transaction, the customer account is debited by the amount in the first currency. The merchant account is credited with the agreed price in the second currency. This amount and price were known by and agreed to by customer user 203 and merchant user 303. Thus, there is ho uncertainty as to the amount or currency to be paid by customer user 203 or the price or currency to be received by merchant user 303.
Several variations on the above described embodiment provides that the currency used in the first currency may be selected by customer user 203 (or server 100) from a plurality of currencies, referred to herein as “customer currencies.” Also, the currency used in the merchant accepted currency may be selected by customer user 203 from a plurality of currencies, referred to herein as “merchant currencies.” A description of these variations is now provided.
A customer user 203 may have access to amounts in a plurality of customer currencies. For example, a customer user 203 may have accounts containing amounts in U.S. dollars, French francs, and Japanese yen. Customer user 203 can purchase products using amounts from any of these accounts. To effect this option, customer computer 200 presents an amount in each of the plurality of customer currencies to customer user 203. This is done using exchange rate data for each customer currency to convert the merchant accepted currency into amounts in each of the customer currencies. In the preferred embodiment, the exchange rate data is provided to customer computer 200 by server 100 at various times. Other mechanisms for obtaining such data include the use of brokers. Customer user 203 selects an amount in one of the plurality of customer currencies in which the customer user 203 will spend for the product. This selected amount represents the amount in the first currency described previously and is referred herein as the “selected currency.”
In the above description, the method by which customer computer 200 determines the amount of customer currency to pay for a purchase in the merchant computer 300's currency is omitted. While there are a number of ways to enable this conversion, in the preferred embodiment, prior to the inception of the customer computer 200's session, customer computer 200 requests exchange rate data. This data will contain at least conversion rates from the session currency to other convertible currencies, it may also contain additional data such as anticipated expiration of the exchange rates. These rates are used by customer computer 200 to estimate the amount of customer currency to pay for a purchase in merchant currency. As conversion rates may change rapidly, in the preferred embodiment, this data is advisory only. Server 100 can send updated data to customer computer 200 during any communication between them. The implication of this decision is that if customer computer 200 pays insufficient funds to convert, it is viewed as a natural error due to obsolete data, not an attempt to defraud.
This aspect of the present invention can further include an optimization feature. The optimization feature is preferably executed by customer computer 200 to determine whether it is advantageous for customer user 203 to pay in one customer currency over another.
More specifically, customer computer 200 determines the agreed price in the merchant accepted currency corresponding to the amount in each of the plurality of customer currencies. For example, assume merchant user 303 will receive a price in currency C for the product and customer user 203 has two customer currencies A and B available to pay merchant user 303. Customer computer 200 determines amounts in currencies A and B which equate to the product price in currency C. These amounts may be compared by converting them to a reference currency of the customer computer 200's choice. Customer user 203 can choose (or customer computer 200 can be programmed to choose) to pay the agreed price in the currency (A or B) which corresponds to the lesser amount in the reference currency. The amount in the chosen currency represents the amount in the first currency and is referred herein as the “selected currency.”
According to another variation to this optimization feature, customer computer 200 can also determine whether it is less expensive to first convert currency A into currency B, and then to convert currency B into currency C. In any case, customer user 203 pays using the optimal payment currency. This preferred mode reduces complexity of currency exchange to customer user 203 without reducing the options available to customer user 203.
In another embodiment, server 100 can execute an optimization feature. In this case, server 100 may include the plurality of customer currencies available to customer user 203. For example, data indicating the plurality of customer currencies may be transmitted in the first set of data from customer computer 200 to server 100 in lieu of the amount in the first currency. In a manner similar to that described above, server 100 determines the agreed amount in the second currency for each of the plurality of customer currencies. Server 100 then chooses an amount in one of the customer currencies corresponding to the amount in the merchant accepted currency which is the least when converted to the reference currency. The amount in the chosen currency represents the amount in the first currency.
In another embodiment of the present invention, it is expected that a merchant user 303 may desire to transact business in more than one currency. Therefore, merchant user 303 will accept a price for the product in one of a plurality of merchant currencies. Merchant computer 300 communicates the agreed price for the product in each of the merchant currencies to customer computer 200. Customer computer 200 presents the agreed price in each of the merchant currencies to customer user 203. Customer user 203 selects the agreed price in one of the merchant currencies that merchant user 303 will accept. This selected currency maybe recommended by the optimization procedure described above. This selected price represents the product price in the merchant accepted currency (PMAC), although it is actually selected by customer user 203.
According to a variation to this optimization feature, customer computer 200 may also determine which customer currency - merchant currency pair represents the best value to customer user 203. This is accomplished by customer computer 200 using exchange rate data to convert the price of the product in each merchant accepted currency into each of the customer currencies and selecting the lowest value among the results. For example, if customer user 203 has access to currencies A, B, C and merchant user 203 is willing to accept currencies y and z, customer computer 200 will determine the cost of the products as quoted in merchant accepted currencies y and z in terms of customer accepted currency A. Whichever of these conversions yields the lowest cost to customer user 203 is the optimal customer currency merchant currency pair for customer currency A. This process is repeated until an optimal currency pair is computed for each customer currency. For example, this process may yield the following results: A to y, B to y, and C to z.
The next step is to decide which of these currency pairs represents the best value to customer user 203. In the preferred embodiment, this is accomplished by converting each customer currency to a single reference currency. The conversion that yields the smaller number is identified as the “best” choice and is displayed to customer user 203. Clearly, other approaches to determining the optimum currency can be devised by those skilled in the art.
Another embodiment of the present invention, as shown in FIG. 2, again uses server 100 to approve the transaction between customer user 203 and merchant user 303. However, the merchant computer need not be connected to network 50 according to this aspect of the invention.
More particularly, in this embodiment, customer user 203 has knowledge about the product that merchant user 303 is providing and the price in the merchant selected currency for the product before submitting the first set of data to server 100. This knowledge need not be gained while customer user 203 shops over network 50. For example, merchant user 303 can have distributed catalogs to customer user 203 (via regular mail, email, etc.) illustrating products, prices, and currencies therefor. Server 100 would receive the same information, that is, data representing the same products, prices and currencies from merchant user 303. This data may be received by server 100 electronically over network 50 or by some other means. For example, merchant user 303 might provide the data representing the products, prices and currencies therefor via a network to which customer computer 200 is not connected or by mail on a diskette. However received, this data would be accessible by server 100.
After viewing the catalog, customer user 203 may purchase a product over network 50. In this case, customer computer 200 transmits to server 100 a description of a desired product (e.g., model number) and an amount in the first currency for the desired product.
Server 100 thus has access to data indicating the amount in the first currency which customer user 203 is willing to pay for a product and the product price in the second currency which merchant user 303 is willing to accept for the product. With this data, server 100 approves the transaction as indicated above.
In any of the foregoing embodiments, notice of approval of the transaction may be provided by server 100 to customer user 203 and merchant user 303 For example, server 100 may transmit data indicating approval to the merchant computer 300. After merchant computer 300 receives the data indicating approval, merchant computer 300 may transmit at least a portion of the data indicating approval to customer computer 200. In a similar manner, data indicating approval may be communicated from server 100 to customer computer 200, which, in turn, would forward this data to merchant computer 300. In this manner, customer user 203 and merchant user 303 may be informed that the transaction was approved.
Alternatively, server 100 may separately transmit data indicating approval to customer computer 200 and merchant computer 300. In yet another embodiment, the absence of notice from server 100 maybe deemed as affirmative notice that the transaction was approved. According to any of these procedures, or other preestablished procedures, notice may be provided to the participants in the transaction. Further, once notice of approval is provided, the product which is the subject of the transaction may be provided to customer user 203 and the payment of the funds corresponding to the agreed price will be received by merchant user 303 in the merchant accepted currency.
Actual settlement may occur contemporaneously with the approval of the transaction or it may be deferred. As is described below, it is the entity charged with performing the actual settlement who bears the risk.
In the preferred embodiment, server 100 performs actual settlement of the transaction. Therefore, according to this aspect of the present invention, server 100 also has its own server accounts. Server accounts are in currencies corresponding to the currencies of the customer and merchant accounts. Server accounts represent real cash, credit, and the like, corresponding to the electronic funds stored in the customer and merchant accounts.
To perform actual settlement, server 100 may transmit data to a currency broker, bank or financial institution to enable actual settlement. For example, server 100 may transmit data identifying server account and the amount in the first currency so that the entity can convert real funds in an amount equal to the amount in the customer selected currency into real funds in the second currency.
In the preferred embodiment, server 100 aggregates the amounts in each currency before settling. This may decrease the number of actual conversions that must be made from possibly hundreds per second to a few times per hour (or day). The frequency may vary depending on the volatility of the currency exchange market and on the relative currency balances in server 100's various currency accounts.
Note that server 100 is bound even if the later currency exchange rates are or become unfavorable to server 100 as compared to the current exchange rates used during the virtual settlement. By eliminating the risk to customer user 203 and merchant user 303, such risk is passed to server 100.
In the preferred embodiment, measures are taken to manage the risk associated with the currency exchange to server 100. For example, server 100 can have a preestablished agreement with the bank or financial institution. The terms of such an agreement might include a commitment on the part of server 100 to settle transactions within a predetermined amount, time, and/or within a predetermined currency rate deviation. The predetermined amount of time may be on the order of several seconds or minutes.
In the preferred embodiment, during this predetermined amount of time, server 100 aggregates transactions and submits them in batch for exchange. In return for server 100's commitment, the entity may offer server 100 a favorable currency exchange rate.
It is seen from the above detailed description that customer and merchant obligations relating to multi-currency transactions can be fixed at the time of the transaction. In this manner, risks to these parties heretofore associated with currency exchange is minimized. To this end, the parties to a multi-currency transaction authorize an approving entity to settle the transaction. Authorization is granted by virtue of customer user 203 and merchant user 303 setting up their respective accounts, knowing that transactions will be submitted and processed. The parties transmit data representing the transaction to the approving authority. This data includes an amount in a first currency that a customer user 203 is willing to pay for a product and a product price in a different second currency which a merchant user 303 is willing to accept for the product. Using predetermined criteria, the approving entity approves the transaction. Once the transaction is approved, the approving entity may actually settle the transaction at its discretion thereby bearing the risk associated with currency exchange. The parties, however, incur no risk. Customer user 203 will pay the amount in the first currency and merchant user 303 will receive the product price in the second currency. These are values known and agreed to by the parties at the time of the transaction.
An alternate method of managing risk for extremely volatile currencies, server 100 may choose to withdraw a currency or currencies from the list of convertible currencies.
Although the particular embodiments shown and described above will prove to be useful in many applications relating to the arts to which the present invention pertains, further modifications of the present invention herein disclosed will occur to persons skilled in the art. All such modifications are deemed to be within the scope of the present invention as defined by the appended claims.

Claims (231)

1. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is at least equal to the product price in the second currency in accordance with current exchange rates.
2. The system of claim 1, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
3. The system of claim 1, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
4. The system of claim 1, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
5. The system of claim 1, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
6. The system of claim 1, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
7. The system of claim 6, wherein the customer selects the first currency from the plurality of currencies.
8. The system of claim 6, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
9. The system of claim 6, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
10. The system of claim 6, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
11. The system of claim 1, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
12. The system of claim 1, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
13. The system of claim 1, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
14. The system of claim 1, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
15. The system of claim 1, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
16. The system of claim 1, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
17. The system of claim 1, wherein the merchant sets the exchange rate.
18. The system of claim 1, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
19. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
20. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
21. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
22. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
23. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
24. The system of claim 23, wherein the customer selects the first currency from the plurality of currencies.
25. The system of claim 23, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
26. The system of claim 23, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
27. The system of claim 23, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
28. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
29. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
30. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
31. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the merchant sets the exchange rate.
32. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
33. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a payment range of the product price in the second currency in accordance with current exchange rates.
34. The system of claim 33, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
35. The system of claim 33, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
36. The system of claim 33, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
37. The system of claim 33, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
38. The system of claim 33, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
39. The system of claim 38, wherein the customer selects the first currency from the plurality of currencies.
40. The system of claim 38, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
41. The system of claim 38, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
42. The system of claim 38, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
43. The system of claim 33, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
44. The system of claim 33, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
45. The system of claim 33, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
46. The system of claim 33, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
47. The system of claim 33, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
48. The system of claim 33, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
49. The system of claim 33, wherein the merchant sets the exchange rate.
50. The system of claim 33, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
51. The system of claim 33, wherein if the converted amount in the second currency is less than the product price in the second currency and the difference between the converted amount in the second currency and the product price in the second currency is within a predetermined range, then the server records the difference.
52. The system of claim 51, wherein the server collects the recorded difference from the customer.
53. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in the second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for approving the transaction when the converted amount in the second currency is at least equal to the product price in the second currency in accordance with current exchange rates.
54. The system of claim 53, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
55. The system of claim 53, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
56. The system of claim 53, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
57. The system of claim 53, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
58. The system of claim 53, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
59. The system of claim 58, wherein the customer selects the first currency from the plurality of currencies.
60. The system of claim 58, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
61. The system of claim 58, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
62. The system of claim 58, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
63. The system of claim 53, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
64. The system of claim 53, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
65. The system of claim 53, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
66. The system of claim 53, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
67. The system of claim 53, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
68. The system of claim 53, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
69. The system of claim 53, wherein the merchant sets the exchange rate.
70. The system of claim 53, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
71. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
72. The system of claim 71, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
73. The system of claim 71, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
74. The system of claim 71, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
75. The system of claim 71, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
76. The system of claim 71, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
77. The system of claim 76, wherein the customer selects the first currency from the plurality of currencies.
78. The system of claim 76, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
79. The system of claim 76, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
80. The system of claim 76, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
81. The system of claim 71, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
82. The system of claim 71, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
83. The system of claim 71, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
84. The system of claim 71, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
85. The system of claim 71, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
86. The system of claim 71, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
87. The system of claim 71, wherein the merchant sets the exchange rate.
88. The system of claim 71, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
89. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept;
a merchant computer associated with a merchant and connected to the network, wherein the merchant computer further comprises a second set of data including a product price at which the merchant agrees to sell the product in a second currency; and
a server connected to both the customer computer via the network and the merchant computer via the network, for receiving the first set of data, the second set of data, and for approving the transaction when the converted amount in the second currency is within a payment range of the product price in the second currency in accordance with current exchange rates.
90. The system of claim 89, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
91. The system of claim 89, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
92. The system of claim 89, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
93. The system of claim 89, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
94. The system of claim 89, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
95. The system of claim 94, wherein the customer selects the first currency from the plurality of currencies.
96. The system of claim 94, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
97. The system of claim 94, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
98. The system of claim 94, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
99. The system of claim 89, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
100. The system of claim 89, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
101. The system of claim 89, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
102. The system of claim 89, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
103. The system of claim 89, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
104. The system of claim 89, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
105. The system of claim 89, wherein the merchant sets the exchange rate.
106. The system of claim 89, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
107. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is at least equal to the product price in the second currency in accordance with current exchange rates.
108. The system of claim 107, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
109. The system of claim 107, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
110. The system of claim 107, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
111. The system of claim 107, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
112. The system of claim 107, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
113. The system of claim 112, wherein the customer selects the first currency from the plurality of currencies.
114. The system of claim 112, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
115. The system of claim 112, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
116. The system of claim 112, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
117. The system of claim 107, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
118. The system of claim 107, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
119. The system of claim 107, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
120. The system of claim 107, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
121. The system of claim 107, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
122. The system of claim 107, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
123. The system of claim 107, wherein the merchant sets the exchange rate.
124. The system of claim 107, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
125. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
126. The system of claim 125, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
127. The system of claim 125, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
128. The system of claim 125, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
129. The system of claim 125, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
130. The system of claim 125, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
131. The system of claim 130, wherein the customer selects the first currency from the plurality of currencies.
132. The system of claim 130, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
133. The system of claim 130, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
134. The system of claim 130, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
135. The system of claim 125, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
136. The system of claim 125, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
137. The system of claim 125, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
138. The system of claim 125, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
139. The system of claim 125, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
140. The system of claim 125, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
141. The system of claim 125, wherein the merchant sets the exchange rate.
142. The system of claim 125, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
143. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including an amount the customer agrees to pay for the a product in a first currency; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, for converting the amount in the first currency into a converted amount in the second currency, and for approving the transaction when the converted amount in the second currency is within a payment range of the product price in the second currency in accordance with current exchange rates.
144. The system of claim 143, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
145. The system of claim 143, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
146. The system of claim 143, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
147. The system of claim 143, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
148. The system of claim 143, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
149. The system of claim 148, wherein the customer selects the first currency from the plurality of currencies.
150. The system of claim 148, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
151. The system of claim 148, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
152. The system of claim 148, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
153. The system of claim 143, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
154. The system of claim 143, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
155. The system of claim 143, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
156. The system of claim 143, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
157. The system of claim 143, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
158. The system of claim 143, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
159. The system of claim 143, wherein the merchant sets the exchange rate.
160. The system of claim 143, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
161. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, and for approving the transaction when the converted amount in the second currency is at least equal to the product price in the second currency in accordance with current exchange rates.
162. The system of claim 161, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
163. The system of claim 161, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
164. The system of claim 161, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
165. The system of claim 161, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
166. The system of claim 161, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
167. The system of claim 166, wherein the customer selects the first currency from the plurality of currencies.
168. The system of claim 166, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
169. The system of claim 166, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
170. The system of claim 166, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
171. The system of claim 161, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
172. The system of claim 161, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
173. The system of claim 161, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
174. The system of claim 161, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
175. The system of claim 161, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
176. The system of claim 161, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
177. The system of claim 161, wherein the merchant sets the exchange rate.
178. The system of claim 161, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
179. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, and for approving the transaction when the converted amount in the second currency is within a risk range of the product price in the second currency in accordance with current exchange rates.
180. The system of claim 179, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
181. The system of claim 179, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
182. The system of claim 179, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
183. The system of claim 179, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
184. The system of claim 179, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
185. The system of claim 184, wherein the customer selects the first currency from the plurality of currencies.
186. The system of claim 184, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
187. The system of claim 184, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
188. The system of claim 184, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
189. The system of claim 179, wherein the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
190. The system of claim 179, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
191. The system of claim 179, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
192. The system of claim 179, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
193. The system of claim 179, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
194. The system of claim 179, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
195. The system of claim 179, wherein the merchant sets the exchange rate.
196. The system of claim 179, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
197. A system for determining approval of a transaction between a merchant and a customer over a network, wherein the transaction includes the merchant providing a product to the customer at a product price in a second currency, wherein the product price in the second currency is known by the customer, wherein the system comprises:
a network;
a customer computer associated with a customer and connected to the network, wherein the customer computer further comprises a first set of data including a converted amount in a second currency, wherein the customer computer generates the converted amount in the second currency by converting the amount the customer agrees to pay for a product in a first amount into the converted amount in the second currency using current exchange rates, wherein the second currency is a currency the merchant is willing to accept; and
a server connected to the customer computer via the network and having the product price in a second currency, for receiving the first set of data, and for approving the transaction when the converted amount in the second currency is within a payment range of the product price in the second currency in accordance with current exchange rates.
198. The system of claim 197, wherein the customer selects the first currency from the plurality of currencies in which the customer has an account for each currency.
199. The system of claim 197, wherein the server selects the first currency from the plurality of currencies in which the customer has an account for each currency, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
200. The system of claim 197, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
201. The system of claim 197, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
202. The system of claim 197, wherein the first currency is selected from a plurality of currencies in which the customer has an account for each currency and the second currency is selected from a plurality of currencies the merchant is willing to accept.
203. The system of claim 202, wherein the customer selects the first currency from the plurality of currencies.
204. The system of claim 202, wherein the server selects the first currency from the plurality of currencies, wherein the selected first currency when converted into the second currency, the merchant price is the least expensive.
205. The system of claim 202, wherein the customer selects the second currency from the plurality of currencies the merchant is willing to accept.
206. The system of claim 202, wherein the server selects the second currency from the plurality of currencies, wherein the merchant price is the least expensive for the selected second currency when the first currency is converted into the second currency.
207. The system of claim 197, wherein the server further comprises a customer balance account associated with the customer, Wherein the customer balance account comprises a customer balance in the first currency and wherein the server deducts the amount in the first currency from the balance in the customer balance account.
208. The system of claim 197, wherein a party other than the server further comprises a customer balance account associated with the customer, wherein the customer balance account comprises a customer balance in the first currency and wherein the party other than the server deducts the amount in the first currency from the balance in the customer balance account based on information provided by the server.
209. The system of claim 197, wherein the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the server adds the converted amount in the second currency to the balance in the merchant balance account.
210. The system of claim 197, wherein a party other than the server further comprises a merchant balance account associated with the merchant, wherein the merchant balance account comprises a merchant balance in the second currency and wherein the party other than the server adds the converted amount in the second currency to the balance in the merchant balance account based on information provided by the server.
211. The system of claim 197, wherein the network is selected from the group consisting of the Internet, an intranet, and a Local Area Network (LAN).
212. The system of claim 197, wherein the current exchange rate is selected from the group consisting of a currency broker and a bank.
213. The system of claim 197, wherein the merchant sets the exchange rate.
214. The system of claim 197, wherein the customer computer sends a copy of the agreed price in the second currency to the server.
215. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
transmitting a first set of data from a customer computer to a server, wherein the first set of data includes an amount in a first currency;
transmitting a second set of data by a merchant computer to the server; wherein the second set of data includes a product price in a second currency;
receiving the first set of data and the second set of data by the server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is at least equal to the product price in the second currency.
216. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
transmitting a first set of data from a customer computer to a server, wherein the first set of data includes an amount in a first currency;
transmitting a second set of data by a merchant computer to the server; wherein the second set of data includes a product price in a second currency;
receiving the first set of data and the second set of data by the server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is within a payment range of the product price in the second currency.
217. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
transmitting a second set of data from a merchant computer to a customer computer, wherein the second set of data includes a product price in a second currency;
receiving the second set of data by the customer computer, wherein the customer computer has a first set of data including an amount in a first currency;
transmitting the first set of data and the second set of data by the customer computer to a server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is at least equal to the product price in the second currency.
218. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant
computer are connected to a server via the network, wherein the method comprises:
transmitting a second set of data from a merchant computer to a customer computer, wherein the second set of data includes a product price in a second currency;
receiving the second set of data by the customer computer, wherein the customer computer has a first set of data including an amount in a first currency;
transmitting the first set of data and the second set of data by the customer computer to a server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is within a payment range of the product price in the second currency.
219. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
transmitting a first set of data from a customer computer to a merchant computer, wherein the first set of data includes an amount in a first currency;
receiving the first set of data by the merchant computer, wherein the merchant computer has a second set of data including a product price in a second currency;
transmitting the first set of data and second set of data by the merchant computer to a server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is at least equal to the product price in the second currency.
220. A method for determining approval of a transaction over a network between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
transmitting a first set of data from a customer computer to a merchant computer, wherein the first set of data includes an amount in a first currency;
receiving the first set of data by the merchant computer, wherein the merchant computer has a second set of data including a product price in a second currency;
transmitting the first set of data and second set of data by the merchant computer to a server;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server when the converted amount in the second currency is within a payment range of the product price in the second currency.
221. A method for determining approval of a transaction over a network connection between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
receiving a first set of data from the customer computer to the server, the first set of data including an amount in a first currency;
receiving a second set of data from the merchant computer to the server, the second set of data including a product price in a second currency;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server if the converted amount in the second currency is at least equal to the product price in the second currency.
222. A method for determining approval of a transaction over a network connection between a customer having a customer computer connected to the network and a merchant having a merchant computer connected to the network, wherein the customer computer and the merchant computer are connected to a server via the network, wherein the method comprises:
receiving a first set of data from the customer computer to the server, the first set of data including an amount in a first currency;
receiving a second set of data from the merchant computer to the server, the second set of data including a product price in a second currency;
converting the amount in the first currency into a converted amount in the second currency using current exchange rates; and
approving the transaction by the server if the converted amount in the second currency is within a payment range of the product price in the second currency.
223. A machine readable storage medium comprising a set of stored instructions capable of being executed by a processor to:
receive a first set of data and a second set of data, the first set of data to include an amount a customer agrees to pay for a product in a first currency, the second set of data to include a product price at which a merchant agrees to sell the product in a second currency;
convert the amount in the first currency into a converted amount in the second currency; and
approve a transaction if the converted amount in the second currency is at least equal to the product price in the second currency in accordance with current exchange rates.
224. The medium of claim 223, wherein the customer is to select the first currency from a plurality of currencies, the customer to have an account for each currency.
225. The medium of claim 223, wherein the instructions are further capable of being executed to select the first currency from a plurality of currencies, the customer to have an account for each currency, the selected first currency being associated with a least expensive merchant price.
226. The medium of claim 223, wherein the customer is to select the second currency from a plurality of currencies the merchant is willing to accept.
227. The medium of claim 223, wherein the instructions are further capable of being executed to select the second currency from a plurality of currencies, the selected first currency being associated with a least expensive merchant price.
228. The medium of claim 223, wherein the first currency is to be selected from a first plurality of currencies, the customer to have an account for each of the first plurality of currencies, the second currency to be selected from a second plurality of currencies the merchant is willing to accept.
229. The medium of claim 227, wherein the customer is to select the first currency from the first plurality of currencies.
230. The medium of claim 227, wherein the instructions are further capable of being executed to select the first currency from a plurality of currencies, the customer to have an account for each currency, the selected first currency being associated with a least expensive merchant price.
231. The medium of claim 227, wherein the customer is to select the second currency from a plurality of currencies the merchant is willing to accept.
US10/390,540 1996-06-14 2003-03-18 System and method for multicurrency transactions Expired - Lifetime USRE41619E1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/390,540 USRE41619E1 (en) 1996-06-14 2003-03-18 System and method for multicurrency transactions
US12/855,603 USRE44502E1 (en) 1996-06-14 2010-08-12 System and method for multi-currency transactions

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US08/663,896 US5897621A (en) 1996-06-14 1996-06-14 System and method for multi-currency transactions
US09/213,590 US6205433B1 (en) 1996-06-14 1998-12-17 System and method for multi-currency transactions
US10/390,540 USRE41619E1 (en) 1996-06-14 2003-03-18 System and method for multicurrency transactions

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US08/663,896 Continuation US5897621A (en) 1996-06-14 1996-06-14 System and method for multi-currency transactions
US09/213,590 Reissue US6205433B1 (en) 1996-06-14 1998-12-17 System and method for multi-currency transactions

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US09/213,590 Continuation US6205433B1 (en) 1996-06-14 1998-12-17 System and method for multi-currency transactions

Publications (1)

Publication Number Publication Date
USRE41619E1 true USRE41619E1 (en) 2010-08-31

Family

ID=24663678

Family Applications (4)

Application Number Title Priority Date Filing Date
US08/663,896 Expired - Lifetime US5897621A (en) 1996-06-14 1996-06-14 System and method for multi-currency transactions
US09/213,590 Ceased US6205433B1 (en) 1996-06-14 1998-12-17 System and method for multi-currency transactions
US10/390,540 Expired - Lifetime USRE41619E1 (en) 1996-06-14 2003-03-18 System and method for multicurrency transactions
US12/855,603 Expired - Lifetime USRE44502E1 (en) 1996-06-14 2010-08-12 System and method for multi-currency transactions

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US08/663,896 Expired - Lifetime US5897621A (en) 1996-06-14 1996-06-14 System and method for multi-currency transactions
US09/213,590 Ceased US6205433B1 (en) 1996-06-14 1998-12-17 System and method for multi-currency transactions

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/855,603 Expired - Lifetime USRE44502E1 (en) 1996-06-14 2010-08-12 System and method for multi-currency transactions

Country Status (5)

Country Link
US (4) US5897621A (en)
EP (1) EP0910840A2 (en)
AU (1) AU713339B2 (en)
CA (1) CA2260002C (en)
WO (1) WO1997048078A2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080167965A1 (en) * 2007-01-09 2008-07-10 Von Nothaus Bernard Apparatus, system, and method for extracting real world value from a virtual account
US20080183590A1 (en) * 2007-01-29 2008-07-31 Antoni Drudis Methods for providing secure eCommerce transactions
US20090076954A1 (en) * 2007-09-14 2009-03-19 Carmody Michael D Method and system for settling financial transactions
US20090228378A1 (en) * 2006-03-01 2009-09-10 Alibaba Group Holding Limited Method and System to Charge an Account
US20120150602A1 (en) * 1999-04-19 2012-06-14 Enpulz, Llc Centralized, online multi-seller interface system
USRE46140E1 (en) * 2000-04-19 2016-09-06 Virginia Innovation Sciences, Inc. Method and system for conducting business in a transnational e-Commerce network

Families Citing this family (418)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5710000A (en) * 1994-09-16 1998-01-20 Affymetrix, Inc. Capturing sequences adjacent to Type-IIs restriction sites for genomic library mapping
US7930340B2 (en) * 1995-11-13 2011-04-19 Lakshmi Arunachalam Network transaction portal to control multi-service provider transactions
US8271339B2 (en) 1995-11-13 2012-09-18 Lakshmi Arunachalam Method and apparatus for enabling real-time bi-directional transactions on a network
US8037158B2 (en) * 1995-11-13 2011-10-11 Lakshmi Arunachalam Multimedia transactional services
US20030195847A1 (en) 1996-06-05 2003-10-16 David Felger Method of billing a purchase made over a computer network
US8229844B2 (en) 1996-06-05 2012-07-24 Fraud Control Systems.Com Corporation Method of billing a purchase made over a computer network
US7555458B1 (en) 1996-06-05 2009-06-30 Fraud Control System.Com Corporation Method of billing a purchase made over a computer network
US5897621A (en) 1996-06-14 1999-04-27 Cybercash, Inc. System and method for multi-currency transactions
US20030014318A1 (en) * 1996-11-08 2003-01-16 Matthew Byrne International trading system and method
FR2756647B1 (en) * 1996-12-03 1999-01-22 Soc D Services Interbancaires METHOD FOR TRANSFERRING BETWEEN SEVERAL QUANTITY SYSTEMS EXPRESSED IN DIFFERENT UNITS OF MEASUREMENT
US6460020B1 (en) * 1996-12-30 2002-10-01 De Technologies, Inc. Universal shopping center for international operation
US6249775B1 (en) * 1997-07-11 2001-06-19 The Chase Manhattan Bank Method for mortgage and closed end loan portfolio management
US20040039668A1 (en) * 1997-07-22 2004-02-26 Patent And Trademark Fee Management, Llc Computerized patent and trademark fee payment method and system
US6363361B1 (en) * 1997-07-22 2002-03-26 Patent & Trademark Fee Management, Llc Computerized patent and trademark fee payment method and system for law firms
US7403922B1 (en) * 1997-07-28 2008-07-22 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US7096192B1 (en) * 1997-07-28 2006-08-22 Cybersource Corporation Method and system for detecting fraud in a credit card transaction over a computer network
JPH1166193A (en) * 1997-08-14 1999-03-09 Hitachi Ltd Method and device for managing electronic money and storage medium where electronic money managing program is stored
US5995947A (en) * 1997-09-12 1999-11-30 Imx Mortgage Exchange Interactive mortgage and loan information and real-time trading system
GB2330923A (en) * 1997-10-28 1999-05-05 Ibm Transaction manager
US6240400B1 (en) * 1998-02-17 2001-05-29 International Business Machines Corporation Method and system for accommodating electronic commerce in the semiconductor manufacturing industry
US6289318B1 (en) 1998-03-24 2001-09-11 Timothy P. Barber Method and architecture for multi-level commissioned advertising on a computer network
US6721715B2 (en) * 1998-03-30 2004-04-13 Martin A. Nemzow Method and apparatus for localizing currency valuation independent of the original and objective currencies
US6615189B1 (en) 1998-06-22 2003-09-02 Bank One, Delaware, National Association Debit purchasing of stored value card for use by and/or delivery to others
US7809642B1 (en) 1998-06-22 2010-10-05 Jpmorgan Chase Bank, N.A. Debit purchasing of stored value card for use by and/or delivery to others
WO2000011586A1 (en) * 1998-08-20 2000-03-02 Equifax, Inc. System and method for system to system credit information transmission
US9098958B2 (en) * 1998-09-15 2015-08-04 U-Paid Systems, Ltd. Convergent communications platform and method for mobile and electronic commerce in a heterogeneous network environment
US7248855B2 (en) 1998-09-15 2007-07-24 Upaid Systems, Ltd. Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account
IL142004A0 (en) 1998-09-15 2002-03-10 In Touch Technologies Ltd Enhanced communication platform and related communication method using the platform
US7792713B1 (en) 2000-01-24 2010-09-07 Ariba, Inc. Method and system for disguised price bidding in online auctions
US6230146B1 (en) 1998-09-18 2001-05-08 Freemarkets, Inc. Method and system for controlling closing times of electronic auctions involving multiple lots
US7383206B2 (en) * 1999-02-19 2008-06-03 Ariba, Inc. Method and apparatus for multiple variable bidding in an online auction
US7283980B2 (en) * 1999-05-14 2007-10-16 Ariba, Inc. Method and system for controlling the initiation and duration of overtime intervals in electronic auctions
US7249085B1 (en) * 1999-03-31 2007-07-24 Ariba, Inc. Method and system for conducting electronic auctions with multi-parameter price equalization bidding
US7152043B2 (en) * 1999-02-19 2006-12-19 Ariba, Inc. Method and system for dynamically controlling overtime in electronic auctions
US7599878B2 (en) * 1999-02-19 2009-10-06 Ariba, Inc. Method, apparatus, and system for bidding in rounds
JP2002528819A (en) 1998-10-28 2002-09-03 バーティカルワン コーポレイション Automatic aggregation device and method, device and method for delivering electronic personal information or data, and transaction involving electronic personal information or data
US7269575B1 (en) * 1998-11-13 2007-09-11 Jpmorgan Chase Bank, N.A. System and method for processing foreign currency payment instructions contained in bulk files
US7809636B1 (en) 1998-11-13 2010-10-05 Jpmorgan Chase Bank, N.A. System and method for multicurrency and multibank processing over a non-secure network
US6141653A (en) * 1998-11-16 2000-10-31 Tradeaccess Inc System for interative, multivariate negotiations over a network
US6338050B1 (en) * 1998-11-16 2002-01-08 Trade Access, Inc. System and method for providing and updating user supplied context for a negotiations system
US7194442B1 (en) * 1998-11-16 2007-03-20 Sky Technologies, Llc System and method for automated, iterative development negotiations
US6336105B1 (en) * 1998-11-16 2002-01-01 Trade Access Inc. System and method for representing data and providing electronic non-repudiation in a negotiations system
US6332135B1 (en) * 1998-11-16 2001-12-18 Tradeaccess, Inc. System and method for ordering sample quantities over a network
US7660763B1 (en) 1998-11-17 2010-02-09 Jpmorgan Chase Bank, N.A. Customer activated multi-value (CAM) card
US8069407B1 (en) 1998-12-08 2011-11-29 Yodlee.Com, Inc. Method and apparatus for detecting changes in websites and reporting results to web developers for navigation template repair purposes
US7672879B1 (en) 1998-12-08 2010-03-02 Yodlee.Com, Inc. Interactive activity interface for managing personal data and performing transactions over a data packet network
US7085997B1 (en) 1998-12-08 2006-08-01 Yodlee.Com Network-based bookmark management and web-summary system
AU763571B2 (en) 1998-12-23 2003-07-24 Chase Manhattan Bank, The System and method for integrating trading operations including the generation, processing and tracking of and trade documents
US7225152B2 (en) * 1999-02-19 2007-05-29 Ariba, Inc. Method, apparatus, and system for varying an award volume in an auction
US7499876B2 (en) * 1999-02-19 2009-03-03 Ariba, Inc. Method and apparatus for configurably adjusting a bid in an online auction
US7451114B1 (en) 1999-02-19 2008-11-11 Visa International Service Association Conducting commerce between individuals
US20020077959A1 (en) * 1999-02-19 2002-06-20 Marc Alaia Method and system for using line item bid limits in electonic auctions
US6477510B1 (en) * 1999-03-15 2002-11-05 Andrew Johnson, Inc. Euro booking currency conversion method
AU3008099A (en) * 1999-03-17 2000-10-04 Edward M. Rose Billing package for web page utilization
US8510219B1 (en) * 1999-03-17 2013-08-13 Edward M. Rose Billing management package for internet access and web page utilization
US6944595B1 (en) * 1999-03-25 2005-09-13 International Business Machines Corporation Apparatus and method for performing conversion between different units of currency using an encapsulated conversion path of exchange rates
US7333942B1 (en) 1999-03-26 2008-02-19 D-Net Corporation Networked international system for organizational electronic commerce
US7840476B1 (en) 1999-03-31 2010-11-23 Ariba, Inc. Transformation bidding with tooling requirements
US8099359B1 (en) 1999-04-19 2012-01-17 The Western Union Company System and method for issuing negotiable instruments by licensed money transmitter from direct deposits
US7068832B1 (en) 1999-05-11 2006-06-27 The Chase Manhattan Bank Lockbox imaging system
US20040078423A1 (en) * 2002-03-22 2004-04-22 Ramakrishna Satyavolu Method and apparatus for controlled establishment of a turnkey system providing a centralized data aggregation and summary capability to third party entities
US7752535B2 (en) 1999-06-01 2010-07-06 Yodlec.com, Inc. Categorization of summarized information
EP1266317A4 (en) * 1999-06-14 2005-12-14 Integral Dev Corp System and method for conducting web-based financial transactions in capital markets
US7882011B2 (en) 2000-10-31 2011-02-01 Integral Development Corp. Systems and methods of conducting financial transactions
US10387952B1 (en) 1999-11-01 2019-08-20 Integral Development Corporation System and method for conducting web-based financial transactions in capital markets
US8862507B2 (en) * 1999-06-14 2014-10-14 Integral Development Corporation System and method for conducting web-based financial transactions in capital markets
US7197475B1 (en) 1999-06-30 2007-03-27 Catalog City, Inc. Multi-vendor internet commerce system for e-commerce applications and methods therefor
US7062462B1 (en) 1999-07-26 2006-06-13 The Chase Manhattan Bank On-line higher education financing system
US7644037B1 (en) 1999-08-16 2010-01-05 Vladimir Ostrovsky Method and system for transferring electronic funds
US8032457B2 (en) * 1999-08-13 2011-10-04 Vladimir Ostrovsky Method and system for transferring electronic funds
WO2001023975A2 (en) * 1999-09-27 2001-04-05 Ibiz Software Inc. Secure system and method for commerce by credit card
US6363360B1 (en) * 1999-09-27 2002-03-26 Martin P. Madden System and method for analyzing and originating a contractual option arrangement for a bank deposits liabilities base
US7805365B1 (en) 1999-10-25 2010-09-28 Jpmorgan Chase Bank, N.A. Automated statement presentation, adjustment and payment system and method therefor
US7337142B1 (en) * 1999-10-27 2008-02-26 Sun Microsystems, Inc. Multiple exchange rate tracking in a financial transaction manager
WO2001037063A2 (en) * 1999-10-29 2001-05-25 Singleshop.Com System and method of data exchange for electronic transactions with multiple sources
US7571131B1 (en) * 1999-11-05 2009-08-04 Ford Motor Company Method of conducting online competitive price quoting events
SE516782C2 (en) * 1999-11-23 2002-03-05 Ericsson Telefon Ab L M Method of payment of goods in an electronic trading system as well as a payment system
US8571975B1 (en) * 1999-11-24 2013-10-29 Jpmorgan Chase Bank, N.A. System and method for sending money via E-mail over the internet
US8793160B2 (en) 1999-12-07 2014-07-29 Steve Sorem System and method for processing transactions
US7593898B1 (en) 1999-12-30 2009-09-22 First Data Corporation Method and system for payment transactions and shipment tracking over the internet
US7206756B1 (en) 2000-01-14 2007-04-17 Trilogy Development Group, Inc. System and method for facilitating commercial transactions over a data network
US10055772B1 (en) 2000-01-14 2018-08-21 Versata Development Group, Inc. Method and apparatus for product comparison
US7835957B1 (en) 2000-01-24 2010-11-16 Ariba, Inc. Method and system for correcting market failures with participant isolation in dutch style online auctions
US7024383B1 (en) 2000-01-31 2006-04-04 Goldman, Sachs & Co. Online sales risk management system
US7430531B1 (en) 2000-02-04 2008-09-30 Verisign, Inc. System and method for assisting customers in choosing a bundled set of commodities using customer preferences
US7006980B1 (en) 2000-02-04 2006-02-28 Callvision, Inc. Method and system for selecting optimal commodities based upon business profile and preferences
US7822656B2 (en) 2000-02-15 2010-10-26 Jpmorgan Chase Bank, N.A. International banking system and method
US7203663B1 (en) 2000-02-15 2007-04-10 Jpmorgan Chase Bank, N.A. System and method for converting information on paper forms to electronic data
US8768836B1 (en) 2000-02-18 2014-07-01 Jpmorgan Chase Bank, N.A. System and method for electronic deposit of a financial instrument by banking customers from remote locations by use of a digital image
US20020062278A1 (en) * 2000-02-18 2002-05-23 Ingram Bradley Kent Method and system for international e-commerce
WO2001061436A2 (en) * 2000-02-18 2001-08-23 Bank One Corporation System and method for electronic deposit of third-party checks by non-commercial banking customers from remote locations
JP2001243366A (en) * 2000-02-25 2001-09-07 Hitachi Ltd Server having trade job supporting function
KR20010087260A (en) * 2000-03-02 2001-09-15 권선복 An automatic exchange calculation electronic commerce service system and a service method thereof
US7069235B1 (en) 2000-03-03 2006-06-27 Pcorder.Com, Inc. System and method for multi-source transaction processing
US7979347B1 (en) * 2000-03-16 2011-07-12 Goldman Sachs & Co. Automated online sales risk management
EP1301878A2 (en) 2000-03-29 2003-04-16 Mastercard International, Inc. Method and system for processing messages in a bill payment and presentment system over a communications network
WO2001077868A2 (en) * 2000-04-05 2001-10-18 Ruesch International, Inc. System, method and apparatus for international financial transactions
AU2001261531A1 (en) 2000-05-10 2001-11-20 E-Centives, Inc. Using currency to purchase from sellers that do not recognize the currency
US6804657B1 (en) * 2000-05-11 2004-10-12 Oracle International Corp. Methods and systems for global sales forecasting
US7908200B2 (en) * 2000-05-16 2011-03-15 Versata Development Group, Inc. Method and apparatus for efficiently generating electronic requests for quote
US8321356B2 (en) * 2000-05-18 2012-11-27 United Parcel Service Of America, Inc. System and method for calculating real-time costing information
US8725656B1 (en) 2000-05-18 2014-05-13 United Parcel Service Of America, Inc. Freight rate manager
IL136334A0 (en) * 2000-05-24 2001-05-20 Almondnet Inc A method for mercantile negotiation participation
EP1295230A4 (en) * 2000-05-31 2004-12-29 American Int Group Inc Method and system for foreign exchange price procurement and automated hedging
US8543495B1 (en) * 2000-06-12 2013-09-24 E. E. System Corporation Online electronic transaction and funds transfer method and system
US7647259B2 (en) * 2000-06-16 2010-01-12 De Fabrega Ingrid Perscky E-commerce development intranet portal
US6892184B1 (en) * 2000-06-19 2005-05-10 E4X Inc. System and method for multiple currency transactions
US20070038523A1 (en) * 2000-06-19 2007-02-15 E4X Inc. System and method for transactional hedging
US7877312B2 (en) * 2000-06-22 2011-01-25 Wgal, Llp Apparatus and method for displaying trading trends
US7827090B2 (en) * 2000-06-22 2010-11-02 Wgal, Llc Apparatus and method for displaying trading trends
US10185936B2 (en) 2000-06-22 2019-01-22 Jpmorgan Chase Bank, N.A. Method and system for processing internet payments
US7333952B1 (en) * 2000-06-23 2008-02-19 Ebs Group Limited Compound order handling in an anonymous trading system
US7949600B1 (en) * 2000-06-27 2011-05-24 Western Union Financial Services, Inc. Method for facilitating payment of a computerized transaction
WO2002003270A1 (en) * 2000-07-04 2002-01-10 Aai Inc. Commerce method and device, system, and recorded medium
US7024397B1 (en) * 2000-07-05 2006-04-04 J. J. Donahue & Company Method and apparatus for negotiating a real estate lease using a computer network
US20020152168A1 (en) * 2000-07-11 2002-10-17 First Data Corporation Automated transfer with stored value fund
US7996310B1 (en) 2000-07-19 2011-08-09 Globys, Inc. Electronic financial management and analysis system and related methods
US7447661B2 (en) * 2000-07-24 2008-11-04 Raja Ahsan I Electronic bearer bond online transaction system
WO2002008868A2 (en) * 2000-07-26 2002-01-31 Biometrics Imagineering, Inc. Electronic shopping mall
US20070228144A1 (en) * 2000-08-01 2007-10-04 Lee Knackstedt Processing transactions using a register portion to track transactions
US8468071B2 (en) * 2000-08-01 2013-06-18 Jpmorgan Chase Bank, N.A. Processing transactions using a register portion to track transactions
WO2002015098A2 (en) 2000-08-11 2002-02-21 Loy John J Trade receivable processing method and apparatus
US7206768B1 (en) * 2000-08-14 2007-04-17 Jpmorgan Chase Bank, N.A. Electronic multiparty accounts receivable and accounts payable system
EP1182593A1 (en) * 2000-08-22 2002-02-27 Baldev Singh Gill Computer billing system
WO2002019188A1 (en) * 2000-08-29 2002-03-07 Kabushiki Kaisha Toshiba Electronic commerce method and electronic commerce system
AU2001292568A1 (en) * 2000-08-31 2002-03-13 Woodrow Hendricks Danda Control system and method for currency exchange and merchandise sales
DE10050350A1 (en) * 2000-10-11 2002-04-25 Ubs Ag Zuerich Computer system for hedging currency exchange rate risk associated with transaction, determines hedging price based on hedging period and transaction time
US6952683B1 (en) 2000-10-11 2005-10-04 Ubs Ag System and method for hedging against foreign exchange risk associated with securities transactions
US7660740B2 (en) 2000-10-16 2010-02-09 Ebay Inc. Method and system for listing items globally and regionally, and customized listing according to currency or shipping area
US8458018B1 (en) * 2000-10-24 2013-06-04 Jpmorgan Chase Bank, N.A. Electronic trading system and method for marketing products and services
US11526940B2 (en) 2000-10-31 2022-12-13 Integral Development Corporation System and method for conducting web-based financial transactions in capital markets
AU2002230418A1 (en) * 2000-11-06 2002-05-15 The Government Of The United States Of America, As Represented By The Secretary Of Health And Human Services Sample delivery system with laminar mixing for microvolume biosensing
US7587363B2 (en) * 2000-11-06 2009-09-08 Jpmorgan Chase Bank, N.A. System and method for optimized funding of electronic transactions
AU2002224473A1 (en) * 2000-11-06 2002-05-15 Electronic Warfare Associates A system and method for controlling online purchases using an online account
US8285641B2 (en) * 2000-11-06 2012-10-09 Jpmorgan Chase Bank, N.A. System and method for selectable funding of electronic transactions
US20070162387A1 (en) * 2000-11-06 2007-07-12 Cataline Glen R System and method for optimized funding of electronic transactions
US7870054B2 (en) * 2000-11-10 2011-01-11 Ariba, Inc. Method, apparatus and system for advancing a bidder to a selected rank
US7634439B1 (en) * 2000-11-14 2009-12-15 Ariba, Inc. Method and apparatus to perform buy versus leasing transformational bidding
US20020069151A1 (en) * 2000-12-01 2002-06-06 Casper Gary B. Internet real estate auction with buyer pre-approval method
US20020072968A1 (en) * 2000-12-12 2002-06-13 Gorelick Richard B. System and method for incentivizing online sales
US8086518B1 (en) 2000-12-29 2011-12-27 Ariba, Inc. Allotting an award volume in an auction
US20020087456A1 (en) * 2000-12-29 2002-07-04 Daniel Abeshouse Method, apparatus, and system for synchronizing timing of an auction throug a computer network
WO2002054314A1 (en) * 2001-01-03 2002-07-11 Fabrega, Marietta E-commerce development intranet portal
CA2332656A1 (en) * 2001-01-26 2002-07-26 Certapay Inc. Online payment transfer and identity management system and method
US8805739B2 (en) 2001-01-30 2014-08-12 Jpmorgan Chase Bank, National Association System and method for electronic bill pay and presentment
JP4701510B2 (en) * 2001-02-09 2011-06-15 ソニー株式会社 Apparatus and method for aggregating transaction information relating to financial transactions
US7072061B2 (en) * 2001-02-13 2006-07-04 Ariba, Inc. Method and system for extracting information from RFQ documents and compressing RFQ files into a common RFQ file type
US7084998B2 (en) * 2001-02-13 2006-08-01 Ariba, Inc. Method and system for processing files using a printer driver
US7277878B2 (en) 2001-02-13 2007-10-02 Ariba, Inc. Variable length file header apparatus and system
US8380608B2 (en) * 2001-02-15 2013-02-19 Ariba, Inc. System and method for creating a spot market
US20020111895A1 (en) * 2001-02-15 2002-08-15 Blair William R. System and method for creating catalog neutral products
FR2821506A1 (en) * 2001-02-23 2002-08-30 France Telecom METHOD AND DEVICE FOR SECURING A TRANSACTION BETWEEN A TRADER AND A CUSTOMER CARRYING A PAYMENT CARD
SG111911A1 (en) * 2001-02-26 2005-06-29 Fairex Internat Financial Syst Method and system for facilitating foreign currency exchange transactions over a network
US20020174031A1 (en) * 2001-03-06 2002-11-21 Andrew Weiss System and method for processing multi-currency transactions at a point of sale
WO2002075632A1 (en) * 2001-03-19 2002-09-26 Agora Development Corporation Networked international system for organizational electronic commerce
US20110131136A1 (en) * 2001-03-20 2011-06-02 David Lawrence Risk Management Customer Registry
US20040193532A1 (en) * 2001-03-20 2004-09-30 David Lawrence Insider trading risk management
US20040006532A1 (en) * 2001-03-20 2004-01-08 David Lawrence Network access risk management
US8140415B2 (en) 2001-03-20 2012-03-20 Goldman Sachs & Co. Automated global risk management
US8285615B2 (en) 2001-03-20 2012-10-09 Goldman, Sachs & Co. Construction industry risk management clearinghouse
US7904361B2 (en) * 2001-03-20 2011-03-08 Goldman Sachs & Co. Risk management customer registry
US20030233319A1 (en) * 2001-03-20 2003-12-18 David Lawrence Electronic fund transfer participant risk management clearing
US7899722B1 (en) * 2001-03-20 2011-03-01 Goldman Sachs & Co. Correspondent bank registry
US7958027B2 (en) * 2001-03-20 2011-06-07 Goldman, Sachs & Co. Systems and methods for managing risk associated with a geo-political area
US8069105B2 (en) 2001-03-20 2011-11-29 Goldman Sachs & Co. Hedge fund risk management
US20020138417A1 (en) * 2001-03-20 2002-09-26 David Lawrence Risk management clearinghouse
US8209246B2 (en) 2001-03-20 2012-06-26 Goldman, Sachs & Co. Proprietary risk management clearinghouse
US7548883B2 (en) * 2001-03-20 2009-06-16 Goldman Sachs & Co Construction industry risk management clearinghouse
US8121937B2 (en) * 2001-03-20 2012-02-21 Goldman Sachs & Co. Gaming industry risk management clearinghouse
US20030225687A1 (en) * 2001-03-20 2003-12-04 David Lawrence Travel related risk management clearinghouse
US20020143562A1 (en) * 2001-04-02 2002-10-03 David Lawrence Automated legal action risk management
US7480638B1 (en) * 2001-04-03 2009-01-20 Ebay Inc. Method and system automatically to remind parties to a network-based transaction to comply with obligations established under a transaction agreement
US7082416B2 (en) * 2001-04-06 2006-07-25 Karyn Elaine Anderson Method of using prepaid cash card for making purchases on the world wide web
US7593884B2 (en) * 2001-04-10 2009-09-22 Goldman Sachs & Co. Multi-currency marketplace
JP2002334285A (en) * 2001-05-10 2002-11-22 Hitachi Ltd System for performing a plurality of electronic money account settlements as agent
US20020174065A1 (en) * 2001-05-18 2002-11-21 Chalice Coward Multi-currency electronic payment system and terminal emulator
US7313546B2 (en) * 2001-05-23 2007-12-25 Jp Morgan Chase Bank, N.A. System and method for currency selectable stored value instrument
US7865427B2 (en) 2001-05-30 2011-01-04 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US6659259B2 (en) * 2001-06-01 2003-12-09 Datawave Systems, Inc. Multiple denomination currency receiving and prepaid card dispensing method and apparatus
US7401048B2 (en) * 2001-06-01 2008-07-15 Jpmorgan Chase Bank, N.A. System and method for trade settlement tracking and relative ranking
US20020198814A1 (en) * 2001-06-22 2002-12-26 International Business Machines Corporation Online e-commerce transactions incorporating determination of end-to-end costs
FI112468B (en) * 2001-06-28 2003-12-15 Kone Corp Method for repayment of elevator investment costs
CN1545668A (en) * 2001-07-05 2004-11-10 却克波特特许公司 Transaction processing system and method
US7483857B2 (en) * 2001-07-09 2009-01-27 International Business Machines Corporation Online e-commerce transactions incorporating effects of uncertainty and risk factors
US7860789B2 (en) 2001-07-24 2010-12-28 Jpmorgan Chase Bank, N.A. Multiple account advanced payment card and method of routing card transactions
US20030033250A1 (en) * 2001-08-10 2003-02-13 Bob Mayes System and method for automatic terminal management
US7306141B1 (en) * 2001-08-13 2007-12-11 Jpmorgan Chase Bank, N.A. System and method for funding a collective account by use of an electronic tag
US8020754B2 (en) 2001-08-13 2011-09-20 Jpmorgan Chase Bank, N.A. System and method for funding a collective account by use of an electronic tag
US7249069B2 (en) * 2001-08-27 2007-07-24 United Parcel Service Of America, Inc. International cash-on-delivery system and method
US20030069836A1 (en) * 2001-09-11 2003-04-10 Neill Penney Method and apparatus for amending financial transactions
US20030069789A1 (en) * 2001-10-04 2003-04-10 Koninklijke Philips Electronics N.V. System and business method for offering seat upgrades to patrons at a public facility
US7822684B2 (en) * 2001-10-05 2010-10-26 Jpmorgan Chase Bank, N.A. Personalized bank teller machine
US6975996B2 (en) * 2001-10-09 2005-12-13 Goldman, Sachs & Co. Electronic subpoena service
US7752266B2 (en) 2001-10-11 2010-07-06 Ebay Inc. System and method to facilitate translation of communications between entities over a network
GB2381089A (en) 2001-10-15 2003-04-23 Chequepoint Franchise Corp A computerized money transfer system and method
US8032454B2 (en) * 2001-10-18 2011-10-04 International Business Machines Corporation Import declaration/foreign supplier invoice payment reconciliation process
US7822679B1 (en) 2001-10-29 2010-10-26 Visa U.S.A. Inc. Method and system for conducting a commercial transaction between a buyer and a seller
US20030088497A1 (en) * 2001-11-02 2003-05-08 Belgrano Eduardo J. Combination currency/barter system
US7536362B2 (en) * 2001-11-07 2009-05-19 Ariba, Inc. Method for selecting an optimal balance between direct cost and a number of suppliers
AU2002367595A1 (en) * 2001-11-28 2003-09-22 Goldman, Sachs And Co. Transaction surveillance
US8108249B2 (en) 2001-12-04 2012-01-31 Kimberly-Clark Worldwide, Inc. Business planner
US20030115127A1 (en) * 2001-12-18 2003-06-19 Freemarkets, Inc. Method of market basket bidding for surplus merchandise
US20030120567A1 (en) * 2001-12-21 2003-06-26 Lee Macklin System for and method of application currency conversion
US8126799B2 (en) * 2002-01-09 2012-02-28 Ariba, Inc. Method of bidding to drive competition in an auction
US20030135444A1 (en) * 2002-01-15 2003-07-17 Nachiappan Annamalai Multiple award optimization
US7146331B1 (en) 2002-01-17 2006-12-05 Ariba, Inc. Method and system for supplier prioritization
US20030154153A1 (en) * 2002-01-31 2003-08-14 Steidlmayer J. Peter Composite commodity financial product
US20030171948A1 (en) * 2002-02-13 2003-09-11 United Parcel Service Of America, Inc. Global consolidated clearance methods and systems
US7756896B1 (en) 2002-03-11 2010-07-13 Jp Morgan Chase Bank System and method for multi-dimensional risk analysis
US7899753B1 (en) 2002-03-25 2011-03-01 Jpmorgan Chase Bank, N.A Systems and methods for time variable financial authentication
US20040210498A1 (en) 2002-03-29 2004-10-21 Bank One, National Association Method and system for performing purchase and other transactions using tokens with multiple chips
AU2003230751A1 (en) 2002-03-29 2003-10-13 Bank One, Delaware, N.A. System and process for performing purchase transaction using tokens
US7483852B2 (en) * 2002-04-24 2009-01-27 Ariba, Inc. Total value bidding
US20030220858A1 (en) * 2002-05-24 2003-11-27 Duc Lam Method and system for collaborative vendor reconciliation
US7689482B2 (en) 2002-05-24 2010-03-30 Jp Morgan Chase Bank, N.A. System and method for payer (buyer) defined electronic invoice exchange
US20030220863A1 (en) 2002-05-24 2003-11-27 Don Holm System and method for varying electronic settlements between buyers and suppliers with dynamic discount terms
US7437327B2 (en) * 2002-05-24 2008-10-14 Jp Morgan Chase Bank Method and system for buyer centric dispute resolution in electronic payment system
US8078505B2 (en) 2002-06-10 2011-12-13 Ebay Inc. Method and system for automatically updating a seller application utilized in a network-based transaction facility
EP1552449A4 (en) * 2002-06-19 2007-12-12 Fx Alliance Llc Method and apparatus for managing financial transactions involving multiple counterparties and processing data pertaining thereto
US20040006530A1 (en) * 2002-07-03 2004-01-08 Freemarkets, Inc. Automated lotting
US8239304B1 (en) 2002-07-29 2012-08-07 Jpmorgan Chase Bank, N.A. Method and system for providing pre-approved targeted products
US7974908B1 (en) 2002-07-29 2011-07-05 Ariba, Inc. System and method for promoting competition in an auction
US8554650B1 (en) 2002-07-31 2013-10-08 Ariba, Inc. Importable template
GB0218020D0 (en) * 2002-08-02 2002-09-11 Omnipay Ltd Currency recognition system
SG145524A1 (en) * 2002-08-07 2008-09-29 Mobilastic Technologies Pte Lt Secure transfer of digital tokens
US6876979B2 (en) * 2002-08-12 2005-04-05 Paybyclick Corporation Electronic commerce bridge system
US7809595B2 (en) 2002-09-17 2010-10-05 Jpmorgan Chase Bank, Na System and method for managing risks associated with outside service providers
US20040078331A1 (en) * 2002-10-17 2004-04-22 Fakih Adonis El Payment system using electronic stamps
US7330835B2 (en) * 2002-10-31 2008-02-12 Federal Reserve Bank Of Minneapolis Method and system for tracking and reporting automated clearing house transaction status
US7792716B2 (en) * 2002-10-31 2010-09-07 Federal Reserve Bank Of Atlanta Searching for and identifying automated clearing house transactions by transaction type
US7693747B2 (en) * 2002-10-31 2010-04-06 Ariba, Inc. Methods, system, and medium for initiating an online auction utilizing a line item detail report
KR20050074986A (en) 2002-11-07 2005-07-19 플래닛 그룹 인코포레이티드 Time-of-transaction foreign currency conversion
WO2004047082A2 (en) * 2002-11-14 2004-06-03 Goldman, Sachs & Co. Independent research consensus earnings estimates and methods of determining such
US7742980B1 (en) 2002-11-15 2010-06-22 Imx, Inc. Automated loan approval system
US7769650B2 (en) 2002-12-03 2010-08-03 Jp Morgan Chase Bank Network-based sub-allocation systems and methods for swaps
US20080040163A1 (en) * 2002-12-13 2008-02-14 James Lacy Harlin System and method for paying and receiving agency commissions
US8126701B2 (en) * 2003-01-31 2012-02-28 Ariba, Inc. Translation technology in electronic sourcing
JP2004240858A (en) * 2003-02-07 2004-08-26 Nec Corp Electronic money system, electronic money exchange server and portable terminal
US20040167863A1 (en) * 2003-02-21 2004-08-26 Knowles W. Jeffrey System and method of transferring data through transaction process
US8041633B2 (en) * 2003-02-21 2011-10-18 Mtrex, Inc. System and method of electronic data transaction processing
US20040187108A1 (en) * 2003-02-21 2004-09-23 Knowles W. Jeffrey Method of scheduling and event processing in computer operating system
US20040167854A1 (en) * 2003-02-21 2004-08-26 Knowles W. Jeffrey System and method of currency conversion in financial transaction process
US10311412B1 (en) 2003-03-28 2019-06-04 Jpmorgan Chase Bank, N.A. Method and system for providing bundled electronic payment and remittance advice
US8630947B1 (en) 2003-04-04 2014-01-14 Jpmorgan Chase Bank, N.A. Method and system for providing electronic bill payment and presentment
US9881308B2 (en) 2003-04-11 2018-01-30 Ebay Inc. Method and system to facilitate an online promotion relating to a network-based marketplace
US8027901B2 (en) * 2003-05-23 2011-09-27 Omx Technology Ab Automatic generation of an order in an instrument in a specified currency
US20040236647A1 (en) * 2003-05-23 2004-11-25 Ravi Acharya Electronic checkbook register
US8306907B2 (en) 2003-05-30 2012-11-06 Jpmorgan Chase Bank N.A. System and method for offering risk-based interest rates in a credit instrument
US7742985B1 (en) * 2003-06-26 2010-06-22 Paypal Inc. Multicurrency exchanges between participants of a network-based transaction facility
US8156040B2 (en) * 2003-07-03 2012-04-10 Federal Reserve Bank Of Minneapolis Method and system for conducting international electronic financial transactions
US20050010495A1 (en) * 2003-07-07 2005-01-13 Pochun Shih Custom product order management system
US7668777B2 (en) * 2003-07-25 2010-02-23 Jp Morgan Chase Bank System and method for providing instant-decision, financial network-based payment cards
US20050027648A1 (en) * 2003-07-29 2005-02-03 Knowles W. Jeffrey System and method of account reconciliation for electronic transactions
WO2005017694A2 (en) * 2003-08-11 2005-02-24 Jp Morgan Chase Bank Coupon payment system
US20050038739A1 (en) * 2003-08-13 2005-02-17 Ncr Corporation Methods of processing payment in an electronic commercial transaction and a payment consolidator therefor
US7953663B1 (en) 2003-09-04 2011-05-31 Jpmorgan Chase Bank, N.A. System and method for financial instrument pre-qualification and offering
US8543477B2 (en) * 2003-09-30 2013-09-24 Federal Reserve Bank Of Atlanta Value tracking and reporting of automated clearing house transactions
US8417636B2 (en) * 2003-09-30 2013-04-09 Federal Reserve Bank Of Atlanta Approving ACH operator processing of ACH payments based on an originating depository financial institution's approved originator list
US20050182713A1 (en) * 2003-10-01 2005-08-18 Giancarlo Marchesi Methods and systems for the auto reconsideration of credit card applications
US20050114258A1 (en) * 2003-10-08 2005-05-26 Neill Penney Fix-enabled order management method and apparatus
US7792717B1 (en) * 2003-10-31 2010-09-07 Jpmorgan Chase Bank, N.A. Waterfall prioritized payment processing
US7702577B1 (en) 2003-11-06 2010-04-20 Jp Morgan Chase Bank, N.A. System and method for conversion of initial transaction to final transaction
US7536343B2 (en) * 2003-11-26 2009-05-19 Fx Alliance, Llc Protocol-independent asset trading system and methods
EP1697892A4 (en) * 2003-11-26 2008-04-09 Fx Alliance Llc Quick-filling customer asset trading system
SG132684A1 (en) * 2003-11-26 2007-06-28 Fx Alliance Llc Latency-aware asset trading system
US7814003B2 (en) 2003-12-15 2010-10-12 Jp Morgan Chase Billing workflow system for crediting charges to entities creating derivatives exposure
CA2988148C (en) * 2003-12-30 2020-11-17 United Parcel Service Of America, Inc. Integrated global tracking and virtual inventory system
US20090313163A1 (en) * 2004-02-13 2009-12-17 Wang ming-huan Credit line optimization
US7380707B1 (en) 2004-02-25 2008-06-03 Jpmorgan Chase Bank, N.A. Method and system for credit card reimbursements for health care transactions
US7702767B2 (en) * 2004-03-09 2010-04-20 Jp Morgan Chase Bank User connectivity process management system
US7725406B2 (en) * 2004-03-30 2010-05-25 United Parcel Service Of America, Inc. Systems and methods for international shipping and brokerage operations support processing
US8175938B2 (en) 2004-04-13 2012-05-08 Ebay Inc. Method and system for facilitating merchant-initiated online payments
US20050273347A1 (en) * 2004-06-04 2005-12-08 Bank One, Delaware, National Association Method and system for processing payment items at a central processor
US7480630B2 (en) * 2004-06-04 2009-01-20 Sap Ag Method for allocating financial values across multiple accounts using precise values
US8571977B2 (en) * 2004-06-17 2013-10-29 Visa International Service Association Method and system for providing seller bank receivable discounting aggregation services
US8554673B2 (en) 2004-06-17 2013-10-08 Jpmorgan Chase Bank, N.A. Methods and systems for discounts management
US20060015439A1 (en) * 2004-06-23 2006-01-19 Brann John E T Shareable quote streams
WO2006002171A2 (en) * 2004-06-23 2006-01-05 Fx Alliance, Llc Dynamic liquidity management system
US8121944B2 (en) * 2004-06-24 2012-02-21 Jpmorgan Chase Bank, N.A. Method and system for facilitating network transaction processing
US8510300B2 (en) 2004-07-02 2013-08-13 Goldman, Sachs & Co. Systems and methods for managing information associated with legal, compliance and regulatory risk
US8762191B2 (en) * 2004-07-02 2014-06-24 Goldman, Sachs & Co. Systems, methods, apparatus, and schema for storing, managing and retrieving information
US8996481B2 (en) * 2004-07-02 2015-03-31 Goldman, Sach & Co. Method, system, apparatus, program code and means for identifying and extracting information
US8442953B2 (en) 2004-07-02 2013-05-14 Goldman, Sachs & Co. Method, system, apparatus, program code and means for determining a redundancy of information
US8016185B2 (en) 2004-07-06 2011-09-13 Visa International Service Association Money transfer service with authentication
US8290862B2 (en) * 2004-07-23 2012-10-16 Jpmorgan Chase Bank, N.A. Method and system for expediting payment delivery
US8290863B2 (en) * 2004-07-23 2012-10-16 Jpmorgan Chase Bank, N.A. Method and system for expediting payment delivery
AU2005278141A1 (en) * 2004-07-27 2006-03-02 Jp Morgan Chase Bank System and method for measuring communication-system infrastructure usage
US7881996B1 (en) 2004-08-03 2011-02-01 Federal Reserve Bank Of Atlanta Method and system for screening financial transactions
US7392222B1 (en) 2004-08-03 2008-06-24 Jpmorgan Chase Bank, N.A. System and method for providing promotional pricing
US8533030B1 (en) 2004-08-30 2013-09-10 Jpmorgan Chase Bank, N.A. In-bound telemarketing system for processing customer offers
US7580886B1 (en) * 2004-09-15 2009-08-25 Federal Reserve Bank Of Atlanta Managing foreign payments in an international ACH
US20060089891A1 (en) * 2004-10-21 2006-04-27 Nigam Rakesh K System and method for generating expense information
US20060095374A1 (en) * 2004-11-01 2006-05-04 Jp Morgan Chase System and method for supply chain financing
US7685064B1 (en) 2004-11-30 2010-03-23 Jp Morgan Chase Bank Method and apparatus for evaluating a financial transaction
US7996351B1 (en) * 2004-12-16 2011-08-09 Apple Inc. Automated estimation of a country where a client computer is configured to operate
US8265991B1 (en) 2004-12-16 2012-09-11 Apple Inc. Automated determination of applicability and value of discounts for a purchase order
US20060287966A1 (en) * 2004-12-21 2006-12-21 Oracle International Corporation Methods and systems for authoring customized contracts using contract templates that include user-configured rules and questions
US7634438B2 (en) * 2004-12-23 2009-12-15 Fx Alliance, Llc Dynamic account mapping system for computerized asset trading
US20060147894A1 (en) * 2004-12-30 2006-07-06 Vicam, L.P. Jacketed vessel for holding semen for sex biasing mammals through artificial insemination and systems and methods for enhancing the probability of sex biasing using the same
US7711639B2 (en) * 2005-01-12 2010-05-04 Visa International Pre-funding system and method
US20100121743A1 (en) * 2005-04-13 2010-05-13 Jp Morgan Chase Bank System and method for generating dividend information
US7698185B2 (en) * 2005-04-28 2010-04-13 Loylogic, Inc. Methods and systems for generating dynamic reward currency values
US7401731B1 (en) 2005-05-27 2008-07-22 Jpmorgan Chase Bank, Na Method and system for implementing a card product with multiple customized relationships
US7739165B2 (en) 2005-06-03 2010-06-15 Jpmorgan Chase Bank Method and system for issuing convertible preferred securities
US7822682B2 (en) 2005-06-08 2010-10-26 Jpmorgan Chase Bank, N.A. System and method for enhancing supply chain transactions
US7676409B1 (en) 2005-06-20 2010-03-09 Jpmorgan Chase Bank, N.A. Method and system for emulating a private label over an open network
US7590590B2 (en) * 2005-06-28 2009-09-15 Jpmorgan Chase Bank Method and system for exchangeable bundled option and no-principal debt securities
US20070011065A1 (en) * 2005-07-07 2007-01-11 Santosh Sreenivasan Method and system for pre-funding with merger call flexibility
US20070011068A1 (en) * 2005-07-08 2007-01-11 Zajkowski Jeffrey J Method and system for net share settlement of a convertible bond
US7925578B1 (en) 2005-08-26 2011-04-12 Jpmorgan Chase Bank, N.A. Systems and methods for performing scoring optimization
US8874477B2 (en) 2005-10-04 2014-10-28 Steven Mark Hoffberg Multifactorial optimization system and method
US7895114B2 (en) * 2005-10-28 2011-02-22 Jpmorgan Chase Bank, N.A. Method and system for repatriating earnings
US8301529B1 (en) 2005-11-02 2012-10-30 Jpmorgan Chase Bank, N.A. Method and system for implementing effective governance of transactions between trading partners
US20080040249A1 (en) * 2006-01-20 2008-02-14 Jpmorgan Chase Bank, N.A. Method for transaction processing in a capture and deposit
US8489497B1 (en) 2006-01-27 2013-07-16 Jpmorgan Chase Bank, N.A. Online interactive and partner-enhanced credit card
US7784682B2 (en) 2006-02-08 2010-08-31 Jpmorgan Chase Bank, N.A. System and method for granting promotional rewards to both customers and non-customers
US8408455B1 (en) 2006-02-08 2013-04-02 Jpmorgan Chase Bank, N.A. System and method for granting promotional rewards to both customers and non-customers
US7753259B1 (en) 2006-04-13 2010-07-13 Jpmorgan Chase Bank, N.A. System and method for granting promotional rewards to both customers and non-customers
US8732044B2 (en) 2006-05-23 2014-05-20 Mastercard International Incorporated Electronic transaction apparatus and method
US7703673B2 (en) 2006-05-25 2010-04-27 Buchheit Brian K Web based conversion of non-negotiable credits associated with an entity to entity independent negotiable funds
US8668146B1 (en) 2006-05-25 2014-03-11 Sean I. Mcghie Rewards program with payment artifact permitting conversion/transfer of non-negotiable credits to entity independent funds
US8684265B1 (en) 2006-05-25 2014-04-01 Sean I. Mcghie Rewards program website permitting conversion/transfer of non-negotiable credits to entity independent funds
US9704174B1 (en) 2006-05-25 2017-07-11 Sean I. Mcghie Conversion of loyalty program points to commerce partner points per terms of a mutual agreement
US10062062B1 (en) 2006-05-25 2018-08-28 Jbshbm, Llc Automated teller machine (ATM) providing money for loyalty points
US7734545B1 (en) 2006-06-14 2010-06-08 Jpmorgan Chase Bank, N.A. Method and system for processing recurring payments
US7540408B2 (en) * 2006-06-22 2009-06-02 Hip Consult Inc. Apparatus and method for facilitating money or value transfer
US8584107B2 (en) * 2006-07-07 2013-11-12 United Parcel Service Of America, Inc. Compiled data for software applications
US8639782B2 (en) 2006-08-23 2014-01-28 Ebay, Inc. Method and system for sharing metadata between interfaces
US7606752B2 (en) 2006-09-07 2009-10-20 Yodlee Inc. Host exchange in bill paying services
US20080071630A1 (en) * 2006-09-14 2008-03-20 J.J. Donahue & Company Automatic classification of prospects
US20080071664A1 (en) * 2006-09-18 2008-03-20 Reuters America, Inc. Limiting Counter-Party Risk in Multiple Party Transactions
US20080147516A1 (en) * 2006-09-29 2008-06-19 Armand Rousso Systems, methods and apparatuses for a payment facilitation engine
US7945496B2 (en) * 2006-10-18 2011-05-17 Pricemetrix, Inc. Reference price framework
US8060437B2 (en) * 2006-10-31 2011-11-15 International Funding Partners Llc Automatic termination of electronic transactions
US20080114684A1 (en) * 2006-10-31 2008-05-15 Chuck Foster Termination of transactions
US20080103966A1 (en) * 2006-10-31 2008-05-01 Chuck Foster System and/or method for dynamic determination of transaction processing fees
DE102007040675A1 (en) * 2006-11-13 2008-05-15 Abb Technology Ag System and method for the lossless processing of process values of a technical plant or a technical process
US7809652B2 (en) * 2007-01-30 2010-10-05 Visa U.S.A. Inc. Signature based negative list for off line payment device validation
US7916925B2 (en) 2007-02-09 2011-03-29 Jpmorgan Chase Bank, N.A. System and method for generating magnetic ink character recognition (MICR) testing documents
US20090030822A1 (en) * 2007-03-12 2009-01-29 Jpmorgan Chase Bank, N.A. System and Method for Contingent Equity Return Forward to Hedge Foreign Exchange Risk in Investments Having Varying Exit Parameters
US20080306784A1 (en) * 2007-06-05 2008-12-11 Vijay Rajkumar Computer-implemented methods and systems for analyzing clauses of contracts and other business documents
US8037004B2 (en) 2007-06-11 2011-10-11 Oracle International Corporation Computer-implemented methods and systems for identifying and reporting deviations from standards and policies for contracts, agreements and other business documents
US8676642B1 (en) 2007-07-05 2014-03-18 Jpmorgan Chase Bank, N.A. System and method for granting promotional rewards to financial account holders
US8762270B1 (en) 2007-08-10 2014-06-24 Jpmorgan Chase Bank, N.A. System and method for providing supplemental payment or transaction information
US8738518B2 (en) * 2007-08-28 2014-05-27 The Western Union Company Methods and systems for executing a plurality of money transfers having a fluctuating parameter
US8788278B2 (en) * 2007-08-28 2014-07-22 Moneygram International, Inc. Consumer database loyalty program for a money transfer system
US7640212B2 (en) * 2007-08-28 2009-12-29 The Western Union Company Methods and systems for executing a plurality of money transfers having a fluctuating parameter
US20090070256A1 (en) * 2007-09-04 2009-03-12 Skycash Sp. Z O.O. Systems and methods for payment
US8417601B1 (en) 2007-10-18 2013-04-09 Jpmorgan Chase Bank, N.A. Variable rate payment card
US8019679B2 (en) * 2007-10-18 2011-09-13 Moneygram International, Inc. Global compliance processing system for a money transfer system
US20090112759A1 (en) * 2007-10-30 2009-04-30 Chuck Foster Accumulated transactions
WO2009064884A2 (en) * 2007-11-15 2009-05-22 Ronald Scheman System and method for international internet shopping
US8788281B1 (en) 2007-12-03 2014-07-22 Jp Morgan Chase Bank, N.A. System and method for processing qualified healthcare account related financial transactions
US8694424B2 (en) 2007-12-18 2014-04-08 Federal Reserve Bank Of Atlanta System and method for managing foreign payments using separate messaging and settlement mechanisms
US8622308B1 (en) 2007-12-31 2014-01-07 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
US7766244B1 (en) 2007-12-31 2010-08-03 Jpmorgan Chase Bank, N.A. System and method for processing transactions using a multi-account transactions device
WO2009088487A1 (en) * 2008-01-04 2009-07-16 Planet Payment, Inc. Merchant rate lookup
US8725611B1 (en) 2008-02-21 2014-05-13 Jpmorgan Chase Bank, N.A. System and method for providing borrowing schemes
US20090248574A1 (en) * 2008-03-28 2009-10-01 Leung Florence F L Peer-to-peer currency exchange and associated systems and methods
US8261334B2 (en) 2008-04-25 2012-09-04 Yodlee Inc. System for performing web authentication of a user by proxy
US20090281946A1 (en) * 2008-05-12 2009-11-12 Davis Peter A ACH Payment Processing
CN101655947A (en) * 2008-08-21 2010-02-24 阿里巴巴集团控股有限公司 Online transaction method and online transaction system for realizing off-shore transaction
US20100057548A1 (en) * 2008-08-27 2010-03-04 Globy's,Inc. Targeted customer offers based on predictive analytics
US8112355B1 (en) 2008-09-05 2012-02-07 Jpmorgan Chase Bank, N.A. Method and system for buyer centric dispute resolution in electronic payment system
US10970777B2 (en) 2008-09-15 2021-04-06 Mastercard International Incorporated Apparatus and method for bill payment card enrollment
US7860772B2 (en) * 2008-09-30 2010-12-28 Ebay, Inc. Funding on-line accounts
US20100100426A1 (en) * 2008-10-16 2010-04-22 Moneygram International, Inc. Agent management system
US8391584B2 (en) 2008-10-20 2013-03-05 Jpmorgan Chase Bank, N.A. Method and system for duplicate check detection
US9092447B1 (en) 2008-10-20 2015-07-28 Jpmorgan Chase Bank, N.A. Method and system for duplicate detection
US20100114774A1 (en) * 2008-11-04 2010-05-06 Moneygram International, Inc. Chargeback decisioning system
US8555359B2 (en) * 2009-02-26 2013-10-08 Yodlee, Inc. System and methods for automatically accessing a web site on behalf of a client
US8595134B2 (en) 2010-02-12 2013-11-26 Mastercard International Incorporated Apparatus and method for bill presentment and payment
US8447641B1 (en) 2010-03-29 2013-05-21 Jpmorgan Chase Bank, N.A. System and method for automatically enrolling buyers into a network
US8429020B2 (en) * 2010-04-23 2013-04-23 Ebay Inc. Currency weighted cross border listing exposure
US8484136B2 (en) * 2010-04-26 2013-07-09 Ca, Inc. Brokering and payment optimization for cloud computing
US8589288B1 (en) 2010-10-01 2013-11-19 Jpmorgan Chase Bank, N.A. System and method for electronic remittance of funds
US8732093B2 (en) 2011-01-26 2014-05-20 United Parcel Service Of America, Inc. Systems and methods for enabling duty determination for a plurality of commingled international shipments
US8700510B2 (en) 2011-02-11 2014-04-15 Federal Reserve Bank Of Atlanta Redirecting or returning international credit transfers
US8543503B1 (en) 2011-03-30 2013-09-24 Jpmorgan Chase Bank, N.A. Systems and methods for automated invoice entry
US8543504B1 (en) 2011-03-30 2013-09-24 Jpmorgan Chase Bank, N.A. Systems and methods for automated invoice entry
US10318932B2 (en) * 2011-06-07 2019-06-11 Entit Software Llc Payment card processing system with structure preserving encryption
US9721237B2 (en) * 2011-06-24 2017-08-01 Paypal, Inc. Animated two-dimensional barcode checks
US9984367B2 (en) * 2011-06-24 2018-05-29 Amazon Technologies, Inc. Paying non-settlement transactions
US20130030924A1 (en) 2011-07-28 2013-01-31 American Express Travel Related Services Company, Inc. Systems and methods for generating and using a digital pass
US10402795B2 (en) 2012-01-05 2019-09-03 Moneygram International, Inc. Prefunding for money transfer send transactions
US8738520B2 (en) 2012-04-23 2014-05-27 Moneygram International, Inc. Send and receive side control of money transfer parameters
USD678653S1 (en) 2012-07-19 2013-03-19 Jpmorgan Chase Bank, N.A. Drive-up financial transaction machine
US20140143073A1 (en) * 2012-11-16 2014-05-22 Abraham Doris-Down Converted Currency Display
US8657688B1 (en) 2012-11-26 2014-02-25 Moneygram International, Inc. Promotion generation engine for a money transfer system
US10296968B2 (en) 2012-12-07 2019-05-21 United Parcel Service Of America, Inc. Website augmentation including conversion of regional content
US10755245B2 (en) 2013-02-25 2020-08-25 Moneygram International, Inc. Money transfer system having location based language and dynamic receipt capabilities
USD690074S1 (en) 2013-03-13 2013-09-17 Jpmorgan Chase Bank, N.A. Financial transaction machine
US10192204B2 (en) * 2013-08-01 2019-01-29 Moneygram International, Inc. System and method for staging money transfers between users having profiles
US20150112856A1 (en) * 2013-10-22 2015-04-23 Kouros Ershadi System and Method for Facilitating International Money Transfers
US9058626B1 (en) 2013-11-13 2015-06-16 Jpmorgan Chase Bank, N.A. System and method for financial services device usage
US9449346B1 (en) 2014-05-21 2016-09-20 Plaid Technologies, Inc. System and method for programmatically accessing financial data
US9595023B1 (en) 2014-05-21 2017-03-14 Plaid Technologies, Inc. System and method for facilitating programmatic verification of transactions
US9965466B2 (en) 2014-07-16 2018-05-08 United Parcel Service Of America, Inc. Language content translation
US10104059B2 (en) 2015-09-08 2018-10-16 Plaid Technologies, Inc. Secure permissioning of access to user accounts, including secure deauthorization of access to user accounts
US20170161762A1 (en) * 2015-12-08 2017-06-08 Formula Technologies, Inc. Financial Monitoring and Forecasting Systems and Methods
US10726491B1 (en) 2015-12-28 2020-07-28 Plaid Inc. Parameter-based computer evaluation of user accounts based on user account data stored in one or more databases
US10984468B1 (en) 2016-01-06 2021-04-20 Plaid Inc. Systems and methods for estimating past and prospective attribute values associated with a user account
US10177691B2 (en) 2016-07-06 2019-01-08 Black & Decker Inc. Electronic braking of brushless DC motor in a power tool
US11468085B2 (en) 2017-07-22 2022-10-11 Plaid Inc. Browser-based aggregation
US10878421B2 (en) 2017-07-22 2020-12-29 Plaid Inc. Data verified deposits
US11263603B1 (en) 2017-07-26 2022-03-01 Square, Inc. Security asset packs
US10055715B1 (en) 2017-07-26 2018-08-21 Square, Inc. Cryptocurrency payment network
US10754871B2 (en) * 2017-12-05 2020-08-25 Oracle International Corporation Context-sensitive data retrieval and conversion
CN108734582A (en) * 2018-05-21 2018-11-02 深圳市富途网络科技有限公司 A kind of securities account management method based on social relations and system
US11316862B1 (en) 2018-09-14 2022-04-26 Plaid Inc. Secure authorization of access to user accounts by one or more authorization mechanisms
US10248527B1 (en) 2018-09-19 2019-04-02 Amplero, Inc Automated device-specific dynamic operation modifications
US20200242573A1 (en) * 2019-01-24 2020-07-30 Sensoriant, Inc. Cryptographic transactions supporting real world requirements
CA3128497A1 (en) * 2019-01-31 2020-08-06 KlickTrack, Inc. Retail platform
FR3095540A1 (en) * 2019-04-24 2020-10-30 Amadeus Sas Method for processing a set of orders in a computerized environment
US11887069B2 (en) 2020-05-05 2024-01-30 Plaid Inc. Secure updating of allocations to user accounts
US11121989B1 (en) 2020-05-29 2021-09-14 Bank Of America Corporation Centralized repository and communication system for cross-network interactions
US11348041B2 (en) 2020-07-02 2022-05-31 Bank Of America Corporation System for predictive resource access within a technical environment
US11327960B1 (en) 2020-10-16 2022-05-10 Plaid Inc. Systems and methods for data parsing

Citations (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3652795A (en) * 1970-11-25 1972-03-28 Electrospace Corp Telephone transaction system
US4251867A (en) * 1978-03-25 1981-02-17 Laurel Bank Machine Co., Ltd. Money exchanger apparatus
EP0251619A2 (en) * 1986-06-26 1988-01-07 Visa International Service Association Portable transaction card
EP0254812A2 (en) * 1986-06-27 1988-02-03 International Business Machines Corporation Cryptovariable initialisation in a public key network
US4812628A (en) * 1985-05-02 1989-03-14 Visa International Service Association Transaction system with off-line risk assessment
US4823264A (en) * 1986-05-27 1989-04-18 Deming Gilbert R Electronic funds transfer system
US4837422A (en) * 1987-09-08 1989-06-06 Juergen Dethloff Multi-user card system
US4877947A (en) * 1986-08-05 1989-10-31 Oki Electric Industry Co., Ltd. Transaction processing system
WO1991016691A1 (en) * 1990-04-12 1991-10-31 Jonhig Limited Value transfer system
GB2261579A (en) * 1990-07-23 1993-05-19 Ericsson Ge Mobile Communicat Authentication system for digital cellular communications
EP0542298A2 (en) * 1991-11-15 1993-05-19 Citibank, N.A. Electronic monetary system
DE4308597A1 (en) * 1993-03-18 1993-08-19 Marc Bode Electronic bank account unit with inter account link - provided by infrared communication with units having keyboard display and built in processing.
EP0590861A2 (en) * 1992-09-29 1994-04-06 AT&T Corp. Secure credit/debit card authorization
US5369705A (en) * 1992-06-03 1994-11-29 International Business Machines Corporation Multi-party secure session/conference
WO1995012169A1 (en) * 1993-10-25 1995-05-04 Visa International Service Association A method and apparatus for disbributing currency
US5440634A (en) * 1991-10-16 1995-08-08 Jonhig Limited Value transfer system
GB2296413A (en) * 1994-07-05 1996-06-26 Motorola Inc A method of messaging in a communciation system
US5535276A (en) * 1994-11-09 1996-07-09 Bell Atlantic Network Services, Inc. Yaksha, an improved system and method for securing communications using split private key asymmetric cryptography
US5557518A (en) * 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
WO1996033568A1 (en) * 1995-04-18 1996-10-24 Hewlett-Packard Company Methods and apparatus for authenticating an originator of a message
WO1996036024A1 (en) * 1995-05-12 1996-11-14 Koninklijke Ptt Nederland N.V. Electronic payment system having several calculation units, electronic payment means, as well as a method for electronic payment
GB2301919A (en) * 1995-06-05 1996-12-18 Bankers Trust Co Multi-step digital signature method and system
WO1997004411A1 (en) * 1995-07-24 1997-02-06 Citibank, N.A. Customer-directed, automated system for transferring funds between accounts
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
US5687323A (en) * 1994-06-17 1997-11-11 Commonweal Incorporated Dual currency debit card
WO1997043727A1 (en) * 1996-05-15 1997-11-20 Crossmar, Inc. Method and system for performing automated financial transactions involving foreign currencies
WO1997048078A2 (en) * 1996-06-14 1997-12-18 Cybercash, Inc. System and method for multi-currency transactions
US5715399A (en) * 1995-03-30 1998-02-03 Amazon.Com, Inc. Secure method and system for communicating a list of credit card numbers over a non-secure network
US5729594A (en) * 1996-06-07 1998-03-17 Klingman; Edwin E. On-line secured financial transaction system through electronic media
US5774553A (en) * 1995-11-21 1998-06-30 Citibank N.A. Foreign exchange transaction system
US5826241A (en) * 1994-09-16 1998-10-20 First Virtual Holdings Incorporated Computerized system for making payments and authenticating transactions over the internet
WO1999041315A1 (en) * 1998-02-13 1999-08-19 Kaneka Corporation Aqueous emulsions containing silicone rubber particles and process for producing the same

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5745886A (en) * 1995-06-07 1998-04-28 Citibank, N.A. Trusted agents for open distribution of electronic money
IES990584A2 (en) * 1999-07-12 2000-07-12 Mainline Corporate Holdings Dynamic currency conversion for card payment systems
US6892184B1 (en) * 2000-06-19 2005-05-10 E4X Inc. System and method for multiple currency transactions

Patent Citations (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3652795A (en) * 1970-11-25 1972-03-28 Electrospace Corp Telephone transaction system
US4251867A (en) * 1978-03-25 1981-02-17 Laurel Bank Machine Co., Ltd. Money exchanger apparatus
US4812628A (en) * 1985-05-02 1989-03-14 Visa International Service Association Transaction system with off-line risk assessment
US4823264A (en) * 1986-05-27 1989-04-18 Deming Gilbert R Electronic funds transfer system
EP0251619A2 (en) * 1986-06-26 1988-01-07 Visa International Service Association Portable transaction card
US4766293A (en) * 1986-06-26 1988-08-23 Visa International Service Association Portable financial transaction card capable of authorizing a transaction in foreign currencies
EP0254812A2 (en) * 1986-06-27 1988-02-03 International Business Machines Corporation Cryptovariable initialisation in a public key network
US4877947A (en) * 1986-08-05 1989-10-31 Oki Electric Industry Co., Ltd. Transaction processing system
US4837422A (en) * 1987-09-08 1989-06-06 Juergen Dethloff Multi-user card system
WO1991016691A1 (en) * 1990-04-12 1991-10-31 Jonhig Limited Value transfer system
GB2261579A (en) * 1990-07-23 1993-05-19 Ericsson Ge Mobile Communicat Authentication system for digital cellular communications
US5440634A (en) * 1991-10-16 1995-08-08 Jonhig Limited Value transfer system
US5455407A (en) * 1991-11-15 1995-10-03 Citibank, N.A. Electronic-monetary system
US5453601A (en) * 1991-11-15 1995-09-26 Citibank, N.A. Electronic-monetary system
EP0542298A2 (en) * 1991-11-15 1993-05-19 Citibank, N.A. Electronic monetary system
US5369705A (en) * 1992-06-03 1994-11-29 International Business Machines Corporation Multi-party secure session/conference
EP0590861A2 (en) * 1992-09-29 1994-04-06 AT&T Corp. Secure credit/debit card authorization
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
DE4308597A1 (en) * 1993-03-18 1993-08-19 Marc Bode Electronic bank account unit with inter account link - provided by infrared communication with units having keyboard display and built in processing.
WO1995012169A1 (en) * 1993-10-25 1995-05-04 Visa International Service Association A method and apparatus for disbributing currency
US5557518A (en) * 1994-04-28 1996-09-17 Citibank, N.A. Trusted agents for open electronic commerce
US5687323A (en) * 1994-06-17 1997-11-11 Commonweal Incorporated Dual currency debit card
GB2296413A (en) * 1994-07-05 1996-06-26 Motorola Inc A method of messaging in a communciation system
US5826241A (en) * 1994-09-16 1998-10-20 First Virtual Holdings Incorporated Computerized system for making payments and authenticating transactions over the internet
US5535276A (en) * 1994-11-09 1996-07-09 Bell Atlantic Network Services, Inc. Yaksha, an improved system and method for securing communications using split private key asymmetric cryptography
US5715399A (en) * 1995-03-30 1998-02-03 Amazon.Com, Inc. Secure method and system for communicating a list of credit card numbers over a non-secure network
WO1996033568A1 (en) * 1995-04-18 1996-10-24 Hewlett-Packard Company Methods and apparatus for authenticating an originator of a message
WO1996036024A1 (en) * 1995-05-12 1996-11-14 Koninklijke Ptt Nederland N.V. Electronic payment system having several calculation units, electronic payment means, as well as a method for electronic payment
GB2301919A (en) * 1995-06-05 1996-12-18 Bankers Trust Co Multi-step digital signature method and system
US5659165A (en) * 1995-07-24 1997-08-19 Citibank. N.A. Customer-directed, automated process for transferring funds between accounts via a communications network
WO1997004411A1 (en) * 1995-07-24 1997-02-06 Citibank, N.A. Customer-directed, automated system for transferring funds between accounts
US5774553A (en) * 1995-11-21 1998-06-30 Citibank N.A. Foreign exchange transaction system
WO1997043727A1 (en) * 1996-05-15 1997-11-20 Crossmar, Inc. Method and system for performing automated financial transactions involving foreign currencies
US5787402A (en) * 1996-05-15 1998-07-28 Crossmar, Inc. Method and system for performing automated financial transactions involving foreign currencies
US5729594A (en) * 1996-06-07 1998-03-17 Klingman; Edwin E. On-line secured financial transaction system through electronic media
WO1997048078A2 (en) * 1996-06-14 1997-12-18 Cybercash, Inc. System and method for multi-currency transactions
WO1999041315A1 (en) * 1998-02-13 1999-08-19 Kaneka Corporation Aqueous emulsions containing silicone rubber particles and process for producing the same

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"RSA" Signs Deal With China; Internet Week, vol. 2, No. 7, (Feb. 12, 1996). *
Bers, Joanna Smith, "Cyberspace: The New Promised Land," Bank Systems & Technology, vo.. 32, No. 7, (Jul. 1995), pp. 32-37. *
Cohen, Jackie, "Citibank's Bid To Be The King of Cash," Bank Technology News, vol. 9, No. 9, (Sep. 1996), pp. 9-12. *
Lee et al.; "Considering exchange rate movements in economic evaluation of foreign direct investments", Engineering Economist, v40n2 pp. 171-199, 1995. *
McDougall, Bruce, "Electronic Evolution," Canadian Banker, vol. 102, No. 5, (Sep./Oct. 1995), pp. 28-33. *
PSINet Teams With WorldPay Ltd. to Launch the Worlds, First Secure Multi-Currency Solution for International Electronic Commerce, PR Newswire, Oct. 6, 1997. *

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9070166B2 (en) 1999-04-19 2015-06-30 Enpluz, LLC Centralized, online multi-seller interface system
US9224170B2 (en) 1999-04-19 2015-12-29 Rpx Corporation Sales channel management infrastructure
US9098879B2 (en) 1999-04-19 2015-08-04 Enpluz, LLC Seller promotion creation and modification
US9082153B2 (en) 1999-04-19 2015-07-14 Enpluz, LLC Web search and promotion search engine integration
US20120150602A1 (en) * 1999-04-19 2012-06-14 Enpulz, Llc Centralized, online multi-seller interface system
US9070167B2 (en) * 1999-04-19 2015-06-30 Enpluz, LLC Centralized, online multi-seller interface system
US9053514B2 (en) 1999-04-19 2015-06-09 Enpluz, LLC System supporting promotion browsing and searching
USRE46140E1 (en) * 2000-04-19 2016-09-06 Virginia Innovation Sciences, Inc. Method and system for conducting business in a transnational e-Commerce network
US20090228378A1 (en) * 2006-03-01 2009-09-10 Alibaba Group Holding Limited Method and System to Charge an Account
US8793169B2 (en) * 2006-03-01 2014-07-29 Alibaba Group Holding Limited Method and system to charge an account
US20080167965A1 (en) * 2007-01-09 2008-07-10 Von Nothaus Bernard Apparatus, system, and method for extracting real world value from a virtual account
US8108266B2 (en) 2007-01-29 2012-01-31 Hewlett-Packard Development Company, L.P. Methods for providing secure eCommerce transactions
US20080183590A1 (en) * 2007-01-29 2008-07-31 Antoni Drudis Methods for providing secure eCommerce transactions
US20090076954A1 (en) * 2007-09-14 2009-03-19 Carmody Michael D Method and system for settling financial transactions

Also Published As

Publication number Publication date
WO1997048078A2 (en) 1997-12-18
US6205433B1 (en) 2001-03-20
USRE44502E1 (en) 2013-09-17
WO1997048078A3 (en) 1998-01-29
US5897621A (en) 1999-04-27
CA2260002A1 (en) 1997-12-18
AU713339B2 (en) 1999-12-02
CA2260002C (en) 2002-12-31
AU3306597A (en) 1998-01-07
EP0910840A2 (en) 1999-04-28

Similar Documents

Publication Publication Date Title
USRE41619E1 (en) System and method for multicurrency transactions
US10810582B2 (en) Multi currency exchanges between participants
US7593898B1 (en) Method and system for payment transactions and shipment tracking over the internet
US7177836B1 (en) Method and system for facilitating financial transactions between consumers over the internet
US7206763B2 (en) Method and system for commodity-based currency for payment of accounts
US8095445B2 (en) Method and system for completing a transaction between a customer and a merchant
US6594647B1 (en) Real time bank-centric universal payment system
US7895119B2 (en) Method and system for pushing credit payments as buyer initiated transactions
AU2009200162B2 (en) Method and system for completing a transaction between a customer and a merchant
US20140337183A1 (en) Online processing for offshore business transactions
US20020072942A1 (en) System and method for push-model fund transfers
US20050021455A1 (en) On-line payments system
US7599885B2 (en) Many-to-many correspondence: methods and systems for replacing interbank funds transfers
MXPA02007983A (en) Method and system for international e commerce.
KR20230152547A (en) Prepayment system for account receivables based on virtual credit card
AU2002247093B8 (en) Method and system for completing a transaction between a customer and a merchant
KR20020059478A (en) Method of shortly settlement using internet network
AU2002247093A1 (en) Method and system for completing a transaction between a customer and a merchant

Legal Events

Date Code Title Description
AS Assignment

Owner name: PAYPAL, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERISIGN, INC.;REEL/FRAME:019019/0170

Effective date: 20051115

Owner name: PAYPAL INTERNATIONAL LIMITED, IRELAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERISIGN, INC.;REEL/FRAME:019019/0170

Effective date: 20051115

AS Assignment

Owner name: PAYPAL, INC., CALIFORNIA

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR AND ASSIGNEE NAMES PREVIOUSLY RECORDED ON REEL 019019 FRAME 0170. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT FROM VERISIGN, INC. TO PAYPAL, INC. AND PAYPAL INTERNATIONAL LIMITED;ASSIGNOR:VERISIGN, INC.;REEL/FRAME:019035/0781

Effective date: 20051115

Owner name: PAYPAL INTERNATIONAL LIMITED, IRELAND

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR AND ASSIGNEE NAMES PREVIOUSLY RECORDED ON REEL 019019 FRAME 0170. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT FROM VERISIGN, INC. TO PAYPAL, INC. AND PAYPAL INTERNATIONAL LIMITED;ASSIGNOR:VERISIGN, INC.;REEL/FRAME:019035/0781

Effective date: 20051115

FPAY Fee payment

Year of fee payment: 12