The resource information below provides PayFac® Developers with transaction status codes detailing the success or failure error messages when developing payment implementations. The response codes listed include successful responses, along with invalid payment requests, failed authentication, internal error messages and soft declines.
Go here for additional PayFac API examples and details about the REST endpoints and the required structure of HTTP headers.
Resource Information
Code | Description |
---|---|
200 | Update/Retrieval/Disable is successful |
201 | Create call is successful |
400 | Invalid Request. For example:
The response message will contain more details |
401 | Failed Authentication |
500 | Internal error. Litle & Co. is investigating the issue. Please contact Litle Customer Support for additional information. |
503 | Returns for a soft decline or if the background checking service is unavailable. For a soft decline, please verify the submitted information and retry. If the service was unavailable, the Retry-After header contains a suggested retry time. |
Example: Error Response - Status Code 400
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<errorResponse>
<transactionId>82820205828260878</transactionId>
<errors>
<error>Error in Request:Legal Entity [Entity Name] has not been approved</error>
</errors>
</errorResponse>
or
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<errorResponse>
<errors>
<error>Error of [may not be null] on [subMerchantCreateRequest.merchantCategoryCode]</error>
<error>Error of [size must be between 1 and 50] on [subMerchantCreateRequest.merchantName]</error>
</errors>
</errorResponse>
Example: Error Response - Status Code 401
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<errorResponse>
<errors>
<error>You are not authorized to access this resource. Please check your credentials.</error>
</errors>
</errorResponse>
Example: Error Response - Status Code 500
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<errorResponse>
<errors>
<error>Internal Error. This error has already been escalated to Litle for resolution.
Please contact support with questions.</error>
</errors>
</errorResponse>