path: root/taler-merchant-api-tutorial.rst
diff options
authorChristian Grothoff <>2020-04-21 10:29:37 +0200
committerChristian Grothoff <>2020-04-21 10:29:37 +0200
commitfc155c001adaa71c1dea164b91a923f63c497a4f (patch)
tree71126aa6dcbf38ddaa99dafd0bd08575cf41e970 /taler-merchant-api-tutorial.rst
parent5823ad8b68e7259de00fda3c1187e046ae04abbd (diff)
expand repurchase detection text based on Florian's feedback
Diffstat (limited to 'taler-merchant-api-tutorial.rst')
1 files changed, 5 insertions, 1 deletions
diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index d42f74b..438c1cd 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -309,7 +309,11 @@ the same digital product where repurchase detection is desired.
Note that changing the session ID to a different device requires the
involvement of the wallet that made the payment, thus reasonably limiting the
-possibility of broadly sharing the digital purchases.
+possibility of broadly sharing the digital purchases. Repurchase detection is
+also *only* done for HTTP(S) fulfillment URLs. In particular, this means
+fulfillment URIs like "taler://fulfillment-success/$MESSAGE" are not
+considered to identify a resource you can pay for and thus do not have to be
.. _Giving-Customers-Tips: