APPARATUS, METHOD, AND COMPUTER PROGRAM PRODUCT FOR PROVIDING A QUALITY CONTROL MECHANISM FOR THE CONTACTLESS INTERFACE OF A DUAL-INTERFACE CARD

• US 20100274712A1
• Filed: 04/28/2010
• Published: 10/28/2010
• Est. Priority Date: 04/28/2009
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Radu, Cristian, Mestré, Patrick
• Granted Patent: US 8,583,561 B2
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06K 19/07749 the record carrier being capable of non-contact communication, e.g. constructional details of the antenna of a non-contact smart card
• CPC Class Codes: G06K 19/07769 the further communication means being a galvanic interface, e.g. hybrid or mixed smart cards having a contact and a non-contact interface
• 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/2295 Parent-child type, e.g. where parent has control on child rights
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/352 Contactless payments by cards
• CPC Class Codes: G06Q 20/357 Cards having a plurality of specified features
• CPC Class Codes: G06Q 20/35765 Access rights to memory zones
• 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: G07F 7/0873 Details of the card reader

Abstract

Techniques for enabling performance of a quality control function on the contactless interface while the contactless interface is disabled are provided. The techniques include implementing, on a dual-interface payment device, one or more security mechanisms, wherein the dual-interface payment device comprises a first interface and a second interface, using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface, and personalizing the dual-interface payment device and the one or more security mechanisms according to one or more requirements of an issuer of the dual-interface payment device.

Claims

1. A method comprising the steps of:

implementing, on a dual-interface payment device, one or more security mechanisms, wherein the dual-interface payment device comprises a first interface and a second interface;

using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface; and

personalizing the dual-interface payment device and the one or more security mechanisms according to one or more requirements of an issuer of the dual-interface payment device.

2. The method of claim 1, wherein the one or more security mechanisms comprise one or more read record filters.

3. The method of claim 1, wherein the first interface comprises a contact interface and the second interface comprises a contactless interface.

4. The method of claim 1, wherein personalizing the dual-interface payment device and the one or more security mechanisms according to one or more requirements of an issuer of the dual-interface payment device is performed by a personalization bureau.

5. The method of claim 1, further comprising performing a quality control function on the second interface, via the first interface, to verify that data corresponding to the second interface is correct.

6. The method of claim 5, wherein performing a quality control function on the second interface, via the first interface, to verify that data corresponding to the second interface is correct comprises performing a quality control function on the second interface, via the first interface, while the second interface is disabled.

7. The method of claim 1, wherein each of the one or more security mechanisms is coded as a combination of zero or more short file identifiers and zero or more record numbers.

8. The method of claim 7, wherein the combination of zero or more short file identifiers and zero or more record numbers specify zero or more records that cannot be read through a read record command.

9. The method of claim 1, wherein a separate security mechanism is used for each interface.

10. The method of claim 1, wherein each of the one or more security mechanisms provides a set of instructions to the dual-interface payment device that identifies to the dual-interface payment device specific data that cannot be read when using a particular interface.

11. The method of claim 1, wherein a security mechanism for a first interface is formatted to allow reading of, through the first interface, all data corresponding to the first interface as well as all data corresponding to the second interface.

12. The method of claim 1, wherein a security mechanism for a second interface contains one or more short file identifiers and one or more record numbers identifying one or more records which contain data restricted to the first interface.

13. The method of claim 1, wherein one or more of the one or more security mechanisms can remain in effect on the dual-interface payment device in perpetuity.

14. The method of claim 1, wherein one or more of the one or more security mechanisms can be modified while the dual-interface payment device is in use.

15. The method of claim 1, wherein using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface comprises providing a command to the first interface to enable reading of application file locators from both the first and second interface.

16. The method of claim 1, wherein using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface comprises providing a read record command to the first interface to enable reading of all of files and records that are not listed in a read record filter.

17. The method of claim 16, further comprising enabling the first interface to read all records included in an application file locator for the first interface and an application file locator for the second interface when an instance of a read record filter corresponding to the first interface is empty.

18. The method of claim 1, wherein using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface comprises preventing reading of all of files and records that are listed in a read record filter.

19. An apparatus comprising:

means for implementing, on a dual-interface payment device, one or more security mechanisms, wherein the dual-interface payment device comprises a first interface and a second interface;

means for using the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface; and

means for personalizing the dual-interface payment device and the one or more security mechanisms according to one or more requirements of an issuer of the dual-interface payment device.

20. A payment device comprising:

a payment device memory; and

at least one payment device processor coupled to the payment device memory, the at least one payment device processor being operative to;

implement one or more security mechanisms to one or more interfaces of the payment device, wherein the one or more interfaces comprise a first interface and a second interface; and

use the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface.

21. The payment device of claim 20, wherein the one or more security mechanisms comprise one or more read record filters.

22. The payment device of claim 20, wherein the first interface comprises a contact interface and the second interface comprises a contactless interface.

23. The payment device of claim 20, wherein the at least one payment device processor being operative to personalize the dual-interface payment device and the one or more security mechanisms according to one or more requirements of an issuer of the dual-interface payment device.

24. The payment device of claim 20, wherein the at least one payment device processor being operative to facilitate performing a quality control function on the second interface, via the first interface, to verify that data corresponding to the second interface is correct.

25. The payment device of claim 24, wherein the at least one payment device processor operative to facilitate performing a quality control function on the second interface, via the first interface, to verify that data corresponding to the second interface is correct is further operative to facilitate performing a quality control function on the second interface, via the first interface, while the second interface is disabled.

26. The payment device of claim 20, wherein each of the one or more read record filters is coded as a combination of zero or more short file identifiers and zero or more record numbers.

27. The payment device of claim 26, wherein the combination of zero or more short file identifiers and zero or more record numbers specify zero or more records that cannot be read through a read record command.

28. The payment device of claim 20, wherein a separate security mechanism is implemented onto each interface.

29. The payment device of claim 20, wherein each of the one or more security mechanisms provides a set of instructions to the dual-interface payment device that identifies to the dual-interface payment device specific data that cannot be read when using a particular interface.

30. The payment device of claim 20, wherein a security mechanism for a first interface is formatted to allow reading of, through the first interface, all data corresponding to the first interface as well as all data corresponding to the second interface.

31. The payment device of claim 20, wherein a security mechanism for a second interface contains one or more short file identifiers and one or more record numbers identifying one or more records which contain data restricted to the first interface.

32. The payment device of claim 20, wherein one or more of the one or more security mechanisms can remain in effect on the payment device in perpetuity.

33. The payment device of claim 20, wherein one or more of the one or more security mechanisms are temporary features of the payment device.

34. The payment device of claim 20, wherein the at least one payment device processor operative to use the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface is further operative to provide a command to the first interface to enable reading of application file locators from both the first and second interface.

35. The payment device of claim 20, wherein the at least one payment device processor operative to use the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface is further operative to provide a read record command to the first interface to enable reading of all of files and records that are not listed in a read record filter.

36. The payment device of claim 35, wherein the at least one payment device processor is further operative to enable the first interface to read all records included in an application file locator for the first interface and an application file locator for the second interface when an instance of a read record filter corresponding to the first interface is empty.

37. The payment device of claim 20, wherein the at least one payment device processor operative to use the one or more security mechanisms to prevent a subset of data corresponding to the first interface from being read using the second interface while allowing data corresponding to the second interface to be read using the first interface is further operative to prevent reading of all of files and records that are listed in a read record filter.