The Card Capture Service (CCS) web service application supports an array of web services for working with the ANSI X9.24-1:2009 Derived Unique Key Per Transaction (DUKPT) algorithm for protecting data and Personal Identification Numbers (PINs). Client applications send requests to the CCS through a standard Simple Object Access Protocol (SOAP)—or Representational State Transfer (REST)-based web services over the Secure Hyper Text Transfer Protocol (HTTPS).

SOAP-based web service calls can be expected to return a CCReturnObject (see definition below). In the case of some errors, you should also anticipate the return of either StrongKeyLiteExceptions or CCExceptions. REST-based web service calls will return HTTP Status Codes corresponding with the success or type of failure encountered. Successful operations always return a 200 OK alongside a JavaScript Object Notation (JSON) or Extensible Markup Language (XML) response. A JSON will be returned unless strongkeylite.cfg.property.ccsresponseformat is overwritten on the SAKA server to specify that “xml” responses should be returned. Other valid Response Statuses specific to failure conditions include:

• 400 Bad Request

• 401 Unauthorized

• 404 Not Found

• 500 Internal Server Error