diff options
| author | Thien-Thi Nguyen <ttn@gnuvola.org> | 2020-11-27 19:21:43 -0500 |
|---|---|---|
| committer | Thien-Thi Nguyen <ttn@gnuvola.org> | 2020-11-27 19:23:43 -0500 |
| commit | 8b8fa591fce11d1763cd94c90a746cac4550ea8a (patch) | |
| tree | e838a5b93fd30cf4926f85f1f059ad84c944f863 /libeufin | |
| parent | 44e94a16d304e162071c8687dfa76db286c41f0d (diff) | |
| download | docs-8b8fa591fce11d1763cd94c90a746cac4550ea8a.tar.gz docs-8b8fa591fce11d1763cd94c90a746cac4550ea8a.tar.bz2 docs-8b8fa591fce11d1763cd94c90a746cac4550ea8a.zip | |
renumber list in section "Bank Transport Setup"
Diffstat (limited to 'libeufin')
| -rw-r--r-- | libeufin/bank-transport-ebics.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/libeufin/bank-transport-ebics.rst b/libeufin/bank-transport-ebics.rst index 844b1f5c..5afdd5d6 100644 --- a/libeufin/bank-transport-ebics.rst +++ b/libeufin/bank-transport-ebics.rst @@ -24,26 +24,26 @@ The following steps are required to set up an EBICS bank transport: 3. The LibEuFin nexus generates cryptographic key material (3 RSA key pairs). -5. The nexus sends the public keys electronically to the bank's EBICS server, together with the information +4. The nexus sends the public keys electronically to the bank's EBICS server, together with the information identifying the subscriber (PartnerID, UserID, SystemID). -6. The user prints a document that contains the public key and hashes for all three key pairs. +5. The user prints a document that contains the public key and hashes for all three key pairs. The user then signs this document and sends it to the bank (physically/scanned). -7. The bank receives the letter and verifies that the keys from the letter correspond +6. The bank receives the letter and verifies that the keys from the letter correspond to the electronically sent keys. If they match, the bank sets the state of the subscriber to "ready". -8. The user now has to wait until the bank has set the EBICS subscriber state to "ready". +7. The user now has to wait until the bank has set the EBICS subscriber state to "ready". There is no in-band notification for this, but the Nexus can try downloading the bank's cryptographic parameters. This will only succeed once the EBICS subscriber is set to "ready" by the bank. -9. The user should confirm the public keys of the bank received in the previous step. +8. The user should confirm the public keys of the bank received in the previous step. Typically the bank gives the value of these public keys in an out-of-band channel. -10. Now the user can finally use the EBICS bank transport. The first step after finishing - the setup should be to import the bank accounts accessible for this EBICS subscriber. +9. Now the user can finally use the EBICS bank transport. The first step after finishing + the setup should be to import the bank accounts accessible for this EBICS subscriber. Alternative ways of setting up the EBICS bank transport are: |