I use paypal in sandbox mode and often receive error "Duplicate Invoice id", although invoice ID is unique for each transaction, I see it in log files:
Message: The remote server returned an error: (400) Bad Request., Response: {"name":"DUPLICATE_TRANSACTION","message":"Duplicate Invoice id","information_link":"https://developer.paypal.com/webapps/developer/docs/api/#DUPLICATE_TRANSACTION","debug_id":"bce3a245b08ae"}, StatusCode: BadRequest, WebExceptionStatus: ProtocolError, InvoiceID: #163403
Message: The remote server returned an error: (400) Bad Request., Response: {"name":"DUPLICATE_TRANSACTION","message":"Duplicate Invoice id","information_link":"https://developer.paypal.com/webapps/developer/docs/api/#DUPLICATE_TRANSACTION","debug_id":"102d2b994e747"}, StatusCode: BadRequest, WebExceptionStatus: ProtocolError, InvoiceID: #573012
Message: The remote server returned an error: (400) Bad Request., Response: {"name":"DUPLICATE_TRANSACTION","message":"Duplicate Invoice id","information_link":"https://developer.paypal.com/webapps/developer/docs/api/#DUPLICATE_TRANSACTION","debug_id":"7ae230278b686"}, StatusCode: BadRequest, WebExceptionStatus: ProtocolError, InvoiceID: #330166
All these transactions are consecutive.
I have switched off this option here: https://www.paypal.com/us/cgi-bin/webscr?cmd=_profile-pref
(I have set option "No, allow multiple payments per invoice ID")
I even created the new test user, with new test credit card and the same error
Why is it necessary for sandbox mode and how to switch off it?
Related
I'm trying to use the Google API Client to gain access to a Google Doc. I get the following error:
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://docs.googleapis.com/v1/documents/1Dc82X_w8UsyZnJe5JEh4E0wNdfbw-_nhVWXwgEJ4HVg?alt=json returned "The caller does not have permission". Details: "The caller does not have permission">
The error comes up in the file extract_text.py, which I got from here: https://developers.google.com/docs/api/samples/extract-text
Specifically, the error shows up at this line when it's obtaining the document's ID:
doc = docs_service.documents().get(documentId=documentID).execute()
The error states that my request has invalid authentication credentials (https://cloud.google.com/asset-inventory/docs/faq). I have made sure that I setup the OAuth correctly.
It seems sandbox doesn't support v1.2/places endpoint,
GET https://sandbox-api.uber.com/v1.2/places/home -->
{
"code": "internal_server_error",
"message": "We have experienced a problem."
}
GET https://api.uber.com/v1.2/places/home -->
Works ok
Also, I notice the Sandbox response is slower when my request is coming from AWS Lambda(Especially, GET https://sandbox-api.uber.com/v1.2/requests/{request_id}).
Do I need to do any setting for it?
I have used to get authenticate to BMC Remedy to get incident via below url:
https:<host>:<port>/api/jwt/login
with username and password as a parameter and content-type as url-form encoded... But I got an error
[
{
"messageType": "ERROR",
"messageNumber": 8790,
"messageText": "Unknown system error",
"appendedText": "HTTP 400 Bad Request"
}
]
Currently i am working on developer sandbox instance.. After I created the sandbox .I got the details to my mail like
Product:Innovation Studio
Host: developerxxx.innovate.bmc.com
AR Java API Port: 46200
Innovation Studio URL: https://developerxxxx.innovate.bmc.com/com.bmc.arsys.rx.innovationstudio/index.html
Mid Tier URL: https://developerxxxx.innovate.bmc.com:8443/arsys
Field ID Range: 10445xx1:10446xx0
I need to get incident details using BMC Remedy REST API Authentication.
Starting at around 21:00 PM GMT today , when we query for a user which doesn't exist in dropbox team, we are receiving an http 500 status with internal error message. In comparison earlier we use to receive http 400 message with message that user doesn't exist in team.
Has something regressed at dropbox end, or is this change intentional and hence we should consider http 500 internal error as equivalent to user not found?
For example RESPONSE#1 is what we expected as valid behavior , while RESPONSE#2 is what we are receiving currently
RESPONSE#1
Resource: https://api.dropbox.com/1/idm/get_profile?email=dummy#authentication.test
Operation: GET
Headers: Authorization: Bearer XXX
Content Type:
Data:
%% Time: 08/28/2014 17:06:51 GMT
Message: The remote server returned an error: (400) Bad Request. Web Response: {"error": "User not on this team"} ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
RESPONSE#2
Resource: https://api.dropbox.com/1/idm/get_profile?email=dummy#authentication.test
Operation: GET
Headers: Authorization: Bearer XXX
Content Type:
Data:
Time: 08/28/2014 22:40:29
(500) Internal Server Error. Web Response: {"error": "Internal Server Error"} ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
Thanks
Somesh
I'm seeing the following error message when attempting to perform a simple payment using the PayPal Adaptive Payments API and the Explicit Approval Payment Flow in the sandbox environment:
Proxy Error
The proxy server could not handle the request GET /webapps/adaptivepayment/flow/expresscheckoutincontextremembermeflow.
Reason: Error during SSL Handshake with remote server
As per this related post, this issue has supposedly been resolved, but I'm still unable to perform a simple payment in the sandbox environment.
The API call to generate a payKey is returning successfully:
{
'responseEnvelope': {
'ack': 'Success',
'timestamp': '2013-04-01T10:00:33.572-07:00',
'build': '5563463',
'correlationId': '9ddb6d34b8b31'
},
'paymentExecStatus': 'CREATED',
'payKey': 'AP-30241506EH984280M'
}
and the following series of redirects are occurring:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/pay?expType=light&paykey=AP-30241506EH984280M
redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/payinit?iframecookie=1364835660832&paykey=AP-30241506EH984280M&expType=light
which redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/corepay
which redirects to:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/expresscheckoutincontextremembermeflow
which gives the 500 proxy error after approximately 210 seconds.
Additionally, if I attempt the workaround of logging into developer.paypal.com in another tab first, I get a 404 error on the initial request:
https:// www.sandbox.paypal.com/webapps/adaptivepayment/flow/pay?expType=light&paykey=AP-45P14958V28124917
I've searched and searched and poked and prodded this issue to death...anyone else seeing this problem, and does anyone have a working resolution?
We are rolling a patch later tonight which we expect to fix this issue permanently.