Closed kristofytp closed 3 years ago
In an old version of the library, the failure reason used to be an enum, which could cause deserialization issues. However, since July 7 2020, it was changed to a string to avoid this exact situation. Could it be that you were using a very old version of the library?
Non the less, I accept your pull request since it's nice to have a full and complete list of possible failure reasons as constant strings in the library.
Ah yes we are still using an older version, good to know the deserialization errors don't happen anymore in newer versions, will update asap :-)
Cool! No problem! Thanks for the PR :)
Not all possible creditcard payment failure reasons are available which is causing deserialization errors in our software: