-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PSS - POST /payments - Move "submissionId" from "Location"-Header to a JSON-body #88
Comments
Considering RESTful design ( |
Meeting Notes 4.4.24The participants agreed that the community shall be asked to provide feedback on the proposed solution. Proposed solution: Return the submission ID in request body instead of location header. Task to all SFTI XS2A members: Please provide your feedback by 30th April if you would agree to implement the proposed solution in the next major version V5. |
|
Meetin Notes 20.6.24This issue will be discussed on 15th August. |
Meetin Notes 15.8.24The pull request has to be generated and presented on 26th September by @ochatelain. |
Meeting Notes 26.9.24The update / Pull Request will be discussed on next meeting 31st October. The pull request will be generated and presented by @ochatelain. |
Meeting Notes 31.10.24@ochatelain presented the issue and elaborated that submissionId in the response will be first added into the body for V5 and then for V6 removed from the header. Dominik M. (ZKB) and Roland (Finnova) will clarify what the change means effort-wise. An update is expected on next meeting. |
Meeting Notes 12.12.24Due to functional adjustments deriving from issue #141 the endpoint POST/payment need to be adapted. In the course of this adjustment the change of the submissionId can be taken up as well. The Pull Request has been approved and will be merged into V5. |
Add the submissionId to standing-order, single-payments, payments. --------- Co-authored-by: chatelao <[email protected]>
Issue merged with respecting pull request. |
IS
SHOULD
The text was updated successfully, but these errors were encountered: