sedex Messaging receipt versions
Overview¶
New releases may contain new message codes and may use a different XML namespace that requires changes in the application. To offer backward compatibility, the sedex Adapter can be configured to use an old message error schema with old message error codes.
Version 1.0¶
The sedex Client 5.0 and later do not support receipt version 1.0.
Version 2.0¶
Since: sedex Adapter 2.0
Receipt xml namespace: eCH0090/2
Receipt codes¶
New codes since version 1.0:
Code | Remark |
---|---|
203 | Message too old to send |
204 | Message expired |
313 | Other recipients are not allowed to receive |
330 | Message size exceeds limit |
404 | Authorization service not reachable |
501 | Error during receiving |
601 | Message successfully sent |
701 | Message expires soon |
Deprecated codes since 1.0:
Code | Remark |
---|---|
320 | Changed to code 204, “Message expired” |
Full list of Codes:
Code | Remark |
---|---|
100 | Message correctly transmitted |
200 | Invalid envelope syntax |
201 | Duplicate message ID |
202 | No payload found |
203 | Message too old to send |
204 | Message expired |
300 | Unknown sender ID |
301 | Unknown recipient ID |
302 | Unknown physical sender ID |
303 | Invalid message type |
304 | Invalid message class |
310 | Not allowed to send |
311 | Not allowed to receive |
312 | User certificate not valid |
313 | Other recipients are not allowed to receive |
330 | Message size exceeds limit |
400 | Network error |
401 | OSCI hub not reachable |
402 | Folder not reachable |
403 | Logging service not reachable |
404 | Authorization service not reachable |
500 | Internal error |
501 | Error during receiving |
601 | Message successfully sent |
701 | Message expires soon |