Postbank holdings

[obccgn]

Hello,

can this be fixed? Whats the issue?

Fatal error: Uncaught Fhp\Protocol\UnexpectedResponseException: The server does not support any HIWPDS versions implemented in this library in D:\wamp\www\vendor\nemiah\php-fints\lib\Fhp\Protocol\BPD.php on line 119

I have tried several different bankcodes, but none works. I am currently using 10010010, the IBAN shows 39070224, login is done with Postbank ID and correct pin.

browser.php example works, but yes, browser.php is only for accounts and not for holdings, as far as i know.

Thanks

[obccgn]

Hello,

can this be fixed? Whats the issue?

Fatal error: Uncaught Fhp\Protocol\UnexpectedResponseException: The server does not support any HIWPDS versions implemented in this library in D:\wamp\www\vendor\nemiah\php-fints\lib\Fhp\Protocol\BPD.php on line 119

I have tried several different bankcodes, but none works. I am currently using 10010010, the IBAN shows 39070224, login is done with Postbank ID and correct pin.

browser.php example works, but yes, browser.php is only for accounts and not for holdings, as far as i know.

Thanks

Chatgpt helped me to find out this:

[HIWPDS] => Array
  | (
  | [6] => Fhp\Segment\AnonymousSegment Object
  | (
  | [type] => HIWPDSv6
  | [segmentkopf] => Fhp\Segment\Segmentkopf Object
  | (
  | [segmentkennung] => HIWPDS
  | [segmentnummer] => 25
  | [segmentversion] => 6
  | [bezugselement] => 3
  | )
  | )
  | )

[Philipp91]

Ooh, ChatGPT is getting good. Printing that would have been my first debugging step as well.

The [6] says that the bank supports version 6. This directory shows that phpFinTS only supports version 5. It should be easy enough to add version 6 (assuming they only added some new fields that we can safely declare but not populate). If you find the specification for it somewhere, just add corresponding three new files to the WDP directory. In the case where there's no change between versions or where only new fields are appended, it's common to use inheritance from the previous version like this.

The "finding the specification" (a PDF online somewhere, sadly the original https://www.hbci-zka.de/dokumente/spezifikation_deutsch/fintsv3/FinTS_3.0_Messages_Geschaeftsvorfaelle_2015-08-07_final_version.pdf seems to have disappeared) will have to be done by a human most likely. The rest ChatGPT might be able to pull off, if you can ingest the old and new specification for that segment type into it.