| Error Code | Error Message |
| PAYT-ERR-1050 | Mandatory info missing: [FieldName] cannot be null or empty. |
| PAYT-ERR-1051 | Invalid Data: [FieldName] provided is invalid. |
| PAYT-ERR-1052 | Invalid Data: [FieldName] provided should contain any of the values [Acceptable values]. |
| PAYT-ERR-1053 | Invalid Data: [FieldName] provided is invalid. Expected format [DateFormat]. |
| PAYT-ERR-1054 | Invalid Data: [FieldName] length is invalid. Expected minimum [MinLength] and maximum [MaxLength]. |
| PAYT-ERR-1057 | Unrecognized Field: [FieldName] is not a valid field. |
| PAYT-ERR-1058 | Invalid Request: request provided is not well-formatted. |
| PAYT-ERR-2001 | Either description or short_description should be provided. |
| PAYT-ERR-2002 | Response_Requested_By date must be a future date and less than 5 days. |
| PAYT-ERR-2004 | PayID details are not supported for migrated agreements. |
| PAYT-ERR-2005 | validity_start_date should be either current date OR future date. |
| PAYT-ERR-2006 | validity_end_date should be greater than OR same as validity_start_date. |
| PAYT-ERR-2008 | validity_end_date should not be provided if agreement should be auto-renewed. |
| PAYT-ERR-2009 | account_details in the request are invalid as per the account_type provided. |
| PAYT-ERR-2010 | Either account (bsb/account number) or PayID details should be provided. |
| PAYT-ERR-2011 | Invalid PayID format for the PayID type provided. |
| PAYT-ERR-2013 | debtor_id_type is mandatory along with debtor_id. |
| PAYT-ERR-2014 | Invalid debtor_id_type for the debtor_type provided. |
| PAYT-ERR-2015 | Date provided in first_payment_info should be between validity_start_date and validity_end_date OR can be same as validity_start_date and validity_end_date. |
| PAYT-ERR-2016 | Date provided in last_payment_info should be between validity_start_date and validity_end_date OR can be same as validity_start_date and validity_end_date. |
| PAYT-ERR-2018 | payment_amount should be less than or equal to maximum amount. |
| PAYT-ERR-2019 | Amount provided in last_payment_info should be less than or equal to maximum amount. |
| PAYT-ERR-2020 | Amount provided in first_payment_info should be less than or equal to maximum amount. |
| PAYT-ERR-2021 | Date provided in last_payment_info should be same OR after the date provided in first_payment_info. |
| PAYT-ERR-2025 | Incorrect value provided for either of these fields - frequency, point_in_time, count_per_period. The combination provided should be valid. |
| PAYT-ERR-2027 | Active direct debit agreement which needs to be migrated does not exist for the user. |
| PAYT-ERR-2028 | Response_Requested_By is applicable only for AUPM agreements with 'ATTENDED' priority type. |
| PAYT-ERR-2029 | For FIXE/BALN type of agreements, specifying payment amount is mandatory. |
| PAYT-ERR-2031 | Invalid Data: Please provide info for all parameters under agreement_info.payment_terms.maximum_amount_info |
| PAYT-ERR-2032 | Invalid Data: Payment frequency [frequency] is not enabled for your platform. If you require this payment frequency to be enabled for your business use-case, kindly get in touch with Zai support. |
| PAYT-ERR-2033 | Invalid Data: Payment parameter '[payment_parameter]' provided is not enabled for your platform. If you require this parameter to be enabled for your business use-case, kindly get in touch with Zai support. |
| PAYT-ERR-2034 | Invalid Data: Agreement type [type] is not enabled for your platform. If you require this agreement type to be enabled for your business use-case, kindly get in touch with Zai support. |
| PAYT-ERR-2035 | Invalid Data: Payment amount type [amount_type] is not enabled for your platform. If you require this payment amount type to be enabled for your business use-case, kindly get in touch with Zai support. |
