Skip to main content
Didit angaria 7,5 milhões de dólares para construir a infraestrutura para identidade e fraude
Didit
KYC White-label

A sua marca. Didit por baixo.

Revenda ou incorpore a verificação de identidade com a sua marca. $0.33 + $0.20 de taxa white-label por verificação, sem UI para construir, sem conformidade para manter. 500 verificações gratuitas por mês.

Apoiado por
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Confiado por mais de 2.000 organizações em todo o mundo.

Uma ilustração cinematográfica abstrata escura de KYC white-label, quatro painéis de vidro translúcidos flutuantes em perspetiva 3D sobre preto puro, atravessados por uma linha luminosa Didit Blue e emoldurados por quatro suportes de scanner brilhantes. Cada painel contém um pequeno motivo abstrato branco pálido que representa a marca do revendedor (ponta de pincel, pontos da paleta de temas, janela do navegador com barra de cabeçalho, peça de puzzle SDK).

O que um revendedor deve

Implemente KYC com a sua marca. Ignore a infraestrutura subjacente.

Configure cores, tipografia, logótipos quadrados + retangulares e o seu próprio domínio personalizado no Editor de Estilo, ative a opção Incluir estilo personalizado em cada fluxo de trabalho. O utilizador final vê a sua marca, o seu domínio, o seu fluxo; você herda iBeta Nível 1 PAD (Deteção de Ataques de Apresentação), atestado Tesoro / SEPBLAC de Espanha, SOC 2 Tipo 1 e ISO/IEC 27001 da Didit. 500 verificações grátis todos os meses.

Como funciona

Do registo ao utilizador verificado em quatro passos.

  1. Passo 01

    Crie o fluxo de trabalho

    Escolha as verificações que pretende, ID, prova de vida, correspondência facial, sanções, morada, idade, telefone, e-mail, perguntas personalizadas. Arraste-as para um fluxo no dashboard, ou publique o mesmo fluxo na nossa API. Crie ramificações com base em condições, execute testes A/B, sem necessidade de código.

  2. Passo 02

    Integre

    Incorpore nativamente com os nossos SDKs Web, iOS, Android, React Native ou Flutter. Redirecione para uma página alojada. Ou simplesmente envie um link ao seu utilizador, por e-mail, SMS, WhatsApp, onde quiser. Escolha o que melhor se adapta à sua stack.

  3. Passo 03

    O utilizador passa pelo fluxo

    A Didit aloja a câmara, as indicações de iluminação, a transição para o telemóvel e a acessibilidade. Enquanto o utilizador está no fluxo, pontuamos mais de 200 sinais de fraude em tempo real e verificamos cada campo em relação a fontes de dados autorizadas. Resultado em menos de dois segundos.

  4. Passo 04

    Recebe os resultados

    Webhooks assinados em tempo real mantêm a sua base de dados sincronizada no momento em que um utilizador é aprovado, recusado ou enviado para revisão. Consulte a API sob demanda. Ou abra a consola para inspecionar cada sessão, cada sinal e gerir os casos à sua maneira.

Criado para revendedores + integradores · Preço de infraestrutura

Seis primitivos. 0,53 $ por verificação.

O white-label é a mesma stack Didit, mas com a sua marca. Crie a sua receita: marca, domínio, SDK, workflow, preços, conformidade.
01 · Editor de Estilo

Troca de marca sem código.

Cores, tipografia, logótipos quadrados + retangulares, raio de borda, ecrã de login Didit opcional (ativado ou desativado). A pré-visualização aparece numa UI alojada que se parece com a sua, não com a da Didit. Configurado uma vez por conta, aplicado por workflow.
Módulo White Label
02 · Domínio personalizado

Alojado em verify.asuamarca.com.

Alvo CNAME = verify.didit.me, certificado TLS auto-provisionado via Let's Encrypt, HSTS ativado por predefinição. Verificado na Business Console, zero operações do seu lado.
Documentação White Label
03 · SDKs · cinco interfaces

Uma marca. Em todas as plataformas.

A mesma configuração do Editor de Estilo aplica-se a Web, iOS (Swift), Android (Kotlin), React Native (TurboModules) e Flutter. Os SDKs são gratuitos; a taxa de white-label cobre a marca em todos eles.
Orquestrador de Workflow
04 · Marca por workflow

Misture branded + unbranded numa só conta.

Ative o estilo personalizado para workflows de cliente, desative para fluxos administrativos internos. Ideal para revendedores multi-marca, uma conta Didit, várias marcas de cliente final, estilo por workflow.
Documentação de Workflow
05 · Preços para revendedores

$0.53 cost in. You pick the sticker.

Pacote Didit KYC 0,33 $ + taxa white-label 0,20 $ = 0,53 $ por verificação. Venda ao seu cliente por 0,99 $–1,49 $; mantenha a margem. Descontos por volume aplicam-se em grande escala, fale com a equipa de vendas.
Módulo de Verificação de Utilizador
06 · Auditoria retida

A sua marca. A mesma conformidade.

iBeta Nível 1 PAD, atestado Tesoro / SEPBLAC de Espanha, SOC 2 Tipo 1, ISO/IEC 27001, alinhamento com GDPR, retenção de 5 anos por predefinição. Mude a marca; a conformidade subjacente não muda.
Módulo de Rastreio AML
Integrar

Uma sessão. A sua marca. O seu domínio.

Abra a sessão com a sua marca. Leia o veredito assinado. O utilizador final nunca vê a Didit.
POST /v3/session/Com marca
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_signup_branded",
    "vendor_data": "end-user-42",
    "metadata": { "tenant_id": "marca-b" }
  }'
201CriadoDevolve um URL alojado no SEU domínio personalizado.
Branding via Style Editor + alternância por fluxo de trabalho. Sem alterações na API.docs →
GET /v3/session/{sessionId}/decision/Veredito
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Returns:
{
  "estado": "Aprovado",
  "aml": { "estado": "Aprovado" }
}
200OKestado Aprovado · Recusado · Em Revisão · Reenviado · Expirado
O mesmo contrato /v3/, independentemente de como personaliza a UI.docs →
Integração pronta para agente

Lance um produto KYC white-label com um único prompt.

Cole no Claude Code, Cursor, Codex, Devin, Aider ou Replit Agent. Preencha a sua marca + domínio + módulos de fluxo de trabalho. O agente configura o Style Editor, liga o webhook assinado e lança o fluxo personalizado.
didit-integration-prompt.md
You are integrating Didit white-label KYC. You're either reselling identity verification to your own customers under your brand, or embedding KYC inside your SaaS product so the end-user never sees Didit. Either way, the verification stack is Didit's; the visible brand is yours.

Three pillars:

  1. Configure your brand once in the Style Editor — colours, typography, square + rectangular logos, optional custom domain.
  2. Toggle Include custom style ON for every workflow that should ship under your brand. Leave it OFF for internal admin flows.
  3. Open POST /v3/session/ as usual. The hosted UI returns under your brand on your domain.

Cost:
  - Didit KYC bundle: $0.33 per check (Sessions API floor)
  - White-label fee: $0.20 per check (adds branding + custom domain + per-workflow style toggle)
  - Reseller cost in: $0.53 per check
  - Mark up to your buyer as you choose — published rate at scale, custom contracts above 100k/month
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - White-label add-on enabled on your account (talk to sales to switch it on).
  - Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
  - A workflow_id from the Workflow Builder that bundles the modules you ship (typically ID Verification + Passive Liveness + Face Match 1:1 + AML Screening) with Include custom style ENABLED.
  - Optional: custom domain (e.g. verify.yourbrand.com) configured in the Business Console — Didit handles the CNAME target + TLS cert via Let's Encrypt.

STEP 1 — Configure brand in the Style Editor (no code)

  Console → White Label → Style Editor:
    Colors:      buttons, text, panels, backgrounds
    Typography:  fonts that match your brand
    Logos:       square + rectangular uploads
    Layout:      border radius for panels and buttons
    Login:       show or skip the Didit login screen
    Domain:      add verify.yourbrand.com (CNAME target = verify.didit.me; TLS auto-provisioned)

STEP 2 — Enable custom style on the workflow

  Console → Workflows → <your workflow> → Settings → Options:
    Toggle Include custom style ON. Without this, the workflow ships with default Didit branding.

  Repeat per workflow. You can mix branded + unbranded workflows on the same account — useful for an internal admin flow that doesn't need the customer brand.

STEP 3 — Open a session as usual

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with Include custom style ON>",
      "vendor_data": "<your end-user id, max 256 chars>",
      "callback": "https://<your-app>/kyc/callback",
      "metadata": {
        "purpose": "white_label_onboarding",
        "tenant_id": "<your reseller tenant id if multi-brand>"
      }
    }

  Response: 201 Created with the hosted session URL — under YOUR domain if you set one. Sub-2-second median verdict on completion.

STEP 4 — Read the signed webhook on completion

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

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your end-user id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "aml": { "status": "Approved", "hits": [] }
    }

  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.

  On Approved → onboard the end-user. On Declined → reject. On In Review or Resubmitted → hold + route to your compliance team.

STEP 5 — Multi-brand on one account (reseller pattern)

  When you serve multiple end-customer brands from a single Didit account:

  - Create one workflow per end-customer brand
  - Configure each workflow with the customer's brand style (or use the Style Editor presets per workflow if your account supports it)
  - On POST /v3/session/, pick the workflow_id that matches the end-customer's brand

  The end-customer sees their own brand; you see one consolidated invoice per month. Didit's MCP (Model Context Protocol) server is included free for programmatic per-tenant workflow management.

STEP 6 — Audit + compliance retained

  Swapping the brand does not change the underlying compliance bar. Every session is still:
  - iBeta Level 1 PAD (Presentation Attack Detection) certified on liveness
  - Backed by Spain's Tesoro / SEPBLAC attestation (only EU member-state government attestation of safer-than-in-person verification)
  - Aligned with SOC 2 Type 1 + ISO/IEC 27001 + GDPR (General Data Protection Regulation)
  - Logged with X-Signature-V2 webhook signing on every event
  - Retained 5 years post-relationship by default per the EU Anti-Money-Laundering package; configurable upward per your supervisor's guidance

  Sub-processor disclosure available on request for your DPA (Data Processing Agreement).

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 (Approved, In Review). Don't transform them.
  - The white-label add-on is a per-account feature — talk to sales to enable it. Once enabled, the Style Editor + custom-domain pipeline is no-code.
  - Custom domain TLS auto-renews 30 days before expiry. Monitor the cert status in the Console.
  - Some end-user browsers (mobile in-app webviews) constrain custom domains — keep verify.didit.me as a fallback for these edge cases.

Read the docs:
  - https://docs.didit.me/console/white-label
  - https://docs.didit.me/console/workflows
  - https://docs.didit.me/sessions-api/create-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.
Precisa de mais contexto? Consulte a documentação completa do módulo.docs.didit.me →
Conformidade desde a conceção

Abra um novo país com um clique. Nós fazemos o trabalho difícil.

Abrimos as subsidiárias locais, garantimos as licenças, realizamos os testes de penetração, obtemos as certificações e alinhamos com cada nova regulamentação. Para lançar verificações num novo país, basta ativar um botão. Mais de 220 países ativos, auditados e testados trimestralmente, o único fornecedor de identidade que um governo de um estado-membro da UE formalmente considerou mais seguro do que a verificação presencial.
Ler o dossiê de segurança e conformidade
Sandbox financeiro da UE
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Segurança da informação · 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
Alinhado com a UE por design

Números comprovativos

Números comprovativos
  • $0.00
    Custo por verificação, pacote KYC de $0.33 + taxa white-label de $0.20. Marque o preço para o seu comprador.
  • 0 SDKs
    Web, iOS, Android, React Native, Flutter, todos com a mesma marca.
  • Per WF
    Inclui alternância de estilo personalizado, fluxos de trabalho com e sem marca numa única conta.
  • 0
    Verificações gratuitas todos os meses, em todas as contas.
Três níveis, uma tabela de preços

Comece grátis. Pague por utilização. Expanda para Enterprise.

500 verificações gratuitas todos os meses, para sempre. Pague à medida que usa para produção. Contratos personalizados, residência de dados e SLAs (Acordos de Nível de Serviço) no Enterprise.
Grátis

Grátis

$0 / mês. Não é necessário cartão de crédito.

  • Pacote KYC gratuito (Verificação de ID + Prova de Vida Passiva + Correspondência Facial + Análise de Dispositivo e IP), 500 / mês, todos os meses
  • Utilizadores Bloqueados
  • Deteção de Duplicados
  • Mais de 200 sinais de fraude em cada sessão
  • KYC reutilizável em toda a rede Didit
  • Plataforma de Gestão de Casos
  • Workflow Builder
  • Documentação pública, sandbox, SDKs, servidor MCP (Model Context Protocol)
  • Apoio da comunidade
Mais popular
Pague por utilização

Baseado na Utilização

Pague apenas pelo que usa. Mais de 25 módulos. Preços públicos por módulo, sem taxa mínima mensal.

  • KYC completo por $0.33 (ID + Biometria + IP / Dispositivo)
  • Mais de 10.000 conjuntos de dados AML, sanções, PEPs, notícias desfavoráveis
  • Mais de 1.000 fontes de dados governamentais para Validação de Base de Dados
  • Monitorização de Transações por $0.02 por transação
  • KYB em tempo real por $2.00 por empresa
  • Rastreio de Carteiras por $0.15 por verificação
  • Fluxo de verificação whitelabel, a sua marca, a nossa infraestrutura
Empresarial

Empresarial

MSA e SLA personalizados. Para grandes volumes e programas regulados.

  • Contratos anuais
  • MSA, DPA e SLA personalizados
  • Canal dedicado no Slack e WhatsApp
  • Revisores manuais sob pedido
  • Termos de revenda e whitelabel
  • Funcionalidades exclusivas e integrações com parceiros
  • CSM nomeado, revisão de segurança, apoio à conformidade

Comece grátis → pague apenas quando uma verificação for executada → desbloqueie o Enterprise para um contrato personalizado, SLA ou residência de dados.

FAQ

Perguntas frequentes

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's a white-label KYC, in plain English?

It's an identity-verification product that runs under your brand, your colours, your logo, your domain, but uses someone else's verification stack under the hood. The end-user never sees the underlying vendor.

Two flavours you can ship:

  • Reseller, your business is identity verification (or a vertical wrapper of it). You charge customers a per-check rate that's higher than your cost, and the margin is the business model. Common for SaaS aggregators, niche compliance plays, regional resellers in markets the big vendors don't serve well.
  • Embedded, you're a SaaS / fintech / platform whose product includes KYC as one feature among many. You don't want your end-users to bounce into a Didit-branded flow mid-onboarding; you want the verification to feel like part of your product.

The Didit recipe handles both with the same Style Editor + per-workflow toggle.

What can I actually customise?

Six categories, all no-code via the Business Console Style Editor:

  • Colours, buttons, text, panels, backgrounds. Every colour element is a token.
  • Typography, fonts that match your brand. Upload custom font files or pick from a curated list.
  • Logos, square and rectangular logo uploads. Used on hosted screens, in-app SDK headers, and email confirmations.
  • Layout, border radius for panels and buttons. Match your design language (sharp corners or rounded).
  • Login screen, show or skip the Didit login screen at session start.
  • Custom domain, host on verify.yourbrand.com instead of verify.didit.me. CNAME + TLS handled inside the Console.

The Style Editor previews live as you change tokens. Once you save, toggle Include custom style on the workflow you want branded, that's the activation gate.

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.

Does the white-label cover the SDKs too?

Yes. The same Style Editor configuration applies across all five Didit SDKs, Web (React, Vue, vanilla JS), iOS (Swift), Android (Kotlin), React Native (TurboModules), and Flutter (Dart). The SDKs are free; the white-label fee covers branding across every surface.

In practice: you set colours, type, logos, and radius once. The SDK reads the same brand config from your account, the hosted flow reads the same config, and your end-user gets a consistent branded experience whether they're in a mobile app, a webview, or a desktop browser.

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.

Do I keep the underlying compliance attestations?

Yes. Swapping the brand does not change the underlying compliance posture:

  • iBeta Level 1 PAD, Didit's Passive Liveness is iBeta Level 1 certified, meaning it has been independently tested against printed photos, screen replays, masks, and deepfakes
  • Tesoro / SEPBLAC, Didit is the only identity provider formally attested by Spain's Tesoro (under SEPBLAC, Spain's financial-intelligence unit) as a safer-than-in-person verification mechanism, for purposes of the EU Anti-Money-Laundering package
  • SOC 2 Type 1, independent audit of Didit's security controls
  • ISO/IEC 27001, international security-management standard
  • GDPR alignment, General Data Protection Regulation by design (data minimisation, lawful basis, DSAR support)

Under your white-label, all of these flow through to your customer. Didit provides sub-processor disclosure on request for your DPA (Data Processing Agreement).

How does this fit with Didit's MCP server and the Workflow Builder?

Both are free, both work with the white-label add-on.

  • Workflow Builder, drag-and-drop composer for KYC + AML + KYB + Wallet Screening modules. Per-workflow Include custom style toggle lives here. Edit rules and module selection without redeploying your app.
  • Didit MCP (Model Context Protocol) server, exposes the same Didit primitives to AI coding agents (Claude Code, Cursor, Codex, Replit Agent, Devin, Aider). Useful for a small reseller team that wants to automate per-tenant workflow provisioning, branded-flow templating, or scripted onboarding tests.

The net: you don't need a large engineering team to ship a white-label KYC product. The Style Editor handles brand, the Workflow Builder handles modules, the MCP server handles automation, and the /v3/ API handles the verification itself.

How fast can a small team launch?

Four wires, one afternoon for a vertical-slice; a week for production:

  • Open business.didit.me, sandbox key in 60 seconds, no credit card
  • Enable the white-label add-on (talk to sales) and open the Style Editor, configure brand, upload logos, add custom domain (CNAME at your DNS provider)
  • Build the workflow in the Workflow Builder with the modules you ship (typically ID + Liveness + Face Match + AML), toggle Include custom style ON
  • Wire POST /v3/session/ + the signed webhook (X-Signature-V2 HMAC SHA-256) into your onboarding flow

For a multi-tenant reseller, add: one workflow per end-customer brand, per-tenant Style Editor configuration, a routing layer that picks the right workflow_id per inbound request. The MCP server scripts these end-to-end.

Infraestrutura para identidade e fraude.

Uma API para KYC, KYB, Monitorização de Transações e Rastreio de Carteiras. Integre em 5 minutos.

Peça a uma IA para resumir esta página