taler-docs

commit 085eb41be9e855249ccdb9415f0fde3e6b784dcf
parent 54249ff93d61e2261c26349c1fb04e18ce6f37de
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue, 28 Oct 2025 22:56:00 +0100

specify new
DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL option, clarify new rules for the various DEFAULT DELAY options of an instance

Diffstat:
M
manpages/taler-merchant.conf.5.rst
 | 
35
++++++++++++++++++++++++++---------

1 file changed, 26 insertions(+), 9 deletions(-)
diff --git a/manpages/taler-merchant.conf.5.rst b/manpages/taler-merchant.conf.5.rst
@@ -176,13 +176,6 @@ LEGAL_PRESERVATION
    How long do we keep data in the database for tax audits after the
    transaction has completed?  Default is 10 years.
 
-DEFAULT_WIRE_TRANSFER_DELAY
-   What is the default wire transfer delay for new instances. This is how long the
-   exchange has to settle the payment with a wire transfer, enabling refunds and aggregation
-   of multiple transfers to happen until this time.
-   This backend default can be changed per-instance and then still overridden per-order.
-   Defaults to one month if not specified in the configuration.
-
 DEFAULT_PAY_DELAY
    What is the default payment delay for new instances. This is how long the
    customer has to pay the order before the offer expires.
@@ -191,11 +184,35 @@ DEFAULT_PAY_DELAY
 
 DEFAULT_REFUND_DELAY
    What is the default refund delay for new instances. This is how long the
-   merchant can grant refunds to the customer. Must be smaller than the
-   wire transfer delay (for an actual order).
+   merchant can grant refunds to the customer. Is added on top of the
+   payment deadline (for an actual order).
    This backend default can be changed per-instance and then still overridden per-order.
+   If the order overrides the wire transfer deadline and does not
+   specify a refund deadline and if the DEFAULT_REFUND_DELAY would
+   imply a longer refund deadline, then the wire transfer deadline
+   is used for the refund deadline.
    Defaults to 15 days if not specified in the configuration.
 
+DEFAULT_WIRE_TRANSFER_DELAY
+   What is the default wire transfer delay for new instances. This is how long the
+   exchange has to settle the payment with a wire transfer, enabling refunds and aggregation
+   of multiple transfers to happen until this time.
+   The value given is added on top of the refund deadline and is then
+   subject to rounding as per DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL.
+   This backend default can be changed per-instance and then still overridden per-order.
+   Defaults to one month if not specified in the configuration.
+
+DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL
+   Specifies to what time interval a wire transfer deadline computed
+   via the DEFAULT_WIRE_TRANSFER_DELAY should be rounded up. Supported
+   values are NONE, SECOND, MINUTE, HOUR, DAY, WEEK, MONTH, QUARTER and
+   YEAR, each implying that wire transfer deadline computed
+   should be rounded up to the respective end of the next interval
+   using the local timezone of the merchant backend.
+   This backend default can be changed per-instance.
+   Rounding does not apply if the wire deadline is overridden per-order.
+   Defaults to NONE (no rounding up) if not specified in the configuration.
+
 FORCE_AUDIT
    Force the merchant to report every transaction to the auditor
    (if the exchange has an auditor)?  Default is ``NO``.