Archived 2022.11.20. Content moved to error scenarios and responses.
Question
In a call to Get Transaction Detail, a payload has extendedData that has New Payments Platform (NPP) related banking transaction data fields, such as extensionUType, extendedDescription, and endToEndId.
What is the response for a Data Holder (DH) who does not support NPP?
Answer
If the DH does not have the requested extended data, then the correct response is 404(Not Found). The isDetailAvailable field should be set to false for Get Transaction Detail calls if the DH does not support the NPP data.
Until other NPP services are included in the transaction payload or the payload is amended, a transaction can only validly have extendedData if it was executed using the X2P01.01 overlay service. Other transactions should return false in the isDetailAvailable field and should return a 404 not found error response if extended data is requested.
Comments
4 comments
James Bligh This is good information. Do you think Standards should reflect this information? I spent hours looking for an answer for the team. Should have checked here first :)
Hi Randima Niroshini,
Thanks for the feedback, glad the article was able to help! In regards to your question; the Consumer Data Standards defines the technical requirements and refrains from being opinionated in how organisations implement the requirements.
We are looking for improvements in the future in how you read and interact with the Standards and the CDR Support Portal.
Regards.
Thanks Jarryd. I was more thinking returning 404 error for Get Transaction Detail for non NPP transactions is more a technical requirement and should be a consistent implementation for Data holders.
404 is not mentioned in the standards anywhere.
Randima Niroshini - if you aren't already aware of Decision Proposal 155: https://github.com/ConsumerDataStandardsAustralia/standards/issues/155 It seeks to consult and develop the Error Catalogue and to address the list of standardised error codes and HTTP status codes for error handling across the CDR ecosystem.
It is open for feedback until the 19th of February 2021.
Please sign in to leave a comment.