WO2016123664A1

WO2016123664A1 - Method, terminal, system and server for terminal advertising

Info

Publication number: WO2016123664A1
Application number: PCT/AU2016/050054
Authority: WO
Inventors: Adam MCARDLE
Original assignee: Advertec Pty Ltd
Priority date: 2015-02-02
Filing date: 2016-02-01
Publication date: 2016-08-11

Abstract

There are disclosed methods for advertising on a payment terminal having a screen. The method include the steps of receiving, at the payment terminal, a start transaction input to provide transaction authorisation data; sending, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal. The method also includes displaying, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and receiving, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertisement display period.

Description

Method, Terminal, System and Server for Terminal Advertising Related Applications

[001] This application claims priority from Australia provisional patent application No. 2015900311 filed on 2 February 2015, the contents of which are incorporated by reference.

Technical Field

[002] The invention relates to a method, terminal, system and server for terminal advertising, in particular, advertising on payment terminals.

Background

[003] Payment terminals are commonly used to make payments using a payment instrument such as a debit or credit card. Such payment terminals include a screen to display transaction information such as purchase price and status, and a key pad or touch screen to receive user input such as a pin code.

[004] Payment terminals are secure devices that need to interact with a banking system to authorise (approve or disapprove) a particular transaction. In use, a user typically needs to insert, swipe or tap the payment instrument such as the debit or credit card, or otherwise allow the terminal to read the payment instrument. The terminal, in most cases, then asks for a pin code and authorisation data, that may include the pin code and payment instrument data, is sent to the banking system for authorisation.

[005] The authorisation period may take about 7 seconds in which time the user is typically waiting or viewing the screen that typically displays an "awaiting approval message". The terminal then typically displays an approval message and the receipt is printed thus completing the transaction. [006] Advertisers desire to present advertisements to a consumer. Advertisers prefer to customise and/or target advertisement to a consumer such as targeting the location or age of the user. Advertisers also desire to interact with consumers such as by being able to track a consumers interest in a particular advertising campaign and capturing information and details of the consumer.

[007] The invention disclosed herein seeks to provide a method, payment terminal and system that are configured to display advertisements via the payment terminal, which are preferably targeted, to the user or consumer undertaking a transaction at the payment terminal.

Summary

[008] In accordance with a first main aspect there is provided, a method for advertising on a payment terminal having a screen, the method including: receiving, at the payment terminal, a start transaction input to provide transaction authorisation data; sending, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; displaying, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and receiving, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertisement display period.

[009] In an aspect, the start transaction input includes the payment terminal reading a payment instrument communicated with the payment terminal.

[0010] In another aspect, the start transaction input includes the payment terminal receiving a code associated with the payment instrument.

[0011] In yet another aspect, the advertisement display period includes a minimum display time, and the method includes the step of: Timing, at the payment terminal, the advertisement display period, and wherein on receipt of the return authorisation data the payment terminal is configured to terminate the advertisement display period if the minimum display time has elapsed.

[0012] In yet another aspect, wherein the minimum display time is about 1 to 10 seconds.

[0013] In yet another aspect, the minimum display time is about 3 seconds.

[0014] In yet another aspect, the method according to any one of the previous claims, wherein the method includes the advertisement displaying a prompt configured to receive prompt input data from a user, and wherein payment terminal is configured to receive and at least temporarily store the prompt input data.

[0015] In yet another aspect, the prompt input data includes a at least one of a click, a selection, personal contact information, a number, a word, a code, a rewards scheme identifier or number, a telephone number and an email address.

[0016] In yet another aspect, the method includes the step of: Sending, via the payment terminal, the prompt input data to an external server.

[0017] In yet another aspect, the method including the step of: displaying, on the screen, a prompt associated with the advertisement during the advertisement display period, the prompt being configured to receive prompt input data.

[0018] In yet another aspect, the method includes the step of: receiving, the prompt input data, and wherein upon receipt of the prompt input data the advertisement display period is extended for a further period.

[0019] In yet another aspect, the further period is terminated at least one of a user inputted termination and a maximum elapsed time. [0020] In yet another aspect, the method includes the step of: on receipt of the prompt input data, displaying on the screen, at least one of a further advertisement, information, a screen view and a further prompt to capture further prompt data.

[0021] In yet another aspect, wherein the further prompt is configured to capture user inputted data least one of a click, a selection, personal contact information, a number, a word, a code, a rewards number, a telephone number and an email address.

[0022] In yet another aspect, wherein the method includes the steps of: determining, via a processor of the payment terminal, the advertisement to display, the payment terminal being configured to select the advertisement from a plurality advertisements stored on memory of the payment terminal based on a selection criteria.

[0023] In yet another aspect, the step of determining the advertisement to display includes: comparing, via the processor, transaction profile data associated with the transaction with advertisement profile data associated with each of the plurality advertisements to determine a selection index, and selecting, via the processor, the advertisement to display based on the selection index that best matches with the selection criteria.

[0024] In yet another aspect, the selection criteria includes values associated with at least one of a terminal identifier, time of day, card type, merchant type, merchant name, merchant location and bank identifier.

[0025] In yet another aspect, wherein the transaction profile data includes at least one of a terminal identifier, time of day, card type, merchant type, merchant name, merchant location and bank identifier.

[0026] In yet another aspect, the start transaction input includes the payment terminal reading a payment instrument, and wherein the transaction profile data includes payment instrument data acquired from reading the payment instrument.

[0027] In yet another aspect, the payment instrument data includes at least one of a payment scheme, issuing bank, card identifier and card type. [0028] In yet another aspect, wherein the method includes the step of: receiving at the payment terminal, advertisement data representing the plurality advertisements.

[0029] In yet another aspect, each of the plurality of advertisements of has associated advertisement profile data, and wherein the payment terminal is configured to compare the transaction profile data with the advertisement profile data to determine the advertisement to display.

[0030] In yet another aspect, wherein the method includes the step of: determining, at the payment terminal, if the payment terminal is in at least one of a transaction period including the advertisement display period and an idle period, wherein: in the transaction period, the payment terminal is configured to restrict communication between an external advertising server and the payment terminal; and in the idle period, the payment terminal is configured to communicate with the external advertising server so as to at least one of receive advertisement data and send captured transactional data.

[0031] In accordance with a second main aspect there is provided, a computer software application for operation on a payment terminal, the software configured to operate a method as defined above.

[0032] In accordance with a third main aspect there is provided, a payment terminal configured to operate a method as defined above.

[0033] In accordance with a fourth main aspect there is provided, a system including a payment terminal as defined above and a server configured to communicate with the payment terminal, the server being configured receive user data inputted to the payment terminal during the advertisement display person, and send further advertising data to the user associated with the user data.

[0034] In an aspect, wherein the user data includes an identifier linkable to the user such as a number, code, reward scheme identifier or number, account number, telephone number, email address, and wherein the server is configured to send the further advertising data to the user using the identifier. [0035] In accordance with a fifth main aspect there is provided, a system including a payment terminal having a screen and a server in communication with the payment terminal, the system being configured to: receive, at the payment terminal, advertising data from the server; receive, at the payment terminal, a start transaction input to provide transaction authorisation data; send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; displaying, on the screen of the payment terminal, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and receiving, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertising display period; sending, to the server, data representing the advertisement displayed during the advertisement display period.

