See some example scenarios for when each HTTP code may return:
Successful responses
Returned HTTP
Example
200 Ok
The request succeeded. E.g.: when creating an AccessToken, when performing a capture, void or GET.
201 Created
The request succeeded and the transaction was created (for all payment methods: boleto, credit, debit, electronic transfer and e-wallet).
Client error responses
Retorno HTTP
Example
400 Bad Request
The request is not valid. E.g: error in JSON request syntax.
401 Unauthorized
Authentication error. E.g.: wrong MerchantKey.
403 Forbidden
Non-authorized due to IP restriction in the e-commerce.
404 Not Found
The server can not find the requested resource. E.g.: wrong endpoint; for order search: the order does not exist, or was created by another merchant or the order is older than three months.
500 Internal Server Error, 502 Bad Gateway or 503 Service Unavailable
These error responses can return due to some internal fail, such as unavailable payment method or low speed. If you get any of these responses, we recommend contacting our Support for further information.
