summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMS <ms@taler.net>2021-01-05 19:11:19 +0100
committerMS <ms@taler.net>2021-01-05 19:11:19 +0100
commit816dee4cfb58658ac2c4dc1b8c19e1d61e359385 (patch)
tree8639e22436b1ad8ad1fb2c7d026c3eb38522577d
parent52acb9b8e905f80551a1a5eec0b0edc6412cbaec (diff)
downloaddocs-816dee4cfb58658ac2c4dc1b8c19e1d61e359385.tar.gz
docs-816dee4cfb58658ac2c4dc1b8c19e1d61e359385.tar.bz2
docs-816dee4cfb58658ac2c4dc1b8c19e1d61e359385.zip
note for Wire Gateway API
-rw-r--r--taler-exchange-manual.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 1d308522..5c314aee 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -81,6 +81,13 @@ currencies such as USD or EUR. Similarly, the Taler exchange must
interact with a bank. The bank of the exchange holds the exchange’s
funds in an escrow account.
+Note that, given the technical burden (XML-based communications,
+additional cryptography, and a vast variety of standards) due to
+interact with banks, the exchange uses a intermediary system to talk
+to its bank. Such intermediary system abstracts the native banking
+protocol by exposing the *Wire Gateway API*; this way, the exchange
+can conduct its banking operations in a simplified and JSON-based style.
+
When customers wire money to the escrow account, the bank notifies the
exchange about the incoming wire transfers. The exchange then creates a
*reserve* based on the subject of the wire transfer. The wallet which