Payeezy transaction_tag value upgrade
Pinned
If you are currently using Payeezy, 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.
Spreedly is already prepared for all changes to the Payeezy Gateway. Spreedly customers will not have to do anything on their end to ensure their transactions are still running after this date.
Let us know if you have any questions!
Please sign in to leave a comment.
Comments
0 comments