Skip to content

API Error Codes ​

What each prefix means ​

Use this table to know what each code prefix represents and what to do when you receive one.

PrefixCategoryWhat to do
NAUT-Authentication or authorization failureRefresh your credentials and retry. If the failure repeats, check your client ID/secret and tenant configuration.
SCHM-Request schema validation failureFix the offending field (location is in the field value) and retry.
RULE-Business rule violationDo not retry as-is. Review the rule named in the error description and adjust the request.
SRVR-Transient server errorRetry with exponential backoff. If it persists, contact support with the code and request ID.

Auth ​

CodeDescription
NAUT-00001Token validation failed: invalid or malformed token.
NAUT-00002Token validation failed: token cannot be used on production endpoints.
NAUT-00003Token validation failed: token cannot be used on sandbox endpoints.
NAUT-00004Authentication failed: Invalid client credentials provided.
NAUT-00005Authorization failed: Tenant security attributes are inactive.
NAUT-00006Authorization failed: Tenant account is currently paused.
NAUT-00007Authorization failed: Tenant is not subscribed to this product.
NAUT-00008Authorization failed: Insufficient permissions for this operation.
SRVR-00001An internal error occurred. Please retry later or contact support if needed.

Accounts ​

CodeDescription
RULE-10001No accounts found for the specified tenant and region.
RULE-10002Account identifier not found for the specified tenant and region.
RULE-10003accountIdentifier.type and accountIdentifier.value must be provided together; the same applies to branchIdentifier.type and branchIdentifier.value.
SCHM-10001The request did not match the API schema.
SCHM-10002A required field is missing from the request.
SCHM-10003The field value does not match the required format.
SCHM-10004The field value is shorter than the minimum length.
SCHM-10005The field value exceeds the maximum length.
SCHM-10006The numeric value is outside the allowed range.
SCHM-10007The field value is not in the set of allowed values.
SCHM-10008The field value is rejected by the schema.
SRVR-10001An internal error occurred. Please retry later or contact support if needed.

Transactions ​

CodeDescription
SCHM-20001The request did not match the API schema.
SCHM-20002A required field is missing from the request.
SCHM-20003The field value does not match the required format.
SCHM-20004The field value is shorter than the minimum length.
SCHM-20005The field value exceeds the maximum length.
SCHM-20006The numeric value is outside the allowed range.
SCHM-20007The field value is not in the set of allowed values.
SCHM-20008The field value is rejected by the schema.
SRVR-20001An internal error occurred. Please retry later or contact support if needed.

Counterparties ​

CodeDescription
RULE-30001Counterparty reference already exists for this tenant.
RULE-30002Counterparty not found for the specified reference.
RULE-30003Counterparty state must be ACTIVE to perform this operation.
RULE-30004When 'accountType' is 'BANK_ACCOUNT', fields 'country', 'currency', and 'branchIdentifier' are required.
RULE-30005The 'branchIdentifier.type' is not valid for the account 'currency' (EUR requires 'BIC', GBP requires 'SORT', USD requires 'ROUTING', INR requires 'IFSC').
RULE-30006When 'currency' is 'INR', 'branchIdentifier.type' must be 'IFSC'.
RULE-30007When 'currency' is 'USD', 'branchIdentifier.type' must be 'ROUTING'.
RULE-30008The 'accountIdentifier.type' is not valid for the account 'currency' (EUR requires 'IBAN'; GBP and USD require 'ID').
RULE-30009When 'currency' is 'INR' or 'USD', 'accountIdentifier.type' must be 'ID'.
RULE-30010Duplicate account in request body: 'accountIdentifier.type' and 'value' combination appears more than once.
RULE-30011'accountIdentifier.type' and 'accountIdentifier.value' must be supplied together.
RULE-30012'branchIdentifier.type' and 'branchIdentifier.value' must be supplied together.
SCHM-30001The request did not match the API schema.
SCHM-30002A required field is missing from the request.
SCHM-30003The field value does not match the required format.
SCHM-30004The field value is shorter than the minimum length.
SCHM-30005The field value exceeds the maximum length.
SCHM-30006The numeric value is outside the allowed range.
SCHM-30007The field value is not in the set of allowed values.
SCHM-30008The field value is rejected by the schema.
SRVR-30001An internal error occurred. Please retry later or contact support if needed.

Payouts ​

CodeDescription
RULE-40001A payout link or counterparty already exists for the supplied identifier / reference.
RULE-40002Account identifier not found for the specified tenant and region.
RULE-40004Payout link ID not found.
RULE-40005Counterparty not found by reference.
RULE-40006Counterparty state must be ACTIVE.
RULE-40007Target counterparty has no active accounts linked.
RULE-40009Payout link ID to cancel was not found.
RULE-40011Payout link ID not found.
RULE-40012UK payouts are available in sandbox only.
RULE-40013The supplied accountHolderName does not match the counterparty on record for this counterpartyReference.
RULE-40014verificationAttempts must not be provided when accountVerificationOption is NO_VERIFICATION.
SCHM-40001The request did not match the API schema.
SCHM-40002A required field is missing from the request.
SCHM-40003The field value does not match the required format.
SCHM-40004The field value is shorter than the minimum length.
SCHM-40005The field value exceeds the maximum length.
SCHM-40006The numeric value is outside the allowed range.
SCHM-40007The field value is not in the set of allowed values.
SCHM-40008The field value is rejected by the schema.
SRVR-40001An internal error occurred. Please retry later or contact support if needed.
SRVR-40002An internal error occurred. Please retry later or contact support if needed.
SRVR-40003An internal error occurred. Please retry later or contact support if needed.
SRVR-40005An internal error occurred. Please retry later or contact support if needed.

Mandates ​

CodeDescription
RULE-50001The tenant has not completed the SEPA mandate setup required before mandates can be created.
RULE-50002The supplied creditor identifier does not match a creditor configured for this tenant.
RULE-50003The supplied creditor name does not match the registered creditor for this tenant.
RULE-50004The requested status is inconsistent with the start date: APPROVED requires a future startDate, ACTIVE requires a startDate of today.
RULE-50005The mandate schedule is invalid: the start date is in the past, or the type/amount combination is not allowed for the requested scheduling.
RULE-50006The mandate is not in a state that permits this operation (already cancelled, already expired, or not active).
RULE-50007A mandate with this mandateReference already exists for the tenant.
RULE-50008The referenced counterparty or account could not be found for the tenant.
SCHM-50001The request did not match the API schema.
SCHM-50002A required field is missing from the request.
SCHM-50003The field value does not match the required format.
SCHM-50004The field value is shorter than the minimum length.
SCHM-50005The field value exceeds the maximum length.
SCHM-50006The numeric value is outside the allowed range.
SCHM-50007The field value is not in the set of allowed values.
SCHM-50008The field value is rejected by the schema.
SRVR-50001An internal error occurred. Please retry later or contact support if needed.

Direct Debit ​

CodeDescription
RULE-60001A direct-debit collection with this collectionReference already exists for the tenant.
RULE-60002The referenced mandate is not in a state that permits collections (not found, not active, cancelled, or expired).
RULE-60003The collectionDate is not valid for the mandate (before its start date, after its end date, or in the past).
RULE-60004The requested sequenceType is not allowed for this mandate's type or current state.
RULE-60005amountMin cannot be greater than amountMax.
RULE-60006initiatedFrom must be less than or equal to initiatedTo.
SCHM-60001The request did not match the API schema.
SCHM-60002A required field is missing from the request.
SCHM-60003The field value does not match the required format.
SCHM-60004The field value is shorter than the minimum length.
SCHM-60005The field value exceeds the maximum length.
SCHM-60006The numeric value is outside the allowed range.
SCHM-60007The field value is not in the set of allowed values.
SCHM-60008The field value is rejected by the schema.
SRVR-60001An internal error occurred. Please retry later or contact support if needed.

Bills ​

CodeDescription
RULE-70001A bill with this uniqueReferenceIdentifier already exists for the tenant.
RULE-70002A linked credit note with this uniqueReferenceIdentifier already exists for the tenant.
RULE-70003The bill is already VOID and cannot be modified. VOID is a terminal state.
RULE-70004The bill is PAID and cannot be modified.
RULE-70005The bill is PROCESSING and cannot be modified while a payment is in progress.
RULE-70006issueDate must not be later than dueDate.
RULE-70007Linked credit note issueDate must not be later than its dueDate.
RULE-70008fromDueDate must not be later than toDueDate.
RULE-70009openAmount cannot be greater than the bill's existing open amount.
RULE-70010openAmount must be 0 when status is set to CLOF or VOID.
RULE-70011status must be CLOF or VOID when openAmount is set to 0.
SCHM-70001The request did not match the API schema.
SCHM-70002A required field is missing from the request.
SCHM-70003The field value does not match the required format.
SCHM-70004The field value is shorter than the minimum length.
SCHM-70005The field value exceeds the maximum length.
SCHM-70006The numeric value is outside the allowed range.
SCHM-70007The field value is not in the set of allowed values.
SCHM-70008The field value is rejected by the schema.
SRVR-70001An internal error occurred. Please retry later or contact support if needed.