WO2016009198A1

WO2016009198A1 - Method and system for providing a payment service

Info

Publication number: WO2016009198A1
Application number: PCT/GB2015/052041
Authority: WO
Inventors: Ewan Cameron; Mahyad GILANI
Original assignee: Monitise Group Limited
Priority date: 2014-07-15
Filing date: 2015-07-15
Publication date: 2016-01-21
Also published as: GB201412538D0; GB2530007A

Abstract

A method and an electronic system providing a payment service is presented. The system comprises: a mobile computing device having a wireless communication interface for communicating with an electronic device over a short-range wireless communication link; the electronic device having a wireless communication interface for communication with the mobile computing device over a short-range wireless communication link; and an intermediary server configured as a gateway to records of at least one banking or payment organization. The mobile computing device and the electronic device cooperate wirelessly to generate a payment execution request indicating a requested payment between a user of the mobile computing device and an entity associated with the electronic device. The intermediary server is configured to receive the payment execution request from the mobile computing device or the electronic device and to transmit information to the at least one banking or payment organization based on the received payment execution request.

Description

METHOD AND SYSTEM FOR PROVIDING A PAYMENT SERVICE

FIELD OF THE INVENTION

[0001] This invention relates to providing payment services. In particular, the invention relates to electronic payment service using a mobile device.

BACKGROUND

[0002] This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present techniques, which are described and/or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

[0003] Many payment or remittance instruments currently exist and may be used to carry out a financial transaction between two or more parties. For example, payments may be made using cash, credit cards, debit cards, checks, electronic checks, and so forth.

[0004] Mobile devices, such as personal digital assistants and smartphones, have become increasingly popular and are now commonplace. It is a known idea to extend the functionality of these devices to carry out financial transactions. However, known attempts to do so are vulnerable to privacy breaches and place undesirable limitations on users and/or mobile devices.

[0005] It is desirable to extend the benefits of a mobile payment system to situations which a consumer can complete a financial transaction, whilst reducing or minimizing the exposure of personal data or sensitive information (such as their banking account or card details, for example) to the risk of fraud. It is also desirable to enable consumers who do not have debit or credit card to use such a method and/or system. SUMMARY

[0006] According to the invention, there is provided an electronic system providing a payment service, comprising: a mobile computing device having a wireless communication interface for communicating with an electronic device over a short-range wireless communication link; the electronic device having a wireless communication interface for communication with the mobile computing device over a short-range wireless communication link; and an intermediary server configured as a gateway to records of at least one banking or payment organization, wherein the mobile computing device and the electronic device cooperate wirelessly to generate a payment execution request indicating a requested payment between a user of the mobile computing device and an entity associated with the electronic device, and wherein the intermediary server is configured to receive the payment execution request from the mobile computing device or the electronic device and to transmit information to the at least one banking or payment organization based on the received payment execution request.

[0007] Embodiments may therefore provide for the implementation of a commercial transaction between the users of two devices linked by a short-range wireless communication link. Information that may not be personal or sensitive may be shared between the two devices over the short-range wireless communication link to generate a payment execution request that is subsequently communicated to an intermediary. The intermediary may then cooperate with one or more banking or payment organizations to execute the payment request. Personal and sensitive information required to execute the payment request may be securely stored and/or processed by the intermediary and/or banking or payment organization(s) and/or communicated between the intermediary and/or banking or payment organization(s) via a highly secure communication link. The exposure of personal data or sensitive information (such as banking account or card details, for example) to unsecure communication links between the devices (or between a user device and the intermediary) may therefore be minimized. Put another way, sensitive information and/or substantial processing requirement may be moved from the front end of the payment system (i.e. the wirelessly coupled devices) towards the backend (i.e. the intermediary), so that information shared between the devices over a short-range wireless communication link is reduced and/or insensitive to attack/snooping. A user of a first device may therefore avoid divulging personal or sensitive details (such as their bank account or payment card details) to another device over a short-range wireless communication link. Embodiments may there minimize the risk of fraud and may help consumers to overcome their reluctance to make payments from a mobile computing device.

[0008] The user of the mobile computing device may be a consumer and the user of the electronic device may be a merchant/supplier. Embodiments may therefore provide for a payment system that enables a consumer to make a payment to the merchant/supplier without divulging personal or sensitive details. Further, where a supplier is authorized to do so (by prior agreement or status, for example), the supplier can "pull" a payment from a user of a mobile computing device that is within the operating range of a short-range wireless network of the supplier's electronic device. Payment from the user of the mobile computing device may therefore be requested automatically (by a wirelessly enabled Point of Sale (PoS) or PEST entry device) when they are at certain location, and the supply or provision of goods or services may then be automatically prevented or enabled depending on whether the payment is executed.

[0009] Also, the system may allow for a mobile computing device to cooperate wirelessly with any other wireless-enabled device with the operating range of the short-range wireless communication link. The user of the mobile computing device may therefore not be required to know certain information (or anything at all) about the other device or its user (such as a telephone number associated with the other device, for example). Embodiments may therefore provide a mobile payment or remittance concept that enables a user to send a payment to a user of any device within a distance that may be based on the operating range of a short-range wireless communication link. The recipient's device (i.e. the device receiving a payment request from a different, initiating device) need not comprise any particular software or application (commonly referred to as an "app") associated with an embodiment, but may sent (or directed to obtain) the software or application if it is not already present on the recipient's device. In alternative embodiments, the payment request may itself include the required software or application necessary to generate a reply to the payment request.

[00010] Embodiments may enable a payer or payee to initiate a request to send/receive funds to/from a payee/payer within range of a short-range wireless communication link. Little to no information may be known about the payee or payer except that the payee or payer is within (short-range wireless) range. In response to receiving such a request, a message may be sent to an intermediary which initiates the transfer of funds between bank/payment accounts associated with the payer and payee.

