docs(scorechain): Scorechain screening & TMS integration spec#3973
Draft
Blume1977 wants to merge 1 commit into
Draft
docs(scorechain): Scorechain screening & TMS integration spec#3973Blume1977 wants to merge 1 commit into
Blume1977 wants to merge 1 commit into
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Specification — Scorechain Wallet-Screening & Transaction-Monitoring Integration
Process: This is a specification only (docs, no code). Per the agreed workflow it
is submitted as a PR for review first — implementation starts only after this spec is
approved.
What this adds
docs/specs/scorechain-integration.md— a full integration spec for the ScorechainAML/KYT provider (license active since 2026-06-22), grounded in the existing codebase:
src/integration/scorechain/module following the existingsrc/integration/iknapattern (HttpService client,Configblock, own entity likesift-error-log). Runs in parallel toikna, does not replace it.(
/scoringAnalysis), deposit/withdrawal monitoring (/registerDeposit//registerWithdrawal) wired into payin / sell-crypto / payout, TMS alert handling,RSA-SHA256 response-signature verification, screening persistence + quota-aware caching
(5,000 checks/month, 1 screening = 2 checks).
src/subdomains/core/amlflow (advisory →manual check, reusing existing
AmlReasonvalues); no auto-reject in v1.pass), format/lint/type-check/test green, co-located immutable migrations, Draft PRs.
signature check, quota policy, ikna coexistence, exact call-sites, webhook vs. polling).
Review asks
ikna, entity in the integrationmodule)?
Kept as Draft until the spec is reviewed and approved.