Please enable JavaScript.
Coggle requires JavaScript to display documents.
pain 008 - Coggle Diagram
pain 008
POST
ZIP
New end point will be used to upload zip file after having considered GAT proposal (to use a file server in future, work needed in infra library if same end point is used temporarily etc)
-
-
The response object should contain a list of unique file ids & list of statusReportId obtained upon uploading a pain.008 file.
For sync processing we should tell the aggregated payment status but for asyn processing we should not(as its not possible to immediately return the status when its async)
-
Zip file upload should be rejected even if one pain file within the zip is incorrect (structure validation). Zip file upload should be accepted if structure received is incorrect with fileId sent back in response.
-
-
-
If the file is uploaded as a zip then file returned on GET end point should have the name of the pain file inside the zip. Both zip and pain file should have the same name but just different extension (zip and xml respectively).
XML
-
-
-
-
The rule for sync and async processing remain the same that is less than 500 positions (configurable value) we do sync processing and 500 or more positions in incoming xml we switch to async processing.
-
-
-
-