taler-docs

commit fa1e3e5c51b09febec252b5a2d60cdd17f5500eb
parent b53697f7d58b0d2527eed98a3b0bbd12b58258ae
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun,  9 Nov 2025 22:05:42 +0100

clarify #10568: fulfillment_url description

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

1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -964,8 +964,13 @@ Querying payment status
       // URI that the wallet must process to complete the payment.
       taler_pay_uri: string;
 
-      // Status URL, can be used as a redirect target for the browser
-      // to show the order QR code / trigger the wallet.
+      // Fulfillment URL of the contract.
+      // If present, it should be possible to create an
+      // equivalent order by redirecting a browser to this
+      // URL. Once the customer has paid, they should see the
+      // order's fulfillment (digital goods, tracking data for
+      // shipping, etc.) under this URL (assuming they use the
+      // same session that the wallet used when making the payment).
       fulfillment_url?: string;
 
       // Alternative order ID which was paid for already in the same session.