![]() ![]() Invalid refresh token passed when trying to get an AT from RT. Cannot decrypt refresh token: Base64 Decode Failed. Risk decline reasons are not transparent, so check with risk. Risk can decline due to Bad IP, OFAC check, and suspicious fraudulent activity. The redirect_uri should match the one configured during the application registration. The Base64-encoded client credentials in the Authorization header are invalid. The authorization code is invalid.Ĭheck your authorization_code and resend. Use the grant_type=client_credentials with response_type=token. Resend with this parameter and its value. The redirect_uri is a required parameter. The client_id should have the GRANT_PROXY_CLIENT scope to use the target_client_id parameter. Current version only supports token for response_type. The refresh_token is a required parameter.Īdd the refresh_token parameter and value. Tip: These are usually access token-related issues and can be cleared by making sure that the token is present and hasn't expired. ![]() The server cannot handle the request for a service due to temporary maintenance.Īuthorization errorsPaypal follows industry standard OAuth 2.0 authorization protocol and returns the HTTP 400, 401, and 403 status code for authorization errors. Although the client appears to provide a correct request, something unexpected occurred on the server. An internal server error has occurred.Ī system or application error occurred. To be informed of the transaction, it is recommended that you repeat the same /execute or /capture call at least once, with the same PayPal-Request-Id HTTP header as before. Note: An HTTP 5xx or network timeout from an /execute or /capture endpoint could have resulted in the creation of a PayPal transaction. The rate limit for the user, application, or token exceeds a predefined value. For example, this error occurs for any business validation errors, including errors that are not usually of the 400 type. No systemic problems limit the API from completing the request. The API cannot complete the requested action and might require interaction with APIs or processes outside of the current request. The API cannot complete the requested action, or the request action is semantically incorrect or fails business validation. For example, this error occurs if the client sends a Content-Type: application/xml request header but the API can only accept application/json request payloads. The API cannot process the media type of the request payload. The server does not support the request payload’s media type. The API cannot complete the requested action as it conflicts with another request that is currently being processed. Request cannot be processed as it conflicts with another request. For example, this error occurs if the client sends an Accept: application/xml request header but the API can generate only an application/json response. The server cannot use the client-request media type to return the response payload. The server does not implement the media type that would be acceptable to the client. The service does not support the requested HTTP method. The server does not implement the requested HTTP method. For example, no data exists in the database at that key. Either the URI is incorrect or the resource is not available. The server did not find anything that matches the request URI. A simple data validation error occurred.The data is not in the expected data format.The API cannot convert the payload data to the underlying data type.The server could not understand the request. Request is not well-formed, syntactically incorrect, or violates schema. Failed requestsFor failed requests, PayPal returns HTTP 4XX status codes if something passed in the request has an error or 5XX status codes when something is wrong on our end with a server or service.For authentication specific HTTP 4XX status codes, see Authorization errors.
0 Comments
Leave a Reply. |