How To
Error Codes - Granular
| Code | HTTP Status | Description | Error Type |
|---|---|---|---|
| UK.Nationwide.DailyPaymentLimitExcess | 400 | Payment request has breached the allowed daily faster payment limit. | InvalidMessage |
| UK.OBIE.Field.Expected | 400 | For the scenario, when a field-value is not provided in the payload, that is expected in combination with preceding field-value pairs. The corresponding path must be populated with the path of the unexpected field. E.g. If RecurringPaymentDateTime is not present in the request, where the Frequency is incompatible with the FirstPaymentDateTime i.e. if the Frequency is not a sufficient period of time to be able to honour the FirstpaymentDateTime. |
InvalidMessage |
| UK.OBIE.Field.Invalid | 400 | An invalid value is supplied in one of the fields, or the length of value supplied is larger than the corresponding maximum field length in ASPSP's domain. Reference of the invalid field should be provided in the path field, and the URL field may have the link to a website explaining the valid behaviour. The error message should describe the problem in detail. | InvalidMessage |
| UK.OBIE.Field.InvalidDate | 400 | An invalid date is supplied e.g. when a future date is expected, a date in past or current date is supplied. The message can specify the actual problem with the date. The reference of the invalid field should be provided in the path field, and URL field may have the link to a website explaining the valid behaviour | InvalidMessage |
| UK.OBIE.Field.Missing | 400 | A mandatory field, required for the API, is missing from the payload. This error code can be used, if it is not already captured under the validation for UK.OBIE.Resource.InvalidFormat. Reference of the missing field should be provided in the path field, and URL field may have the link to a website explaining the valid behaviour |
InvalidMessage |
| UK.OBIE.Field.Unexpected | 400 | For the scenario, when a field-value is provided in the payload, that is not expected in combination with preceding field-value pairs. E.g., If Reference field is populated then SecondaryIdentification field is unexpected, and vice versa. |
InvalidMessage |
| UK.OBIE.Header.Invalid | 400 | An invalid value is supplied in the HTTP header. The HTTP Header should be specified in the path element. | InvalidMessage |
| UK.OBIE.Header.Missing | 400 | A required HTTP header has not been provided. The HTTP Header should be specified in the path element. | InvalidMessage |
| UK.OBIE.Resource.ConsentMismatch | 400 | {payment-order-consent} and {payment-order} resource mismatch. For example, if an element in the resource’s Initiation or Risk section does not match the consent section. The path element should be populated with the field of the resource that does not match the consent. | InvalidMessage |
| UK.OBIE.Resource.InvalidConsentStatus | 400 | The resource’s associated consent is not in a status that would allow the resource to be created, or a request to be executed. E.g., if a consent resource had a status of AwaitingAuthorisation or Rejected, a resource could not be created against this consent. The path element should be populated with the field in the consent resource that is invalid. |
AuthoriseConsent |
| UK.OBIE.Resource.InvalidFormat | 400 | When the Payload schema does not match to the endpoint, e.g., /domestic-payments endpoint is called with a JSON Payload, which cannot be parsed into a class such as OBWriteDomestic1 | InvalidMessage |
| UK.OBIE.Resource.NotFound | 400 | Returned when a resource with the specified Id does not exist (and hence could not be operated upon). | InvalidMessage AccountPermanentlyUnavailable AccountTemporarilyUnavailable |
| UK.OBIE.Rules.FailsControlParameters | 400 |
Payment request has breached the allowed limit set by controlParameters : MaximumIndividualAmount OR Payment request has breached the allowed limit set by controlParameters: {FieldNames} |
InvalidMessage |
|
UK.Nationwide.DailyPaymentLimitExcess |
400 | Payment request has breached the allowed daily faster payment limit. | InvalidMessage |
| UK.OBIE.Field.Expected | 400 | For the scenario, when a field-value is not provided in the payload, that is expected in combination with preceding field-value pairs. The corresponding path must be populated with the path of the unexpected field. E.g. If RecurringPaymentDateTime is not present in the request, where the Frequency is incompatible with the FirstPaymentDateTime i.e. if the Frequency is not a sufficient period of time to be able to honour the FirstpaymentDateTime. |
InvalidMessage |
| UK.OBIE.Field.Invalid | 400 | An invalid value is supplied in one of the fields, or the length of value supplied is larger than the corresponding maximum field length in ASPSP's domain. Reference of the invalid field should be provided in the path field, and the URL field may have the link to a website explaining the valid behaviour. The error message should describe the problem in detail. | InvalidMessage |
| UK.OBIE.Field.InvalidDate | 400 | An invalid date is supplied e.g. when a future date is expected, a date in past or current date is supplied. The message can specify the actual problem with the date. The reference of the invalid field should be provided in the path field, and URL field may have the link to a website explaining the valid behaviour | InvalidMessage |
| UK.OBIE.Field.Missing | 400 | A mandatory field, required for the API, is missing from the payload. This error code can be used, if it is not already captured under the validation for UK.OBIE.Resource.InvalidFormat. Reference of the missing field should be provided in the path field, and URL field may have the link to a website explaining the valid behaviour |
InvalidMessage |
| UK.OBIE.Field.Unexpected | 400 | For the scenario, when a field-value is provided in the payload, that is not expected in combination with preceding field-value pairs. E.g., If Reference field is populated then SecondaryIdentification field is unexpected, and vice versa. |
InvalidMessage |
| UK.OBIE.Header.Invalid | 400 | An invalid value is supplied in the HTTP header. The HTTP Header should be specified in the path element. | InvalidMessage |
| UK.OBIE.Header.Missing | 400 | A required HTTP header has not been provided. The HTTP Header should be specified in the path element. | InvalidMessage |
| UK.OBIE.Resource.ConsentMismatch | 400 | {payment-order-consent} and {payment-order} resource mismatch. For example, if an element in the resource’s Initiation or Risk section does not match the consent section. The path element should be populated with the field of the resource that does not match the consent. | InvalidMessage |
| UK.OBIE.Resource.InvalidConsentStatus | 400 | The resource’s associated consent is not in a status that would allow the resource to be created, or a request to be executed. E.g., if a consent resource had a status of AwaitingAuthorisation or Rejected, a resource could not be created against this consent. The path element should be populated with the field in the consent resource that is invalid. |
AuthoriseConsent |
| UK.OBIE.Resource.InvalidFormat | 400 | When the Payload schema does not match to the endpoint, e.g., /domestic-payments endpoint is called with a JSON Payload, which cannot be parsed into a class such as OBWriteDomestic1 | InvalidMessage |
| UK.OBIE.Resource.NotFound | 400 | Returned when a resource with the specified Id does not exist (and hence could not be operated upon). | InvalidMessage AccountPermanentlyUnavailable AccountTemporarilyUnavailable |
| UK.OBIE.Rules.FailsControlParameters | 400 |
Payment request has breached the allowed limit set by controlParameters : MaximumIndividualAmount OR Payment request has breached the allowed limit set by controlParameters: {FieldNames} |
InvalidMessage |