summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-04-19 14:56:47 +0200
committerFlorian Dold <florian@dold.me>2021-04-19 14:56:47 +0200
commitf29c8456f2d75673523a72682af5c8b877167721 (patch)
tree11707c81b7a3370021c1fe58c0ace896e1dd44bb
parent5e1be48814d87374dcd1fecbeab57071ed278fd6 (diff)
downloaddocs-f29c8456f2d75673523a72682af5c8b877167721.tar.gz
docs-f29c8456f2d75673523a72682af5c8b877167721.tar.bz2
docs-f29c8456f2d75673523a72682af5c8b877167721.zip
clarify Q/A
-rw-r--r--design-documents/013-peer-to-peer-payments.rst10
1 files changed, 6 insertions, 4 deletions
diff --git a/design-documents/013-peer-to-peer-payments.rst b/design-documents/013-peer-to-peer-payments.rst
index 1724605..6c87df9 100644
--- a/design-documents/013-peer-to-peer-payments.rst
+++ b/design-documents/013-peer-to-peer-payments.rst
@@ -400,9 +400,11 @@ Q / A
* Q: Why do merchant payments not use purses?
- * A: Refunds aren't possible with purses, the customer can't prove that
- they own the contract terms (contract terms claiming isn't interactive).
+ * Refunds aren't possible with purses after they're closed
+ * Partial refunds aren't possible
+ * the customer can't prove that they own the contract terms (contract terms claiming isn't interactive)
+ * the merchant can't cover deposit fees
+ * (All of these could be addressed, but the resulting protocol isn't necessarily simpler
+ than what we currently have.)
- * All these issues could be addressed though. But that
- would be a major "Taler 2.0 / 3.0" protocol change