Closed weppos closed 8 years ago
@weppos we did in fact recently change the errors response from:
<errors>Your card was declined.</errors>
To something more idiomatic:
<errors>
<error>Your card was declined.</error>
</errors>
Obviously we neglected to ensure this change wouldn't break the gem. We'll work on fixing this ASAP. Sorry for the confusion!
Cool! Let me know if you want me to provide a patch.
@weppos sure, PRs are always welcome. :smile:
We recently started to experience this error
It looks like the cause of this issue is an override of the
load_remote_errors
method created in 2013.Removing this override and falling back to the original implementation seems to work as expected.
This is an example response (without the unnecessary headers)
Any chance that the response was recently changed at Chargify?