taler-docs

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

commit b8cbb2c8fa7bdbeb7ed129d150e21c2f678892f5
parent c31719e2c873ed9f3a529ead33a83a9f75f583bb
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue, 12 Nov 2024 23:37:08 +0100

document implementation of #9217

Diffstat:
Mcore/api-merchant.rst | 22++++++++++++++++++++++
1 file changed, 22 insertions(+), 0 deletions(-)

diff --git a/core/api-merchant.rst b/core/api-merchant.rst @@ -1493,6 +1493,28 @@ KYC status checks interface MerchantAccountKycRedirect { + // Summary of the status of the KYC process. Possible values are: + // + // o "no-exchange-keys": we do not (yet) have the /keys of the exchange + // - "kyc-wire-impossible": KYC auth transfer needed but not possible + // @ "kyc-wire-required": KYC auth transfer still needed and possible + // @ "kyc-required": merchant must supply KYC data to proceed + // + "awaiting-aml-review": account under review by payment provider + // + "ready": everything is fine, account can be fully used + // - "logic-bug": merchant backend logic bug + // o "exchange-internal-error": exchange had an internal error + // o "exchange-gateway-timeout": network timeout at gateway + // o "exchange-unreachable": exchange did not respond at all + // - "exchange-status-invalid": exchange violated protocol in reply + // + // "+" are perfectly normal states, "@" are states where the user + // must performn an action (show link!); "o" are reasonable transient + // states that could happen and are we are expected to likely recover + // from automatically but that we should inform the user about + // (show in yellow?), "-" are hard error states from which + // there is likely no good automatic recovery from (show in red?). + status: string; + // Full payto URI of the bank wire account this is about. payto_uri: string;