A METHOD TO VALIDATE A DYNAMIC SECURITY CODE IN A PAYMENT TRANSACTION

1 . A method to validate a dynamic security code generated for a payment transaction, said method comprising the steps of:

providing for a given payment transaction a dynamic security code associated to an identifier of said transaction;

verifying using a verification memory if the provided dynamic security code has already been validated when associated to the same associated identifier;

if not, verifying the validity of the provided dynamic security code;

if the provided dynamic security code is valid, memorizing in the verification memory the provided dynamic security code, the associated identifier of the payment transaction.

2 . The method according to claim 1 , wherein the identifier of the payment transaction is the amount of said transaction.

3 . The method according to claim 1 , wherein the identifier of the payment transaction is a challenge code.

4 . The method according to claim 1 comprising a step of approving the payment transaction once the validity of the dynamic security code is validated.

5 . The method according to claim 1 comprising a step of declining the payment transaction applied if another payment transaction has already been approved using the same dynamic security code associated to the same transaction identifier.

6 . The method according claim 1 , wherein the validated dynamic security codes are stored with their associated payment transaction identifier together and with a date of at which the transaction was initiated.

7 . The method according to claim 1 , wherein the validated dynamic security codes are stored with their associated payment transaction identifier together with a time counter data associated to or embedded in the dynamic security code of the received set of data.

8 . The method according to claim 1 , wherein a set of data comprising a validated dynamic security codes and an associated payment transaction identifier is removed from the verification memory depending on predefined expiration data such as a cryptographic key, an increasing counter or a data.

9 . The method according to claim 1 , wherein the step of verifying if a dynamic secure code has already been validated is carried out by verifying if said dynamic secure code and the associated identifier of the payment transaction are comprised in a verification list memorized in the verification memory.

10 . The method according to claim 1 , wherein the step of verifying if a dynamic secure code has already been validated is carried out by verifying if said dynamic secure code and the associated identifier of the payment transaction for less than a predefined time period.

11 . The method according to claim 1 , wherein the dynamic secure code is a Dynamic CVV.

12 . A dynamic security code verification system adapted to implement a method comprising the steps of:

providing for a given payment transaction a dynamic security code associated to an identifier of said transaction;

verifying using a verification memory if the provided dynamic security code has already been validated when associated to the same associated identifier;

if not, verifying the validity of the provided dynamic security code;

if the provided dynamic security code is valid, memorizing in the verification memory the provided dynamic security code, the associated identifier of the payment transaction.

13 . The dynamic security code verification system according to claim 12 comprising a DSC generation device and a transaction approval server, wherein the DSC generation device is configured to verify using a verification memory if the provided dynamic security code has already been validated when associated to the same associated identifier.

14 . A non-transitory computer program storage device comprising a memory for storing computer programs executable by a computer, the computer program including instructions instructing the computer to perform a method comprising the steps of:

providing for a given payment transaction a dynamic security code associated to an identifier of said transaction;

verifying using a verification memory if the provided dynamic security code has already been validated when associated to the same associated identifier;

if not, verifying the validity of the provided dynamic security code;

if the provided dynamic security code is valid, memorizing in the verification memory the provided dynamic security code, the associated identifier of the payment transaction.

15 . The dynamic security code verification system according to claim 1 , wherein the identifier of the payment transaction is the amount of said transaction.

16 . The dynamic security code verification system according to claim 1 , wherein the identifier of the payment transaction is a challenge code.

17 . The dynamic security code verification system according to claim 1 , comprising a step of approving the payment transaction once the validity of the dynamic security code is validated.

18 . The dynamic security code verification system according to claim 1 , comprising a step of declining the payment transaction applied if another payment transaction has already been approved using the same dynamic security code associated to the same transaction identifier

19 . The dynamic security code verification system according to claim 1 , wherein the validated dynamic security codes are stored with their associated payment transaction identifier together and with a date of at which the transaction was initiated.

20 . The dynamic security code verification system according to claim 1 , wherein the validated dynamic security codes are stored with their associated payment transaction identifier together with a time counter data associated to or embedded in the dynamic security code of the received set of data.