paypal
PayPal API Error Codes
Named error identifiers returned in the `details[].issue` or top-level `name` field of PayPal REST API (Orders, Payments, Invoicing) error responses.
15 codes
references developer.paypal.com/api/rest/responses/developer.paypal.com/api/rest/reference/orders/v2/errors/
· All codes 15 codes
- AUTHENTICATION_FAILURE Authentication Failure Authentication failed due to missing or invalid authentication credentials, such as an expired or malformed OAuth 2.0 access token. Returned as a 401 Unauthorized response.
- DUPLICATE_INVOICE_NUMBER Duplicate Invoice Number The `invoice_id` supplied for the order or payment has already been used in a previous transaction. Invoice IDs must be unique per merchant.
- INSTRUMENT_DECLINED Instrument Declined The funding instrument presented by the payer, such as a card or bank account, was declined by the issuer during order confirmation. The buyer should be prompted to select a different payment source.
- INTERNAL_SERVICE_ERROR Internal Service Error An internal server error occurred while processing the request. Returned as a 500 Internal Server Error response; the `debug_id` in the response body can be provided to PayPal support for investigation.
- INVALID_PARAMETER_VALUE Invalid Parameter Value The value of a request field is invalid, such as an amount that fails currency-specific decimal-place rules. The `details[].field` value identifies the offending parameter.
- INVALID_REQUEST Invalid Request The request is malformed or missing required data, such as a required header or an invalid content type. Returned as a 400 Bad Request response.
- MALFORMED_REQUEST_JSON Malformed Request JSON The request JSON is not well-formed, such as invalid syntax or a mismatched brace. Returned as a 400 Bad Request response.
- MISSING_REQUIRED_PARAMETER Missing Required Parameter A required request parameter is missing. The `details[].field` value in the response body identifies which parameter is absent.
- NOT_AUTHORIZED Not Authorized Authorization failed due to insufficient permissions on the calling application or merchant account. Returned as a 403 Forbidden response.
- ORDER_NOT_APPROVED Order Not Approved An attempt was made to capture or authorize an order that the payer has not yet approved. The payer must complete the approval flow before the order can be processed.
- PAYER_ACTION_REQUIRED Payer Action Required The order requires the payer to complete an additional action, such as approving the order or authenticating via 3D Secure, before it can be captured. Redirect the payer to the `payer-action` link in the response.
- PERMISSION_DENIED Permission Denied The access token does not have permission to execute this request. Returned as a 403 Forbidden response, typically because a required scope was not granted during authorization.
- RATE_LIMIT_REACHED Rate Limit Reached The app has exceeded its allotted request rate. Returned as a 429 Too Many Requests response; retry using an exponential backoff strategy.
- RESOURCE_NOT_FOUND Resource Not Found The specified resource, such as an order, payment, or invoice ID, does not exist. Returned as a 404 Not Found response.
- UNPROCESSABLE_ENTITY Unprocessable Entity The request was well-formed but could not be processed due to semantic errors, such as a business rule violation. The `details` array in the response body identifies the specific issue. Returned as a 422 Unprocessable Entity response.