commit d13c3cb6a5a7a2da100c0479a38ffe9d1df5fe2c parent a864b45f2454038b7a6055b6b44c53bfc5b2f6f4 Author: Christian Grothoff <christian@grothoff.org> Date: Thu, 7 Mar 2024 10:27:37 +0100 fix name Diffstat:
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/core/api-corebank.rst b/core/api-corebank.rst @@ -83,7 +83,7 @@ Config // The format is "current:revision:age". version: string; - // Bank display name to be used in user interfaces. + // Bank display name to be used in user interfaces. // For consistency use "Taler Bank" if missing. // @since v4, will become mandatory in the next version. bank_name?: string; @@ -175,7 +175,7 @@ Account Management cashout_payto_uri?: string; // Internal payto URI of this bank account. - // Used mostly for testing, this field is ignored if the bank payment + // Used mostly for testing, this field is ignored if the bank payment // method is not IBAN. payto_uri?: string; @@ -507,7 +507,7 @@ Account Management // as well. contact_data?: ChallengeContactData; - // IBAN 'payto' URI with a 'receiver-name' parameter of a fiat bank + // IBAN 'payto' URI with a 'receiver-name' parameter of a fiat bank // account where to send cashouts. This field is optional // because not all the accounts are required to participate // in the merchants' circuit. One example is the exchange: @@ -831,7 +831,7 @@ Cashouts :http:statuscode:`200 OK`: The cashout request was correctly created. - This returns the `CashoutPending` response. + This returns the `CashoutResponse` response. :http:statuscode:`202 Accepted`: 2FA is required for this operation. This returns the `Challenge` response. :http:statuscode:`404 Not found`: diff --git a/kyc-process.pdf b/images/kyc-process.pdf Binary files differ. diff --git a/kyc-process.png b/images/kyc-process.png Binary files differ. diff --git a/kyc-process.tex b/images/kyc-process.tex diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst @@ -978,7 +978,7 @@ Taler permits an exchange to require KYC data under the following circumstances: Any of the above requests can trigger the KYC process, which can be illustrated as follows: -.. image:: kyc-process.png +.. image:: images/kyc-process.png At the end of the KYC process, the wallet re-tries the original request, and assuming KYC was successful, the