[0036] In accordance with a sixth main aspect there is provided, a system for targeted advertising including a payment terminal having a screen and a server in communication with the payment terminal, the system being configured to: receive, at the payment terminal, advertisement data from the server; receive, at the payment terminal, a start transaction input to provide transaction authorisation data; send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; determine, via a processor of the payment terminal, an advertisement to display, the payment terminal being configured to select the advertisement from advertisement data representing a plurality of advertisements stored based on an advertisement selection criteria; display, on the screen of the payment terminal, the selected advertisement having an input prompt for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; receive, at the payment terminal, user data inputted in response the input prompt; receive, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertising display period; send, to the server, the user data representing any user data inputted and advertisement data identifying the selected advertisement displayed.

[0037] In accordance with a seventh main aspect there is provided, a computer readable medium for a payment terminal having a screen, the computer readable medium being configured to operate the payment terminal to: receive, at the payment terminal, a start transaction input to provide transaction authorisation data; send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; display, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and receive, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of the receipt of the return authorisation data and expiry of the advertisement display period.

[0038] In accordance with a eighth main aspect there is provided, a payment terminal having a screen, the payment terminal being configured by software to: receive, at the payment terminal, a start transaction input to provide transaction authorisation data; send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; display, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and receive, at the payment terminal, the return authorisation data, and terminate, the advertisement display period upon at least one of receipt of the return authorisation data and expiry of a minimum elapsed time of the advertisement display period.

[0039] In accordance with a ninth main aspect there is provided, a payment terminal having a screen, the payment terminal being configured by software to: read, via the payment terminal, a payment instrument communicable with the payment terminal thereby providing payment instrument data; receive, at the payment terminal, a start transaction input to provide transaction authorisation data; send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal; determine, via a processor of the payment terminal, an advertisement to display, the payment terminal being configured to select the advertisement from advertisement data representing a plurality of advertisements stored on memory of the payment terminal, the selection being at least partially based on a comparison between transaction profile data including payment instrument data and advertisement profile data associated with the advertisement data; display, on the screen, the selected advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; time, via the processor of the payment terminal, an elapsed time associated with the advertisement display period; receive, at the payment terminal, the return authorisation data, and terminate, the advertisement display period upon at least one of receipt of the return authorisation data and expiry of a minimum elapsed time of the elapse time associated with the advertisement display period.

[0040] In accordance with a tenth main aspect there is provided, a server configured to communicate with a payment terminal described above, the server having a database storing advertising data.

Brief Description of the Figures

[0041] The invention is described, by way of non-limiting example only, by reference to the accompanying figures, in which;

[0042] Figure 1 is a system diagram illustrating a advertising system including a payment terminal and an advertising server;

[0043] Figure 2 is a diagram illustrating a payment terminal including a computer system and a display screen;

[0044] Figure 3 is a relational diagram illustrating software relationships between the payment terminal and the server;

[0045] Figure 4a is a illustrating a method for advertising on a payment terminal having a screen;

[0046] Figure 4b is a series of example screens provided by the payment terminal during the method as shown in Figure 4a;

[0047] Figure 5 is a flow chart illustrating a method of use a payment terminal configured to display an advertisement and collect user information;

[0048] Figures 6a & 6b is a flow chart illustrating a method of operation of a payment terminal during a transaction configured to display an advertisement and collect user information;

[0049] Figures 7a & 7b is a flow chart illustrating a method of operation of a payment terminal during idle time (between transactions) configured to display an advertisement and collect user information;

[0050] Figures 8a and 8b is a data relationship diagram illustrating data relationships between advertiser data stored on a database of the system; and

[0051] Figure 9 is a data relationship diagram illustrating data relationships between terminal data stored on a database of the system.

Detailed Description

[0052] Referring to Figures 1 to 3, there is shown a system 100 for advertising including a payment terminal 102 and a server 104 in communication with the payment terminal 102.

[0053] The payment terminal 102 is configured to interact with, display an advertisement to, and receive information from a card holder or user 106. The payment terminal 102 includes a display screen 108 which may be a touch screen, on which the advertisement is displayed, and an input device 110 in the form of a keypad 112. However, the input device 110 may also be the screen 108 when configured as a touch screen. Some examples may include both a touch screen and keypad or buttons.

[0054] As shown in Figure 2, the payment terminal 102 includes a computer device or system 103 including a processor 114, a data storage device or memory 116, a communications module 118 for communicating with the server 104 and a remote external authorisation system or banking system 120, and an I/O module (I/O) 128 for communicating with a display 108 and the user input device 110. The payment terminal 102 includes a reader 109 configured to read data from a payment instrument such as a bank card or the like.

[0055] The communication may be over a network 119 such as wired networks, the internet and wireless networks such a 3G/4G networks. The payment terminal 102 is configured to read a payment instrument 105 such as, but not limited to, a bank card or the like. An example of suitable payment terminals may be a Verifone™, Ingenico™ or PAX™ payment terminal. These are typically portable and hand held, or mounted payment terminals. However, other payment terminal and computing configurations may be utilised. Such payment terminals are commercially available and are not described in further detail herein. It is noted that such payment terminals are also sometimes referred to as POS (Point of Sale) Devices.

[0056] The terminal 102 is configured to operate a software product 135, as illustrated in Figure 3, which is stored on the data storage device or memory 116 and executed by the computing system 103, more specifically the processor 114, so as to allow the terminal 102 to perform the methods described below. The software includes a payment application 130 which interacts with the bank system 120 to authorise payment transactions and an advertising software application 132 that is configured to interface, via an API 134 (Application Programming Interface) with the main payment application 130.

[0057] The main payment application 130 is commercially available (typically the main payment application is provided by a bank or industry gateway for use with the payment terminal) to communicate with the bank system 102 that is operated by the bank or financial institution. However, the advertising software application 135 and API 134 have been specially coded or developed to operate the methods described herein, such as timing the display of advertisements, selection of advertisements for display based on transaction profile data, and sending and receiving data to the server 104, and sending and receiving data between the user 106 and the payment terminal 102.

[0058] Accordingly, the advertising software application 132 and API 134 may be considered as the software product 135 that may be loaded or installed onto payment terminals 102. Whilst the software applications are technically different, from a users perspective the software operating the advertising system 100, and in particular the payment terminal 104, may be considered a single advertising software product or solution.

[0059] The server 104 also includes a computer device or system 113 including a processor 124, memory 126, a communications module 128 for communicating with payment terminal and a remote banking system 120 102 via the network 119, and an I/O module (I/O) 131 for communicating with I/O devices such as screens and keyboards. Other computing configurations may be utilised. The server 104 also includes application software stored on memory 126 and may include one or more databases 129, such as an Oracle™ or MySQL™ database, which stores advertising data. The data held on such databases is further described below with reference to Figures 8a, 8b and 9. Such servers and computer systems 113 are commercially available and are not described in further detail herein. Various types of cloud computing and database systems may also be employed to achieve a similar functionality.

[0060] The server 104 may be configured to communicate transaction profile data such as TID (Terminal Identification), MID (Merchant Identification), MCC (Merchant Type) and SID (unique Store Identifier) with the bank system 120. Accordingly, the server 104 is able to generate transaction profile data , for example, MCC and configure a particular terminal 102 to display advertisement suitable for that particular MCC. [0061] The server application software may allow configuration of the server 104 and terminal 102 software and operations, and in particular, modification of the advertisements (such as advertisement selection and scheduling) by a terminal merchant 121 and other users that may include a sales person 123 and an advertiser 125.

[0062] The server 104 is also configured to receive user input data, which may include identifiers such as codes, numbers text, rewards scheme identifiers, and personal information including, but not limited to, mobile telephone data, email address data. The server 104 may also be configured to perform further data operations such as by storing the user data, and sending (or instructing further systems to send) communications related to the identifiers and personal information such as, but not limited to, emails 140 or text messages 142 to the customer 106 whom made the transaction at the payment terminal 102. The server 104 is configured by the server application software to send advertisement data to the payment terminal 102 which is then at least temporarily stored by the payment terminal 102 for displaying advertisements as is further described below.

[0063] Turning now the methods of use of the advertising system 100, and in particular the payment terminal 102. Figure 4a presents a method 150 of terminal advertising using the system 100 as described above and Figure 4b shows a selection of example screen views 191 during the method 150.

[0064] The more detailed methods 200, 300, 400 as operated by, in particular the payment terminal 102, are then described below with reference to Figures 5, 6 and 7 and details on the advertising data (in particular the structure of the back-end databases) are further described below with reference to Figures 8 and 9.

[0065] Referring to Figure 4a, there is shown a method 150 for displaying advertising on a payment terminal 102 having a screen 108. The method includes, at step 160, receiving, at the payment terminal 102, a start transaction input to provide transaction authorisation data. The start transaction input is typically be initiated by the payment terminal reading the payment instrument 105, such as a bank card, communicated with the payment terminal by a user or purchaser and the user then inputs a code, such as a pin code associated with the payment instalment, and presses "accept" or "enter" on the terminal thereby providing the start transaction input. An example of the screen view of the payment terminal 102 at this step is indicated at 192 in Figure 4b. To communicate with the payment terminal the payment instrument 105 may be swiped past or inserted into a reader of the payment terminal 102.

[0066] At step 170, the payment terminal 102 is configured to send, the transaction authorisation data to an external authorisation system that is typically a bank system 120. The external authorisation system being configured to provide return authorisation data to the payment terminal 102.

[0067] At step 180, the payment terminal 102 is configured to display on its screen 108 an advertisement for an advertisement display period. The advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data. The advertisement display thereby being initiated by the transaction and occurring intra-transaction.

[0068] The advertisement may include prompts to entice and receive user input as is further detailed below in methods 200, 300 and 400. This allows intra-transaction interaction with the user, typically the card holder. User inputted data may then be obtained. An example of the screen view of the payment terminal 102 at this step is indicated at 193 in Figure 4b.

[0069] The payment terminal 102 may also be configured to determine or build transaction profile data that may include information such as information read from the payment instrument 105 and other information associated with the transaction such as terminal ID, time of day, bank etc. The payment terminal 102 may also be configured to compare the transaction profile data to advertisement profile data thereby enabling the payment terminal 102 to select intra-transaction a particular advertisement for display. The payment terminal 102 may also be configured to record user input associated with the prompt.

[0070] The advertisement display period is typically a minimum of around 3 seconds, although other periods may be used within the range of about 1 to 10 seconds. However, the payment terminal 102 may configured to extend the advertisement display period if the user interacts with the prompts of the advertisement. For example, if the user interacts the with prompt, the a further screen may be displayed and an example of the screen view of the payment terminal 102 at this step is indicated at 194 in Figure 4b.

[0071] At step 190, the payment terminal 102 is configured to receive the return authorisation data. The payment terminal 102 is then configured to terminate the advertisement display period on at least one of receipt of the return authorisation data and expiry of the advertisement display period. An example of the screen view of the payment terminal 102 at this step is indicated at 195 in Figure 4b.

[0072] Preferably, the payment terminal 102 is configured to display the advertisement for a minimum display time, say 3 seconds, and then on receipt of the return authorisation data the payment terminal is configured to terminate the advertisement display period if the minimum display time has elapsed in which case the advertisement period sets the advertisement display period. However, in other examples, the advertisement display period may be terminated on receipt of the return authorisation data so as to not prolong the transaction.

[0073] In some examples, the payment terminal 102 may also increase the minimum display time when the user interacts with the prompt. This enables the user to prolong the advertisement display period, if desired. The payment terminal 102 may also be configured to record and store information about the transaction such as the transaction profile data, any user input such as clicks or interaction with the prompt, and the selected advertisement that has been shown.

[0074] Further details in relation to method 150 and the operation of the system 100 are now provided below.

[0075] Referring to Figure 5, the method 200 includes actions or data transfer between the payment terminal 102, the user or cardholder 106 and the server 104. When not engaging in a payment transaction process, the method 200 includes an idle step 202 which include step 204 of sending advertising data from server 104 to the payment terminal 102. The advertising data may be targeted based upon a set of advertising selection criteria or data and comparison of this data with transaction profile data that is further described below. The idle time processes are further described below with reference to Figures 7a & 7b.

[0076] The payment or transaction process typically begins at step 206 in which the merchant enters a transaction or purchase amount into the payment terminal 102. The payment instrument 105, such as bank card, is then typically communicated with the payment terminal 102 and the payment terminal 102 reads payment instrument data from the payment instrument 105. However, the ordering of the transaction process may be altered and may include the payment instrument 105 being first communicated prior to the transaction amount being confirmed or entered into the payment terminal 102.

[0077] As step 208, the merchant or the user (at step 210) selects the account type which may be one of cheque, savings or credit. At step 212, the user is requested to enter the pin and at step 214 the cardholder or user enters the pin. At step 216, the payment terminal 102 sends authorisation data, which includes the card data and pin, to the external banking system 120.

[0078] In response to the terminal 102 sending the transaction authorisation data to the external banking system 120, the terminal is configured to initiate an advertising display routine 218 including an advertising display period. The reading of the payment instrument such as the credit card or debit card or the entering of the amount provides a start transaction input which the initiates the terminal 102 sending the transaction authorisation data to the external banking system 120 which in turn initiates the advertising display routine 218.

[0079] At step 220, the payment terminal 102 is configured to display the advertisement. Further details on the method and processes of the payment terminal 102 during the advertising display routine 218 are further described below with reference to method 300 as shown in Figure 5a & 5b.

[0080] However, at step 222, the payment terminal 102 is configured to display a prompt to the user which may include, for example, a prompt including a question such as "press enter for more information". If the user provides a positive response or user input to the prompt such as by pressing or clicking "enter" at step 224, then at step 225 the user is provided with a further prompt requesting and input from the user. In this example, the input request prompt may include the text "enter mobile phone number" or "enter email address" or the like which is at least temporarily recorded by the payment terminal 102.

[0081] The user then enters this input information at step 228. The advertising display routine 218 is then terminated at steps 226 by the payment terminal receiving transaction approval data from the external banking system 120. If the user declines to press enter for more information and step 222, the routine simply awaits receipt of the transaction approval data from the external banking system 120 at which point the advertisement display routine is terminated at step 226.

[0082] At step 230, the payment terminal 102 prints payment receipt and at step 234 the customer takes the receipt which ends the users or customers transaction process. At step 236, the payment terminal 102 is configured to send, to the server 104, any captured customer or user data including, but not limited to, card information, time information, transaction time and, in particular, any contact details inputted by the customer at step 225 and 228.

