EP1246144A2 - Wireless point of sale transaction - Google Patents
Wireless point of sale transaction Download PDFInfo
- Publication number
- EP1246144A2 EP1246144A2 EP01610070A EP01610070A EP1246144A2 EP 1246144 A2 EP1246144 A2 EP 1246144A2 EP 01610070 A EP01610070 A EP 01610070A EP 01610070 A EP01610070 A EP 01610070A EP 1246144 A2 EP1246144 A2 EP 1246144A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- customer
- transaction
- wireless communications
- customer device
- transaction system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
- 238000004891 communication Methods 0.000 claims abstract description 92
- 238000000034 method Methods 0.000 claims abstract description 58
- 238000012545 processing Methods 0.000 claims abstract description 20
- 230000004044 response Effects 0.000 claims description 61
- 238000013475 authorization Methods 0.000 claims description 26
- 238000012546 transfer Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 5
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000008569 process Effects 0.000 description 21
- 230000008901 benefit Effects 0.000 description 11
- 238000012790 confirmation Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- VBMOHECZZWVLFJ-GXTUVTBFSA-N (2s)-2-[[(2s)-6-amino-2-[[(2s)-6-amino-2-[[(2s,3r)-2-[[(2s,3r)-2-[[(2s)-6-amino-2-[[(2s)-2-[[(2s)-6-amino-2-[[(2s)-2-[[(2s)-2-[[(2s)-2,6-diaminohexanoyl]amino]-5-(diaminomethylideneamino)pentanoyl]amino]propanoyl]amino]hexanoyl]amino]propanoyl]amino]hexan Chemical compound NC(N)=NCCC[C@@H](C(O)=O)NC(=O)[C@H](CCCCN)NC(=O)[C@H](CCCCN)NC(=O)[C@H]([C@@H](C)O)NC(=O)[C@H]([C@H](O)C)NC(=O)[C@H](CCCCN)NC(=O)[C@H](C)NC(=O)[C@H](CCCCN)NC(=O)[C@H](C)NC(=O)[C@H](CCCN=C(N)N)NC(=O)[C@@H](N)CCCCN VBMOHECZZWVLFJ-GXTUVTBFSA-N 0.000 description 8
- 108010068904 lysyl-arginyl-alanyl-lysyl-alanyl-lysyl-threonyl-threonyl-lysyl-lysyl-arginine Proteins 0.000 description 8
- 239000003795 chemical substances by application Substances 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 5
- 238000004422 calculation algorithm Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 241000692881 Polygonia faunus Species 0.000 description 1
- 206010000210 abortion Diseases 0.000 description 1
- 235000008452 baby food Nutrition 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000005670 electromagnetic radiation Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000005294 ferromagnetic effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000005291 magnetic effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005855 radiation Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/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/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- 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
-
- 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/20—Point-of-sale [POS] network 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/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/322—Aspects of commerce using mobile devices [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/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/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/68—Payment of value-added services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0196—Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/32—Involving wireless systems
Abstract
Description
establishing respective wireless communications links between the transaction system and a number of customer devices corresponding to respective customers; and
identifying the first customer device among the number of customer devices having established respective wireless communications links as being a customer device carried by a selected customer.
It is an advantage of the invention, that it allows customers to use a customer device to instead of a traditional credit card, otherwise leaving the customer's shopping experience unchanged. Examples of other transactions include the transfer of data, the use of tokens, e.g. bonus or credit points, etc.
- assigning respective identifiers to each of the number of customer devices by the transaction system, a first identifier being assigned to the first customer device;
- transmitting the respective identifiers from the transaction system to the corresponding customer devices via the corresponding wireless communications links; and
- using the first identifier to identify the first customer device carried by the selected customer.
- presenting the first identifier to the selected customer by the first customer device; and
- receiving a first input by the transaction system from a user of the transaction system, the first input being indicative of the first identifier.
- storing in a storage medium a set of customer data items in relation to a set of device data items, the set of customer data items being indicative of a set of registered customers and the set of device data items being indicative of a corresponding set of customer devices;
- presenting to a user of the transaction system selected ones of the set of customer data items related to the customer devices having established respective wireless communications links;
- receiving a second input by the transaction system from the user of the transaction system, the second input being indicative of a selected one of the presented customer data items.
- transmitting a second data signal indicative of the predetermined amount from the transaction system to the first customer device via the corresponding wireless communications link;
- receiving a third input from the selected customer to the wireless customer device, the third input being indicative of an authorisation to transfer the predetermined amount from the customer account to the recipient account;
- transmitting the first data signal in response to the third input; and
- initiating the transfer of the predetermined amount by the transaction system in response to the received first data signal.
- communications means for establishing respective wireless communications links between the transaction component and corresponding ones of the number of customer devices; and
- means for identifying a first one of the number of customer devices having established respective wireless communications links as being a customer device carried by a selected one of the customers.
- the means for identifying a first one of the number of customer devices comprise first processing means adapted to assign respective identifiers to each of the number of customer devices, a first identifier corresponding to the first customer device;
- the communications means is adapted to transmit the respective identifiers from the transaction component to corresponding customer devices via the corresponding wireless communications links; and
- the means for identifying a first one of the number of customer devices comprises means for using the identifier to associate the selected customer with the first customer device.
- first output means for presenting the first identifier to the selected customer; and
- first input means for receiving a first input from a user of the transaction component, the first input being indicative of the first identifier.
- a storage medium adapted to store a set of customer data items in relation to a set of device data items, the set of customer data items being indicative of a set of registered customers and the set of device data items being indicative of a corresponding set of customer devices;
- second output means for presenting selected ones of the set of customer data items to a user of the transaction component; and
- second input means for receiving a second input from the user, the second input being indicative of a selected one of the presented customer data items.
- the transaction request includes a request to transfer a predetermined amount from a customer account to a recipient account;
- the communication means is adapted to transmit a second data signal indicative of the predetermined amount from the transaction component to the first customer device via the corresponding wireless communications link;
- the first customer device comprises third input means for receiving a third input from the selected customer, the third input being indicative of an authorisation to transfer the predetermined amount from the customer account to the recipient account;
- the communication means is further adapted to transmit the first data signal in response to the third input; and
- the system further comprises second processing means adapted to initiate the transfer of the predetermined amount by the transaction component in response to the received first data signal.
- communications means for establishing a wireless communications link between the customer device and the transaction system; and
- means for assisting the transaction system in identifying the customer device among a number of customer devices having established respective wireless communications links as being a customer device carried by a selected customers.
- communications means for establishing respective wireless communications links between the transaction system and a number of customer devices; and
- means for identifying the first customer device among the number of customer devices having established respective wireless communications links as being a customer device carried by a selected customer.
- the
customer 501, i.e. the person shopping and paying using a customer device according to the invention, - the
issuing agent 503, i.e. the agent issuing the electronic credit cards, e.g. via the bank of thecustomer 501, - the
merchant 502, i.e. the company offering a payment service according to the invention, - the
acquirer 505, i.e. the bank of themerchant 502, and - the
collector 504, i.e. a company acting as intermediate between merchants and acquirers.
- Open:
- The customer has chosen to pay using the PTD. Multiple customers may be queued in the system, waiting to pay.
- Active:
- The transaction has been tied to a purchase and the total amount to be paid is known. Preferably, only one transaction can be active per POS.
- Offered:
- The customer has been issued a payment contract to sign. Preferably, only one transaction may be offered per POS.
- Signed:
- The customer has signed the payment contract and it has been forwarded to the collector. Preferably, only one transaction may be signed per POS.
- Authorised:
- The collector has authorised the payment. Preferably, only one transaction may be authorised per POS.
- Completed:
- The POS system has written a paper receipt to the customer.
contract ::= <amount> NEWLINE <acceptor>
amount ::= "Pay" NEWLINE <currency> SPACE <value>
currency ::= [AAA-ZZZ]
value ::= [0.00-99999999.99]
acceptor ::= "to: "<name> NEWLINE <street> NEWLINE <city>
name ::= [A-Za-z0-9][A-Za-z0-9 ]*
street ::= [A-Za-z0-9][A-Za-z0-9 ]*
city ::= [A-Z][A-Za-z0-9 ]*.
"Pay
USD 20.00
to: Joe's Grocery Store
Someroad 20A
Sometown"
- Serial number:
- The serial number of the certificate assigned by the certification authority (CA).
- Signature algorithm:
- Preferably a secure hash algorithm (SHA-1) with RSA encryption.
- Issuer:
- Distinguished name of the CA as specified by the standard RFC2459 (X.509 certificate profile).
- Subject:
- Distinguished name of the customer as specified by RFC2459 (X.509 certificate profile).
- Subject Public Key Info:
- The customer's public RSA key.
- Validity:
- Validity period of customer's certificate. Represented using UTC time.
- Extensions:
- SubjectAltName: encrypted track 2 information, i.e. card number and expire date. KeyUsage: digitalSignature and nonRepudiation)
- ID:
- The transaction's ID (equal to the ID in the signed contract), e.g. a 14 digit integer. The ID is made up of a 4-digit year, a 2-digit month, a 2-digit date, and a 6-digit serial number.
- ACCEPTOR:
- Identification of the merchant extracted from merchant certificate, e.g. a 20-digit number constructed by concatenating the organisation and card acceptor id numbers.
- VAT:
- The amount of VAT paid by the customer. The currency is the same as expressed in the contract, e.g. an integer expressing the amount in the smallest unit of the currency.
- LOCALE:
- Indicates the locale of the contract, i.e. the language and number representation used to format the contract, e.g. "en-US" for English language and US as country.
- CONTRACT:
- The contract signed by the customer, e.g. Base64-encoded data.
- The signed contents received from the PTD is decoded (e.g. base64 and ASN-1/DER) into a data structure as specified in the WAP 1.2 WML script cryptography library specification.
- The contract text is inserted into the data structure.
- The data structure is transformed from WAP standard to PKCS#7 layout and encoded according to PKCS#7.
- The resulting binary data is base64 encoded.
"<!xml version=1.0/>
<MeTAuthorisationRequest>
<ID>20001012123456</ID>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
<VAT>500</VAT>
<LOCALE>en-US</LOCALE>
<CONTRACT>kFr4G78i45e46h8g5+4HFi4Ut78H5DDhGKj7bi66nswe</C
ONTRACT>
</MeTAuthorisationRequest>."
- ID:
- Transaction ID
- ACCEPTOR:
- Identification of merchant extracted from merchant certificate.
- STATUS:
- Indicates whether authorisation was granted. Status values may comprise "authorised", "unknown merchant", "duplicate transaction", "merchant certificate invalid", "merchant certificate expired", "merchant certificate revoked", "customer certificate invalid", "customer certificate expired", "customer certificate revoked", "bad merchant signature", "bad customer signature", "invalid contract", "invalid date", "invalid amount", "system error".
- CURRENCY:
- The currency of total and VAT.
- TOTAL:
- The total amount authorised.
- VAT:
- VAT of authorised amount.
"<!xml version=1.0/>
<MeTAuthorisationResponse>
<ID>20001012123456</ID>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
<STATUS>0</STATUS>
<CURRENCY>USD</CURRENCY>
<TOTAL>2000</TOTAL>
<VAT>500</VAT>"
</MeTAuthorisationResponse>."
response := <authorised> | <failed>
authorised ::= "AUTH" SPACE <currency> SPACE <value>
currency ::= [AAA-ZZZ]
value ::= [0,00-99999999,99]
failed ::= "FAIL" SPACE <reason>
reason ::= "COMFAILURE" | "INVALIDMERC" |
"INVALIDCARD" | "EXPIREDCARD" | "REVOKEDCARD."
- COMFAILURE:
- The merchant system failed to communicate with the collector. Either the connection could not be established or there was an error in the format of the messages.
- INVALIDMERC:
- The merchant system was not recognised by the collector. The merchant may not be registered or have an invalid, expired or revoked certificate.
- INVALIDCARD:
- The customer's certificate was not recognised by the collector.
- EXPIREDCARD:
- The customer's certificate has expired.
- REVOKEDCARD:
- The customer's certificate has been revoked.
"<!xml version=1.0/>
< MeTConfirmationResponse > <RESULT>OK</RESULT>
</ MeTConfirmationResponse >."
"http://someserver/servlets/CashRegisterServlet/receipt?c ardno=20001023123456." In response to the
"<!xml version=1.0/>
< MeTReceiptNotificationResponse > <RESULT>OK</RESULT>
</ MeTReceiptNotification Response >."
"<!xml version=1.0/>
<MeTCancelResponse> <RESULT>OK</RESULT>
</ MeTCancelResponse >."
- The payment application cancels the transaction before it forwards the contract to the collector. For example, the cancellation may be caused by an invalid contract or invalid customer certificates. When the application cancels the ongoing transaction, it sends cancel responses to the PTD and POS system, respectively. The cancel responses may be given in response to any PTD or POS request.
- The collector may decline authorisation. In this case, a negative payment response is sent to the PTD, and a negative confirmation response is sent to the POS.
- A communication failure may have occurred, e.g. due to a failure to connect to a remote system or due to garbled, incomplete, or invalid contents of a message. Preferably, it is the responsibility of the PTD and POS system to respond gracefully to the first category of failures. When this happens, the payment application should ensure that the ongoing transaction is marked as failed after a given amount of time. Garbled, incomplete, or invalid request and response messages should be handled gracefully by the PTD, POS, collector, and application. Preferably, this includes reporting the fault to the customer and/or cashier and to respond with cancel response to a request.
- A time-out may occur. In order to guard against system lock-up caused by communication failures or human error, the payment application may impose a time limit on a transaction, i.e. a maximum time between the transaction is created and until it has been cancelled or completed. If a transaction times out, the application should respond with cancel messages to the PTD and POS.
- If the PTD crashes in the middle of a transaction, the connection to the merchant system will be lost. When/if the connection is re-established, the PTD will start a new session with the merchant system. Consequently, the interrupted transaction will time out if it has not reached the "signed" state. If the contract has been signed, and the collector grants authorisation, the customer will receive a receipt from the POS system as notification that the transaction was completed. The customer will not be issued a new contract in this case.
- If the payment application crashes in the middle of a transaction, it will treat all transactions, which have not reached "completed" state, as aborted. Once the application restarts, the interrupted transactions will be closed and cancel messages will be sent to the POS and PTD (if they have not discovered the crash). This ensures that capture is not performed against incomplete transactions, i.e. if the customer has not received a receipt from the POS system, capture will not be performed.
- If the POS system crashes in the middle of a transaction, the transaction will time out, causing cancel messages to be sent to the PTD. Because the transaction did not reach "completed" state, capture will not be performed for it.
- If the collector crashes before an authorisation request has been fully processed, the application does not receive an authorisation response. This will cause the transaction to time out and consequently cancel messages will be sent to the PTD and POS system.
- ACCEPTOR:
- Identification of the merchant extracted from the merchant certificate.
- TRANSACTION:
- ID of transactions to be included in the capture.
"<!xml version=1.0/>
<MeTCaptureRequest>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
<TRANSACTION>20001107034512</TRANSACTION>
<TRANSACTION>20001107034513</TRANSACTION>
<TRANSACTION>20001107034514</TRANSACTION>
</MeTCaptureRequest>."
- ID:
- Capture ID, e.g. a 14 digit integer, e.g. made up of a 4-digit year, a 2-digit month, a 2-digit day, and a 6-digit serial number.
- ACCEPTOR:
- Identification of the merchant extracted from the merchant certificate.
- STATUS:
- Indicates whether capture was accepted.
Examples of status values include "Capture in progress", "unknown merchant", "merchant certificate invalid", "merchant certificate expired", "merchant certificate revoked", "bad merchant signature", "system error". - TRANSACTION:
- ID of transactions included in the capture.
"<!xml version=1.0/>
<MeTCaptureResponse>
<ID>20000912000010</ID>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
<STATUS>0<STATUS>
<TRANSACTION>20001107034512</TRANSACTION>
<TRANSACTION>20001107034513</TRANSACTION>
<TRANSACTION>20001107034514</TRANSACTION>
</MeTCaptureResponse>."
"<!xml version=1.0/>
<MeTReportRequest>
<ID>20000912000010</ID>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
</MeTReportRequest> ."
- ID:
- Capture ID.
- ACCEPTOR:
- Identification of the merchant extracted from the merchant certificate.
- STATUS:
- Indicates whether the capture succeeded.
- INFO:
- Additional information if the capture was rejected, e.g. a text string.
- CURRENCY:
- The currency of credit and debit.
- CREDIT:
- Total amount transferred to the merchant's account.
- DEBIT:
- Total amount deducted from the merchant's account.
"<!xml version=1.0/>
<MeTReportResponse>
<ID>20000912000010</ID>
<ACCEPTOR>74967396749673967385</ACCEPTOR>
<STATUS>0<7STATUS>
<CURRENCY>USD</CURRENCY>
<CREDIT>120000</CREDIT>
<DEBIT>0</DEBIT>
</MeTReportResponse>."
Claims (23)
- A method of processing a transaction request by a first customer device (T1) and a transaction system (100), the transaction request being approved by transmitting a first data signal from the first customer device to the transaction system via a wireless communications link (105); the method comprising the steps of
establishing (113) respective wireless communications links (105,106,107) between the transaction system and a number of customer devices (T1,T2,T3) corresponding to respective customers (A,B,D); and
identifying (114) the first customer device among the number of customer devices having established respective wireless communications links as being a customer device carried by a selected customer (A). - A method according to claim 1, characterised in that the step of identifying the first customer device further comprises the steps ofassigning (203) respective identifiers to each of the number of customer devices by the transaction system, a first identifier being assigned to the first customer device;transmitting (204) the respective identifiers from the transaction system to the corresponding customer devices via the corresponding wireless communications links; andusing (205,207,208) the first identifier to identify the first customer device carried by the selected customer.
- A method according to claim 2, characterised in that the first identifier is a sequence of alphanumeric characters.
- A method according to claim 3, characterised in that the first identifier comprises less than five characters.
- A method according to any one of claims 2 through 4, characterised in that the first identifier has a length determined by the transaction system on the basis of the number of customer devices having established a wireless communications link with the transaction system.
- A method according to any one of claims 2 through 5, characterised in that the step of using the first identifier to identify the first customer device comprises the steps ofpresenting (205) the first identifier to the selected customer by the first customer device; andreceiving (207) a first input by the transaction system from a user of the transaction system, the first input being indicative of the first identifier.
- A method according to claim 1, characterised in that the method further comprises the steps ofstoring in a storage medium (104b, 411) a set of customer data items in relation to a set of device data items, the set of customer data items being indicative of a set of registered customers and the set of device data items being indicative of a corresponding set of customer devices;presenting (407) to a user of the transaction system selected ones of the set of customer data items related to the customer devices having established respective wireless communications links;receiving (408) a second input by the transaction system from the user of the transaction system, the second input being indicative of a selected one of the presented customer data items.
- A method according to claim 7, characterised in that the step of presenting selected ones of the set of customer data items further comprises the step of selecting a subset of the number of customer devices based on additional information about the customer devices.
- A method according to claim 7 or 8, characterised in that the step of presenting selected ones of the set of customer data items further comprises the step of presenting the selected customer data items in a predetermined order based on additional information about at least one of the customer data and the customer devices.
- A method according to claim 8 or 9, characterised in that the additional information comprises reception characteristics of at least the established wireless communications links.
- A method according to any one of the claims 1 through 10, characterised in that the transaction includes a transfer of a predetermined amount from a customer account to a recipient account, and the method further comprises the steps oftransmitting a second data signal (720) indicative of the predetermined amount from the transaction system (Sv1) to the first customer device (PTD) via the corresponding wireless communications link;receiving (721) a third input from the selected customer to the wireless customer device, the third input being indicative of an authorisation to transfer the predetermined amount from the customer account to the recipient account;transmitting the first data signal (722) in response to the third input; andinitiating (724) the transfer of the predetermined amount by the transaction system in response to the received first data signal.
- A method according to any one of the claims 1 through 11, characterised in that at least a first one of the respective wireless communications links is a Bluetooth link.
- A method according to any one of the claims 1 through 12, characterised in that the transaction system is a point of sale system.
- A system for processing a transaction request, the system including a transaction component and a number of customer devices (T1,T2,T3) carried by respective customers (A,B,D), a transaction request being approved by transmitting a first data signal from a customer device to the transaction component via a wireless communications link (105,106,107); the system comprisingcommunications means (102) for establishing respective wireless communications links between the transaction component and corresponding ones of the number of customer devices; andmeans for identifying a first one (Tl) of the number of customer devices having established respective wireless communications links as being a customer device carried by a selected one (A) of the customers.
- A system according to claim 14, characterised in thatthe means for identifying a first one of the number of customer devices comprise first processing means (104) adapted to assign respective identifiers to each of the number of customer devices, a first identifier corresponding to the first customer device;the communications means is adapted to transmit the respective identifiers from the transaction component to corresponding customer devices via the corresponding wireless communications links; andthe means for identifying a first one of the number of customer devices comprises means for using the identifier to associate the selected customer with the first customer device.
- A system according to claim 14 or 15, characterised in that the means for using the identifier to associate the selected customer with the first customer device comprisesfirst output means (T1a) for presenting the first identifier to the selected customer; andfirst input means (101b) for receiving a first input from a user of the transaction component, the first input being indicative of the first identifier.
- A system according to claim 14, characterised in that the system further comprisesa storage medium (104b, 411) adapted to store a set of customer data items in relation to a set of device data items, the set of customer data items being indicative of a set of registered customers and the set of device data items being indicative of a corresponding set of customer devices;second output means (101a) for presenting selected ones of the set of customer data items to a user of the transaction component; andsecond input means (101b) for receiving a second input from the user, the second input being indicative of a selected one of the presented customer data items.
- A system according to any one of the claims 14 through 17, characterised in thatthe transaction request includes a request to transfer a predetermined amount from a customer account to a recipient account;the communication means is adapted to transmit a second data signal indicative of the predetermined amount from the transaction component to the first customer device via the corresponding wireless communications link;the first customer device comprises third input means for receiving a third input from the selected customer, the third input being indicative of an authorisation to transfer the predetermined amount from the customer account to the recipient account;the communication means is further adapted to transmit the first data signal in response to the third input; andthe system further comprises second processing means adapted to initiate the transfer of the predetermined amount by the transaction component in response to the received first data signal.
- A customer device for processing a transaction request from a transaction system, a transaction request being approved by transmitting a first data signal from the customer device to the transaction system via a wireless communications link; the customer device comprisingcommunications means for establishing a wireless communications link between the customer device and the transaction system; andmeans for assisting the transaction system in identifying the customer device among a number of customer devices having established respective wireless communications links as being a customer device carried by a selected customers.
- A customer device according to claim 19, characterised in that the customer device is a mobile terminal.
- A transaction system for processing a transaction request to be approved by a first customer device by transmitting a first data signal from the first customer device to the transaction system via a wireless communications link; the transaction system comprisingcommunications means for establishing respective wireless communications links between the transaction system and a number of customer devices; andmeans for identifying the first customer device among the number of customer devices having established respective wireless communications links as being a customer device carried by a selected customer.
- A computer program comprising program code means for performing all the steps of any one of the claims 1 through 13 when said program is run on a computer.
- A computer program according to claim 22, characterised in that the computer program is embodied on a computer-readable medium.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/472,966 US7587196B2 (en) | 2001-03-29 | 2002-03-05 | Wireless point of sale transaction |
PCT/EP2002/002461 WO2002080120A2 (en) | 2001-03-29 | 2002-03-05 | Wireless point of sale transaction |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DK200100520 | 2001-03-29 | ||
DKPA200100520 | 2001-03-29 | ||
DKPA200100582 | 2001-04-09 | ||
DK200100582 | 2001-04-09 |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1246144A2 true EP1246144A2 (en) | 2002-10-02 |
EP1246144A3 EP1246144A3 (en) | 2003-11-12 |
Family
ID=26068995
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01610071A Withdrawn EP1246145A3 (en) | 2001-03-29 | 2001-07-05 | A method and system for purchasing goods |
EP01610070A Ceased EP1246144A3 (en) | 2001-03-29 | 2001-07-05 | Wireless point of sale transaction |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01610071A Withdrawn EP1246145A3 (en) | 2001-03-29 | 2001-07-05 | A method and system for purchasing goods |
Country Status (1)
Country | Link |
---|---|
EP (2) | EP1246145A3 (en) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10337081A1 (en) * | 2003-08-12 | 2005-03-17 | Deutsche Postbank Ag | Credit note handling device e.g. for credit transfer via mobile phone server network, includes credit note computer for handling credit note at/for credit account |
WO2005073934A1 (en) * | 2004-01-28 | 2005-08-11 | Aron Matalon | Method and system for authenticating credit transactions |
EP3167416A1 (en) * | 2014-07-11 | 2017-05-17 | Google, Inc. | Hands-free transactions with a challenge request |
EP3167417A1 (en) * | 2014-07-11 | 2017-05-17 | Google, Inc. | Hands-free offline communications |
US10460317B2 (en) | 2014-07-11 | 2019-10-29 | Google Llc | Hands-free transaction tokens via payment processor |
US10474879B2 (en) | 2016-07-31 | 2019-11-12 | Google Llc | Automatic hands free service requests |
US10482463B2 (en) | 2016-03-01 | 2019-11-19 | Google Llc | Facial profile modification for hands free transactions |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080126251A1 (en) * | 2006-09-21 | 2008-05-29 | Tomas Karl-Axel Wassingbo | System and method for utilizing a portable network device to initiate and authorize a payment transaction |
DE102011081751B3 (en) * | 2011-08-29 | 2013-02-07 | MFL Suisse GmbH | Method for operating at least one vending machine |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5804807A (en) * | 1996-09-12 | 1998-09-08 | Symbol Technologies, Inc. | Scan-ahead system for processing merchandise at a checkout register |
US5978772A (en) * | 1996-10-11 | 1999-11-02 | Mold; Jeffrey W. | Merchandise checkout system |
JP2000004299A (en) * | 1998-06-17 | 2000-01-07 | Nec Corp | Turn wait calling device |
US6175922B1 (en) | 1996-12-04 | 2001-01-16 | Esign, Inc. | Electronic transaction systems and methods therefor |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE4443018C2 (en) * | 1994-12-02 | 2001-02-08 | Shopping Box Gmbh & Co Kg | Process for ordering goods |
DK175911B1 (en) * | 1997-05-26 | 2005-06-20 | Metax Olie As | Automatic fuel release system and method of refueling a vehicle |
JP2000184085A (en) * | 1998-12-18 | 2000-06-30 | Fujitsu Ltd | Portable equipment, attachment for portable terminal and system using portable equipment |
US6721542B1 (en) * | 1999-05-28 | 2004-04-13 | Nokia Corporation | System for location specific, automatic mobile station behavior control |
IL130505A0 (en) * | 1999-06-16 | 2000-06-01 | Israwash Ltd | Method and system for remote purchase payments |
AU7346800A (en) * | 1999-09-02 | 2001-03-26 | Automated Business Companies | Communication and proximity authorization systems |
FI19991978A (en) | 1999-09-16 | 2001-03-16 | Nokia Corp | Electronic data transmission |
DE19961793C1 (en) | 1999-12-21 | 2001-01-04 | Siemens Ag | Method of selling goods in automatic vending machine using mobile terminal |
-
2001
- 2001-07-05 EP EP01610071A patent/EP1246145A3/en not_active Withdrawn
- 2001-07-05 EP EP01610070A patent/EP1246144A3/en not_active Ceased
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5804807A (en) * | 1996-09-12 | 1998-09-08 | Symbol Technologies, Inc. | Scan-ahead system for processing merchandise at a checkout register |
US5978772A (en) * | 1996-10-11 | 1999-11-02 | Mold; Jeffrey W. | Merchandise checkout system |
US6175922B1 (en) | 1996-12-04 | 2001-01-16 | Esign, Inc. | Electronic transaction systems and methods therefor |
JP2000004299A (en) * | 1998-06-17 | 2000-01-07 | Nec Corp | Turn wait calling device |
US6449357B1 (en) * | 1998-06-17 | 2002-09-10 | Nec Corporation | Queuing status reporting apparatus |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10337081A1 (en) * | 2003-08-12 | 2005-03-17 | Deutsche Postbank Ag | Credit note handling device e.g. for credit transfer via mobile phone server network, includes credit note computer for handling credit note at/for credit account |
DE10337081B4 (en) * | 2003-08-12 | 2006-04-27 | Deutsche Postbank Ag | Credit management apparatus |
WO2005073934A1 (en) * | 2004-01-28 | 2005-08-11 | Aron Matalon | Method and system for authenticating credit transactions |
EP3167416A1 (en) * | 2014-07-11 | 2017-05-17 | Google, Inc. | Hands-free transactions with a challenge request |
EP3167417A1 (en) * | 2014-07-11 | 2017-05-17 | Google, Inc. | Hands-free offline communications |
US10460317B2 (en) | 2014-07-11 | 2019-10-29 | Google Llc | Hands-free transaction tokens via payment processor |
US11574301B2 (en) | 2014-07-11 | 2023-02-07 | Google Llc | Hands-free transactions with voice recognition |
US10482463B2 (en) | 2016-03-01 | 2019-11-19 | Google Llc | Facial profile modification for hands free transactions |
US10839393B2 (en) | 2016-03-01 | 2020-11-17 | Google Llc | Facial profile modification for hands free transactions |
US10474879B2 (en) | 2016-07-31 | 2019-11-12 | Google Llc | Automatic hands free service requests |
US11495051B2 (en) | 2016-07-31 | 2022-11-08 | Google Llc | Automatic hands free service requests |
Also Published As
Publication number | Publication date |
---|---|
EP1246144A3 (en) | 2003-11-12 |
EP1246145A2 (en) | 2002-10-02 |
EP1246145A3 (en) | 2003-11-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7587196B2 (en) | Wireless point of sale transaction | |
US10990977B2 (en) | System communications with non-sensitive identifiers | |
JP4525556B2 (en) | Settlement system, transaction management server, settlement method used for them, and program thereof | |
CN109328445B (en) | Unique token authentication verification value | |
EP3841498B1 (en) | Method and system for token provisioning and processing | |
US7708194B2 (en) | Virtual wallet | |
US20190066089A1 (en) | Secure transactions using digital barcodes | |
US20080052091A1 (en) | Secure near field transaction | |
US20120203644A1 (en) | Apparatus, system and method for providing electronic receipts | |
US20210319450A1 (en) | Authenticating transactions using risk scores derived from detailed device information | |
KR20110094176A (en) | The electronic payment application system and payment authorization method | |
CN108886522B (en) | System and method for associating diverse location data for data security | |
RU2263347C2 (en) | Method for performing transactions of users of mobile communication devices and computerized cashless transaction system for realization of said method | |
WO2013181737A1 (en) | Systems and methods for secure remote payments | |
EP1246144A2 (en) | Wireless point of sale transaction | |
EP2316101A1 (en) | Method and system for managing financial transactions | |
CN116711267A (en) | Mobile user authentication system and method | |
WO2002080120A2 (en) | Wireless point of sale transaction | |
CN113518990A (en) | Virtual access credential interaction system and method | |
US20220343314A1 (en) | Processing using machine readable codes and secure remote interactions | |
CN116471017A (en) | Domain verification using verification values | |
CN117501268A (en) | Method and system for processing motion data | |
WO2023224735A1 (en) | Efficient and secure token provisioning | |
CN115280721A (en) | Token-to-token provisioning | |
WO2002025865A1 (en) | Verification protocol for a point of sale merchandising system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Free format text: AL;LT;LV;MK;RO;SI |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK RO SI |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL) |
|
17P | Request for examination filed |
Effective date: 20040428 |
|
AKX | Designation fees paid |
Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
17Q | First examination report despatched |
Effective date: 20101115 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20160509 |