Payout Error Codes & Handling
The following table lists payout-related error codes, HTTP statuses, and handling guidance.
| Code | Number (optional) | HTTP Status | Description |
|---|---|---|---|
Missing_mandatory_parameter | 3150 | 400 | Self explanatory - I.E Missing mandatory parameter CustomerIdentifier if the parameter CustomerIdentifier is missing in the payout request. |
Merchant_not_allowed_to_perform_this_action | 3161 | 400 | The merchant account has not been activated for the usage of payouts. Please contact your account manager or the integration team to inquire about the status of payout activation for your account. |
Duplicate_payout_request | 3164 | 400 | Transaction already exists. We only allow unique values for payout requests. |
Invalid_amount | 3165 | 400 | Invalid amount. |
Merchant_limit_reached | 3166 | 400 | Merchant payout limit reached. You can inquire the current limits of your account using the getPayoutState call. |
Payout_id_collides_with_existing_disposition_id | 3169 | 400 | We do not allow the payout ID to be the same as a previously used payment ID. Please use unique identifiers always. |
Payout_amount_is_below_minimum_payout_amount_of_the_merchant | 3171 | 400 | Self explanatory. |
Payout_blocked_due_to_security_reasons | 3199 | 400 | Self explanatory. |
Invalid_combination_of_parameters | 3299 | 400 | Invalid combination of country, currency, bank account type or ID document type. |
Error response structure
Depending on which internal service layer encounters an error, the structure of the error response may vary.
Errors originating from the core validation process return the standard error fields, for example:
{
"code": "invalid_request_parameter",
"message": "must be a valid date in the form of yyyy-mm-dd",
"number": 10028,
"param": "date_of_birth"
}