ExpressPay Encrypted Device Processing Overview

Transcription

1 This document contains information on the use of an encrypted device via a direct integration with the ExpressPay payment processing platform. Notes The device must be encrypted with an Element encryption key, and may or may not be keyboardemulation. Encrypted Swiped/Keyed Data and Card Data Key Serial Number alpha characters should stay capitalized when submitted to the ExpressPay platform. Processing Flow Standard XML Output: Keyboard Emulation 1. The merchant will enter basic purchase information into the point of sale application. 2. When ready to process the real-time credit card transaction, the end user will initiate a swipe or key entry of the card using the encrypted device (following the appropriate prompts on the device). 3. Once the card is successfully swiped or keyed into the device, the output from the device will be in an XML format that contains the encrypted values (such as the encrypted track data, etc.) that will be submitted to the ExpressPay payment platform. These encrypted values have been outlined below. 4. The point of sale application will parse these output values from the device and map them to the appropriate input values as specified in the Express interface specification. 5. The point of sale application will submit a direct programmatic CreditCardSale (or appropriate transaction type) to the ExpressPay processing platform. 6. ExpressPay will process the transaction and return the response values to be displayed in the point of sale application. Receipts may also be printed using this information. Proprietary Output: Application Must Drive Device 1. The merchant will enter basic purchase information into the point of sale application. 2. When ready to process the real-time credit card transaction, the end user will initiate a swipe or key entry of the card using the encrypted device (following the appropriate prompts on the device). 3. Once the card is successfully swiped or keyed into the device, the output from the device will be in a format defined by the hardware manufacturer and containing the encrypted values (such as the encrypted track data, etc.) that will be submitted to the ExpressPay payment platform. These encrypted values are outlined below. 4. The point of sale application will parse these output values from the device and map them to the appropriate input values as specified in the Express interface specification. 5. The point of sale application will submit a direct programmatic CreditCardSale (or appropriate transaction type) to the ExpressPay processing platform. 6. ExpressPay will process the transaction and return the response values to be displayed in the point of sale application. Receipts may also be printed using this information. External-Encrypted Device Overview Page 1 of 5

2 Input and Output Details Input Fields Name Value I/O Max Object Description EncryptedTrack1Data String I 300 Card Encrypted Track 1 data EncryptedTrack2Data String I 200 Card Encrypted Track 2 data EncryptedCardData String I 200 Card Encrypted card (keyed) data String I 26 Card Card data key serial number Enum I 2 Card Terminal encryption format: XML input/soap input (description) ** 0/Default (Default) ** 1/Format1 (MagTek) ** 2/Format2 (Ingenico DPP) ** 3/Format3 (Ingenico On-Guard) ** 4/Format4 (ID Tech) ** 5/Format5 (Verifone Vx devices) ** 6/Format6 (IPC devices) ** 7/Format7 (Verifone Mx devices) String I 40 Terminal Device serial number Encrypted Device Standard XML Output Format The XML output follows an attribute structure: Msg Ver="1.0"> attribute list...> attribute list...> <Addr attribute list...> attribute list...> Field Names and Attributes Note All fields are listed for clarity. If a field is not used, it need not be present in the XML. Field Name Attributes DvcMsg Ver = Device Message Version Dvc App = Application Name AppVer = Application Version DvcType = Device Type = Device Serial Number Entry = CardEntryMethod (SWIPE, MANUAL,...) Card ETrk1 = Encrypted Track 1 ETrk2 = Encrypted Track 2 ECData = Encrypted Card Data (Card Number=ExpDate=Security Code) = Card Data KSN DbtPINB = Debit PIN DbtKSN = Debit KSN MskPAN = Masked PAN Exp = Expiration Date CHolder = Cardholder Name = Encrypted Format Addr AVSAddr = AVS Address AVSZip = AVS Zipcode Tran TranType = (CREDIT, DEBIT,...) Amt = Amount TipAmt = Tip Amount SigCap = Signature Capture (Base64 encoded) CashBackAmt = Cash Back Amount External-Encrypted Device Overview Page 2 of 5

3 XML Examples Credit Card Swipe Msg Ver= 1.2 > = Entry= SWIPE > ETrk2= F753F933E3C1177DAA0BF E1FE58C265E97EF44C752C3D94A3CA97471A371A95563C916DA = A08B000C E6 CHolder="GLOBAL PAYMENTS TEST CARD/ > TranType= CREDIT Credit Card Manually Keyed Msg Ver= 1.2 > = Entry= MANUAL > ECData= D7DBAD35858E484D0CC7FF3DE0914CE4426B08FB04455B4D210F45C75AA1727CD58026F E11244AA 13C1D4B2F2 = A08B000C E6 Exp= 1012 CHolder="GLOBAL PAYMENTS TEST CARD/" DbtPINB = DbtKSN= > <Addr AVSAddr= 123 AVSZip= > </Addr> TranType= CREDIT External-Encrypted Device Overview Page 3 of 5

4 Debit Card Swipe Msg Ver= 1.2 > = Entry= SWIPE > ETrk2= F753F933E3C1177DAA0BF E1FE58C265E97EF44C752C3D94A3CA97471A371A95563C916DA = A08B000C E6 Exp= 1012 CHolder="GLOBAL PAYMENTS TEST CARD/" DbtPINB = 785AB DbtKSN= FFFF3D F > TranType= DEBIT Mapping from XML to ExpressPay Interface Specification Fields Transaction Type XML ExpressPay field Credit Card Swipe Credit Card Manually Keyed Debit Card Swipe ETrk1 OR ETrk2 ECData ETrk2 DbtPINB DbtKSN EncryptedTrack1Data OR EncryptedTrack2Data EncryptedCardData EncryptedTrack2Data PINBlock KeySerialNumber External-Encrypted Device Overview Page 4 of 5

5 Examples Encrypted Format Entry Method ExpressPay Fields 1 through Credit Card manual entry Debit Card swipe Credit Card manual entry Debit Card swipe EncryptedTrack2Data OR EncryptedTrack1Data EncryptedCardData EncryptedTrack2Data PINBlock KeySerialNumber EncryptedCardData PINBlock KeySerialNumber External-Encrypted Device Overview Page 5 of 5