taler-docs

commit 44ca01614b389c6481f902dec622d189a58fd868
parent f5f172df180ed46f0f0b2b3bd334f0b6df774d80
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue, 23 Sep 2025 16:14:08 +0200

address #10446

Diffstat:
M
core/api-challenger.rst
 | 
6
------
M
core/api-merchant.rst
 | 
9
++++++++-

2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/core/api-challenger.rst b/core/api-challenger.rst
@@ -31,12 +31,6 @@ the resulting client ID to the console.
 
 .. note::
 
-  The current service mandates that redirection URIs
-  start with "http://" or "https://". See issue #7838
-  for what should be done to lift this restriction.
-
-.. note::
-
   Right now, registration of a unique redirection URI is *mandatory* for
   each client. If multiple redirection URIs are needed, it is suggested to
   just register additional clients.  (While OAuth 2.0 would support not
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -575,7 +575,14 @@ Making the payment
       pos_confirmation?: string;
 
       // Signed tokens. Returned in the same order as the
-      // token envelopes were provided in the request.
+      // token envelopes were provided in the request. Specifically,
+      // the order will follow the order of the outputs from the
+      // contract terms, and then within each output follow the
+      // order in which the ``wallet_data`` contained the respective
+      // blinded envelopes.  The donation tokens will be present
+      // at the offset matching the place where a donation receipt
+      // was indicated in the outputs array, and of course be skipped
+      // if the ``PayWalletData`` did not have a ``donau`` field.
       // @since protocol **v21**
       token_sigs?: SignedTokenEnvelope[];