EP2724303B1 - Système et procédés de traitement de transaction distribuée - Google Patents

Système et procédés de traitement de transaction distribuée Download PDF

Info

Publication number
EP2724303B1
EP2724303B1 EP12737228.2A EP12737228A EP2724303B1 EP 2724303 B1 EP2724303 B1 EP 2724303B1 EP 12737228 A EP12737228 A EP 12737228A EP 2724303 B1 EP2724303 B1 EP 2724303B1
Authority
EP
European Patent Office
Prior art keywords
terminal
mobile terminal
transaction
customer mobile
request message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP12737228.2A
Other languages
German (de)
English (en)
Other versions
EP2724303A1 (fr
Inventor
Rory MEEHAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PLANET PAYMENT SOLUTIONS Ltd
Original Assignee
PLANET PAYMENT SOLUTIONS Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by PLANET PAYMENT SOLUTIONS Ltd filed Critical PLANET PAYMENT SOLUTIONS Ltd
Priority to EP12737228.2A priority Critical patent/EP2724303B1/fr
Publication of EP2724303A1 publication Critical patent/EP2724303A1/fr
Application granted granted Critical
Publication of EP2724303B1 publication Critical patent/EP2724303B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • 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
    • G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • 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]
    • G06Q20/3229—Use of the SIM of a M-device as secure element
    • 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
    • G06Q20/3278—RFID or NFC payments by means of M-devices

Definitions

  • the present invention relates to electronic transaction processing systems at point of sales. More particularly, the present invention relates to distributed electronic transaction processing systems having network - connected point of sales and mobile customer terminals.
  • a card payment terminal typically reads the encoded data from the card memory means and connects to a plurality of remote terminals over a network, for purposes of card authentication, checking funds availability, personal identification number verification, transaction authorising and processing, all being implemented as local and/or remote data communication messages.
  • Recent systems developed for this purpose typically interface a customer's mobile terminal with a proximate point of sale terminal, by means of either reconfiguring the point of sale terminal with an additional, wireless local networking device or apparatus, or simply changing the point of sale terminal altogether for a newer model having such wireless local networking functionality built-in.
  • DE102007005427 discloses such a system, wherein a point of sale terminal (POS) is reconfigured or otherwise interfaced with an RFID device, and wherein each electronic transaction is processed through a combination of local data communications between a customer's mobile communication terminal and the RFID device and remote data communications between the POS and a remote trust centre system.
  • POS point of sale terminal
  • a method of processing a transaction in a distributed electronic payment system comprising at least one point of sale terminal and at least one customer mobile terminal, each being respectively configured to communicate with at least one host terminal over a network, the method comprising the steps of associating the at least one point of sale terminal with a machine- readable unique identifier at the least one host terminal, reading the machine-readable unique identifier associated with the at least one point of sale terminal with the at least one customer mobile terminal; at each of the at least one point of sale terminal and the at least one customer mobile terminal, encoding and communicating a respective transaction request message to the at least one host terminal, wherein the encoded transaction request message of the at least one customer mobile terminal includes the unique identifier read; and at the least one host terminal, matching the respective transaction request messages with the unique identifier and encoding and communicating a payment request message to the at least one customer mobile terminal.
  • _an inexpensive machine - readable terminal identifier is affixed to any existing point of sale terminal, and existing customer mobile terminals and point of sale terminals are configured with respective, unobtrusive sets of data processing instructions which repurpose their hardware features, pursuant to which users of suitably configured customer mobile terminals can actively control the electronic transaction process at the point of sale, without requiring the addition of new point of sale data processing hardware or the replacement of terminals.
  • the transaction request sent to the at least one customer mobile terminal includes, in its simplest embodiment, a request for payment with an amount.
  • a request for payment with an amount includes, in its simplest embodiment, a request for payment with an amount.
  • further embodiments contemplate the inclusion of store-specific and/or location data, for instance store name, address and optionally corporate trade mark or logo; payable amount in store currency; items concerned by the transaction and still more information pertaining to facilitate the mobile terminal user's decision to accept or reject the transaction request.
  • the data included in the transaction request sent to the at least one customer mobile terminal contains all the data present on a conventional point of sale receipt, whereby the transaction request effectively embodies an electronic receipt permitting a fully-paperless transaction, which is environmentally convenient and saves further transaction time.
  • This embodiment also usefully allows the mobile terminal user to receive and review a transaction receipt before authorizing a payment.
  • the method comprises the further step of inputting a personal identification number at the at least one customer mobile terminal, in response to the transaction request message.
  • Users of customer mobile terminals thus remain at liberty to cancel the electronic transaction prior to inputting the PIN and, advantageously and securely, input the PIN on their personal customer mobile terminal rather than on a third party's terminal.
  • the method comprises the further steps of encoding and communicating the personal identification number to at the at least one host terminal.
  • the at least one host terminal may then process the electronic transaction with known back-end electronic transaction processing systems to which it is also connected, for instance card payment remote hosts.
  • the method preferably comprises the further step of communicating a message indicative of transaction completion to the at least one point of sale terminal with the at least one host terminal.
  • the merchant user of the at least one point of sale terminal is thus informed that a payment operation has been completed, and that the customer user of the customer mobile terminal now has ownership of the goods sold.
  • the method preferably comprises the further step of communicating a message indicative of transaction completion to the at least one customer mobile terminal with the at least one host terminal.
  • the customer user of the customer mobile terminal is thus informed that he or she now has ownership of the goods sold.
  • the method preferably comprises the further step of storing image data representative of the user of the at least one customer mobile terminal at the at least one host terminal.
  • Operators of the at least one host terminal thus benefit from a form of positive identification of each user of a customer mobile terminal configured for use with the host terminal.
  • This method may advantageously comprise the further step of including the image data representative of the user in the message indicative of transaction completion sent to the at least one point of sale terminal.
  • the merchant user of the at least one point of sale terminal thus also benefits from a positive identification of the user of the customer mobile terminal substantially at the time of transaction, for mitigating the fraudulent use of misappropriated customer mobile terminals.
  • the machine - readable terminal identifier is preferably a near field communication (NFC) tag selected from the group comprising an optical machine - readable tag such as a one-dimensional barcode or a two-dimensional barcode, a radio-frequency identifier (RFID) tag and a wireless network terminal identifier.
  • NFC near field communication
  • a distributed electronic transaction system comprising a plurality of terminals connected to a network, the said terminals including at least one host terminal, at least one point of sale terminal configured with a machine-readable unique identifier, and at least one customer mobile terminal having means to read the machine-readable unique identifier.
  • Each of the at least one point of sale terminal and at least one customer mobile terminal comprises means for encoding a transaction request message including the unique identifier, and means for communicating encoded transaction request messages to the at least one host terminal over the network.
  • the at least one host terminal comprises means for associating the at least one point of sale terminal with the machine-readable unique identifier; means for matching transaction request messages, means for encoding a payment request message, and means for communicating the encoded payment request message to the at least one customer mobile terminal over the network.
  • the identifier is preferably a near field communication (NFC) tag.
  • NFC near field communication
  • the tag is a one-dimensional barcode or a two-dimensional barcode, and the means to read the identifier comprises optical capturing means.
  • the tag may be a radio-frequency identifier (RFID) tag, and the means to read the identifier comprises radio-frequency receiving means.
  • the tag may be a wireless network terminal identifier, for instance a Bluetooth or WLAN ('Wi-Fi') terminal name, and the means to read the identifier comprises wireless local networking means.
  • the tag is a label with a pre-printed, machine-readable pictogram encoding a numerical or alphanumerical expression, which usefully implements proximity electronic payment at point of sales equipped with legacy electronic transaction processing hardware, without the need for any local hardware or software specifically bridging the tag with that legacy hardware and, accordingly, with no additional power requirement. Rather, the customer terminal and the at least one remote host bear the corresponding data processing overhead.
  • the legacy electronic transaction processing hardware requires a minimal set of instructions for implementing additional communications with the at least one host terminal, wherein such communications use known formats and protocols and, at the time of processing an electronic transaction according to the invention, effectively replace equivalent communications with conventional remote hosts for purposes of card transaction authorising, acquiring and the like. Accordingly, in addition to the above benefits, the tag further implements proximity electronic payment without increasing the bandwidth requirements of the legacy electronic transaction processing hardware.
  • the means for encoding a transaction request message including the unique identifier preferably comprises a terminal central processing unit configured by a set of data processing instructions.
  • the means for matching transaction request messages and the means for encoding a payment request message preferably comprises a host terminal central processing unit configured by a set of data processing instructions.
  • the host terminal encoding means is preferably further adapted to encode a transaction completion message.
  • the at least one host terminal preferably further comprises means for storing image data representative of the user of the at least one customer mobile terminal.
  • the host terminal encoding means is preferably further adapted to include image data representative of the user in the message indicative of transaction completion.
  • FIG. 1 shows a networked environment in which an embodiment of the invention is implemented, including a plurality of terminals.
  • the electronic transaction processing system comprises at least one customer mobile terminal 101A, at least one point of sale terminal 102 and at least one host terminal 103, each terminal being connected to a communication network 104.
  • the merchant using the at least one point of sale terminal 102 may have the use of a merchant mobile terminal 101B.
  • the mobile terminals 101A, 101B are a mobile telephone handsets having wireless telecommunication emitting and receiving functionality over a cellular telephone network configured according to the Global System for Mobile Communication ('GSM'), General Packet Radio Service ('GPRS'), International Mobile Telecommunications-2000 (IMT - 2000, '3G') network industry standards, and wherein telecommunication is performed as voice, alphanumeric or audio-video data using the Short Message Service ('SMS') protocol, the Wireless Application protocol ('WAP') the Hypertext Transfer Protocol ('HTTP') or the Secure Hypertext Transfer Protocol ('HTTPS').
  • 'GSM' Global System for Mobile Communication
  • 'GPRS' General Packet Radio Service
  • IMT - 2000, '3G' International Mobile Telecommunications-2000
  • '3G' Global System for Mobile Communication
  • telecommunication is performed as voice, alphanumeric or audio-video data using the Short Message Service ('SMS') protocol, the Wireless Application protocol ('WAP') the
  • the mobile telephone handset 101A, 101B receives or emits voice, text, audio and/or image data encoded as a digital signal over a wireless data transmission 105, wherein the signal is relayed respectively to or from the device by the geographically-closest communication link relay 106 of a plurality thereof.
  • the plurality of communication link relays 106 allows digital signals to be routed between the mobile handset 101A and their destination by means of a remote gateway 107.
  • Gateway 107 is for instance a communication network switch, which couples digital signal traffic between wireless telecommunication networks, such as the network within which wireless data transmissions 107 take place, and the communication network 101A, which is a Wide Area Network ('WAN') 104, an example of which being the Internet.
  • the gateway 107 further provides protocol conversion if required, for instance whether the mobile handset 101A uses the WAP or HTTPS protocol to communicate data.
  • the customer mobile terminal 101A, 101B may have wireless telecommunication emitting and receiving functionality over a wireless local area network ('WLAN') conforming to the 802.11 standard ('Wi-Fi') and wherein telecommunication is likewise performed as voice, alphanumeric or audio-video data using the voice data over IP ('VoIP') protocol, the Hypertext Transfer Protocol ('HTTP') or the Secure Hypertext Transfer Protocol ('HTTPS'), the signal being relayed respectively to or from the customer mobile terminal 101A by a wireless router 109 interfacing the mobile telephone handset 101A, 101B to the WAN communication network 104.
  • 'WLAN' wireless local area network
  • 'Wi-Fi' 802.11 standard
  • telecommunication is likewise performed as voice, alphanumeric or audio-video data using the voice data over IP ('VoIP') protocol, the Hypertext Transfer Protocol ('HTTP') or the Secure Hypertext Transfer Protocol ('HTTPS')
  • the customer mobile terminal 101A, 101B may for instance be an iPhoneTM handset manufactured by the Apple Corporation or a Nexus OneTM handset manufactured for Google, Inc. by the HTC Corporation.
  • the customer mobile terminal 101A, 101B may be any portable computing device having at least means to read a point of sale terminal identifier as will be described hereafter, and networking means apt to establish a bilateral data communication with to the host terminal 104.
  • the point of sale terminal 102 is a computing device which emits and receives data encoded as a digital signal over a wireless data transmission 108 conforming to the IEEE 802.11 ('Wi-Fi') standard, wherein the signal is relayed respectively to or from the computing device by the wireless router 109 interfacing the computing device 102 to the WAN communication network 104
  • 'Wi-Fi' IEEE 802.11
  • the computing device may alternatively emit and receive data encoded as a digital signal over a wired data transmission conforming to the IEEE 802.3 ('Gigabit Ethernet') standard, wherein the signal is relayed respectively to or from the computing device by a wired router interfacing the computing device to the WAN 101A.
  • IEEE 802.3 'Gigabit Ethernet'
  • the point of sale terminal 102 may for instance be a EFT series terminal manufactured by Ingenico, an Optimum T series terminal manufactured by Hypercom, or an MX 800 series terminal manufactured by VeriFone.
  • the point of sale terminal 102 may be any computing device having at least networking means apt to establish a bilateral data communication with to the host terminal 104, noting that a built-in capacity to read memory means of payment cards is not material to the present invention.
  • the mobile handset 101A, 101B firstly includes a data processing unit 201, for instance a general-purpose microprocessor ('CPU'), acting as the main controller of mobile handset 101A, 101B and which is coupled with memory means 202, comprising non-volatile random-access memory ('NVRAM').
  • a data processing unit 201 for instance a general-purpose microprocessor ('CPU'), acting as the main controller of mobile handset 101A, 101B and which is coupled with memory means 202, comprising non-volatile random-access memory ('NVRAM').
  • 'NVRAM' non-volatile random-access memory
  • the mobile communication device 101A, 101B further includes a modem 203 to implement the wireless communication functionality, as the modem provides the hardware interface to external communication systems, such as the GSM or GPRS cellular telephone network 106, 107, shown in Figure 1 .
  • An aerial 204 coupled with the modem 203 facilitates the reception of wireless signals from nearby communication link relays 106.
  • the modem 203 includes an analogue-to-digital converter 205 ('ADC') for demodulating wavelength wireless signals received via the antenna 204 into digital data, and reciprocally for outgoing data.
  • the mobile handset 101A, 101B further includes imaging means 206 in the form of an electronic image sensor, for capturing image data which the data processing unit 201 or a dedicated data processing unit processes into digital image data.
  • the mobile handset 101A, 101B may optionally further include self-locating means in the form of a GPS receiver 207, wherein the ADC 205 receives analogue positional and time data from an orbiting satellite (not shown), which the data processing unit 201 or a dedicated data processing unit processes into digital data.
  • self-locating means in the form of a GPS receiver 207, wherein the ADC 205 receives analogue positional and time data from an orbiting satellite (not shown), which the data processing unit 201 or a dedicated data processing unit processes into digital data.
  • the CPU 201, NVRAM 202, modem 203, digital camera 206 and optional GPS receiver 207 are connected by a data input/output bus 208, over which they communicate and to which further components of the mobile handset 101A, 101B are similarly connected, in order to provide wireless communication functionality and receive user interrupts, inputs and configuration data.
  • Alphanumerical and/or image data processed by CPU 201 is output to a video display unit 209 ('VDU'), from which user interrupts may also be received if it is a touch screen display. Further user interrupts may also be received from a keypad 210 of the handset, or from an external human interface device ('HiD') connected to the handset via a Universal Serial Bus ('USB') interface 211.
  • the USB interface advantageously also allows the CPU 201 to read data from and/or write data to an external storage device.
  • Power is provided to the handset 101A, 101B by an internal module battery 212, which an electrical converter 213 charges from a mains power supply as and when required.
  • FIG. 3 A typical hardware architecture of either the point of sale terminal 102 or the host terminal 103 or both is shown in Figure 3 in further detail, by way of non-limitative example.
  • the data processing device 102 is a computer configured with a data processing unit 301, data outputting means such as video display unit (VDU) 302, data inputting means such as HiD devices, commonly a keyboard 303 and a pointing device (mouse) 304, as well as the VDU 202 itself if it is a touch screen display, and data inputting/outputting means such as the wireless network connection 108 to the router 109, a magnetic data-carrying medium reader/writer 306 and an optical data-carrying medium reader/writer 307.
  • VDU video display unit
  • HiD devices commonly a keyboard 303 and a pointing device (mouse) 304
  • HiD devices commonly a keyboard 303 and a pointing device (mouse) 304
  • a central processing unit (CPU) 308 provides task coordination and data processing functionality. Instructions and data for the CPU 308 are stored in memory means 309 and a hard disk storage unit 310 facilitates non-volatile storage of the instructions and the data.
  • a wireless network interface card (NIC) 311 provides the interface to the network connection 108.
  • a universal serial bus (USB) input/output interface 312 facilitates connection to the keyboard and pointing devices 303, 304.
  • All of the above devices are connected to a data input/output bus 313, to which the magnetic data-carrying medium reader/writer 306 and optical data-carrying medium reader/writer 307 are also connected.
  • a video adapter 314 receives CPU instructions over the bus 313 for outputting processed data to VDU 302. All the components of data processing unit 301 are powered by a power supply unit 315, which receives electrical power from a local mains power source and transforms same according to component ratings and requirements.
  • the hardware architecture of the host terminal 103 is substantially similar to that of the point of sale terminal 102 shown in Figure 3 , as skilled persons will readily understand.
  • the present invention introduces an inexpensive machine - readable terminal identifier 110, which is affixed to the point of sale terminal 102 by its user at the time of registering the point of sale terminal 102 with the system at the host terminal 104, as will be described hereafter.
  • the machine - readable terminal identifier 110 embodies the unique physical identity of the terminal 102 in the system only. For each customer mobile terminal 101A conducting a transaction at that point of sale terminal 102, and for each distinct transaction conducted by a same customer mobile terminal 101A at that point of sale terminal 102, the machine - readable terminal identifier 110 is used as a common linking variable. associated with each unique transaction instance between a customer mobile terminal 101A with the point of sale terminal 102 across the network, without there being any requirement to configure either terminal 101A, 102 with additional acceptance or compliance hardware.
  • the machine - readable terminal identifier 110 is thus apt to retrofit legacy point of sale terminals 102, possibly even deemed otherwise obsolete, with a proximity or 'Near Field' communication capability, by simply affixing a self-adhesive pre-printed label 401 or 402 to the terminal 102 in its simplest embodiment.
  • Example embodiments of machine - readable terminal identifiers 110 are shown in Figure 4 as optical machine - readable data constructs, conventionally referred to as barcodes.
  • Machine - readable terminal identifiers 110 suitable for use with the system of the present invention include linear or 'one - dimensional' barcodes 401, which represent data by varying the widths and spacings of a plurality of parallel lines. Such barcodes are known as Universal Product Codes or European Article Numbers.
  • Machine - readable terminal identifiers 110 suitable for use with the system of the present invention may also include geometric pattern or 'two - dimensional' barcodes 402 which uses elementary dots or lines arranged into symmetric or asymmetric geometrical shapes.
  • Such barcodes are known as matrix codes, known examples of which include Aztec Code, Datamatrix, QR Code, ShotCode, SmartCode, MaxiCode and EZCode.
  • the machine - readable terminal identifier 110 is a QR Code conforming to the ISO/IEC 18004 standard, which the imaging means 206 of the customer mobile terminal 101A is apt to read and which instructions in the memory means 202 of the customer mobile terminal 101A processed by the CPU 201 are apt to decode into alphanumerical data, typically a Uniform Resource Locator embodying an host address on the network 104, according to known techniques.
  • a radio-frequency identifier (RFID) tag may be affixed to the point of sale terminal 102 rather than a barcode label.
  • RFID radio-frequency identifier
  • This embodiment of a machine - readable terminal identifier 110 is more costly than a barcode label 401, 402 and obviates the power advantage of the label embodiments described above, albeit marginally so since this embodiment still has no requirement for any bridging hardware interface between the legacy PoS terminal 102 and the RFID 110, nor for any bridging software for communicating data between the legacy PoS terminal 102 and the RFID 110 one way or the other.
  • a machine - readable RFID identifier 110 advantageously increases the operational distance between a customer mobile terminal 101A and a point of sale terminal 102 for processing an electronic transaction as described herein, to the extent that the user of a customer mobile terminal 101A may not even need to be proximate any point of sale in the retail location when processing the electronic transaction as described herein. This allows a retail location to process more transactions in any given time period, and saves time for the mobile terminal user who may simply select products from a retail shelf and pay for them substantially at the same time over the air.
  • a unique terminal identifier of the point of sale terminal 102 on the wireless local area network 108, 109 may be used rather than or in addition to a barcode label, providing substantially the same advantages as an RFID tag. This is particularly advantageous when the hardware configuration of the point of sale terminal 102 includes a WLAN NIC 311 as described in relation to Figure 3 , since implementing the unique terminal identifier of the point of sale terminal 102 with this terminal configuration requires no additional hardware whatsoever.
  • the processing steps according to which the customer mobile terminal 101A is configured for communicating data with the host terminal 103 over the network 101A begins with the customer mobile terminal 101A obtaining the network address of the host terminal 103.
  • the imaging means 206 of the customer mobile terminal 101A reads the QR Code 110 affixed to the point of sale terminal 102 at the retail location, or affixed, printed or otherwise displayed on another support. Instructions of the customer mobile terminal 101A decode the unique identifier 110 into a unique a sequence of alphanumerical characters, a portion of which embodies a Uniform Resource Locator of the host terminal on the network 104 according to known techniques, whereby the customer mobile terminal 101A sends a request to the host terminal 103 across the network 104 at step 502 by means of this decoded address.
  • the host terminal 103 determines that the customer mobile terminal 101A is unknown to it and a registration procedure must first be followed, whereby the user of the customer mobile terminal 101A is queried at step 503, as to whether to register. If the user declines, then the host terminal 104 concludes the data communication at step 504 and the user of the customer mobile terminal 101A may conduct a conventional transaction at the point of sale terminal 102, electronic or otherwise.
  • the customer mobile terminal 101A sends at least one parameter representative of the user, in the example an electronic mail address, to the host terminal 103.
  • the host terminal 103 sends a message to the communicated electronic mail address across the network 104, wherein the message comprises a verification token, for instance a Uniform Resource Locator embodying the host address on the network 104 and a unique identifier for the registration session.
  • the customer mobile terminal 101A verifies the electronic mail address by accessing the host terminal 103 with the Uniform Resource Locator and unique identifier for the registration session.
  • the customer mobile terminal 101A may communicate further parameters representative of the user, for instance a photograph of the user, a name of the user, residence data of the user.
  • the customer mobile terminal 101A communicates financial data of the user, for instance a payment card number, an online payment system user identifier, a financial institution account number or the like.
  • All of the data communicated by the customer mobile terminal 101A to the host terminal 103 over the network 104 at steps 505, 508 and 509 is stored by the host terminal 103 in a relevant data structure, for instance a database, and uniquely associated with a unique host terminal access token, for instance a user password.
  • the customer mobile terminal 101A requests and obtains a set of data processing instructions from the host terminal 103 over the network 104 which, when processed, configure the customer mobile terminal 101A for processing distributed electronic transactions with point of sale terminals 102 via the host terminal 103 and configure the display 209 of the customer mobile terminal 101A with a corresponding user interface.
  • the set of data processing instructions configures the customer mobile terminal 101A to establish a secure connection with the host terminal 103 at step 511, by communication a request for an authentication token, in the example a session key, the request comprising the stored electronic mail address of step 505 and the password.
  • the host terminal 103 authenticates the request by comparing the communicated electronic mail address and password with the database contents and returns a valid session key to the customer mobile terminal 101A at step 512.
  • the session key is communicated with each subsequent network message sent at step 513 by the customer mobile terminal 101A, for maintaining a verification that payment authorisation messages are broadcast by an authorized terminal 101A.
  • Figure 7 shows the contents of memory means 202 of the customer mobile terminal 101A at runtime, after the processing steps of Figures 5 and 6 .
  • An operating system is shown at 701 which, if the customer mobile terminal 101A is a mobile telephone handset, may be iOS4TM distributed by Apple Corporation or AndroidTM distributed by Goole, Inc.
  • a subset 702 of the operating system 701 corresponds to instructions for processing the input from the electronic image sensor 206 into digital image data.
  • Another subset 703 of the operating system 701 corresponds to instructions for processing tactile interrupts on the display 209 into digital input data 704.
  • the application downloaded and installed at step 511 is shown at 705, which is interfaced with the OS 701, and the imaging and input translating subsets 702, 703 thereof via one or more suitable application programmer interfaces.
  • a user interface of the application 705 is shown at 706, with which the user of the customer mobile terminal 101A interacts by providing tactile interrupts on the display 209.
  • User of customer mobile terminals 101A authorize electronic transactions by inputting their personal identification number in the user interface 706, and the application 705 creates a mathematical version of the PIN, known as a PIN hash, by processing the alphanumerical sequence of the PIBN with an algorithm using seed data.
  • the application 705 subsequently communicates the PIN Hash to the host terminal 103.
  • Application data comprises local data 707 such as the session key of step 512, the user PIN or a PIN hash processed from same, and network data 708 being sent to, or received from, the host terminal 103.
  • Application data received from the host terminal 103 includes the session key at step 512, and thereafter may include, non - exhaustively, data representative of the particulars of a transaction, data representative of a payment request message and data representative of a message indicating completion of a transaction.
  • Application data sent to the host terminal 103 includes the electronic mail address and password of step 511 before the session key is received at step 512, and thereafter may include, non - exhaustively, decoded data representative of the unique machine - readable terminal identifier 110 of a point of sale terminal 102 configured for communicating data with the host terminal 103 over the network 104 and the PIN hash for confirming that the electronic transaction should be settled.
  • the processing steps according to which the point of sale terminal 102 is configured for communicating data with the host terminal 103 over the network 104 begins with the user of the point of sale terminal 102, a merchant, receiving a unique machine - readable terminal identifier 110, 402 and affixing it to the terminal at step 801.
  • the user of the point of sale terminal 102 next requires the use of a merchant mobile terminal 101B substantially as described hereinbefore with reference to Figures 1 and 2 .
  • the host terminal 103 initiates a registration procedure with the merchant mobile terminal 101B at step 802.
  • the merchant mobile terminal 101B sends at least one parameter representative of the store at which one or more point of sale terminals 102 are located, in the example an electronic mail address, to the host terminal 103.
  • the host terminal 103 sends a message to the communicated electronic mail address across the network 104, wherein the message comprises a verification token, for instance a Uniform Resource Locator embodying the host address on the network 104 and a unique identifier for the registration session.
  • the merchant mobile terminal 101B verifies the electronic mail address by accessing the host terminal 103 with the Uniform Resource Locator and unique identifier for the registration session.
  • the merchant mobile terminal 101B may communicate further parameters representative of the store, for instance a name and address of the store.
  • the merchant mobile terminal 101B communicates financial data of the store, for instance a payment card number, an online payment system user identifier, a financial institution account number or the like. All of the data communicated by the merchant mobile terminal 101B to the host terminal 103 over the network 104 at steps 803, 806 and 807 is stored by the host terminal 103 in a relevant data structure, for instance a database, and uniquely associated with a unique host terminal access token, for instance a merchant password.
  • the merchant mobile terminal 101B requests and obtains a set of data processing instructions, e.g. a merchant application, from the host terminal 103 over the network 104 which, when processed, configures the merchant mobile terminal 101B to access and conduct a variety of operations with the financial data stored in the database.
  • the database and the set of data processing instructions of step 808 are required to settle financial transactions between the host terminal 103 and the store's financial services provider, details of which were input at step 807. As distributed electronic payment transactions are processed throughout the day with consumer mobile terminals 101A, the store account balance increases in the database.
  • the user of the merchant mobile terminal 101B may select to transfer any portion of their store balance to their registered financial account or to another account maintained in the database with the merchant application of step 808, which preferably configures the display 209 of the merchant mobile terminal 101B with a corresponding user interface.
  • the imaging means 206 of the merchant mobile terminal 101A reads the QR Code 110 newly - affixed to the point of sale terminal 102. Instructions of the merchant mobile terminal 101B decode the QR Code 110 into unique a sequence of alphanumerical characters, a portion of which embodies the Uniform Resource Locator of the host terminal on the network 104 according to known techniques.
  • the merchant inputs the electronic mail address and merchant password associated with the merchant mobile terminal 101B at step 810, and inputs a unique sequence of alphanumerical characters of their choice as the respective name of the point of sale terminal 102 to which the QR Code 110 has been newly - affixed at step 811.
  • the merchant mobile terminal 101B logs in at the host terminal 103 across the network 104 and communicates this input.
  • the host terminal authenticates the merchant mobile terminal 101B with the received electronic mail address and merchant password, and updates the store records stored in the database with the communicated input, which registers the point of sale terminal 102 at the host terminal 103.
  • the host terminal 103 next generates a unique point of sale terminal keyfile from at least the unique sequence of alphanumerical characters communicated as the respective name of the point of sale terminal 102.
  • the keyfile is a small set of data and instructions for configuring the point of sale terminal 102 to perform steps required to process a distributed electronic transaction when in use.
  • the merchant mobile terminal 101B requests and obtains the unique point of sale terminal keyfile from the host terminal 103 over the network 104 and transfers the keyfile to the memory means 309 of the point of sale terminal 102 according to known techniques at step 814, at which time the point of sale terminal 102 is fully configured for use with the host terminal 103.
  • Figure 10 shows the contents of memory means 309 of the point of sale terminal 102 at runtime, after the processing steps of Figures 7 and 8 .
  • An operating system is shown at 1001 which, if the point of sale terminal 102 is a desktop computer, may be Windows 7TM distributed by Microsoft Corporation.
  • a subset 1002 of the operating system 1001 corresponds to instructions for processing any of interrupts on the display 302, the keyboard 303 and the HiD devices 303, 304 into digital input data 1003.
  • a retail application is shown at 1004, which configures the point of sale terminal 102 to collate data representative of the particulars of a transaction, for instance by matching product barcodes scanned with an optical reader by the merchant with electronic inventory records comprising product details and product price data, and having a user interface 1005 which is displayed on VDU 302 via the video adapter 314.
  • the instruction set of the keyfile downloaded and installed at steps 813, 814 is shown at 1006, which is interfaced with the OS 1001, the input translating subset 1002 and the retail application 1004 via one or more suitable application programmer interfaces.
  • a user interface of the application 1006 is shown at 1007 which, in its simplest embodiment, may take the form of a user - selectable 'pay by mobile' button implemented within the user interface 1005 of the retail application 1004, wherein the user of the point of sale terminal 102 calls upon the functionality of the application 1006 by providing a tactile interrupt on the button 1007 displayed in the interface 1005 or selecting it with the mouse 304.
  • Application data is shown at 1008, which comprises local data 1009 such as the dataset of the keyfile of steps 813, 814 and transaction products, quantities and prices data, and network data 1010 being sent to, or received from, the host terminal 103.
  • Application data 1010 received from the host terminal 103 includes data representative of a message indicating completion of a transaction, optionally including image data representative of the user of a customer mobile terminal 101A with whom a transaction has been processed.
  • Application data 1010 sent to the host terminal 103 includes, non - exhaustively, data representative of the particulars of a transaction and data representative of the unique machine - readable terminal identifier 110 of the point of sale terminal 102.
  • the host terminal 103 processes data and communicates data with the customer mobile terminal 101A and the point of sale terminal 102 over the network 104 are detailed with reference to Figure 11 .
  • the host terminal 103 receives network data from a mobile terminal 101A, 101B or from a point of sale terminal 102.
  • a determination is made at step 1102, as to whether the network data has been sent by a registered customer mobile terminal 101A, a registered merchant mobile terminal 101B, a registered point of sale terminal 102 or an unregistered mobile terminal 101A, 101B
  • the host terminal performs a registration procedure at step 1103, respectively according to steps 505 to 510 if the network data has been sent by an unregistered customer mobile terminal 101A, or according to steps 802 to 808 if the network data has been sent by an unregistered merchant mobile terminal 101B.
  • the host terminal subsequently receives a data request for the user application 705 of step511, the merchant application of step 808 or for the keyfile 100 of step 813, which it then communicates to the requesting registered mobile terminal 101A, 101B at step 1105. Control subsequently returns to step 1101.
  • the host terminal authenticates access at step 1106 and communicates data with the terminal 101B, either for registering a point of sale terminal 102 to which a QR Code 110 has been newly - affixed according to steps 809 to 814 at step 1107, or for processing a variety of operations with the financial data stored in the database as described with reference to Figure 8 , for instance transferring portions of store balance to registered financial accounts, at step 1107. Control subsequently returns to step 1101.
  • the host terminal authenticates access or, depending on the processing stage of an ongoing distributed electronic transaction, maintains or renews access via, respectively, the session key 707 of the registered user mobile terminal 101A or the keyfile 1008 of the registered point of sale terminal 102.
  • the encoded network data is decoded and a determination is made as to whether the network data is an encoded transaction request message including a unique point of sale terminal identifier 110, a PIN Hash or a transaction cancellation interrupt sent by a registered user terminal 101A, or an encoded transaction request message sent by a registered point of sale terminal 102.
  • the host terminal 103 instantiates and stores a new transaction record in the database, which it associates with the point of sale terminal identifier 110 of the sending registered point of sale terminal 102 and which it populates with the transaction data, typically product data, product quantity data and price data.
  • the host terminal 103 may optionally associate further data with the transaction record, intended to further facilitate the decision by the user of the relevant registered user terminal 101A to accept or reject the transaction request.
  • Such further data may for instance include store-specific and/or location data, e.g. store name, address and optionally corporate trade mark or logo; payable amount in store currency; and items concerned by the transaction. Control subsequently returns to step 1101.
  • the host terminal 103 matches the transaction request of the user terminal 101A with a stored transaction request message of a point of sale terminal 102, using the point of sale terminal identifier 110 contained in the message sent by the registered user terminal 101A for identifying the corresponding stored transaction record.
  • the host terminal 103 encodes and communicates a payment request message to the customer mobile terminal 102, to which the customer mobile terminal 102 is expected to reply with the PIN hash or a transaction cancellation interrupt, as the case may be. Control subsequently returns to step 1101.
  • the seed data that is used to process the PIN into the PIN hash on the customer mobile terminal 101 is included in the communication and, at step 1113, the host terminal 103 performs the same processing of the PIN into a PIN hash and compares the result to the received PIN hash. If both PIN hashes match, then the host terminal 103 authorizes electronic payment for the stored transaction and, at step 1114, communicates a message indicative of transaction completion to the relevant point of sale terminal 102 associated with the transaction record, optionally including image data representative of the user of the customer mobile terminal 101 for purposes of final security verification. Control subsequently returns to step 1101. The host server 103 may optionally also communicate a message indicative of transaction completion to the customer mobile terminal 101. Control subsequently returns to step 1101.
  • step 1115 the host terminal 103 matches the cancellation interrupt with the corresponding stored transaction record and deletes the record from the database. Control subsequently returns to step 1101.
  • Figure 12 shows the contents of memory means 309 of the host terminal 103 in use, at runtime.
  • An operating system is shown at 1201 which, if the host terminal 103 is a desktop computer, may be Windows 7TM distributed by Microsoft Corporation.
  • a payment settlement application is shown at 1202, which interfaces the host terminal 103 with conventional electronic payment systems, for instance card payment scheme networks including card payment authorisation hosts and card payment settlement hosts, online payment providers such as PaypalTM and more.
  • An application is shown at 1203, which configures the host terminal 103 to perform at least processing steps 1101 to 1115 as described hereinbefore, and which is interfaced with the OS 1201 and the payment settlement application 1202 via one or more suitable application programmer interfaces.
  • Application data is shown at 1204, which comprises local and network data.
  • Local data 1205 comprises the database 1206 of registered customer mobile terminals 101A, registered stores and registered point of sale terminals 102, wherein each registered customer mobile terminal 101A is uniquely identified therein by its respective unique combination of personal electronic mail address and password, as well as image data representative of its user where available, and each registered point of sale terminal 102 is uniquely identified therein by its respective unique machine - readable terminal identifier 110.
  • Local data further comprises session keys 707 and keyfiles 1008.
  • Network data 1207 comprises data received at the host terminal 103 respectively from customer mobile terminals 101A (1208) and point of sale terminals 102 (1209), and data sent by the host terminal 103 respectively to customer mobile terminals 101A (1210) and point of sale terminals 102 (1211).
  • Network data 1207 thus comprises data representative of the particulars of transactions, decoded data representative of unique machine - readable terminal identifiers 110, data representative of payment request messages, encoded personal identification numbers and data representative of messages indicating completion of transactions.
  • a consumer presents their basket of items to the merchant at the point of sale.
  • the merchant scans details of the items and their respective quantities into the point of sale terminal 102 and a transaction total amount is calculated, according to known techniques.
  • the details and quantity of each item in the basket and the transaction total amount are sent by the point of sale terminal 102 to the host terminal 103 in a payment authorization request at step 1301.
  • the consumer scans the tag 110 that is attached to the point of sale 102 with their customer mobile terminal 101A at step 1302.
  • the unique POS identifier data encoded in the tag 110 is sent from the customer mobile terminal 101A to the host terminal 103 at step 1303.
  • the host terminal 103 receives the respective messages from steps 1301 and 1303, and generates a payment authorization request message, which it sends to the customer mobile terminal 101A at step 1304.
  • the payment authorization request message includes the items and the total amount for the payment request
  • the application 705 on the customer mobile terminal 101A displays the payment request and prompts the consumer to input their PIN at step 1305, to be processed into a PIN hash.
  • the consumer may either reject the transaction or authorize it by inputting their PIN.
  • the customer mobile terminal 101A generates a PIN hash and a payment authorization message from the PIN input, sent to the host terminal 103 in response at step 1306.
  • the host terminal 103 stores a mathematical version of the consumer PIN and never the actual PIN or an encrypted version thereof. At step 1307, the host terminal 103 performs the same algorithmic operations as the customer mobile terminal 101A and compares the result to the PIN hash sent from the customer mobile terminal 101. The electronic payment is authorized if the comparison yields a match.
  • the host terminal 103 responds to the point of sale terminal 102 with a payment authorization response, which may also include a photograph of the consumer.
  • the point of sale terminal 102 receives the authorization response and displays the optional photograph to the merchant.
  • the merchant may use the photograph as a final authorization check.
  • all communications are encrypted using a Secure Socket Layer.
  • the two dimensional QR code 110 may be generated as an image file and stored by an online store server configured as a POS 102, to be communicated to every remote purchaser as part of an online checkout page.
  • Such remote users may thus avail of substantially the same payment method as described hereinabove with their respective mobile terminal 101A, by performing step 1302 on the display 302 of their personal computing device.
  • the QR code 110 can be dynamically created where the code can be auto-generated online using an algorithm, and then matched at the back end host. By generating the QR code in this way eliminates the risk of fraud.
  • a first example of an additional feature that may be implemented in the application 1203 is dynamic currency conversion, when the currency of the customer account registered pursuant to step 509 differs from the currency of the transaction request of step 1304.
  • the application 1203 may usefully perform currency conversion substantially in real-time between steps 1303 and 1304, so that the transaction request contains transaction amount data in both currencies and an exchange rate. This helps the user of the mobile terminal 101A better understand how much the goods considered for purchase are worth.
  • a second example of an additional feature that may be implemented in the application 1203 is dynamic rebating, when the store with the POS 102 concerned by a transaction request is providing point-in-time, frequency-based or spend-based incentives.
  • the application 1203 may usefully perform dynamic rebating substantially in real-time between steps 1303 and 1304 according to relevant data stored in the database 1206 against the POS 102 identifier and/or the mobile terminal identifier, so that the transaction request contains a transaction amount data reflecting the incentive. Again this helps the user of the mobile terminal 101A better understand how much the goods considered for purchase are worth.
  • Such user-input may include crediting a personal account maintained locally in database 1206 with funds from any or a combination of traditional bank accounts, online-only bank or deposit accounts, payment cards and the like. More simply, or additionally, such user-input may include viewing balance and/or transaction history. Usefully, such user-input may include the registration of new and/or additional terminals substantially according to steps 505 to 510, so that users may register a plurality of personal devices for e.g. different, respective fund sources, or different family members, and administer these with e.g. transaction limits in given periods.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Cash Registers Or Receiving Machines (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Claims (13)

  1. Procédé de traitement d'une transaction dans un système de paiement électronique distribué comprenant au moins un terminal de point de vente (102) et au moins un terminal de mobile client (101A, 101B), chacun étant respectivement configuré pour communiquer avec au moins un terminal hôte (103) sur un réseau, le procédé comprenant les étapes :
    de lecture d'un identifiant unique lisible par machine (110) de l'au moins un terminal de point de vente (102) avec l'au moins un terminal de mobile client (101A, 101B) ;
    au niveau de l'au moins un terminal de point de vente (102) et de l'au moins un terminal de mobile client (101A, 101B), d'encodage et de communication d'un message de demande de transaction (1301, 1303) respectif vers l'au moins un terminal hôte (103), dans lequel le message de demande de transaction encodé communiqué par l'au moins un terminal de point de vente (102) inclut des données de transaction et l'identifiant unique (110) et le message de demande de transaction encodé communiqué par l'au moins un terminal de mobile client (101A, 101B) inclut l'identifiant unique (110) ;
    au niveau de l'au moins un terminal hôte (103), d'identification du message de demande de transaction communiqué par l'au moins un terminal de point de vente (102), et d'instanciation et de stockage d'un enregistrement de transaction associé à l'identifiant unique (110) et peuplé des données de transaction incluses dans le message de demande de transaction de l'au moins un terminal de point de vente (102) ;
    au niveau de l'au moins un terminal hôte (103), d'identification du message de demande de transaction communiqué par l'au moins un terminal de mobile client (101A, 101B), et de mise en correspondance (1111) du message de demande de transaction de l'au moins un terminal de mobile client (101A, 101B) avec le message de demande de transaction stocké de l'au moins un terminal de point de vente (102) en utilisant l'identifiant unique (110) contenu dans le message de demande de transaction de l'au moins un terminal de mobile client (101A, 101B) afin d'identifier l'enregistrement de transaction stocké correspondant ; d'encodage et de communication d'un message de demande de paiement (1304) pour l'enregistrement de transaction vers l'au moins un terminal de mobile client (101A, 101B) ; de saisie d'un numéro d'identification personnel au niveau de l'au moins un terminal de mobile client (101A, 101B) en réponse au message de demande de paiement ;
    de génération par l'au moins un terminal de mobile client (101A, 101B) d'un hachage du numéro d'identification personnel saisi et de communication (1306) du hachage généré du numéro d'identification personnel vers l'au moins un terminal hôte (103) ;
    de comparaison par l'au moins un terminal hôte (103) du hachage du numéro d'identification personnel reçu à partir du terminal de mobile client (101A, 101B) avec un hachage du numéro d'identification personnel généré par le terminal hôte (103) ; et
    d'autorisation d'un paiement électronique pour la transaction stockée si le hachage du numéro d'identification personnel reçu à partir du terminal de mobile client (101A, 101B) correspond au hachage du numéro d'identification personnel généré par le terminal hôte (103).
  2. Procédé selon la revendication 1, comprenant l'étape supplémentaire de communication d'un message (1308) indiquant la fin d'une transaction à l'au moins un terminal de point de vente (102) avec l'au moins un terminal hôte (103).
  3. Procédé selon la revendication 1 ou 2, comprenant l'étape supplémentaire de communication d'un message (1309) indiquant la fin d'une transaction à l'au moins un terminal de mobile client (101A, 101B) avec l'au moins un terminal hôte (103).
  4. Procédé selon l'une quelconque des revendications 1 à 3, comprenant l'étape supplémentaire (508) de stockage de données d'image (1010) représentatives de l'utilisateur de l'au moins un terminal de mobile client (101A, 101B) au niveau de l'au moins un terminal hôte (103).
  5. Procédé selon la revendication 4, lorsque dépendante de la revendication 2, comprenant l'étape supplémentaire d'inclusion de données d'image (1010) représentatives de l'utilisateur dans le message indiquant la fin d'une transaction (1308).
  6. Procédé selon l'une quelconque des revendications 1 à 5, dans lequel l'identifiant (110) est sélectionné parmi le groupe comprenant une étiquette de communication en champ proche (NFC), une étiquette lisible par machine optique telle d'un code-barres unidimensionnel (401) ou un code-barres bidimensionnel (402), une étiquette d'identifiant radiofréquence (RFID) et un identifiant de terminal de réseau sans fil.
  7. Système de transaction électronique distribuée comprenant une pluralité de terminaux (101A, 101B, 102, 103) connectée à un réseau, lesdits terminaux incluant
    au moins un terminal hôte (103),
    au moins un terminal de point de vente (102) configuré avec un identifiant unique lisible par machine (110), et
    au moins un terminal de mobile client (101A, 101B) présentant des moyens de lecture de l'identifiant unique lisible par machine (110),
    dans lequel l'au moins un terminal de point de vente (102) comprend
    des moyens d'encodage d'un message de demande de transaction incluant l'identifiant unique (110) et des données de transaction, et
    des moyens de communication du message de demande de transaction encodé vers l'au moins un terminal hôte (103) sur le réseau,
    et dans lequel l'au moins un terminal de mobile client (101A, 101B) comprend des moyens d'encodage d'un message de demande de transaction incluant l'identifiant unique (110) et des moyens de communication du message de demande de transaction encodé vers l'au moins un terminal hôte (103) sur le réseau, et
    dans lequel l'au moins un terminal hôte (103) comprend
    des moyens d'identification d'un message de demande de transaction communiqué par l'au moins un terminal de point de vente (102), des moyens d'instanciation et de stockage d'un enregistrement de transaction associé à l'identifiant unique (110) pour être peuplé avec les données de transaction incluses dans le message de demande de transaction de l'au moins un terminal de point de vente (102),
    des moyens d'identification d'un message de demande de transaction communiqué par l'au moins un terminal de mobile client (101A, 101B),
    des moyens de mise en correspondance d'un message de demande de transaction de l'au moins un terminal de mobile client (101A, 101B) avec un message de demande de transaction stocké de l'au moins un terminal de point de vente (102) en utilisant l'identifiant unique (110) contenu dans le message de demande de transaction de l'au moins un terminal de mobile client (101A, 101B) afin d'identifier l'enregistrement de transaction stocké correspondant,
    des moyens d'encodage d'un message de demande de paiement pour un enregistrement de transaction,
    des moyens de communication du message de demande de paiement encodé vers l'au moins un terminal de mobile client sur le réseau, et
    dans lequel l'au moins un terminal de mobile client (101A, 101B) comprend en outre :
    des moyens de saisie d'un numéro d'identification personnel en réponse au message de demande de paiement ;
    des moyens de génération d'un hachage du numéro d'identification personnel saisi et des moyens de communication du hachage généré du numéro d'identification personnel vers l'au moins un terminal hôte (103) ;
    dans lequel l'au moins un terminal hôte (103) comprend en outre :
    des moyens de comparaison du hachage du numéro d'identification personnel reçu à partir du terminal de mobile client (101A, 101B) avec un hachage du numéro d'identification personnel généré par le terminal hôte (103) ; et
    des moyens d'autorisation d'un paiement électronique pour la transaction stockée si le hachage du numéro d'identification personnel reçu à partir du terminal de mobile client (101A, 101B) correspond au hachage du numéro d'identification personnel généré par le terminal hôte (103).
  8. Système selon la revendication 7, dans lequel l'identifiant (110) est une étiquette de communication en champ proche (NFC) (110).
  9. Système selon la revendication 8, dans lequel l'étiquette (110) est un code-barres unidimensionnel (401) ou un code-barres bidimensionnel (402), et les moyens de lecture de l'identifiant comprennent des moyens de capture optique (206).
  10. Système selon la revendication 8, dans lequel l'étiquette (110) est une étiquette d'identifiant radiofréquence (RFID), et les moyens de lecture de l'identifiant comprennent des moyens de réception de fréquences radio (201, 203, 204).
  11. Système selon la revendication 8, dans lequel l'étiquette (110) est un identifiant de terminal réseau sans fil, et les moyens de lecture de l'identifiant comprennent des moyens de mise en réseau local sans fil (311).
  12. Système selon l'une quelconque des revendications 7 à 11, dans lequel les moyens d'encodage d'un message de demande de transaction incluant l'identifiant unique (110) comprennent une unité centrale de traitement de terminal (201, 308) configurée par un ensemble d'instructions de traitement de données (705, 1006).
  13. Système selon l'une quelconque des revendications 7 à 12, dans lequel les moyens de mise en correspondance de messages de demande de transaction et les moyens d'encodage d'un message de demande de paiement comprennent une unité centrale de traitement de terminal hôte (308) configurée par un ensemble d'instructions de traitement de données (1203).
EP12737228.2A 2011-06-24 2012-06-21 Système et procédés de traitement de transaction distribuée Active EP2724303B1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP12737228.2A EP2724303B1 (fr) 2011-06-24 2012-06-21 Système et procédés de traitement de transaction distribuée

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP11171370 2011-06-24
EP12737228.2A EP2724303B1 (fr) 2011-06-24 2012-06-21 Système et procédés de traitement de transaction distribuée
PCT/EP2012/061955 WO2012175606A1 (fr) 2011-06-24 2012-06-21 Système de traitement de transaction distribué et procédés associés

Publications (2)

Publication Number Publication Date
EP2724303A1 EP2724303A1 (fr) 2014-04-30
EP2724303B1 true EP2724303B1 (fr) 2019-10-23

Family

ID=46545341

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12737228.2A Active EP2724303B1 (fr) 2011-06-24 2012-06-21 Système et procédés de traitement de transaction distribuée

Country Status (10)

Country Link
US (1) US10147078B2 (fr)
EP (1) EP2724303B1 (fr)
AR (1) AR086746A1 (fr)
BR (1) BR112013033359A2 (fr)
CA (1) CA2840467A1 (fr)
ES (1) ES2773100T3 (fr)
HK (1) HK1197309A1 (fr)
MX (1) MX2014000257A (fr)
TW (1) TWI559239B (fr)
WO (1) WO2012175606A1 (fr)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9642005B2 (en) * 2012-05-21 2017-05-02 Nexiden, Inc. Secure authentication of a user using a mobile device
US9521548B2 (en) * 2012-05-21 2016-12-13 Nexiden, Inc. Secure registration of a mobile device for use with a session
US20130311382A1 (en) 2012-05-21 2013-11-21 Klaus S. Fosmark Obtaining information for a payment transaction
SG10201506662XA (en) * 2015-03-03 2016-10-28 Mastercard Asia Pacific Pte Ltd Method For Enabling A Communication Link Between A Mobile Terminal And A Receiving Terminal
US20160299918A1 (en) * 2015-04-07 2016-10-13 Dell Software, Inc. Device Control Using a Secure Decentralized Transactional Ledger
US10496968B2 (en) * 2015-09-25 2019-12-03 Everi Payments Inc. Financial terminal that automatically reconfigures into different financial processing terminal types
TWI596559B (zh) * 2016-07-25 2017-08-21 Host device for a bank transaction system
SG10201610340WA (en) * 2016-12-09 2018-07-30 Mastercard International Inc Control of permissions for making transactions
TWI634435B (zh) * 2017-07-31 2018-09-01 全家便利商店股份有限公司 雲端翻譯及列印系統及方法
JP6756905B2 (ja) * 2018-06-29 2020-09-16 アリババ・グループ・ホールディング・リミテッドＡｌｉｂａｂａ Ｇｒｏｕｐ Ｈｏｌｄｉｎｇ Ｌｉｍｉｔｅｄ Ｕｒｌベースの二次元コードに関連付けたサービスの管理
US11165581B2 (en) * 2018-10-05 2021-11-02 Mimecast Services Ltd. System for improved identification and authentication
US11032275B2 (en) * 2018-10-05 2021-06-08 Mimecast Services Ltd. System for improved identification and authentication
EP4250208B1 (fr) * 2022-03-25 2024-05-08 Rubean AG Dispositifs, procédés et système de transactions de paiements électroniques sécurisées
EP4250207B1 (fr) * 2022-03-25 2024-05-08 Rubean AG Dispositifs, procédés et système de transactions de paiements électroniques sécurisées
EP4250209B1 (fr) * 2022-03-25 2024-05-01 Rubean AG Dispositifs, procédés et système de transactions de paiements électroniques sécurisées
EP4250210A1 (fr) * 2022-03-25 2023-09-27 Rubean AG Dispositifs, procédés et système de transactions de paiements électroniques sécurisées

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE19701697A1 (de) * 1997-01-20 1998-07-23 Werner Debold Abwicklungssystem für bargeldlosen Zahlungsverkehr und Transaktionsbedieneinrichtung hierfür
US7801826B2 (en) * 2002-08-08 2010-09-21 Fujitsu Limited Framework and system for purchasing of goods and services
US7784684B2 (en) * 2002-08-08 2010-08-31 Fujitsu Limited Wireless computer wallet for physical point of sale (POS) transactions
DE102007005427A1 (de) 2007-01-30 2008-07-31 Hischam Telib Verfahren und Vorrichtung zur elektronischen Zahlung
US20090254479A1 (en) * 2008-04-02 2009-10-08 Pharris Dennis J Transaction server configured to authorize payment transactions using mobile telephone devices
US8600881B2 (en) * 2008-11-13 2013-12-03 Visa International Service Association System and method for uniquely identifying point of sale devices in an open payment network
TW201032160A (en) 2009-02-19 2010-09-01 Simpleact Inc System and method for mobile trade
US9734495B2 (en) * 2009-06-02 2017-08-15 Qualcomm Incorporated Mobile commerce authentication and authorization systems
US8928456B2 (en) * 2010-01-08 2015-01-06 Apg Cash Drawer, Llc Wireless device operable cash drawer
US20120226565A1 (en) * 2011-03-05 2012-09-06 Motreus Inc. Method and apparatus for payment with mobile device at point of sale terminal
US8751317B2 (en) * 2011-05-12 2014-06-10 Koin, Inc. Enabling a merchant's storefront POS (point of sale) system to accept a payment transaction verified by SMS messaging with buyer's mobile phone

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
BR112013033359A2 (pt) 2017-02-07
TW201303761A (zh) 2013-01-16
WO2012175606A1 (fr) 2012-12-27
HK1197309A1 (en) 2015-01-09
MX2014000257A (es) 2014-09-01
CA2840467A1 (fr) 2012-12-27
EP2724303A1 (fr) 2014-04-30
TWI559239B (zh) 2016-11-21
US20140143078A1 (en) 2014-05-22
US10147078B2 (en) 2018-12-04
ES2773100T3 (es) 2020-07-09
AR086746A1 (es) 2014-01-22

Similar Documents

Publication Publication Date Title
EP2724303B1 (fr) Système et procédés de traitement de transaction distribuée
US11232437B2 (en) Transaction token issuing authorities
US9208482B2 (en) Transaction token issuing authorities
US8660948B2 (en) System and method for managing transactions with a portable computing device
AU2012311546B2 (en) Systems and methods for making a payment using a wireless device
US9600812B2 (en) Method and apparatus for fulfilling purchases
JP6151916B2 (ja) 証印読み取り機システムおよびモバイルデバイスへの自動情報配信システム
US20120284130A1 (en) Barcode checkout at point of sale
US10664819B1 (en) Systems and methods for associating a mobile device with a point of sale terminal
WO2013142209A1 (fr) Système et procédé pour faciliter des transactions par paiement libre-service sécurisé de produits de détail
KR20100045586A (ko) 휴대용 이동통신단말기를 이용한 결제 서비스 방법 및 그 시스템
KR20120114799A (ko) 큐알 코드를 이용한 지불 시스템
JP2021131844A (ja) モバイル端末機を利用した決済情報伝達システム及びこれを利用した決済情報伝達方法
KR20140038697A (ko) 무선통신 단말기 및 이를 이용한 금융결제 시스템 및 방법
US11514450B2 (en) System and method for mobile payments
KR20100046128A (ko) 포스단말을 이용한 결제처리 시스템
KR20100005628A (ko) 포스단말을 이용한 결제처리 방법 및 시스템과 이를 위한프로그램 기록매체
KR20100042716A (ko) 입금내역 조회 기능이 구비된 결제단말과 결제단말을 이용한 입금내역 조회 서비스 방법 및 시스템

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

17P Request for examination filed

Effective date: 20140123

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1197309

Country of ref document: HK

17Q First examination report despatched

Effective date: 20150327

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20190710

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602012065075

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1194517

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191115

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191023

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200124

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200123

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200123

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200224

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2773100

Country of ref document: ES

Kind code of ref document: T3

Effective date: 20200709

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602012065075

Country of ref document: DE

PG2D Information on lapse in contracting state deleted

Ref country code: IS

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200223

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1194517

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191023

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

26N No opposition filed

Effective date: 20200724

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602012065075

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200621

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200621

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200621

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200630

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200630

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200621

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200630

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200621

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200622

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20191023