Process variant 1 for HKTAN2

[mehmetkemalbayer]

Hello,
When do you plan to implement process variant 1 for HKTAN2?
Thank you.

[raphaelm]

We currently have no plans, but feel free to contribute :)

[mehmetkemalbayer]

Hi @raphaelm,
I'd really appreciate if I could contribute.
I have really minor knowledge of python but I have 12 years of experience.
So please help me to get started then I can handle the rest.
Best.

[raphaelm]

Hi Mehmet, I just looked into this and unfortunately, this will be pretty complicated. We currently implement process variant 2, which works like this

Customer → Bank: Here's a bank transfer
Bank → Customer: We need a TAN, here's a challenge
Customer → Bank: Here's the TAN computed from the challenge
Bank → Customer: OK, job executed.

Process variant 1 looks different:

Customer → Bank: Here's the hash value of a transfer I'm about to do
Bank → Customer: Okay, we'll need a TAN, here's a challenge
Customer → Bank: Okay, here's the TAN and our actual transfer.
Bank → Customer: OK, job executed.

It's therefore not just about implementing a new variant of a segment type, but we'd need to

1. Rework the implementation of multi-step requests to change the order in which things are being sent.

2. Implement the methods to compute a hash of the job. The hash method is set by the bank during dialog initialization. It should default to RIPEMD-160 today, but that's not guaranteed.

Implementing this will require

1. a good study of the sepcification which is only available im German

2. a bank account to test with

Things get much more complicated once a job requires multiple TANs, but we are ignoring that for process variant 2 as well right now.

If I may ask, what kind of bank and type of transfer do you use where process variant 2 doesn't work?

[raphaelm]

Closing for inactivity