[00011] Reference to short-range wireless communication link should be taken to exclude a mobile/cellular phone radio communication link (such as a GSM or CDMA link, for example). Reference to short-range wireless communication link is instead meant to refer to wireless communication links that have a range significantly less than that of a mobile/cell phone radio. Current examples of such short-range wireless communication technologies or standards include: ANT+; Bluetooth; Bluetooth Low Energy (LE); ISA 100a; Infrared (IrDA); ISM band; NFC; RFID; 6L0WPAN; UWB; Wi-Fi; Wireless HART; WirelessHD; WirelessUSB; ZigBee; and Z-Wave. All of the short-range wireless communication technologies or standards listed above have a range of less than 100m, and most have a range of less than 10m. A short-range wireless communication link according to an embodiment may therefore have a range of less than 100m, or less than 10m.

[00012] Further, reference to a mobile computing device having a wireless communication interface for communicating over a short-range wireless communication link should be understood to refer to any suitable portable computing device having short-range wireless communication capabilities. Current examples of mobile computing devices include: a mobile phone; a laptop computer, a portable tablet computer, a smartphone, and a smart watch.

[00013] Reference to an electronic device having a wireless communication interface for communicating over a short-range wireless communication link should be understood to refer to any suitable electronic device having short-range wireless communication capabilities. Current examples of such electronic devices therefore include: a payment terminal, a PoS terminal, a PIN entry device, a personal computer, a smart TV, a mobile phone; a laptop computer, a portable tablet computer, a smartphone, and a smart watch.

[00014] In an embodiment, the wireless communication interface of the mobile computing device may configured to transmit or receive a payment request to or from the electronic device and to receive or transmit a payment request acknowledgement from or to the electronic device in response to the transmitted or received payment request, and wherein the wireless communication interface of the electronic device is configured to receive or transmit a payment request from or to the mobile computing device and to transmit or receive a payment request acknowledgement to or from the mobile computing device in response to the received or transmitted payment request.

[00015] In an embodiment, the intermediary server may comprise: a first communication interface for communication with at least one of: the mobile computing device; and the electronic device to receive the payment execution request from the mobile computing device or the electronic device, the payment execution request being communicated from the mobile computing device or the electronic device to the intermediary server in response to the payment request acknowledgement; and a second communication interface for communication with the at least one banking or payment organization, the second communication interface being configured to transmit information to the at least one banking or payment organization based on the payment execution request received via the first communication interface.

[00016] The intermediary server may include a personal identification security system. Such a system may employ Personal Identification Number (PIN) identification, password authentication, or biometric identification systems for example.

[00017] The intermediary server may include PIN Block 3DES encryption.

[00018] In an embodiment, the intermediary server may be adapted to communicate with a software application of the mobile computing device or the electronic device.

[00019] The mobile computing device may be a first mobile telephony device, and the intermediary server may be adapted to communicate with the first mobile telephony device via a mobile telephone network.

[00020] Also, the electronic device may be a second mobile telephony device, and the intermediary server may be adapted to communicate with the second mobile telephony device via a mobile telephone network.

[00021] In an embodiment, the intermediary server may be configured to receive information from the at least one banking or payment organization indicating the status of the requested payment, and the intermediary server may be further configured to provide information regarding the status of the requested payment to at least one of: the mobile computing device; and the electronic device. [00022] The intermediary server may further comprise a database storing information relating to users of the system.

[00023] In an embodiment, the system may implement a security verification process by verifying at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode or password provided by a user of the mobile computing device; a passcode or password provided by a user of the electronic device; and an account identifier set by a banking or payment organization.

[00024] The system may be further adapted to verify an account personal identification number agreed with the banking or payment organization.

[00025] In an embodiment, the information transmitted to the at least one banking or payment organization may comprise information relating to at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode/password provided by a user of the electronic device; requested fund amount; payment reference; type of currency; and requested expiry date.

[00026] According to another aspect of the invention, there is provided a mobile telephone network, comprising: a system according to an embodiment of the invention, wherein the mobile computing device is a mobile telephony device.

[00027] In an embodiment, the mobile telephony device may be operable to cooperate wirelessly with an electronic device via a short-range wireless communication link to generate a payment execution request indicating a requested payment between a user of the mobile telephony device and entity associated with the electronic device.

[00028] According to yet another aspect of the invention, there is provided a method of providing a payment service, comprising: wirelessly cooperating a mobile computing device and an electronic device over a short-range wireless communication link to generate a payment execution request indicating a requested payment between a user of the mobile computing device and a user of the electronic device; transmitting the payment execution request from the mobile computing device or the electronic device to an intermediary server configured as a gateway to records of at least one banking or payment organization; and transmitting information from the intermediary server to the at least one banking or payment organization based on the received payment execution request.

[00029] In an embodiment, the step of wirelessy cooperating may comprise: controlling the mobile computing device to transmit/receive a payment request to/from the electronic device and to receive/transmit a payment request acknowledgement from/to the electronic device in response to the transmitted/received payment request; and controlling the electronic device to receive/transmit a payment request from/to the mobile computing device and to transmit/receive a payment request acknowledgement to/from the mobile computing device in response to the received/transmitted payment request.

[00030] The step of transmitting the payment execution may be executed in response to the payment request acknowledgement.

[00031] The mobile computing device may be a first mobile telephony device, and the intermediary server may be adapted to communicate with the first mobile telephony device via a mobile telephone network.

[00032] The mobile computing device may be a second mobile telephony device, and the intermediary server may be adapted to communicate with the second mobile telephony device via a mobile telephone network.

[00033] Embodiments may further comprise the steps of: transmitting from the at least one banking or payment organization to the intermediary server information indicating the status of the requested payment; and providing information regarding the status of the requested payment to at least one of: the mobile computing device; and the electronic device.

