The document categorises card data based on the degree of sensitivity from the security perspective. The guidelines enable you to adopt PCI-compliant card data protection practices and thereby protect yourself and your clients from the consequences of data breach.
Introduction
Contis is a PCI-DSS compliant organisation and guarantees adherence of all security standards for card data generation, processing, storage and transmission.
Contis offers API interfaces to clients and gives them access to confidential information for card processing. Hence, Contis strictly enforces security protocol on its API clients to protect them from the consequences of data breach, such as litigation, loss of money and reputation.
Contis has classified various data based on the level of confidentiality (Table 1, Table 2 and Table 3) and prepared a guideline (Table 4) on how to preserve the data privacy in the systems and prevent any data breach incident.
Contis recommends that every API client strictly follows the guidelines and contacts the Contis support team regarding any queries on data safety compliance.
Classification based on data sensitivity
HIGHLY SENSITIVE DATA
This type of data should not be stored anywhere in your system, even on an intermittent basis. The data should be processed in the real time as it is transmitted by Contis.
Category | Parameters | Description |
Card Authentication Data | PIN | The four-digit, Personal Identification Number known only to the user for ATM/POS transaction |
PIN Block | The block of data composed of PIN, PIN length and PAN data, used to retrieve the PIN | |
CVV2 | Three-digit number printed on the back of the VISA card | |
PAN/ VirtualCardNumber | 16-digit Permanent Account Number of the card/ virtual card number, used for e-commerce and online transactions | |
Magnetic Strip Data | Known as ‘Full Track Data’, it is the encoded data stored in the magnetic strip on the back of the card for transaction authorisation | |
m-PIN | Four- to six-digit Mobile PIN needed to log into the mobile |
SENSITIVE DATA
This type of data should be stored in an encrypted form and rendered unreadable. The security keys and encrypted data should be stored in a highly secure area, controlled by authorised access.
Category | Parameters | Description |
API Configuration Data | 3DES PIN IV key | Used for encryption and decryption of the PIN number during PIN retrieve function call |
3DES PIN Secret Key | Used for encryption and decryption of the PIN number during PIN retrieve function call | |
Hash PAN key | Used to generate hash PAN number from clear PAN | |
SecurityKey | The security key provided by Contis to every API user after login. Used to generate Hash using Hashdatastring method | |
Token | The authentication key generated after successful login to the API account. Used to call other API methods | |
DeviceToken | The unique string that individually identifies each mobile device | |
API Authentication Data | Username | Username needed to login to API account |
Password | Password needed to access the API Account | |
VerificationCode | The verification code for the cardholder’s main mobile number, which is used to verify the cardholder’s mobile phone number | |
Card Activation Code | The three-digit card activation code used to activate the card | |
Scheme Client Account Number | The main or master account of client in a scheme | |
ContisUniqueReferenceID | On successful registration, Contis returns a unique reference ID from the Contis system for the ClientSSOReferenceNumber provided by the client | |
ClientSSOReferenceNumber | The client-filled unique SSO reference value, used for Contis SSO service integration | |
Hash | A security feature used by Contis to prevent confidential data access and modification. It is generated by security key and hashdatastring. | |
HashDataString | Contains the linked object field’s data, which is used to generate the Hash. See API reference for more information | |
Token | The authentication key generated after successful login to the API account. Used to call other API methods. | |
DeviceToken | The unique string that individually identifies each mobile device | |
Account Data | Account Number | Cardholder’s eight-digit account number |
BankAccountNumber | The number used in domestic bank transfer transaction. | |
IBAN | International Bank Account Number used in international bank transaction | |
BIC | Bank Identifier Code used in international bank transaction | |
Personal Data | MobileNumber | Mobile number of cardholder |
Landlinenumber | The landline number of cardholder | |
Passportnumber | The passport number of the cardholder | |
DrivinglicenceNumber | The driving licence number of the cardholder | |
Nationalidcard | The national ID card number of the account holder | |
SocialSecurityNumber | The four-digit social security number | |
DOB | Date of birth of cardholder | |
Address | Address of the cardholder | |
Display Name | The name of the Cardholder printed on the card | |
Card Data | CardIssueDate | The date on which card has been issued |
CardID | Contis specified CardID number to refer the card | |
CardHolderID | Contis specified ID of the Card holder | |
ObscuredCardNumber | The card number with visible first and last four digits and obscured middle digits for data protection | |
Expiry Date | Card expiry data | |
Hash Card Number | Hash card number derived using MD5 algorithm, PAN (16-digit card number) and Hash PAN Key provided by Contis |
GENERAL DATA
The non-confidential data is stored in normal format in your system, but still covered by industry-compliant data protection policy and not for public use.
Data like Card Status (Lost, locked, Active, Inactive, Suspended, Cancelled, Frozen, etc.), HOSC, SWEAR, Agreement (Terms & Conditions), Scheme features, Card Design features/program, Communication templates, etc.
PCI DSS
Payment Card Industry (PCI) is an autonomous body. It was set up by major card brands like VISA, American Express, MasterCard, Discover and JCB for world-wide adoption of Data Security Standards (DSS). The body frames and encourages adoption of regulations for safe processing, transmission and storage of card data. PCI DSS applies to all the merchants, processors, acquirers, issuers and service providers involved in the card payment processing. Payment brand and acquirers are responsible for enforcing the PCI DSS compliance.
Contis is bound by PCI DSS regulations and encourages you to adopt the best practices. See table 4 on what “not to do” and “to do” for card data protection in line with the PCI data safety norms.
Contis is bound by PCI DSS regulations and encourages you to adopt the best practices. See Table 4 on what “not to do” and “to do” for card data protection in line with the PCI data safety norms.
Cardholder data protection best practices
Consequences of Data Breach
Contis warns that failure to adopt card data protection guidelines will lead to a data breach. If that happens, you may face the following consequences:- Termination of card processing privileges
- Loss of reputation of your brand
- Invite a forensic audit from compliance authority
- Face client litigation
- Take 90-120 days to implement remedial measures, which could throw your business out of gear