From the team
Research and product notes on identity, fraud, compliance infrastructure, eIDAS 2.0, MiCA and AMLD6.
Identity Verification
Real ID. Matching selfie. Clean liveness. You approved the account, and it belongs to a fraudster. Your checks never looked at who was holding the document. This is how that happens, what it costs you, and how silent capture closes the gap.
Product Updates
Manage team access, environments and cost controls deliberately. Give each teammate the permissions needed for their job and keep Sandbox preparation separate from Production activity.
Product Updates
Test the complete integration, including failures and recovery. Choose the supported fixture for the API family you use, then inspect both Toden’s record and your application’s behaviour.
Product Updates
Receive Toden results reliably with a signed webhook receiver. Verify the exact bytes, store each event durably and recover retries without repeating the customer action.
Product Updates
Connect the customers already in your application to Toden records using stable references. Retain what you know about their verification source rather than upgrading imported claims into verified facts.
Product Updates
Add verification to your app using a published workflow and a supported SDK or hosted session. Keep capture in the customer journey and final result handling on your backend.
Identity Verification
Verify a business against a supported registry and choose the additional evidence your onboarding policy needs. Company existence and authority to represent it are different questions.
Identity Verification
Verify address presence over a supported observation window. Configure capture, native reporting and customer consent together, then distinguish verified, failed and inconclusive evidence.
Identity Verification
Review the address evidence already in your customer book. Upload a permitted CSV, inspect the quote and use the resulting grades to choose the right next capture or presence check.
Risk & Compliance
Keep crypto destination records and deposit observations organised. A deposit observation, customer match, screening decision and settled funds are separate facts.
Risk & Compliance
Set up your organisation’s Travel Rule information-exchange journey, test it and follow the displayed activation requirements. Every transfer still needs its own current authorisation before your wallet acts.
Risk & Compliance
Screen a saved crypto wallet and inspect the decision with its exposure evidence. Keep blockchain risk, address approval, signed control and transfer clearance separate.
