summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2019-01-24 07:07:35 +0100
committerChristian Grothoff <christian@grothoff.org>2019-01-24 07:07:35 +0100
commit1b4eb988604d39c57be795275901fc4b5125a803 (patch)
treec887dd7cd39b92e9dff1077f30b412272a718865
parentd84969bf8ec2434b1b1d3bec34aff70993fa2571 (diff)
downloadwww-1b4eb988604d39c57be795275901fc4b5125a803.tar.gz
www-1b4eb988604d39c57be795275901fc4b5125a803.tar.bz2
www-1b4eb988604d39c57be795275901fc4b5125a803.zip
FAQ on recurring payments
-rw-r--r--faq.html.j220
1 files changed, 20 insertions, 0 deletions
diff --git a/faq.html.j2 b/faq.html.j2
index 6d00a729..0feabc82 100644
--- a/faq.html.j2
+++ b/faq.html.j2
@@ -147,5 +147,25 @@ the project (see also <a href="https://gnunet.org/bugs/">our bugtracker</a>
for a list of open issues).</p>
{% endtrans %}
+
+<h2>{{ _("Does Taler support recurring payments?") }}</h2>
+
+{% trans %}
+<p>Today, our wallet implementation does not support recurring
+payments. Recurring payments, where some fixed amount is paid on a
+regular basis are in theory possible with Taler, but they come with a
+few caveats. Specifically, recurring payments can only work if the
+Taler wallet is running and online around the desired time.
+Furthermore, given their repetitive nature they are linkable, and
+could thus be used to deanonymize the user making the recurring
+payment, for example by forcing the user offline at the time of the
+payment and observing that it does then not happen on time. Finally,
+the Taler wallet does not work with credit and thus the user would
+have to make sure to carry a sufficient balance for the recurring
+payment to be made. Still, they can be useful, and a future version of
+the Taler wallet will likely support them. But this is not a feature
+that we are targeting for Taler 1.0. at this time</p>
+{% endtrans %}
+
</div>
{% endblock body_content %}