Skip to main content
Didit 融资 750 万美元，打造身份与欺诈基础设施
Didit
PSD3 · 强客户认证

两个 SCA 因素。一键完成。

生物识别认证 ($0.10) 加上设备与 IP 分析 ($0.03)，在一个提示中提供两个 PSD3 级别的 SCA 因素。防钓鱼。可替代短信一次性密码。

免费开始阅读文档
投资方
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

全球2,000多家组织信赖。

一幅电影般的深色抽象合规插图, 在纯黑画布上，四个浮动的半透明深色玻璃面板呈 3D 透视，由一条发光的 Didit 蓝色垂直线穿过，并由四个发光扫描支架框住。每个面板都带有一个微小的浅白色抽象图案（指纹弧线、面部椭圆、手机轮廓、锁形），代表生物识别强客户认证。

为何短信验证码（OTP）即将退出历史舞台

防 SIM 卡互换。防钓鱼。每次认证 $0.13。

PSD3 正在逐步淘汰短信一次性密码（OTP）作为强客户认证（SCA）因素。 Didit 的设备绑定生物识别 SCA 能有效阻止 SIM 卡劫持、实时网络钓鱼和 SS7 拦截。 每次认证仅需 $0.13，两秒内即可完成验证，并支持动态链接。每月免费提供 500 次验证。

工作原理

从注册到验证用户，仅需四步。

  1. 步骤 01

    创建工作流

    选择您需要的验证项, 身份、活体、人脸匹配、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制面板中拖拽构建流程，或通过 API 发布。支持条件分支、A/B 测试，无需代码。

  2. 步骤 02

    集成

    通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。也可重定向到托管页面，或直接通过邮件、短信、WhatsApp 等方式向用户发送链接。选择最适合您技术栈的方案。

  3. 步骤 03

    用户完成流程

    Didit 负责托管摄像头、光线提示、移动设备切换和无障碍功能。在用户进行流程时，我们实时分析 200 多个欺诈信号，并根据权威数据源验证所有字段。两秒内即可获得结果。

  4. 步骤 04

    接收结果

    实时签名的 Webhook 可确保用户通过、拒绝或需要审核时，您的数据库即时同步。您也可以按需轮询 API，或打开控制台检查每个会话、每个信号，并按您的方式管理案例。

专为 SCA 构建 · 基础设施定价

双重因素。一次提示。每次认证 $0.13。

真正的强客户认证（SCA）并非单一检查，而是一套组合拳。您可以根据工作流切换豁免规则，并根据风险信号升级到硬件密钥。无需重新部署。
阅读文档获取 API 密钥
01 · SCA 因素

双重因素。不同类别。

固有性（被动活体检测 + 人脸 1:1 匹配）加上持有性（用户绑定的设备）。默认符合 PSD3 标准。知识因素（PIN、密码）可选，可根据工作流配置。
生物识别认证模块
02 · 动态链接

一次批准。绑定金额 + 收款人。

对于支付，认证挑战会嵌入确切的金额和收款人信息。用户在生物识别提示中即可看到。任何篡改都会使批准失效, 这是 PSR 内置的功能。
会话 API 参考
03 · 为何短信验证码（OTP）即将退出历史舞台

原生防钓鱼设计。

SIM 卡劫持欺诈、实时网络钓鱼工具、SS7 拦截, 这些都能攻破短信一次性密码。设备绑定生物识别技术与源绑定功能，能有效阻止欧洲银行管理局在其 2024 年 SCA 意见中指出的所有常见攻击。
账户盗用预防
04 · 豁免引擎

豁免策略，按工作流精细校准。

低价值远程交易（低于 30 欧元）、非接触式销售点交易（低于 50 欧元）、重复相同交易、受信任受益人、交易风险分析层级。所有这些都可以在无代码工作流构建器中编辑。
工作流编排器
05 · 每次认证 200+ 信号

每次认证，200+信号实时分析。

设备指纹、IP 地理定位、VPN / 代理 / 数据中心检测、新设备标记、行为漂移。当风险超过您的阈值时，自动升级到硬件密钥。
设备与 IP 分析模块
06 · 经济效益

$0.13 per auth, not $0.04 plus SIM-swap loss.

生物识别认证 $0.10 + 设备和 IP 分析 $0.03 = 每次强客户认证 $0.13。短信一次性密码的成本为 $0.04-$0.07，此外还有投递失败、重试以及监管机构在 PSD3 中考虑的 SIM 卡劫持损失风险。
定价
集成

一次会话。一键确认。一个 Webhook。

通过金额和收款人信息开启会话。用户在手机上批准。签名 Webhook 确认绑定。
POST /v3/session/登录
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_sca_biometric",
    "vendor_data": "user-42",
    "metadata": { "purpose": "login" },
    // base64 KYC enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201已创建状态：已批准 · 已拒绝 · 审核中
将 KYC 注册自拍作为 portrait_image 传递。无需重新注册。文档 →
POST /v3/session/支付
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_sca_biometric",
    "vendor_data": "user-42",
    "metadata": { "amount": "247.50", "payee_account": "ES91…1332" },
    // base64 KYC enrolment selfie, ≤ 1MB
    "portrait_image": "/9j/4AAQSkZJRgABAQE..."
  }'
201已创建webhook 回显金额 + 收款人以供验证
用户在生物识别提示中直接看到金额 + 收款人。动态链接。文档 →
代理就绪集成

一个提示，搞定 PSD3 SCA 流程。

粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent。填入您的技术栈。Agent 将构建工作流，连接动态链接，集成 SDK，并在五分钟内交付一个可用的强客户认证方案。
didit-integration-prompt.md
You are integrating Didit's Strong Customer Authentication into a payment service provider, bank, EMI, or wallet to satisfy PSD3 / the Payment Services Regulation (PSR). Two factors in one prompt:

  1. Inherence — Biometric Authentication: Passive Liveness + Face Match 1:1 against the user's previously-enrolled KYC selfie.
  2. Possession — Device & IP Analysis: 200+ real-time fraud signals binding the auth to the user's known device.

Pricing (verified live 2026-05-16):
  - Biometric Authentication: $0.10 per auth
  - Device & IP Analysis: $0.03 per auth
  - Total: $0.13 per Strong Customer Authentication
  - First 500 verifications free every month, forever
  - Re-uses the enrolled selfie from the original KYC — no re-enrolment

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - Webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header.
  - A workflow_id from the no-code Workflow Builder configured as a Biometric Authentication workflow (Passive Liveness + Face Match 1:1 + Device & IP Analysis).
  - The user has previously completed a Didit KYC (the same enrolled selfie backs every subsequent auth).

STEP 1 — Open an authentication session

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body (for login auth):
    {
      "workflow_id": "<wf id for SCA biometric auth>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/auth/callback",
      "metadata": {
        "purpose": "login",
        "session_id": "<your front-end session id>"
      },
      "portrait_image": "<base64 JPEG of the user's KYC enrolment selfie, ≤ 1 MB — REQUIRED for SCA's inherence factor; OMIT only if the workflow is liveness-only>"
    }

  Body (for payment with dynamic linking):
    {
      "workflow_id": "<wf id for SCA biometric auth>",
      "vendor_data": "<your user id>",
      "callback": "https://<your-app>/payment/callback",
      "metadata": {
        "purpose": "payment",
        "amount": "247.50",
        "currency": "EUR",
        "payee_account": "ES9121000418450200051332",
        "payee_name": "<merchant or recipient>",
        "transaction_reference": "<your internal transaction id>"
      },
      "portrait_image": "<base64 JPEG of the user's KYC enrolment selfie, ≤ 1 MB — REQUIRED for SCA's inherence factor>"
    }

  Response: 201 Created with the hosted session URL. Push the URL to the user via deep-link / push notification / in-app sheet.

STEP 2 — User completes the biometric auth

  The user sees one prompt on their phone (or via the Didit SDK in your native app). Three things happen on the same screen:

  1. The amount + payee are displayed (dynamic linking — the user explicitly approves THIS amount to THIS payee for payments).
  2. Passive Liveness defeats screen replay, printed photo, mask, deepfake.
  3. Face Match 1:1 matches the new selfie against the enrolled KYC selfie.

  Device & IP Analysis runs server-side on the session. Sub-2-second median verdict.

STEP 3 — Read the signed webhook on the auth verdict

  Didit POSTs to your callback. Session statuses (Title Case With Spaces):

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved", "vpn_detected": false, "datacenter_ip": false },
      "metadata_echo": {
        "amount": "247.50",
        "payee_account": "ES9121000418450200051332"
      }
    }

  Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

  Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.

  For payments, verify that metadata_echo.amount and metadata_echo.payee_account match the values you passed in. If they do not, REJECT the payment — it's a dynamic-linking violation.

STEP 4 — Branch on verdict

  Approved   → unlock the action (login, payment, account change).
  In Review  → hold the action, route to manual review queue.
  Declined   → block, log the attempt, surface a friendly "try again" to the user.
  Resubmitted → the user re-submitted after a soft fail (poor lighting, occlusion); proceed if the latest status is Approved.

STEP 5 — Retrieve the full decision later

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full payload: liveness verdict (iBeta Level 1 anti-spoof certified), Face Match similarity score, device fingerprint, IP geolocation, VPN / proxy / datacenter flags, 200+ fraud-signal score, dynamic-linking echo, HMAC signature.

  Use this for the audit-trail surface a regulator examines on Strong Customer Authentication coverage.

STEP 6 — Step up on risk

  When Device & IP Analysis surfaces a high-risk signal (new device + high-value payment, VPN/proxy on a login, geolocation jump), your workflow can step up to:

  - A separate hardware-key challenge (FIDO2 / WebAuthn)
  - A trusted-beneficiary whitelist confirmation
  - A manual-review hold

  Encode the step-up policy in the no-code Workflow Builder — no redeploy required.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE on a session.
  - Dynamic linking is REQUIRED for payments — pass amount + payee in metadata, verify the echo on the webhook.
  - The enrolled selfie that backs every SCA is the one captured during the user's original KYC — no separate enrolment step.
  - PSD3 / PSR exemptions (low-value remote < EUR 30, contactless point-of-sale < EUR 50, recurring identical, trusted beneficiary, Transaction Risk Analysis tiers) are configured per workflow in the Business Console.
  - Default record retention is 5 years per the EU AML and payments rules.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks

Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.
需要更多上下文？请参阅完整的模块文档。docs.didit.me →
合规性设计

一键开启新国家/地区业务。 我们为您解决难题。

我们负责设立当地子公司、获取许可证、进行渗透测试、获得认证，并与所有新法规保持一致。要在新国家/地区发布验证服务，只需轻点开关。已覆盖220多个国家/地区，每个季度进行审计和渗透测试, 是唯一一个被欧盟成员国政府正式认定比线下验证更安全的身份提供商。
阅读安全与合规性档案
欧盟金融沙盒
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
信息安全 · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
原生符合欧盟标准

数据证明

数据证明
  • $0.00
    每次强客户认证, 生物识别认证 + 设备与 IP 分析。
  • <0s
    在入门级 Android 设备上，每次会话的端到端认证结果。
  • 0+
    每次认证都会评估实时欺诈信号, VPN、数据中心、地理位置漂移、设备漂移。
  • 0
    每个账户每月免费验证。
三个层级，一份价目表

免费开始。按使用量付费。可扩展至企业级。

每月 500 次免费验证，永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
免费

免费

每月 $0。无需信用卡。

  • 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
  • 黑名单用户
  • 重复检测
  • 每次会话 200+ 欺诈信号
  • Didit 网络中可重复使用的 KYC
  • 案件管理平台
  • 工作流构建器
  • 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
  • 社区支持
免费开始
最受欢迎
按用量付费

按用量计费

按实际用量付费。25+模块。公开的模块定价，无每月最低费用。

  • 完整KYC $0.33（身份+生物识别+IP/设备）
  • 10,000+ AML数据集, 制裁、PEP、负面媒体
  • 1,000+ 政府数据源用于数据库验证
  • 交易监控 $0.02/笔交易
  • 实时KYB $2.00/家企业
  • 钱包筛选 $0.15/次检查
  • 白标验证流程, 您的品牌，我们的基础设施
查看完整价格列表免费开始
企业版

企业版

定制MSA和SLA。适用于大批量和受监管项目。

  • 年度合同
  • 定制MSA、DPA和SLA
  • 专属Slack和WhatsApp频道
  • 按需人工审核员
  • 经销商和白标条款
  • 独家功能和合作伙伴集成
  • 指定CSM、安全审查、合规支持
联系我们

免费开始 → 仅在检查运行时付费 → 解锁企业版以获取定制合约、SLA 或数据驻留。

FAQ

常见问题

What is Didit?

Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:

  • Fast, sub-2-second p99 on every session
  • Reliable, in production with 1,500+ companies across 220+ countries
  • Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

What is Strong Customer Authentication, in plain English?

Strong Customer Authentication (SCA) is a rule from the EU's payment-services regulation that says: when a customer logs in to their account or initiates a payment, you must verify them using at least two of three independent factor categories.

The three categories:

  • Knowledge, something only the user knows (password, PIN, secret answer)
  • Possession, something only the user has (phone, hardware key, SIM-bound device)
  • Inherence, something only the user is (fingerprint, face, behavioural pattern)

The two factors must come from different categories, a password plus a security question is not SCA, because both are knowledge. A password plus a fingerprint is, because they cross categories.

A third requirement, dynamic linking, says the second factor for a payment must be tied uniquely to the transaction amount and payee, so a stolen code cannot be replayed against a different transaction.

What is PSD3, and how is it different from PSD2?

PSD3, short for Payment Services Directive 3, is the EU's 2026 rewrite of the rulebook PSD2 introduced in 2018. Alongside it sits the Payment Services Regulation (PSR) which is directly applicable across member states without national transposition.

Key changes over PSD2:

  • Fewer exemptions, the corporate-payments and trusted-beneficiary exemptions are tightened
  • Phishing-resistant SCA mandated, SMS one-time-password is being phased out as the sole second factor; FIDO2, device-bound biometrics, or app-based push become the new default
  • Open-banking access strengthened, banks must offer a clean, unified API; permissioned third-party providers get better technical terms
  • Fraud-liability clarified, payment service providers (PSPs) carry more of the fraud loss when their SCA was weak
  • Wider scope, wallet providers, electronic-money institutions (EMIs), and some crypto providers come into the regime

Transition is rolling, most SCA changes are expected to take effect 18 to 24 months after final adoption.

How fast is the verification for my end user?

The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.

On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.

Which transactions need SCA, and which are exempt?

Need SCA by default:

  • Customer login to a payment account
  • Initiating an electronic payment
  • Any action that could be exploited to commit payment fraud

Exempt (PSD3 keeps most PSD2 exemptions but tightens the thresholds):

  • Low-value remote transactions, under €30 single, with cumulative caps per customer
  • Contactless point-of-sale payments, under €50 single, with cumulative caps
  • Recurring transactions of identical amount and payee, SCA on first, exempt after
  • Trusted beneficiaries, user explicitly whitelists, but PSD3 tightens approval flow
  • Transaction Risk Analysis (TRA), under thresholds linked to your overall fraud rate (1, 5, 10, 25 basis points)
  • Corporate dedicated channels, when both ends are corporate users on a closed system

Getting the exemption math right is the highest-leverage SCA optimisation work most teams do, applied well it drops auth friction without raising fraud.

What happens if a user fails, abandons, or expires?

Every session lands on one of seven clear statuses, so your code always knows what to do:

  • Approved, every check passed. Move the user forward.
  • Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
  • In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
  • In Progress, user is mid-flow.
  • Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
  • Abandoned, user opened the link but did not finish in time. Re-engage or expire.
  • Expired, the session link aged out. Create a new session.

A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.

Where does my customer data live and how is it protected?

Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.

Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.

Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.

Is Didit compliant for my industry?

Didit ships compliant by default for the regulators that matter to identity infrastructure:

  • GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
  • AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
  • eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
  • MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
  • DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
  • UK Online Safety Act, age-gating and child-safety obligations.
  • FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: /security-compliance.

How fast can I integrate and start verifying users?
  • 60 seconds to a sandbox account at business.didit.me, no credit card.
  • 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
  • A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths, pick whichever fits your stack:

  • Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
  • Redirect the user to the hosted verification page, zero SDK.
  • Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.

How does this work on iOS, Android, and the web?

Same POST /v3/session/ API on every surface, the user-facing capture differs:

  • Web (desktop browser), Didit launches the auth flow in a popup; the user's phone receives a push notification, completes the biometric on the phone, and the popup closes with the approved verdict. Universal-link handoff if the user is on mobile web.
  • Native iOS / Android, drop in the Didit iOS or Android SDK, call the auth method, the OS-native biometric prompt appears (Face ID, Touch ID, fingerprint) backed by the secure enclave
  • React Native / Flutter / Cordova, official SDKs wrap the native modules; identical API surface
  • MCP server, if the auth lives behind an AI agent, the agent calls the auth tool, the user receives a push on their phone, approves, and the verdict returns

The same biometric template the user enrolled at KYC time backs every auth, no re-enrolment, no separate flow.

Does this work outside PSD3 / the EU?

Yes, the same auth bundle satisfies most equivalent global rules:

  • United Kingdom, the FCA's Strong Customer Authentication rules mirror PSD2/PSD3 in substance; Didit's auth bundle qualifies
  • United States, no nationwide SCA mandate, but bank regulators (OCC, Federal Reserve) and the Federal Financial Institutions Examination Council (FFIEC) recommend multi-factor authentication for high-value transactions; Didit drops in
  • Singapore, Monetary Authority of Singapore (MAS) Notice 644 mandates SCA on Internet banking
  • India, Reserve Bank of India two-factor authentication is mandatory on every domestic card transaction
  • Brazil, Banco Central rules align with PSD2-style SCA on instant payments
  • Australia, Japan, South Korea, equivalent multi-factor authentication requirements for banking and high-value e-commerce

One API, one auth bundle, every jurisdiction. The exemption math changes; the technical contract does not.

What does the auth event evidence look like for an examiner?

Every authentication produces a signed evidence record exportable from the Business Console:

  • The auth challenge, timestamp, session ID, requested factors
  • The biometric verdict, Passive Liveness pass/fail, Face Match similarity score (linked to the user's KYC reference selfie), iBeta Level 1 anti-spoof claim
  • The device verdict, device fingerprint, IP geolocation, VPN/proxy/datacenter flags, 200+ fraud-signal score
  • The dynamic-linking payload, amount, payee, timestamp, signed end-to-end
  • The full audit trail, every step state-machined from Pending to Approved or Declined, with reviewer notes if escalated
  • HMAC SHA-256 signature on the payload so chain-of-custody is provable

All records stored in the European Union (EU data centres), retained indefinitely while your subscription is active. Default record retention is 5 years per the EU AML and payments rules, extensible per your supervisor's guidance.

Related

相关模块 + 工作流

身份与欺诈基础设施。

一个 API 即可实现 KYC、KYB、交易监控和钱包筛选。5 分钟即可集成。

免费开始联系我们
让 AI 总结此页面