Field of the Invention

The present invention relates to payment handling apparatus which is operable to effect payment between a first party and a second party. The present invention also relates to a payment handling method which effects payment between a first party and a second party.

Background Art

Arrangements for making payments by way of a mobile device are known.

According to one longer used approach, the vendor has apparatus comprising a handheld device such as a smartphone and a credit/debit card reader. The handheld device and the credit/debit card reader are in data communication and normally wireless data communication with each other such as by way of Bluetooth. Payment for goods or services is accomplished by the vendor entering the transaction details including the cost of the goods or services into the apparatus before the purchaser's credit/debit card is read by the credit/debit card reader and the purchaser authorises payment by entering a PIN associated with the credit/debit

More recently approaches to making payments without operative use of a

credit/debit card have been introduced. One such approach involves the purchaser entering credit/debit card data into the vendor's mobile device or into a client process running on the purchaser's mobile device which is controlled over the Internet by a vendor process. This approach relies on underlying card payment infrastructure. A further known approach involves the purchaser logging into his banking application before the vendor passes a code containing payment details including the vendor's banking details to the purchaser. The purchaser then enters the code into the banking application which is then operative by way of data communication with the vendor's bank server to effect payment to the vendor such as by way of a faster Automated Clearing House (ACH) payment.

The present inventors have appreciated the above described known approaches to have shortcomings. The present invention has been devised in light of this appreciation. It is therefore an object for the present invention to provide improved payment handling apparatus which is operable to effect payment between a first party and a second party. It is a further object for the present invention to provide an improved payment handling method which effects payment between a first party and a second party.

Statement of Invention

According to a first aspect of the present invention there is provided payment handling apparatus which is operable to effect payment between a first party and a second party, the payment handling apparatus comprising:

a first party's apparatus which is operable to send a payment request to a payment handling establishment;

the payment handling establishment being configured to send payment identification data to the first party's apparatus in dependence on receipt of the payment request; a second party's apparatus configured to receive the payment identification data from the first party's apparatus; and

a user interface function comprised in the first party's apparatus, the user interface function being configured to provide for operation of the first party's apparatus to send the payment request in dependence on user interaction with the user interface function,

the user interface function being operative to display a first graphical user interface which is superimposed over a second graphical user interface displayed by another function comprised in the first party's apparatus, the first graphical user interface being transparent.

The payment handling apparatus is operable to effect payment between a first party and a second party. The payment handling apparatus comprises a first party's apparatus, such as a purchaser's mobile device, which is operable to send a payment request to a payment handling establishment. The payment handling apparatus comprises the payment handling establishment, which is configured to send payment identification data to the first party's apparatus in dependence on receipt of the payment request. The payment identification data may be unique to the present payment. The payment handling apparatus further comprises a second party's apparatus, such as a vendor's apparatus, configured to receive the payment identification data from the first party's apparatus.

The payment handling apparatus yet further comprises a user interface function comprised in the first party's apparatus, the user interface function being configured to provide for operation of the first party's apparatus to send the payment request in dependence on user interaction with the user interface function. The user interface function is operative to display a first graphical user interface which is superimposed over a second graphical user interface displayed by another function comprised in the first party's apparatus, the first graphical user interface being transparent. The first graphical user interface may be configured in respect of transparency such that graphic content of the first graphical user interface and graphic content of the second graphical user interface underneath the first graphical user interface may be seen by the user at the same time. Sending of the payment request may initiate effecting payment between the first party and the second party. The user interface function may be comprised in each of the first party's apparatus and the second party's apparatus. Therefore and as described in more detail below either one of the first party's apparatus, e.g.

purchaser's apparatus, and the second party's apparatus, e.g. vendor's apparatus, may be operative to initiate effecting payment. The user interface function may thus be configured to provide for making a payment and for receiving a payment.

The user interface function may be comprised in an operating system of the first party's apparatus. The operating system may be configured to superimpose the first graphical user interface over any other graphical user interface displayed by the operating system and more specifically over any other graphical user interface displayed by another function comprised in the first party's apparatus.

The user interface function may be comprised in an App (i.e. application) comprised in the first party's apparatus. The App may, for example, be a banking application which is otherwise of known form and function. Alternatively the first party's apparatus may comprise a library with the library comprising the user interface function. The library may be comprised in the App.

The user interface function may be configured to be operative as a wrapper for an App. The App may, for example, be a banking application which is otherwise of known form and function.

The payment handling apparatus may be configured and more specifically the first party's apparatus may be configured for user interaction with the user interface function by way of manual operation. The first graphical user interface may comprise at least one operable area which when touched by a user provides for user interaction with the user interface function. More specifically the first party's apparatus, for example a smartphone, may comprise a touchscreen on which the first graphical user interface is displayed, the touchscreen providing for actuation when the at least one operable area is touched by a user. Alternatively or in addition, the first party's apparatus may comprise a mechanically operable keyboard or keypad, the first party's apparatus being configured to provide for user interaction with the user interface function by way of manual operation of the keyboard or keypad. Alternatively or in addition, the first party's apparatus may be configured for voice actuation, such as by way of a microphone and voice analyser comprised in the first party's apparatus. Furthermore, the first party's apparatus may be

configured to provide for user interaction with the user interface function in

dependence on voice actuation. The second party's apparatus is configured to receive the payment identification data from the first party's apparatus. The first party's apparatus therefore may be configured to send the payment identification data to the second party's apparatus. The payment handling apparatus may comprise a communications channel whereby the payment identification data may be sent from the first party's apparatus to the second party's apparatus. The communications channel may comprise a data network, such as the Internet. The first party's apparatus and the second party's apparatus may be configured for sending of the payment identification data from the first party's apparatus to the second party's apparatus by way of software and more specifically an App running on each party's apparatus. The same App may be running on the first party's apparatus and the second party's apparatus. The App may be a social media App, such as Facebook, Facebook Messenger or WhatsApp.

The payment handling apparatus may be configured for communication of the payment request and the payment identification data between the first party's apparatus and the payment handling establishment by way of a payment handling establishment data network. The payment handling apparatus may comprise the payment handling establishment data network. The payment handling establishment data network may comprise the Internet. The payment handling apparatus may be configured such that the payment handling establishment data network is operable in accordance with known practice such as known practice for secure payment handling over the Internet. The payment handling apparatus may be configured for entry into the payment handling apparatus of an amount to be paid. The payment handling apparatus may be configured for entry of the amount to be paid into the first party's apparatus. More specifically the first party's apparatus may be configured, such as by way of a mechanically operable keypad or a touchscreen, for entry of the amount to be paid by a user of the first party's apparatus. Alternatively or in addition, the second party's apparatus may be configured for entry of the amount to be paid by a user of the second party's apparatus. The amount to be paid may be entered manually or electronically into the second party's apparatus. The second party's apparatus may be configured accordingly, such as by way of mechanically operable keypad or a touchscreen or by way of a transceiver which provides for wireless reception of payment data. Thereafter the second party's apparatus may be configured to convey the entered amount to be paid to the first party's apparatus. The amount to be paid may be entered before the payment request is sent from the first party's apparatus. Alternatively, the amount to be paid may be entered after the payment request is sent from the first party's apparatus.

As described above the second party's apparatus is configured to receive the payment identification data from the first party's apparatus. The second party's apparatus may be operative to effect payment either to the second party or from the second party.

Where the second party's apparatus is operative to effect payment to the second party, e.g. where the second party is a vendor, the second party's apparatus may be operative to form a payment message comprising the payment identification data and an amount to be paid. The second party's apparatus may be further operative to convey the payment message to a second party's bank server. The second party's bank server may be comprised in the payment handling apparatus. The second party's bank server may be operative to make payment from a first party's bank server to the second party's bank server in dependence on the payment message. The first party's bank server may be comprised in the payment handling apparatus. Communication between the first party's bank server and the second party's bank server may be by way of a secure communication channel of known form and function. The payment identification data may suffice for identifying a bank account held by a user of the first party's apparatus. Otherwise, bank account data which provides for identification of a bank account held by a user of the first party's apparatus may be sent from the first party's apparatus to the second party's apparatus. The bank account data may be sent with the payment identification data to the second party's apparatus.

Where the amount to be paid is entered after the payment request is sent from the first party's apparatus, the second party's apparatus may be operative to form a payment approval request comprising the payment identification data and an amount to be paid. The second party's apparatus may be further operative to convey the payment approval request to the first party's apparatus. The first party's apparatus may be operative to convey payment approval data to the second party's apparatus in dependence on receipt of the payment approval request and user interaction with the first party's apparatus. User interaction with the first party's apparatus may be under control of the user interface function and more specifically may be by way of user interaction with the first graphical user interface. The first graphical user interface may be operative to invite the user to one of approve and decline making payment and to respond to user interaction thereupon. The second party's apparatus may be operative to convey the payment approval request to the first party's apparatus before the payment message is conveyed to the second party's bank server. The payment handling apparatus may comprise a communications channel whereby the payment approval request and the payment approval data may be sent between the first party's apparatus and the second party's apparatus. As described above in more detail, the communications channel may comprise a data network, such as the Internet. Furthermore, the first party's apparatus and the second party's apparatus may be configured for communication by way of software and more specifically an App running on each party's apparatus. The App may be a social media App, such as Facebook, Facebook Messenger or WhatsApp. Where the amount to be paid is entered before the payment request is sent from the first party's apparatus, the payment identification data may be sent from the first party's apparatus with the amount to be paid. There may therefore be no need to form a payment approval request as described above in view of approval to pay being implicit in the sending of the payment identification data with the amount to be paid from the first party's apparatus.

Where the second party's apparatus is operative to effect payment from the second party, e.g. where the second party is a purchaser, the second party's apparatus may be operative to form a payment message comprising the payment identification data and an amount to be paid. The second party's apparatus may be further operative to convey the payment message to a second party's bank server. The second party's bank server may be operative to make payment from the second party's bank server to a first party's bank server in dependence on the payment message. As described above, communication between the first party's bank server and the second party's bank server may be by way of a secure communication channel of known form and function. The payment identification data may suffice for identifying a bank account held by a user of the first party's apparatus. Otherwise, bank account data which provides for identification of a bank account held by a user of the first party's apparatus may be sent from the first party's apparatus to the second party's apparatus. The bank account data may be sent with the payment identification data to the second party's apparatus.

Where the amount to be paid is entered before the payment request is sent from the first party's apparatus, approval to pay may be implicit in the forming of the payment message by the second party's apparatus. Likewise, where the amount to be paid is entered after the payment request is sent from the first party's apparatus, approval to pay may be implicit in the forming of the payment message. The user interface function may be comprised in each of the first party's apparatus and the second party's apparatus. The payment handling apparatus may comprise plural second party's apparatus. The payment handling apparatus may be configured to effect payment from the first party's apparatus to each of the plural second party's apparatus or to the first party's apparatus from each of the plural second party's apparatus. The payment handling apparatus may be configured to use the payment identification data received by the first party's apparatus for a payment effected between the first party's apparatus and each second party's apparatus. More specifically the first party's apparatus may be configured to send the payment identification data to each of the plural second party's apparatus.

The payment handling establishment may be a clearing bank, a credit/debit card handling establishment, an acquiring bank, etc. The payment handling

establishment may be comprised in a bank server, such as a purchaser's bank server. The payment handling establishment may, for example, be a credit card handling establishment such that payment is made on behalf of a purchaser with actual settlement of the sum being paid by the purchaser at a later time.

The payment handling apparatus may further comprise a second party's bank server, such as a vendor's bank server. The payment handling apparatus may further comprise a first party's bank server, such as a purchaser's bank server. The payment handling apparatus may be configured such that payment may be effected by way of communication between the first party's bank server and the second party's bank server in dependence on receipt of the payment message from the second party's apparatus. Payment may be effected in accordance with known practice.

At least one of a first party's bank server and a second party's bank server may comprise the payment handling establishment. The payment handling apparatus may be configured such that each of plural first party's apparatus or second party's apparatus engages a different payment handling establishment at any one time.

The payment handling apparatus may comprise at least one of plural first party's bank servers and plural second party's bank servers. Where the payment handling apparatus comprises bank server apparatus the first and second party's apparatus and the bank server apparatus may be at locations spaced apart from each other. Where the payment handling apparatus comprises first party's bank server apparatus and second party's bank server apparatus, the first party's bank server and the second party's bank server may be at locations spaced apart from each other.

At least one of the first party's apparatus and the second party's apparatus may be a mobile device such as a smartphone. The payment handling apparatus may comprise computing apparatus, such as a server, which comprises the payment handling establishment.

According to a second aspect of the present invention there is provided a payment handling method which effects payment between a first party and a second party, the method comprising:

operating a first party's apparatus to send a payment request to a payment handling establishment;

receiving payment identification data in the first party's apparatus in

dependence on receipt of the payment request by the payment handling

establishment; and

sending the payment identification data from the first party's apparatus to the second party's apparatus; and

in which the step of operating the first party's apparatus is in dependence on a user interacting with a user interface function comprised in the first party's apparatus, the user interface function being operative to display a first graphical user interface which is superimposed over a second graphical user interface displayed by another function comprised in the first party's apparatus, the first graphical user interface being transparent. Embodiments of the second aspect of the present invention may comprise one or more features of the first aspect of the present invention. According to a third aspect of the present invention there is provided a computer program comprising program instructions for causing computer apparatus to perform the method according to the second aspect of the present invention. More specifically, the computer program may be at least one of: embodied on a record medium; embodied in read only memory; stored in a computer memory; and carried on an electrical carrier signal. Further embodiments of the third aspect of the present invention may comprise one or more features of the first aspect of the present invention. According to a fourth aspect of the present invention there is provided a computer system comprising program instructions for causing computer apparatus to perform the method according to the second aspect of the present invention. More specifically the program instructions may be at least one of: embodied on a record medium; embodied in a read only memory; stored in a computer memory; and carried on an electrical carrier signal. Further embodiments of the fourth aspect of the present invention may comprise one or more features of the first aspect of the present invention.

According to a further aspect of the present invention there is provided payment handling apparatus which is operable to effect payment from a purchaser to a vendor, the payment handling apparatus comprising: a first party's apparatus which is operable to send a payment request to a payment handling establishment; the payment handling establishment which is configured to send payment identification data to the first party's apparatus in dependence on receipt of the payment request; a second party's apparatus configured to receive the payment identification data from the first party's apparatus; and a user interface function comprised in the first party's apparatus, the user interface function being configured to provide for operation of the first party's apparatus to send the payment request in dependence on user interaction with the user interface function.

Embodiments of the further aspect of the present invention may comprise one or more features of the first aspect of the present invention. Brief Description of Drawings

Further features and advantages of the present invention will become apparent from the following specific description, which is given by way of example only and with reference to the accompanying drawings, in which:

Figure 1 is a block diagram representation of payment handling apparatus according to the present invention;

Figure 2A is a flow chart representation of a method according to a first embodiment of the present invention; and

Figure 2B is a flow chart representation of a method according to a second embodiment of the present invention.

Description of Embodiments A block diagram representation of payment handling apparatus 10 according to the present invention is shown in Figure 1 . The payment handling apparatus 10 comprises a first party's client 12, a first party's bank server 14, a second party's client 16 and a second party's bank server 18. The first party's client 12 is a process operative on computing apparatus possessed by a first party, such as a tablet computer or more typically a smartphone where the first party is a purchaser, or a laptop computer, a tablet computer or a PC based till where the first party is a vendor. The second party's client 16 is a process operative on computing apparatus possessed by a second party, such as a laptop computer, a tablet computer or a PC based till where the second party is a vendor, or a tablet computer or more typically a smartphone where the second party is a purchaser. The first party's bank server 14 is comprised in first party's server apparatus operated by a payment processing authority such as a bank. Typically the first party's server apparatus has a distributed architecture. Likewise the second party's bank server 18 is comprised in second party's server apparatus operated by a payment processing authority such as a bank. Again the second party's server apparatus typically has a distributed architecture. Communication of data between the first party's client 12 and the first party's bank server 14 is by way of a computer network 20, such as the Internet or a metropolitan or wide area network 20, such as the Global System for Mobile Communications (GSM) or 4G network. Likewise communication of data between the second party's client 16 and the second party's bank server 18 is by way of a computer network 22, such as the Internet, or a metropolitan or wide area network 22, such as the Global System for Mobile Communications (GSM) or 4G network. Communication between the first party's bank server 14 and the second party's bank server 18 is by way of a communications link 24, for example a dedicated communications link or a computer network, such as the Internet. Under certain circumstances a dedicated

