commit eebd0b2be304080faea953db8e5296a36b3ed981 parent e9c1ede11da852e0f7d49a30c88fd27b02ff08e3 Author: Thien-Thi Nguyen <ttn@gnuvola.org> Date: Tue, 23 Mar 2021 16:45:56 -0400 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:
| M | taler-mcig.rst | | | 8 | +++++--- |
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git 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