Preliminary Release. For Planning and Review. Notice:

Transcription

1 100 New Britain Blvd Chalfont, PA Tel: DSIEMVClientX Canadian EMV Programming Interface Specification V00.07 Preliminary Release For Planning and Review Notice: This document contains information proprietary to Datacap Systems Inc. The only acceptable use for the information contained herein is to interface third party systems exclusively to Datacap s Tran and epay server products. Any other use is strictly prohibited.

2 Copyright Notice Copyright 2010 Datacap Systems Inc. 100 New Britain Blvd. Chalfont, Pennsylvania USA All rights reserved. Notice This document contains information proprietary to Datacap Systems Inc. The only acceptable use for the information contained herein is to interface third party systems exclusively to Datacap s epay server products. Any other use is strictly prohibited. The DSIEMVClientX, DSICientX, DataTran, NETePay, DIALePay, GIFTePay, epay, epay Administrator, DataTran, DialTran, IPTran, TwinTran and Datacap names and logos and all related trademarks, trade names, and other intellectual property are the property of Datacap Systems Inc. and cannot be used without its express prior written permission. Notice Preliminary Release For Planning and Review This is a preliminary document for review and planning purposes. While the information contained herein is accurate at the time of release, it is expected that there will be changes which will have some impact on the contents until final certification is completed with the Canadian processors. A final form of this document will be released at V01.00 (or higher); any versions less than should be considered preliminary and subject to change. Copyright 2010 Proprietary Information Version: Page 2

3 Revision History Jan 2010 Initial Release of Preliminary Draft Feb 2010 Revised Release of Preliminary Draft Mar 2010 Revised Release of Preliminary Draft Added GetPrePaidStripe command Added instructions on bilingual receipt printing Corrected slected response templates Revised Section 5 use description Mar 2010 Revised Release of Preliminary Draft Corrected French spelling in draft instructions Intentionally skipped Jul 2010 Revised Release of Preliminary Draft Added new PIN Pad Type: Global1 for Global or Mercury Added optional <CardType> tag with argument Debit to to EMVSale command to enforce debit card use at PIN pad for possible cash back Jul 2010 Corrected SeverVersion, EMVPublicKeyReport, EMVStatisticsReport, EMVOfflineDeclineReport, BatchSummary, BatchClose, XML request from <Transaction> to <Admin> Added EMVParameterReport request section Copyright 2010 Proprietary Information Version: Page 3

4 Table Of Contents 1.0 INTRODUCTION EMV SUPPORTED TRANSACTIONS SUMMARY EMV TRANSACTION REQUEST/RESPONSE XML DEFINITIONS EMVPADRESET EMVKEYCHANGE EMVPARAMDOWNLOAD EMVSALE EMVVOIDSALE EMVRETURN EMVVOIDRETURN EMVVOICEAUTH EMVPUBLICKEYREPORT EMVSTATISTICSREPORT EMVOFFLINEDECLINEREPORT EMVPARAMETERREPORT BATCHSUMMARY BATCHCLOSE SERVERVERSION GETPREPAIDSTRIPE TRANSACTION RESPONSES EMVPADRESET XML RESPONSE TEMPLATE EMVKEYCHANGE XML RESPONSE TEMPLATE EMVPARAMDOWNLOAD XML RESPONSE TEMPLATE XML RESPONSE TEMPLATE FOR...53 EMVSALE...53 EMVVOIDSALE...53 EMVRETURN...53 EMVVOIDRETURN...53 EMVVOICEAUTH XML RESPONSE TEMPLATES FOR...56 EMVPUBLICKEYREPORT...56 EMVPARAMETERREPORT...56 EMVSTATISTICSREPORT...56 EMVOFFLINEDECLINEREPORT BATCHSUMMARY XML RESPONSE TEMPLATE BATCHCLOSE XML RESPONSE TEMPLATE SERVERVERSION XML RESPONSE TEMPLATE GETPREPAIDSTRIPE XML RESPONSE TEMPLATE DSIEMVCLIENTX PROGRAMMING INTERFACE FOR EMV TRANSACTIONS ERROR CODES...65 Copyright 2010 Proprietary Information Version: Page 4

5 1.0 Introduction This document is targeted to developers who have previous experience in integration with Datacap s DSIClientX ActiveX component. If you are new to integration with Datacap s epay line of products, please refer to the document DSIClientX Interface Specification. DSIEMVClientX is a Windows ActiveX control that provides applications with the ability to process an EMV (chip card) electronic payments in a multi-tiered client-server architecture. Applications integrated with DSIEMVClientX act as a client to Datacap s EMV certified payment servers to process payments. The DSIEMVClientX software is designed to communicate exclusively with Datacap s in-store NETePay server products using Internet Protocol (IP). Messages exchanged between the DSIEMVClientX and the server are encrypted for secure transmission over open networks (such as the Internet). This secure communications architecture provides the flexibility to configure systems using LAN and/or WAN networks. Datacap servers are available for in-store or enterprise configurations and are designed to communicate with specific payment systems providers. DSIEMVClientX does not use any storage on the client machine; the Datacap servers provide consolidated transaction data storage, logging and data management functions. DSIEMVClientX directly controls an approved EMV PIN pad on a PC COM (serial) port to manage all PIN pad interactions. The DSIEMVClientX control uses XML formatted requests and responses for transaction processing requests. Copyright 2010 Proprietary Information Version: Page 5

6 2.0 EMV Supported Transactions Summary The following transaction codes <TranCode> are supported in DSIEMVClientX: Transaction EMVPadReset EMVKeyChange EMVParamDownload EMVSale EMVVoidSale EMVReturn EMVVoidReturn This command should be done before every transaction (Sale, VoidSale, Return, VoidReturn, VoiceAuth) to assure that no card is in the PIN pad chip reader before starting a transaction. If no card is in the reader, then a response should be returned with 2-3 seconds. If there s a card in the reader, the PIN pad displays Remove Card and waits for the card to be removed before returning a response; another EMVPadReset should then be issued. This command should be performed on demand from outside source OR when a pad is replaced OR new PIN pad installation This command should be perfumed on demand from outside source OR when a pad is replaced OR new PIN pad installation Sale transaction credit or debit Sale transaction Void credit or debit Return transaction credit or debit Return transaction Void credit or debit EMVVoiceAuth Force a transaction was authorized by voice and put it into the batch credit only (must have PIN pad) Admin EMVPublicKeyReport EMVParameterReport EMVStatisticsReport EMVOfflineDeclineReport BatchSummary BatchClose ServerVersion Public Key Report required at every PIN pad (lane) Parameter Report required at every PIN pad (lane) Statistics Report required at every PIN pad (lane) Offline Decline Report required at every PIN pad (lane) Batch Summary Report required at every PIN pad (lane) if merchant processing profile is set for merchant initiated close Batch Close process required at every PIN pad (lane) if merchant processing profile is set for merchant initiated close Reports the NETePay server version with which the DSIEMVClientX is communicating Implementation Notes: 1. All transactions must be implemented for EMV compliance. Copyright 2010 Proprietary Information Version: Page 6

7 3.0 EMV Transaction Request/Response XML Definitions 3.1 EMVPadReset Use: To reset the EMV PIN pad device. This command should be performed before every transaction (Sale, VoidSale, Return, VoidReturn, VoiceAuth) to assure that no card is in the EMV PIN pad chip card (insertion) reader before starting a transaction. If no card is in the reader, then a response should be returned with 2-3 seconds. If there s a card in the reader, the PIN pad displays Remove Card and waits for the card to be removed before returning a response; another EMVPadReset should then be issued. XML Template: EMVPadReset <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTracedata> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <Tran Code>EMVPadReset</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description/Value HostOrIP Y A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID Y 1 24 A Merchant identification assigned by processor. TerminalID Y 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage Y 6 7 A English or French TranCode Y 1 40 A EMVPadReset PadType Y 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort Y 1 3 N COM (Serial) port number to which an EMV approved PIN pad is attached (1-255). Copyright 2010 Proprietary Information Version: Page 7

8 InvoiceNo Y 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo Y 1 24 A Use the same data as InvoiceNo SequenceNo Y A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Request for EMVPadReset <TStream> <Transaction> <HostOrIP>BOB</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTraceData>Dev1</UserTraceData> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVPadReset</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>1</InvoiceNo> <RefNo>1</RefNo> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Response for EMVPadReset <RStream> <CmdResponse> <ResponseOrigin>Client</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Success</CmdStatus> <TextResponse>Reset Successful.</TextResponse> <SequenceNo> </SequenceNo> <UserTraceData>Dev1</UserTraceData> </CmdResponse> </RStream> Copyright 2010 Proprietary Information Version: Page 8

9 3.2 EMVKeyChange Use: To change the encryption keys in the EMV PIN pad device. This command should be performed on demand from an outside source (eg. processor) OR when a pad is replaced OR a new PIN pad installation. The EMV PIN pads receive updated key information from the processing network from time to time to encrypt user PIN information. When a new PIN pad is initially deployed, it will have internal keys, which are out of synch with the processing host. In order to update the keys in the PIN pad with the processing host, a Key Change transaction must first be performed. The ECR/POS must support the EMVKeyChange transaction and make it available as an administrative function. XML Template: EMVKeyChange <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVKeyChange</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description/Value HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVKeyChange PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and Copyright 2010 Proprietary Information Version: Page 9

10 supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Request for EMVKeyChange <TStream> <Transaction> <HostOrIP>BOB</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTrace>Dev1</UserTrace> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVKeyChange</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>1</InvoiceNo> <RefNo>1</RefNo> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Reply for EMVKeyChange <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Success</CmdStatus> <TextResponse>SUCCESS</TextResponse> <SequenceNo> </SequenceNo> <UserTrace>Dev1</UserTrace> </CmdResponse> <TranResponse> <TranCode>EMVKeyChange</TranCode> </TranResponse> </RStream> Copyright 2010 Proprietary Information Version: Page 10

11 3.3 EMVParamDownload Use: To load parameters into the EMV PIN pad device. This command should be performed on demand from an outside source (eg. processor) OR when a pad is replaced OR a new PIN pad installation OR when a setting changes at NETePay. The EMV PIN pad may need to receive updated parameter information from the processing network from time to time to operate successfully with the processing host. When a new EMV PIN pad is initially deployed, it must obtain parameters that are in synch with the processing host. In order to update the parameters in the EMV PIN pad with the processing host, an EMVParamDownload transaction must first be performed. The ECR/POS must support the EMVParamDownload transaction and make it available as an administrative function; the EMVParamDownload transaction is the only method to remedy a parameter discrepancy and permit processing to continue with the EMV PIN pad. XML Template: EMVParamDownload XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVParamDownload</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description/Value HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVParamDownload Copyright 2010 Proprietary Information Version: Page 11

12 PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Request for EMVParamDownload <TStream> <Transaction> <HostOrIP>BOB</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTrace>Dev1</UserTrace> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVParamDownload</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>1</InvoiceNo> <RefNo>1</RefNo> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Response for EMVParamDownload <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Success</CmdStatus> <TextResponse>SUCCESS</TextResponse> <SequenceNo> </SequenceNo> <UserTrace>Dev1</UserTrace> </CmdResponse> <TranResponse> <TranCode>EMVParamDownload</TranCode> <RefNo> </RefNo> </TranResponse> </RStream> Copyright 2010 Proprietary Information Version: Page 12

13 3.4 EMVSale Use: To process a payment using EMV capable equipment. Credit and Debit transactions with chip, MSR and manually input account information are supported. XML Template: EMVSale XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <CardType>CardType</CardType> <TranCode>EMVSale</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <Account> <AcctNo>AcctNo</AcctNo> </Account> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <Amount> <Purchase>Purchase</Purchase> <Gratuity>Gratuity</Gratuity> </Amount> <Duplicate>Duplicate</Duplicate> <SequenceNo>SequenceNo</SequenceNo> <PartialAuth>PartialAuth</PartialAuth> </Transaction> </TStream> Element Req Min Max Type Description/Value HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French CardType O 3 20 AN Use value DEBIT only if use of a Debit card is to be enforced by the PIN pad (for possible cash back); otherwise omit this tag TranCode R 1 40 A EMVSale Copyright 2010 Proprietary Information Version: Page 13

14 PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). Account:AcctNo o 1 24 A Prompt When the optional Account tag is included with the value Prompt, the PIN pad will prompt the operator for manual input of account number and expiration date from the card. InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo Amount:Purchase R 1 8 N Purchase price (with 2 place decimal eg ) Amount:Gratuity O 1 8 N Gratuity Amount (with 2 place decimal eg ) OR Prompt (which will cause the PIN pad to prompt the cardholder to input the gratuity amount) Duplicate O 1 24 A None OR Override (See implementation note 1) SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. PartialAuth R 1 20 A Allow Legend: A Alphanumeric N Numeric O Optional R Required Sample Request for EMVSale (Chip or MSR Read) <TStream> <Transaction> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTrace>Dev1</UserTrace> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVSale</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo> </InvoiceNo> <RefNo> </RefNo> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Response for EMVSale (Chip or MSR Read) <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> Copyright 2010 Proprietary Information Version: Page 14

15 <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTrace>Dev1</UserTrace> </CmdResponse> <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************8291<AcctNo> <CardType>VISA</CardType> <TranCode>EMVSale</TranCode> <AuthCode>094661</AuthCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo> </InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> <AcqRefData>T C </AcqRefData> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. SALE </Line4> <Line5>.</Line5> <Line6>.************8291</Line6> <Line7>.VISA ENTRY METHOD: SWIPED</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/01/14 TIME: 16:51:57</Line9> <Line10>.</Line10> <Line11>.INV#: APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Cardholder Signature </Line27> <Line28>.</Line28> </PrintData> </RStream> Sample Request for EMVSale (Manual Account Number Read) <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTrace>Dev1</UserTrace> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVSale</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <Account> <AcctNo>Prompt</AcctNo> </Account> Copyright 2010 Proprietary Information Version: Page 15

16 <InvoiceNo>1</InvoiceNo> <RefNo>1</RefNo> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Response for EMVSale (Manual Account Number Read) <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTrace>Dev1</UserTrace> </CmdResponse> <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************1212</AcctNo> <CardType>VISA</CardType> <TranCode>EMVSale</TranCode> <AuthCode>092129</AuthCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo>1</InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> <AcqRefData>T BK6C </AcqRefData> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. SALE </Line4> <Line5>.</Line5> <Line6>.************1212</Line6> <Line7>.VISA ENTRY METHOD: MAN</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/02/04 TIME: 12:42:08</Line9> <Line10>.</Line10> <Line11>.INV#: 1 APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Cardholder Signature </Line27> <Line28>.</Line28> </PrintData> </RStream> Implementation Notes: Copyright 2010 Proprietary Information Version: Page 16

17 1. The Duplicate tag applies to Global Payment Systems and Mercury Payment Systems. In the event that an APDUPE response is received for a request, using a value of Override for the Duplicate tag on a subsequent attempt will force the processing host to skip duplicate checking and therefore approve what appears to be a duplicate transaction. This is useful in cases where multiple charges of the same amount to the same card within a short time period are necessary. Copyright 2010 Proprietary Information Version: Page 17

18 3.5 EMVVoidSale Use: To void a previous EMVSale XML Template: EMVVoidSale (Stripe Account Input on Canadian approved PIN pad) XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> optional (9000 unless supplied) <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVVoidSale</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <Account> <AcctNo>AcctNo</AcctNo> </Account> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <AuthCode>AuthCode</AuthCode> <Amount> <Purchase>Purchase</Purchase> <Gratuity>Gratuity</Gratuity> </Amount> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVVoidSale PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). Copyright 2010 Proprietary Information Version: Page 18

19 Account:AcctNo o 1 24 A Prompt When the optional Account tag is included with the value Prompt, the PIN pad will prompt the operator for manual input of account number and expiration date from the card. InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo AuthCode R 1 24 A The value of <AuthCode> returned in the response to the EMVSale to be voided. Amount:Purchase R 1 8 N Purchase price (with 2 place decimal eg ) Amount:Gratuity O 1 8 N Gratuity Amount (with 2 place decimal eg ) SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Request for EMVVoidSale <TStream> <Transaction> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTrace>Dev1</UserTrace> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVVoidSale</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo> </InvoiceNo> <RefNo> </RefNo> <AuthCode>006896</AuthCode> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Response for EMVVoidSale <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTrace>Dev1</UserTrace> </CmdResponse> Copyright 2010 Proprietary Information Version: Page 19

20 <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************0020</AcctNo> <CardType>M/C</CardType> <TranCode>EMVVoidSale</TranCode> <AuthCode>000000</AuthCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo> </InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. VOID SALE </Line4> <Line5>.</Line5> <Line6>.************0020</Line6> <Line7>.M/C ENTRY METHOD: CHIP</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/01/14 TIME: 16:54:23</Line9> <Line10>.</Line10> <Line11>.INV#: APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Merchant Signature </Line27> <Line28>.</Line28> <Line29>.</Line29> <Line30>.Application Label:MasterCard</Line30> <Line31>.AID:A </Line31> <Line32>.TVR: </Line32> <Line33>.TSI:A800</Line33> <Line34>.RESP CD:</Line34> </PrintData> </RStream> Copyright 2010 Proprietary Information Version: Page 20

21 3.6 EMVReturn Use: To process a return (refund) using EMV capable equipment. Credit and Debit transactions with chip, MSR and manually input account information are supported. XML Template: EMVReturn XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> optional (9000 unless supplied) <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVReturn</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <Account> <AcctNo>AcctNo</AcctNo> </Account> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <Amount> <Purchase>Purchase</Purchase> <Gratuity>Gratuity</Gratuity> </Amount> <Duplicate>Duplicate</Duplicate> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVReturn PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). Copyright 2010 Proprietary Information Version: Page 21

22 Account:AcctNo o 1 24 A Prompt When the optional Account tag is included with the value Prompt, the PIN pad will prompt the operator for manual input of account number and expiration date from the card. InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo Amount:Purchase R 1 8 N Purchase price (with 2 place decimal eg ) Amount:Gratuity O 1 8 N Gratuity Amount (with 2 place decimal eg ) Duplicate O 1 24 A None OR Override (See implementation note 1) SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Canadian EMV Return Request <TStream> <Transaction> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTraceData>Dev1</UserTraceData> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVReturn</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>5</InvoiceNo> <RefNo>5</RefNo> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Canadian EMV Return Response <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTraceData>Dev1</UserTraceData> </CmdResponse> <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************0020</AcctNo> Copyright 2010 Proprietary Information Version: Page 22

23 <CardType>M/C</CardType> <TranCode>EMVReturn</TranCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo>5</InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. REFUND </Line4> <Line5>.</Line5> <Line6>.************0020</Line6> <Line7>.M/C ENTRY METHOD: CHIP</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/01/14 TIME: 16:54:50</Line9> <Line10>.</Line10> <Line11>.INV#: 5 APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Merchant Signature </Line27> <Line28>.</Line28> <Line29>.</Line29> <Line30>.Application Label:MasterCard</Line30> <Line31>.AID:A </Line31> <Line32>.TVR: </Line32> <Line33>.TSI:A800</Line33> <Line34>.RESP CD:</Line34> </PrintData> </RStream> Implementation Notes: 1. The Duplicate tag applies to Global Payment Systems and Mercury Payment Systems. In the event that an APDUPE response is received for a request, using a value of Override for the Duplicate tag on a subsequent attempt will force the processing host to skip duplicate checking and therefore approve what appears to be a duplicate transaction. This is useful in cases where multiple transactions of the same amount to the same card within a short time period are necessary. Copyright 2010 Proprietary Information Version: Page 23

24 3.7 EMVVoidReturn Use: To void a previous EMVReturn. XML Template: EMVVoidReturn XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> optional (9000 unless supplied) <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVReturn</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <Account> <AcctNo>AcctNo</AcctNo> </Account> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <Amount> <Purchase>Purchase</Purchase> <Gratuity>Gratuity</Gratuity> </Amount> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVVoidReturn PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). Account:AcctNo o 1 24 A Prompt When the optional Account tag is included with the value Prompt, the PIN pad will prompt the operator for Copyright 2010 Proprietary Information Version: Page 24

25 manual input of account number and expiration date from the card. InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo AuthCode R 1 24 A The value of <AuthCode> returned in the response to the EMVSale to be voided. Amount:Purchase R 1 8 N Purchase price (with 2 place decimal eg ) Amount:Gratuity O 1 8 N Gratuity Amount (with 2 place decimal eg ) SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Canadian EMVVoidReturn Request <TStream> <Transaction> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTraceData>Dev1</UserTraceData> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVVoidReturn</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo> </InvoiceNo> <RefNo> </RefNo> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Canadian EMVVoidReturn Response <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTraceData>Dev1</UserTraceData> </CmdResponse> <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************0020</AcctNo> <CardType>M/C</CardType> Copyright 2010 Proprietary Information Version: Page 25

26 <TranCode>EMVVoidReturn</TranCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo> </InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. VOID REFUND </Line4> <Line5>.</Line5> <Line6>.************0020</Line6> <Line7>.M/C ENTRY METHOD: CHIP</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/01/14 TIME: 16:55:11</Line9> <Line10>.</Line10> <Line11>.INV#: APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Merchant Signature </Line27> <Line28>.</Line28> <Line29>.</Line29> <Line30>.Application Label:MasterCard</Line30> <Line31>.AID:A </Line31> <Line32>.TVR: </Line32> <Line33>.TSI:A800</Line33> <Line34>.RESP CD:</Line34> </PrintData> </RStream> Copyright 2010 Proprietary Information Version: Page 26

27 3.8 EMVVoiceAuth Use: To capture a previously voice authorized transaction. XML Template: EMVVoiceAuth XML Request Template: <?xml version= 1.0?> <TStream> <Transaction> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> optional (9000 unless supplied) <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVVoiceAuth</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <Account> <AcctNo>AcctNo</AcctNo> </Account> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <Amount> <Purchase>Purchase</Purchase> <Gratuity>Gratuity</Gratuity> </Amount> <Duplicate>Duplicate</Duplicate> <SequenceNo>SequenceNo</SequenceNo> </Transaction> </TStream> Element Req Min Max Type Description HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVVoiceAuth PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). Copyright 2010 Proprietary Information Version: Page 27

28 Account:AcctNo o 1 24 A Prompt When the optional Account tag is included with the value Prompt, the PIN pad will prompt the operator for manual input of account number and expiration date from the card. InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo AuthCode R 1 24 A The authorization code obtained via telephone to the processing provider.. Amount:Purchase R 1 8 N Purchase price (with 2 place decimal eg ) Amount:Gratuity O 1 8 N Gratuity Amount (with 2 place decimal eg ) Duplicate O 1 24 A None OR Override (See implementation note 1) SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a SequnceNo value) to re-sync. Legend: A Alphanumeric N Numeric O Optional R Required Sample Canadian EMVVoiceAuth Request <TStream> <Transaction> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTraceData>Dev1</UserTraceData> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVVoiceAuth</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>6</InvoiceNo> <RefNo>6</RefNo> <AuthCode>123456</AuthCode> <Amount> <Purchase>10.00</Purchase> </Amount> <SequenceNo> </SequenceNo> </Transaction> </TStream> Sample Canadian EMVVoiceAuth Response <RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>APPROVED</TextResponse> <SequenceNo> </SequenceNo> <UserTraceData>Dev1</UserTraceData> Copyright 2010 Proprietary Information Version: Page 28

