-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
202 HTTP reponse code and status not handled #26
Comments
Is this something you are looking at and/or working on? |
Hi, We have communicated this to the relevant team to get more information regarding response code 202. Kindly be patient with us and we will relay any information as soon as we get it. |
I am assuming, based on the lack of an update, that this issue is still not corrected? |
@jwgcooke this still exist. these response code are document in Simple Order API reference guide. Can this be fixed ? Can we not send decision manager response code as status ? the sdk documentation only has these values
|
Bump. |
Not sure why you are tagging me? Perhaps you should tag the Cybersource folks who maintain this repo. Honestly there are so many issue with the REST API we stopped working on implementing it and went to the SOAP API which is antique but at least functions |
@gnongsie Could you please check? |
Hi, |
18 months later.... |
2 years later. truing to find info of wrong error code response... |
on a payment call we are seeing a 202 HTTP response coming back with a status of "202" and an errorInformation block that indicates a reject state. There is nowhere in the rest sdk of any of the docs that suggest that a 202 is a valid response code OR a valid status code
Example Response:
{ "id": "#################", "submitTimeUtc": "2019-07-10T14:46:06Z", "status": "202", "errorInformation": { "reason": "REJECT", "message": "The order has been rejected by Decision Manager" } }
FYI this is reproducible in the REST API "try it live" page
The text was updated successfully, but these errors were encountered: