All CCS operations require a cryptographic key—usually called a Base Derivation Key (BDK)—to be identified for use in the web service operation. Each web service provides one or more mechanisms for identifying the right key to use for that operation. One mechanism is to identify a BDK based on a Manufacturer Identifier, as shown in the following table. At any time in a particular domain, there can only be a single BDK loaded into the appliance per manufacturer for use by SAKA in processing CCS transactions. Note that this does not prevent storing many BDKs on SAKA, but for decrypting CHD only one BDK may be loaded for use per manufacturer. By supplying the manufacturer ID as a web service parameter, you can instruct the appliance to use the corresponding BDK for that manufacturer in the DUKPT operation the web service will be performing.

Additionally in the case of the GetCardCaptureData web service, the manufacturer ID also determines how the appliance will parse the card-swipe captured, encrypted, and provided by your application to SAKA for processing. Every terminal manufacturer defines their CHD swipe data format differently, so it is important that the correct manufacturer ID parameter is passed in when submitting a request to the GetCardCaptureData web service. A list of manufacturers by their associated identifiers follows here:

NOTE: When processing PINs from cards, this parameter is irrelevant.