Lei Felcaに準拠。Felca対応の年齢確認で。

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.

Lei Felca is Brazil's child-protection law for digital platforms (sanctioned 2025, in force 2026). It demands that platforms hosting age-restricted content, adult, gambling, alcohol, certain social-media reach features, verify that users are old enough, with documented evidence retained for inspection.

The law was named after Felca (Felca Comazzetto), a Brazilian online-safety advocate whose campaign drove the bill. It sits alongside the Estatuto da Criança e do Adolescente (ECA) and the Lei Geral de Proteção de Dados (LGPD).

Any platform offering or hosting age-restricted features to Brazilian users:

• Social-media platforms, direct messaging, live streaming, public profiles for users under 16.
• iGaming and sports-betting, federally regulated by SIGAP under Lei nº 14.790/2023, age threshold 18.
• Adult content, 18+ hard gate.
• Alcohol e-commerce + delivery, 18+ gate at checkout.
• Influencer marketplaces / creator economy, verify minors who appear in monetised content.

Non-compliance fines reach 6 % of group revenue under the LGPD enforcement carry-over.

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.

Self-declared age has been struck down by every major regulator that's looked at it (UK Online Safety Act, France SREN, Germany Jugendmedienschutz-Staatsvertrag, Brazil Felca). The law requires the platform to take steps to verify, not just ask.

Effective age verification under Felca means a combination of:

• A capture event, selfie, document, or both.
• A model or document that produces evidence, Age Estimation confidence band or a date-of-birth field from a verified document.
• Audit-ready retention of that evidence for at least 5 years.

Didit's tiered workflow is the cheapest way to satisfy all three.

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.

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.

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.

• 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.

Hard block + log. The session status flips to Declined, your platform refuses access, and the event is piped to your Felca reporting line (typically a child-safety officer mailbox or your Ouvidoria channel). The event metadata includes:

• The Age Estimation result and confidence.
• The Internet Protocol (IP) country and device fingerprint.
• The session ID for traceability.
• The timestamp in BRT.

Didit doesn't surface any identifying detail of a confirmed minor in the marketing analytics layer, only the compliance evidence pack.

Felca's evidence-collection obligation runs through LGPD's data-protection regime:

• Lawful basis, Felca compliance is a legal obligation (LGPD Art. 7, V), so explicit consent isn't required for the age-check itself.
• Data minimisation, Didit's tiered flow only collects a document image when the age estimation isn't confident. Most users only contribute a selfie.
• Retention, default 5 years post-relationship, configurable per workflow.
• Subject rights, every artefact exportable on request, deletable when retention expires.
• Cross-border transfer, Didit's Sub-processors registry and standard contractual clauses cover the transfer.

Didit's Privacy Notice and DPA are drafted to satisfy both regimes simultaneously.

Brazilian regulated sports-betting and online casino operators (Lei nº 14.790/2023, regulated by SIGAP under the Ministry of Finance) face a hard 18+ gate on every signup and an additional onboarding obligation:

• ID Verification of the player.
• Face Match against the document selfie.
• AML Screening on deposits above the threshold.
• Self-exclusion register cross-check (where the operator participates in the Programa Jogo Responsável).

Didit's /solutions/igaming-responsible-gaming page covers the full operator-side recipe; the Felca page covers the platform-side age-gate that sits in front of it.