[0083] At step 238, the server 104 is configured to record the customer data which preferably includes at least one of a user identifier code or number such as those associated with a rewards scheme, customer loyalty program or frequent flyer program, a customer email address or contact mobile phone number. In this example, the customer data includes a mobile telephone number, and at step 240 the server 104 is configured to send an SMS message to the cardholder and at step 242 the cardholder may enter an email address in reply to the text message sent at step 240. At step 244, the email address is received by the server 104 and further data operations are performed which may include sending an email to the user which is received by the user at step 246. The email preferably includes links to advertisers and the user may directly interact with the advertiser. [0084] Referring now to Figures 6a & 6b, there is shown a method 300 for advertising on a payment terminal 102 having a screen 108. The method 300 includes actions or data transferred between the payment terminal 102, the user or cardholder 106, the server 104 and an external banking system 120. When not engaging in a payment transaction process, the method 300 includes an idle step 302 which includes step 304 of sending advertising data from the server 104 to the payment terminal 102. The advertising data may be targeted based upon a set of advertising selection criteria or data that is further described below. The idle time processes are further described below with reference to Figures 7a & 7b.

[0085] It is noted that Figures include four columns having headings: Advert application; Payment Terminal; Card Holder; and Server. It is noted that the Advert application is preferably the advert VAS (Value Added Server Application) application 132 operated locally on the payment terminal 102, the card holder may include a user such as a purchaser or customer 106 and a merchant, and the server is typically the server 104 in communication with the payment terminal 102.

[0086] Turning to Figures 6a & 6b in detail, similar to method 200, the payment or transaction process typically begins at step 306 in which the merchant enters a transaction or purchase amount into the payment terminal 102 and the payment instrument 105 is read by the payment terminal 102. At step 308, the merchant or the user, at step 310, chooses the account type which may be one of cheque, savings or credit. At step 212, a start transaction input is requested in which the user is requested to provide the start transaction input which is in this example, a pin or code and at step 214 the cardholder or user enters or provides the start transaction input. In this example, the start transaction input is the user entering a pin. However, the start transaction input may include any user activated, payment input or instrument including the communication of a payment instrument, such as a debit or credit card, in contact with or in contactless communication with the payment terminal and/or the providing of a user inputted password, code or pin. The payment instrument or inputted password, code or pin provides payment or transaction authorisation data.

[0087] At step 316, the payment terminal 102 is configured to send the transaction authorisation data, which includes the card data and pin, to the external banking system 120. In response to the terminal 102 sending the transaction authorisation data to the external banking system 120, the payment terminal 102 is configured to initiate an advertisement display routine 318 including in displaying an advertisement during a display period. In this example, the advertisement display routine 318 is initiated directly by the sending of the transaction authorisation data to the external banking system 120. However, the advertisement display routine 318 may be initiated by the start transaction input either directly or indirectly. In this example, the start transaction input indirectly begins the advertisement display routine 318.

[0088] Turning now the advertisement display routine 318 in more detail. The advertisement display routine 318 includes, at step 320, acquiring or building a transaction profile data. The transaction profile data includes identifiers such as TID (Terminal Identification), MID (Merchant Identification), Payment instrument or card type (credit card, savings card etc) and Scheme Type (Visa™, MasterCard™ etc.), time of day or other data associated with the transaction.

[0089] The transaction profile data is communicated with or sent to the advertising application 132 that in this example is operating locally on the payment terminal 102. The payment terminal, via the advertising application 132, then performs an advertisement selection or targeting routine 322 in which the payment terminal determines and selects the advertisement for display. The advertisement selection or targeting routine utilises the transaction profile data to select and target an advertisement to the user based on the transaction profile data. The advertisement selection or targeting routine makes the selection from one or more of a series of advertisements that include advertisement data including advertisement identification data.

[0090] The payment terminal 102 is configured by the advertisement selection routine 322, at steps 324 and 326, to determine if one or more of the series of advertisements includes a pre-determined to be displayed or guaranteed advertisement that guaranteed to be displayed. For example, the advertisement data may include a Guaranteed to Display tag or identifier and a display counter. If the advertisement includes a Guaranteed to Display tag or identifier, and has, for example, a zero display counter - then the payment terminal of configured to display this advertisement at step 332 whereby the advertisement is called and displayed by the payment terminal. If there are multiple guaranteed advertisements, the payment terminal 102 determines which advertisement to show based on a lowest counter at step 326. The selected advertisement is then displayed at step 332.

[0091] At step 324, if the advertisement data indicated that no preferred or guaranteed advertisements are present, then the payment terminal 102 is configured to select an advertisement based on a Advertisement Weighting Index (ADI). The Advertisement Weighting Index may include a variety of parameters including, but not limited to including, the transaction profile data and advertisement counter data. The selected or determined advertisement is then sent to or called from the payment terminal 102 at step 332 and displayed.

[0092] In more detail, the ADI is calculated based on the transaction profile data (including the TID, MID, Payment Instrument or Card Type, Scheme Type (Visa™, MasterCard™,) time of day etc. and pre-determined advertisement selection profile data associated with the advertisement.

[0093] The pre-determined advertisement selection profile data may include Time of Day Offers, Location Offers (based on Terminal Postcode and association between TID and postcode to allow geographic targeting), Shopping Centre (association between TID and installing shopping centre), Card Scheme Offers, Type of Card Offers and Type of terminal offers.

[0094] Accordingly, the payment terminal 102, via the advertisement application, undertakes processing operation to determine a best match between the transaction profile data and the pre-determined advertisement selection data. These operations include, for example, associating the TID & MID with their locations and shopping centres and associating the Card Type and Scheme Type with a particular scheme and card type stored on the pre-determined advertisement selection data.

[0095] For example, requirements for selecting the advertisement may include: [Card type match = 101 points]; [Scheme type match = 100 points]; [Time of day match = 98 points] and ADI may include a calculation of: [Card type + Scheme type + Time of day = Advertisement to display]. For example, if the users Card Type is a credit card with a particular bank - then the advertisement selected may be based on this selection criteria so that the user is shown an advertisement for the particular bank or selected by the particular bank for display.

[0096] Alternatively, there may be a match only for TDD (Time of Day) such as a midday period between 11 :30 and 1 :30 pm in which a particular advertisement is selected to be displayed. In more detail, Time of Days Offers may be based on the following options that may be based one or more of the following selection criteria: Offer promoted before a certain time of day: Offer promoted after a certain time of day: Offer promoted between 2 times: Offer promoted on particular days of the week (e.g. Monday - Friday): Offer promoted at any time during day but limited to particular days of the week; and Offer promoted any time/ any day.

[0097] Other examples, may include Location offers that may be based on the following options: Offer within same postcode as Terminal; Offer within same city; Offer within same state as Terminal; Offer Australia Wide; Offer within same Shopping Centre; Offer within distance Radius of same postcode as Terminal. This requires the TID to be matched to a postcode (or other location information).

[0098] Various selection calculations or algorithms may be applied. However, importantly, the method makes direct use of the transaction profile data (at the time of the transaction) to directly target the advertisement.

[0099] At step 334, the selected advertisement is displayed for an advertisement display period. In this example, the advertisement display period is set to a minimum period of 3 seconds. However, other minimum periods may also be set in the range of about 1 second to about 10 seconds.

[00100] In this example, the payment terminal 102 is configured to display a prompt, within or associated with the displayed advertisement, to the user which may include, for example, a prompt including a question such as "press enter for more information". The user may optionally interact with the prompt at step 335. [00101] If the payment terminal 102 receives a user prompt input at step 336 such as by the user pressing "enter" at step 335, then at step 338 the user is provided with a further prompt requesting an input from the user. In this example, the input request prompt may include the text "enter mobile phone number" or "enter email address" or the like which is at least temporarily recorded by the payment terminal 102. The user then enters this input information at step 340.

[00102] At step 342, payment terminal 102 is configured to wait for the minimum time period which in this example is 3 seconds. If a prompt response is received from the user at step 340, then at step 344 the payment terminal 102 is configured to record the input data steps 344. However, if no user prompt input is received then the routine proceeds to step 346, which times the minimum wait time period of 3 seconds and continues to wait until receipt of the return or reply authorisation data from the banking system at step 348. At step 348, provided the minimum time has elapsed, receipt of the return authorisation data ends or terminates the advertisement display period.

[00103] At step 350, the payment terminal 102 is configured to return to a payment-processing mode and at step 352 the payment terminal is configured to display or indicate if the transaction has been approved or declined by the banking system 120. At step 356, the receipt is printed and the user takes the receipt at step 356 which concludes the users transaction process.

[00104] At step 358, the payment terminal 102, via the advertising application, is configured to, record the inputted or received user data which may include an email address or phone number or the like. The advertisement identification (ADID) is also recorded to associate the user input data, profile data and click data. This allows the user to be associated with a particular advertisement and also tracking of the clicking (user interaction) with a particular advertisement. At step 360, the advertisement data which may include a click counter is updated or incremented to count the clicks of the advertisement.

[00105] At step 362, the payment terminal 102 directly sends captured advertising data which may include the user data, profile data, click data and ADID to the server 104. At step 364, the server 104 records the captured data including the user input data, profile data and click data. At step 366, the server 104 is configured to send a communication such as SMS message to the user or cardholder (who made the transaction) and at step 370 the cardholder may enter an email address in reply to the text message sent at step 370. At step 366, the users email is received by the server 104 and further data operations are performed which may include, at step 368, sending an email to the user which is received by the user at step 372. The email preferably includes links to advertisers and the user may directly interact with the advertiser.

[00106] Referring to Figures 7a & 7b, the idle time process is now described in further detail as method 400. The idle time process is performed by the system 100 when the payment terminal 102 is not in use. At step 402, the server 104 receives an input from an administration user as to the frequency at which to update the advertisement data on the payment terminal 102. In this example, this is provided by an update frequency profile (UFP) number or index.

[00107] At step 404, the payment terminal 102 receives the update frequency profile counter (UFP) number. At step 406, the counter is incremented and updated until the counter reaches the UFP number. At step 408, a UFP flag is set. The update frequency profile (UFP) will determine the % of idle time used for displaying Banner Adverts. The UFP will be sent from the server 104. The payment terminal 102 will check the sever 104 after each Banner advert display to see if there are new banner or inter-transactional advertisements for the terminal 102.

[00108] At step 410, the payment terminal is configured to undergo a waiting routine period that in this example is set to about 5 minutes. Other periods, shorter or longer, may also be utilised. At step 412, the payment terminal is configured to determine in the UFP flag is set and, if the flag is set, the payment terminal 102 via the payment application is configured to call in an advertisement at step 414, the advertisement page is then sent from the advertising application at step 416 and displayed at step 418 on the screen of the payment terminal 102.

[00109] At step 420, the payment terminal 102 is configured to display a prompt, within or associated with the displayed advertisement, to the user which may include, for example, a prompt including a question such as "press enter for more information". If the user provides a positive response to the prompt such as by pressing "enter" at step 420, then the payment terminal 102 as configured by the payment application is configured to call more information at step 422 and the advertising application is configured to send more information at step 424 which is displayed at step 426, via the payment application, by the payment terminal 102.

[00110] At step 428, the user is provided with a further prompt requesting and input from the user. In this example, the input request prompt may include the text "enter mobile phone number" or "enter email address" or the like which is at least temporarily recorded by the payment terminal 102.

[00111] A step 430, the payment application records the input data, by recording key strokes, and at step 432, the payment terminal 102, via the advertising application, is configured to, record the inputted or received user data which may include an email address or phone number or the like. The advertisement identification (ADID) is also recorded to associated the user input data, profile data and click data. This allows the user to be associated with a particular advertisement and also tracking of the clicking (user interaction) with a particular advertisement.

[00112] At step 436, the payment terminal 102 directly sends captured advertising data which may include the user data, profile data, click data and ADID to the server 104. At step 438, the server 104, via server application software, records the captured data including the user input data, profile data and click data. At step 440, the server 104 is configured to send a communication such as an SMS message to the user or cardholder (who made the transaction) and at step 442 the user or cardholder may enter an email address in reply to the text message. The users email is received by the server 104 and further data operations are performed which may include, at step 444, sending an email to the user which is received by the user at step 446. The email preferably includes links to advertisers and the user may then directly interact with the advertiser.

[00113] At step 448, the server application undertakes a protection routine in which the MID and TID may be checked to ensure the Merchant (terminal operator) has not opted out of advertisements on their terminals. Other checks include MID shall be checked to see if the Merchant only wants to advertise their own organisation and also advertisers using the same MCC code as the terminal merchant shall not be allowed to be displayed on the terminal. For example, if the MCC (merchant type) is a mechanic - then other mechanics (who are not the terminal operators) cannot display advertisements on the particular terminal.

[00114] At step 450, the server 104 via the server application then undertakes a selection routine in which the advertisements which the highest score (determined by click rate and user interaction) are selected. The selection of advertisements is taken from a database or pool of advertisements and the selection may include a subset of, for example, 5 advertisements selected for a particular terminal and associated with its TID.

[00115] At step 452, the payment terminal 102, via the advertising application

132, is configured to check or determine if any new advertisements are available for display. If there are no new advertisements, then the routine returns to step 402, and if there are new advertisements, then at step 454 the new advertisements communicated, more specifically downloaded, from the server 104 to the payment terminal 104. At step 456, the advertisements are saved or stored locally on the payment terminal 104 and the download is completed at step 458. Typically, the advertisements may be provided as a set of five advertisements selected for and associated with the particular TID. The old or previous advertisements and associated advertising data may be deleted from the payment terminal 104 at step 460.

[00116] Referring now to Figures 8a, 8b and 9, the data relationships and structures to be stored on the database 129 stored of the server 104 will be described in further detail. This section of the database is used by advertisers to build advertisements and advertisement campaigns. It is also used to track the advertisers and the billing. Referring firstly to Figure 7a and 8b, the data relationships and structures are now described in further detail. Ad Campaign

[00117] Background: This is the key table in the advertisers section and is the hub for which Adverts are displayed and when. There may be many campaigns that use the same Advert but the campaign will be unique on all levels. When a terminal connects then the five best matched campaigns will be loaded on the terminal.

[00118] Key Links: This table links to the:

• Advertiser table through the Advertiser ID to allow for billing and access control

• Ads table through the ADID to allow for the selection of which advert to target in the campaign

• Card Holder details table through Card Type and Scheme Type to allow for the selection of which Card and Scheme to target in the campaign

• MCC table through the MCC to allow for the selection of which Merchant Type to target in the campaign

• Shopping Centre table through the Centre ID to allow for the selection of which Shopping centre to target in the campaign

• Terminal through the AID (Advertec ID) this is the main link between the two sections and over this link a decision tree needs to choose which campaigns best suit the terminal

[00119] Fields:

• Campaign ID - is the Identifier for people to find this campaign

• Start Date - start of the campaign and allows for the campaign to only become active on/after this date

• Finish Date - end of the campaign and allows for the campaign to only become de-active on/after this date

• Advertiser ID - allows for the selection of the advertiser to be billed for the campaign and access control to the campaign as only people approved for that advertiser will be able to access the campaign

• Number of Guaranteed views - advertisers will be able to purchase guaranteed views for a given criteria and this sets the number they have purchased. These views will need to be recorded in the Campaign Counter table and this reduced for each guaranteed view delivered

• AID - The unique identifier for a terminal

• Premium Account - Does the advertiser have a premium account, this will allow for premium functions like the guaranteed views

• Price per view - Price per view the advertiser will be paid

• Price per click - Price per click the advertiser will be paid

• ADID - allows for the selection of the Advert to be used in the campaign from the table with all adverts stored

• Target time of day - the targeted time of day for the campaign (one selection may be all)

• Card Type - the targeted card type for the campaign (one selection may be all)

• Scheme Type - the targeted scheme for the campaign (one selection may be all)

• MCC - the targeted Merchant Type for the campaign (one selection may be all)

• Acquiring bank -

• Centre ID - the targeted shopping centre for the campaign (one selection may be all)

• Post Code - the targeted area for the campaign (one selection may be all)

• Bank ID - if they are a Bank this will reduce the options for Acquiring Bank as banks can only advertise on their own fleet.

Advertisements

[00120] Background: This is the table where all advertisements are stored and in all the types of image. The flow of an advert and the subsequent pages are all designed and controlled from this table.

[00121] Key Links: This table links to the:

• Ad Campaign table through the ADID to allow for the selection of which advert to target in the campaign • Card Holder engagement table through the ADID to allow for the storage of Mobile numbers and email addresses collected by an advert. These are then sent to advertisers at predetermined times to allow the advertiser to contact the Card Holder.

[00122] Fields:

• ADID - is the key Identifier for an Advert and used to track everything about the Advert

• Mobile Number - are the mobile numbers that are entered by card holders for future information about this advert

• Email Address - is the email address cardholders SMS to us for further information on the Advert.

Advertiser

[00123] Background: This table is about identifying all advertisers, shown as

Advertiser 125 on Figure 1, and their key information.

[00124] Key Links: This table links to the:

• Ad Campaign table through the Advertiser ID to allow for an advertiser to be able to see all campaigns they have.

• Advertiser account table through the Advertiser ID to allow for tracking of the advertisers account balance

[00125] Fields:

• Advertiser ID - is the key identifier for advertisers

• Advertiser Name - is the corporate name of the advertiser

• Billing Name - is corporate name for billing, this could be the agency or a division of the advertiser

• Billing Address - is the billing address for the advertiser

• Advertiser Contact Name - the contact' s name at the advertiser or agency

• Advertiser Contact Phone - the contact' s phone at the advertiser or agency

• Advertiser Contact Email - the contact's email at the advertiser or agency

• Advertiser Financial Controller Name - the name of the financial controller at the advertiser or agency for billing and payment issues

• Advertiser Financial Controller Phone - the phone number of the financial controller at the advertiser or agency for billing and payment issues

• Advertiser Financial Controller Email - the email of the financial controller at the advertiser or agency for billing and payment issues

• Advertec Sales ID - the ID for the sales person within Advertec responsible for this advertiser

• Advertec Sales Contact - the ID would bring up the name from the Sales person table on selection of the Sales ID

Advertiser Account

[00126] Background: this table keeps track of all financial transactions from or to the customer. It will show the history and current status of the account for an advertiser.

[00127] Key Links: Advertiser table through the Advertiser ID to allow for tracking of the advertisers financial transactions.

[00128] Fields:

• Advertiser ID - is the key identifier for advertisers

• Amount deposited - tracks all deposits by amount and date/time for the advertiser

• Campaign ID allocation - is the amount allocated to a campaign ID

• Campaign Debit - tracks the amount debited for each view/click by amount and date/time

• Advertisers balance - is the calculation of amount deposited - campaign debits

Sales People

[00129] Background: this table is used to track all the sales people and there performance against targets. [00130] Key Links: Advertiser Table through the Advertec Sales ID to allow contacts and account performance information to be linked to individual sales people.

[00131] Fields:

• Advertec Sales ID - the ID for the sales person within Advertec responsible for a sales target to advertisers

• Name - is the name of the sales person

• Address - is the address of the sales person's office

• Phone - is the phone number of the sales person

• Email - is the email address of the sales person

• Advertisers - is a list of the advertisers assigned to the sales person

• Quarterly Sales Target - is the current periods sales target

• Annual Sales Target - is the overall annual sales target for the sales person

Card Holder Details

[00132] Background: the table is a list of the different card types and scheme types from the BIN (the first 8 digits on the card) to allow the advertisers to target card types or Scheme types in campaigns.

[00133] Key Links: Ads Campaign table through the Card type and Scheme

Type fields.

[00134] Fields:

• Bin - is the first 8 digits assigned to a card number and are unique to a bank and scheme.

• Card type - is the bank card type that uses a particular BIN

• Scheme type - is the range of of BIN's assigned to a scheme (i.e. Visa, Mastercard, AMEX, etc)

Campaign Counter

[00135] Background: this tables role is to monitor the performance of a campaign and allow the tracking of data that can be used for reporting to a sales person or the advertisers.

[00136] Key Links: Ads Campaign table through the Campaign ID the track the performance of the campaign.

[00137] Fields:

• Ads Campaign ID - is the identifier of the ad campaign

• General Views Counter - counts the number of times the advert is viewed not under the guaranteed views scheme

• Times clicked - counts the number of times the advert is clicked for more information

• Guaranteed Views Counter - counts the number of times the advert is viewed under the guaranteed views scheme

• Time of general view - records the time of each view of the advert

• time of clicked - records the time of each click of the advert

• Time of guaranteed view - records the time of each guaranteed view of the advert

• post code of general view - records the postcode of the terminal of each view of the advert

• Post code of the clicked - records the postcode of the terminal of each click of the advert

• Postcode of the garneted view - records the postcode of the terminal of each view of the advertguaranteed

• MCC of the general view - records the MCC of the terminal of each view of the advert

• MCC of the clicked - records the MCC of the terminal of each click of the advert

• MCC of the guaranteed view - records the MCC of the terminal of each guaranteed view of the advert

• Shopping centre of the general view - records the shopping centre of the terminal of each view of the advert

• shopping centre of the clicked - records the shopping centre of the terminal of each click of the advert

• shopping centre of the guaranteed view - records the shopping centre of the terminal of each guaranteed view of the advert

• acquiring bank of the general view - records the acquiring bank of the terminal of each view of the advert

• acquiring bank of the clicked - records the acquiring bank of the terminal of each click of the advert

• acquiring bank of the guaranteed view - records the acquiring bank of the terminal of each guaranteed view of the advert

Advert Counter

[00138] Background: this tables role is to monitor the performance of an

Advert across a number of campaigns and allow the tracking of data that can be used for reporting to a sales person or the advertisers.

[00139] Key Links: Ads table through the ADID to track the performance of an advert.

[00140] Fields:

• ADID - is the identifier of the adverts

• Time of general view - records the time of each view of the advert

• time of clicked - records the time of each click of the advert

• post code of general view - records the postcode of the terminal of each view of the advert • Post code of the clicked - records the postcode of the terminal of each click of the advert

Card Holder Engagement

[00141] Background: this table is to record the contact details of the Card Holders that what more information about the advert.

[00142] Key Links: Ads table through the ADID to track the contact details for the SMS communication application to use.

[00143] Fields:

• ADID - is the identifier of the adverts • Mobile Number - the cardholders mobile number for the SMS communication application to use for the more information script

• Email Address - the cardholders email address for the SMS communication application to use for the more information script.

Terminal Section

[00144] Referring now to Figure 9, the terminal section of the database is used to identify the terminal and track details of each of the terminals. This information on the terminal will be used by the advertising application to choose the best advertisements for the terminal.

Terminal

[00145] Background: The Terminal table is the main table for this section and tracks the Individual terminals and their current characteristics. This table will be a very large table and a complex table to maintain and archive.

[00146] Key Links: Merchant table through the MID to track the Merchant details as some merchants will have opted out and others only want their own adverts on their terminals.

• Terminal Type table through the terminal type to track what capability this terminal has MCC table through the MCC to track the merchants industry as the advertisers MCC and the merchants MCC cannot be the same.

• Shopping centre table through the centre ID to track the shopping centre the terminal is located in.

• Bank table through the Bank ID to track the acquiring bank to allow for bank advertiser control and payment management for the bank.

[00147] Fields: • TID - is the bank unique terminal identifier and how the bank will identify each individual terminal in their fleet

• MID - is the bank unique merchant identifier and how the bank will identify each individual merchant in their fleet

• AID - is a unique identifier by Advertec, which is made of the XOR of the TID and MID and how the record is managed within the terminal section

• Terminal Type - is an identifier of the type of terminal as different terminals have different spec and can handle different

• SID - is only used by 1 bank and the rest do not use it, it is a unique store identifier for Westpac

• Post code - is the postal code for the area that the terminal is currently in

• Centre ID - is a unique identifier from the shopping centre table that indicates the shopping centre that the terminal is in.

• MCC - is a globally used identifier that indicates what industry and segment the merchant is in.

• Bank ID - is an identifier to indicate the acquiring bank for the terminal and is used to make sure the bank advertisers only show on their own terminal fleet.

Merchant

[00148] Background: this table is all the merchant details including contact details, MCC, acquiring bank, types of adverts they preclude from there terminals, if they have opted out of the service. Not all fields will be avalible for all merchants in this table.

[00149] Key Links:

• Terminal table through the MID to track the Merchant details as some merchants will have opted out and others only want their own adverts on their terminals.

• Ad campaign table through the MCC to advertisers to select the MCC they are and the MCC they want to target [00150] Fields:

• Name - Is the name of the merchant

• Head Office Address - is the head office address for postage

• Head Office Contact - is the contact person at the merchant head office

• Head Office Contact Phone - is the contact person's phone number at the merchant head office

• Head Office Email - is the contact person's emails at the merchant head office

• MCC - is a globally used identifier that indicates what industry and segment the merchant is in

• Acquiring Bank - is the acquiring bank that the merchant uses, this is so we know which bank to talk to about merchants.

• Types of Ads - is a list of advert types that the merchant will not allow, one option is that they only allow their own adverts.

• Opt Out - is this is selected then NO adverts will show on terminals in this merchant

Terminal Type

[00151] Background: the terminal type table is because different terminal types will have different specs and some adverts will only run on terminals with a special spec i.e. does the terminal type have a touch screen.

• Key Links: Terminal table through the terminal type to identify the characteristics of an individual terminal

• Bank table through the Bank ID to allow for the Banks Payment type to be taken into account in the terminal type

[00152] Fields: • Terminal Type - is an identifier of the type of terminal as different terminals have different spec and can handle different

• Terminal type ID - is an alpha numeric identifier for a terminal type

• Communication types - the types of comms available on this type of terminal type i.e. PSTN, IP, Wifi, 3G, 4G

• Display specs - this is the screen size, resolution, touch screen, colour

• Bank ID - This is the identifier for the bank as many banks may use the same hardware but different comms or payment software

• Bank Payment application - each bank will always have a different payment application but some banks will have multiple payment applications for the same hardware.

• Advertising VAS - This will show the Advertising application and version that should be used on this terminal type

Bank

[00153] Background: This table will be the key table for tracking relationship with the banks, it will be used for contacts, contract management and payment of fees to the bank.

[00154] Key Links: Bank table through the Bank ID to track the acquiring bank to allow for bank advertiser control and payment management for the bank.

[00155] Fields:

• Banks Name - The resisted Bank Name

• Bank' s contact Name - The Bank' s main contact

• Bank' s Contact Phone - The Bank' s main contact

• Bank's Contact Email - The Bank's main contact

• Contract Number - this is for information to allow everyone to see which agreement is being used in calculating the payments to the bank • Agreed fees with the Bank - This is the agreed fee payable to the bank

• Outstanding Bill - this is the outstanding invoice from the bank

• Billing Period - the is the payment terms agreed with the bank

Shopping Centre

[00156] Background: This table is to allow the terminal to be isolated by its shopping centre and to allow for advertising to be targeted by shopping centres.

[00157] Key Links:

• Terminal table through the centre ID to track the shopping centre the terminal is located in.

• Ad Campaign table through the centre ID to allow advertisers to select the shopping centre the terminal is located in.

[00158] Fields:

• Centre ID - is the unique identifier for each shopping centre

• Centre Management - large companies manage most shopping centres and that is what this field is for i.e. Westfield's

• Centre Name - is the name of the actual centre .i.e. Erina Fair (which is managed by Westfield's)

• Centre Address - the physical address for the shopping centre

• Centre Management contact name - the name of the contact for this centre

• Centre Management Contact Phone - the phone number of the contact for this centre

• Centre Management Email - the email of the contact for this centre.

[00159] Advantageously, there has been described a payment terminal, method, system and software applications for displaying a targeted advertisement to a user. In particular, there is provided a method for displaying a targeting advertisement on a payment terminal in which the advertisement is displayed on the terminal and within the payment transaction period (the period in which the payment terminal is awaiting transaction authorisation data from a banking system).

[00160] In particular, the method makes use of the payment transaction period, which is typically not utilised, and makes use of transaction profile data (such as a Terminal Identification, Merchant Identification, Time of Date, Card type and Scheme Type) to select and display one or more particular advertisements to the user based on the transaction profile data. This allows targeting of the advertisement directly during the transaction to a user.

[00161] Further advantageously, the method includes displaying prompts to collect and record user information (such as phone numbers) and includes sending this user information to a server configured to take further actions such as sending text messages to the user with further advertising, promotion offers or requesting further information such as an email address or the like.

[00162] The method, system and software applications disclosed herein provide an advantageous technical solution for payment terminal advertising as the payment terminal has stored advertisements that are selected by the payment terminal during the transaction "intra-transaction", preferably, without communication to the external advertising server during the transaction. This ensures that security is maintained between payment terminal and the bank system during the transaction. However, outside the transaction period, the payment terminal may communicate with the external advertising server to, for example, update the advertisements stored on the payment terminal and communicate captured user data to the server. The advertisements may be selected for display at least partially based on transaction profile data acquired during the transaction thereby allowing specific targeting of advertisements during the transaction period.

[00163] The method, system and software applications disclosed herein provide a benefit a terminal operators (merchants) and also terminal providers (mainly banks) to generate revenue from advertisers who may wish to display advertisements. The user may also benefit from special offers and the ultimate reducing of overhead of the terminal operator and the terminal providers that may be passed on as savings to the user.

[00164] Throughout this specification and the claims which follow, unless the context requires otherwise, the word "comprise", and variations such as "comprises" and "comprising", will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.

[00165] The reference in this specification to any known matter or any prior publication is not, and should not be taken to be, an acknowledgment or admission or suggestion that the known matter or prior art publication forms part of the common general knowledge in the field to which this specification relates.

[00166] While specific examples of the invention have been described, it will be understood that the invention extends to alternative combinations of the features disclosed or evident from the disclosure provided herein.

[00167] Many and various modifications will be apparent to those skilled in the art without departing from the scope of the invention disclosed or evident from the disclosure provided herein.

Claims

The claims defining the Invention are as follows:

1. A method for advertising on a payment terminal having a screen, the method including:

Receiving, at the payment terminal, a start transaction input to provide transaction authorisation data;

Sending, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal;

Displaying, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and

Receiving, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertisement display period.

2. The method according to claim 1, wherein the start transaction input includes the payment terminal reading a payment instrument communicated with the payment terminal.

3. The method according to claim 2, wherein the start transaction input includes the payment terminal receiving a code associated with the payment instrument.

4. The method according to claim 1, wherein the advertisement display period includes a minimum display time, and the method includes the step of:

Timing, at the payment terminal, the advertisement display period, and wherein on receipt of the return authorisation data the payment terminal is configured to terminate the advertisement display period if the minimum display time has elapsed.

5. The method according to claim 4, wherein the minimum display time is about 1 to 10 seconds.

6. The method according to claim 4, wherein the minimum display time is about 3 seconds.

7. The method according to any one of the previous claims, wherein the method includes the advertisement displaying a prompt configured to receive prompt input data from a user, and wherein payment terminal is configured to receive and at least temporarily store the prompt input data.

8. The method according to claim 7, wherein the prompt input data includes at least one of a click, a selection, personal contact information, an identifier, a number, a word, a code, a reward scheme identifier, a telephone number and an email address.

9. The method according to claim 7, wherein the methsod includes the step of:

Sending, via the payment terminal, the prompt input data to an external server.

10. The method according to any one of claims 1 to 6, wherein the method including the step of:

Displaying, on the screen, a prompt associated with the advertisement during the advertisement display period, the prompt being configured to receive prompt input data.

11. The method according to claim 10, wherein the method includes the step of:

Receiving, the prompt input data, and wherein upon receipt of the prompt input data the advertisement display period is extended for a further period.

12. The method according to claim 11, wherein the further period is terminated at least one of a user inputted termination and a maximum elapsed time

13. The method according to claim 11, wherein the method includes the step of: On receipt of the prompt input data, displaying on the screen, at least one of a further advertisement, information, a screen view and a further prompt to capture further prompt data.

14. The method according to claim 13, wherein the further prompt is configured to capture user inputted data including at least one of a click, a selection, personal contact information, an identifier, a number, a word, a code, a rewards scheme identifier, a telephone number and an email address.

14. The method according to claim 1, wherein the method includes the steps of:

Determining, via a processor of the payment terminal, the advertisement to display, the payment terminal being configured to select the advertisement from a plurality advertisements stored on memory of the payment terminal based on a selection criteria.

15. The method according to claim 14, wherein the step of determining the advertisement to display includes:

Comparing, via the processor, transaction profile data associated with the transaction with advertisement profile data associated with each of the plurality advertisements to determine a selection index, and

Selecting, via the processor, the advertisement to display based on the selection index that best matches with the selection criteria.

16. The method according to claim 14, wherein the selection index is calculated from values associated with at least one of a terminal identifier, time of day, card type, merchant type, merchant name, merchant location and bank identifier.

17. The method according to claim 15, wherein the transaction profile data includes at least one of a terminal identifier, time of day, card type, merchant type, merchant name, merchant location and bank identifier.

18. The method according to claim 15, wherein the start transaction input includes the payment terminal reading a payment instrument, and wherein the payment terminal is configured to form the transaction profile data so as to include payment instrument data acquired from reading the payment instrument.

19. The method according to claim 18, wherein the payment instrument data includes at least one of a payment scheme, issuing bank, card identifier and card type.

20. The method according to claim 14, wherein the method includes the step of: receiving at the payment terminal, advertisement data representing the plurality advertisements.

21. The method according to claim 20, wherein each of the plurality of advertisements of has associated advertisement profile data, and wherein the payment terminal is configured to compare the transaction profile data with the advertisement profile data to determine the advertisement to display.

22. The method according to claim 1, wherein the method includes the step of:

Determining, at the payment terminal, if the payment terminal is in at least one of a transaction period including the advertisement display period and an idle period, wherein:

In the transaction period, the payment terminal is configured to restrict communication between an external advertising server and the payment terminal; and

In the idle period, the payment terminal is configured to communicate with the external advertising server so as to at least one of receive advertisement data and send captured transactional data.

23. A computer software application for operation on a payment terminal, the software configured to operate a method as defined in any one of the previous claims.

24. A payment terminal configured to operate a method as defined in any one of claim 1 to 21.

25. A system including a payment terminal as defined in claim 24 and a server configured to communicate with the payment terminal, the server being configured receive user data inputted to the payment terminal during the advertisement display person, and send further advertising data to the user associated with the user data.

26. The system according claim 25, wherein the user data includes an identifier linkable to the user such as a number, code, rewards scheme identifier, account number, telephone number, email address, and wherein the server is configured to send the further advertising data to the user using the identifier.

27. A system including a payment terminal having a screen and a server in communication with the payment terminal, the system being configured to:

Receive, at the payment terminal, advertising data from the server;

Receive, at the payment terminal, a start transaction input to provide transaction authorisation data;

Send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal;

Displaying, on the screen of the payment terminal, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and

Receiving, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of receipt of the return authorisation data and expiry of the advertising display period;

Sending, to the server, data representing the advertisement displayed during the advertisement display period.

28. A system for targeted advertising including a payment terminal having a screen and a server in communication with the payment terminal, the system being configured to:

Receive, at the payment terminal, advertisement data from the server;

Receive, at the payment terminal, a start transaction input to provide transaction authorisation data; Send, from the payment terminal, the transaction authorisation data to an external authorisation system, the external authorisation system being configured to provide return authorisation data to the payment terminal;

Determine, via a processor of the payment terminal, an advertisement to display, the payment terminal being configured to select the advertisement from advertisement data representing a plurality of advertisements stored based on an advertisement selection criteria;

Display, on the screen of the payment terminal, the selected advertisement having an input prompt for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data;

Receive, at the payment terminal, user data inputted in response the input prompt;

Sending, to the server, the user data representing any user data inputted and advertisement data identifying the selected advertisement displayed.

29. A computer readable medium for a payment terminal having a screen, the computer readable medium being configured to operate the payment terminal to:

Display, on the screen, an advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; and

Receive, at the payment terminal, the return authorisation data, the payment terminal being configured to terminate the advertisement display period upon at least one of the receipt of the return authorisation data and expiry of the advertisement display period.

30. A payment terminal having a screen, the payment terminal being configured by software to:

Receive, at the payment terminal, the return authorisation data, and

Terminate, the advertisement display period upon at least one of receipt of the return authorisation data and expiry of a minimum elapsed time of the advertisement display period.

31. A payment terminal having a screen, the payment terminal being configured by software to:

Read, via the payment terminal, a payment instrument communicable with the payment terminal thereby providing payment instrument data;

Determine, via a processor of the payment terminal, an advertisement to display, the payment terminal being configured to select the advertisement from advertisement data representing a plurality of advertisements stored on memory of the payment terminal, the selection being at least partially based on a comparison between transaction profile data including payment instrument data and advertisement profile data associated with the advertisement data;

Display, on the screen, the selected advertisement for an advertisement display period, the advertisement display period being initiated by at least one of receiving the start transaction input and sending the transaction authorisation data; Time, via the processor of the payment terminal, an elapsed time associated with the advertisement display period;

Receive, at the payment terminal, the return authorisation data, and

Terminate, the advertisement display period upon at least one of receipt of the return authorisation data and expiry of a minimum elapsed time of the elapse time associated with the advertisement display period.