About Latest First Data (Payeezy) Gateway Transaction_tag Value Upgrade
If you are currently using VPCart First Data (Payeezy) Gateway Hosted Payment, you may have received this message:
On 08/09/2017, Payeezy Gateway will start issuing transaction_tag values exceeding 2,147,483,647. The Payeezy Gateway provides a unique identifying number called transaction_tag in the response payload of every transaction, and the number increments by one for every transaction processed. The transaction_tag value is approaching a numeric data type length limit (2,147,483,647) in the Payeezy Gateway database, which requires a new data type to be assigned. The updated data type will allow Payeezy Gateway to safely exceed the current maximum value.
Payeezy Gateway clients coming through Web-Service API or Payeezy API need to ensure their API integrations and databases will handle transaction_tag values exceeding 2,147,483,647; otherwise clients will be unable to process any transactions. Payeezy Gateway clients coming through Hosted Checkout (HCO) need to check their HCO message to ensure their databases will handle transaction_tag values exceeding 2,147,483,647; otherwise clients will be unable to process any transactions.
From the information above, Payeezy has upgraded their response field transaction_tag value.
In our VPCart First Data (Payeezy) Gateway Hosted Payment result file (fdge4hostedresult.asp), when getting response from Payeezy, we do not use this response field transaction_tag.
Here are the list of response fields we use in our VPCart First Data (Payeezy) Gateway Hosted Payment :
Transaction_tag is usually hold the same value like x_trans_id and we do not need to get response value from Transaction_tag.
That means VPCart customers will not have to do anything on their end to ensure their transactions are still running after this date.
If you have any questions regarding this please submit a helpdesk ticket to us.