Date Updated: 1/19/2020

The following updates were deployed to the Production environment on 1/19/2020.

Note: Visit status.cardconnect.com and click subscribe to updates to receive important release and status notifications.

Updated Cardholder Signature Requirements

The CardPointe Gateway now uses the amount value to determine whether or not a cardholder signature is required, based on the guidelines for each card brand.

The EMV tag data returned in the auth response includes a Cardholder Verification Method (CVM) indicator that determines if a PIN or signature is required.

Note: The CVM value is not used by Bolt terminals. In a Bolt transaction, the cardholder signature prompt is instead driven by the includeSignature parameter in the request or a separate request to the readSignature endpoint.

When the CVM response returned to the CardPointe Gateway includes signature:"true", the Gateway checks the amount and adjusts the signature value as follows:

  • For Visa transactions
    • if the amount is less than $25, then signature:"false".
    • if the amount is greater than or equal to $25, then signature:"true".
  • For Mastercard, Discover, and Amex transactions
    • if the amount is less than $50, then signature:"false".
    • if the amount is greater than or equal to $50, then signature:"true".

bin Field Added to the Authorization and Bin Response

The BIN service now returns the exact bank identification number (BIN) in the bin field in the following responses:

DPS Response Code Changes

The following DPS Payment Express (DPS) response codes have been added:

respprocrespcoderespstatresptext
DPSAQC"Amex not enabled"
DPSD4C"User blocked"
DPSD9C"Invalid merchant or password"

The following DPS response code has been removed:

respprocrespcoderespstatresptext
DPSD5C"Invalid password"

See Gateway Response Codes for a comprehensive list of response codes.

UAT Emulator Updates

The following updates have been made to better align the UAT emulators with the processor host responses received in the production environment:

  • The First Data Rapid Connect emulator now returns the emvTagData array in the auth response when an EMV test card is used.
  • The Paymentech emulator has been updated to support voids for Amex authorizations.