Release Notes

Release Notes

  • Year 2018 (Builds 6856 - 6577)

    Build 6856 (version 16.0.6856) – October 9, 2018

    • Adds support for FSA/HSA/HRA transactions in FDMS Rapid Connect. A new component is exposed named FDMSRcHealthCare to enable users to process Healthcare transactions in FDMS Rapid Connect platform.
    • Adds support for Void of Return transactions in FDMS Rapid Connect components.
    • Updated the generation of ClientRef tag in FDMS North/Nashville Session transactions processed through Datawire to follow the latest specifications. Adds a new property in FDMSSettle component “ApiVersion” and updated the existing “BatchSequenceNumber” property.
    • Adds new value raTaxExempt (5) for “ReimbursementAttribute” property in TSYSDebit and TSYSReversal components and “DebitReimbursementAttribute” property in TSYSDetailRecord component.

    User action: Make sure to set the “BatchSequenceNumber” property in FDMSSettle component as instructed in our documentation to follow the latest specifications. This property should contain a 7-digit unique transaction sequence identifier. You may set the “ApiVersion” property in FDMSSettle component to reflect your application Version and Revision Number. Default value of “ApiVersion” indicates the current Version and Revision number of 4D Payments SDK.


    Build 6802 (version 16.0.6802) – August 16, 2018

    • Adds support for Visa Merchant Initiated Transactions (MIT) in TSYS components.
    • Adds configuration settings “IsMerchantInitiatedTransaction” to indicate a Visa MIT transaction, “MITTransactionId” to hold the Transaction Id associated with the original authorization of a Visa MIT transaction and “MessageReasonCode” to identify the reason for the Visa MIT transaction in TSYSRetail and TSYSECommerce components.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support Visa MIT transactions with TSYS you can. Note that depending on the type of the Visa MIT transaction (MIT Standing Instruction or MIT Industry Practice) you may set either the “POSEnvironmentIndicator” or “MessageReasonCode” configuration settings respectively, but not both.


    Build 6726 (version 16.0.6726) – June 1, 2018

    • Adds support for Electronic Benefits Transfer (EBT) transactions in FDMS Rapid Connect. A new component is exposed named FDMSRcBenefit to enable users to process Food Stamp, Cash Benefit and eWIC transactions in FDMS Rapid Connect platform.
    • Adds “TerminalLocationIndicator” configuration setting in FDMS Rapid Connect components to enable users to set this field according to their needs.
    • Adds support for Swiped Verification transactions in FDMSRcRetail component.
    • Updates the default value of “CombineRecords” configuration setting in TSYSSettle component to ‘True’ to optimize message size and expedite the overall settlement process by minimizing the total number of settlement packets.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support EBT transactions with FDMS Rapid Connect you can.


    Build 6696 (version 16.0.6696) – May 02, 2018

    • Adds support for Partial Reversals in TSYS Host Capture components. Adds new “SettleAmount” property in TSYSHCReversal component to indicate the final settlement amount when running Partial Reversals.
    • Adds support for Food Stamp Authorization Reversals, Cash Benefit Authorization Reversals, Food Stamp Credit Reversals and Cash Benefit Credit Reversals in TSYS Host Capture components. Adds new values for “TransactionType” property in TSYSHCReversal component: ttFoodStampAuthorizationReversal(4), ttCashBenefitAuthorizationReversal(5), ttFoodStampCreditReversal(6) and ttCashBenefitCreditReversal(7).
    • Adds support for Retail/Restaurant Card NOT Present transactions in TSYS Host Capture components. Adds “CardPresent” property in TSYSHCRetail component to indicate that this is a Card Present transaction.
    • Adds support for fields: Partial Authorization Indicator in ecommerce and debit transactions, MasterCard Paypass Mobile in MasterCard Contactless transactions, Authorization Indicator required in all MasterCard transactions and POS Environment Indicator required for ecommerce Recurring and Installment transactions. Adds the configuration settings: “AllowPartialAuths”, “DomainServer”, “MobileDeviceType”, “AuthorizationIndicator” and “POSEnvironmentIndicator” in TSYS Host Capture components.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support all the above mentioned transactions with TSYS Summit you can.


    Build 6687 (version 16.0.6687) – April 23, 2018

    • Adds support for Bill Payment Reversals in TSYS components.
    • Adds “Retry” configuration setting in TSYSReversal component to retry a failed Bill Payment Reversal.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support Bill Payment Reversal transactions with TSYS you can.


    Build 6660 (version 16.0.6660) – March 27, 2018
    Does not send Card Verification Code 2 field in Visa manually entered Card Present transactions following the Visa article on the CVV2 requirement changes.
    User action: No action is required from the user and no impact on your current system.


    Build 6627 (version 16.0.6627) – February 22, 2018

    • Adds support for Amex Payment Service Provider/Aggregator fields in TSYS components.
    • Adds configurations settings “MerchantSellerID”, “LocationDetailPhone”, “LocationDetailEmail”, and “AmexAggregatorName” in TSYSRetail and TSYSECommerce components apart from the ones that are currently available: “LocationDetailName”, “LocationDetailAddress”, “LocationDetailCity”, “LocationDetailRegion”, “LocationDetailCountry”, and “LocationDetailPostal”.
    • Adds “AmexAggregatorName” configuration setting in TSYSSettle component for merchants participating in Amex OptBlue program.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support Amex transactions originating from a Payment Service Provider/Aggregator with TSYS you can.


    Build 6610 (version 16.0.6610) – February 5, 2018

    Addresses an issue with Payment Facilitator fields that were not being send in TSYS detail records during settlement, due to incorrect EIS 1081 specifications.


    Build 6577 (version 16.0.6577) – January 3, 2018

    Adds support for Existing Debt Indicator field in TSYS components

    Year 2017 (Builds 6561 - 6276)

    Build 6561 (version 16.0.6561) – December 18, 2017

    Update per TSYS specs – send G3v001 only for Visa and MasterCard transactions in TSYS components


    Build 6550 (version 16.0.6550) – December 11, 2017

    Enables users to set the UserAgent in their requests to FDMS platforms


    Build 6549 (version 16.0.6549) – December 7, 2017

    Update per FDMS specs – send EcommURL in FDMS Rapid Connect e-Commerce Authorizations


    Build 6547 (version 16.0.6547) – December 7, 2017

    Adds support for HostTotals transaction in FDMS Rapid Connect components


    Build 6534 (version 16.0.6534) – November 21, 2017

    Adds support for RP token in Paymentech EMV transactions


    Build 6529 (version 16.0.6529) – November 17, 2017

    Adds support for Authorization Type field in FDMS Rapid Connect components


    Build 6512 (version 16.0.6512) – November 1, 2017

    Updates the schema version in FDMS Rapid Connect components


    Build 6507 (version 16.0.6507) – October 25, 2017

    Changes the formatting of the Merchant Zip field in TSYS components to remove spaces and dashes before appending the field to the request


    Build 6501 (version 16.0.6501) – October 21, 2017

    Fixes a bug when setting the Verification Code in TSYS and TSYSHC components


    Build 6500 (version 16.0.6500) – October 19, 2017

    Adds support for Transaction Integrity Class in TSYS components


    Build 6486 (version 16.0.6486) – October 5, 2017

    Adds support for Unattended Terminal Indicator Token in Paymentech components


    Build 6485 (version 16.0.6485) – October 3, 2017

    Adds support for MasterCard UCAF transactions in TSYS components


    Build 6479 (version 16.0.6479) – September 27, 2017

    Fixes an issue with card type determination when parsing the aggregate for subsequent requests in FDMSRc components


    Build 6457 (version 16.0.6457) – September 6, 2017

    Fixes a bug in level 2 transactions in TSYS Host Capture Components


    Build 6439 (version 16.0.6439) – September 4, 2017

    Adds support for B4-B6 subfields of A101 group in TSYS HC components and updates Level2 property description in help files


    Build 6432 (version 16.0.6432) – September 4, 2017

    Adds support for MasterCard UCAF transactions in TSYS HC components


    Build 6430 (version 16.0.6430) – August 9, 2017

    • Updates the Registration and Activation requests for Rapid Connect platform to follow the latest DataWire specs (FDMSRegister component)
    • Fixes a bug in ServiceDiscovery for FDMS Rapid Connect platform

    Build 6429 (version 16.0.6429) – August 9, 2017

    Add support for G3v071-POS Environment Indicator sent in VISA Card-On-File transactions in TSYS components


    Build 6423 (version 16.0.6423) – August 2, 2017

    Add support for TSYS VISA Purchase Return Authorizations and VISA Purchase Return Authorization Reversals


    Build 6418 (version 16.0.6418) – July 28, 2017

    • Fixes an issue with Transaction Code sent for Quasi Cash transactions in the batch Detail Records during settlement (TSYS components)
    • Fixes an issue with Transaction Code sent for Force/Offline Bill Payment transactions in TSYS components

    Build 6410 (version 16.0.6410) – July 20, 2017

    • Fixes an inconsistency with the Data Entry Source sent in the EMV authorizations and the detail records in Paymentech components
    • Fixes a bug with TS token value saved in the detail aggregate of PTech components

    Build 6387 (version 16.0.6387) – June 29, 2017

    Adds support for detail aggregates in host capture debit transactions (PTechCharge and PTechDebit)


    Build 6386 (version 16.0.6386) – June 26, 2017

    Adds two new values for the ReversalReason property of the PTechReversal component following the latest Chase Paymentech specs. Previously supported values were 0-3 (rrNotSet, rrNoResponseFromHost, rrLateResponseFromHost, and rrUnableToDeliverToPOS, respectively). The new values added are:

    • 4 = Card declined the transaction (applicable only to EMV transactions)
    • 9 = Auth Reversal Suspected Fraud

    User action: No action is required from the user and no impact on your current system.

    Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. Furthermore, this is a minor change that does not provide sufficient enhancement of functionality or otherwise to justify a minor version increase. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6386 (full version 16.0.6386).


    Build 6383 (version 16.0.6383) – June 23, 2017

    Exposed a new Config “IsPassengerTransport” in TSYSEcommerce component. When set to True, the transaction will be sent as a PassengerTransport transaction. Default value is False.

    User action: No action is required from the user and no impact on your current system. However, if you wish to utilize the TSYSEcommerce component for processing Passenger Transport transactions you can do so by setting the “IsPassengerTransport” config to True.

    Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. Furthermore, this is a minor change that does not provide sufficient enhancement of functionality or otherwise to justify a minor version increase. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6383 (full version 16.0.6383).


    Build 6376 (version 16.0.6376) – June 16, 2017

    Exposed a new Config “ODG46” in TSYSDetailRecord component. ODG46 (Merchant Descriptor) is an optional non-settlement field that is used for merchant and client informational purposes. You do not need to set this config but if you wish to send it for certain transactions you may do so.

    User action: No action is required from the user and no impact on your current system.

    Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. Furthermore, this is a minor change that does not provide sufficient enhancement of functionality or otherwise to justify a minor version increase. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6376 (full version 16.0.6376).


    Build 6326 (version 16.0.6326) – April 28, 2017

    • Adds the Passenger Transport (sitPassengerTrasnport) IndustryType for TSYS components
    • Adds a new configuration setting for G3v028: AMEX Airline Passenger Data (APD) named “AmexAirlinePassengerData”. When this config is set, the industry type is sitPassengerTrasnport and card type is Amex, the G3v028 APD field will be appended to the request following the TSYS specifications.
    • Adds configs “TravelAgencyCode” and “TravelAgencyName”in TSYSSettle to set the ODG1 subfields. This ODG must be set for Visa Passenger Transport Transactions (Capture)
    • Adds configs: “RestrictedTicketIndicator”, “TicketNumber”, “PassengerName”, “DepartureDate”, “Origin”, “Leg1”, “Leg2”, “Leg3” and “Leg4” to set the ODG9 subfields. • Adds “PassengerNumber” and “PassengerCount” property in TSYSDetailRecord component to set the ODG9 subfields. They stand for Multiple Clearing Sequence Number and Multiple Clearing Sequence Count, respectively. • When industry type is sitPassengerTransport, card type is Visa and the required ODG9 fields are set, the component builds the request accordingly, otherwise an error is thrown indicating that the card is not Visa or that the required fields are missing.

    User action: No action is required from the user and no impact on your current system. However, if you wish to support Passenger Transport transactions with TSYS you can.

    Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. A minor version increment was considered due to the fact that this new build adds support for an industry type however, we decided to not increment at this time. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6376 (full version 16.0.6376).


    Build 6278 (version 16.0.6278) – March 20, 2017

    The last build version (16.0.6278) provides support for the following functionalities and/or is subject to the following changes, following the specifications provided by Paymentech processor:

    • Updated the test server URLs in the powershell scripts accompanying the gateway, located in the installation folder under /www.
    • Added support for RN, P1 and P2, and P8 tokens in Electronic Benefit Transfer transactions. The following configuration settings are exposed in PTechBenefit component to enable you to send these tokens, respectively:
      • POSRetrivalNumber (RN token): Merchant-generated reference number used for Reversals.
      • VendorID, SoftwareID, HardwareSerialNum (P1 token)
        • VendorID: Hardware/Vendor Identifier assigned by Paymentech at the time of certification.
        • SoftwareID: Software Identifier assigned by Paymentech at the time of certification.
        • HardwareSerialNum: Used to determine the serial number of the hardware device.
      • HostProcessingTypes (P2 token): Determines the host processing platform.
      • AllowPartialAuths, RequestBalanceInfo (P8 token)
        • AllowPartialAuths: Used to indicate whether partial authorizations are supported. Default value is ‘True’.
        • RequestBalanceInfo: Used to specify whether to request balance information. Default value is ‘False’.
      • DeviceID (DP token): Used to specify the device user, retail lane, fuel pump etc. to identify where the transaction originated from.

    User action: No action is required from the user and no impact on your current system.

    Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. Furthermore, this is a minor change that does not provide sufficient enhancement of functionality or otherwise to justify a minor version increase. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6278 (full version 16.0.6278).


    Build 6276 (version 16.0.6276) – March 17, 2017

    The last build version (16.0.6276) provides support for the following functionalities and/or is subject to the following changes, following the specifications provided by the Global Payments processor:

    • Support swiped EMV credit and debit card transactions. Support manual EMV credit card transactions. New supported for EMVEntryDataSource configuration setting are the following:
      • 4 – EMV Swipe.
      • 5 – EMV Manual.
    • Added the Device Capability fields in the request message of credit and debit transactions following the specifications in the latest Global Payments API release. Exposed the following configuration settings:
      • PINCapable (GlobalDebit component): used to indicate if the POS device is capable of accepting PINs.
      • ContactOnly (GlobalCharge and GlobalDebit components): used to indicate if the device is only able to accept EMV chip card transactions.
    • Note that following the Global Payments specifications the EMVCapable configuration setting in GlobalCharge and GlobalDebit components must be set to ‘True’ for swiped and keyed fallback transactions. If otherwise an error will be thrown indicating you to set this value to ‘True’.
    • Added support for track1 contactless and track2 contactless transactions. New supported values:
      • 5 – edsTrack1Contactless
      • 6 – edsTrack2Contactless

      of Card.EntryDataSource property in Global Payments components are valid only for AuthOnly and Sale transactions.

    • User action: No action is required from the user and no impact on your current system.

      Impact on the version number: this change has no impact on security and / or PA-DSS requirements and consequently there is no need to increment the major version number. Furthermore, this is a minor change that does not provide sufficient enhancement of functionality or otherwise to justify a minor version increase. Therefore, the version number will remain at 16.0 (2016.0) whereas the automatically incremented build number will be 6276 (full version 16.0.6276).

  • Still Need Help?


    Send us an email at: support@4dpayments.com.