commit fc155c001adaa71c1dea164b91a923f63c497a4f parent 5823ad8b68e7259de00fda3c1187e046ae04abbd Author: Christian Grothoff <christian@grothoff.org> Date: Tue, 21 Apr 2020 10:29:37 +0200 expand repurchase detection text based on Florian's feedback Diffstat:
| M | taler-merchant-api-tutorial.rst | | | 6 | +++++- |
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git 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 +unique. .. _Giving-Customers-Tips: