commit c2b0b6fc3ff00f6ccc814f3b5da33ebc4461c70b parent 0f7959da0e94659e72e114544ed8503a2e423664 Author: Christian Grothoff <christian@grothoff.org> Date: Sat, 24 Aug 2024 18:10:58 +0200 update spec for #9040 Diffstat:
| M | core/api-exchange.rst | | | 7 | ++++++- |
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -59,7 +59,7 @@ possibly by using HTTPS. as well as the list of possible KYC requirements. This endpoint is largely for the SPA for AML officers. Merchants should use ``/keys`` which also contains the protocol version and currency. - This specification corresponds to ``current`` protocol being **v20**. + This specification corresponds to ``current`` protocol being **v21**. **Response:** @@ -2721,6 +2721,11 @@ proof to the seller for the escrow of sufficient fund. `DenominationExpiredMessage`. Clients must evaluate the error code provided to understand which of the cases this is and handle it accordingly. + :http:statuscode:`451 Unavailable For Legal Reasons`: + This merchant has not yet passed the KYC checks. + The client must pass KYC checks before proceeding with the deposit. + The response will be an `LegitimizationNeededResponse` object. + Since protocol **v21**. **Details:**