29 </CmdResponse> <TranResponse> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <AcctNo>************0020</AcctNo> <CardType>M/C</CardType> <TranCode>EMVVoiceAuth</TranCode> <AuthCode>123456</AuthCode> <CaptureStatus>Captured</CaptureStatus> <RefNo> </RefNo> <InvoiceNo>6</InvoiceNo> <OperatorID>55</OperatorID> <Amount> <Purchase>10.00</Purchase> <Authorize>10.00</Authorize> </Amount> </TranResponse> <PrintData> <Line1>.MERCHANT ID: </Line1> <Line2>.TERM ID: 009</Line2> <Line3>.</Line3> <Line4>. POST AUTH </Line4> <Line5>.</Line5> <Line6>.************0020</Line6> <Line7>.M/C ENTRY METHOD: CHIP</Line7> <Line8>.</Line8> <Line9>.DATE: 2010/01/14 TIME: 16:55:38</Line9> <Line10>.</Line10> <Line11>.INV#: 6 APPR CODE: </Line11> <Line12>.RETRIEVAL #: </Line12> <Line13>.</Line13> <Line14>.AMOUNT $ 10.00</Line14> <Line15>. ==========</Line15> <Line16>.TOTAL $ 10.00</Line16> <Line17>.</Line17> <Line18>. APPROVED - THANK YOU </Line18> <Line19>.</Line19> <Line20>.I AGREE TO PAY THE ABOVE TOTAL AMOUNT</Line20> <Line21>.ACCORDING TO CARD ISSUER AGREEMENT</Line21> <Line22>.(MERCHANT AGREEMENT IF CREDIT VOUCHER)</Line22> <Line23>.</Line23> <Line24>.</Line24> <Line25>.</Line25> <Line26>.x </Line26> <Line27>. Merchant Signature </Line27> <Line28>.</Line28> <Line29>.</Line29> <Line30>.Application Label:MasterCard</Line30> <Line31>.AID:A </Line31> <Line32>.TVR: </Line32> <Line33>.TSI:A800</Line33> <Line34>.RESP CD:</Line34> </PrintData> </RStream> Implementation Notes: 1. The Duplicate tag applies to Global Payment Systems and Mercury Payment Systems. In the event that an APDUPE response is received for a request, using a value of Override for the Duplicate tag on a subsequent attempt will force the processing host to skip duplicate checking and therefore approve what appears to be a duplicate transaction. This is useful in cases where multiple transactions of the same amount to the same card within a short time period are necessary. Copyright 2010 Proprietary Information Version: Page 29

