WO2003060796A1 - Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil - Google Patents

Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil Download PDF

Info

Publication number
WO2003060796A1
WO2003060796A1 PCT/US2003/002054 US0302054W WO03060796A1 WO 2003060796 A1 WO2003060796 A1 WO 2003060796A1 US 0302054 W US0302054 W US 0302054W WO 03060796 A1 WO03060796 A1 WO 03060796A1
Authority
WO
WIPO (PCT)
Prior art keywords
merchant
payment
customer
central system
wireless device
Prior art date
Application number
PCT/US2003/002054
Other languages
English (en)
Inventor
Tara Chand Singhal
Original Assignee
Tara Chand Singhal
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
Priority claimed from US10/046,834 external-priority patent/US7890433B2/en
Priority claimed from US10/091,882 external-priority patent/US8494957B2/en
Application filed by Tara Chand Singhal filed Critical Tara Chand Singhal
Priority to AU2003235604A priority Critical patent/AU2003235604A1/en
Priority to EP03729695A priority patent/EP1472636A4/fr
Publication of WO2003060796A1 publication Critical patent/WO2003060796A1/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/08—Payment architectures
    • G06Q20/14—Payment architectures specially adapted for billing systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/023—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] the neutral party being a clearing house
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/12—Payment architectures specially adapted for electronic shopping systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/24—Credit schemes, i.e. "pay after"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/353—Payments by cards read by M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/383—Anonymous user system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F19/00—Complete banking systems; Coded card-freed arrangements adapted for dispensing or receiving monies or the like and posting such transactions to existing accounts, e.g. automatic teller machines
    • G07F19/20—Automatic teller machines [ATMs]
    • G07F19/203—Dispensing operations within ATMs

Definitions

  • the present invention is directed to facilitating private and secure payment and financial transactions by the use of a wireless device, in lieu of bankcards and bank checks, between a customer and a merchant and between private parties.
  • the customer While making payment for such a subscription service, the customer gives his/her name, credit card number to the merchant along with other data such as e-mail address, so that the merchant can process the payment for initial payment and for subsequent periodic payments and notify the customer via the e- mail address.
  • a customer may conduct a private and secure payment transaction: (i) with a retail merchant at the merchant's site using a wireless device; (ii) with a web-merchant using a wireless device; (iii) with a restaurant merchant at the dining table using a wireless device;
  • a customer does not share his/her identity and personal sensitive data with the merchants. Further, in these embodiments, a customer need not carry his/her bankcards and/or personal checks bearing personal and sensitive data with him/her and thus, avoid the risks of theft or loss. All of these embodiments are similar in their method of operation and apparatus, differing only in degree of detail in the operation and the data required to be maintained in a central system.
  • the payment system includes a central system, a wireless device belonging to a customer and an existing bankcard and or bank account.
  • the wireless device is a cellular telephone or it may be a Personal Digital Assistant
  • PDA wireless personal area network
  • Figure 1A is a block diagram that illustrates a payment system use in a retail merchant site according to the present invention
  • Figure 1 B is a block diagram that illustrates payment system use in a restaurant according to the present invention
  • Figure 1C is a block diagram that illustrates features of the present invention payment system between a customer and a online subscription merchant
  • Figure 2A is a block diagram that illustrates operation features of the present invention payment system between a customer and a merchant
  • Figure 2B is a block diagram that illustrates operation features of the present invention payment system between two private parties
  • Figure 2C is a block diagram that illustrates the operation features of the use of a wireless device for withdrawing cash from an ATM having features of the present invention
  • Figure 3A illustrates a central system having features of the present invention
  • Figure 3B-C illustrates a databases in the central system having features of the present invention.
  • Figure 4A illustrates flow chart for an online subscription periodic billing system having features of the present invention
  • Figure 4B illustrates flow chart for an online subscription system having features of the present invention
  • Figure 4C illustrates flow chart for an restaurant payment system having features of the present invention
  • Figures 5A illustrate flow charts of the payment system operation for a retail merchant, having feature of the present invention.
  • FIGS. 5B illustrate flow charts of the payment system operation between private parties, having feature of the present invention. DESCRIPTION
  • the payment system 02 includes a central system 10, a wireless device 12, in the form of a cell phone or a PDA equipped with a communication module, commonly available in the market.
  • a payment function 12D coupled with an interface means of keypad 12A and optical camera lens 12E in the wireless device 12 capture the data necessary to process a payment transaction from a merchant interface such as a display screen 14 and communicates that data to the central system 10.
  • the central system 10 retrieves pre-stored detailed data required to process the payment transaction and communicates with a prior art card processor and/or an automated clearing house (ACH) 36 to process the payment transaction between the customer's bank and a merchant's bank, or more generally, between the banks of a payer and a payee.
  • ACH automated clearing house
  • the payment approval data record is communicated to the merchant display terminal 14 and the customer on his/her wireless device 12.
  • a Party A can make a payment to another private party B without disclosing personal sensitive data as it happens when giving a personal check for payment.
  • Most personal checks are imprinted with name, address and driver license data and reveal customer bank and bank account number.
  • One of the embodiments facilitates use of a wireless device in lieu of an ATM card.
  • no ATM card need to be carried, and many people carry a wireless device in the form of a cellular telephone.
  • the payment system 02 of this invention does not require the customer to give any personal data including name, bankcard data, identification data such as driver license etc, to a merchant during payment transaction.
  • the merchant does not have the burden of safeguarding customer sensitive data from theft and misuse
  • the different embodiments using the payment system that are specific to different ways to interface with the payee or merchant are described herein.
  • the different payee/merchant can be a retail merchant, a web based merchant, a web- based online subscription merchant, a restaurant merchant, a private business or individual.
  • the device 12 is used to with draw cash at a ATM without the use of the ATM card.
  • the headings are provided for the convenience of the reader.
  • the portable wireless-device 12 is used by a customer to make a payment transaction at a retail-merchant site.
  • a portable wireless device 12 in the form of a cell phone is equipped with an optical reader camera 12E, a screen 12B, a keypad 12A, a mouse 12C and a payment function 12D.
  • the retail merchant has a display screen 14 attached to and being part of the merchant's sales terminal.
  • the display screen 14 displays a window 16A, window 16B and a window 16C.
  • the window 16A displays a merchant id, a registered ID and a total for this sale transaction.
  • the merchant id and the register id may be written may be pasted on top of the screen 16D and the window 16A then only would display the payment amount.
  • the window 16A may not be required.
  • the payment amount may be entered via keypad 12A by the customer in the device 12.
  • the window 16B may display the list of items being purchased along with a final total payment. Alternatively, it may display only the final total amount to be paid.
  • the window 16C shows the payment transaction approval record that is received from a card processor 36.
  • the approval record may include an approval code, a date and time and the amount that was approved.
  • the device 12 is in communication with a central system 10, which pre-stores customer and merchant data as described later.
  • the customer activates the pay function 12D. Then faces the device 12 with camera 12E towards the display screen 14, where the camera view angle is 12F is pointed towards the window 16A or 16D.
  • the pay function 12D captures the window 16A or 16D image in the camera and then displays on the device 12 screen 12B entry for a sequence of numeric digits that identify one of customer's accounts to be used for payment of this transaction.
  • Customer enters a Customer Account Personal Identification Number (CAPIN) that has been pre-selected by the customer and is used to both verify the customer to the system 10 as well as identity the particular account to be used for this payment transaction if the customer has more than one account.
  • CAPIN Customer Account Personal Identification Number
  • the pay function 12D converts the image into the numerical data corresponding to the Merchant Identification (MID), Register Identification (RID) and the amount, and sends these data including the CAPIN to the central system 10.
  • the pay function 12D may send the image and the conversion to numerical data may be performed in the system 10.
  • the system 10 receive data from the cell phone 12, verifies the customer by cell phone caller id and
  • the system 10 then sends the retrieved data to CP 36 to process and waits to receive approval/ authorization.
  • the system 10 sends the approval data to the merchant terminal 14, to be displayed in window 16C and also to the customer cell phone 12 to be displayed on screen 12B.
  • the CP 36 may directly send the approval data record to the merchant system which displays it on the sales terminal screen 14 in window 16C.
  • the customer 06 is at a merchant 08 ready to make a payment.
  • the customer 06 activates the payment function and faces the reader element 12E of the wireless device 12 to the merchant terminal 14.
  • the merchant terminal identification 862, register identification 863 and payment amount 852 are received optically via camera image into the wireless device 12.
  • the customer may scan the identification tag 16D using camera 12E and manually enter the payment amount into the device 12. If the customer 06 is not at the location of the merchant 08, the customer may manually enter both the terminal identification 862, and payment amount 852 into the device using its keypad 12A
  • the customer enters CAPIN 854 for a specific existing bankcard and selects payment function 12D.
  • the device 12 sends the payment record 28 to the central system.
  • the system receives record, decodes device ID 850 to find customer ID 854, verifies CAPIN 856 and identifies the specific card 858 chosen by customer 06 for this payment transaction.
  • system 10 creates a transaction reference 870, assembles specific card data of name, card number, expiration date, and merchant identification as the central system business bank 40 and sends the payment transaction to the ACH 36.
  • system 10 receives authorization record, saves the record in the transaction database 842, and forwards the approval data to merchant display terminal.
  • the terminal receives approval data, letting the merchant 08 know that the transaction has been approved.
  • a portable wireless-device 12 is used by the customer to make a payment transaction to a web-merchant.
  • the display terminal screen 14 is displayed on the customer's personal computer, and is provided by the web-merchant.
  • the process of payment to a web-merchant is similar to as described in the first embodiment above.
  • a portable wireless-device 12 is used by the customer to make a payment transaction to a restaurant merchant.
  • the payment system 02 includes a central system 10 and a portable wireless device 12 and a card processor 36.
  • a partition 420 may divide the dining tables with a customer 06 from the merchant computer system 08 with a payment terminal 14.
  • a waiter 422 makes a trip to bring a bill 426 to the customer 06.
  • the bill 426 in addition to the normal items, as illustrated in Figure 1B, carries a service code 436.
  • the service code 436 may be made up of three parts, the merchant number 442, the table number 452 and the server number 454.
  • the customer 06 using device 12 connects to a secure web connection with the system 10 and is presented a data card 414.
  • the customer enters the data as identified and as described later.
  • the central system 10 with the pre-stored data of the merchant and customer and using the card processor 36 process the payment. After the approval of the payment transaction is received from the card processor 36, the central system 10 presents to the customer, on the wireless device 12, a data card 416, and showing that the payment has been processed.
  • the central system 10 concurrently sends to the merchant system 08 a data record 424 showing the payment has been processed successfully.
  • the merchant system 08 is attached to a display terminal 423 that displays the table number, server number, amount and the status of the payment by a color coded display icon 418, where the waiter 422 may verify the payment has been made.
  • the operation of the apparatus 02 for a payment transaction between a customer and a restaurant merchant can be further understood with reference to the Figure 3A, 4A and 4C. Importantly, the order of some or all of the steps can be varied. Further, not all of the steps outlined below may be necessary to perform a payment transaction pursuant to the present invention.
  • step 550 merchant 08 opens an account with central system 10 with a Merchant number 452 and providing merchant identifier 866, URL 864, e-mail 869.
  • customer 06 opens an account at central system 10 with customer ID in form of telephone number 850, CAPIN 856, e-mail 860 and bankcard data 858.
  • waiter 422 brings a bill 426 to a customer 06 with a service code 436.
  • customer 06 takes out his/her wireless device 12 and connects to central system 10 website and is presented a data card 414.
  • customer 06 enters data of customer ID 450, service code 436, amount 430, tip 432 and CAPIN 456 and OK to send to central system 10.
  • central system 10 receives record 414, uses customer id 850 to verify CAPIN 856 and retrieves customer account data 858.
  • central system 10 uses service code 436 to find merchant number 452, retrieve merchant ID 866, assemble payment record and sends to card processor 36.
  • central system 10 receives authorization record from card processor 36, forwards approval data to customer as data card 416.
  • central system 10 forwards approval data record 424 to merchant system 08 for display on display terminal 423 that includes table and server information and payment status 418.
  • the portable wireless-device 12 is used by the customer to make a payment transaction for an online subscription from a web merchant and receive a password to access the service.
  • This embodiment is directed to an online subscription service system that facilitates receiving a subscription service without providing customer personal sensitive data to merchant employees and merchant computer systems.
  • the payment system 02 includes a central system 10, a web-enabled portable wireless device 12, and a card processor 36.
  • a subscription merchant website 626 is accessible to the customer 06, identifying and describing the different subscription choices in terms of content 616 and different pricing 618, 620, 622, and a service code 610.
  • the service code 610 is composed of a merchant number 612 and service number 614. Alternatively, the service code may be only one number or code that uniquely identifies both the merchant and the service in a relational database.
  • the customer 06 using device 12 After having reviewed the website 626, and made a decision to purchase subscription service, the customer 06 using device 12 connects to a secure web connection with the system 10 and is presented a data card 620. From this data card 620, the customer 06 selects from Account 632, Start 634, Cancel 636 and retrieve 638 and is presented data cards 612, 614, 616 and 618 respectively.
  • Start card 614 customer can start a subscriptions service by specifying desired password 630, by using Account card 612, can open an account, by using Cancel card 616 can cancel a service and by using Retrieve card 618, can check the status of the service including the activated password 631 for accessing the service.
  • the desired password 630 is what a customer desires the password to be, the activated password 631 is what the merchant has enabled the particular service for access.
  • the desired password 630 may be Jeff and the activated password may be Jeff999.
  • the central system 10 with the pre-stored data of the merchant and customer and using the card processor 36 processes the payment. After the approval of the payment transaction is received from the card processor 36, the central system 10 sends to the merchant system 08 a data record 624 showing the payment has been successfully processed and the customer desired password 630 to access the service number 614, and awaits a response record 622 for the service activation and confirmation of the activated password 631. After the central system 10 receives the response record 622, it updates the billing table 842D ( Figure 3C) with the activated password 631 and status 636 as Active. The customer 06 by using Retrieve card 618 retrieves the service status 636 and activated password 631 , permitting him/her to access the service. Thus a customer can receive an online subscription service and cancel the service without disclosing any time any personal data to the merchant such as name, e-mail address and bankcard data.
  • Step 500 Merchant 08 opens an account with Central system 10 with a Merchant number 642 and providing merchant ID, merchant name, URL, and e-mail.
  • Step 502 Merchant 08 interfaces with central system 10 and enters Service data including Service Number, subscription fee in service table 840C.
  • Customer 06 connects to system 10, presented data 620, selects Account 632, sees card 612, enters personal number 650, and data 652-658, 654, 658 to open an account.
  • Customer 06 is at web page 626 with intention to purchase service and sees a service code 636.
  • Customer 06 takes out its wireless device 12. Connects to central system 10 and is presented a data card 620.
  • Step 510 Customer selects Start 634 from data card 620 and is presented with start card 614. Enters personal number 650, service code 610, desired password 630 and click OK to send to central system 10.
  • Central System 10 receives card 614, uses personal number 650 to verify and retrieve customer account data 258.
  • Step 514 Central System 10 uses service code 610 to extract merchant number 600, and retrieve merchant ID 604.
  • Step 516 Central System 10 uses service code 610 to extract service number 614, retrieve payment amount 618 from service table 840C, assemble payment record and sends to Card Processor 36.
  • Step 518 Central System 10 receives authorization record from card processor 36. Assembles record 624 including desired password 630 and forwards to merchant system 08.
  • Step 520 Merchant 08 receives record 624 from the central system 10 and activates the service and confirms/changes to activated password 631 and sends record 622 to the central system 10.
  • Central System 10 receives record 622, updates the billing table 842D with activated password 631 and the service status 636 as Active.
  • Customer 06 from data card 620 selects Retrieve 638 and is presented Retrieve card 618. Enters personal number 650 and Clicks OK and receives service code 610, activated password 631 and Status 636.
  • Customer 06 decides to cancel by using device 12 connecting to system 10 and being presented data record 620.
  • Step 528 Customer selects cancel 636, sees cancel card 616, enters personal number 650, service code 610 and OK to send to system 10.
  • Step 530 the system 10 verifies the customer and the service and updates billing table 842D with cancel date 634 equal to system date.
  • the billing function specific to this embodiment is described with reference to Figure 4A.
  • the transaction table 842 and the billing table 842D fields are populated.
  • the periodic billing function performs billing and maintains service status.
  • the billing function is executed every 24 hours.
  • Status Cancel.
  • the cancel date 634 is changed to system date by the customer interface program 810, when customer cancels service via the Cancel card 636.
  • IF (Status Expire Or Null Or Cancel Or Decline) Return.
  • the status is initialized to null and changes state when service is cancelled, expires or the card payment is declined.
  • Initiate Payment Function 808 for amount Periodic fee 620.
  • Payment Function 808 assembles payment record and submits to the card processor 36.
  • card processor 36 authorizes approval. If approved, Status is not changed, if declined then, Status is changed to Decline.
  • the online subscription system 02 allows an online subscription service merchant 08 to receive payments from a subscription customer 06 and allows customer 06 to receive subscription service with activated password 631 , without the customers using and disclosing their personal data to employees of the merchant and merchant computer system.
  • a person or business can make a private and secure payment to another private party of an individual or a business.
  • a payment system between two parties has a central system 10, a portable wireless device 12 belonging to party A 200, the central system 10 and the portable wireless device 12 are on a global computer network 18.
  • the portable wireless device 12 is used to effect a private and secure payment transaction to private party B 202.
  • a party B identification 204 and a payment amount 205 are entered into device 12.
  • the party B identification may be the party B's telephone number 855.
  • Party identification in the form a telephone number is preferred as it is the most widely familiar structure of numbers. In actual use it may be a real telephone number of the party or a made up telephone number. Alternatively other forms of identification may be used.
  • a data record 208 including at least the party B identification 855, the payment amount 205 and a portable wireless device identification code 850 is transferred over the global network 18 to the central system 10.
  • the wireless device identification code is a combination of a pre-programmed identification code and a customer entered CAPIN 856 to identify which card or bank account 858 the payment is being made from.
  • the device 12 has a payment function 226.
  • the payment function 226 is a firmware function within the device 12, which may be activated by a menu item called "payment", a key pad key combination such as an arrow key followed by a numeric key, or a special key for payment.
  • the payment function 226 on being activated creates an encrypted payment data record 208 including at least the party B's identification 855, the payment amount, CPIN 856 and the device identification 850 and transfers it over the global network to the central system 10.
  • the central system 10 has two database 838A and 838B that identify party
  • the system 10 assembles a payment transaction record 210 including at least the party A pre- stored bank account data 858, payment amount and identifies a central system business bank 40, submits the payment transaction record 210 to an automated clearing house 36 and receives a payment authorization record 214.
  • the central system 10 using the database 838B identifies Party B's identification 855 and a party B's bank account identification 858.
  • the system 10 assembles a payment transaction record 218 including at least party B 202 pre- stored bank account data, payment amount and identifies the central system bank 40 and submits the payment transaction record 218 to an automated clearing house 36 and receives a payment authorization record 220.
  • the central system 10 having party A and party B identifications and their e-mail addresses 860 in database 838B sends a e-mail notification 225 of the payment authorization to the party A and e-mail notification 224 to party B's e-mail address.
  • party A has made a private and secure payment to party B without either party A or party B knowing each other's personal and sensitive data.
  • party B can make a similar payment to party A.
  • Party A or B need to know each other's telephone number or a pseudo telephone number to make such a private payment
  • party A 200 wishes to make a private payment to party B 202 and inquires party B's telephone number.
  • party A takes out its wireless device 12 and enters party B identification (telephone number), a payment amount, a CPIN and activates payment function 226.
  • the device 12 creates a payment record 208 and sends to central system 10.
  • central system 10 receives the data, decodes device Identification to find the customer identification number and verifies CPIN and identifies the specific account chosen by party A 200 for payment.
  • the central system 10 creates transaction reference, assembles specific account data of party A, central system bank identifier 40, amount and sends to the ACH 36 and receives transfer of funds to the bank 40.
  • the central system 10 creates another transaction reference, assembles specific account data of party B, central system bank identifier 40, and amount and sends to the ACH to effect transfer of funds to party B's bank account.
  • the system 10 saves in transaction database 842 the data associated with the completion of transfer of funds and sends notification e-mail 225 to party A 200 and to party B 224.
  • the payment system 02 enables the use of an ATM to withdraw cash without the need to carry an ATM card. Privacy and security is provided to a user because the ATM card which identifies the owner by name and card number, need not be carried on the person.
  • a cash withdrawal system between a party A 300 and an ATM machine has a central system 10, a portable wireless device 12 belonging to customer 300, an ATM machine 333 and a ATM identification tag 334.
  • the central system 10, the portable wireless device 12, and the ATM 333 are on a global computer network 18 and the portable wireless device 12 is used to effect a cash withdrawal transaction from the ATM 333.
  • the portable wireless device 12 with a built-in reading element 12E, at the time of a withdrawal transaction, reads the terminal identification tag 334 and a withdrawal amount 305, and a CAPIN 856 is entered into it 305.
  • a withdraw function 326 in the wireless device is activated, enabling a data record 308 including at least the ATM terminal identification, the withdrawal amount, a portable wireless device identification code and the CPIN to be transferred over the global network to the central system 10.
  • the device 12 has a withdrawal function 326.
  • the withdrawal function 326 is a firmware function within the device 12, which may be activated by a menu item "withdraw", a key pad key combination such as an arrow key followed by a numeric key, or a special key for payment.
  • the withdraw function 326 on being activated creates an encrypted withdraw data record 308 including at least the ATM terminal identification 334, the withdraw amount 304, CAPIN 856 and the device identification code 850 and transfers it over the global network to the central system 10.
  • the central system 10 assembles a withdraw transaction record 324 including the customer pre-stored bank account data 858, and submits the withdraw transaction record to the ATM system 333, enabling the ATM to process and disburse cash amount to the party 300.
  • the ATM 333 knowing the means of arrival of ATM card data from the central system 10 as opposed to from an ATM card insertion, suppresses printing of a paper record for the ATM customer, because an e-mail notification 325 is sent to the party 300 by the central system 10.
  • the payment system 02 between a customer 06 and a merchant 08 has a central system 10, a portable wireless device 12, and a merchant display terminal 14 with an identification tag 16D.
  • the central system, the portable wireless device and the merchant terminal are on a global computer network 18.
  • the portable wireless device is used to effect a private and secure payment transaction from the customer to the merchant.
  • the central system 10 provides a customer interface 03 allowing the interface to receive record 78 from customer 06 to create and enter account data, account identification code, and personal identification code.
  • the interface additionally provides a record 80 to search and retrieve payment and refund transactions by type of transaction, transaction date, and merchant identification. It allows entry of customer identifying data and search query and receiving the data so requested.
  • the interface is web-based and is prior art.
  • the central system 10 provides a merchant interface 04 allowing the interface to receive record 82 from merchant to enter merchant identification, merchant account identification, and terminal identification.
  • the interface additionally provides a record 84 to search and retrieve payment and refund transactions by type of transaction, by date, and transaction reference number.
  • the interface allows entry of merchant identifying data, and a search query and receiving the data so requested.
  • the interface is web-based and is prior art.
  • the central system 10 assembles a payment transaction record 32 that includes the customer pre-stored bank account data 858, and submits the payment transaction record to an automated clearing house 36 and receives a payment authorization record 38. Subsequently the central system 10 sends the payment authorization record 38 to the merchant display terminal 14 using the terminal uniform resource locator 864 over the global computer network.
  • the payment transaction record 32 submitted to the ACH 36 identifies a central system business bank 40 for receiving payment amount from the customer bank 22.
  • the ACH depending upon the form of the bankcard or bank account is prior art bankcard authorization network for authorizing amounts from customer banks or a check automated clearinghouse used by banks to clear checks with each other.
  • the merchant funds from a plurality of payment transactions are in the bank 40. These merchant funds are transferred to the merchant bank account 48 on a periodic basis.
  • the central system 10 has a merchant database 840 that maintains the terminal identification 862 and merchant identification 866 and a merchant bank account identification 868.
  • the system 10 creates and submits a merchant payment record 46 to the ACH for transferring an aggregate amount from a plurality of payment transactions from the central system business bank 40 into the merchant bank account 48.
  • the central system 10 maintains a transaction database 842 cataloging each payment transaction by a transaction reference 870, date and time 872, an authorization reference 874, payment amount 876, customer identification 854, merchant identification 866, and payment sequence number 857.
  • the merchant 08 is paying the customer 06 for a refund from a previous payment transaction.
  • a merchant refund terminal 66 is part of the merchant system 20, which is on the global computer network 18.
  • the refund terminal 66 may a web-based interface.
  • the merchant 08 enters into the refund terminal 66 a refund record 68 that includes the payment transaction reference 870 from a previous payment transaction, merchant identification 866, a refund-authorizing password, and a refund amount and then the refund record 68 is sent to the central system 10.
  • the central system 10 receives the refund record 68 from the merchant system 20 and verifies the elements of the record against the transaction catalog 842, in particular, verifying the refund amount is less than or equal to the payment amount.
  • the central system then creates a refund ACH record 74 identifying the central system bank 40 as the bank for receiving funds from the merchant bank account 48.
  • the refund record 74 is sent to the ACH 36 and an approval record 75 is received.
  • the central system 10 then forwards the refund approval record 75 to the refund terminal 66.
  • the merchant system 20 having the refund terminal 66 is equipped with a printer capability 76 and prints a refund record.
  • the central system 10 then creates a fund transfer record and submits to ACH 36 for crediting the funds from the central system bank 40 to the customer bank account 22.
  • the portable wireless device 12 may be a cellular telephone with a screen and a keypad. Alternatively, it may be PDA with a wireless modem, which also has a display screen and a soft keypad.
  • the portable wireless device 12 has an interface that enables it to receive merchant identification and payment amount at the time of the payment transaction.
  • the interface may consist of a numeric keypad with a screen, an optical-magnetic reading element or an infrared reading element. The operation of the interface is described below.
  • Figure 1A shows a wireless device 12, with a keypad 12A, a cursor control
  • the interface may consist of the customer manually entering the merchant identification and the payment amount in the wireless device using the keypad 12A and the screen 12B. Typically, the customer may not be at the location where the merchant is located such as for a catalog merchant, and is given the information by the merchant.
  • the customer is at a merchant checkout counter and is holding the device 12 in his hand enabling it to capture the data optically.
  • the interface may also have a reading element 12E that scan- reads the identification tag 16D to read the terminal ID and a payment amount is manually entered into the device 12 by the customer.
  • the reading element 12E is an optical type.
  • the tag 16D is of the type as shown in Figure 1A showing numerical characters that can be read by an optical lens.
  • the identification tag 16D identifies the merchant, the store, and the terminal within the store for those merchants having more than one store and having more than one payment terminal in a store. Typically, when the customer is at merchant checkout counter, the customer is holding the device 12 in his/her hand and scans the tag 16D to read the terminal identification. And then subsequently enters a payment amount.
  • a CAPIN 856 is a personal identification code that identifies the customer and/or identifies the customer and one of the bankcards he/she wishes to use for the payment transaction.
  • the device 12 has an identification code 850, which uniquely identifies the device.
  • the code 850 may be the telephone number assigned to the device 12 or the code 850 may be a identification identifying the chip inside the device 12 or the code 850 may be the frequency code used by the device 12.
  • the device 12 has a payment function 26.
  • the payment function 26 is a firmware function within the device 12, which may be activated by a menu item "payment", a keypad key combination such as an arrow key followed by a numeric key, or a special key for payment.
  • the payment function 26, on being activated, creates an encrypted payment data record 28 including at least the merchant terminal identification 862, the payment amount 24, CAPIN 856 and the device identification code 850 and transfers it over the global network to the central system 10.
  • the system 10 on receiving the data record 28, after decryption, identifies and verifies the customer and the particular bankcard he/she wishes to use for this payment, using the device identification 850 and the CAPIN 856.
  • the customer may have a plurality of pre-stored accounts 858 in the central system 10.
  • the customer enters an account identification in the form of CAPIN 856 into the wireless device 12, identifying a specific account 858 to be used for a payment transaction.
  • the account identification may be a combination of personal identification code verifying the customer and an account identification code and is collectively called CAPIN 856 as described earlier.
  • the central system 10 includes (i) a system storage device 826, (ii) a system operating system 802 stored in the system storage device 826, (iii) a system program 804 stored in the system storage device 826, (iv) and a system processor 230 connected to the system storage device 826.
  • the system processor 830 can include one or more conventional CPU's.
  • the system processor 830 can be capable of high volume processing and database searches.
  • the system storage device 826 can, for example, include one or more magnetic disk drives, magnetic tape drives, optical storage units, CD-ROM drives and/or flash memory.
  • the system storage device 826 also contains a plurality of databases used in the processing of transactions pursuant to the present invention.
  • the system storage device 826 can include a merchant database 840, a customer database 838 and a transaction database 842.
  • the system 10 includes a system network interface (not shown) that allows the system 10 to communicate with the customer 06 and the merchant 08 and the card processor 36.
  • Conventional internal or external modems may serve as the system network interface.
  • the system network interface is connected to the customer, merchant and the card processor on a global network.
  • a merchant network interface (not shown) allows the merchant 08 to communicate with the system 10.
  • Conventional internal or external modems may serve as the merchant network interface.
  • the merchant network interface is connected to the system 10 on the global network.
  • a customer network interface (not shown) allows the customer to communicate with the system 10.
  • Conventional internal or external modems may serve as the customer network interface.
  • the customer network interface is connected to the system 10 on the global network.
  • the system 10 interfaces with a card processor 36 representing a bankcard authorization network.
  • the bankcard authorization network is a computer system that process payments from bankcards using an automated clearing house to process payments between banks.
  • the system 10 interfaces with an ACH/ bank card authorization network 36.
  • the ACH/bankcard authorization network 36 is a computer system that process data from an existing bankcard or an automated clearing house to process payments between banks.
  • the system processor 830 is operative with the system program 804 to perform a Security Function 806, a Payment Processing Function 808, a Customer Interface function 810, a Merchant Interface function 812, an ACH interface function 814, and a Billing function 816.
  • the customer database 838 within the central system 10 contains private data specifically related to the customer 06 that is transferred to the system 10 from the customer.
  • the customer 06, party A 200, party B 202, party 300 may enter data into this database data via a web interface (not shown).
  • the private data related to the customer 06 can be separated and stored in at least two separate sub-databases, namely, (i) an identifier sub-database 838A, and (ii) existing bank card data sub-database 838B.
  • the sub-databases are explained below.
  • This database contains the wireless device identifier 850, payment card number 852 and a customer identification number 854.
  • This database is used by security function 806 on first contact with the central system 10, by a wireless device 12 to identify a customer identification 850.
  • This database contains the customer identifier 850, CAPIN 856, Bank account data 858 and e-mail address 860.
  • the telephone number of the wireless device may serve as the customer identifier.
  • Multiple CAPIN and bank account data for each customer may be maintained allowing a customer to use any one of his/her accounts whether they are checking accounts, debit card accounts or credit card accounts.
  • Card Account Personal Identification Number (CAPIN) may be used to identify one of many cards that the customer wishes to use for a payment.
  • This database maintains private data of the customer anchored by the customer identification number 854.
  • the customer identifier for private party B is a telephone number 855.
  • the other data is CPIN 856, Bank account data 858 and e-mail address 860. Multiple CPIN and bank account data for each customer may be maintained allowing a customer to use any one of his/her accounts whether they are checking accounts, debit card accounts or credit card accounts.
  • the payment sequence number 857 is used to identify one or more payment cards or bank accounts of the customer.
  • the bank account data may contain customer name, bank number/routing number, card or account number and any specific PIN codes for that account.
  • this database maintains data on the merchants who use the payment system 02.
  • the database 840 maintains data on each of the merchant. There are two databases, one is a merchant identifying sub-database 840A and second is merchant bank account data sub-database 840B. There is additional data that is specific to the type of the merchant such as a restaurant, an online subscription merchant and is shown in Figure 3B.
  • the sub-database 840A maintains data on each of the merchant display terminals 862, a terminal URL 864, and a merchant identification number 866 and e-mail address 869.
  • the terminal identification identifies a terminal of the merchant and is the one present on the terminal identification tag and is the one transferred to the wireless device 12.
  • the terminal URL 864 is used to send a payment record to the terminal over the global computer network.
  • the merchant 08 may enter data into this database data via a web interface (not shown).
  • the sub-database 840B maintains data on the merchant identifier 866, merchant name 867 and merchant bank account 868 allowing funds from payment transactions to be directed to the merchant bank 48.
  • the merchant data 867 may include merchant name and address.
  • the type of merchant specific data is a service table 840C maintains data on the services provided by the merchant as Service
  • this database 842 logs all payment transactions by a transaction reference 870, date/time of transaction 872, merchant terminal identification 862 from which the transaction originated, merchant ID 866, amount 876, authorization code 874 received from the ACH/card network and customer identification 854 and the sequence number of the payment account used for this transaction 857.
  • This database may be searched by the customer 06, via a search query record 80, to display payment transactions by a search criterion such as merchant identification and date/time ranges via a web interface (not shown).
  • a search criterion such as merchant identification and date/time ranges via a web interface (not shown).
  • This database may be searched by the merchant 08, via a search query record 82, to display payment transactions by a search criterion such as terminal identification and date/time ranges via a web interface (not shown).
  • the transaction table 842 logs all payment transactions with the card processor 36 by a transaction reference 870, date/time of transaction 872, merchant number 862, amount 876, authorization code 874 received from the card processor 36, customer ID 854 and additionally payment sequence number
  • this database logs all payment transactions that are specific to a merchant type such as for a restaurant merchant, table 842C such as, tip amount 430, table number 452, and server number 454.
  • this database has a billing table 842D.
  • Table 842D is data that is needed to process periodic subscription billing.
  • the billing table 842D maintains service status including pending periodic payment transactions by a combination of direct and computed fields. These fields are: merchant number 612, billing reference 624, personal number 650, service number 614, order/initial bill date 626, next bill date (computed field) 628, number of periods remaining (computed field) 630, authorize number 632, cancel date 634, and status 636.
  • the status field 636 has one of the states of Null or Active or Cancel or Expire or Declined. The logic for the change in these fields is illustrated with reference to figures 4A.
  • the merchant system 08 is a prior art computer system. It may be used by the merchant in conjunction with a card processing terminal 04 that is connected to the card processor 36 to process card payments.
  • the central system program 804 is operative with the central system processor 830 to provide the functions of (i) Security Function 806, (ii) Payment Processing Function 808, (iii) Customer Interface Function 810, (iv) Merchant Interface Function 812, and (v) Billing function 814. Further, the system program 804 is operated with the payment system processor 830 to perform the tasks of the central system 10 provided herein.
  • the Security Function 806 performs the tasks of determining and verifying from the personal number 850 and optional CAPIN 856, the customer 06 and the specific bank account 858 when the customer initiates a payment transaction using the wireless device 12.
  • the system 10 is a secure server and uses encryption when communicating with the device 12 and the card processor 36.
  • the payment processing function 808 performs the tasks of creating payment records and notification records that are transmitted to and from the central system 10. For each payment transaction initiated by the customer via device 12, a payment record to the card processor 36 is assembled. Details of such a payment record are prior art and are used in processing payment transactions with a prior art card-processing network.
  • the card-processing network approves the payment and responds with an approval record containing the same data as in payment record and additionally containing an authorization or approval code and date and time of the approval.
  • the central system 10 on receiving the payment approval record from the card processor 36 creates and sends notification records to the customer and the merchant.
  • the customer Interface function 810 performs the tasks of permitting the customer to open an account and enter customer data.
  • the interface is web based. Alternatively, it could be voice based. The knowledge to create an interface is prior art.
  • the merchant Interface function 812 performs the tasks of permitting the merchant to open an account and enter merchant data.
  • the interface is web based. Alternatively, it could be voice based. The knowledge to create an interface is prior art.
  • the Billing function 814 performs, for an online subscription merchant, the tasks of initial billing, periodic billing and maintaining service status. It uses a service table 840C that identifies all subscriptions from all merchants and billing table 842D that identifies and maintains the status of the service transactions.
  • the payment system 02 allows the customer 06 to use a device 12 in lieu of many bankcards and checks to facilitate private and secure payments to a merchant 08 and private individuals and businesses. Additionally the payment system 02 allows a private party to make a cash withdrawal at an
  • the payment system 02 provides private and secure payment transactions.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système de paiement (02) permettant à un client (06) d'effectuer une transaction de paiement privée et sûre avec un détaillant, un commerçant sur site Web, un restaurateur à une table de salle à dîner, un fournisseur d'abonnement en ligne et une partie privée; et de retirer des espèces à partir d'une machine ATM au moyen d'un dispositif sans fil (12) au lieu d'utiliser des cartes ou des chèques bancaires. Dans toutes ces transactions, le client ne partage pas son identité et des données personnelles sensibles avec les commerçants et la partie privée. Dans lesdites transactions, le client n'a pas besoin de prendre ses cartes bancaires et/ou ses chèques personnels portant des données sensibles et personnelles, ce qui évite les risques de vol ou de perte.
PCT/US2003/002054 2002-01-15 2003-01-14 Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil WO2003060796A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2003235604A AU2003235604A1 (en) 2002-01-15 2003-01-14 Method and apparatus for a private and secure payment system using a wireless device
EP03729695A EP1472636A4 (fr) 2002-01-15 2003-01-14 Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US10/046,834 US7890433B2 (en) 2000-06-30 2002-01-15 Private and secure payment system
US10/046,834 2002-01-15
US10/091,882 US8494957B2 (en) 2000-12-09 2002-03-06 Method and apparatus for restaurant payment system
US10/091,882 2002-03-06
US10/100,380 US9037499B2 (en) 2000-12-09 2002-03-18 Method and apparatus for an online subscription system
US10/100,380 2002-03-18

Publications (1)

Publication Number Publication Date
WO2003060796A1 true WO2003060796A1 (fr) 2003-07-24

Family

ID=27366991

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/002054 WO2003060796A1 (fr) 2002-01-15 2003-01-14 Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil

Country Status (3)

Country Link
EP (1) EP1472636A4 (fr)
AU (1) AU2003235604A1 (fr)
WO (1) WO2003060796A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1566779A1 (fr) * 2004-02-23 2005-08-24 e-Prompt International Holding AG Systeme de transaction
WO2006032944A1 (fr) * 2004-09-22 2006-03-30 NIANE, Mamadou, Tambérou Application nouvelle du telephone mobile gsm au transfert d’ argent
GB2438236A (en) * 2006-05-19 2007-11-21 Mark Edward Ashcroft Using a mobile telecommunications device to perform a monetary transaction
EP1923844A1 (fr) 2006-11-18 2008-05-21 Fiducia IT AG Procédé destiné à l'interaction de clients de banque avec un distributeur automatique, dispositif d'entrée et/ou de sortie mobile correspondant, ainsi que système destiné à la réalisation d'une telle interaction
GB2447709A (en) * 2007-03-23 2008-09-24 Eddie Parker Payment between a user and a merchant using a mobile communications device
EP2056246A1 (fr) * 2007-10-30 2009-05-06 Nederlandse Organisatie voor toegepast-natuurwetenschappelijk Onderzoek TNO Paiements électroniques à l'aide de cartes de paiements
EP2095345A1 (fr) * 2006-10-23 2009-09-02 Behruz Nader Daroga Système de transmission numérique (dts) pour la sécurité de guichets automatiques bancaires (atm)
EP2463817A1 (fr) * 2010-12-10 2012-06-13 1356382 Alberta Ltd. Système et procédé pour l'interopérabilité de différentes plateformes d'autorisation de paiements ou de transactions
EP3142055A1 (fr) * 2015-09-08 2017-03-15 SK Planet Co., Ltd. Appareil, procédé, système de fourniture de services de paiement sur le web et support d'informations non transitoire lisible par ordinateur mémorisant un programme informatique enregistré en son sein

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6038548A (en) * 1997-11-26 2000-03-14 International Business Machines Corporation System and method for conducting electronic commerce in a computer network using a cashier desk payment framework
DE19903363A1 (de) 1999-01-28 2000-08-10 Mueller Judex Donald Verfahren, System und Mobilstation zur Durchführung von bargeldlosen Transaktionen
US6295428B1 (en) * 1998-12-17 2001-09-25 Canon Kabushiki Kaisha Image forming apparatus carrying charged particles on resin sleeve

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997045814A1 (fr) * 1996-05-24 1997-12-04 Behruz Vazvan Procede et systeme en temps reel servant a effectuer des transactions a distance de paiement de factures et d'achats et a transferer de la monnaie electronique et d'autres donnees
JP3660101B2 (ja) * 1996-11-14 2005-06-15 松下電器産業株式会社 パーソナル電子決済システム
EP1093097A3 (fr) * 1999-10-14 2004-01-07 International Business Machines Corporation Système et méthode pour réaliser des transactions financières sécurisées
JP3437148B2 (ja) * 2000-06-13 2003-08-18 株式会社エイティング 携帯端末による電子決済方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6038548A (en) * 1997-11-26 2000-03-14 International Business Machines Corporation System and method for conducting electronic commerce in a computer network using a cashier desk payment framework
US6295428B1 (en) * 1998-12-17 2001-09-25 Canon Kabushiki Kaisha Image forming apparatus carrying charged particles on resin sleeve
DE19903363A1 (de) 1999-01-28 2000-08-10 Mueller Judex Donald Verfahren, System und Mobilstation zur Durchführung von bargeldlosen Transaktionen

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1472636A4

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1566779A1 (fr) * 2004-02-23 2005-08-24 e-Prompt International Holding AG Systeme de transaction
WO2006032944A1 (fr) * 2004-09-22 2006-03-30 NIANE, Mamadou, Tambérou Application nouvelle du telephone mobile gsm au transfert d’ argent
GB2438236A (en) * 2006-05-19 2007-11-21 Mark Edward Ashcroft Using a mobile telecommunications device to perform a monetary transaction
EP2095345A1 (fr) * 2006-10-23 2009-09-02 Behruz Nader Daroga Système de transmission numérique (dts) pour la sécurité de guichets automatiques bancaires (atm)
EP2095345A4 (fr) * 2006-10-23 2011-04-27 Behruz Nader Daroga Système de transmission numérique (dts) pour la sécurité de guichets automatiques bancaires (atm)
EP1923844A1 (fr) 2006-11-18 2008-05-21 Fiducia IT AG Procédé destiné à l'interaction de clients de banque avec un distributeur automatique, dispositif d'entrée et/ou de sortie mobile correspondant, ainsi que système destiné à la réalisation d'une telle interaction
GB2447709A (en) * 2007-03-23 2008-09-24 Eddie Parker Payment between a user and a merchant using a mobile communications device
EP2056246A1 (fr) * 2007-10-30 2009-05-06 Nederlandse Organisatie voor toegepast-natuurwetenschappelijk Onderzoek TNO Paiements électroniques à l'aide de cartes de paiements
WO2009058010A1 (fr) * 2007-10-30 2009-05-07 Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno Paiements électroniques effectués à l'aide d'une carte de paiement
EP2463817A1 (fr) * 2010-12-10 2012-06-13 1356382 Alberta Ltd. Système et procédé pour l'interopérabilité de différentes plateformes d'autorisation de paiements ou de transactions
EP3142055A1 (fr) * 2015-09-08 2017-03-15 SK Planet Co., Ltd. Appareil, procédé, système de fourniture de services de paiement sur le web et support d'informations non transitoire lisible par ordinateur mémorisant un programme informatique enregistré en son sein

Also Published As

Publication number Publication date
EP1472636A4 (fr) 2005-03-09
EP1472636A1 (fr) 2004-11-03
AU2003235604A1 (en) 2003-07-30

Similar Documents

Publication Publication Date Title
US20220019984A1 (en) System and method for a private and secure merchant payment system using a mobile wireless device
US9037499B2 (en) Method and apparatus for an online subscription system
US10825016B2 (en) Electronic bearer bond online transaction and card system and method thereof
US20020016749A1 (en) Methods and systems for network based electronic purchasing system
US20150206128A1 (en) Contactless wireless transaction processing system
US20120232981A1 (en) Contactless wireless transaction processing system
US20150371212A1 (en) Integrated transaction and account system
US20070185780A1 (en) System for anonymous purchase of goods by providing a pluarlity of active account numbers
WO2004079603A1 (fr) Systeme de transaction
WO2012109485A1 (fr) Système de traitement de transaction sans fil et sans contact
JP2004326348A (ja) 携帯端末を利用したプリペイド型電子マネー決済システム及び方法
US20050108117A1 (en) Method and apparatus for providing itemization detail for credit card transactions
US20030182207A1 (en) Electronic Commerce Transaction System
US20040122767A1 (en) Method for secure, anonymous electronic financial transactions
EP1472636A1 (fr) Procede et appareil pour systeme de paiement prive et sur au moyen d'un dispositif sans fil
US20140032372A1 (en) Transaction system and method
WO2009140731A1 (fr) Système et procédé pour faciliter une transaction de paiement
US20230113356A1 (en) A method and system for making a secure payment
TW381240B (en) Automatic payment method and apparatus
WO2013170101A2 (fr) Système de traitement de transactions sans fil et sans contact

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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 NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

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 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
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REEP Request for entry into the european phase

Ref document number: 2003729695

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2003729695

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003729695

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: JP