summaryrefslogtreecommitdiff
path: root/core/api-merchant.rst
diff options
context:
space:
mode:
Diffstat (limited to 'core/api-merchant.rst')
-rw-r--r--core/api-merchant.rst28
1 files changed, 25 insertions, 3 deletions
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index ecb4d4e7..d8e3c910 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -34,7 +34,12 @@ This is useful when multiple businesses want to share the same payment
infrastructure.
Merchant backends have one special ``default`` instance. This ``default``
-instance is used when no explicit instance is specified.
+instance is used when no explicit instance is specified. Despite its name,
+this instance must be created after the installation. In case *no* default
+instance is found - or its credentials got lost -, the administrator can use
+the default instance's rights by resorting on the ``--auth`` command line option,
+or by restarting the service by providing a environment variable called
+``TALER_MERCHANT_TOKEN``.
Each instance (default and others) has a base URL. The resources under
this base URL are divided into to categories:
@@ -2592,6 +2597,14 @@ Query funds remaining
// Is this reserve active (false if it was deleted but not purged)?
active: boolean;
+
+ // URI to use to fill the reserve, can be NULL
+ // if the reserve is inactive or was already filled
+ payto_uri: string;
+
+ // URL of the exchange hosting the reserve,
+ // NULL if the reserve is inactive
+ exchange_url: string;
}
.. ts:def:: TipStatusEntry
@@ -2840,10 +2853,19 @@ The contract terms must have the following structure:
amount: Amount;
// The URL for this purchase. Every time it is visited, the merchant
- // will send back to the customer the same proposal. Clearly, this URL
- // can be bookmarked and shared by users.
+ // will send back to the customer the same proposal.
+ // The URL should be bookmarkable.
+ // Either fulfillment_url or fulfillment_message must be specified.
fulfillment_url?: string;
+ // Message shown to the customer after paying for the order.
+ // Either fulfillment_url or fulfillment_message must be specified.
+ fulfillment_message?: string;
+
+ // Map from IETF BCP 47 language tags to localized fulfillment
+ // messages.
+ fulfillment_message_i18n: { [lang_tag: string]: string };
+
// Maximum total deposit fee accepted by the merchant for this contract.
max_fee: Amount;