From 1666a64182e546fbd1ed1c1397b02b890fb541e2 Mon Sep 17 00:00:00 2001
From: Christian Grothoff <christian@grothoff.org>
Date: Wed, 8 Jan 2020 10:04:20 +0100
Subject: remove ebics (#6038)

---
 manpages/taler.conf.5.rst | 14 ++------------
 taler-exchange-manual.rst | 33 +++++++++++----------------------
 2 files changed, 13 insertions(+), 34 deletions(-)

diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index 413150d7..2b2d7f39 100644
--- a/manpages/taler.conf.5.rst
+++ b/manpages/taler.conf.5.rst
@@ -107,7 +107,7 @@ PRIVACY_DIR
 PRIVACY_ETAG
    Works the same as TERMS_ETAG, just for the privacy policy.
 
-   
+
 EXCHANGE POSTGRES BACKEND DATABASE OPTIONS
 ------------------------------------------
 
@@ -237,7 +237,7 @@ WIRE_RESPONSE
 
 PLUGIN
    Name of the plugin can be used to access the account
-   (i.e. “taler-bank” or “ebics”). Used by the merchant backend for back
+   (i.e. “taler_bank”). Used by the merchant backend for back
    office operations (i.e. to identify incoming wire transfers) and by
    the exchange.
 
@@ -280,16 +280,6 @@ PASSWORD
    Password to use for authentication. Used with the “basic”
    authentication method.
 
-EBICS AUTHENTICATION OPTIONS
-----------------------------
-
-The following authentication options are supported by the “ebics” wire
-plugin. They must be specified in the “[account-]” section that uses the
-“ebics” plugin.
-
-NONE
-   Currently the “ebics” implementation is incomplete and does not
-   support authentication.
 
 EXCHANGE WIRE FEE OPTIONS
 -------------------------
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index e12c4562..49638171 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -398,9 +398,9 @@ information:
    “x-taler-bank”) is called the wire method.
 
 -  A matching wire plugin that implements a protocol to interact with
-   the banking system. For example, the EBICS plugin can be used for
-   SEPA transfers, or the “taler-bank” plugin can interact with the
-   Taler bank demonstrator. A wire plugin only supports one particular
+   the banking system. For example, the “taler-bank” plugin can interact
+   with the Taler bank demonstrator or with libeufin.
+   A wire plugin only supports one particular
    wire method. Thus, you must make sure to pick a plugin that supports
    the wire method used in the URL.
 
@@ -452,8 +452,10 @@ The generated file will be echoed by the exchange when serving
 Wire plugin “taler_bank”
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-x-taler-bank
-taler_bank plugin
+.. meta::
+   :keywords: x-taler-bank
+   :keywords: taler_bank plugin
+
 The ``taler_bank`` plugin implements the wire method “x-taler-bank”.
 
 The format of the ``payto://`` URL is
@@ -476,28 +478,15 @@ the “USERNAME” and “PASSWORD” of the respective account at the bank.
    USERNAME = exchange
    PASSWORD = super-secure
 
-.. _Wire-plugin-_0060_0060ebics_0027_0027:
-
-Wire plugin “ebics”
-~~~~~~~~~~~~~~~~~~~
-
-The “ebics” wire plugin is not fully implemented and today does not
-support actual wire transfers.
-
-   **Note**
-
-   The rationale behind having multiple bank accounts is that the
-   exchange operator, as a security measure, may want to instruct the
-   bank that the incoming bank account is only supposed to *receive*
-   money.
-
 .. _Wire-fee-structure:
 
 Wire fee structure
 ~~~~~~~~~~~~~~~~~~
 
-wire fee
-fee
+.. meta::
+  :keywords: wire fee
+  :keywords: fee
+
 For each wire method (“sepa” or “x-taler-wire”, but not per plugin!) the
 exchange configuration must specify applicable wire fees. This is done
 in configuration sections of the format ``fees-METHOD``. There are two
-- 
cgit v1.2.3