01-25-2013 02:00 PM
I'm using the native/cascades PaymentManager in test connection mode, and all the different errors have the same code (4). Is this because it is in test mode or will the result be the same on a live connection?
Also is there a list of the error codes for the payment service? I've looked but couldn't find any in the documentation. At the moment the only way I can differentiate between the errors is via the errorText but is this text fixed or likely to change in the future?
Thanks for any help.
01-25-2013 02:15 PM
The error code being returned is a bug which I reported a while back but has yet to be resolved. More error codes have also been requested to help handle a wider variety of error responses.
A list of error codes can be found here:
These codes should get added to the Cascades docs shortly as well.
01-28-2013 07:48 AM
07-23-2013 03:29 PM
I'm still experiencing this problem in OS 10.1. All the errors in testing, return code 4. Also I still can't find the list of error codes in the Cascades documentation.
Specifically, how can I test for the "Already Purchased" response?
07-24-2013 08:43 AM
07-24-2013 11:25 AM
In testing locally (PaymentConnectionMode::Test) every error returns code 4. It was reported that this was a bug in 10.0 that was due to be fixed but I'm still experiencing the same issue running on 10.1.
Since that isn't working, I'm looking for the list of possible error codes that can be returned from this:
I'd like to be able to detect an "Already Purchased" error in production mode.
07-24-2013 11:35 AM
In 10.2 new error codes have been created: