Apparatus, method, and computer program product for providing a quality control mechanism for the contactless interface of a dual-interface card

• US 8,583,561 B2
• Filed: 04/28/2010
• Issued: 11/12/2013
• Est. Priority Date: 04/28/2009
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Mestr, Patrick, Radu, Cristian
• Primary Examiner(s): KIM, STEVEN S
• Application Number:
  US12/769,395
• Publication Number:
  US 20100274712A1
• Time in Patent Office: 1,294 Days
• Field of Search: 705/64, 705/65, 705/41, 235/380, 235/438, 235/440
• US Class Current: 705/64
• 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:

personalizing, by one or more processors, a dual-interface payment device and implementing one or more security mechanisms on the dual-interface payment device according to one or more requirements, wherein the dual-interface payment device comprises a first interface and a second interface;

wherein the step of personalizing the dual-interface payment device comprises;

storing first data associated with the first interface; and

storing second data associated with the second interface;

disabling, by the one or more processors, the second interface; and

performing, by the one or more processors, a quality control function on the second data;

wherein the step of performing the quality control function on the second data comprises;

receiving a read record command at the first interface;

retrieving, via the first interface, at least one record of the second data listed in the read record command based on a read record filter corresponding to the first interface, wherein the read record filter is a security mechanism of the one or more security mechanisms; and

verifying the at least one record of the retrieved second data.

2. The method of claim 1, wherein the one or more security mechanisms comprise one or more read record filters including the read record filter corresponding to the first interface.

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, further comprising receiving the one or more requirements from an issuer, wherein the programming of the dual-interface payment device is performed by a personalization bureau.

5. 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.

6. The method of claim 5, 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 the read record command.

7. The method of claim 1, wherein a separate security mechanism is used for each of the first and the second interface.

8. The method of claim 1, wherein each of the one or more security mechanisms is stored as a set of instructions on the dual-interface payment device that identifies to the dual-interface payment device specific data that cannot be read when using the second interface.

9. The method of claim 1, wherein a security mechanism for the first interface, among the one or more security mechanisms, is maintained in a state enabling reading of, through the first interface, all first data corresponding to the first interface and all second data corresponding to the second interface during the performance of the quality control function.

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

11. The method of claim 1, wherein the one or more security mechanisms is stored in a non-volatile memory of the dual-interface payment device.

12. The method of claim 1, further comprising modifying one or more of the one or more security mechanisms of the dual-interface payment device.

13. The method of claim 1, wherein the step of performing the quality control function comprises providing the read record command to the first interface to enable reading of application file locators from both the first data and second data.

14. The method of claim 1, wherein the step of performing the quality control function comprises:

providing the read record command to the first interface; and

reading at least one record not listed in the read record filter corresponding to the first interface.

15. The method of claim 14, further comprising reading all records included in an application file locator for the first interface and an application file locator for the second interface via the first interface when an instance of the read record filter corresponding to the first interface is empty.

16. The method of claim 1, wherein the step of performing the quality control function further comprises preventing reading of all of files and records that are listed in the read record filter.