note on #7365

1 files changed, 10 insertions, 3 deletions

diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index 6680cd88..720d5a82 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -4243,11 +4243,11 @@ KYC status updates
   Check or update KYC status of a particular payment target.
   Returns the current KYC status of the account and, if
   negative, returns the URL where the KYC process can be
-  initiated.  The REQUIREMENT_ROW must have been
+  initiated.  The ``$REQUIREMENT_ROW`` must have been
   returned previously from an exchange API endpoint that
-  determined that KYC was needed.  The H_PATYO must be
+  determined that KYC was needed.  The ``$H_PATYO`` must be
   the hash of the payto:// URI of the payment target.
-  The USERTYPE states whether the entity to perform
+  The ``$USERTYPE`` states whether the entity to perform
   the KYC is an "individual" or "business".
 
   **Request:**
@@ -4273,6 +4273,9 @@ KYC status updates
   :http:statuscode:`204 No content`:
     The exchange is not configured to perform KYC and thus
     generally all accounts are simply considered legitimate.
+  :http:statuscode:`402 Payment Required`:
+    The client must pay the KYC fee for the KYC process.
+    **This is currently not implemented, see #7365.**
   :http:statuscode:`403 Forbidden`:
     The provided hash does not match the payment target.
   :http:statuscode:`404 Not found`:
@@ -4428,6 +4431,10 @@ naturally expire and possibly (5) wire the funds to a designated account.
       // operation.
       payments: OpenPaymentDetail[];
 
+      // Amount to be paid from the reserve for this
+      // operation.
+      reserve_payment: Amount;
+
       // Time when the client made the request.
       // Timestamp must be reasonably close to the time of
       // the exchange, otherwise the exchange may reject