Loading help articles…
69 articles
Still need a hand?
Send the reference, environment and the step you need help with. Keep API secrets and identity documents out of your message.
Toden helps a business verify people and companies, investigate risk and keep track of changes after onboarding.
Use Sandbox fixtures to rehearse your verification journey and the outcomes your application must handle.
Understand the difference between an applicant, a session, a verification, a workflow and a decision.
Use a published Sandbox workflow and its hosted verification link to try the applicant journey.
Start with the organisation and environment, then open the records or configuration relevant to your task.
Select Sandbox and use the documented fixtures for the product you are testing.
Give your agent Toden’s current contracts and integration prompt, then review and test what it builds in Sandbox.
The MCP server searches the public documentation. It does not access your account or perform verification actions.
The verification’s status tells you its current outcome.
Read the current outcome, the automated findings, the workflow version and the latest attempt together.
Open the verification and inspect the failed finding, workflow decision or reviewer action that produced the decline.
In review means your workflow has asked a person to assess the verification.
An authorised reviewer can use Verify again or send a finished verification back for resubmission.
Check whether the applicant has submitted and, if so, what the workflow is waiting for.
Use the recorded identity or face-search evidence, then investigate the candidate records before deciding what a match means.
Check the source and capture quality, then request a fresh attempt when the applicant can correct the evidence.
Read authorised results from your backend and include only the evidence needed for the receiving process.
Use your account’s enabled configuration to choose countries and ID types, then check the workflow’s capture requirements.
A government-record check depends on the enabled country, ID type and workflow configuration; document analysis is a different method.
Choose a supported method for the evidence your business needs, and keep identity verification separate from crypto wallet screening.
Native mobile SDKs can read eligible identity-document chips, and Toden checks the submitted chip evidence on the server.
Separate the applicant’s declared address from supporting records, device presence and any multi-day presence result.
Check the capture, document type, file format, size and exact error before asking for another submission.
Liveness checks assess capture evidence for a live person. Read that finding separately from face matching and the final workflow decision.
Identify whether capture, liveness, comparison or a workflow decision caused the problem, then use the appropriate review or retry path.
A similarity score is judged against your recorded comparison policy; it is not a probability that an applicant is trustworthy.
Review the implemented checks and current assurance documents separately from independent certification claims.
A KYB workflow combines the company lookup with the application evidence and people checks your business configures.
Check country coverage, registry results and ownership evidence before designing a business onboarding flow.
Understand declared people, registry corroboration, role requirements and unresolved corporate ownership.
Distinguish queued checks, clear results, potential matches and confirmed matches before making a customer decision.
Understand screening categories and how to confirm the coverage your compliance policy requires.
Compare identifying evidence, document the review and keep screening adjudication separate from onboarding decisions.
Understand enrolment, policy frequency, customer overrides and the difference between pausing and turning monitoring off.
Read the recorded allow, review or block decision and understand the rule evidence and next action.
Read wallet risk, exposure and rule decisions without confusing a screen with ownership proof or a transfer.
Understand information requirements, assessment outcomes and the separate responsibilities for exchange and execution.
Create a draft, configure the applicant flow, test it and publish the version your integration will use.
Use workflow questionnaires for declarations and keep applicant answers distinct from verified evidence.
Design decision paths around the evidence your policy requires and test missing data as well as successful checks.
Keep full identity results on your backend and understand why fields differ across checks and attempts.
Configure logos, colours and copy on a workflow, preview the screens and check any paid branding conditions before publishing.
Learn the current hosted-domain limit and the supported way to keep verification inside your website or app.
English is built in. Learn how SDK custom texts work and the current limits of translated and hosted flows.
Choose the capture experience that suits your product while keeping final results and sensitive data on your backend.
Find the supported client SDK for your platform and check feature and version requirements before integrating.
Choose a reusable workflow link or a traceable per-applicant session, and handle each link as intended.
Set up the right webhook subscriptions, verify signatures and safely process retries and later status changes.
Start with the webhook delivery history.
Find the error code, check credentials and environment, and collect the right information for support.
Check your sign-in method, organisation membership and permissions without sharing passwords or API keys.
Choose the right environment and key type, store secrets safely and replace keys without disrupting integrations.
Invite the intended email address, choose a suitable role and understand the controls that protect organisation ownership.
Keep team membership, API credentials, workflows and test data in the right scope.
Use the organisation audit log to investigate administrative actions and distinguish it from API delivery logs.
Compare the same period, environment and channel, and understand why verification and workflow rates differ.
Understand prepaid credit, account-specific rates and the difference between a failed check and a system error.
For identity verification, charging follows the checks performed, not whether the applicant receives a positive decision.
Use your organisation’s Billing area, confirm the displayed amount and distinguish payment records from usage records.
Check the business’s available credit and the affected request or verification.
Review the documented encryption, credential scopes, signed notifications and team access controls.
Understand soft deletion, retained history and why removing a record is different from complete data erasure.
Find the current policy and request written answers about model training, processing purposes and contractual requirements.
Find published legal documents and request the DPA, subprocessor list and processing details your review needs.
Use the Trust Centre for Toden’s current assurance position and distinguish implemented controls from independent certification.
Toden supplies the verification flow used by the business that asked you to verify.
Check the message, fix capture problems where possible and ask the business that invited you about review or another attempt.
Understand the roles of the inviting business and Toden when you need an account decision or review explained.
Find the right privacy contact, understand controller and processor roles and request help without exposing your documents.