AI resources
Possible errors
Check the list of possible errors returned by the Orders API and how to fix them.
| Error type | Status | Code | Description and possible solutions |
| Request error | 400 | json_syntax_error | Make sure the request has a valid JSON structure, with appropriate keys and values. |
| Request error | 400 | required_properties | Some required properties are missing. Check the request and make sure to include all required properties according to the API documentation. |
| Request error | 400 | unsupported_properties | Some properties provided are not supported by the API. Review the request and remove or correct the unsupported properties. |
| Request error | 400 | minimum_properties | The minimum number of required properties has not been met. Add the necessary properties to complete the request. |
| Request error | 400 | property_type | The type of the provided property is invalid. Make sure the value sent in the request matches the expected type. |
| Request error | 400 | property_value | The value of the provided property is invalid. Check the sent value and make adjustments to match the allowed values. |
| Request error | 400 | maximum_items | The maximum number of allowed items has been exceeded. Reduce the number of items sent so it does not exceed the maximum allowed. |
| Request error | 400 | minimum_items | The minimum number of required items has not been met. Add more items to the request to meet the API requirements. |
| Request error | 400 | invalid_path_param | Check if the ID provided as a parameter is valid. |
| Request error | 400 | invalid_properties | Some properties provided are invalid or malformed. Review the sent properties and check if they comply with the API specifications. |
| Request error | 400 | empty_required_header | One or more required headers are empty. Check the request and make sure all required headers are present and properly filled in. |
| Request error | 400 | invalid_idempotency_key_length | The value sent in the header X-Idempotency-Key exceeded the maximum allowed size. The header accepts values between 1 and 64 characters. |
| Request error | 400 | order_builder_without_transactions | There is no transaction associated with the order. Make sure to include at least one transaction for the order creation. |
| Request error | 400 | invalid_order_mode_for_operation | The mode provided is not valid for this operation. Check if you are using the correct mode according to the desired operation. |
| Request error | 400 | invalid_order_type | The order type is invalid. Check if the type used is valid for the operation. |
| Request error | 400 | invalid_transaction_id | The transaction ID is invalid. Make sure the ID is correct. |
| Request error | 400 | exceeded_number_of_transactions | An error occurred in the request. The Order accepts a maximum of one transaction. Remove the excess transactions. |
| Request error | 400 | invalid_email_for_sandbox | The email format is not valid for the sandbox environment, it must contain "@testuser.com". |
| Request error | 400 | order_invalid_sponsor_id | The order sponsor identifier is invalid. Make sure the ID is correct. |
| Request error | 400 | invalid_header_value | Caller identifier (caller_id) not found. Make sure the ID is correct. |
| Request error | 401 | 401 | The value sent as Access Token is incorrect. Please verify it and try again by sending the correct value. |
| Request error | 401 | invalid_credentials | There is no support for test credentials. Use test users with production credentials for the test environment (sandbox) and your production credentials for the production environment. |
| Processing error | 402 | failed | There was an error processing one of the transactions. Check the returned message for more information. |
| Request error | 404 | order_not_found | The order was not found. Check if the provided ID is correct. |
| Request error | 404 | transaction_not_found | The transaction was not found. Check if the provided ID is correct. |
| Request error | 409 | cannot_refund_order | Make sure the order is in a state that allows a refund. |
| Request error | 409 | cannot_capture_order | Check if the order state allows capture and that it was created with the processing_mode field set to automatic. |
| Request error | 409 | cannot_cancel_order | Make sure the order is in a state that allows cancellation. |
| Idempotency error | 409 | idempotency_key_already_used | The X-Idempotency-Key provided has already been used. Each idempotency key must be unique to ensure the operation is performed only once. Use a new key for the next request. |
| Request error | 409 | operation_not_supported | The requested operation is not supported. Check if the operation you are trying to perform is valid for the current context. |
| Request error | 409 | order_already_refunded | The order has already been refunded. It is not possible to process a refund on an order that already has this status. |
| Request error | 409 | order_already_canceled | The order has already been canceled. It is not possible to perform operations on an order that is already canceled. |
| Request error | 409 | order_refund_already_in_process | There is already a full refund request in process for the order in question. |
| Idempotency error | 423 | resource_locked | The idempotency key is temporarily locked. Wait a few moments and try to execute the request again. |
| Idempotency error | 500 | idempotency_validation_failed | An internal server error occurred. Try resending the request with a new and unique idempotency key to avoid conflicts. If the problem persists, contact Support and provide the x-request-id along with more details about the operation performed. |
| API error | 500 | internal_error | An internal server error occurred. Please try again later. If the problem persists, contact Support and provide the x-request-id along with more details about the operation performed. |
| Request error | 400 | invalid_sequence_control | It is not possible to create the payment by sending information from the automatic_payments.subscription.sequence node using a payment profile with sequence_control set to AUTO. The value of this field must be set to MANUAL to send recurrence-related information. Access Manage scheduled recurring payments for more information. |
| Request error | 400 | invalid_payment_methods | The payment profile being used to create the order has no associated payment methods, or has two cards and the order is being processed with synchronous mode, which is not allowed. Review your configuration to try again. |
| Request error | 400 | invalid_capture_mode | The order has retry logic configured but the processing mode is set to automatic. The retries field will only be allowed if processing_mode=automatic_async has been set. |
| Request error | 400 | invalid_payment_method_list | The payment profile being used to create the order has more than two associated payment methods, which is the maximum allowed. Review your configuration to try again. |
| Request error | 400 | invalid_application_id | The application identifier being used to execute the request is incorrect or not authorized. Verify that you are sending the correct information. |
| Request error | 400 | profile_not_found | The payment profile being used to create the payment does not exist or is invalid. Verify that you have sent the correct value and try again. |
| Request error | 400 | invalid_profile_status | You are trying to create the order using a payment profile with a status that does not allow it. It is only possible to create payments with payment profiles with status=READY. Check the profile status using the Profiles API. |
| Request error | 400 | invalid_customer_id | The customer identifier sent in the request does not match the one in the payment profile. Verify that you have sent the correct values in both cases. |
| Request error | 400 | invalid_collector_with_application_fee | An application_fee greater than 1 must be sent for the request to be correct. |
| Request error | 404 | profile_not_found | The payment profile being used to create the payment was not found. Verify that you have sent the correct value and try again. |
| Request error | 400 | profile_id_must_be_informed | The profile identifier was not sent, which is required in cases where sequence_control.reason=recurring. |
| Request error | 400 | invalid_intent_status | It is not possible to refund the order in its current state. Make sure the order is in a state that allows a refund. |
| Request error | 400 | invalid_refund_amount | It is not possible to refund the amount defined in the request. Make sure you have sent the correct value. |
| Request error | 400 | refund_error | There was an error trying to process the refund. Wait a moment and try again. |
| Request error | 400 | invalid_refund | You are trying to refund a payment that does not allow it. Make sure you meet the conditions to create a refund and try again. |
| API error | 424 | error_dependency | An internal error occurred. Wait a moment and try again. |