Method for increasing the security of payment of tradesman by a client, corresponding localization center and system

• US 20020174068A1
• Filed: 04/29/2002
• Published: 11/21/2002
• Est. Priority Date: 05/07/2001
• Status: Abandoned Application

• Current Assignee: Cegetel Groupe
• Original Assignee: Cegetel Groupe
• Inventors: Marsot, Rodolphe
• Application Number:
  US10/137,672
• Publication Number:
  US 20020174068A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 20/425 using two different networks, one for transaction and one for security confirmation
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02

Abstract

The invention concerns a security method for a payment from a client to a supplier, including a transmission step to a management center of a payment request including at least one identifier of said client, according to a predefined protocol.

Set forth in the invention, such a process includes a validation step wherein:

said management center generates a validation request, to the attention of said client, according to a second protocol independent from said first protocol, to an address indicated by said client;

a transmission is made in the name of said client of a payment validation or refusal message, according to said second protocol.

Claims

1. Security method for payment from a client to a supplier, including a step wherein a payment request including at least one identifier of said client is transmitted to a management center, according to a previously defined protocol,

characterized in that it contains a validation step according to which:

said management center manages a validation request, to the attention of said client, according to a second protocol independent from said first protocol, to an address indicated by said client;

a message of payment validation or refusal is transmitted in the name of said client, as set forth in the second protocol.

2. Security method according to claim 1, characterized in that said client is equipped with a terminal that possesses means of radio-communication.

3. Security method according to claim 1 or 2, characterized in that said second protocol is the SIP protocol.

4. Security method according to claim 3, characterized in that said validation request is managed in the form of an “

INVITE”

message.

5. Security method according to any of claims 1 through 4, characterized in that they include the following steps:

(a) receipt, by said management center, of a payment request sent by said supplier;

(b) transmission of a validation request from said management center to a localization server;

(c) identification of a proxy server wherein said client is saved, by said localization server;

(d) transmission of said validation request to said proxy server;

(e) transmission by said proxy server of said response to said management center.

6. Security method according to claim 5, characterized in that it further includes, after said transmission step of said validation request to said proxy server, the following steps among others:

(dbis) transmission by said proxy server of said validation request to said client equipped with a terminal;

(dter) transmission by said client equipped with a terminal of a response to said validation request, to said proxy server;

such that said proxy server transmits said response to said management center.

7. Security method according to claim 6, characterized in that when the client is equipped with a terminal, said steps (dbis) and (dter) set up a transmission using at least one of the techniques from a group that includes:

short messages (SMS);

telephone communications;

electronic messages.

8. Security method according to any of claims 1 through 7, characterized in that said management center and/or said proxy server set up a validation request procedure only in predetermined cases.

9. Security method according to claim 8, characterized in that said predetermined cases depend on at least one of the following parameters:

transaction amount;

client type;

supplier type;

proxy server type.

10. Security method according to any of claims 8 and 9, characterized in that at least one of the parameters of said predetermined cases are configurable by at least one of the following interveners:

the client;

the supplier;

the management center;

the proxy server.

11. Security method according to any of claims 1 through 10, characterized in that a response to a validation request may be one of three types:

positive response;

negative response;

absence of a response.

12. Security method according to claim 11, characterized in that the absence of a response is interpreted by said proxy server and/or by said management center as a negative response.

13. Security method according to any of claims 1 through 12, characterized in that said management center only executes all bank processing related to said payment after receiving a positive response to said validation request.

14. Security method according to any of claims 1 through 13, characterized in that said payment is made using a bank card.

15. Localization center of at least one client, that sets up the process according to any of claims 1 through 14.

16. Security method for payments amongst a plurality of clients and suppliers, characterized in that it sets up a localization server, capable of receiving validation requests from at least one management center from which a payment was required, of transmitting said validation requests to terminals held respectively by each of said clients, and of receiving and passing on a response to said validation request, sent by said client using their terminal.