summaryrefslogtreecommitdiff
path: root/design-documents/026-refund-fees.rst
diff options
context:
space:
mode:
Diffstat (limited to 'design-documents/026-refund-fees.rst')
-rw-r--r--design-documents/026-refund-fees.rst12
1 files changed, 8 insertions, 4 deletions
diff --git a/design-documents/026-refund-fees.rst b/design-documents/026-refund-fees.rst
index f65da4a4..b2d03066 100644
--- a/design-documents/026-refund-fees.rst
+++ b/design-documents/026-refund-fees.rst
@@ -1,5 +1,9 @@
-Refunds and Fees
-################
+DD 26: Refunds and Fees
+#######################
+
+.. note::
+
+ This is implemented (as of 2023-09-15).
Summary
=======
@@ -15,7 +19,7 @@ When a user receives a refund, we have to decide what happens to the deposit
fee that was originally paid on the associated deposit. Originally, we said
that the deposit fee is waived when any refund happens. However, if the
refund fee is zero and the deposit fee is non-zero, this results in a
-problematic scenario where merchants issue miniscule refunds that primarily
+problematic scenario where merchants issue minuscule refunds that primarily
enable customers to effectively obtain the deposit fee.
@@ -25,7 +29,7 @@ Requirements
* If the refund and refresh fees are zero, it should be possible for
consumers to get 100% of their digital cash back on refunds.
* This should not result in a problematic situation where merchants
- conspire with consumers and issue miniscule refunds to allow consumers
+ conspire with consumers and issue minuscule refunds to allow consumers
to work around deposit fees.
Proposed Solution