[00034] In an embodiment, the information transmitted to the at least one banking or payment organization may comprise information relating to at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode provided by a user of the electronic device; requested fund amount; type of currency; and requested expiry date. [00035] According to another aspect of the invention, there is provided a computer program product for providing a payment service, wherein the computer program product comprises a computer-readable storage medium having computer-readable program code embodied therewith, the computer-readable program code configured to perform all of the steps of a method according to an embodiment.

[00036] According to another aspect of the invention, there is provided a computer system comprising: a computer program product according to an embodiment; and one or more processors adapted to perform all of the steps of a method according to an embodiment.

[00037] In other illustrative embodiments, a computer program product comprising a computer readable medium having a computer readable program may be provided. The computer readable program, when executed on a computing device, may cause the computing device to perform various ones of, and combinations of, the operations outlined above with regard to the method illustrative embodiment.

[00038] In yet another illustrative embodiment, a system or apparatus is provided. The system or apparatus may comprise one or more processors and a memory coupled to the one or more processors. The memory may comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform various ones of, and combinations of, the operations outlined above with regard to the method illustrative embodiment.

[00039] The invention may allow users to make mobile payments without having to divulge personal or sensitive details to a recipient.

[00040] In addition to not disclosing the user's personal or sensitive details, embodiments may further decrease the risk of fraud as a payment request may be arranged to be valid for a limited period of time and for a fixed amount. Such limitations may be selected by the user, for example.

[00041] Embodiments may not require the consumer to have a debit or credit card, or in fact any card-based bank account. This may enable cashpoint card holders (i.e. cards that can be used in an ATM, to withdraw cash, but cannot be used as a debit card) to execute payments using their mobile computing device. [00042] These and other features and advantages of the present invention will be described in, or will become apparent to those of ordinary skill in the art in view of, the following detailed description of the example embodiments of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[00043] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

[00044] Figure 1 depicts a pictorial representation of an example system in which aspects of the illustrative embodiments may be implemented;

[00045] Figure 2 is a block diagram of an example computing device in which aspects of the illustrative embodiments may be implemented;

[00046] Figure 3 is a flow chart of an example of an implementation of a method of registering a user with a system according to an embodiment of the present subject matter;

[00047] Figure 4 depicts a pictorial representation of an example system in which aspects of the illustrative embodiments may be implemented;

[00048] Figure 5 is a flow chart of an example of an implementation of a method according to an embodiment of the present subject matter; and

[00049] Figure 6 shows four examples of different security layers present in a system according to an embodiment of the present subject matter.

DETAILED DESCRIPTION

[00050] The illustrative embodiments provide concepts for enabling mobile payments to or from a mobile computing device. The concepts may employ wireless communication between a mobile computing device and an electronic device via a short-range wireless communication device at a front-end of the system, whilst sharing of sensitive/personal information and implementation of the payment is undertaken securely at the back-end of the system.

[00051] Embodiments may therefore be said to enable the transfer of funds between users of mobile computing devices. Other embodiments, may enable a user of a mobile computing device, such as a smart phone, to pay a supplier via an electronic payment terminal without sharing sensitive or personal information over a wireless short-range communication link (between the mobile computing device and the electronic payment terminal).

[00052] Illustrative embodiments may be utilized in many different types of data processing environments. In order to provide a context for the description of elements and functionality of the illustrative embodiments, Figures 1 and 2 are provided hereafter as example environments in which aspects of the illustrative embodiments may be implemented. It should be appreciated that the Figures only depict examples and are not intended to assert or imply any limitation with regard to the environments, networks or systems in which aspects or embodiments of the present invention may be implemented. Many modifications to the depicted examples may be made without departing from the scope of the present invention.

[00053] Figure 1 depicts a pictorial representation of an example system in which aspects of the illustrative embodiments may be implemented. Distributed data processing system 100 may include a network of computing devices in which aspects of the illustrative embodiments may be implemented. The system 100 contains at least one network 102, which is the medium used to provide communication links between various devices and computers connected together within the system 100. The network 102 may include connections, such as wire, wireless communication links, or fiber optic cables.

[00054] In the depicted example, a first 104 and second 106 servers are connected to the network 102 along with a storage unit 108. In addition, clients 110, 112, and 114 are also connected to the network 102. The clients 110, 112, and 114 may be, for example, personal computers, mobile computing devices, electronic payment terminals, laptop computers, tablet computers, or the like.

[00055] The clients 110, 112, and 114 are provided with wireless communication capabilities so that they may communicate with each other via one or more short-range wireless communication links 116 separate from the network 102. For example, the clients 110, 112, and 114 may be within short-range wireless communication network 120.

[00056] In the depicted example, the first server 104 provides data, such as operating system instructions, and applications to the clients 110, 1 12, and 1 14. Clients 110, 112, and 114 are clients to the first server 104 in the depicted example. The system 100 may include additional servers, clients, and other devices not shown.

[00057] In the depicted example, the system 100 is the Internet with the network 102 representing a worldwide collection of networks and gateways that use the Transmission Control Protocol/Internet Protocol (TCP/IP) suite of protocols to communicate with one another. At the heart of the Internet is a backbone of high-speed data communication lines between major nodes or host computers, consisting of thousands of commercial, governmental, educational and other computer systems that route data and messages. Of course, the system 100 may also be implemented to include a number of different types of networks, such as for example, a mobile phone/cell network, an intranet, a local area network (LAN), a wide area network (WAN), or the like. As stated above, Figure 1 is intended as an example, not as an architectural limitation for different embodiments of the present invention, and therefore, the particular elements shown in Figure 1 should not be considered limiting with regard to the environments in which the illustrative embodiments of the present invention may be implemented.

[00058] Figure 2 is a block diagram of an example mobile computing device 200 in which aspects of the illustrative embodiments may be implemented. The mobile computing device 200 is an example of a mobile computer or laptop, such as client 110 in Figure 1, in which computer usable code or instructions implementing the processes for illustrative embodiments of the present invention may be located.

[00059] In the depicted example, the mobile computing device 200 employs a hub architecture including a north bridge and memory controller hub (NB/MCH) 202 and a south bridge and input/output (I/O) controller hub (SB/ICH) 204. A processing unit 206, a main memory 208, and a graphics processor 210 are connected to NB/MCH 202. The graphics processor 210 may be connected to the NB/MCH 202 through an accelerated graphics port (AGP).

[00060] In the depicted example, a network adapter 212 connects to SB/ICH 204. An audio adapter 216, a keyboard and a mouse adapter 220, a modem 222, a read only memory (ROM) 224, a hard disk drive (HDD) 226, a CD-ROM drive 230, a universal serial bus (USB) ports and other communication ports 232, and PCI/PCIe devices 234 connect to the SB/ICH 204 through first bus 238 and second bus 240. PCI/PCIe devices may include, for example, Ethernet adapters, add-in cards, and PC cards for notebook computers. PCI uses a card bus controller, while PCIe does not. ROM 224 may be, for example, a flash basic input/output system (BIOS).

[00061] The HDD 226 and CD-ROM drive 230 connect to the SB/ICH 204 through second bus 240. The HDD 226 and CD-ROM drive 230 may use, for example, an integrated drive electronics (IDE) or serial advanced technology attachment (SATA) interface. Super I/O (SIO) device 236 may be connected to SB/ICH 204.

[00062] An operating system runs on the processing unit 206. The operating system coordinates and provides control of various components within the computing device 200 in Figure 2. As a client, the operating system may be a commercially available operating system. An object-oriented programming system, such as the Java™ programming system, may run in conjunction with the operating system and provides calls to the operating system from Java™ programs or applications executing on data processing system 200.

[00063] Instructions for the operating system, the object-oriented programming system, and applications or programs are located on storage devices, such as HDD 226, and may be loaded into main memory 208 for execution by processing unit 206. The processes for illustrative embodiments of the present invention may be performed by processing unit 206 using computer usable program code, which may be located in a memory such as, for example, main memory 208, ROM 224, or in one or more peripheral devices 226 and 230, for example.

[00064] A bus system, such as first bus 238 or second bus 240 as shown in Figure 2, may be comprised of one or more buses. Of course, the bus system may be implemented using any type of communication fabric or architecture that provides for a transfer of data between different components or devices attached to the fabric or architecture. A communication unit, such as the modem 222 or the network adapter 212 of Figure 2, may include one or more devices used to transmit and receive data. A memory may be, for example, main memory 208, ROM 224, or a cache such as found in B/MCH 202 in Figure 2.

[00065] Those of ordinary skill in the art will appreciate that the hardware in Figures 1 and 2 may vary depending on the implementation. Other internal hardware or peripheral devices, such as flash memory, equivalent non-volatile memory, or optical disk drives and the like, may be used in addition to or in place of the hardware depicted in Figures 1 and 2. Also, the processes of the illustrative embodiments may be applied to a multiprocessor data processing system without departing from the spirit and scope of the present invention.

[00066] Moreover, the mobile computing device 200 may take the form of any of a number of different mobile computing devices including a tablet computer, a smart phone, a mobile phone, a laptop computer, a personal digital assistant (PDA), a smart watch, a wearable computing device (such as glasses or a wristband for example), or the like. In some illustrative examples, the mobile computing device 200 may be a portable computing device that is configured with flash memory to provide non-volatile memory for storing operating system files and/or user-generated data, for example. Thus, the mobile computing device 200 may essentially be any known or later-developed mobile computing device 200 without architectural limitation.

[00067] The proposed invention enhances a system (such as that depicted in Figure 2) by providing for payment services. Embodiments may provide a system for providing a payment service enabling users to securely make or receive payments using a mobile computing device (such as a mobile telephony device, smart phone, tablet computer, laptop, or PDA, for example).

[00068] How a consumer gains access to the services and a how a consumer subsequently uses the services will now be described in the following sections.

[00069] User Registration

[00070] For security reasons, it may be necessary for users to register for the service. This can be achieved in one of two ways; by registering via the service web site or registering for the service directly from a mobile phone. An overview of an exemplary registration process is given in Figure 3, which shows how a user registers for the service.

[00071] Figure 3 shows the stages for registering to use the service. In step 302, the user becomes aware of the existence of the service. For example, the user may be informed of the service by an advertisement or a message sent to the user. In step 304, there is a registration process, and the subsequent step 306 involves a password being sent to the user . This provides a link between the IP address or mobile identity of the user and the postal address, and thereby provides an additional level of security over the simple anonymous use of a PC or mobile telephone. It will, however, be appreciated that other identities may be used, e.g. card details, credentials to log onto other system or one time use identification token, etc. Next, in step 308, the user authenticates the registration by confirming details (such as the password for example). After this registration process, the user is able to use the service in step 310.

[00072] Once registered, consumers can then begin to use the service and do so by navigating to an applications menu on their mobile computing device and executing a required application. In a similar fashion to logging into a secure service, physical Automatic Teller Machine (ATM) or self-service banking system, the user may be required to enter a numeric code, or Passcode, which forms part of an identification process.

[00073] A description of an implementation of the system of the invention now follows. A high level overview of such a system is shown in Figure 4.

[00074] The system comprises a mobile computing device (DEVICE 1) 402 and an electronic device (DEVICE2) 404 connected to an intermediary server 406 via a communication network 408.

[00075] The mobile computing device 402 comprises a wireless communication interface 410 for communicating with an electronic device (such as the electronic device 404) over a short-range wireless communication link 412. The mobile computing device 402 also comprises a processor 414 for executing instructions that operate/control the mobile computing device 402. Also, the mobile computing device 402 comprises a further communication interface 416 which is adapted to enable communication between the mobile computing device 402 and the intermediary server 406 via the communication network 408. By way of example, the mobile computing device 402 may be a mobile telephony device and the communication network 408 may be a conventional mobile phone or cell network. In such an example, the further communication interface 416 may comprise a conventional mobile phone transceiver adapted to enable communication with the intermediary server 406 via the mobile/cell network 408.

[00076] The electronic device 404 comprises a wireless communication interface 418 for communicating with a mobile computing device (such as the mobile computing device 402) over a short-range wireless communication link 420. The short-range wireless communication link 420 may be the same or different as/from the short-range wireless communication link 412 employed by the wireless communication interface 410 of the mobile computing device 402. The electronic device 404 also comprises a processor 422 for executing instructions that operate/control the electronic device 404. Also, the electronic device 404 comprises a further communication interface 424 which is adapted to enable communication between the electronic device 404 and the intermediary server 406 via the communication network 408. By way of example, the electronic device 404 may be a mobile telephony device and the communication network 408 may be a conventional mobile phone or cell network. In such an example, the further communication interface 424 may comprise a conventional mobile phone transceiver adapted to enable communication with the intermediary server 406 via the mobile/cell network 408.

[00077] The intermediary server 406 is configured as a gateway to banking records of first 430 to second 432 banking organizations and records of first 434 to second 436 payment organizations. Such records may include one or more databases storing information about customers of the banking/payment organization including, for example, account details, customer activity, customer information and/or services available/offered to customers.

[00078] To implement a mobile payment service, the mobile computing device 402 and the electronic device 404 cooperate wirelessly via the short-range wireless communication link(s) 412,420 to generate a payment execution request. The payment execution request indicates a requested payment between a user of the mobile computing device 402 and a user of the electronic device 404.

[00079] In cooperating wirelessy, the mobile computing device 402 may transmit a payment request to the electronic device 404 and then receive a payment request acknowledgement from the electronic device 404 in response to the transmitted payment request. Alternatively, the mobile computing device 402 may receive a payment request from the electronic device 404 and then transmit a payment request acknowledgement to the electronic device 404 in response to the received payment request.

[00080] Similarly, the electronic device 404 may receive a payment request from the mobile computing device 402 and transmit a payment request acknowledgement to the mobile computing device 402 in response to the received payment request. Alternatively, the electronic device 404 may transmit a payment request to the mobile computing device 402 and receive a payment request acknowledgement from the mobile computing device 402 in response to the transmitted payment request. [00081] Put another way, either device 402 or 404 may initiate the payment process by requesting that a payment be executed. A payment may therefore be "pushed" or "pulled" by a user of the mobile computing device 404 or by a user of the electronic device 404.

[00082] At least one of the mobile computing device 402 and the electronic device 404 communicates the generated payment execution request to the intermediary server 406 via the communication network 408. The intermediary server 406 is configured to receive the payment execution request and, based on the received payment execution request, the intermediary server 406 transmits information to the at least one of the banking/payment organizations 430,432,434,436.

[00083] Here, the intermediary server comprises a first communication interface 440 for communication with the mobile computing device 402 and the electronic device 404 to receive a payment execution request. The intermediary server 406 also comprises a second communication interface 450 for communication with the banking/payment organizations, the second communication interface 450 being configured to transmit information to the at least one banking/payment organization based on the payment execution request received via the first communication interface.

[00084] The intermediary server further comprises a database storing information relating to users of the system. Based on information stored by the database, the system implements a security verification process by verifying at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode or password provided by a user of the mobile computing device; a passcode or password provided by a user of the electronic device; and an account identifier set by a banking or payment organization. Additional verification/security checks may be undertaken by the system, for example by verifying an account personal identification number agreed with the appropriate banking or payment organization(s).

[00085] The information transmitted from the intermediary server 406 to the banking or payment organization(s) may comprise information relating to at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode provided by a user of the electronic device; requested fund amount; type of currency; and requested expiry date. Such information may be used by the banking or payment organization(s) to verify and/or execute the requested payment.

[00086] In some embodiment, the intermediary server 406 may also receive information back from the banking or payment organization(s) indicating the status of the requested payment. This information may be used to provide information regarding the status of the requested payment to the mobile computing device and/or and the electronic device. For example, the intermediary server may be informed by the banking or payment organization(s) that a requested payment has been successfully made, and confirmation of the executed payment may then be provided to the mobile computing device 402 and/or and the electronic device 404 from the intermediary server 406 via the communication network 408. Similarly, failure of a request payment may also be communicated to the mobile computing device 402 and/or and the electronic device 404 in this way.

[00087] A description of an implementation of a method 500 according to an embodiment will now be provided with the reference to Figure 5.

[00088] The method begins/starts in step 502 and proceeds to step 504 wherein a user instructs their mobile computing device to search for and identify locally positioned device having short-range wireless communication capabilities. In other words, the user causes the mobile computing device to identify all electronic devices that are within range of a short- range wireless communication link provided by the mobile computing device and that are adapted to establish communication with the mobile computing device over a short-range wireless communication link (which may the same link or a different short-range wireless communication link).

[00089] Next, in step 506, the user selects one the identified electronic devices that he/she would like to send a payment to and instructs the mobile computing device to send a payment request to the selected electronic device via a short-range communication link. The selected electronic device receives the payment request in step 508.

[00090] In response to receiving the payment request in step 508, the electronic device determines whether or not it (and/or its' user) is registered to use the payment service in step 510. If, in step 510, it is determined that the electronic device (and/or its' user) is not registered, the method proceeds to step 512 in which the electronic device (and/or its' user) is registered (using the procedure outlined in Figure 3 for example. Once the registration process of step 512 is complete, the method proceeds to step 514. If, in step 510, it is determined that the electronic device (and/or its' user) is registered, the method proceeds straight to step 514, thus avoiding the registration process of step 514.

[00091] In step 514, a user of the electronic device confirms acceptance of the requested payment, thereby causing the electronic device to transmit a payment request acknowledgement message to the mobile computing device via a short-range wireless communication link. The payment request acknowledgement message is received by the mobile computing and processed so as to generate a payment execution request in step 516. The generated payment execution request comprises information representing the requested payment between a user of the mobile computing device and a user of the electronic device.

[00092] It will therefore be understood that the method steps 504 through 516 may be summarized as a mobile computing device and an electronic device wirelessly cooperating over a short-range wireless communication link to generate a payment execution request. Such a payment execution request contains information that may be used by the intermediary server to authenticate or authorize the payment request and to subsequently request execution of (an authenticated or authorized) payment request by a banking or payment organization.

[00093] The processing of step 516 is completed by transmitting the payment execution request from the mobile computing device to then intermediary server via a communication network (such as the internet or a mobile/cell phone network for example) using a secure communications protocol. Examples of information that may be included in the payment execution request include: the identity of a user of the mobile computing device; other contact details of the user of the mobile computing device; details relating to the identity of the mobile computing device; the identity of a user of the electronic device; other contact details of the user of the electronic device; details relating to the identity of the electronic device; a passcode provided by a user; an account identifier set by a banking or payment organization; a requested fund amount; a type of currency.

[00094] The intermediary server then receives the payment execution request in step 518.

[00095] Next, in step 520, the intermediary server processes the received payment execution request to determine whether or not to send information to a banking institute and/or what is to be included in such information. The step of 520, may therefore implement a security verification process which verifies information provided by the payment execution request. For example, such a security verification process may verify at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode or password provided by a user of the mobile computing device; a passcode or password provided by a user of the electronic device; an account identifier set by a banking or payment organization; and an account personal identification number agreed with a banking or payment organization.

[00096] After completing the processing of step 520, and determining to send information to a banking institute, the intermediary server transmits information to at least one banking or payment organization in step 522. The transmitted information is based on the received payment execution request and may include, for example, information relating to at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode provided by a user of the electronic device; requested fund amount; type of currency; and requested expiry date.

[00097] The at least one banking or payment organization then receives, in step 524, the information transmitted by the intermediary server. Next, in step 536, the at least one banking or payment organization process the received information and executes the payment in accordance with the received information. In other words, the at least one banking or payment organization executes the payment as requested by the payment execution request.

[00098] After executing the payment in step 536, the at least one banking or payment organization transmits status information indicating the status of the requested payment to the intermediary server. Such status information may indicate whether or not the payment was successfully executed along with information (such as time, date, amount, currency, payee, payer, success, failure, reason for failure, etc.) associated with the payment. In other words, a banking or payment organization may report back to the intermediary server regarding the status of the requested payment. This status information is received by the intermediary server in step 528, and the intermediary then provides information regarding the status of the requested payment to the mobile computing device and/or the electronic device via the communication network (Steps 530, 532). As depicted in the diagram of Figure 5, the information regarding the status of the requested payment may be sent directly to both the mobile computing device and the electronic device. Alternatively, the information regarding the status of the requested payment may be sent to either the mobile computing device or the electronic device and then relayed/forwarded on to the other device via a short-range wireless communication link.

[00099] The method than ends/stops in step 534.

[000100] When a user enters information at each stage of the process, the information may be encrypted and securely provided to the intermediary. In this way, the amount of processing undertaken by the mobile computing device and/or the electronic device may be reduced. In alternative embodiments, however, the amount of processing undertaken by the mobile computing device and/or the electronic device may depend upon the processing undertaken by the intermediary server. For example, the mobile computing device may be arranged to simply relay user inputs to the intermediary server via the communication network, therefore undertaking a minimal amount of processing. Conversely, the mobile computing device may complete numerous steps of processing the inputs provided by a user, with only minimal processing being required by the intermediary server. Thus, a trade-off may be made between the mobile computing device and/or the electronic device and the server in terms of the processing requirements.

[000101] It will be understood that the embodiment depicted in Figure 5 includes the steps of identifying local devices and then sending a request to send payment to an identified device. Other embodiments may not include the step of searching for local devices. Further, rather than sending a request to send payment, a request to receive payment may instead by sent (e.g. a request to be paid). Put another way, either device (e.g. the mobile computing device or the electronic device) may initiate a payment process by requesting that a payment be executed. A payment may therefore be "pushed" (e.g. requested to be sent) or "pulled" (e.g. requested to be received) by a user of the mobile computing device 404 or by a user of the electronic device 404.

[000102] Embodiments may thus enable a payer or payee to initiate a request to send/receive funds to/from a payee/payer within range of a short-range wireless communication link. The mobile computing device and the electronic device thus cooperate wireless (over a short-range wirelss communication link) to generate a message (e.g. a payment execution request). Either of the devices may then send the generated message to the intermediary server for processing which initiates the transfer of funds between bank/payment accounts associated with the payer and payee.

[000103] End to End Security Model

[000104] A primary design consideration for a system and/or service according to the invention may be security. As shown in Figure 6, the invention may employ a multi-layer security model.

[000105] In Figure 6, part A is an overview of Multi-Layer Security Layer for a SIM Client which shows that network level security is provided by the encryption of over-the-air traffic from the SFM card 660 and the PIN encryption layer provides PIN Block 3DES level security for the PIN.

[000106] Part B is an overview of the Multi-Layer Security Model for a Mobile Information Device Protocol (MIDP) 1.0 Client, in which the security has been further improved to provide a network level security in addition to the mobile network security level. This level provides a secure Secure Sockets Layer (SSL) like connection between the mobile phone application and the intermediary server 635.

[000107] Part C is an overview of the Multi-Layer Security Model for a MIDP 2.0 Client, in which the network security has been further enhanced by providing an SSL tunnel directly from the mobile computing device 630 to the intermediary server 635. This model includes signed application code to address man-in-the-middle attacks.

[000108] Part D is a further enhancement for a MIDP 2.0 client with Java Specification Request (JSR) 177 Support. In this model, the encryption and decryption tasks are carried out within the SFM environment.

[000109] As shown in Figure 6, different client types allow different types of security protection. However in each case there is OTA Encryption, SSL Tunneling and the ΡΓΝ block encryption, which provides 3 DES ΡΓΝ protection.

[000110] General security features of the service may include:

[000111] -No customer banking account data is stored within the client application. [000112] -No customer banking account data is stored within the handset memory. [000113] -Not enough banking account information is held by the intermediary server at the server side to clone a bank card or to perform a Card Not Present Transaction, for example.

[000114] -The customer selects their own Passcode

[000115] -The Passcode secures the entire intermediary server channel.

[000116] -The messaging protocol employed by intermediary server may be Hyper- Text Transfer Protocol (HTTP) request/response.

[000117] The PIN block encryption layer may have the following attributes:

[000118] -Passcodes are associated with the user ID to which they relate.

[000119] -The Passcode offset value is an offset value from the Natural PIN generated from the customer ID using the intermediary server Private Encryption Key (PVK).

[000120] -The customer entered Passcode value is not shown on the handset screen during entry.

[000121] -The Passcode value held by the intermediary server may be stored within a database as a PIN offset value protected by the intermediary server.

[000122] -The user may be given a set number consecutive attempts to correctly enter their Passcode into the client.

[000123] -Each customer entered Passcode may be be formed into an ISO Format- 1 PIN block and encrypted with the intermediary server Working Key (WK) prior to transportation to the intermediary server.

[000124] -Following five consecutive incorrect Passcode entry attempts the intermediary server account for this customer may be locked. To gain access to the service the customer must request a new random key which is posted to their home address.

[000125] -The intermediary server may use a Thales RG8000 HSM (High Security Module - which is a standard banking security component) to verify the encrypted customer entered Passcode against the offset value stored in the database. [000126] Exemplary advantages that may be provided by one or more embodiments may include the following:

[000127] A mobile computing device may be used to send a payment to a near-by device. Embodiments may therefore enable payment for goods/ services using a mobile computing device, for example. Thus, embodiments may allow consumers to shop in both a cardholder- not-present or cardholder present environment, without having to divulge sensitive or personal data and may therefore help to minimise the risk of fraud. Use of the service/system may be promoted by banks and merchants to minimise the risk of fraud and overcome consumers' reluctance to make mobile payments.

[000128] Features of the System

[000129] Notable features that may be provided by a system according to the invention include the following:

[000130] · A PEST or password is required to enter and use the system/service

[000131] · A request to execute a payment may be provided to the intermediary server from a mobile computing device via a secure and encrypted delivery method.

[000132] · The user may select a value to exactly match the payment required, rather than an incremental fixed amount.

[000133] · The user may select from a variety of currencies.

[000134] · The transaction may be authorised and settled from the user's bank account or debit /credit card rather than prepaying an amount.

[000135] · The user may select, in real time, an account to be used as a source of settlement, and this may be chosen depending on availability of funds.

[000136] · The system/service may enable real-time execution of a payment to a nearby device, which may thus be used to undertake an rapid or instant payment.

[000137] · The system/service may be highly secure since the registration procedure can take account of the identity of the mobile computing device, a passcode provided by the user and the address of the user, for example. [000138] As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method, or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Furthermore, aspects of the present invention may take the form of a computer program product embodied in any one or more computer readable medium(s) having computer usable program code embodied thereon.

[000139] Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CDROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[000140] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in a baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[000141] Computer code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio frequency (RF), etc., or any suitable combination thereof. [000142] Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as JavaTM, SmalltalkTM, C++, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user' s computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[000143] Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the illustrative embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[000144] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions that implement the function/act specified in the flowchart and/or block diagram block or blocks.

[000145] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[000146] It will be clear to one of ordinary skill in the art that all or part of the method of one embodiment of the present invention may suitably and usefully be embodied in a logic apparatus, or a plurality of logic apparatus, comprising logic elements arranged to perform the steps of the method and that such logic elements may comprise hardware components, firmware components or a combination thereof.

[000147] It will be equally clear to one of skill in the art that all or part of a logic arrangement according to one embodiment of the present invention may suitably be embodied in a logic apparatus comprising logic elements to perform the steps of the method, and that such logic elements may comprise components such as logic gates in, for example a programmable logic array or application-specific integrated circuit. Such a logic arrangement may further be embodied in enabling elements for temporarily or permanently establishing logic structures in such an array or circuit using, for example, a virtual hardware descriptor language, which may be stored and transmitted using fixed or transmittable carrier media.

[000148] It will be appreciated that the method and arrangement described above may also suitably be carried out fully or partially in software running on one or more processors (not shown in the figures), and that the software may be provided in the form of one or more computer program elements carried on any suitable data-carrier (also not shown in the figures) such as a magnetic or optical disk or the like. Channels for the transmission of data may likewise comprise storage media of all descriptions as well as signal-carrying media, such as wired or wireless signal-carrying media.

[000149] A method is generally conceived to be a self-consistent sequence of steps leading to a desired result. These steps require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It is convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, parameters, items, elements, objects, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these terms and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. [000150] The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[000151] A data processing system suitable for storing and/or executing program code will include at least one processor coupled directly or indirectly to memory elements through a system bus. The memory elements can include local memory employed during actual execution of the program code, bulk storage, and cache memories which provide temporary storage of at least some program code in order to reduce the number of times code must be retrieved from bulk storage during execution.

[000152] Input/output or I/O devices (including but not limited to keyboards, displays, pointing devices, etc.) can be coupled to the system either directly or through intervening I/O controllers. Network adapters may also be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices through intervening private or public networks. Modems, cable modems and Ethernet cards are just a few of the currently available types of network adapters.

[000153] The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. An electronic system providing a payment service, comprising:

a mobile computing device having a wireless communication interface for communicating with an electronic device over a short-range wireless communication link;

the electronic device having a wireless communication interface for communication with the mobile computing device over a short-range wireless communication link; and

an intermediary server configured as a gateway to records of at least one banking or payment organization,

wherein the mobile computing device and the electronic device cooperate wirelessly to generate a payment execution request indicating a requested payment between a user of the mobile computing device and an entity associated with the electronic device, and wherein the intermediary server is configured to receive the payment execution request from the mobile computing device or the electronic device and to transmit information to the at least one banking or payment organization based on the received payment execution request.

2. The system of claim 1,

wherein the wireless communication interface of the mobile computing device is configured to transmit/receive a payment request to/from the electronic device and to receive/transmit a payment request acknowledgement from/to the electronic device in response to the transmitted/received payment request,

and wherein the wireless communication interface of the electronic device is configured to receive/transmit a payment request from/to the mobile computing device and to transmit/receive a payment request acknowledgement to/from the mobile computing device in response to the received/transmitted payment request.

3. The system of claim 1 or 2, wherein the intermediary server comprises:

a first communication interface for communication with at least one of: the mobile computing device; and

the electronic device

to receive the payment execution request from the mobile computing device or the electronic device, the payment execution request being communicated from the mobile computing device or the electronic device to the intermediary server in response to a payment request acknowledgement; and

a second communication interface for communication with the at least one banking or payment organization, the second communication interface being configured to transmit information to the at least one banking or payment organization based on the payment execution request received via the first communication interface.

4. The system of any preceding claim, wherein the intermediary server includes a personal identification security system.

5. The system of claim 4, wherein the intermediary server includes PIN Block 3DES encryption.

6. The system of any preceding claim, wherein the entity associated with the electronic device is a user of the electronic device.

7. The system of any preceding claim, wherein the intermediary server is adapted to communicate with a software application of the mobile computing device or the electronic device.

8. The system of any preceding claim, wherein the mobile computing device is a first mobile telephony device, and wherein the intermediary server is adapted to communicate with the first mobile telephony device via a mobile telephone network.

9. The system of any preceding claim, wherein the electronic device is a second mobile telephony device, and wherein the intermediary server is adapted to communicate with the second mobile telephony device via a mobile telephone network.

10. The system of any preceding claim, wherein the intermediary server is further configured to receive information from the at least one banking or payment organization indicating the status of the requested payment, and wherein the intermediary server is further configured to provide information regarding the status of the requested payment to at least one of: the mobile computing device; and the electronic device.

11. The system of any preceding claim, wherein the intermediary server further comprises a database storing information relating to users of the system.

12. The system of any preceding claim, wherein the system implements a security verification process by verifying at least one of: the identity of a user of the mobile computing device; the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode or password provided by a user of the mobile computing device; a passcode or password provided by a user of the electronic device; and an account identifier set by a banking or payment organization.

13. A system as claimed in claim 12, wherein the system is further adapted to verify an account personal identification number agreed with the banking or payment organization.

14. A system as claimed in any preceding claim wherein the information transmitted to the at least one banking or payment organization comprises information relating to at least one of: the identity of a user of the mobile computing device; the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode provided by a user of the electronic device; requested fund amount; payment reference; type of currency; and requested expiry date.

15. A mobile telephone network, comprising:

a system as claimed in any preceding claim, wherein the mobile computing device is a mobile telephony device.

16. The mobile telephone network of claim 15, wherein the mobile telephony device is operable to cooperate wirelessly with an electronic device via a short-range wireless communication link to generate a payment execution request indicating a requested payment between a user of the mobile telephony device and entity associated with the electronic device.

17. A method of providing a payment service, comprising:

wirelessly cooperating a mobile computing device and an electronic device over a short-range wireless communication link to generate a payment execution request indicating a requested payment between a user of the mobile computing device and an entity associated with the electronic device; transmitting the payment execution request from the mobile computing device or the electronic device to an intermediary server configured as a gateway to records of at least one banking or payment organization; and

transmitting information from the intermediary server to the at least one banking or payment organization based on the received payment execution request.

18. The method of claim 17, wherein the step of wirelessly cooperating comprises:

controlling the mobile computing device to transmit/receive a payment request to/from the electronic device and to receive/transmit a payment request acknowledgement from/to the electronic device in response to the transmitted/received payment request; and controlling the electronic device to receive/transmit a payment request from/to the mobile computing device and to transmit/receive a payment request acknowledgement to/from the mobile computing device in response to the received/transmitted payment request.

19. The method of claim 18, wherein the step of transmitting the payment execution is executed in response to the payment request acknowledgement.

20. The method of any of claims 17 to 19, wherein the mobile computing device is a first mobile telephony device, and wherein the intermediary server is adapted to communicate with the first mobile telephony device via a mobile telephone network.

21. The method of any of claims 17 to 20, wherein the electronic device is a second mobile telephony device, and wherein the intermediary server is adapted to communicate with the second mobile telephony device via a mobile telephone network.

22. The method of any of claims 17 to 21, further comprising the steps of:

transmitting from the at least one banking or payment organization to the intermediary server information indicating the status of the requested payment; and

providing information regarding the status of the requested payment to at least one of: the mobile computing device; and the electronic device.

23. The method of any of claims 17 to 22, wherein the information transmitted to the at least one banking or payment organization comprises information relating to at least one of: the identity of a user of the mobile computing device, the identity of a user of the electronic device; details relating to the identity of the mobile computing device; details relating to the identity of the electronic device; a passcode provided by a user of the mobile computing device; a passcode provided by a user of the electronic device; requested fund amount; a payment reference; type of currency; and requested expiry date.

24. A computer program product for providing a payment service, wherein the computer program product comprises a computer-readable storage medium having computer-readable program code embodied therewith, the computer-readable program code configured to perform all of the steps of any of claims 17 to 23.

25. A computer system comprising: a computer program product according to claim 24; and one or more processors adapted to perform all of the steps of any of claims 17 to 23.