SSB tickets with numeric station IDs marked as AlphaNum (DB, SNCB)

[craftbyte]

While inspecting SNCB SSB tickets, I noticed that the station codes/numbers are marked as AlphaNum but then proceed to be encoded as 30-bit integers.

The same seems to happen with DB-issued Netherlands KeyCards (issued for example when someone books a disabled companion ticket to the Netherlands from the ticket machines).

Here is an example of an SNCB ticket:

3110204040020006544975996596184d74a5800008cf8b64c33e2d9300008208010dc05528000000000000000000000000000000000000000000302c02146e0df9b853324bcf4a7127d999ad0395bd44e11a0214458e942a0e2a244ab00ab7099276eebd3cc9dc8100000000000000000000

Here is some DB Keycard payloads:

310e044040408986106525548d55e14d250c0281580f4260a387526a00013c3a5374ffdf759c8000000000000000000000000000000000000000302c02147107d4e8e958f082734a3a411641101729f48abd021451d9646e819f4cd939bd60df27a719a3ff4e973900000000000000000000
310e044040408986106525548d55d692350c01009809ba3e838752fd80013c3a5374ffdf759c8000000000000000000000000000000000000000302c02140f66520abbd6b610200917d2cde6c7827a7df92602145539ce6cae6e08003e2cdf417e37960d739f19a000000000000000000000

Should the library support overriding the decoder or maybe allow the user the access the raw byte array in the destination field?

[CGantert345]

DB is looking into the topic.

[craftbyte]

Anything from SNCB as well?

[CGantert345]

The issue will be dicussed on the UIC user group. Maybe it will be solved by moving forward to use the FCB barcode in the near future.