Differences

This shows you the differences between two versions of the page.

--- vantiv_pin_debit_upgrade [2016/03/23 10:11 (8 years ago)] – [What CVM Option Should a Merchant Select?] craig
+++ vantiv_pin_debit_upgrade [2017/02/01 11:59 (7 years ago)] (current) – [What you need to know about NETePay version 5.06.11 and MSD PIN Debit] craig
@@ Line 18: / Line 18: @@
   * A Load New Parameter must be sent after the new DeploymentID is entered or the existing PSCS stage has been updated Vantiv Integrated Payments Technical Support team. This brings the new swiped debit configuration to the local NETePay
   * An EMVParmeterDownload command must then be used to download the new parameter to the pad.
-  * Version 1.03 of the dsiEMVUS client must be installed.
+  * Version 1.03 or higher of the dsiEMVUS client must be installed.
   * Merchants not planning to support PIN debit can continue to use earlier versions of NETePay.
@@ Line 30: / Line 30: @@
 ===== What Card Verification Method (CMV) Option Should a Merchant Select? =====
-<note tip>The CVM is the method in which the merchant confirms that the card is in the hands of the card holder. The options are signature or PIN.  Normally the PIN Pad is set to use the method that the EMV chip was programmed with, however this can be overridden by the PIN pad to use signature only. If you use signature, the merchant/clerk is responsible for verifying the signature and the merchant may be liable for the transaction if this is not done and the transaction was fraudulent. \\</note>
+<note tip>The CVM is the method in which the merchant confirms that the card is in the hands of the card holder. The options are signature or PIN.  Normally the PIN Pad is set to use the method that the EMV chip was programmed with, however this can be overridden by the PIN pad to use signature only. If you use signature, the merchant/clerk is responsible for verifying the signature and the merchant may be liable for the transaction if this is not done and the transaction was fraudulent.</note>
 The dsiEMVUS solution now supports two options for card verification method (CVM) prompts. It is important to understand the differences, the risks associated and merchant use cases to help decide the best option. Merchants generally processing in the restaurant or QSR verticals may be better suited to support Chip+Signature CVM. However, any merchant can request this CVM option based on their need.