Add CAMT.052 v08 support

[Robera16]

This PR adds support for the CAMT.052 v08 message format while keeping v02 as a fallback to ensure backward compatibility. The change updates the supported_camt_messages list so that v08 is preferred if the bank supports it, but older versions will still work. This ensures the system remains compliant with the latest ISO 20022 standard and compatible with banks still using earlier versions.

[thtomate]

I guess it hit Atruvia (service provider of many german credit unions and the like) tonight.

[chrisv2]

@thtomate

Yes, and with Atriuva the PR doesn't work, one needs to set only urn:iso:std:iso:20022:tech:xsd:camt.052.001.08, if we add .02 as in the patch it would return 9010 camt-Nachricht nicht zugelassen:

            responses = self._fetch_with_touchdowns(
                dialog,
                lambda touchdown: hkcaz(
                    account=hkcaz._fields['account'].type.from_sepa_account(account),
                    all_accounts=False,
                    date_start=start_date,
                    date_end=end_date,
                    touchdown_point=touchdown,
                    supported_camt_messages=SupportedMessageTypes([
                        'urn:iso:std:iso:20022:tech:xsd:camt.052.001.08'
                    ]),
                ),
                FinTS3Client._response_handler_get_transactions_xml,
                'HICAZ'
            )

[FabKn]

@chrisv2: I can confirm that your solution solves the problem for Atruvia. Two lists entries is not working. It would be great if the pull request could be adjusted accordingly.

[lindstrom79]

Is there any update here? We also face issues with Atruvia. We can login, but we can´t fetch transactions and get a HICAZ error. Thanks a lot.

[chrisv2]

@lindstrom79 you can patch your version manually, that's what I do right now. Be aware that while this works for Atruvia and Sparkasse, it may not work for all other banks. It is really unfortunate that Atruvia doesn't serve requests as soon as there is an output format they don't support, even though other supported formats are present (like in the original patch).

FWIW, here is my patch:

--- client.orig.py	2025-11-18 17:51:12.728612162 +0100
+++ client.py	2025-11-18 17:51:48.599798844 +0100
@@ -591,7 +591,7 @@
                     date_start=start_date,
                     date_end=end_date,
                     touchdown_point=touchdown,
-                    supported_camt_messages=SupportedMessageTypes(['urn:iso:std:iso:20022:tech:xsd:camt.052.001.02']),
+                    supported_camt_messages=SupportedMessageTypes(['urn:iso:std:iso:20022:tech:xsd:camt.052.001.08']),
                 ),
                 FinTS3Client._response_handler_get_transactions_xml,
                 'HICAZ'

I apply this in my Dockerfile like this, ofc if you don't use docker you have to adapt paths to your environment:

COPY patches/fints_camt.patch /tmp/fints_camt.patch
RUN patch -p0 -d /usr/local/lib/python3.12/site-packages/fints < /tmp/fints_camt.patch 

For a proper fix it would probably be necessary to read supported formats from the BPD. The information is there, but it is not used atm.

[Robera16]

@lindstrom79 removed the camt.052.001.02 support from the SupportedMessageTypes. Now it works fine for Atruvia

[Robera16]

@raphaelm Please review this PR so it can be merged, as MT940 support is now deprecated.

[lindstrom79]

@lindstrom79 removed the camt.052.001.02 support from the SupportedMessageTypes. Now it works fine for Atruvia

Thank you so much. Will try it.

[varac]

@Robera16 I am still getting the No supported HIKAZS version found. with atruvia (see #200), even when I use your branch like this:

uv add "fints @ git+https://github.com/Robera16/python-fints" --branch add-support-for-CAMT-v08-formats  

[varac]

@lindstrom79 Does it work for you ?

[Robera16]

@Robera16 I am still getting the No supported HIKAZS version found. with atruvia (see #200), even when I use your branch like this:

uv add "fints @ git+https://github.com/Robera16/python-fints" --branch add-support-for-CAMT-v08-formats  

@varac I'm not sure, but maybe try the other versions. It’s better if you check which version your bank supports.
Here are some other versions you can try:

urn:iso:std:iso:20022:tech:xsd:camt.053.001.08

urn:iso:std:iso:20022:tech:xsd:camt.054.001.08

[raphaelm]

This will be fixed more permanently in #201

[varac]

@varac I'm not sure, but maybe try the other versions. It’s better if you check which version your bank supports. Here are some other versions you can try:

urn:iso:std:iso:20022:tech:xsd:camt.053.001.08

urn:iso:std:iso:20022:tech:xsd:camt.054.001.08

@Robera16 Unfortunatly both of them didn't fix the issue, neither latest head as of now (with merged #201)