communications link is preferred on account of the greater level of security afforded in comparison to a more open Internet based communications link. Communication of data between the first party's client 12 and the second party's client 16 is by way of a wireless communication link 26 such as in accordance with the WiFi or

Bluetooth® standard. The first party's client 12 and the second party's client 16 is each configured by way of the same social media App, such as Facebook, Facebook Messenger or WhatsApp, for communication of data, as described in more detail below, between the first party's client 12 and the second party's client 16. Each of the first party's client 12 and the second party's client 16 comprises a user interface function which is operative, amongst other things, to display a user interface function graphical user interface which is superimposed over any other graphical user interface displayed by other functions comprised in the said party's client. The user interface function graphical user interface is transparent whereby the other graphical user interfaces may be seen by the user. The user interface function is configured, as described further below, to provide for operation of the said client's apparatus in respect of steps of effecting payment between the first party's client 12 and the second party's client 16. Operation of the said client's apparatus is in dependence on user interaction with the user interface function. In a first form of user interaction, the user interface function graphical user interface comprises operable areas which when touched by a user provides for user interaction with the user interface function. The operable areas are provided by way of a touchscreen which provides for actuation when touched by the user. In a second form of user interaction, the computing apparatus on which the said party's client operates comprises a mechanically operable keyboard or keypad. The computing apparatus is configured to provide for user interaction with the user interface function by way of manual operation of the keyboard or keypad. In a third form of user interaction, the computing apparatus on which the said party's client operates is configured for voice actuation, such as by way of a microphone and voice analyser comprised in the computing apparatus. In this form, the computing apparatus is configured to provide for user interaction with the user interface function in dependence on voice actuation. The user interface function is implemented according to one of three different approaches. According to a first approach, the user interface function is comprised in the operating system of the computing apparatus on which the said party's client operates. The operating system is configured to superimpose the user interface function graphical user interface over any other graphical user interface displayed by the operating system. According to a second approach, the user interface function is comprised in an App comprised in the first party's apparatus, the App being a banking application of known form and function. Considering this approach further, the App comprises a library which in turn comprises the user interface function.

According to a third approach, the user interface function is configured to be operative as a wrapper for an App, the App being a banking application of known form and function.

A method according to a first embodiment of the present invention will now be described with reference to Figure 1 and the flow chart representation of Figure 2A. According to the first embodiment the first party's client 12 is operative to purchase goods or services and the second party's client 16 is operative as a vendor of such goods or services. The method according to the first embodiment commences with the first party's client 12 being operative to form a payment request and to send the payment request to a payment handling establishment 32. The payment handling establishment is a clearing bank, such as comprises the first party's bank server 14, or a payment handling intermediary, such as credit/debit card handling establishment or PayPal®. Following receipt of the payment request, the payment handling establishment is operative to form a unique transaction code in the form of payment identification data and to send the payment identification data to the first party's client 12, 34. The first party's client 12 then sends the payment identification data to the second party's client 16, 36. Under certain circumstances the payment identification data is sufficient to identify the bank account of the user of the first party's client 12. Under other circumstances, the payment identification data is insufficient to identify the bank account held by the user of the first party's client 12. Therefore the first party's client 12 is operative to send with the payment

identification data bank account data which provides for identification of the bank account held by the user of the first party's client 12.

Following receipt of the payment identification data, the second party's client 16 is operative to form a payment approval request comprising the payment identification data and an amount to be paid. The amount to be paid is entered into computing apparatus on which the second party's client 16 operates manually by way of operation of a keyboard or keypad or electronically by way of near field wireless communication or scanning of a barcode or QR code. The second party's client 16 is then operative to send the payment approval request to the first party's client 12, 38. Following receipt of the payment approval request, the first party's client 12 is operative to invite the user of the computing apparatus running the first party's client 12 by way of the user interface function graphical user interface running on the user's computing apparatus to one of approve and decline making payment. The user of the computing apparatus running the first party's client 12 interacts

accordingly with the computing apparatus by one of the means described above to either approve or decline making payment 40. If the user approves making payment, the first party's client 12 is operative to send payment approval data to the second party's client 16, 42. Following receipt of the payment approval data, the second party's client 16 is operative to form a payment message comprising the payment identification data and the amount to be paid and to send the payment message to the second party's bank server 18, 44. The second party's bank server 18 is then operative to make payment from the first party's bank server 14 to the second party's bank server 18, 46. Payment is made in accordance with known practice in this regard. As described above, the amount to be paid is entered after the payment request is sent from the first party's client 12. In an alternative approach, amount to be paid is entered before the payment request is sent from the first party's client 12. According to this approach, the amount to be paid is entered by the vendor into computing apparatus operating the second party's client 16 as described above and then conveyed by wireless communication, such as near field communication, to the computing apparatus operating the first party's client 12. Alternatively, the purchaser himself or herself enters the amount to be paid into computing apparatus operating the first party's client 12 by means described above in respect of computing apparatus operating the second party's client 16. Thereafter the first party's client 12 obtains the payment identification data as described above and sends the payment identification data with the amount to be paid to the second party's client 16. There is therefore no need for the above described steps of forming and sending a payment approval request and sending payment approval data in view of approval to pay being implicit in the sending of the payment identification data with the amount to be paid from the first party's client 12.

A method according to a second embodiment of the present invention will now be described with reference to Figure 1 and the flow chart representation of Figure 2B. According to the second embodiment the first party's client 12 is operative as a vendor of goods or services and the second party's client 16 is operative as a purchaser of such goods or services. The method according to the second embodiment commences with the first party's client 12 being operative to form a payment request and to send the payment request to a payment handling

establishment 52 as per the first embodiment described above. Likewise and following receipt of the payment request, the payment handling establishment is operative to form a unique transaction code in the form of payment identification data and to send the payment identification data to the first party's client 12, 54. The amount to be paid is entered into computing apparatus on which the first party's client 12 operates manually by way of operation of a keyboard or keypad or electronically by way of near field wireless communication or scanning of a barcode or QR code. Then the first party's client 12 sends the payment identification data and the amount to be paid to the second party's client 16, 56. Under certain circumstances the payment identification data is sufficient to identify the bank account of the user of the first party's client 12. Under other circumstances, the payment identification data is insufficient to identify the bank account held by the user of the first party's client 12. Therefore the first party's client 12 is operative to send with the payment identification data bank account data which provides for identification of the bank account held by the user of the first party's client 12. Then the second party's client 16 is operative to form a payment message comprising the payment identification data and the amount to be paid and to send the payment message to the second party's bank server 18, 58. Irrespective of whether the amount to be paid is entered before or after the payment request is sent from the first party's apparatus, approval to pay is implicit in the forming of the payment message. Hence there is no need for the steps according to the first embodiment of forming and sending a payment approval request and sending payment approval data. Following receipt of the payment message, the second party's bank server 18 is operative to make payment from the second party's bank server 18 to the first party's bank server 18, 60. Payment is made in accordance with known practice in this regard. In another un-illustrated embodiment, the payment handling apparatus comprises plural second party's clients 16 with payment being made from the first party's client 12 to each of the second party's clients. According to this embodiment, the method proceeds according to the first embodiment wherein the same payment identification data is sent with an amount to be paid from the first party's client 12 to each of the second party's clients 16. The amount to be paid may differ from second party's client to second party's client. Each of the second party clients 16 is then operative to form a payment message and the payment handling apparatus is further operative to provide for payment to each of the second party clients 16 as described above with reference to the first embodiment.

In another un-illustrated embodiment, the payment handling apparatus comprises plural second party's clients 16 with payment being made to the first party's client 12 from each of the second party's clients. According to this embodiment, the method proceeds according to the second embodiment wherein the same payment identification data is sent from the first party's client 12 to each of the second party's clients 16. An amount to be paid is entered in each of the second party's clients. The amount to be paid may differ from second party's client to second party's client. Each of the second party clients 16 is then operative to form a payment message and the payment handling apparatus is further operative to provide for payment from each of the second party clients 16 as described above with reference to the second embodiment.