summaryrefslogtreecommitdiff
path: root/taler-mcig.rst
diff options
context:
space:
mode:
authorThien-Thi Nguyen <ttn@gnuvola.org>2021-03-23 16:45:56 -0400
committerThien-Thi Nguyen <ttn@gnuvola.org>2021-03-23 16:45:56 -0400
commiteebd0b2be304080faea953db8e5296a36b3ed981 (patch)
treeb067ad94b97bfbaa44afb4330322563e501aedaa /taler-mcig.rst
parente9c1ede11da852e0f7d49a30c88fd27b02ff08e3 (diff)
downloaddocs-eebd0b2be304080faea953db8e5296a36b3ed981.tar.gz
docs-eebd0b2be304080faea953db8e5296a36b3ed981.tar.bz2
docs-eebd0b2be304080faea953db8e5296a36b3ed981.zip
partially explain ‘${ORDER_ID}’ hack in fulfillment URI
(This edit includes a FIXME/question because i don't understand the phrase "POSTing to the merchant" in the original (core/api-merchant.rst) text.)
Diffstat (limited to 'taler-mcig.rst')
-rw-r--r--taler-mcig.rst8
1 files changed, 5 insertions, 3 deletions
diff --git a/taler-mcig.rst b/taler-mcig.rst
index 52ccf227..1140e891 100644
--- a/taler-mcig.rst
+++ b/taler-mcig.rst
@@ -250,9 +250,11 @@ are demonstrated in the next section.
The fulfillment URI is normally included in the contract.
You specify it in :http:post:`[/instances/$INSTANCE]/private/orders`.
- NOTE: explain hack to have the backend include the order ID in
- the fulfillment URI somewhere (useful if the backend auto-generates
- an order ID).
+
+ If the fulfillment URI contains the literal string ``${ORDER_ID}``
+ (including curly braces), that will be replaced by the order ID when
+ POSTing to the merchant. (FIXME: What does "POSTing to the merchant" mean?)
+ This is useful when the backend auto-generates the order ID.
Sample Interaction Traces