However, today (21st Jan) in the morning, we received a DirectDebit response with the requiredDirectDebit/Name field missing.
Impact
High. This issue affects an unknown cohort of users, and prevents them from sharing their direct debit data, as the payload is invalid according to Account and Transaction API Specification v1.1.0.
Barclays has identified the issue and a fix is currently in test. Barclay will confirm when released into live environment – outcome for the specific customer will not change.
According to the Account and Transaction API Specification v1.1.0 "Direct Debits" section, a DirectDebit has the following required fields:
AccountId
MandateIdentification
Name
However, today (21st Jan) in the morning, we received a
DirectDebit
response with the requiredDirectDebit/Name
field missing.Impact
High. This issue affects an unknown cohort of users, and prevents them from sharing their direct debit data, as the payload is invalid according to Account and Transaction API Specification v1.1.0.
Remediation
Include
DirectDebit/Name
in the response.Submitted as OBSD-6250.