Bank Card Issuing & Processing
The Bank Card Security System (BCSS) is used by card issuers, secure personalization bureaus and card processors to reduce the amount of programming required to create a system for issuing secure cards, and processing transactions.from Prime Factors is used by payment card issuers to create security codes and PINs, and by processors to authenticate transactions. BCSS reduces the amount of programming required to accomplish these tasks, and to implement key management.
Leading card issuers around the world have saved money and expedited their time to market by using subroutines in BCSS to create security codes and PINs for credit, debit and prepaid cards. The security codes and PINs are then sent to a secure card manufacturer where the cards are produced. BCSS allows the issuer to manage and control sensitive processes and data. It is more cost-effective for the issuer to create security codes and PINs than to outsource their creation to a secure card manufacturer.
Card processors use BCSS to verify card transactions. BCSS decrypts PIN blocks and verifies security codes. The verification process begins when a point-of-sale device encrypts the cardholder PIN block, and sends it to the issuing bank or processing center. BCSS sends the encrypted PIN block, secret keys and security information to the Thales HSM (hardware security module). The PIN block is decrypted inside the HSM so that the PIN and keys are never in the clear. The expected security code is compared to the one in the transaction. If the codes match, the transaction is approved.
When hardware is required, BCSS simplifies integration of Thales HMSs. BCSS makes the whole process a lot easier because BCSS manages Ethernet (TCP/IP) communications, builds host commands, and stores a database of encrypted keys created by the HSM. Together, the two provide the most secure environment for creating and verifying security codes and PINs.
BCSS has a library of subroutines that handles more than 100 functions that access the BCSS database and Thales HSMs. The extensive BCSS library eliminates the need to know Thales' proprietary host commands and makes it easier to issue calls from popular programming languages such as C, C++, C#, COBOL, Java and Visual Basic. The subroutines include those that call the HSM to create and verify all security codes including CVV, CVV2, CAVV, CVC, CVC2, CVC3, CSC. , PIN, PVV.
Customers rely on BCSS to keep them current with the latest security standards established by Visa, MasterCard, Discover and American Express. BCSS also keeps issuers current with security requirements for different types of plastic media: magnetic-stripe cards, smartcards (chip cards) and contactless cards (EMV and RFID cards).
Learn more about BCSS:
back to overview
|