30 3.9 EMVPublicKeyReport Use: To print the public key report for the EMV PIN pad. The ECR/POS must support the EMVPublicKeyReport and make it available as an administrative function. XML Template: EMVPublicKeyReport XML Request Template: <?xml version= 1.0?> <TStream> <Admin> <HostOrIP> </HostOrIP> <IpPort>99999</IpPort> <MerchantID>MerchantID</MerchantID> <TerminalID>TerminalID</TerminalID> <OperatorID>OperatorID</OperatorID> <UserTraceData>UserTraceData</UserTraceData> <MerchantLanguage>MerchantLanguage</MerchantLanguage> <TranCode>EMVPublicKeyReport</TranCode> <PadType>PadType</PadType> <ComPort>ComPort</ComPort> <InvoiceNo>InvoiceNo</InvoiceNo> <RefNo>RefNo</RefNo> <SequenceNo>SequenceNo</SequenceNo> </Admin> </TStream> Element Req Min Max Type Description HostOrIP R A IP address of server to use for this transaction. IpPort O 1 5 N IP port number on server to use for this transaction. If omitted, default port is MerchantID R 1 24 A Merchant identification assigned by processor. TerminalID R 1 24 A Terminal ID as assigned by the processor. OperatorID O 1 24 A Operator (clerk, server, etc.) associated with the transaction. UserTraceData O 1 24 A A unique value created and supplied by POS system. MerchantLanguage R 6 7 A English or French TranCode R 1 40 A EMVPublicKeyReport PadType R 1 24 A Paymentech1 for Paymentech Global1 for Global or Mercury ComPort R 1 3 N COM (Serial) port number to which a EMV approved PIN pad is attached (1-255). InvoiceNo R 1 24 A Invoice number - sequential receipt number, check number, or other unique transaction identifier created and supplied by POS system. RefNo R 1 24 A Use the same data as InvoiceNo SequenceNo R A The sequence number returned in all responses to be used on the next request. If the SequenceNo is lost or if it is the initial deployment of the PIN pad, the ECR/POS should attempt any transaction (using as a Copyright 2010 Proprietary Information Version: Page 30

31 Legend: A Alphanumeric N Numeric O Optional R Required SequnceNo value) to re-sync. Sample Canadian EMVPublicKeyReport Request <TStream> <Admin> <HostOrIP>ePayServer</HostOrIP> <IpPort>9000</IpPort> <MerchantID> </MerchantID> <TerminalID>009</TerminalID> <OperatorID>55</OperatorID> <UserTraceData>Dev1</UserTraceData> <MerchantLanguage>English</MerchantLanguage> <TranCode>EMVPublicKeyReport</TranCode> <PadType>Paymentech1</PadType> <ComPort>1</ComPort> <InvoiceNo>12</InvoiceNo> <RefNo>12</RefNo> <SequenceNo> </SequenceNo> </Admin> </TStream> Sample Canadian EMVPublicKeyReport Response <RStream> <CmdResponse> <ResponseOrigin>Server</ResponseOrigin> <DSIXReturnCode>00000</DSIXReturnCode> <CmdStatus>Success</CmdStatus> <TextResponse>Record Found</TextResponse> <SequenceNo> </SequenceNo> <UserTraceData>Dev1</UserTraceData> </CmdResponse> <TranResponse> <TranCode>EMVPublicKeyReport</TranCode> </TranResponse> <PrintData> <Line1>. EMV PUBLIC KEY LOAD REPORT </Line1> <Line2>.</Line2> <Line3>.MERCHANT ID: </Line3> <Line4>.TERM ID: 009</Line4> <Line5>.DATE: 2010/01/14 TIME: 17:04:33</Line5> <Line6>.</Line6> <Line7>. CARD ASSOCIATION: VISA </Line7> <Line8>.</Line8> <Line9>.RID: A </Line9> <Line10>.KEY INDEX: 92</Line10> <Line11>.KEY MODULUS</Line11> <Line12>.99 6A F5 6F D0</Line12> <Line13> C E D8</Line13> <Line14>.---</Line14> <Line15>.D4 6A D8 E3 0A 24 7C 9F</Line15> <Line16>.KEY EXPONENT: 03</Line16> <Line17>.</Line17> <Line18>.RID: A </Line18> <Line19>.KEY INDEX: 94</Line19> <Line20>.KEY MODULUS</Line20> <Line21>.AC D2 B EE 64 4F</Line21> <Line22>.3F 83 5A BD 1F C7 A6 F6</Line22> <Line23>.---</Line23> <Line24> A2 6E 0F C6 17</Line24> <Line25>.KEY EXPONENT: 03</Line25> <Line26>.</Line26> <Line27>.RID: A </Line27> Copyright 2010 Proprietary Information Version: Page 31