commit c7823c6929be3c4b4f61bc07266ee32be0dd027d parent 179c07b75471025ed89f14a51650f2632723a537 Author: Christian Grothoff <christian@grothoff.org> Date: Tue, 3 Jun 2025 20:36:38 +0200 document API change for #9890 Diffstat:
| M | core/api-exchange.rst | | | 12 | +++++++++++- |
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -60,7 +60,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 **v27**. + This specification corresponds to ``current`` protocol being **v28**. **Response:** @@ -5237,6 +5237,16 @@ and freeze or unfreeze accounts suspected of money laundering. // Available KYC checks. checks: { "$check_name" : KycCheckInformation; }; + // Default KYC rules. This is the set of KYC rules that + // applies by default to new "accounts". Note that some + // rules only apply to wallets, while others only apply to + // bank accounts. The returned array is the union of all + // possible rules, applications should consider the + // ``operation_type`` to filter for rules that actually + // apply to a specific situation. + // @since protocol **v28**. + default_rules: KycRule[]; + } .. ts:def:: MeasureInformation