As of January 22nd, 2018, we will add validation on the
timestamp attribute in the secure parameters for Chargify Direct card updates.
Previously, we did not validate the timestamp, and if it was invalid, we would allow the card update to proceed, but then be unable to store the record of the API call. This would lead to an error when you tried to retrieve the call to see the results.
Going forward, we will instead return an error message if the timestamp is invalid.
The most common reasons for an invalid timestamp are sending a value in milliseconds instead of seconds, or sending a decimal value. (For example:
1511896498.426 instead of
For more information, please see the section on Secure Parameters in the Chargify Direct documentation.