Error response codes

Airwallex uses conventional HTTP response codes to indicate the success or failure of an API request.

HTTP response codes

HTTP Response Codes and description

Code	Description
200	OK - The request was processed successfully
201	Created - The request was processed successfully
400	Error - The request was invalid, or an error occurred in Airwallex or downstream provider
401	Unauthorized - Please verify that the authentication token is provided and is valid
404	Not found - The requested endpoint does not exist

Error response structure

When we send an error response, the body will generally contain the following fields:

Name	Type	Description	Example
code	String	Error code	validation_error
source	String	Name of the request parameter that caused the error (This attribute is only for code validation_error)	merchant_order_id
message	String	Error message	merchant_order_id must be provided
provider_original_response_code	String	Original response code from downstream provider (This attribute is only for code provider_declined or issuer_declined)	01

Error response examples for HTTP response code 400

validation_error

{   
    "code":"validation_error",
    "source":"merchant_order_id",
    "message":"merchant_order_id must be provided."
}

resource_not_found

{   
    "code":"resource_not_found",
    "message":"The resource with ID int_n3fXc5NDzgVE9DLx3zGhMibdSlx cannot be found"
}

internal_error

{   
    "code":"internal_error",
    "message":"An internal error was encountered. Please try again later."
}

issuer_declined

{   
    "code":"issuer_declined",
    "message":"The card issuer declined this transaction. Please refer to the original response code.",
    "provider_original_response_code": "01"
}

Error codes for 401, 404

Error Codes for HTTP Response code 401 and 404

Http response code	Code	Message
401	unauthorized	Access denied
404	not_found	The requested endpoint does not exist

Error codes for 400

Error Codes for HTTP Response code 400