J.P. Morgan has been tested for their global EBICS channel as well and confirmed to be working.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
When using the software with multiple banks, the current config file solution wasn't very flexible. We had some different local implementation at our end. In order to use upstream software directly without any changes, suggesting to merge these changes. For me locally it would mean I can get rid of a lot of local example code which are currently bank and even entity specific and can be made more generic.
This will also allow multiple EBICS connections with the same bank for different entities as well, in case this is needed. In our case we have multiple EBICS connections with the same bank.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
For some unknown reason, the signature gets a length of 257 bytes instead of 256 bytes, and the length of the hex value is 514 bytes instead of 512 bytes.
This works around it, until a proper fix is implemented. The bug seems to be caused by https://github.com/node-ebics/node-ebics-client/blob/master/lib/crypto/Crypto.js#L71 somehow.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
Some banks provide zipped CAMT statements, add some example code on how to write these to a file.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
Add custom order types (G02, G52, G53, G1R and G1V) and examples for Bank GPB AO (Gazprombank Russia).
Pain.001.001.06 (RUB) - G1R
Pain.001.001.06 (FCY/FX/RLS) - G1V
Pain.002.001.06 - G02
Camt.052.001.05 - G52
Camt.053.001.05 - G53
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
XG1 order type is used for ISO XML 20022 CGI (Common Global Implementation) which should be a unified format that works within a country (irrespective of bank).
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
