transaction-screening-workflow-concepts
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTransaction screening workflow (concepts)
交易筛查工作流(概念)
Educational reference only. Limits (batch sizes, engines, STR formats) change by product and jurisdiction—confirm in phalcon-compliance-documentation and your compliance program. Pair with address-screening-workflow-concepts (wallet inventory) and risk-exposure-screening-concepts (how direction affects participant and flow rules).
仅作为教育参考。 限制条件(批量大小、引擎、STR格式)会因product和jurisdiction而异——请在phalcon-compliance-documentation及您的合规计划中确认。请搭配address-screening-workflow-concepts(钱包清单)和risk-exposure-screening-concepts(方向如何影响参与者及流程规则)一起使用。
Unit of analysis
分析单位
- The smallest screening unit is often a single transfer (asset movement from from → to within a tx).
- One transaction (one hash) may contain many transfers. Products may let you screen each transfer, subset, or roll up to transaction-level risk—behavior varies by vendor.
- 最小的筛查单位通常是单笔转账(资产在一笔交易中从转出方→转入方的转移)。
- 一笔交易(一个交易哈希)可能包含多笔转账。不同产品可能允许您筛查每一笔转账、部分转账,或汇总至交易层面评估风险——具体行为因供应商而异。
Direction (deposit vs withdrawal)
方向(存入 vs 转出)
Setting Deposit vs Withdrawal steers which rules and which side of the flow the engines emphasize:
| Direction | Typical screening focus |
|---|---|
| Deposit | Inflow to the platform/customer relationship—provenance of funds arriving. |
| Withdrawal | Outflow and destination—where funds leave toward. |
Common product behavior (verify in docs):
- Rules can be scoped to one direction (for example deposit-only policies do not run on withdrawal-labeled items).
- If no direction is set, some products default to running both deposit- and withdrawal-oriented passes to reduce misconfiguration.
- Correct direction is used to tune rules and reduce false positives—it is an operational control, not a legal classification.
This aligns with participant/flow screening notes in risk-exposure-screening-concepts.
设置存入与转出将引导引擎侧重不同的规则和流程环节:
| 方向 | 典型筛查重点 |
|---|---|
| 存入 | 流入平台/客户关系——核查资金来源。 |
| 转出 | 流出及目的地——追踪资金去向。 |
常见产品行为(请在文档中确认):
- 规则可限定为单一方向(例如仅存入规则不会在标记为转出的项目上运行)。
- 如果未设置方向,部分产品默认同时运行存入和转出导向的筛查,以减少配置错误。
- 正确设置方向可用于优化规则并降低误报率——这是一项操作控制,而非法律分类。
这与risk-exposure-screening-concepts中的参与者/流程筛查说明一致。
Labels
标签
Labels are user-defined strings for organization and case context on a transaction or transfer (distinct from address tags/markers in address-screening-workflow-concepts).
标签是用户定义的字符串,用于为交易或转账添加分类和案例上下文(与address-screening-workflow-concepts中的地址标记/标签不同)。
Import methods
导入方式
- Single transaction hash — Paste a hash; the product fetches parsed transfers; you select which transfer(s) to screen and attach direction, labels, and customer linkage.
- Bulk CSV — Template-driven import of many rows (batch size caps are product-specific—on the order of hundreds per file in some docs).
Typical CSV-style columns (names vary):
| Field | Purpose |
|---|---|
| Chain | Network identifier per template |
| Transaction hash | On-chain tx id |
| Label | Optional private label |
| Direction | Optional |
| Customer ID | Optional internal customer key |
| Transfer From / Transfer To | Optional pair to disambiguate one transfer inside a multi-transfer tx |
Review per-row import outcomes in the UI.
- 单笔交易哈希 —— 粘贴哈希值;产品将获取解析后的转账记录;您可选择要筛查的转账,并关联方向、标签和客户信息。
- 批量CSV导入 —— 基于模板导入多行数据(批量上限因product而异——部分文档显示上限为每文件数百条)。
典型CSV格式列(列名可能不同):
| 字段 | 用途 |
|---|---|
| Chain | 模板指定的网络标识符 |
| 交易哈希(Transaction hash) | 链上交易ID |
| Label | 可选私有标签 |
| Direction | 可选 |
| Customer ID | 可选内部客户密钥 |
| Transfer From / Transfer To | 可选字段,用于区分多转账交易中的某一笔转账 |
在UI中查看逐行导入结果。
Transaction list
交易列表
Lists commonly show: hash, risk summary, screening direction, open alerts, last screened, notional (often USD), token amount, asset, from/to, timestamp, customer, labels, added time. Multi-transfer rows may collapse with expand to child transfers.
列表通常显示:哈希、风险摘要、筛查方向、未处理警报、最后筛查时间、名义金额(通常为美元)、代币数量、资产、转出/转入方、时间戳、客户、标签、添加时间。多转账行可能折叠,可展开查看子转账记录。
Transaction details page
交易详情页
Typical sections:
- Basic information — Asset, time, labels, customer, etc.
- Risk summary — Rolled-up alert view.
- Risk overview — Finer breakdown: risk categories, exposure-style charts, exposed address lists, fund-flow narrative; products may link to an external graph or trace tool where integrated.
- Token transfers — Graph plus tabular list of each transfer; per-transfer alerts; unscreened legs may be screenable on demand.
- Transfers overview — Compact index with shortcuts into each transfer.
- Alerts — Filterable list.
- Audit log — Comments and system events (same idea as address workflow).
Rescreen — Re-run screening for the whole transaction or a specific transfer; direction may be set per run.
典型板块:
- 基本信息 —— 资产、时间、标签、客户等。
- 风险摘要 —— 汇总式警报视图。
- 风险概览 —— 更详细的分类:风险类别、暴露情况图表、涉险地址列表、资金流向说明;若集成相关工具,产品可能链接至外部图谱或追踪工具。
- 代币转账 —— 图谱加表格形式展示每笔转账;逐笔转账警报;未筛查的转账可按需启动筛查。
- 转账概览 —— 紧凑索引,可快速跳转至每笔转账。
- 警报 —— 可筛选的列表。
- 审计日志 —— 评论和系统事件(与地址工作流逻辑相同)。
重新筛查 —— 为整笔交易或特定转账重新运行筛查;可在每次运行时设置方向。
STR-style and regulatory exports
STR格式及监管导出
Some products expose Suspicious Transaction Report (STR) or regional equivalents:
- Region selection matters—formats and fields differ by jurisdiction.
- Direction is often a prerequisite for valid STR generation in the product model.
- Reports may be generated per transfer when policy requires transfer-level suspicious activity narratives.
Not legal advice. STR obligations depend on local law and institutional policy; use qualified compliance and legal review for filings.
部分产品支持**可疑交易报告(Suspicious Transaction Report, STR)**或区域等效报告:
- 区域选择至关重要——格式和字段因司法管辖区而异。
- 在产品模型中,方向通常是生成有效STR的先决条件。
- 当政策要求按转账层面撰写可疑活动说明时,可按每笔转账生成报告。
非法律建议。 STR义务取决于当地法律和机构政策;申报需咨询专业合规和法律人员。
Deleting a transaction
删除交易
Removing a transaction record typically deletes associated transfers and expires related alerts in the product. Public-chain data remain on explorers.
删除交易记录通常会在产品中删除关联的转账记录并终止相关警报。链上数据仍将保留在区块链浏览器中。
Guardrails
注意事项
- Do not paste live production tx hashes tied to identifiable customers into public channels.
- Do not assist with structuring flows to evade monitoring or mis-labeling direction.
- STR and travel rule questions need program-specific guidance beyond generic skills.
- 请勿将与可识别客户关联的实时生产交易哈希粘贴至公开渠道。
- 请勿协助构建旨在规避监控的流程或错误标记方向。
- STR和旅行规则相关问题需参考特定计划的指导,超出通用知识范围。
See also
另请参阅
- address-screening-workflow-concepts — wallet inventory, tags/markers, blacklist/whitelist.
- behavioral-risk-screening-concepts — velocity and amount heuristics that may surface at transfer level.
Goal: a portable mental model of transaction screening UIs and direction semantics aligned with common compliance products, without binding a specific vendor implementation.
- address-screening-workflow-concepts —— 钱包清单、标记/标签、黑白名单。
- behavioral-risk-screening-concepts —— 可能在转账层面触发的速度和金额启发式规则。
目标: 建立一个可通用的交易筛查UI及方向语义的心智模型,与常见合规产品对齐,不绑定特定供应商实现。