Question 1

We already use Smile ID. Is switching disruptive?

Accepted Answer

No. Existing verified customers import in bulk with their verification status intact and immediately begin screening and monitoring. Nobody re-verifies, and your back book is being watched from day one.

Question 2

How exactly do we migrate from Smile ID?

Accepted Answer

Four steps, and the first two commit you to nothing. One, take an instant sandbox key and build against the test catalogue, which publishes a working ID for every failure outcome. Two, export your already-verified customers and import them in bulk; they arrive with their verification status intact and immediately begin screening and monitoring, so nobody re-verifies. Three, run both platforms in parallel on live traffic and compare outcomes on your own users. Four, cut over by pointing the SDK, hosted link or API at us. A solutions engineer maps your existing approval rules into a workflow and stays on the parallel run, with no professional-services invoice attached.

Question 3

Is your verification quality comparable?

Accepted Answer

Yes, and ahead on evidence. Chip authentication is verified server-side against the issuing government's signature, liveness recordings are re-analysed rather than trusted from the device, and every verification returns an assurance level telling you how strongly it passed.

Question 4

What do we gain that we do not have today?

Accepted Answer

Behavioural monitoring, alert rollup, investigation cases with SLA tracking, goAML filing with four-eyes separation, perpetual re-verification and a versioned decision graph with an audit trace. All of it on the same record as the verification.

Question 5

Can we keep verifying in the same markets?

Accepted Answer

Yes, with authoritative database validation in the same core markets, plus document and chip verification across 190+ countries on top.

Question 6

Do we need a separate case management tool?

Accepted Answer

No. Cases are core product, with priority-driven SLA deadlines, assignment and an immutable investigation record. Bolting a ticketing tool onto a verification vendor gives you neither the deadlines nor the audit trail.

Question 7

Can our compliance team write rules themselves?

Accepted Answer

Yes, as configuration in the dashboard, backtested against your own stored history before going live. No engineering release required.

Question 8

How is pricing structured?

Accepted Answer

Per component and fully itemised. Every verification shows which checks ran and what each cost, with no minimum commitment and no platform fee underneath it.

Question 9

What does an auditor actually see?

Accepted Answer

One customer record carrying every ID presented, every check, alert and case on a single timeline, secured by a tamper-evident hash chain proving no entry was altered or removed.

Feature
Costs and pricing	Per-component pricingincluded No minimum commitmentincluded Cheaper at the same volumeincluded Sandbox never chargedincluded	Costs rise as you add vendorslimited Published per-check pricingincluded Volume tierslimited Compliance tooling bought elsewherenot offered
Commercial flexibility	Pay only for checks that runincluded No platform feeincluded Nothing locked behind a tierincluded	Pay-per-checkincluded Verification only, so the stack growslimited
Integration speed	Instant self-serve sandboxincluded Test ID for every failure outcomeincluded SDKs, hosted links and direct APIincluded	Self-serve sandboxincluded SDKs availableincluded
Workflows and SDK	No-code workflow builderincluded Versioned, publish without a releaseincluded One SDK for every componentincluded Hosted link needs no integrationincluded	Flow configuration limitedlimited Separate SDKs per capabilitylimited Biometric re-auth not documentedlimited
Verification and biometrics	Face match 1:1included Active liveness, re-analysed server-sideincluded Chip authentication verified server-sideincluded Biometric re-authentication built inincluded Assurance level on every resultincluded	Face match 1:1included Active livenessincluded Chip authentication not documentedlimited No assurance level returnednot offered
After onboarding	Transaction and session monitoringincluded Rules your compliance team writesincluded Investigation cases with SLA trackingincluded Perpetual re-verificationincluded Address presence verification & monitoringincluded	No transaction or session monitoringnot offered No investigation casesnot offered No rule authoring for compliance teamsnot offered
Regulatory reporting	goAML SAR and STR generationincluded Filing-ready XML exportincluded Four-eyes separation enforcedincluded	No goAML generationnot offered No filing workflownot offered
The audit record	One customer record end to endincluded Tamper-evident hash chainincluded Versioned decision traceincluded	No tamper-evident audit chainnot offered Verification records onlylimited
Coverage	190+ countries, 48 KYB, 200+ screening jurisdictions	Regional focus, document coverage beyond

The Smile ID alternative,same verification depth,plus the compliance engine.

What you gainby moving.

The obligation continues after onboarding

From alert to filed report, without leaving

Coverage that follows your users

Myaza Trust vs Smile ID,line by line.

Myaza Trust vs Smile ID,questions.

Test it on your own traffic,not on our table.