Status Code Values

To effectively manage errors in i-payout API responses, follow these steps:

  1. Evaluate HTTP Status Code:
    1. Success: A status code of 200 indicates success. Proceed with response handling.
    2. Error: Any status code not on the 200 range signals an error. Refer to the HTTP Status Codes documentation for specifics.
  2. Inspect the isSuccess Data Field:
    1. If true, the API call succeeded. Examine the data object for relevant information specific to the API call.
    2. If false, the API call failed. To understand the reason for the failure, proceed to the following step.
  3. Analyze Failure Details:
    1. Status Code: Check the statusCode field in the response to identify the nature of the error. Consult the Status Code Values table below for detailed explanations.
    2. Message: The message field provides a human-readable explanation that might hint at the error's cause.
    3. Log Identifier: The logIdentifier field contains an identifier useful for debugging. Record this identifier for any necessary communication with i-payout support.

📘

Note:

Make sure to keep track of important details, especially the logIdentifier, to help quickly solve any problems if you contact our technical support.

Below is the list of the available status codes in the i-payout system:

STATUS CODESHORT DESCRIPTIONLONG DESCRIPTION
0OKSuccessful API call.
-1Internal ErrorAn internal error has occurred. Please try again.
-2User not foundThe user is not found. Please check the username value sent.
-3General ErrorA general error has occurred. Please try again. If the issue continues, please contact i-payout.
-5Account not foundAccount not found. Please try different account credentials.
-7Invalid client credentialsInvalid client credentials. Please validate account credentials.
-12A user with this username already existsThe username you are trying to create already exists. Please try another unique username.
-15Insufficient fundsInsufficient funds for this transaction. Please try a lesser amount or load sufficient funds to support this transaction and try again.
-26Invalid card numberThe card number is not valid. Please try a valid card number.
-37Cannot find Pal by such an emailAn account associated with this email address cannot be found. Please verify.
-53Invalid MerchantThe merchant account is not configured appropriately.
-56No records foundThere are no records found associated.
-57PendingThe transaction is pending and cannot be acted upon until completion.
-58ProcessingThe transaction is being processed and, therefore, cannot be acted upon until completed.
-60Invalid Country CodeThe country code specified is not supported. Please see the Country / Currency Support page.
-61Access permission is required to use this functionThis function requires access permission, which is not associated with the credentials utilized.
-62Invalid server configurationThe server is not properly configured for this function.
-63Invalid request response parameterA request/response parameter is not valid.
-64Invalid API input parameter, Model Validation FailedAn input parameter cannot be properly parsed.
-65Parameter requiredA required parameter was not sent.
-66Invalid currencyThe currency specified is not supported. Please see the Country / Currency Support page.
-67Invalid amountThe amount specified is not valid.
-68Invalid URLThe URL specified is not formatted properly or is not supported.
-71Missing header parameterAn HTTP Header parameter was not specified and is required.
-72Invalid parameterInvalid parameter.
-73Merchant not foundThe merchant account specified was not found.
-75IP address generation IssueUnable to generate an IP address to support this function.
-75Fee value not found for customerA fee value, which is required, has not been configured for this customer.
-76Unauthorized api callThis API call is not authorized.
-77Invalid field value lengthA parameter sent has a field length that exceeds the maximum length.
-78Country not allowedThe country specified is not supported. Please see the Country / Currency Support page.
-79IP not allowedThe IP address that sent this request is not allowed.
-79IP blacklistedThe IP address that sent this request is not allowed.
-80Rate limit exceededToo many API calls have been made in a short time, and this request has been automatically declined.
-82FX conversion rate issueUnable to complete foreign exchange conversion.
-83Error in deleting a recordUnable to delete this record.
-84ReferenceId already existsThis referenceId already exists. Please try a unique referenceId.
-84Batch already closedThis batch has already been closed and can no longer be utilized.
-85Cannot create a new batch for e-wallet loadUnable to create a new batch for eWallet Load. Please try again.
-86User cannot be createdThis user cannot be created.
-87Old and new user mismatchThe usernames must match. Please correct and try again.
-88File not existsThe file does not exist.
-89Error parsing private key fileUnable to parse private key file.
-90Invalid e-wallet registrationThe eWallet cannot be registered.
-92Invoice capabilities disabledFunction attempted without appropriate configuration.
-93Invalid recurring payment statusRecurring payment was attempted but not allowed on this resource.
-94Invalid recurring payment statusRecurring payment was attempted but not allowed on this resource.
-95User not accepted feesThe user has not accepted the fees, so this transaction must be declined.
-96Credit card processor payment issueThere is an issue processing this credit card transaction.