taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit e32431b9b3c699d2009ea371d7f8ea394147716b
parent dbc12d37fc842f99f4ab951caaff9dadcb06a14b
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Mon, 16 Oct 2023 22:03:39 +0200

fix 2nd link (#7945)

Diffstat:
Mtaler-merchant-manual.rst | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst @@ -267,13 +267,13 @@ Transfers .. index:: wire transfer The Taler backend can be used to verify that the exchange correctly wired all -of the funds to the merchant. However, if no `Taler Bank Merchant HTTP API -<taler-bank-merchant-http-api>`_ was provided for the respective bank account, +of the funds to the merchant. However, if no :ref:`Taler Bank Revenue HTTP API +<taler-bank-merchant-http-api>` was provided for the respective bank account, the backend does not have access to the incoming wire transfers of the -merchant's bank account. In this case, merchants must manually provide the +merchant's bank account. In this case, merchants should manually provide the backend with wire *transfer* data that specifies the *wire transfer subject* and the amount that was received. Given this information, the backend can -detect and report any irregularities that might arise. +detect and report any irregularities that might arise. Rewards -------