Open the Portico Developer Guide site
PosGateway Schema
PinBlock Element
PosGateway Schema > EBTFSVoucherReqBlock1Type Complex Type : PinBlock Element
Description

PIN block generated from the encrypted cardholder PIN and key serial number (KSN); see the guide for the specific PIN pad device being used to determine how to obtain the data elements required to create a PIN block.

Note: Portico requires the order of the data to be encrypted PIN followed by the KSN. If the encrypted PIN was 11111111 and the KSN was 22222222, the PIN block would have to be 1111111122222222 when sent to the gateway.

Note:This field has been deprecated. EBTVoucherPurchase does not support PINBlock verification and is ignored when sent.

Namespace http://Hps.Exchange.PosGateway
Type
pinBlockType Simple Type
Overview
PinBlock optional pinBlockType Simple Type

PIN block generated from the encrypted cardholder PIN and key serial number (KSN); see the guide for the specific PIN pad device being used to determine how to obtain the data elements required to create a PIN block.

Note: Portico requires the order of the data to be encrypted PIN followed by the KSN. If the encrypted PIN was 11111111 and the KSN was 22222222, the PIN block would have to be 1111111122222222 when sent to the gateway.

Note:This field has been deprecated. EBTVoucherPurchase does not support PINBlock verification and is ignored when sent.

Source
<xs:element name="PinBlock" type="pinBlockType" minOccurs="0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:annotation>
    <xs:documentation>
      <p xmlns="http://Hps.Exchange.PosGateway">PIN block generated from the encrypted cardholder PIN and key serial number (KSN); see the guide for the specific PIN pad device being used to determine how to obtain the data elements required to create a PIN block.</p>
      <p xmlns="http://Hps.Exchange.PosGateway" />
      <p xmlns="http://Hps.Exchange.PosGateway">
        <strong>Note:</strong> Portico requires the order of the data to be encrypted PIN followed by the KSN. If the encrypted PIN was 11111111 and the KSN was 22222222, the PIN block would have to be 1111111122222222 when sent to the gateway.
            </p>
      <p xmlns="http://Hps.Exchange.PosGateway" />
      <p xmlns="http://Hps.Exchange.PosGateway">
        <strong>Note:</strong>This field has been deprecated.  EBTVoucherPurchase does not support PINBlock verification and is ignored when sent.
            </p>
    </xs:documentation>
  </xs:annotation>
</xs:element>
See Also
EBTFSVoucherReqBlock1Type Complex TypePosGateway Schema