WO2004031908A2 - Procede et systeme de paiement de personne a personne securise - Google Patents

Procede et systeme de paiement de personne a personne securise Download PDF

Info

Publication number
WO2004031908A2
WO2004031908A2 PCT/US2003/030900 US0330900W WO2004031908A2 WO 2004031908 A2 WO2004031908 A2 WO 2004031908A2 US 0330900 W US0330900 W US 0330900W WO 2004031908 A2 WO2004031908 A2 WO 2004031908A2
Authority
WO
WIPO (PCT)
Prior art keywords
payee
payer
account
payment
host computer
Prior art date
Application number
PCT/US2003/030900
Other languages
English (en)
Other versions
WO2004031908A9 (fr
WO2004031908A3 (fr
Inventor
David John Liu
Original Assignee
Rysix Holdings, Llc
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 Rysix Holdings, Llc filed Critical Rysix Holdings, Llc
Priority to AU2003277132A priority Critical patent/AU2003277132A1/en
Publication of WO2004031908A2 publication Critical patent/WO2004031908A2/fr
Publication of WO2004031908A3 publication Critical patent/WO2004031908A3/fr
Publication of WO2004031908A9 publication Critical patent/WO2004031908A9/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits

Definitions

  • the present invention relates to the field of money transfer between the account of one person or entity and the account of another person or entity. More particularly, the present invention relates to a method and system for the transfer of money from a payer to a payee, securely and instantly without exchanging account data between the parties to the transfer.
  • Payment by check also provides the payee, as well as any subsequent endorsers, information regarding the account on which the check is drawn. For example, the bank and account number is normally printed on a check. A payer may not want the payee and others to have this additional information. Moreover, checks often contain other information, such as the payer's name, address and telephone number. In many instances, the tendering of a check by a payer elicits a demand by the payee for the payer's driver's license or other identification information. Clearly, the use of checks for payment includes many serious negatives.
  • Another method of transferring funds from a payer to a payee is for the payer to wire the funds into the payee's account, either from the payer's account or by a service that accepts cash or other payment and then sends the funds to a payee (such as Western Union®). Wiring funds usually requires that the payer visit a bank and pay a fee, which may be substantial. It also normally requires that the payer have knowledge of the payee's account number, so as to enable the transfer. This is information that the payee may not want to disclose.
  • None of these methods result in a real time credit to a payee's account. Moreover, the payer's account is not debited in real time. These methods thus may entail inconvenient delays. For example, the payment of cash from a payer to a payee requires that the payer first go to a bank or other source of cash, withdraw funds from their account, go to the payee's location, transfer the cash and optionally receive change. The payee collects the cash, optionally pays out change, goes to their bank or place of deposit, and deposits the cash into their account. Each of these steps involve a potential delay.
  • the invention includes a method of interparty payment.
  • a host computer generates a transaction reference that indexes a payment amount and a credit account into which the payment amount is to be credited in response to a request for payment by a payee.
  • the host computer forwards the transaction reference through the payee to a payer.
  • the payer then forwards payment information comprising the transaction reference and a debit account from which the payment amount is to be taken to the host computer, which transfers the payment amount from the debit account to the credit account to complete the interparty payment.
  • the host computer issues a transaction receipt to the payee, the payer, or both.
  • the request for payment includes an account number and authentication information for the credit account.
  • the authentication information is a personal identification number (PIN).
  • the payment information provided to the host computer by the payer includes an account number and authentication information for the debit account.
  • a request for credit is sent by the payee to the host computer, along with the amount, the transaction reference, and the authentication information for the credit account. The host computer then transfers the amount from the credit account to the debit account.
  • the invention also includes a system for interparty payment that includes a host computer in communication with a payer, a payee, and a bank financial network.
  • the bank financial network includes a payee account and a payer account.
  • the host computer is configured to generate, in response to a request for payment by a payee, a transaction reference that indexes a payment amount and a credit account into which the payment amount is to be credited.
  • the host computer forwards the transaction reference through the payee to a payer.
  • the payer then sends the host computer payment information comprising the transaction reference and a debit account together with authentication token (information) and a PIN from which the payment amount is to be taken.
  • the host computer then transfers, by communication with a bank financial network, the payment amount from the debit account to the credit account to complete the interparty payment.
  • the host computer is further configured to issue a transaction receipt to the payee, the payer, or both.
  • the request for payment includes an account number and authentication information for the credit account, debit account, or both.
  • the system further includes a computer database into which the host computer is further configured to store the payer, the payer, the amount and the transaction information.
  • Figure 1 is a block diagram of a person to person payment system in accordance with one embodiment of the present invention.
  • FIGS. 2(a) and 2(b) are flowcharts of the process of account registration by the payer and payee, respectively, in accordance with an embodiment of the present invention
  • Figure 3 is a flowchart depicting the processing of a person to person payment by a payment manager, payer and payee in accordance with an embodiment of the present invention.
  • a system and method for the transfer of money from a payer to a payee, securely and instantly without exchanging account data between the parties to the transfer.
  • the system and method provides a minimal transfer of information between the payer and payee, yet does not incur the disadvantages of using cash.
  • the payer does not require the payer carry a supply of cash, which might be lost or stolen.
  • the payee does not need to maintain a cash supply for making change, nor handle accumulations of cash by making bank deposits on a regular basis.
  • the payee has a reduction in their need to scrutinize employees due to the lack of available liquid currency exposed to internal theft.
  • the method and system of the present invention also has advantages over the use of checks in the prior art.
  • the present invention does not communicate the payer's account number to the payee, as is typically done on the face of a check.
  • there is no longer a need for any of the payer's personal information to be communicated to the payee as is normally the case when a payer uses a personal check to pay a payee.
  • most personal checks have the payer's name, address, account number, and the name of the bank on the face of the check.
  • additional information such as the payer's telephone number, social security number, or driver's license number as an assurance to the payee that the check is valid. This additional assurance , and thus the additional information is not necessary using the present invention.
  • the present invention is additionally advantageous over the wiring of funds by a payer to a payee.
  • Wiring funds requires that the payer travel to a location from which funds can be wired, such as a Western Union®, pay both the amount to wire and an additional fee, and provide the information of where to send the wire.
  • This requires either that the payee provide the payer with the payee's account information for wiring the funds to, or that the payee travel to a location, such as another Western Union®, to receive the funds so wired.
  • the present invention forgoes the need for the payer to travel to travel, pay an additional fee, and provide payee account information, as well as the need for the payee to either travel or provide account information to collect the wired funds.
  • Another advantage of the present invention over other methods and systems of transferring a payment from a payer to a payee is that, unlike the prior art, the payment amount is debited from the payer account and credited to the payee account quickly, in real time. Other methods of transferring payment from a payer to a payee required further non-real time steps before the payer account was debited and the payee account could be credited.
  • Figure 1 a person to person payment system and method in accordance with one embodiment of the present invention is shown.
  • the system includes a payer 2, payee 1, payment manager 3, payer account 4, and payee account 5.
  • the payer account 4 is alternatively, but equivalently referred to herein as a debit account.
  • the payee account 5 is alternatively, but equivalently referred to herein as a credit account.
  • the method of this embodiment may be used when a payer 2 decides to transfer funds from the payer's account 4 to a payee's account 5.
  • the payer 2 can be shopping in a retail establishment operated by the payee 1.
  • the payer 2 informs the payee 1 that the payer 2 wants to transfer the purchase price from the payer's account 4 to the payee's account 5.
  • the payee 1 sends the payment manager 3 a payment request which includes the payee's account information 6.
  • Any communications link may be used between the payee 1 and payment manager 3, including, but not limited to a telephone or cellular link, the Internet, or any other communications channel. Since the payee account information transferred generally includes confidential account information, it is preferable that the communications link employed be secure. This security can be achieved through a suitable combination of encryption of the data to be transferred with the choice of physical communications link.
  • the payment request 6 includes information regarding the payee's account 5 to receive the transfer. This information includes the amount of money to transfer, and may also include an identification of the currency to be used. For example, a domestic system in the United States can default to the US dollar as the currency of exchange. To transfer other currency on the domestic system would require that an identification of the currency to transfer be provided, unless the transfer currency can be determined from the context of the transaction.
  • An important component of the payment request 6 is the information identifying the payee's account 5 to the payment manager 3.
  • This identifying information includes the payee account number.
  • the identifying information also includes the personal identification number (PIN) of the payee's account 5.
  • PIN personal identification number
  • the payee 1 could have previously registered their payee account number and PIN with the payment manager. This information could then be indexed to an alternative registration number by the payment manager 3. It may even be accessed by the payee's telephone number using caller identification technology.
  • the payee 1 accesses the payment manager 3 over the Internet by logging into the payment manager 3 using a user id and password
  • the user id and password may be used by the payment manager 3 to index the payee's account information.
  • the payment manager 3 then issues a transaction reference number 7 to the payee 1.
  • the payment manager 3 will later use this reference number 7 to determine the amount to transfer and the account to transfer it to (the payee account 5).
  • the payment manager should save the reference number 7, preferable in a database with the payee account information and the amount to transfer. This information may be indexed for easy access when needed.
  • the reference number generated by the payment manager is next sent to the payer by the payee 8.
  • Communication between the payer and payee can be by any of several methods.
  • the payee may be a retail establishment and the payer may actually purchase an item at the retail establishment.
  • the payer 2 and payee 1 may communicate verbally or in writing, or may use an electronic form of communication.
  • the payee can print out the reference number and hand it to the payer.
  • the payer sends payer account information to the payment manager 9. This information should include the reference number the payer 2 received from the payee 1.
  • the payment manager 3 can determine the amount of the payment and the payee account 5 to transfer the payment to.
  • the payer 2 can send the payer account information and reference number to the payment manager 3 using any of several different methods.
  • the payer 2 has already registered the payer account 4 to be used by the payment manager 3 whenever the payer 2 authorizes such payment.
  • the transfer 9 of payer account information and reference number by the payer 2 to the payment manager 3 can then be a accomplished without the payer 2 actually sending the payer account 4 number or its associated PIN.
  • the payer 2 could send their login identification and password together with the reference number.
  • the payment manager 3 could verify the payer login identification and password, and retrieve the transaction information using the reference number. Thus, no account information would necessarily be communicated at the time of the transaction.
  • the payer and/or payee may choose not to register with the payment manager. In this instance, sufficient account information would need to be sent by the payer/payee to the payment manager to enable the payment manager to correctly identify and access the payer/payee account using a financial network.
  • FIGS 2(a) and 2(b) are flowcharts of the process of account registration by the payer and payee, respectively, in accordance with an embodiment of the present invention.
  • a payer first decides to begin the process of registering with a payment manager 20.
  • the payer provides the payment manager with the payer account information 21.
  • the payer can provide this information by any of several methods. For example, the payer can communicate their account information over an Internet web page maintained by the payment manager. In this case the payer could enter their account information onto an online form and send it to the payment manager via a secure encrypted web transfer. Numerous alternatives exist for encrypting information for communication over an Internet link.
  • the payer may fill in an actual form and send it to a payment manager through the mail system or another delivery service.
  • the payer account information would include an identification of the payer, the payer account number, and the institution or bank where the payer account is held.
  • the payer may also include the personal identification number (“PIN”) for the account, although this is not strictly required.
  • the payment manager issues a user identification and a password to the payer 22. From this point onward, the payer no longer needs to refer to the actual payer account number in communications with the payment manager. Instead, the payer uses the user identification/password combination issued by the payment manager. It should be noted that the choice of user identification and password does not necessarily have to be made by the payment manager.
  • An alternative embodiment allows the payer to select a user identification and a password. In such an embodiment the user identification would be issued to the payer if it conforms to certain minimal standards, such as a length requirement, and if it is available (not being used by another user). Otherwise, the payment manager would either allow the payer to select another user identification or assign one by itself.
  • a payer-selected password would need to satisfy certain minimal standards, such as length of the password.
  • a given password may be used by several users at the same time without being a burden on security.
  • the payment manager saves the payer account information, user identification and password 23.
  • the payment manager may use any of several methods to save this information.
  • a particularly useful and efficient method is to save the information into a relational computer database.
  • Such a database may also be object-oriented.
  • the database would also be indexed for fast and efficient database searches and other queries.
  • a payee registers with the payment manager in a manner synonymous with the payer registration described above. After deciding to register 30, the payee provides account information to the payment manager 31. The payment manager 31 then issues a user identification and a password to the payee 32.
  • the methodology employed by the payment manager in issuing the user identification and password to the payee may vary significantly from one embodiment to another. For example, in one embodiment, the payee selects their user identification, which is checked by the payment manager for uniqueness. Once the payee's user identification is selected in this embodiment of the invention, the payment manager sends a randomly-generated password to the payee.
  • the payee may select their own password, adhering to a simple set of rules for password construction, such as a requirement that the password be alphanumeric and of at least 8 characters. These requirements are cited here for exemplary purposes, another embodiment of the invention may incorporate entirely different rules for password construction.
  • the payee's account information, user identification and password are saved 33 in a manner similar to the method used to save the payer's information.
  • FIG. 3 is a flowchart depicting the processing of a person to person payment by a payment manager, payer and payee in accordance with an embodiment of the present invention.
  • the payer and payee first determine to transfer funds from the payer to the payee 41. This decision may be the result of a retail sale, wherein the payee is a merchant and the payer is a customer. It may also, however, be due to any other transaction between a payer and payee resulting in a need to transfer funds from a payer to a payee.
  • the payee sends a payment request for the amount to transfer, along with the payee account information, to the payment manager 42.
  • the payee account information includes all the information necessary to identify the account to the payment manager.
  • the payee may only need to send their user identification and password in order for the payment manager to correctly identify the payee account. Otherwise, enough information needs to be sent by the payee to enable the payment manager to correctly identify and access the payee account.
  • the payee then verifies the payee account information, and, if verified, saves the payee account information, the amount, and a payment manager-generated transaction reference number 43.
  • these items are saved in a computer database to allow for efficient indexed lookups and record-keeping. Alternatively, any method may be employed by the payment manager to save this information. If the payee account information is not verifiable, the process terminates without transferring any payment.
  • the payment manager sends the transaction reference number to the payee 44, who then sends it to the payer 45. It is only the transaction reference number that is passed to the payer, not payee account information, thus providing an added layer of security to the payee.
  • the transfer of the transaction reference number to the payer may be by any method, including an electronic, written, or verbal transfer, as well as any other method.
  • the payer sends the payer account information and the transaction reference number to the payment manager 46.
  • the payer account information including the account number and any validation code, or personal identification code (PIN), may be explicitly sent in this step. If, however, the payer has previously registered with the payment authority, the payer would only need to send their user identification and password together with the transaction reference number to the payment manager.
  • the payer may communicate with the payment manager by any means, including over the Internet, over a telephone line, or using any other method.
  • a payer using the Internet to communicate in a preferred embodiment would enter their user identification, password, and the transaction reference number into a web page maintained by the payment manager.
  • the payer might in another embodiment speak with an operator representative of the payment manager on a telephone and verbally communicate the payer's information and transaction reference number to the operator, who would then enter the data into the payment manager system.
  • the payment manager verifies the payer account information and the transaction reference number. If valid, the payment manager causes the amount of the transaction to be debited from the payer account and credited to the payee account 47. In invalid, the process is terminated without any transaction of funds taking place.
  • the payment manager accesses the payee and payer accounts by participating on a network for real-time financial transaction.
  • the mechanism of interacting with such a network is well known to those skilled in the art.
  • the procedure starts with establishing a connection to a remote computer operated by the network.
  • the computer operated by the payment manager then authenticates itself to the network.
  • the payment manager After being admitted to the network, the payment manager then sends transaction requests for debit and credit, and receives results (approval or decline) of these transactions.
  • the payment manager issues transaction receipts to the payer and payee for their records 48. This step of issuing transaction receipts is not mandatory, and alternative embodiments of the payment manager can issue receipts to both, one or none of the payer and payee, as preferred.
  • the receipt(s) may take any of several forms, including an electronic receipt sent over a communications network or the Internet, a verbal receipt sent over a telephone connection, a paper receipt sent by mail, or any other form.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un procédé et un système permettant un paiement entre parties. Une demande de paiement est envoyée par un bénéficiaire à un ordinateur hôte, cette demande comprenant un numéro de compte et un numéro d'identification personnel (NIP) pour un compte de crédit. En réponse, l'ordinateur hôte génère une référence de transaction indexant un montant de paiement et le compte de crédit sur lequel le montant de paiement doit être versé. La référence de transaction est transférée par l'intermédiaire du bénéficiaire à un payeur. Le payeur fournit alors à l'ordinateur hôte des informations de paiement comprenant la référence de transaction et un compte de débit avec jeton d'authentification, tel qu'un NIP, à partir duquel le montant de paiement doit être transféré. Au moyen d'un réseau financier bancaire, l'ordinateur hôte transfère le montant de paiement du compte de débit au compte de crédit de manière à exécuter le paiement entre parties. Ensuite, le payeur et/ou le bénéficiaire reçoit éventuellement une quittance en provenance de l'ordinateur hôte.
PCT/US2003/030900 2002-10-01 2003-10-01 Procede et systeme de paiement de personne a personne securise WO2004031908A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003277132A AU2003277132A1 (en) 2002-10-01 2003-10-01 Method and system for secure person to person payment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US26030402A 2002-10-01 2002-10-01
US10/260,304 2002-10-01

Publications (3)

Publication Number Publication Date
WO2004031908A2 true WO2004031908A2 (fr) 2004-04-15
WO2004031908A3 WO2004031908A3 (fr) 2004-06-03
WO2004031908A9 WO2004031908A9 (fr) 2004-07-22

Family

ID=32068189

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/030900 WO2004031908A2 (fr) 2002-10-01 2003-10-01 Procede et systeme de paiement de personne a personne securise

Country Status (2)

Country Link
AU (1) AU2003277132A1 (fr)
WO (1) WO2004031908A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011047331A2 (fr) * 2009-10-16 2011-04-21 Visa International Service Association Système et procédé d'anti-hameçonnage comprenant une liste avec des données d'utilisateur
WO2014097174A1 (fr) * 2012-12-21 2014-06-26 Leon Johannes Brits Paiements sécurisés à l'aide de dispositifs de communication portables et de codes bidimensionnels
US20170300960A1 (en) * 2016-04-19 2017-10-19 Mastercard International Incorporated Method and system for platform attribution using digitized tokens
US10600039B2 (en) 2015-05-20 2020-03-24 Mastercard International Incorporated Systems and methods for managing financial payments between parties
US20220114581A1 (en) * 2020-10-09 2022-04-14 Mastercard International Incorporated Personally identifiable information secure person-to-person payment technology

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6408284B1 (en) * 1993-11-01 2002-06-18 Visa International Service Association Electronic bill pay system for consumers to generate messages directing financial institutions to pay a biller's bill
US6629080B1 (en) * 1998-07-20 2003-09-30 Usa Technologies, Inc. Transaction processing method of fulfilling an electronic commerce transaction by an electronic commerce terminal system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6408284B1 (en) * 1993-11-01 2002-06-18 Visa International Service Association Electronic bill pay system for consumers to generate messages directing financial institutions to pay a biller's bill
US6629080B1 (en) * 1998-07-20 2003-09-30 Usa Technologies, Inc. Transaction processing method of fulfilling an electronic commerce transaction by an electronic commerce terminal system

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011047331A2 (fr) * 2009-10-16 2011-04-21 Visa International Service Association Système et procédé d'anti-hameçonnage comprenant une liste avec des données d'utilisateur
WO2011047331A3 (fr) * 2009-10-16 2011-07-14 Visa International Service Association Système et procédé d'anti-hameçonnage comprenant une liste avec des données d'utilisateur
WO2014097174A1 (fr) * 2012-12-21 2014-06-26 Leon Johannes Brits Paiements sécurisés à l'aide de dispositifs de communication portables et de codes bidimensionnels
US10600039B2 (en) 2015-05-20 2020-03-24 Mastercard International Incorporated Systems and methods for managing financial payments between parties
US20170300960A1 (en) * 2016-04-19 2017-10-19 Mastercard International Incorporated Method and system for platform attribution using digitized tokens
US10861042B2 (en) * 2016-04-19 2020-12-08 Mastercard International Incorporated Method and system for platform attribution using digitized tokens
US20220114581A1 (en) * 2020-10-09 2022-04-14 Mastercard International Incorporated Personally identifiable information secure person-to-person payment technology

Also Published As

Publication number Publication date
WO2004031908A9 (fr) 2004-07-22
AU2003277132A1 (en) 2004-04-23
WO2004031908A3 (fr) 2004-06-03
AU2003277132A8 (en) 2004-04-23

Similar Documents

Publication Publication Date Title
JP5005871B2 (ja) 金融手段を確認するためのシステムおよび方法
US6736314B2 (en) Methods and systems for transferring funds
US7337953B2 (en) Negotiable instrument authentication systems and methods
US20050182720A1 (en) Online payment system and method
US8109435B2 (en) Identity verification switch
US20100179906A1 (en) Payment authorization method and apparatus
US20070005467A1 (en) System and method for carrying out a financial transaction
US20030055787A1 (en) Electronic settlement method
US20070168279A1 (en) Disposable payment account
TW200306483A (en) System and method for secure credit and debit card transactions
KR20010110740A (ko) 개인간, 개인과 사업체간, 사업체와 개인간 그리고사업체간 금융 거래 시스템
WO2002014985A9 (fr) Systeme automatise de paiement
US20020194080A1 (en) Internet cash card
US20100276486A1 (en) Issuing a value-bearing card associated with only non-personally identifying information
AU2006309231B2 (en) Web terminal and bridge that support passing of authentication data to acquirer for payment processing
KR20020010178A (ko) 이동통신 단말기를 이용한 신용카드 결제 방법
US20090216651A1 (en) Dispensing valuable media
JP2004506998A (ja) 預金メモリから電子マネーを送金するための方法及び装置
EP1134707A1 (fr) Procédé et dispositif d'authorisation de paiement
JP2005521181A (ja) クレジットカード決済方法およびシステム
US8401969B2 (en) Virtual traveler's check
JP4579408B2 (ja) 海外送金システム
WO2004031908A2 (fr) Procede et systeme de paiement de personne a personne securise
US20020095374A1 (en) Method and apparatus for processing cash payments for electronic and internet transactions
US11144912B2 (en) Authentication bypass software for merchant terminals

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
COP Corrected version of pamphlet

Free format text: PAGES 1/4-4/4, DRAWINGS, REPLACED BY NEW PAGES 1/4-4/4; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established
32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: COMMUNICATION PURSUANT TO RULE 69 EPC (EPO FORM 1205A OF 090805)

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP