taler-docs

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

commit 8651de8f18fc52096424144d6f7cab753d828434
parent 70504f7c42f483ad4a44e03150d71449de006e62
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon,  6 May 2024 21:42:00 +0200

work on DD23

Diffstat:
Mdesign-documents/023-taler-kyc.rst | 6+++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst @@ -1757,16 +1757,20 @@ on GET ``/deposits/`` with the respective legitimization requirement row. ,access_token BYTEA NOT NULL UNIQUE CHECK (LENGTH(access_token)=32) REFERENCES wire_targets (access_token) ,start_time INT8 NOT NULL - ,jmeasures TEXT NOT NULL + ,jmeasures TEXT NOT NULL -- FIXME: rename to jrule? ,display_priority INT4 NOT NULL ,is_finished BOOL NOT NULL DEFAULT(FALSE) ) PARTITION BY HASH (access_token); + COMMENT ON TABLE legitimization_measures + IS 'Rules that have been triggered for the account (FIXME: check this is consistent with usage)'; COMMENT ON COLUMN legitimization_measures.access_token IS 'Used to uniquely identify the account and as a symmetric access control mechanism for the SPA'; COMMENT ON COLUMN legitimization_measures.start_time IS 'Time when the measure was triggered (by decision or rule)'; + -- FIXME: LegitimizationMeasures is *bad* here, as we only have the KycRule; the specific measure may + -- not yet have been selected at the time of the trigger! COMMENT ON COLUMN legitimization_measures.jmeasures IS 'JSON object of type LegitimizationMeasures with KYC/AML measures for the account encoded'; COMMENT ON COLUMN legitimization_measures.display_priority