diff options
| author | MS <ms@taler.net> | 2020-08-31 13:39:53 +0200 |
|---|---|---|
| committer | MS <ms@taler.net> | 2020-08-31 13:39:53 +0200 |
| commit | ac6f28ecbfc116894ef82f02decfc61da52cad13 (patch) | |
| tree | 75fc4c84f3027c9e5d1284f8ff3d007c59fe7702 /libeufin | |
| parent | ca3c4460f6b59076980456d30c5dd13dec4a87ee (diff) | |
| download | docs-ac6f28ecbfc116894ef82f02decfc61da52cad13.tar.gz docs-ac6f28ecbfc116894ef82f02decfc61da52cad13.tar.bz2 docs-ac6f28ecbfc116894ef82f02decfc61da52cad13.zip | |
english
Diffstat (limited to 'libeufin')
| -rw-r--r-- | libeufin/bank-transport-ebics.rst | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/libeufin/bank-transport-ebics.rst b/libeufin/bank-transport-ebics.rst index 0d06f83b..d335c6ef 100644 --- a/libeufin/bank-transport-ebics.rst +++ b/libeufin/bank-transport-ebics.rst @@ -27,8 +27,8 @@ The following steps are required to set up an EBICS bank transport: 5. 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 print a document that contains the public key and hashes for all three key pairs. - The user then signs this document sends it to the bank (physically/scanned). +6. 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 to the electronically sent keys. If they match, the bank sets the state of the @@ -51,5 +51,3 @@ Alternative ways of setting up the EBICS bank transport are: * Importing from a backup. The backup contains metadata (EBICS URL, HostID, UserId, ...) and the three passphrase-protected subscriber keys. * Certificate-based setup (currently not supported by LibEuFin, only used in France) - - |