WO2013160830A1 - A server and mobile device for authorizing a transaction - Google Patents

A server and mobile device for authorizing a transaction Download PDF

Info

Publication number
WO2013160830A1
WO2013160830A1 PCT/IB2013/053205 IB2013053205W WO2013160830A1 WO 2013160830 A1 WO2013160830 A1 WO 2013160830A1 IB 2013053205 W IB2013053205 W IB 2013053205W WO 2013160830 A1 WO2013160830 A1 WO 2013160830A1
Authority
WO
WIPO (PCT)
Prior art keywords
recipient
provider
transaction
processor
authorization
Prior art date
Application number
PCT/IB2013/053205
Other languages
French (fr)
Inventor
Uvir ERAMAN
Original Assignee
Eraman Uvir
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Eraman Uvir filed Critical Eraman Uvir
Publication of WO2013160830A1 publication Critical patent/WO2013160830A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223—Realising banking transactions through M-devices

Definitions

  • This invention relates to a server for authorizing a transaction between a provider of goods or services and a recipient of the goods or services.
  • This invention relates also to a mobile device for authorizing a transaction between a provider of goods or services and a recipient of the goods or services.
  • a server for authorizing a transaction between a provider of goods or services and a recipient of the goods or services the server being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving a provider authorization request via the communication network from a provider communication device associated with the provider, requesting authorization for the transaction between the recipient and the provider, the provider authorization request including sufficient information to identify the transaction; in response to receipt of the provider authorization request, the processor generating an administrator authorization request requesting authorization for the transaction between the recipient and the provider and including sufficient information to identify the transaction; and sending the administrator authorization request via the communication network to a mobile device application of a mobile device of the recipient; the processor receiving a recipient authorization response via the communication network from the mobile device application of the mobile device of the recipient, the recipient authorization response containing information sufficient to identify the transaction and the recipient's response which is in the form of information authorizing or declining
  • the server may include a database.
  • the processor may be operable to execute computer program instructions including a data entry module causing the processor to accept input of data pertaining to a number of recipients and a number of providers; and to store the data in the database.
  • the processor may be operable to execute computer program instructions including a provider identification module causing the processor to search the database to identify a data record associated with a particular provider which is stored in the database, by comparing information of the provider contained in the provider authorization request, with the data stored in the database to determine a match.
  • the processor may be operable to execute computer program instructions including a recipient identification module causing the processor to search the database to identify a data record associated with a particular recipient which is stored in the database, by comparing information of the recipient contained in the provider authorization request, with the data stored in the database to determine a match.
  • a recipient identification module causing the processor to search the database to identify a data record associated with a particular recipient which is stored in the database, by comparing information of the recipient contained in the provider authorization request, with the data stored in the database to determine a match.
  • a mobile device for authorizing a transaction between a provider of goods or services and a recipient of the goods or services
  • the mobile device being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving an administrator authorization request via the communication network from an administrator server, requesting authorization for the transaction between the recipient associated with the mobile device and the provider, the administrator authorization request containing information sufficient to identify the transaction; in response to receipt of the administrator authorization request, the processor generating an alert on the mobile device prompting the recipient to input a response to the administrator authorization request which is in the form of information authorizing or declining the administrator authorization request; and in response to input of the recipient's response, the processor generating a recipient authorization response including information sufficient to identify the transaction and the recipient's response and sending the recipient authorization response to the administrator server via the communication network.
  • Figure 1 shows a block diagram of a provider communication device, a server in accordance with the invention and a mobile device in accordance with the invention, shown, in use, in a system and method for authorizing a transaction between a provider of goods or services and a recipient of the goods or services;
  • Figures 2 show various steps in the method which is executed on the provider communication device of Figure 1 ;
  • Figures 3a and 3b show various steps in the method which are executed on the server of Figure 1 ;
  • Figures 4 shows various steps in the method which are executed on the mobile device of Figure 1 ;
  • a system for authorizing a transaction between a provider of goods or services and a recipient of the goods or services is designated generally by the reference numeral 10.
  • the system 10 includes broadly, a plurality of provider communication devices 12 which are each associated with a particular provider; a server, in accordance with a first aspect of the invention, in the form of an administrator server system, designated generally by the reference numeral 14; and a plurality of mobile devices, in accordance with a second aspect of the invention, in the form of recipient mobile devices which are each designated generally by the reference numeral 16 and which are each associated with a particular recipient.
  • the Applicant envisages that providers of goods or services and recipients of the goods or services will subscribe to the system 10.
  • the providers and recipients will register and subscribe to the system 10 by providing an administrator of the administrator server system 14 all their relevant details including their full contact details such as, for example, cellular phone numbers, physical address, telephone numbers, and unique International Mobile Subscriber Identity (IMSI) stored on the Subscriber Identification Module (SIM) of their devices which are connected to the communication network. Furthermore, the providers and recipients will provide the administrator with their unique Internet Protocol (IP) addresses of their devices which are connected to the communication network.
  • IP Internet Protocol
  • the Applicant envisages that the providers will be, for example, in the form of merchants, or any supplier of any goods or any services and the recipients will be, for example, in the form of customers, or clients.
  • the recipients will each receive a card for making payment for goods or services at providers who subscribe to the system 10.
  • the applicant envisages that the recipients will be issued with card numbers for making online and telephonic payments to providers who subscribe to the system 1 0, as will be explained in more detail hereinbelow.
  • the cards and card numbers will be linked to an existing bank facility of each recipient such as, for example, a credit card; a cheque card or a debit card.
  • Each provider communication device 12 is connected to, and is operable to send and receive authorization information to and from the administrator server system 14 via a communication network 18 such as, for example, a cellular communications network, telephone network, wireless data network, Internet, or the like, as will be explained in more detail hereinbelow.
  • a communication network 18 such as, for example, a cellular communications network, telephone network, wireless data network, Internet, or the like, as will be explained in more detail hereinbelow.
  • the provider communication device 12 includes a processor 19 operable to execute computer program instructions in the form of a provider application 20 which is executable on the processor 19 of the provider communication device 12; and a credit card machine 21 including a card reader for reading the cards of recipients.
  • the provider application 20 includes a communication module 22 for sending and receiving authorization information to and from the administrator server system 14 via the communication network 18; and a provider authorization module 24, for generating and interpreting authorization information sent from and received by the communication module 22, as will be described in more detail hereinbelow.
  • the administrator server system 14 is connected to the communication network 18 and includes a server database 26 for storing data of a number of recipients and providers, a processor 27 and computer program instructions in the form of a server application 28 executable on the processor 27.
  • the server database 26 includes a database of providers 26.1 and a database of recipients 26.2.
  • the database of providers 26.1 contains data of a number of providers who form part of and subscribe to the system 10 and who have been registered on the database of providers 26.1 .
  • the database of recipients 26.2 contains data of a number of recipients who form part of and subscribe to the system 10 and who have been registered on the database of recipients 26.2.
  • the processor 27 is operable to execute the server application 28 causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, as will be explained in more detail hereinbelow.
  • the applicant envisages that the server application 28 will be made available for a number of different platforms including, but not limited to, Windows ®; Linux ®, Mac OS®.
  • the server application 28 includes a data entry module 29, a communication module 30; a provider identification module 32; a recipient identification module 34 and an administrator authorization module 35.
  • the data entry module 29 is operable, when executed on the processor 27, to cause the processor 27 to accept input of the data of the providers and to store the data of the providers in the database of providers 26.1 .
  • the data entry module 29 is also operable, when executed on the processor 27, to cause the processor 27 to accept input of the data of the recipients and to store the data of the recipients in the database of recipients 26.2.
  • the communication module 30 is operable, when executed on the processor 27, to cause the processor 27 to send and receive authorization information via the communication network 18, as will be explained in more detail hereinbelow.
  • the provider identification module 32 is operable, when executed on the processor 27, to cause the processor 27 to search the database of providers 26.1 to identify a data record associated with a particular provider which is stored on the database of providers 26.1 , as will be explained in more detail hereinbelow.
  • the recipient identification module 34 is operable, when executed on the processor 27, to cause the processor 27 to search the database of recipients 26.2 to identify a data record associated with a particular recipient which is stored on the database of recipients 26.2, as will be explained in more detail hereinbelow.
  • the administrator authorization module 35 is operable, when executed on the processor 27, to cause the processor 27 to process authorization information received from the recipient mobile device 16 and the provider communication device 12; and to generate authorization request information, as will be explained in more detail hereinbelow.
  • the recipient mobile device is in the form of a "Smart Phone".
  • PDA personal digital assistant
  • Each recipient mobile device 16 is connected to the communication network 18 and has a processor 39 and computer program instructions in the form of a mobile device application 40 executable on the processor 39.
  • the processor 39 is operable to execute the mobile device application 40 causing the processor 39 to execute a method for automating authorization of the transaction between the provider and the recipient, as will be explained in more detail hereinbelow.
  • the mobile device application 40 includes a communication module 42 and a recipient response module 44.
  • the communication module 42 and the recipient response module 44 are each executed on the processor 39 to cause the processor 39 to execute various steps in a method for authorizing the transaction between the provider and the recipient, as will be explained in more detail hereinbelow.
  • the communication module 42 is operable when executed on the processor 39, to cause the processor 39 to send and receive authorization information to and from the administrator server system 14 via the communication network 18, as will be explained in more detail hereinbelow.
  • the recipient response module 44 is operable, when executed on the processor 39, to generate an alert prompting the recipient to input a response to authorization information received from the administrator server system 14, for authorizing or declining a transaction, as will be explained in more detail hereinbelow.
  • the recipient response module 44 is also operable to generate authorization information, as will be explained in more detail hereinbelow.
  • a method for authorizing a transaction between a provider of goods or services and a recipient of the goods or services is designated generally by the reference numeral 100.
  • the method 100 is illustrated by block diagrams showing various steps in the method which are executed, in use, by the provider application 20 of the provider communication device 12, the server application 28 of the administrator server system 14; and the mobile device application 40 of the recipient mobile device 16. It will be understood that it is the processors 19,27,39 which are operable to execute the applications 20,28,40, respectively, which cause the processors to execute the steps in the method.
  • the method 100 will be described as being implemented by the various modules of the applications 20,28,40 referred to above.
  • various steps in the method 100 which are executed, in use, by the provider application 20 of the provider communication device 12 are illustrated in a block diagram.
  • the Applicant envisages that the system 10 and method 100 may be used for authorizing debit and / or credit card transactions during "in-store” purchases and / or online / telephone purchases wherein the recipient purchase goods or services from the provider of the goods or services.
  • the Applicant envisages that a particular recipient will present his card at the provider's business premises to pay for the goods or services.
  • the card will be read by the credit card machine 21 of the provider communication device 12 and the method will proceed from step 1 1 1 , indicated in Figure 2 of the drawings.
  • the Applicant envisages that a particular recipient will provide his card number to the provider either verbally via the telephone or by entering his card number into a website of the provider. Once the recipient's card number is given to the provider then the method will, similarly, proceed from step 1 1 1 , indicated in Figure 2 of the drawings.
  • the communication module 22 of the provider application 20 of the provider communication device 12 sends authorization information in the form of a provider authorization request 46 to the administrator server system 14 via the communication network 18, requesting authorization for a transaction between the recipient and the provider.
  • the provider authorization request 46 includes sufficient information to identify the recipient, the provider and the details of the transaction for which authorization is requested. More specifically, the provider authorization request 46 includes a unique identifier code for identifying the provider, for example, the providers IP address and/or IMSI ; and a unique identifier code for identifying the recipient, such as, for example, the recipient's card number.
  • step 1 15 the communication module 30 of the server application 28 of the administrator server system 14 receives the provider authorization request 46 from the provider communication device 12, via the communication network 18, requesting authorization for the transaction between the provider and the recipient.
  • the provider identification module 32 searches the database of providers to attempt to identify a data record associated with a particular provider which is stored in the database of providers 26.1 , by comparing the information of the provider contained in the provider authorization request 46 with the data stored in the database of providers 26.1 to determine a match.
  • the determination of the match indicates that the particular provider is registered on the database of providers 26.1 , whereas the failure to determine the match indicates that the particular provider is not registered on the database of providers 26.1 .
  • the administrator authorization module 35 generates information in the form of an administrator authorization response 50 including sufficient information to identify the transaction and the administrator's response to decline the transaction.
  • the communication module 30 of the server application 28 sends the administrator authorization response 50 to the provider communication device 12 to decline the transaction.
  • the recipient identification module 34 of the server application 28 searches the database of recipients 26.2 to attempt to identify a data record associated with the recipient, which is stored on the database of recipients 26.2, by comparing the information of the recipient contained in the provider authorization request 46, with the data stored in the database of recipients 26.2, to determine a match.
  • the determination of the match indicates that the particular recipient is registered on the database of recipients 26.2, whereas the failure to determine the match indicates that the particular recipient is not registered on the database of recipients 26.2.
  • the Applicant envisages that the recipient's card number contained in the provider authorization request 46 will be used to identify the data record associated with the recipient.
  • the administrator authorization module 35 If the recipient identification module 34 determines, in step 124, that the recipient is not registered on the database of recipients 26.2, then in step 125, the administrator authorization module 35 generates information in the form of an administrator authorization response 50 including sufficient information to identify the transaction and the administrators response to decline the transaction. In step 128 the communication module 30 sends the administrator authorization response 50 to the provider communication device 12 to decline the transaction.
  • the recipient identification module 34 identifies, in step 124, that the data record of the recipient is stored in the database of recipients 26.2, then in step 131 the recipient identification module 34 reads the data record of the recipient contained in the database of recipients 26.2 and copies and transfers the data record of the recipient to the administrator authorization module 35, which thus receives details pertaining to the recipient, including details pertaining to the mobile device application 40 of the recipient and details of the recipients mobile device 16, such as, for example, the recipient's email address, mobile phone number, unique IMSI and unique IP address. As such, the IP address of the recipient's mobile device 15 is obtained for identifying the recipient on the communication network.
  • the administrator authorization module 35 Having now obtained the IP address of the recipient's mobile device, in step 132, the administrator authorization module 35 generates information in the form of an administrator authorization request 48 requesting authorization for the transaction between the recipient and the provider and including sufficient information to identify the transaction. In step 133 the communication module 30 sends the administrator authorization request 48 to the mobile device application 40 of the recipient mobile device 16 via the communication network 18, requesting authorization from the recipient for the transaction.
  • step 138 the communication module 42 of the mobile device application 40 receives the administrator authorization request 48 from the administrator server system 14 via the communication network 18, requesting authorization for a transaction between the recipient and the provider and containing sufficient information to identify the transaction.
  • step 140 the recipient response module 44 of the mobile device application 40 generates an alert prompting the recipient to input a response to the administrator authorization request 48, which is in the form of information authorizing or declining the administrator authorization request 48.
  • the recipient response module 44 in response to input of the recipient's response, the recipient response module 44 generates information in the form of a recipient authorization response 52 including sufficient information to identify the transaction and including the recipient's response, which is in the form of information authorizing or declining the administrator authorization request 48.
  • the communication module 42 sends, via the communication network 18, the recipient authorization response 52 to the administrator server system 14.
  • the recipient authorization response 52 includes sufficient information to identify the transaction and either the recipient's authorization for the transaction, or the recipient's declining of the transaction.
  • step 148 the communication module 30 of the server application 28 receives the recipient authorization response 52 from the recipient mobile device application 40 of the recipient mobile device 16 via the communication network 18.
  • step 150 the administrator authorization module 35 determines whether or not the transaction is authorized by the recipient, by analyzing the recipient authorization response 52.
  • step 150 the administrator authorization module 35 determines, in step 150, that the transaction is authorized by the recipient. If the administrator authorization module 35 determines, in step 150, that the transaction is authorized by the recipient, then, in step 151 , the administrator authorization module 35 generates an administrator authorization response 50 including sufficient information to identify the transaction and the recipient's response to the provider's request for authorization. In step 152, the communication module 30 of the server application 28 sends the administrator authorization response 50 to the provider communication device 12, authorizing the transaction.
  • step 150 the administrator authorization module 35 determines, in step 150, that the transaction is declined by the recipient. If the administrator authorization module 35 determines, in step 150, that the transaction is declined by the recipient, then, in step 155, the administrator authorization module 35 generates an administrator authorization response 50 including sufficient information to identify the transaction and the recipient's response declining the transaction. In step 156, the communication module 30 of the server application 28 sends, via the communication network 18, the administrator authorization response 50 to the provider communication device 12 declining the transaction.
  • the communication module 22 of the provider application 20 of the provider communication device 12 receives the administrator authorization response 50 from the administrator server system 14.
  • step 166 the provider authorization module 24 of the provider application 20 determines from the administrator authorization response 50 whether the transaction is authorized or declined.
  • step 166 the provider authorization module 24 determines, in step 166, that the transaction is declined, then in step 168 the provider authorization module 24 notifies the provider that the transaction has been declined by the recipient. If the provider authorization module 24 determines, in step 166, that the transaction is authorized by the recipient, then in step 172, the transaction is processed by the credit card machine 21 , as per normal known credit / debit card processing procedures.
  • the Applicant envisages that the system 10 and method 100 will assist in ameliorating fraudulent and unauthorized use of the recipient's card and/or the recipient's card number. Specifically, it is envisaged that, if the recipient's card and/or the recipient's card number, is used without the recipient's knowledge and/or authority, then the recipient will merely decline the transaction after the administrator authorization request information 48 is received by the recipient mobile device 16. As such, an extra level of security is provided for authorizing and securing credit / debit card transaction.
  • the invention extends to the administrator server system 14, as defined and described hereinabove.
  • the invention extends also to a provider communication device 12 having stored therein the provider application 20, as described and defined hereinabove.
  • the invention extends further to a mobile device having stored thereon the mobile device application 40, as described and defined hereinabove.
  • the invention extends also to both the system 10 and the method 100 which are described and defined hereinabove. It will be appreciated that the exact configuration of the server, in accordance with the invention, and the mobile device, in accordance with the invention, may each vary greatly, while still incorporating the essential features of the invention, as described hereinabove. The invention clearly extends to all such variations, which still incorporate the essential principles of the invention as above described and defined.
  • the Applicant envisages that the system 10 and method 100, as described and defined hereinabove, may also be used in other applications, other than the application described hereinabove. More specifically, the Applicant envisages that the system and method, as described and defined above, may be used for authorizing any type of an online transaction such as, for example, authorizing access to a companies' email server granted to employees of the company. In such an application, the Applicant envisages that a company which wishes to grant authorized access to its email server to employees of the company will constitute the provider. As such, the companies email server will constitute the provider communication device and each employee who registers and subscribes to the system for authorizing a transaction, will constitute recipients of the system and their mobile devices will each constitute recipient mobile devices.
  • each recipient will not receive a card and a card number, as described hereinabove, in relation to the system 10 and the method 100. Instead, the Applicant envisages that each recipient will receive a recipient card and a unique recipient identifier number, which are similar to the card and the card number, respectively, described hereinabove.
  • the recipient wishes to log onto the provider's company email server, in use, then the recipient will access a gateway to the companies email server, via the internet, and enter his unique recipient identifier number into a field provided therefore.
  • the companies email server which constitutes the provider communication device, will send provider authorization request information including sufficient information to identify the transaction, to the administrator server system via the communication network, and the recipient's authorization will be obtained and access to the companies email server granted in a manner similar to that described hereinabove in relation to the system 10 and method 100. As such, an extra level of security is provided for authorizing and securing any type of an online transaction.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

An administrator server system 14 for authorizing a transaction between a provider and a recipient and includes a server database 26; a processor 27 and a server application 28 executed on the processor 27. The processor is operable to execute a method wherein the processor 27 is operable to receive a provider authorization request 46 via a communication network 18 from a provider communication device 12 requesting authorization for the transaction. In response, the processor is also operable to generate an administrator authorization request 48; and send the request 48 via the network 18 to a mobile device application 40 of a mobile device 16 of the recipient. The processor 27 is further operable to receive a recipient authorization response 52 via the network 18 from the application 40, authorizing or declining the request 48. In response, the processor 27 is operable to generate an administrator authorization response 50 including the recipient's response; and to send the response 50 to the device 12 via the network 18, authorizing or declining the transaction.

Description

A SERVER AND MOBILE DEVICE FOR AUTHORIZING A TRANSACTION
FIELD OF INVENTION This invention relates to a server for authorizing a transaction between a provider of goods or services and a recipient of the goods or services. This invention relates also to a mobile device for authorizing a transaction between a provider of goods or services and a recipient of the goods or services. SUMMARY OF INVENTION
According to a first aspect of the invention there is provided a server for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, the server being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving a provider authorization request via the communication network from a provider communication device associated with the provider, requesting authorization for the transaction between the recipient and the provider, the provider authorization request including sufficient information to identify the transaction; in response to receipt of the provider authorization request, the processor generating an administrator authorization request requesting authorization for the transaction between the recipient and the provider and including sufficient information to identify the transaction; and sending the administrator authorization request via the communication network to a mobile device application of a mobile device of the recipient; the processor receiving a recipient authorization response via the communication network from the mobile device application of the mobile device of the recipient, the recipient authorization response containing information sufficient to identify the transaction and the recipient's response which is in the form of information authorizing or declining the administrator authorization request; and in response to receipt of the recipient authorization response, the processor generating an administrator authorization response including sufficient information to identify the transaction and the recipient's response; and sending the administrator authorization response to the provider communication device of the provider, via the communication network. The server may include a database. The processor may be operable to execute computer program instructions including a data entry module causing the processor to accept input of data pertaining to a number of recipients and a number of providers; and to store the data in the database. The processor may be operable to execute computer program instructions including a provider identification module causing the processor to search the database to identify a data record associated with a particular provider which is stored in the database, by comparing information of the provider contained in the provider authorization request, with the data stored in the database to determine a match. The processor may be operable to execute computer program instructions including a recipient identification module causing the processor to search the database to identify a data record associated with a particular recipient which is stored in the database, by comparing information of the recipient contained in the provider authorization request, with the data stored in the database to determine a match.
According to a second aspect of the invention there is provided a mobile device for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, the mobile device being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving an administrator authorization request via the communication network from an administrator server, requesting authorization for the transaction between the recipient associated with the mobile device and the provider, the administrator authorization request containing information sufficient to identify the transaction; in response to receipt of the administrator authorization request, the processor generating an alert on the mobile device prompting the recipient to input a response to the administrator authorization request which is in the form of information authorizing or declining the administrator authorization request; and in response to input of the recipient's response, the processor generating a recipient authorization response including information sufficient to identify the transaction and the recipient's response and sending the recipient authorization response to the administrator server via the communication network. BRIEF DESCRITION OF THE DRAWINGS
Further features of the invention are described hereinafter by way of a non-limiting example of the invention, with reference to and as illustrated in the accompanying schematic block diagrams. In the drawings:
Figure 1 shows a block diagram of a provider communication device, a server in accordance with the invention and a mobile device in accordance with the invention, shown, in use, in a system and method for authorizing a transaction between a provider of goods or services and a recipient of the goods or services;
Figures 2 show various steps in the method which is executed on the provider communication device of Figure 1 ; Figures 3a and 3b show various steps in the method which are executed on the server of Figure 1 ; and
Figures 4 shows various steps in the method which are executed on the mobile device of Figure 1 ;
DETAILED DESCRIPTION OF THE DRAWINGS
With reference to Figure 1 of the drawings, a system for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, is designated generally by the reference numeral 10.
The system 10 includes broadly, a plurality of provider communication devices 12 which are each associated with a particular provider; a server, in accordance with a first aspect of the invention, in the form of an administrator server system, designated generally by the reference numeral 14; and a plurality of mobile devices, in accordance with a second aspect of the invention, in the form of recipient mobile devices which are each designated generally by the reference numeral 16 and which are each associated with a particular recipient. The Applicant envisages that providers of goods or services and recipients of the goods or services will subscribe to the system 10. Typically, the providers and recipients will register and subscribe to the system 10 by providing an administrator of the administrator server system 14 all their relevant details including their full contact details such as, for example, cellular phone numbers, physical address, telephone numbers, and unique International Mobile Subscriber Identity (IMSI) stored on the Subscriber Identification Module (SIM) of their devices which are connected to the communication network. Furthermore, the providers and recipients will provide the administrator with their unique Internet Protocol (IP) addresses of their devices which are connected to the communication network. The Applicant envisages that the system 10 may either be used in a commercial environment or, alternatively, may be used for securing online transactions, as will be explained in more detail hereinbelow. In an application wherein the system 10 is used in a commercial environment, the Applicant envisages that the providers will be, for example, in the form of merchants, or any supplier of any goods or any services and the recipients will be, for example, in the form of customers, or clients. The recipients will each receive a card for making payment for goods or services at providers who subscribe to the system 10. Furthermore, the applicant envisages that the recipients will be issued with card numbers for making online and telephonic payments to providers who subscribe to the system 1 0, as will be explained in more detail hereinbelow. The cards and card numbers will be linked to an existing bank facility of each recipient such as, for example, a credit card; a cheque card or a debit card. The providers and recipients will subscribe to the system 10 in order to enhance the security of credit and/or debit card transactions. The system 10 enhances the security of the transactions by requiring the providers to obtain the recipients' prior authorization for the transactions, as will be explained in more detail hereinbelow. Each provider communication device 12 is connected to, and is operable to send and receive authorization information to and from the administrator server system 14 via a communication network 18 such as, for example, a cellular communications network, telephone network, wireless data network, Internet, or the like, as will be explained in more detail hereinbelow. The provider communication device 12 includes a processor 19 operable to execute computer program instructions in the form of a provider application 20 which is executable on the processor 19 of the provider communication device 12; and a credit card machine 21 including a card reader for reading the cards of recipients. The provider application 20 includes a communication module 22 for sending and receiving authorization information to and from the administrator server system 14 via the communication network 18; and a provider authorization module 24, for generating and interpreting authorization information sent from and received by the communication module 22, as will be described in more detail hereinbelow. The administrator server system 14 is connected to the communication network 18 and includes a server database 26 for storing data of a number of recipients and providers, a processor 27 and computer program instructions in the form of a server application 28 executable on the processor 27. The server database 26 includes a database of providers 26.1 and a database of recipients 26.2. The database of providers 26.1 contains data of a number of providers who form part of and subscribe to the system 10 and who have been registered on the database of providers 26.1 . The database of recipients 26.2 contains data of a number of recipients who form part of and subscribe to the system 10 and who have been registered on the database of recipients 26.2.
The processor 27 is operable to execute the server application 28 causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, as will be explained in more detail hereinbelow. The applicant envisages that the server application 28 will be made available for a number of different platforms including, but not limited to, Windows ®; Linux ®, Mac OS®. The server application 28 includes a data entry module 29, a communication module 30; a provider identification module 32; a recipient identification module 34 and an administrator authorization module 35. The data entry module 29 is operable, when executed on the processor 27, to cause the processor 27 to accept input of the data of the providers and to store the data of the providers in the database of providers 26.1 . The data entry module 29 is also operable, when executed on the processor 27, to cause the processor 27 to accept input of the data of the recipients and to store the data of the recipients in the database of recipients 26.2. The communication module 30 is operable, when executed on the processor 27, to cause the processor 27 to send and receive authorization information via the communication network 18, as will be explained in more detail hereinbelow. The provider identification module 32 is operable, when executed on the processor 27, to cause the processor 27 to search the database of providers 26.1 to identify a data record associated with a particular provider which is stored on the database of providers 26.1 , as will be explained in more detail hereinbelow. The recipient identification module 34 is operable, when executed on the processor 27, to cause the processor 27 to search the database of recipients 26.2 to identify a data record associated with a particular recipient which is stored on the database of recipients 26.2, as will be explained in more detail hereinbelow. The administrator authorization module 35 is operable, when executed on the processor 27, to cause the processor 27 to process authorization information received from the recipient mobile device 16 and the provider communication device 12; and to generate authorization request information, as will be explained in more detail hereinbelow.
The recipient mobile device is in the form of a "Smart Phone". The applicant envisages that the recipient mobile device 16 may, alternatively, be in the form of, for example, a personal digital assistant (PDA); a laptop; a tablet, or the like. Each recipient mobile device 16 is connected to the communication network 18 and has a processor 39 and computer program instructions in the form of a mobile device application 40 executable on the processor 39. The processor 39 is operable to execute the mobile device application 40 causing the processor 39 to execute a method for automating authorization of the transaction between the provider and the recipient, as will be explained in more detail hereinbelow. The applicant envisages that the mobile device application 40 will be made available for a number of different platforms such as Android®; Blackberry OS®; IOS®; Palm OS®; Windows Mobile®; Windows®; Linux®; MacOS®, and the like. The mobile device application 40 includes a communication module 42 and a recipient response module 44. The communication module 42 and the recipient response module 44 are each executed on the processor 39 to cause the processor 39 to execute various steps in a method for authorizing the transaction between the provider and the recipient, as will be explained in more detail hereinbelow. The communication module 42 is operable when executed on the processor 39, to cause the processor 39 to send and receive authorization information to and from the administrator server system 14 via the communication network 18, as will be explained in more detail hereinbelow. The recipient response module 44 is operable, when executed on the processor 39, to generate an alert prompting the recipient to input a response to authorization information received from the administrator server system 14, for authorizing or declining a transaction, as will be explained in more detail hereinbelow. The recipient response module 44 is also operable to generate authorization information, as will be explained in more detail hereinbelow.
With reference to Figure 1 of the drawings, a method for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, is designated generally by the reference numeral 100. With reference to Figures 2 to 4 of the drawings, the method 100 is illustrated by block diagrams showing various steps in the method which are executed, in use, by the provider application 20 of the provider communication device 12, the server application 28 of the administrator server system 14; and the mobile device application 40 of the recipient mobile device 16. It will be understood that it is the processors 19,27,39 which are operable to execute the applications 20,28,40, respectively, which cause the processors to execute the steps in the method. However, for convenience and ease of understanding, the method 100 will be described as being implemented by the various modules of the applications 20,28,40 referred to above. With reference to Figure 2 of the drawings, various steps in the method 100 which are executed, in use, by the provider application 20 of the provider communication device 12, are illustrated in a block diagram.
The Applicant envisages that the system 10 and method 100 may be used for authorizing debit and / or credit card transactions during "in-store" purchases and / or online / telephone purchases wherein the recipient purchase goods or services from the provider of the goods or services.
In the case of in-store debit / credit card purchases, the Applicant envisages that a particular recipient will present his card at the provider's business premises to pay for the goods or services. The card will be read by the credit card machine 21 of the provider communication device 12 and the method will proceed from step 1 1 1 , indicated in Figure 2 of the drawings. In the case of online / telephone purchases, the Applicant envisages that a particular recipient will provide his card number to the provider either verbally via the telephone or by entering his card number into a website of the provider. Once the recipient's card number is given to the provider then the method will, similarly, proceed from step 1 1 1 , indicated in Figure 2 of the drawings.
Referring to Figure 2 of the drawings, in step 1 1 1 the communication module 22 of the provider application 20 of the provider communication device 12 sends authorization information in the form of a provider authorization request 46 to the administrator server system 14 via the communication network 18, requesting authorization for a transaction between the recipient and the provider. The provider authorization request 46 includes sufficient information to identify the recipient, the provider and the details of the transaction for which authorization is requested. More specifically, the provider authorization request 46 includes a unique identifier code for identifying the provider, for example, the providers IP address and/or IMSI ; and a unique identifier code for identifying the recipient, such as, for example, the recipient's card number.
With reference to Figures 3a and 3b of the drawings the various steps in the method 100 which are executed, in use, by the server application 28 of the administrator server system 14, are illustrated in a block diagram.
As shown in Figure 3a of the drawings, in step 1 15 the communication module 30 of the server application 28 of the administrator server system 14 receives the provider authorization request 46 from the provider communication device 12, via the communication network 18, requesting authorization for the transaction between the provider and the recipient.
In steps 1 16 and 1 18 the provider identification module 32 searches the database of providers to attempt to identify a data record associated with a particular provider which is stored in the database of providers 26.1 , by comparing the information of the provider contained in the provider authorization request 46 with the data stored in the database of providers 26.1 to determine a match. The determination of the match indicates that the particular provider is registered on the database of providers 26.1 , whereas the failure to determine the match indicates that the particular provider is not registered on the database of providers 26.1 .
More specifically, if the provider identification module 32 determines, in step 1 16, that the provider is not registered on the database of providers 26.1 then in step 1 19, the administrator authorization module 35 generates information in the form of an administrator authorization response 50 including sufficient information to identify the transaction and the administrator's response to decline the transaction. In step 120, the communication module 30 of the server application 28 sends the administrator authorization response 50 to the provider communication device 12 to decline the transaction. More specifically, if the provider identification module 32 identifies the data record of the provider and determines, in step 1 16, that the provider is registered on the database of providers 26.1 , then in steps 124 and 126, the recipient identification module 34 of the server application 28 searches the database of recipients 26.2 to attempt to identify a data record associated with the recipient, which is stored on the database of recipients 26.2, by comparing the information of the recipient contained in the provider authorization request 46, with the data stored in the database of recipients 26.2, to determine a match. The determination of the match indicates that the particular recipient is registered on the database of recipients 26.2, whereas the failure to determine the match indicates that the particular recipient is not registered on the database of recipients 26.2. The Applicant envisages that the recipient's card number contained in the provider authorization request 46 will be used to identify the data record associated with the recipient.
If the recipient identification module 34 determines, in step 124, that the recipient is not registered on the database of recipients 26.2, then in step 125, the administrator authorization module 35 generates information in the form of an administrator authorization response 50 including sufficient information to identify the transaction and the administrators response to decline the transaction. In step 128 the communication module 30 sends the administrator authorization response 50 to the provider communication device 12 to decline the transaction.
If the recipient identification module 34 identifies, in step 124, that the data record of the recipient is stored in the database of recipients 26.2, then in step 131 the recipient identification module 34 reads the data record of the recipient contained in the database of recipients 26.2 and copies and transfers the data record of the recipient to the administrator authorization module 35, which thus receives details pertaining to the recipient, including details pertaining to the mobile device application 40 of the recipient and details of the recipients mobile device 16, such as, for example, the recipient's email address, mobile phone number, unique IMSI and unique IP address. As such, the IP address of the recipient's mobile device 15 is obtained for identifying the recipient on the communication network. The applicant envisages that the unique IMSI can then be used in addition to, or in substitution of, the IP address, in order to identify the recipient on the communication network. Having now obtained the IP address of the recipient's mobile device, in step 132, the administrator authorization module 35 generates information in the form of an administrator authorization request 48 requesting authorization for the transaction between the recipient and the provider and including sufficient information to identify the transaction. In step 133 the communication module 30 sends the administrator authorization request 48 to the mobile device application 40 of the recipient mobile device 16 via the communication network 18, requesting authorization from the recipient for the transaction.
With reference to Figure 4 of the drawings the various steps in the method 100 executed by the mobile device application 40 of the recipient mobile device 16, are illustrated in a block diagram.
In step 138 the communication module 42 of the mobile device application 40 receives the administrator authorization request 48 from the administrator server system 14 via the communication network 18, requesting authorization for a transaction between the recipient and the provider and containing sufficient information to identify the transaction.
In step 140 the recipient response module 44 of the mobile device application 40 generates an alert prompting the recipient to input a response to the administrator authorization request 48, which is in the form of information authorizing or declining the administrator authorization request 48.
In step 141 , in response to input of the recipient's response, the recipient response module 44 generates information in the form of a recipient authorization response 52 including sufficient information to identify the transaction and including the recipient's response, which is in the form of information authorizing or declining the administrator authorization request 48. In step 142 the communication module 42 sends, via the communication network 18, the recipient authorization response 52 to the administrator server system 14. In use, the recipient authorization response 52 includes sufficient information to identify the transaction and either the recipient's authorization for the transaction, or the recipient's declining of the transaction.
With reference to Figure 3b of the drawings, the further steps in the method 100 which are executed by the server application 28 of the administrator server system 14, are illustrated in a block diagram.
In step 148 the communication module 30 of the server application 28 receives the recipient authorization response 52 from the recipient mobile device application 40 of the recipient mobile device 16 via the communication network 18.
In step 150 the administrator authorization module 35 determines whether or not the transaction is authorized by the recipient, by analyzing the recipient authorization response 52.
If the administrator authorization module 35 determines, in step 150, that the transaction is authorized by the recipient, then, in step 151 , the administrator authorization module 35 generates an administrator authorization response 50 including sufficient information to identify the transaction and the recipient's response to the provider's request for authorization. In step 152, the communication module 30 of the server application 28 sends the administrator authorization response 50 to the provider communication device 12, authorizing the transaction.
If the administrator authorization module 35 determines, in step 150, that the transaction is declined by the recipient, then, in step 155, the administrator authorization module 35 generates an administrator authorization response 50 including sufficient information to identify the transaction and the recipient's response declining the transaction. In step 156, the communication module 30 of the server application 28 sends, via the communication network 18, the administrator authorization response 50 to the provider communication device 12 declining the transaction.
With reference again to Figure 2 of the drawings, in step 162, the communication module 22 of the provider application 20 of the provider communication device 12 receives the administrator authorization response 50 from the administrator server system 14.
In step 166, the provider authorization module 24 of the provider application 20 determines from the administrator authorization response 50 whether the transaction is authorized or declined.
If the provider authorization module 24 determines, in step 166, that the transaction is declined, then in step 168 the provider authorization module 24 notifies the provider that the transaction has been declined by the recipient. If the provider authorization module 24 determines, in step 166, that the transaction is authorized by the recipient, then in step 172, the transaction is processed by the credit card machine 21 , as per normal known credit / debit card processing procedures.
The Applicant envisages that the system 10 and method 100 will assist in ameliorating fraudulent and unauthorized use of the recipient's card and/or the recipient's card number. Specifically, it is envisaged that, if the recipient's card and/or the recipient's card number, is used without the recipient's knowledge and/or authority, then the recipient will merely decline the transaction after the administrator authorization request information 48 is received by the recipient mobile device 16. As such, an extra level of security is provided for authorizing and securing credit / debit card transaction.
The applicant envisages that the recipient's information will be kept strictly confidential and that the provider will only require the card or the card number of the recipient in order to request authorization for the transaction. As such, none of the other personal details of the recipient need be given to the provider in order to obtain authorization for the transaction.
The invention extends to the administrator server system 14, as defined and described hereinabove. The invention extends also to a provider communication device 12 having stored therein the provider application 20, as described and defined hereinabove. The invention extends further to a mobile device having stored thereon the mobile device application 40, as described and defined hereinabove. The invention extends also to both the system 10 and the method 100 which are described and defined hereinabove. It will be appreciated that the exact configuration of the server, in accordance with the invention, and the mobile device, in accordance with the invention, may each vary greatly, while still incorporating the essential features of the invention, as described hereinabove. The invention clearly extends to all such variations, which still incorporate the essential principles of the invention as above described and defined.
The Applicant envisages that the system 10 and method 100, as described and defined hereinabove, may also be used in other applications, other than the application described hereinabove. More specifically, the Applicant envisages that the system and method, as described and defined above, may be used for authorizing any type of an online transaction such as, for example, authorizing access to a companies' email server granted to employees of the company. In such an application, the Applicant envisages that a company which wishes to grant authorized access to its email server to employees of the company will constitute the provider. As such, the companies email server will constitute the provider communication device and each employee who registers and subscribes to the system for authorizing a transaction, will constitute recipients of the system and their mobile devices will each constitute recipient mobile devices.
In use, the Applicant envisages that each recipient will not receive a card and a card number, as described hereinabove, in relation to the system 10 and the method 100. Instead, the Applicant envisages that each recipient will receive a recipient card and a unique recipient identifier number, which are similar to the card and the card number, respectively, described hereinabove. When the recipient wishes to log onto the provider's company email server, in use, then the recipient will access a gateway to the companies email server, via the internet, and enter his unique recipient identifier number into a field provided therefore.
The companies email server which constitutes the provider communication device, will send provider authorization request information including sufficient information to identify the transaction, to the administrator server system via the communication network, and the recipient's authorization will be obtained and access to the companies email server granted in a manner similar to that described hereinabove in relation to the system 10 and method 100. As such, an extra level of security is provided for authorizing and securing any type of an online transaction.

Claims

CLAIMS:
1 . A server for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, the server being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving a provider authorization request via the communication network from a provider communication device associated with the provider, requesting authorization for the transaction between the recipient and the provider, the provider authorization request including sufficient information to identify the transaction; in response to receipt of the provider authorization request, the processor generating an administrator authorization request requesting authorization for the transaction between the recipient and the provider and including sufficient information to identify the transaction; and sending the administrator authorization request via the communication network, to a mobile device application of a mobile device of the recipient; the processor receiving a recipient authorization response via the communication network from the mobile device application of the mobile device of the recipient, the recipient authorization response containing information sufficient to identify the transaction and the recipient's response which is in the form of information authorizing or declining the administrator authorization request; and in response to receipt of the recipient authorization response, the processor generating an administrator authorization response including sufficient information to identify the transaction and the recipient's response; and sending the administrator authorization response to the provider communication device of the provider, via the communication network.
2. A server as claimed in Claim 1 , wherein the server includes a database and wherein the processor is operable to execute computer program instructions including a data entry module causing the processor to accept input of data pertaining to a number of recipients and a number of providers; and to store the data in the database.
3. A server as claimed in Claim 2, wherein the processor is operable to execute computer program instructions including a provider identification module causing the processor to search the database to identify a data record associated with a particular provider which is stored in the database, by comparing information of the provider contained in the provider authorization request, with the data stored in the database to determine a match.
4. A server as claimed in Claim 2, wherein the processor is operable to execute computer program instructions including a recipient identification module causing the processor to search the database to identify a data record associated with a particular recipient which is stored in the database, by comparing information of the recipient contained in the provider authorization request, with the data stored in the database to determine a match.
5. A mobile device for authorizing a transaction between a provider of goods or services and a recipient of the goods or services, the mobile device being connected to a communication network and including: a processor operable to execute computer program instructions causing the processor to execute a method for automating authorization of the transaction between the provider and the recipient, the method comprising: the processor receiving an administrator authorization request via the communication network from an administrator server, requesting authorization for the transaction between the recipient associated with the mobile device and the provider, the administrator authorization request containing information sufficient to identify the transaction; in response to receipt of the administrator authorization request, the processor generating an alert on the mobile device prompting the recipient to input a response to the administrator authorization request which is in the form of information authorizing or declining the administrator authorization request; and in response to input of the recipient's response, the processor generating a recipient authorization response including information sufficient to identify the transaction and the recipient's response and sending the recipient authorization response to the administrator server via the communication network.
PCT/IB2013/053205 2012-04-23 2013-04-23 A server and mobile device for authorizing a transaction WO2013160830A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ZA201202964 2012-04-23
ZA2012/02964 2012-04-23

Publications (1)

Publication Number Publication Date
WO2013160830A1 true WO2013160830A1 (en) 2013-10-31

Family

ID=48576477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2013/053205 WO2013160830A1 (en) 2012-04-23 2013-04-23 A server and mobile device for authorizing a transaction

Country Status (1)

Country Link
WO (1) WO2013160830A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190228136A1 (en) * 2018-01-25 2019-07-25 Oracle International Corporation Integrated context-aware software applications

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10025565A1 (en) * 2000-03-01 2001-09-06 Siemens Ag Arrangement for acknowledging credit card payment transaction via mobile telephone has central processing unit that sends data to mobile terminal in response data acquired by reader unit
EP1180757A1 (en) * 2000-08-18 2002-02-20 Siemens Aktiengesellschaft Method and arrangement for the transaction of electronic money from a prepaid account
WO2004070492A2 (en) * 2003-02-03 2004-08-19 Mega-Tel Ag/Sa Verification of credit card transactions
WO2008015637A2 (en) * 2006-08-02 2008-02-07 Firstrand Bank Limited Mobile payment method and system
WO2008045007A2 (en) * 2006-10-10 2008-04-17 Baknet Iletisim Ve Bilgisayar Urunleri Pazarlama Sanayi Ve Ticaret Anonim Sirketi The method for credit card and atm transaction by mobile device
WO2009012731A1 (en) * 2007-07-26 2009-01-29 Direct Pay, S.R.O. Method of effecting payment transaction using a mobile terminal
WO2009069905A2 (en) * 2007-11-28 2009-06-04 Harex Infotech Inc. System for mobile payment service using phone number and method thereof
EP2189932A1 (en) * 2008-11-24 2010-05-26 Research in Motion Electronic payment system using mobile wireless communications device and associated methods
US20110276486A1 (en) * 2010-05-10 2011-11-10 Kuba Nir System and method for securing payment

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10025565A1 (en) * 2000-03-01 2001-09-06 Siemens Ag Arrangement for acknowledging credit card payment transaction via mobile telephone has central processing unit that sends data to mobile terminal in response data acquired by reader unit
EP1180757A1 (en) * 2000-08-18 2002-02-20 Siemens Aktiengesellschaft Method and arrangement for the transaction of electronic money from a prepaid account
WO2004070492A2 (en) * 2003-02-03 2004-08-19 Mega-Tel Ag/Sa Verification of credit card transactions
WO2008015637A2 (en) * 2006-08-02 2008-02-07 Firstrand Bank Limited Mobile payment method and system
WO2008045007A2 (en) * 2006-10-10 2008-04-17 Baknet Iletisim Ve Bilgisayar Urunleri Pazarlama Sanayi Ve Ticaret Anonim Sirketi The method for credit card and atm transaction by mobile device
WO2009012731A1 (en) * 2007-07-26 2009-01-29 Direct Pay, S.R.O. Method of effecting payment transaction using a mobile terminal
WO2009069905A2 (en) * 2007-11-28 2009-06-04 Harex Infotech Inc. System for mobile payment service using phone number and method thereof
EP2189932A1 (en) * 2008-11-24 2010-05-26 Research in Motion Electronic payment system using mobile wireless communications device and associated methods
US20110276486A1 (en) * 2010-05-10 2011-11-10 Kuba Nir System and method for securing payment

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190228136A1 (en) * 2018-01-25 2019-07-25 Oracle International Corporation Integrated context-aware software applications
US10984079B2 (en) * 2018-01-25 2021-04-20 Oracle International Corporation Integrated context-aware software applications

Similar Documents

Publication Publication Date Title
US10552828B2 (en) Multiple tokenization for authentication
CN109658103B (en) Method, device and equipment for identity authentication, number storage and sending and number binding
US9805368B2 (en) End-to end secure payment processes
US8239325B2 (en) Method and system to verify the identity of a user
US20100094732A1 (en) Systems and Methods to Verify Payment Transactions
US20070063017A1 (en) System and method for securely making payments and deposits
US20140136352A1 (en) Social Network-Assisted Electronic Payments
US20120059758A1 (en) Protecting Express Enrollment Using a Challenge
US8831979B1 (en) System and method for anonymous processing of financial transactions
WO2016187662A1 (en) Secure payment
KR20140125449A (en) Transaction processing system and method
MX2011002067A (en) System and method of secure payment transactions.
US20120072346A1 (en) System and method for securing and authenticating purchase transactions
US20170186014A1 (en) Method and system for cross-authorisation of a financial transaction made from a joint account
US20210406909A1 (en) Authorizing transactions using negative pin messages
US10769631B2 (en) Providing payment credentials securely for telephone order transactions
WO2019178075A1 (en) Digital access code
KR20130014947A (en) Credit transactions system, apparatus, terminal capable of granting credit and method therefor
WO2013160830A1 (en) A server and mobile device for authorizing a transaction
US20240070677A1 (en) Aggregated transaction accounts
US20220253512A1 (en) Authenticating and verifying users with unique identification numbers and finger vein patterns
John METHOD AND SYSTEM FOR SECURE CREDENTIAL GENERATION
EP4338371A1 (en) Method and system for identity verification in a telecommunication network and a verification service
KR20100089156A (en) Card payment service system and method using smart card embedded mobile communication terminal
WO2016016876A1 (en) Transactions processing system and method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13726877

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13726877

Country of ref document: EP

Kind code of ref document: A1