You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The media-type of XML messages is currently defined as application/xml.
In the example request <?xml version="1.0" encoding="UTF-8"?> is declared inside the file as text, but not mandatory. ... so the content-type negotiation would be up to the SU / SP ...
One Service User sent us XML without any encoding.
We expected for historic reason "ISO-8859-1" as default.
PROPOSAL
Let's change the media-type from application/xml to application/xml; charset=utf-8 in Release 5.0 and never talk about the issue again :-).
Here the location in the specification:
One of the sections affected - PAIN.001 upoad in PSS:
/iso20022/payments:
post:
tags:
- iso20022
summary: Submit an ISO20022 XML payment instruction (PAIN.001)
description: >
Submit an ISO20022 XML PAIN.001 payment instruction.
The submitted payment instruction must conform to the XML Schema and
Implementation Guidelines defined by Swiss Payment Standards;
see:
https://www.six-interbank-clearing.com/en/home/standardization/iso-payments/customer-bank/implementation-guidelines.html
operationId: submitIso20022PaymentInstruction
parameters:
- $ref: '#/components/parameters/permissionid_in_header'
- $ref: '#/components/parameters/correlation_in_header'
- $ref: '#/components/parameters/agent_in_header'
- $ref: '#/components/parameters/targetid_in_header'
- $ref: '#/components/parameters/psu_ip_in_header'
- $ref: '#/components/parameters/psu_user_agent_in_header'
- $ref: '#/components/parameters/optional_authorization_in_header'
- $ref: '#/components/parameters/optional_instance_id_in_header'
requestBody:
required: true
description: Payment instruction details as defined by data model.
content:
application/xml:
schema:
type: string
The text was updated successfully, but these errors were encountered:
The adding of the «charset=utf-8» in the content header will not be any breaking change. bLink system will not validate if the enconding complies with UTF-8 therefore there will be no impact on serivce user nor service provider.
The adding helps to state more precise and clear which enconding is expected.
IS:
application/xml
.<?xml version="1.0" encoding="UTF-8"?>
is declared inside the file as text, but not mandatory.... so the content-type negotiation would be up to the SU / SP ...
PROPOSAL
application/xml
toapplication/xml; charset=utf-8
in Release 5.0 and never talk about the issue again :-).Here the location in the specification:
![image](https://private-user-images.githubusercontent.com/123551879/298952863-e04a05ed-074f-457d-a5c5-f41911e7e00b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkwMTY2MzgsIm5iZiI6MTcxOTAxNjMzOCwicGF0aCI6Ii8xMjM1NTE4NzkvMjk4OTUyODYzLWUwNGEwNWVkLTA3NGYtNDU3ZC1hNWM1LWY0MTkxMWU3ZTAwYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjIyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyMlQwMDMyMThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04OWJkNjM5YmM2ZmE2ODMzNDIyZDI4NDA2N2M2MDIwZmRjNTU1N2M2ZWJiZmM1NzBjNDU0NGJhM2E2NWNjOGM3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.TYlCMUO891f7Osu5cIVw_X4dx2GZIf6qiio9ttKxzTc)
One of the sections affected - PAIN.001 upoad in PSS:
The text was updated successfully, but these errors were encountered: