blob: 23d68fbc29149261639caa1004c0e150b65a54a3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
https://vrkennung.de/fintshbci-allgemein/
### ---- key based access. Extracted from https://www.aquamaniac.de/sites/download/download.php?package=09&release=09&file=01&dummy=aqbanking4-handbook-20091231.pdf
# 1 Create local keys _container_ (so no keys are created yet).
$ gct-tool create -t ohbci -n output.medium
# 2 Create user associated with local keys. (From now on, ${UNIQUEID} points to this fresh user)
$ aqhbci-tool4 adduser -s 'https://hbci.gad.de' -u VRK588XXXX -c VRK588XXX -N 67264051XXX -b 43060967 -t ohbci --context=1 --rdhtype=0 --hbciversion=300 -n output.medium
# 3 Get keys (sign & crypt) from the bank. Didn't work.
$ aqhbci-tool4 getkeys --user=${UNIQUEID}
# 4 Show local (container) and bank's keys. No warnings reported, but neither keys hashcodes.
$ gct-tool showkey -t ohbci -n output.medium
# 5 Actually create keys now. Worked.
$ aqhbci-tool4 createkeys --user=${USER}
# 6 Send keys to the bank. Didn't work (I suspect the URL associate with the user is not right).
$ aqhbci-tool4 sendkeys --user=${USER}
# 7 Last, generate letter. Worked.
$ aqhbci-tool4 iniletter --user=${USER} > ini.txt
# 8 Pen-sign the letter and send via snail mail to the bank.
============== mobile TAN method below; could not get it to work.
# Add a user in the system. The user has a bank and a customer id,
# but is _not_ active yet (see commands below).
$ aqhbci-tool4 adduser -s 'https://hbci-pintan.gad.de/cgi-bin/hbciservlet' -u VRK588XXX -c VRK588XXX -N 6726405XXX -b 43060967 -t pintan --context=1
# Then get the "sysid".
$ aqhbci-tool4 getsysid --user=U
# Finally, give the following command to "unlock" the user.
$ aqhbci-tool4 getitanmodes --user=U
# If the three commands above all worked out, then balance
# and transactions list should be available. Try this with
# the following commands.
$ aqbanking-cli request --balance
# and
$ aqbanking-cli request --transactions
# At this point, we need to workaround the lack of a BIC code
# in the configuration, in order to be able to get the PIN by
# phone. Say the BIC is BANKBIC, edit the following file adding
# a 'bic=BANKBIC' line next to the other details in the upper part
# of the file:
~/.aqbanking/settings6/accounts/<unique-user-id>.conf
# If the previous step worked, then issue a SEPA transfer with:
$ aqbanking-cli sepatransfer --aid=<bank-account-id> --riban='DEXXX' --value="1,00:EUR" --rbic="REMOBIC" --rname="Remote Owner Name" --purpose="Test transfer 2" --name="Issuer Name" -E "Test 222"
# NOTE: <bank-account-id> is the id number that Aqbanking gives
# to bank accounts (not users!). It can be seen by the following
# command:
$ aqbanking-cli listaccs
# <bank-account-id> is now found in the second to last field.
|
