diff options
| author | Marcello Stanisci <marcello.stanisci@inria.fr> | 2016-09-21 15:24:45 +0200 |
|---|---|---|
| committer | Marcello Stanisci <marcello.stanisci@inria.fr> | 2016-09-21 15:24:45 +0200 |
| commit | 3c7867cff99db24c17d613fd73bb01f9948d16cc (patch) | |
| tree | dfedcc932c6f14cf2c92c1878e08c7a45e474e7a /api-merchant.rst | |
| parent | f3bdacc82bd86c4895dd5ec62b4093a8716f8503 (diff) | |
| download | docs-3c7867cff99db24c17d613fd73bb01f9948d16cc.tar.gz docs-3c7867cff99db24c17d613fd73bb01f9948d16cc.tar.bz2 docs-3c7867cff99db24c17d613fd73bb01f9948d16cc.zip | |
completing merchant config
Diffstat (limited to 'api-merchant.rst')
| -rw-r--r-- | api-merchant.rst | 20 |
1 files changed, 4 insertions, 16 deletions
diff --git a/api-merchant.rst b/api-merchant.rst index 8815e750..a0c4b938 100644 --- a/api-merchant.rst +++ b/api-merchant.rst @@ -17,6 +17,8 @@ @author Florian Dold @author Christian Grothoff +.. _merchant-api: + ============ Merchant API ============ @@ -70,7 +72,7 @@ The Frontent HTTP API // maximum fees merchant agreed to cover as per the contract max_fee: Amount; - // The merchant instance which is going to receive the final wire transfer. See paragraph `Merchant Instances` + // The merchant instance which is going to receive the final wire transfer. See :ref:`instances-lab` receiver: string; // signature by the merchant over the contract, must match signed data of purpose TALER_SIGNATURE_MERCHANT_CONTRACT @@ -227,7 +229,7 @@ The following API are made available by the merchant's `backend` to the merchant **Request:** :query id: ID of the transaction we want to trace (an integer) - :query receiver: identificative token for the merchant instance which is to be tracked (optional). See :ref:`instances`. + :query receiver: identificative token for the merchant instance which is to be tracked (optional). See :ref:`instances-lab`. This information is needed because the request has to be signed by the merchant, thus we need to pick the instance's private key. **Response:** @@ -285,20 +287,6 @@ Encodings Data such as dates, binary blobs, and other useful formats, are encoded as described in :ref:`encodings-ref`. -.. _instances: - ------------------------------------------- -Merchant Instances (To be moved elsewhere) ------------------------------------------- - -Any backend can account for multiple bank accounts, and we call `instance` or `receiver` (interchangeably) -any of those bank accounts. The backend needs that due to the ability we give to a merchant to route money -(he earns through Taler) to multiple bank accounts, depending on his will. For example, a donation shop using -Taler needs to know any bank account of any entity which is going to receive money through his website. That -happens because when the merchant deposits coins to the exchange, he must provide bank details to it about the -money receiver, see :ref:`deposit-par`. - - .. _contract: ------------------ |