summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--api-bank.rst6
-rw-r--r--api-common.rst28
-rw-r--r--api-merchant.rst26
-rw-r--r--api-mint.rst232
-rw-r--r--impl-merchant.rst14
-rw-r--r--impl-mint.rst42
-rw-r--r--index.rst16
-rw-r--r--integration-bank.rst10
-rw-r--r--integration-general.rst8
-rw-r--r--wireformats.rst6
10 files changed, 194 insertions, 194 deletions
diff --git a/api-bank.rst b/api-bank.rst
index 8d2d562..23e870d 100644
--- a/api-bank.rst
+++ b/api-bank.rst
@@ -2,9 +2,9 @@
Bank API
=========
-The following APIs are served from banks, in order to allow mints to
+The following APIs are served from banks, in order to allow exchanges to
deposit funds to money recipients. A typical scenario for calling this
-APIs is after a merchant has deposited coins to the mint, and the mint
+APIs is after a merchant has deposited coins to the exchange, and the exchange
needs to give real money to the merchant.
------------------
@@ -12,7 +12,7 @@ Administrative API
------------------
This is `local` API, meant to make the bank communicate with trusted entities,
-namely mints.
+namely exchanges.
.. _bank-deposit:
.. http:post:: /admin/add/incoming
diff --git a/api-common.rst b/api-common.rst
index 55083eb..e503a85 100644
--- a/api-common.rst
+++ b/api-common.rst
@@ -30,7 +30,7 @@ handle the error as if an internal error (500) had been returned.
:resheader Content-Type: application/json
:status 200: The request was successful.
:status 500 Internal server error:
- This always indicates some serious internal operational error of the mint,
+ This always indicates some serious internal operational error of the exchange,
such as a program bug, database problems, etc., and must not be used for
client-side problems. When facing an internal server error, clients should
retry their request after some delay. We recommended initially trying after
@@ -38,9 +38,9 @@ handle the error as if an internal error (500) had been returned.
informed and another three retries should be scheduled within the next 24h.
If the error persists, a report should ultimately be made to the auditor,
although the auditor API for this is not yet specified. However, as internal
- server errors are always reported to the mint operator, a good operator
+ server errors are always reported to the exchange operator, a good operator
should naturally be able to address them in a timely fashion, especially
- within 24h. When generating an internal server error, the mint responds with
+ within 24h. When generating an internal server error, the exchange responds with
a JSON object containing the following fields:
:status 400 Bad Request: One of the arguments to the request is missing or malformed.
@@ -274,15 +274,15 @@ uses 512-bit hash codes (64 bytes).
uint8_t ecdhe_priv[32];
};
- struct TALER_MintPublicKeyP {
+ struct TALER_ExchangePublicKeyP {
uint8_t eddsa_pub[32];
};
- struct TALER_MintPrivateKeyP {
+ struct TALER_ExchangePrivateKeyP {
uint8_t eddsa_priv[32];
};
- struct TALER_MintSignatureP {
+ struct TALER_ExchangeSignatureP {
uint8_t eddsa_signature[64];
};
@@ -393,7 +393,7 @@ size of `FIELDS`.
};
struct TALER_DepositConfirmationPS {
- signed (purpose = TALER_SIGNATURE_MINT_CONFIRM_DEPOSIT) {
+ signed (purpose = TALER_SIGNATURE_EXCHANGE_CONFIRM_DEPOSIT) {
struct GNUNET_HashCode h_contract;
struct GNUNET_HashCode h_wire;
uint64_t transaction_id GNUNET_PACKED;
@@ -415,24 +415,24 @@ size of `FIELDS`.
};
struct TALER_RefreshMeltConfirmationPS {
- signed (purpose = TALER_SIGNATURE_MINT_CONFIRM_MELT) {
+ signed (purpose = TALER_SIGNATURE_EXCHANGE_CONFIRM_MELT) {
struct GNUNET_HashCode session_hash;
uint16_t noreveal_index;
}
};
- struct TALER_MintSigningKeyValidityPS {
+ struct TALER_ExchangeSigningKeyValidityPS {
signed (purpose = TALER_SIGNATURE_MASTER_SIGNING_KEY_VALIDITY) {
struct TALER_MasterPublicKeyP master_public_key;
struct GNUNET_TIME_AbsoluteNBO start;
struct GNUNET_TIME_AbsoluteNBO expire;
struct GNUNET_TIME_AbsoluteNBO end;
- struct TALER_MintPublicKeyP signkey_pub;
+ struct TALER_ExchangePublicKeyP signkey_pub;
}
};
- struct TALER_MintKeySetPS {
- signed (purpose=TALER_SIGNATURE_MINT_KEY_SET) {
+ struct TALER_ExchangeKeySetPS {
+ signed (purpose=TALER_SIGNATURE_EXCHANGE_KEY_SET) {
struct GNUNET_TIME_AbsoluteNBO list_issue_date;
struct GNUNET_HashCode hc;
}
@@ -459,8 +459,8 @@ size of `FIELDS`.
}
};
- struct TALER_MintWireSupportMethodsPS {
- signed (purpose = TALER_SIGNATURE_MINT_WIRE_TYPES) {
+ struct TALER_ExchangeWireSupportMethodsPS {
+ signed (purpose = TALER_SIGNATURE_EXCHANGE_WIRE_TYPES) {
struct GNUNET_HashCode h_wire_types;
}
};
diff --git a/api-merchant.rst b/api-merchant.rst
index 72b7592..bcaf38e 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -57,7 +57,7 @@ The contract must have the following structure:
interface Contract {
// Total price for the transaction.
- // The mint will subtract deposit fees from that amount
+ // The exchange will subtract deposit fees from that amount
// before transfering it to the merchant.
amount: Amount;
@@ -104,18 +104,18 @@ The contract must have the following structure:
// The hash of the merchant's wire details.
H_wire: HashCode;
- // Any mints audited by these auditors are accepted by the merchant.
+ // Any exchanges audited by these auditors are accepted by the merchant.
auditors: Auditor[];
- // Mints that the merchant accepts even if it does not accept any auditors that audit them.
- mints: Mint[];
+ // Exchanges that the merchant accepts even if it does not accept any auditors that audit them.
+ exchanges: Exchange[];
// Map from label to a `Location`_.
// The label strings must not contain a colon (`:`).
locations: { [label: string]: Location>;
}
- The wallet must select a mint that either the mechant accepts directly by listing it in the mints arry, or for which the merchant accepts an auditor that audits that mint by listing it in the auditors array.
+ The wallet must select a exchange that either the mechant accepts directly by listing it in the exchanges arry, or for which the merchant accepts an auditor that audits that exchange by listing it in the auditors array.
The `product` object describes the product being purchased from the merchant. It has the following structure:
@@ -193,11 +193,11 @@ The contract must have the following structure:
.. code-block:: ts
- interface Mint {
- // the mint's base URL
+ interface Exchange {
+ // the exchange's base URL
url: string;
- // master public key of the mint
+ // master public key of the exchange
master_pub: EddsaPublicKey;
}
@@ -207,7 +207,7 @@ The contract must have the following structure:
When the contract is signed by the merchant or the wallet, the
signature is made over the hash of the JSON text, as the contract may
be confidential between merchant and customer and should not be
-exposed to the mint. The hashcode is generated by hashing the
+exposed to the exchange. The hashcode is generated by hashing the
encoding of the contract's JSON obtained by using the flags
``JSON_COMPACT | JSON_PRESERVE_ORDER``, as described in the `libjansson
documentation
@@ -264,7 +264,7 @@ merchant's offer.
:<json base32 merchant_sig: signature by the merchant over the contract, must match signed data of purpose TALER_SIGNATURE_MERCHANT_CONTRACT
:<json date timestamp: a timestamp of this deposit permission. It equals just the contract's timestamp
:<json date refund_deadline: same value held in the contract's `refund` field
- :<json string mint: the chosen mint's base URL
+ :<json string exchange: the chosen exchange's base URL
:<json array coins: the coins used to sign the contract
For each coin, the array contains the following information:
@@ -272,8 +272,8 @@ merchant's offer.
:<json amount f: the :ref:`amount <Amount>` this coin is paying, including this coin's deposit fee
:<json base32 coin_pub: the coin's public key
:<json base32 denom_pub: the denomination's (RSA public) key
- :<json base32 ub_sig: the mint's signature over this coin's public key
- :<json base32 coin_sig: the signature made by the coin's private key on a `struct TALER_DepositRequestPS`. See the :ref:`dedicated section <Signatures>` on the mint's specifications.
+ :<json base32 ub_sig: the exchange's signature over this coin's public key
+ :<json base32 coin_sig: the signature made by the coin's private key on a `struct TALER_DepositRequestPS`. See the :ref:`dedicated section <Signatures>` on the exchange's specifications.
**Success Response:**
@@ -281,7 +281,7 @@ merchant's offer.
**Failure Responses:**
- The error codes and data sent to the wallet are a mere copy of those gotten from the mint when attempting to pay. The section about :ref:`deposit <deposit>` explains them in detail.
+ The error codes and data sent to the wallet are a mere copy of those gotten from the exchange when attempting to pay. The section about :ref:`deposit <deposit>` explains them in detail.
.. http:post:: $exec_url
diff --git a/api-mint.rst b/api-mint.rst
index 99adfc7..ca91f75 100644
--- a/api-mint.rst
+++ b/api-mint.rst
@@ -1,20 +1,20 @@
=========================
-The Mint RESTful JSON API
+The Exchange RESTful JSON API
=========================
The API specified here follows the :ref:`general conventions <http-common>`
for all details not specified in the individual requests.
-------------------
-Obtaining Mint Keys
+Obtaining Exchange Keys
-------------------
This API is used by wallets and merchants to obtain global information about
-the mint, such as online signing keys, available denominations and the fee
-structure. This is typically the first call any mint client makes, as it
+the exchange, such as online signing keys, available denominations and the fee
+structure. This is typically the first call any exchange client makes, as it
returns information required to process all of the other interactions with the
-mint. The returned information is secured by (1) signature(s) from the mint,
-especially the long-term offline signing key of the mint, which clients should
+exchange. The returned information is secured by (1) signature(s) from the exchange,
+especially the long-term offline signing key of the exchange, which clients should
cache; (2) signature(s) from auditors, and the auditor keys should be
hard-coded into the wallet as they are the trust anchors for Taler; (3)
possibly by using HTTPS.
@@ -28,28 +28,28 @@ possibly by using HTTPS.
**Response:**
:status 200 OK:
- The mint responds with a `MintKeysResponse`_ object. This request should
+ The exchange responds with a `ExchangeKeysResponse`_ object. This request should
virtually always be successful.
**Details:**
- .. _MintKeysResponse:
+ .. _ExchangeKeysResponse:
.. code-block:: tsref
- interface MintKeysResponse {
- // EdDSA master public key of the mint, used to sign entries in `denoms` and `signkeys`
+ interface ExchangeKeysResponse {
+ // EdDSA master public key of the exchange, used to sign entries in `denoms` and `signkeys`
master_public_key: EddsaPublicKey;
- // Denomination offered by this mint.
+ // Denomination offered by this exchange.
denoms: Denom[];
// The date when the denomination keys were last updated.
list_issue_date: string;
- // Auditors of the mint.
+ // Auditors of the exchange.
auditors: Auditor[];
- // The mint's signing keys.
+ // The exchange's signing keys.
signkeys: SignKey[];
// compact EdDSA signature_ (binary-only) over the SHA-512 hash of the
@@ -57,14 +57,14 @@ possibly by using HTTPS.
// in `denoms` in the same order as they were in `denoms`. Note that for
// hashing, the binary format of the RSA public keys is used, and not their
// `base32 encoding <base32>`_. Wallets cannot do much with this signature by itself;
- // it is only useful when multiple clients need to establish that the mint
+ // it is only useful when multiple clients need to establish that the exchange
// is sabotaging end-user anonymity by giving disjoint denomination keys to
- // different users. If a mint were to do this, this signature allows the
- // clients to demonstrate to the public that the mint is dishonest.
+ // different users. If a exchange were to do this, this signature allows the
+ // clients to demonstrate to the public that the exchange is dishonest.
eddsa_sig: string;
- // Public EdDSA key of the mint that was used to generate the signature.
- // Should match one of the mint's signing keys from /keys. It is given
+ // Public EdDSA key of the exchange that was used to generate the signature.
+ // Should match one of the exchange's signing keys from /keys. It is given
// explicitly as the client might otherwise be confused by clock skew as to
// which signing key was used.
eddsa_pub: string;
@@ -85,25 +85,25 @@ possibly by using HTTPS.
stamp_expire_withdraw: Timestamp;
// Timestamp indicating by when legal disputes relating to these coins must
- // be settled, as the mint will afterwards destroy its evidence relating to
+ // be settled, as the exchange will afterwards destroy its evidence relating to
// transactions involving this coin.
stamp_expire_legal: Timestamp;
// Public (RSA) key for the denomination in base32 encoding.
denom_pub: string;
- // Fee charged by the mint for withdrawing a coin of this denomination
+ // Fee charged by the exchange for withdrawing a coin of this denomination
fee_withdraw: Amount;
- // Fee charged by the mint for depositing a coin of this denomination
+ // Fee charged by the exchange for depositing a coin of this denomination
fee_deposit: Amount;
- // Fee charged by the mint for refreshing a coin of this denomination
+ // Fee charged by the exchange for refreshing a coin of this denomination
fee_refresh: Amount;
// Signature with purpose
// `TALER_SIGNATURE_MASTER_DENOMINATION_KEY_VALIDITY` over the expiration
- // dates, value and the key, created with the mint's master key.
+ // dates, value and the key, created with the exchange's master key.
master_sig: EddsaSignature;
}
@@ -119,13 +119,13 @@ possibly by using HTTPS.
.. code-block:: tsref
interface SignKey {
- // The actual mint's EdDSA signing public key.
+ // The actual exchange's EdDSA signing public key.
key: EddsaPublicKey;
// Initial validity date for the signing key.
stamp_start: Timestamp;
- // Date when the mint will stop using the signing key, allowed to overlap
+ // Date when the exchange will stop using the signing key, allowed to overlap
// slightly with the next signing key's validity to allow for clock skew.
stamp_expire: Timestamp;
@@ -133,7 +133,7 @@ possibly by using HTTPS.
// henceforth no longer be considered valid in legal disputes.
stamp_end: Timestamp;
- // Signature over `key` and `stamp_expire` by the mint master key.
+ // Signature over `key` and `stamp_expire` by the exchange master key.
// Must have purpose TALER_SIGNATURE_MASTER_SIGNING_KEY_VALIDITY.
master_sig: EddsaSignature;
}
@@ -165,7 +165,7 @@ possibly by using HTTPS.
denom_pub_h: HashCode;
// A signature_ (binary-only) with purpose
- // `TALER_SIGNATURE_AUDITOR_MINT_KEYS` over the mint's public key and the
+ // `TALER_SIGNATURE_AUDITOR_EXCHANGE_KEYS` over the exchange's public key and the
// denomination key information. To verify the signature, the `denom_pub_h`
// must be resolved with the information from `denoms`
auditor_sig: EddsaSignature;
@@ -188,11 +188,11 @@ Obtaining wire-transfer information
.. http:get:: /wire
- Returns a list of payment methods supported by the mint. The idea is that wallets may use this information to instruct users on how to perform wire transfers to top up their wallets.
+ Returns a list of payment methods supported by the exchange. The idea is that wallets may use this information to instruct users on how to perform wire transfers to top up their wallets.
**Response:**
- :status 200: The mint responds with a `WireResponse`_ object. This request should virtually always be successful.
+ :status 200: The exchange responds with a `WireResponse`_ object. This request should virtually always be successful.
**Details:**
@@ -206,13 +206,13 @@ Obtaining wire-transfer information
methods: string[];
// the EdDSA signature_ (binary-only) with purpose
- // `TALER_SIGNATURE_MINT_PAYMENT_METHODS` signing over the hash over the
+ // `TALER_SIGNATURE_EXCHANGE_PAYMENT_METHODS` signing over the hash over the
// 0-terminated strings representing the payment methods in the same order
// as given in methods.
sig: EddsaSignature;
- // public EdDSA key of the mint that was used to generate the signature.
- // Should match one of the mint's signing keys from /keys. It is given
+ // public EdDSA key of the exchange that was used to generate the signature.
+ // Should match one of the exchange's signing keys from /keys. It is given
// explicitly as the client might otherwise be confused by clock skew as to
// which signing key was used.
pub: EddsaPublicKey;
@@ -222,21 +222,21 @@ Obtaining wire-transfer information
.. http:get:: /wire/test
The "test" payment method is for testing the system without using
- real-world currencies or actual wire transfers. If the mint operates
+ real-world currencies or actual wire transfers. If the exchange operates
in "test" mode, this request provides a redirect to an address where
the user can initiate a fake wire transfer for testing.
- :status 200: The mint responds with a `WireTestResponse`_ object. This request should virtually always be successful.
- :status 501: This wire transfer method is not supported by this mint.
+ :status 200: The exchange responds with a `WireTestResponse`_ object. This request should virtually always be successful.
+ :status 501: This wire transfer method is not supported by this exchange.
.. http:get:: /wire/sepa
- Provides instructions for how to transfer funds to the mint using the SEPA
- transfers. Always signed using the mint's long-term offline master public
+ Provides instructions for how to transfer funds to the exchange using the SEPA
+ transfers. Always signed using the exchange's long-term offline master public
key.
- :status 200: The mint responds with a `WireSepaResponse`_ object. This request should virtually always be successful.
- :status 501: This wire transfer method is not supported by this mint.
+ :status 200: The exchange responds with a `WireSepaResponse`_ object. This request should virtually always be successful.
+ :status 501: This wire transfer method is not supported by this exchange.
**Details:**
@@ -246,17 +246,17 @@ Obtaining wire-transfer information
.. code-block:: tsref
interface WireSepaResponse {
- // Legal name of the mint operator who is receiving the funds
+ // Legal name of the exchange operator who is receiving the funds
receiver_name: string;
- // IBAN account number for the mint
+ // IBAN account number for the exchange
iban: string;
- // BIC of the bank of the mint
+ // BIC of the bank of the exchange
bic: string;
// the EdDSA signature_ (binary-only) with purpose
- // `TALER_SIGNATURE_MINT_PAYMENT_METHOD_SEPA` signing over the hash over the
+ // `TALER_SIGNATURE_EXCHANGE_PAYMENT_METHOD_SEPA` signing over the hash over the
// 0-terminated strings representing the receiver's name, IBAN and the BIC.
sig: EddsaSignature;
}
@@ -268,16 +268,16 @@ Withdrawal
This API is used by the wallet to obtain digital coins.
-When transfering money to the mint such as via SEPA transfers, the mint creates
+When transfering money to the exchange such as via SEPA transfers, the exchange creates
a *reserve*, which keeps the money from the customer. The customer must
specify an EdDSA reserve public key as part of the transfer, and can then
withdraw digital coins using the corresponding private key. All incoming and
outgoing transactions are recorded under the corresponding public key by the
-mint.
+exchange.
.. note::
- Eventually the mint will need to advertise a policy for how long it will keep transaction histories for inactive or even fully drained reserves. We will therefore need some additional handler similar to `/keys` to advertise those terms of service.
+ Eventually the exchange will need to advertise a policy for how long it will keep transaction histories for inactive or even fully drained reserves. We will therefore need some additional handler similar to `/keys` to advertise those terms of service.
.. http:get:: /reserve/status
@@ -288,10 +288,10 @@ mint.
The client currently does not have to demonstrate knowledge of the private
key of the reserve to make this request, which makes the reserve's public
key privliged information known only to the client, their bank, and the
- mint. In future, we might wish to revisit this decision to improve
+ exchange. In future, we might wish to revisit this decision to improve
security, such as by having the client EdDSA-sign an ECDHE key to be used
to derive a symmetric key to encrypt the response. This would be useful if
- for example HTTPS were not used for communication with the mint.
+ for example HTTPS were not used for communication with the exchange.
**Request:**
@@ -300,8 +300,8 @@ mint.
**Response:**
:status 200 OK:
- The mint responds with a `ReserveStatus`_ object; the reserve was known to the mint,
- :status 404 Not Found: The withdrawal key does not belong to a reserve known to the mint.
+ The exchange responds with a `ReserveStatus`_ object; the reserve was known to the exchange,
+ :status 404 Not Found: The withdrawal key does not belong to a reserve known to the exchange.
**Details:**
@@ -362,12 +362,12 @@ mint.
coin is not lost.
:status 401 Unauthorized: The signature is invalid.
:status 404 Not Found:
- The denomination key or the reserve are not known to the mint. If the
+ The denomination key or the reserve are not known to the exchange. If the
denomination key is unknown, this suggests a bug in the wallet as the
wallet should have used current denomination keys from /keys. If the
reserve is unknown, the wallet should not report a hard error yet, but
instead simply wait for up to a day, as the wire transaction might simply
- not yet have completed and might be known to the mint in the near future.
+ not yet have completed and might be known to the exchange in the near future.
In this case, the wallet should repeat the exact same request later again
using exactly the same blinded coin.
:status 402 Payment Required:
@@ -382,10 +382,10 @@ mint.
interface WithdrawRequest {
// Denomination public key (RSA), specifying the type of coin the client
- // would like the mint to create.
+ // would like the exchange to create.
denom_pub: RsaPublicKey;
- // coin's blinded public key, should be (blindly) signed by the mint's
+ // coin's blinded public key, should be (blindly) signed by the exchange's
// denomination private key
coin_ev: CoinEnvelope;
@@ -440,7 +440,7 @@ denomination.
.. _deposit:
.. http:POST:: /deposit
- Deposit the given coin and ask the mint to transfer the given :ref:`amount`
+ Deposit the given coin and ask the exchange to transfer the given :ref:`amount`
to the merchants bank account. This API is used by the merchant to redeem
the digital coins. The request should contain a JSON object with the
following fields:
@@ -450,7 +450,7 @@ denomination.
**Response:**
:status 200:
- The operation succeeded, the mint confirms that no double-spending took place.
+ The operation succeeded, the exchange confirms that no double-spending took place.
:status 401 Unauthorized:
One of the signatures is invalid.
:status 403:
@@ -472,7 +472,7 @@ denomination.
f: Amount;
// The merchant's account details. This must be a JSON object whose format
- // must correspond to one of the supported wire transfer formats of the mint.
+ // must correspond to one of the supported wire transfer formats of the exchange.
// See `wireformats`_.
wire: WireFormat;
@@ -481,7 +481,7 @@ denomination.
H_wire: HashCode;
// SHA-512 hash of the contact of the merchant with the customer. Further
- // details are never disclosed to the mint.
+ // details are never disclosed to the exchange.
H_contract: HashCode;
// coin's public key, both ECDHE and EdDSA.
@@ -490,14 +490,14 @@ denomination.
// denomination RSA key with which the coin is signed
denom_pub: RsaPublicKey;
- // mint's unblinded RSA `signature`_ of the coin
+ // exchange's unblinded RSA `signature`_ of the coin
ub_sig: RsaSignature;
// timestamp when the contract was finalized, must match approximately the
- // current time of the mint
+ // current time of the exchange
timestamp: Timestamp;
- // indicative time by which the mint undertakes to transfer the funds to
+ // indicative time by which the exchange undertakes to transfer the funds to
// the merchant, in case of successful payment.
edate: Timestamp;
@@ -509,7 +509,7 @@ denomination.
merchant_pub: EddsaPublicKey;
// date until which the merchant can issue a refund to the customer via the
- // mint, possibly zero if refunds are not allowed.
+ // exchange, possibly zero if refunds are not allowed.
refund_deadline: Timestamp;
// The EdDSA signature (binary-only) made with purpose
@@ -529,14 +529,14 @@ denomination.
status: string;
// the EdDSA :ref:`signature` (binary-only) with purpose
- // `TALER_SIGNATURE_MINT_CONFIRM_DEPOSIT` using a current signing key of the
- // mint affirming the successful deposit and that the mint will transfer the
+ // `TALER_SIGNATURE_EXCHANGE_CONFIRM_DEPOSIT` using a current signing key of the
+ // exchange affirming the successful deposit and that the exchange will transfer the
// funds after the refund deadline, or as soon as possible if the refund
// deadline is zero.
sig: EddsaSignature;
- // public EdDSA key of the mint that was used to generate the signature.
- // Should match one of the mint's signing keys from /keys. It is given
+ // public EdDSA key of the exchange that was used to generate the signature.
+ // Should match one of the exchange's signing keys from /keys. It is given
// explicitly as the client might otherwise be confused by clock skew as to
// which signing key was used.
pub: EddsaPublicKey;
@@ -582,20 +582,20 @@ Refreshing
Refreshing creates `n` new coins from `m` old coins, where the sum of
denominations of the new coins must be smaller than the sum of the old coins'
-denominations plus melting (refresh) and withdrawal fees charged by the mint.
+denominations plus melting (refresh) and withdrawal fees charged by the exchange.
The refreshing API can be used by wallets to melt partially spent coins, making
-transactions with the freshly minted coins unlinkabe to previous transactions
+transactions with the freshly exchangeed coins unlinkabe to previous transactions
by anyone except the wallet itself.
However, the new coins are linkable from the private keys of all old coins
using the /refresh/link request. While /refresh/link must be implemented by
-the mint to achieve taxability, wallets do not really ever need that part of
+the exchange to achieve taxability, wallets do not really ever need that part of
the API during normal operation.
.. _refresh:
.. http:post:: /refresh/melt
- "Melts" coins. Invalidates the coins and prepares for minting of fresh
+ "Melts" coins. Invalidates the coins and prepares for exchangeing of fresh
coins. Taler uses a global parameter `kappa` for the cut-and-choose
component of the protocol, for which this request is the commitment. Thus,
various arguments are given `kappa`-times in this step. At present `kappa`
@@ -610,7 +610,7 @@ the API during normal operation.
The operation is not allowed as at least one of the coins has insufficient funds. The response
is `MeltForbiddenResponse`_ in this case.
:status 404:
- the mint does not recognize the denomination key as belonging to the mint,
+ the exchange does not recognize the denomination key as belonging to the exchange,
or it has expired
**Details:**
@@ -663,7 +663,7 @@ the API during normal operation.
// Coin public key, uniquely identifies the coin
coin_pub: string;
- // The denomination public key allows the mint to determine total coin value.
+ // The denomination public key allows the exchange to determine total coin value.
denom_pub: RsaPublicKey;
// Signature over the coin public key by the denomination.
@@ -693,16 +693,16 @@ the API during normal operation.
// Which of the `kappa` indices does the client not have to reveal.
noreveal_index: number;
- // binary-only Signature_ for purpose `TALER_SIGNATURE_MINT_CONFIRM_MELT`
- // whereby the mint affirms the successful melt and confirming the
+ // binary-only Signature_ for purpose `TALER_SIGNATURE_EXCHANGE_CONFIRM_MELT`
+ // whereby the exchange affirms the successful melt and confirming the
// `noreveal_index`
- mint_sig: EddsaSignature;
+ exchange_sig: EddsaSignature;
- // public EdDSA key of the mint that was used to generate the signature.
- // Should match one of the mint's signing keys from /keys. Again given
+ // public EdDSA key of the exchange that was used to generate the signature.
+ // Should match one of the exchange's signing keys from /keys. Again given
// explicitly as the client might otherwise be confused by clock skew as to
// which signing key was used.
- mint_pub: EddsaPublicKey;
+ exchange_pub: EddsaPublicKey;
}
@@ -735,8 +735,8 @@ the API during normal operation.
.. http:post:: /refresh/reveal
- Reveal previously commited values to the mint, except for the values
- corresponding to the `noreveal_index` returned by the /mint/melt step.
+ Reveal previously commited values to the exchange, except for the values
+ corresponding to the `noreveal_index` returned by the /exchange/melt step.
Request body contains a JSON object with the following fields:
@@ -755,14 +755,14 @@ the API during normal operation.
.. code-block:: tsref
interface RevealRequest {
- // Hash over most of the arguments to the /mint/melt step. Used to
+ // Hash over most of the arguments to the /exchange/melt step. Used to
// identify the corresponding melt operation. For details on which elements
- // must be hashed in which order, please consult the source code of the mint
+ // must be hashed in which order, please consult the source code of the exchange
// reference implementation.
session_hash: HashCode;
// 2D array of `kappa - 1` times number of melted coins ECDHE transfer
- // private keys. The mint will use those to decrypt the transfer secrets,
+ // private keys. The exchange will use those to decrypt the transfer secrets,
// check that they match across all coins, and then decrypt the private keys
// of the coins to be generated and check all this against the commitments.
transfer_privs: EddsaPrivateKey[][];
@@ -773,7 +773,7 @@ the API during normal operation.
.. code-block:: tsref
interface RevealResponse {
- // List of the mint's blinded RSA signatures on the new coins. Each
+ // List of the exchange's blinded RSA signatures on the new coins. Each
// element in the array is another JSON object which contains the signature
// in the "ev_sig" field.
ev_sigs: BlindedRsaSignature[];
@@ -800,7 +800,7 @@ the API during normal operation.
oldcoin_infos: OldCoinInfo[];
// array with RSA denomination public keys of the coins the original
- // refresh request asked to be minted
+ // refresh request asked to be exchangeed
newcoins_infos: RsaPublicKey[];
// 2D array with `kappa` entries in the first dimension and the same
@@ -842,7 +842,7 @@ the API during normal operation.
.. http:get:: /refresh/link
- Link the old public key of a melted coin to the coin(s) that were minted during the refresh operation.
+ Link the old public key of a melted coin to the coin(s) that were exchangeed during the refresh operation.
**Request:**
@@ -851,11 +851,11 @@ the API during normal operation.
**Response:**
:status 200 OK:
- All commitments were revealed successfully. The mint returns an array,
+ All commitments were revealed successfully. The exchange returns an array,
typically consisting of only one element, in which each each element contains
information about a melting session that the coin was used in.
:status 404 Not Found:
- The mint has no linkage data for the given public key, as the coin has not
+ The exchange has no linkage data for the given public key, as the coin has not
yet been involved in a refresh operation.
**Details:**
@@ -874,7 +874,7 @@ the API during normal operation.
secret_enc: Base32;
// array with (encrypted/blinded) information for each of the coins
- // minted in the refresh operation.
+ // exchangeed in the refresh operation.
new_coins: NewCoinInfo[];
}
@@ -885,10 +885,10 @@ the API during normal operation.
// Encrypted private key and blinding factor information of the fresh coin
link_enc: Base32;
- // RSA public key of the minted coin.
+ // RSA public key of the exchangeed coin.
denom_pub: RsaPublicKey;
- // Mint's blinded signature over the minted coin.
+ // Exchange's blinded signature over the exchangeed coin.
ev_sig: BlindedRsaSignature;
}
@@ -900,7 +900,7 @@ Tracking wire transfers
-----------------------
This API is used by merchants that need to find out which wire
-transfers (from the mint to the merchant) correspond to which deposit
+transfers (from the exchange to the merchant) correspond to which deposit
operations. Typically, a merchant will receive a wire transfer with a
**wire transfer identifier** and want to know the set of deposit
operations that correspond to this wire transfer. This is the
@@ -941,10 +941,10 @@ typically also view the balance.)
**Response:**
:status 200 OK:
- The wire transfer is known to the mint, details about it follow in the body.
+ The wire transfer is known to the exchange, details about it follow in the body.
The body of the response is a `WireDepositsResponse`_.
:status 404 Not Found:
- The wire transfer identifier is unknown to the mint.
+ The wire transfer identifier is unknown to the exchange.
.. _WireDepositsResponse:
.. code-block:: tsref
@@ -985,7 +985,7 @@ typically also view the balance.)
}
.. note::
- We might want to add a signature of the mint over the response in the future. That way, a merchant has proof should a mint ever try to change the story here. (#4135)
+ We might want to add a signature of the exchange over the response in the future. That way, a merchant has proof should a exchange ever try to change the story here. (#4135)
.. http:post:: /deposit/wtid
@@ -997,15 +997,15 @@ typically also view the balance.)
**Response:**
:status 200 OK:
- The deposit has been executed by the mint and we have a wire transfer identifier.
+ The deposit has been executed by the exchange and we have a wire transfer identifier.
The response body is a `WtidResponse`_ object.
:status 202 Accepted:
The deposit request has been accepted for processing, but was not yet
- executed. Hence the mint does not yet have a wire transfer identifier. The
+ executed. Hence the exchange does not yet have a wire transfer identifier. The
merchant should come back later and ask again.
The response body is a `WtidAcceptedResponse`_.
:status 401 Unauthorized: The signature is invalid.
- :status 404 Not Found: The deposit operation is unknown to the mint
+ :status 404 Not Found: The deposit operation is unknown to the exchange
**Details:**
@@ -1054,15 +1054,15 @@ typically also view the balance.)
// Total amount transferred
total_amount: Amount;
- // binary-only Signature_ for purpose `TALER_SIGNATURE_MINT_CONFIRM_WIRE`
- // whereby the mint affirms the successful wire transfer.
- mint_sig: EddsaSignature;
+ // binary-only Signature_ for purpose `TALER_SIGNATURE_EXCHANGE_CONFIRM_WIRE`
+ // whereby the exchange affirms the successful wire transfer.
+ exchange_sig: EddsaSignature;
- // public EdDSA key of the mint that was used to generate the signature.
- // Should match one of the mint's signing keys from /keys. Again given
+ // public EdDSA key of the exchange that was used to generate the signature.
+ // Should match one of the exchange's signing keys from /keys. Again given
// explicitly as the client might otherwise be confused by clock skew as to
// which signing key was used.
- mint_pub: EddsaPublicKey;
+ exchange_pub: EddsaPublicKey;
}
.. _tsref-type-WtidAcceptedResponse:
@@ -1070,7 +1070,7 @@ typically also view the balance.)
.. code-block:: tsref
interface WtidAcceptedResponse {
- // time by which the mint currently thinks the deposit will be executed.
+ // time by which the exchange currently thinks the deposit will be executed.
execution_time: Timestamp;
}
@@ -1114,11 +1114,11 @@ Administrative API: Key update
This is not yet implemented (no bug number yet, as we are not sure we will
implement this; for now, adding new files to the directory and sending a
- signal to the mint process seems to work fine).
+ signal to the exchange process seems to work fine).
-New denomination and signing keys can be uploaded to the mint via the
+New denomination and signing keys can be uploaded to the exchange via the
HTTP interface. It is, of course, only possible to upload keys signed
-by the mint's master key. Furthermore, this API should probably only
+by the exchange's master key. Furthermore, this API should probably only
be used via loopback, as we want to protect the private keys from
interception.
@@ -1163,7 +1163,7 @@ Administrative API: Bank transactions
.. http:POST:: /admin/add/incoming
- Notify mint of an incoming transaction to fill a reserve.
+ Notify exchange of an incoming transaction to fill a reserve.
**Request:**
@@ -1204,9 +1204,9 @@ Administrative API: Bank transactions
.. http:POST:: /admin/add/outgoing
- Notify mint about the completion of an outgoing transaction satisfying a
+ Notify exchange about the completion of an outgoing transaction satisfying a
/deposit request. In the future, this will allow merchants to obtain details
- about the /deposit requests they send to the mint.
+ about the /deposit requests they send to the exchange.
.. note::
@@ -1248,10 +1248,10 @@ Administrative API: Bank transactions
The Test API
------------
-The test API is not there to test the mint, but to allow
-clients of the mint (merchant and wallet implementations)
+The test API is not there to test the exchange, but to allow
+clients of the exchange (merchant and wallet implementations)
to test if their implemenation of the cryptography is
-binary-compatible with the implementation of the mint.
+binary-compatible with the implementation of the exchange.
.. http:POST:: /test/base32
@@ -1371,7 +1371,7 @@ binary-compatible with the implementation of the mint.
:status 200: the signature was valid
:status 401 Unauthorized: the signature was invalid
- The mint responds with another valid signature, which gives the
+ The exchange responds with another valid signature, which gives the
client the opportunity to test its signature verification implementation.
.. code-block:: tsref
@@ -1380,7 +1380,7 @@ binary-compatible with the implementation of the mint.
// Another EdDSA public key
eddsa_pub: EddsaPublicKey;
- // EdDSA signature using purpose TALER_SIGNATURE_MINT_TEST_EDDSA
+ // EdDSA signature using purpose TALER_SIGNATURE_EXCHANGE_TEST_EDDSA
eddsa_sig: EddsaSignature;
}
diff --git a/impl-merchant.rst b/impl-merchant.rst
index 28bfc76..0218426 100644
--- a/impl-merchant.rst
+++ b/impl-merchant.rst
@@ -18,7 +18,7 @@ one of those is trivial.
The `backend` is a standalone C application intended to implement all
the cryptographic routines required to interact with the Taler wallet
-and a Taler mint.
+and a Taler exchange.
@@ -76,7 +76,7 @@ The following API are made available by the merchant's `backend` to the merchant
The `proposition` that is to be sent from the frontend is a `contract` object without the fields
* `merchant_pub`
- * `mints`
+ * `exchanges`
* `H_wire`
The `backend` then completes this information based on its configuration.
@@ -94,7 +94,7 @@ The following API are made available by the merchant's `backend` to the merchant
.. http:post:: /pay
- Asks the `backend` to execute the transaction with the mint and deposit the coins.
+ Asks the `backend` to execute the transaction with the exchange and deposit the coins.
**Request:**
@@ -106,15 +106,15 @@ The following API are made available by the merchant's `backend` to the merchant
**Response:**
:status 200 OK:
- The mint accepted all of the coins. The `frontend` should now fullfill the
+ The exchange accepted all of the coins. The `frontend` should now fullfill the
contract. This response has no meaningful body, the frontend needs to
generate the fullfillment page.
:status 400 Precondition failed:
- The given mint is not acceptable for this merchant, as it is not in the
- list of accepted mints and not audited by an approved auditor.
+ The given exchange is not acceptable for this merchant, as it is not in the
+ list of accepted exchanges and not audited by an approved auditor.
- The `backend` will return verbatim the error codes received from the mint's
+ The `backend` will return verbatim the error codes received from the exchange's
:ref:`deposit <deposit>` API. If the wallet made a mistake, like by
double-spending for example, the `frontend` should pass the reply verbatim to
the browser/wallet. This should be the expected case, as the `frontend`
diff --git a/impl-mint.rst b/impl-mint.rst
index 21eb9d3..1757464 100644
--- a/impl-mint.rst
+++ b/impl-mint.rst
@@ -1,25 +1,25 @@
===================================
-The Mint Reference Implementation
+The Exchange Reference Implementation
===================================
----------------------
The Configuration File
----------------------
-The section `[mint]` contains various global options for the mint:
+The section `[exchange]` contains various global options for the exchange:
-* `master_public_key`: Must specify the mint's master public key.
-* `wireformat`: The wireformat supported by the mint (i.e. "SEPA")
-* `currency`: The currency supported by the mint (i.e. "EUR")
+* `master_public_key`: Must specify the exchange's master public key.
+* `wireformat`: The wireformat supported by the exchange (i.e. "SEPA")
+* `currency`: The currency supported by the exchange (i.e. "EUR")
^^^^^^^^^^^^^^^^^^^^^^
SEPA accounts
^^^^^^^^^^^^^^^^^^^^^^
-The command line tool `taler-mint-sepa` is used to create a file with
-the JSON response to /wire/sepa requests using the mint's offline
-master key. This file needs to be created and added to the configuration under SEPA_RESPONSE_FILE in section [mint-wire-sepa] when the
+The command line tool `taler-exchange-sepa` is used to create a file with
+the JSON response to /wire/sepa requests using the exchange's offline
+master key. This file needs to be created and added to the configuration under SEPA_RESPONSE_FILE in section [exchange-wire-sepa] when the
`wireformat` option in the configuration file allows SEPA transactions.
@@ -27,23 +27,23 @@ master key. This file needs to be created and added to the configuration under
Key Management Options
^^^^^^^^^^^^^^^^^^^^^^
-The command line tool `taler-mint-keyup` updates the signing key and list of denominations offered by the mint. This process requires the mint's master key, and should be done offline in order to protect the master key. For this, `taler-mint-keyup` uses additional configuration options.
+The command line tool `taler-exchange-keyup` updates the signing key and list of denominations offered by the exchange. This process requires the exchange's master key, and should be done offline in order to protect the master key. For this, `taler-exchange-keyup` uses additional configuration options.
-The section `[mint_keys]` containts the following entries:
+The section `[exchange_keys]` containts the following entries:
* `signkey_duration`: How long should one signing key be used?
* `lookahead_sign`: For how far into the future should keys be issued? This determines the frequency
of offline signing with the master key.
-* `lookahead_provide`: How far into the future should the mint provide keys? This determines the attack
+* `lookahead_provide`: How far into the future should the exchange provide keys? This determines the attack
window on keys.
Sections specifying denomination (coin) information start with "coin\_". By convention, the name continues with "$CURRENCY_[$SUBUNIT]_$VALUE", i.e. "[coin_eur_ct_10] for a 10 cent piece. However, only the "coin\_" prefix is mandatory. Each "coin\_"-section must then have the following options:
* `value`: How much is the coin worth, the format is CURRENCY:VALUE.FRACTION. For example, a 10 cent piece is "EUR:0.10".
-* `duration_withdraw`: How long can a coin of this type be withdrawn? This limits the losses incured by the mint when a denomination key is compromised.
+* `duration_withdraw`: How long can a coin of this type be withdrawn? This limits the losses incured by the exchange when a denomination key is compromised.
* `duration_overlap`: What is the overlap of the withdrawal timespan for this coin type?
-* `duration_spend`: How long is a coin of the given type valid? Smaller values result in lower storage costs for the mint.
+* `duration_spend`: How long is a coin of the given type valid? Smaller values result in lower storage costs for the exchange.
* `fee_withdraw`: What does it cost to withdraw this coin? Specified using the same format as `value`.
* `fee_deposit`: What does it cost to deposit this coin? Specified using the same format as `value`.
* `fee_refresh`: What does it cost to refresh this coin? Specified using the same format as `value`.
@@ -54,9 +54,9 @@ Sections specifying denomination (coin) information start with "coin\_". By con
Reserve management
------------------
-Incoming transactions to the mint's provider result in the creation or update of reserves, identified by their withdrawal key.
+Incoming transactions to the exchange's provider result in the creation or update of reserves, identified by their withdrawal key.
-The command line tool `taler-mint-reservemod` allows create and add money to reserves in the mint's database.
+The command line tool `taler-exchange-reservemod` allows create and add money to reserves in the exchange's database.
-------------------
@@ -87,7 +87,7 @@ Database Scheme
expiration INT8,
-- The blinding key (public part) for the purse, can be NULL
- -- if funds are insufficient or the mint has not
+ -- if funds are insufficient or the exchange has not
-- generated it yet.
blinding_pub BYTEA,
@@ -117,7 +117,7 @@ Database Scheme
-- The coin blank provided by the customer.
blind_blank_coin BYTEA,
- -- Signature over the minting request by the customer.
+ -- Signature over the exchangeing request by the customer.
customer_sig BYTEA,
-- The signed blind blank coin.
@@ -127,13 +127,13 @@ Database Scheme
-- blind signed coin.
denom_pub BYTEA,
- -- The purse that requested the minting of this
+ -- The purse that requested the exchangeing of this
-- coin.
withdraw_pub BYTEA REFERENCES purses(withdraw_pub)
);
-The table `coins` stores information about coins known to the mint.
+The table `coins` stores information about coins known to the exchange.
.. sourcecode:: postgres
@@ -198,7 +198,7 @@ The following tables are used for refreshing.
idx INTEGER,
coin_link_enc BYTEA,
-- The blinding key (public part) for the purse, can be NULL
- -- if funds are insufficient or the mint has not
+ -- if funds are insufficient or the exchange has not
-- generated it yet.
blinding_pub BYTEA,
@@ -215,7 +215,7 @@ The following tables are used for refreshing.
Key Storage Format
------------------
-The mint's key directory contains the two subdirectories `signkeys` and `coinkeys`.
+The exchange's key directory contains the two subdirectories `signkeys` and `coinkeys`.
The directory `signkeys` contains signkey files, where the name is the start date of the respective key.
diff --git a/index.rst b/index.rst
index f8b938e..f2c0386 100644
--- a/index.rst
+++ b/index.rst
@@ -3,21 +3,21 @@ GNU Taler Documentation
We are building an anonymous, taxable payment system using modern
cryptography. Customers will use traditional money transfers to send
-money to a digital Mint and in return receive (anonymized) digital
+money to a digital Exchange and in return receive (anonymized) digital
cash. Customers can use this digital cash to anonymously pay
Merchants. Merchants can redeem the digital cash for traditional
-money at the digital Mint. As Merchants are not anonymous, they can
+money at the digital Exchange. As Merchants are not anonymous, they can
be taxed, enabling income or sales taxes to be withheld by the state
while providing anonymity for Customers.
Cryptography is used to ensure that none of the participants can
defraud the others without being detected immediately; however, in
-practice a fradulent Mint might go bankrupt instead of paying the
-Merchants and thus the Mint will need to be audited regularly like any
+practice a fradulent Exchange might go bankrupt instead of paying the
+Merchants and thus the Exchange will need to be audited regularly like any
other banking institution.
The system will be based on free software and open protocols.
-In this document, we describe the REST-based API of the Mint,
+In this document, we describe the REST-based API of the Exchange,
which is at the heart of the system.
@@ -25,13 +25,13 @@ which is at the heart of the system.
Operator Handbook
-----------------
-The *Operator Handbook* is for people who want to run a mint or a merchant.
+The *Operator Handbook* is for people who want to run a exchange or a merchant.
It focuses on how to install, configure and run the required software.
.. toctree::
:maxdepth: 2
- impl-mint
+ impl-exchange
impl-merchant
@@ -64,7 +64,7 @@ interfaces between the core components of Taler.
:maxdepth: 2
api-common
- api-mint
+ api-exchange
api-merchant
api-bank
diff --git a/integration-bank.rst b/integration-bank.rst
index 348f70a..b51ca0c 100644
--- a/integration-bank.rst
+++ b/integration-bank.rst
@@ -18,24 +18,24 @@ Reserve Creation Request
-------------------------
The bank website can request the creation of a :term:`reserve`. This operation
-will require the user to specify the mint where he wants to create the reserve
+will require the user to specify the exchange where he wants to create the reserve
and the resolution of a CAPTCHA, before any action will be taken.
As a result of the reserve creation request, the following steps will happen in sequence:
1. The user chooses the desired amount from the bank's form
2. Upon confirmation, the wallet fetches the desired amount from the user-filled form and
- prompts the user for the *mint base URL*. Then ask the user to confirm creating the
+ prompts the user for the *exchange base URL*. Then ask the user to confirm creating the
reserve.
2. The wallet will create a key pair for the reserve.
3. The wallet will request the CAPTCHA page to the bank. In that request's parameters it
- communicates the desired amount, the reserve's public key and the mint base URL to the
+ communicates the desired amount, the reserve's public key and the exchange base URL to the
bank
4. Upon successful resolution of the CAPTCHA by the user, the bank initiates the reserve
creation according to the gotten parameters. Together with `200 OK` status code sent back
to the wallet, it gets also a `ReserveCreated`_ object.
Note that the reserve creation can be done by a SEPA wire transfer or some other means,
-depending on the user's bank and chosen mint.
+depending on the user's bank and chosen exchange.
In response to the reserve creation request, the Taler wallet MAY cause the
current document location to be changed, in order to navigate to a
@@ -60,7 +60,7 @@ The event data must be a `CreateReserveDetail`_:
// amount_fraction
// amount_currency
// reserve_pub
- // mint
+ // exchange
callback_url: string;
// list of wire transfer types supported by the bank
diff --git a/integration-general.rst b/integration-general.rst
index 5e5c156..fc8f0d6 100644
--- a/integration-general.rst
+++ b/integration-general.rst
@@ -57,7 +57,7 @@ Events can be received by installing a listener:
Normalized Base URLs
--------------------
-Mints and merchants have a base URL for their service. This URL *must* be in a
+Exchanges and merchants have a base URL for their service. This URL *must* be in a
canonical form when it is stored (e.g. in the wallet's database) or transmitted
(e.g. to a bank page).
@@ -65,10 +65,10 @@ canonical form when it is stored (e.g. in the wallet's database) or transmitted
2. The path component of the URL must end with a slash.
3. The URL must not contain a fragment or query.
-When a user enters a URL that is, technically, relative (such as "alice.example.com/mint"), wallets
-*may* transform it into a canonical base URL ("http://alice.example.com/mint/"). Other components *should not* accept
+When a user enters a URL that is, technically, relative (such as "alice.example.com/exchange"), wallets
+*may* transform it into a canonical base URL ("http://alice.example.com/exchange/"). Other components *should not* accept
URLs that are not canonical.
-Rationale: Joining non-canonical URLs with relative URLs (e.g. "mint.example.com" with "reserve/status")
+Rationale: Joining non-canonical URLs with relative URLs (e.g. "exchange.example.com" with "reserve/status")
results in different and slightly unexpected behavior in some URL handling libraries.
Canonical URLs give more predictable results with standard URL joining.
diff --git a/wireformats.rst b/wireformats.rst
index 8a72da0..1c096ac 100644
--- a/wireformats.rst
+++ b/wireformats.rst
@@ -3,14 +3,14 @@
Wire Transfer Formats
=====================
-A wire transfer is essential for the mint to transfer funds into a merchant's
+A wire transfer is essential for the exchange to transfer funds into a merchant's
account upon a successful deposit (see :ref:`deposit request <deposit>`). The
-merchant has to include the necessary information for the mint to initiate the
+merchant has to include the necessary information for the exchange to initiate the
wire transfer.
The information required for wire transfer depends on the type of wire transfer
used. Since the wire transfers differ for each region, we document here the
-ones currently supported by the mint.
+ones currently supported by the exchange.
TEST
----