Devconnect Content Creation Menu Block


Certificate change to

Payeezy API Sandbox environment is updated with the latest certificate as of July 17th 2018. Merchants can test SDK update in this environment as of now.

On Friday 7/20 between 3-6 am ET certificate will be temporarily updated in production. You have an opportunity to test in production during this window. The certificate will be restored back before 6 am ET.

The permanent update of the certificate in production is scheduled for Wed 7/25 at 3 AM ET.


TLS 1.2 Migration

In compliance with PCI SSC direction that all processors must upgrade to current versions of TLS (Version 1.2 recommended), Payeezy API will be disabling all non-compliant SSL and TLS protocols (TLS 1.0 and 1.1) in each environment as outlined in the below schedule.

Sandbox ( - Jan 10,2018
Live - ( - Jan 24, 2018


Payeezy API Mandated Change of Request Method

First Data remains vigilant in protecting data and ensuring that our products and services are compliant with industry standards and PCI requirements. In order to further improve the protection of sensitive cardholder data, the GET request method for the Tokenization Credit Card API will be replaced with a Tokenization Credit Card API call that uses the POST request method. The new call has been published in the Payeezy Developer Portal (


Removal of CVV Field From API Response

In a token-based transaction, the CVV number can be included as an optional field in the request payload.

Today, if the CVV number is included in the request payload, it is echoed back in the response by Payeezy API. This CVV number in the API response is redundant and will be removed from the API response. The highlighted below will be removed from the API Response: