--- title: DSIEMVClientX® slug: datacap-api-overview/dsiemvclientxr docTags: createdAt: 2026-09-01T15:15:50.705Z --- :::hint{type="warning"} DSIEMVClientX is a Canada only solution. ::: 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 via USB/Serial (recommended) or IP to manage all PIN pad interactions. The DSIEMVClientX control uses XML formatted requests and responses for transaction processing requests. ## Differences between US and Canadian Integration 1. Support for Credit and Debit (Interac) is required. 2. Contactless transaction limit and CVM limit is $250.00 for all cards except JCB. 3. Contactless transaction limit and CVM limit is $100.00 for JCB. 4. Store and Forward (offline processing) is supported - credit only. 5. Cash Back is not allowed 6. SurchargeWithLookup is not supported 7. PaymentFee is not supported 8. EMVSaleWithSplit is not supported 9. SequenceNo value is returned by the processors in Canada. The SequenceNo value is tracked per terminal 10. Prompting for tip at time of sale is supported 11. Support for English and French languages 12. Additional XML Response tags are returned for receipt printing specific to merchant and customer language. 13. Receipt data is returned for merchant and customer copy | **Tag** | **Description** | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `` | **(String 6-7 chars)** Returns a value of French or English. This value is used by the POS to determine the language to be used to print the Merchant receipt header (“TRANSACTION RECORD” or “RELEVE DE TRANSACTION”) | | `` | **(String 6-7 chars)** Returns a value of French or English. This value is used by the POS to determine the language to be used to print the Customer receipt header (“TRANSACTION RECORD” or “RELEVE DE TRANSACTION”) | | `` | **(Number 3 chars)** 3 digit response code from Canadian Host. | Receipts -------- For Canada, receipt data is returned for the merchant and customer copy. Two separate sets of receipt data are returned. The merchant receipt is returned in tags `` to ``. The customer receipt is returned in tags `` to ``. The merchant receipt is generated in the language of the merchant and corresponds with Merchant Language set as the PSCS parameter. The customer receipt is generated in the cardholder language. Before printing the receipt, the POS should still print the receipt header, merchant name, address, and phone number as separate lines at the top of the receipt. ### ## EMV Transactions and Operations Supported by DSIEMVClientX The following transaction codes TranCode are supported in DSIEMVClientX ### Transactions | **Operation** | **Definition** | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | EMVPadReset | 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. | | EMVKeyChange | This command should be performed on demand from outside source OR when a pad is replaced OR new PIN pad installation | | EMVParamDownload | This command loads essential parameter and security information into the EMV PIN pad. This command must be performed as requested by the payment service provider OR when a pad is replaced OR new PIN pad installation | | EMVSale | EMV Sale transaction | | EMVVoidSale | Void of a previously completed EMV Sale transaction | | EMVReturn | EMV Return transaction | | EMVVoidReturn | Void of a previously completed EMV Return transaction | | VoidSaleByRecordNo | To void a previously processed EMVSale transaction without a card present – credit. Available on select Processors. | | VoidReturnByRecordNo | Void of a previously completed EMVReturn transaction without a card present – credit. Available on select Processors. | | EMVPreAuth | To preauthorize a credit card which must be subsequently captured for settlement. Credit cards only are supported. Available on select Processors. | | PartialReversalByRecordNo | To decrease the authorized amount of a previous PreAuth transaction. Available on select Processors. | | PreAuthCaptureByRecordNo | To add a gratuity to a previously processed EMVPreAuth transaction and capture the transaction to the current batch. Available on select Processors. | | EMVZeroAuth | To verify a card is valid without charging any amount. **This transaction does not create a charge/debit to the cardholder account and no funds will be accrued to the merchant.** Available on select Processors. | ## Supported EMV PIN Pad Devices (PadType) | **Device/Payment Processing Provider** | **`` Value** | | ---------------------------------------------------------------------------- | ---------------------------- | | Verifone VX820 - Chase Canada | Paymentech1 | | Verifone P400 - Chase Canada with Datacap PAN encryption | P400PaymentechDatacapE2E | | Verifone P400 - Chase Canada with Bluefin PAN encryption | P400PaymentechDatacapBlueFin | | PAX A6630 - Global Payments Canada via NETePay Hosted | A6630GlobalDatacapE2E | | PAX A6650 - Global Payments Canada via NETePay Hosted | A6650GlobalDatacapE2E | | PAX A920MAX - Global Payments Canada via NETePay Hosted | A920MaxGlobalDatacapE2E | | PAX A800 - Global Payments Canada via NETePay Hosted | A800GlobalDatacapE2E | | PAX A35 - Global Payments Canada via NETePay Hosted | A35GlobalDatacapE2E | | PAX A30 - Global Payments Canada via NETePay Hosted | A30GlobalDatacapE2E | | PAX A3700 - Global Payments Canada via NETePay Hosted | A3700GlobalDatacapE2E | | Verifone VX820 - Global Payments Canada | Global1 | | Verifone P400 - Global Payments Canada via NETePay Hosted Direct E2E | P400GlobalDatacapE2E | | Verifone P400 - Global Payments Canada via NETePay Hosted PCI-Validated P2PE | P400GlobalDatacapBlueFin | | PAX A920Pro - Global Payments Canada via NETePay Hosted | A920ProGlobalDatacapE2E | | PAX IM30 - Global Payments Canada via NETePay Hosted | IM30GlobalDatacapE2E | | PAX A35 - Moneris via NETePay Hosted | A35MonerisDatacapE2E | | PAX A920Pro - Moneris via NETePay Hosted | A920PROMonerisDatacapE2E | | PAX A920MAX - Moneris via NETePay Hosted | A920MAXMonerisDatacapE2E | | PAX A800 - Moneris via NETePay Hosted | A800MonerisDatacapE2E | | PAX A6630 - Moneris via NETePay Hosted | A6630MonerisDatacapE2E | | PAX A6650 - Moneris via NETePay Hosted | A6650MonerisDatacapE2E | | PAX A30 - Moneris via NETePay Hosted | A30MonerisDatacapE2E | | PAX A3700 - Moneris via NETePay Hosted | A3700MonerisDatacapE2E | | Ingenico iPP320 - MonerisPOSPad | MonerisPOSPAD | | Verifone P400 - MonerisPOSPad | MonerisPOSPAD | | PAX A800 - Worldpay Core Canada via NETePay Hosted | A800WPCoreDatacapE2E | | PAX A6630 - Worldpay Core Canada via NETePay Hosted | A6630WPCoreDatacapE2E | | PAX A6650 - Worldpay Core Canada via NETePay Hosted | A6650WPCoreDatacapE2E | | PAX A920Pro - Worldpay Core Canada via NETePay Hosted | A920ProWPCoreDatacapE2E | | PAX A920MAX - Worldpay Core Canada via NETePay Hosted | A920MaxWPCoreDatacapE2E | | PAX A35 - Worldpay Core Canada via NETePay Hosted | A35WPCoreDatacapE2E | | PAX A30 - Worldpay Core Canada via NETePay Hosted | A30WPCoreDatacapE2E | | PAX A3700 - Worldpay Core Canada via NETePay Hosted | A3700WPCoreDatacapE2E | | Verifone VX820 - Worldpay Integrated Payments Canada (MercuryPay) | Global1 | :::hint{type="info"} **Note:** For Moneris, PAX devices are only supported through the NETePay Hosted platform. ::: ## Request Access to DSIEMVClientX API :::CtaButton{label="Request Access" externalHref="https://dsidevportal.com/request-access" openInNewTab="true"} ::: :::hint{type="success"} **Get started:** Request developer credentials for free access to every product's integration guide. :::