Co-founder
Charles Archibong co-founded Myaza Trust. He writes about identity verification, financial technology, and the practical work of building trusted digital services.
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 Myaza’s record and your application’s behaviour.
Product Updates
Receive Myaza 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 Myaza 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.
Risk & Compliance
Measure decision quality using confirmed downstream outcomes. Review fraud capture and customer friction without silently changing the live policy.
Risk & Compliance
Turn a risk alert into owned casework. Review the reason, gather evidence and record a clear outcome that the next team member can understand.
Risk & Compliance
Read customer risk with its evidence and assessment basis. Customer risk helps explain a customer’s recorded state; it is different from the risk decision for a specific payment.
Risk & Compliance
Assess transaction risk before your application moves money. Submit an exact amount, the right direction and the parties involved, then use the decision and its explanation.
Risk & Compliance
Assess logins, account recovery and other non-payment activity. Send the actual customer and device context, read the returned decision and enforce it in your own app.
Risk & Compliance
Continuous monitoring rechecks selected customer evidence over time. Configure a policy, enrol eligible customers and give material changes a clear review owner.
Risk & Compliance
Screen customers for sanctions, politically exposed person and adverse-media findings. Start with a correctly linked customer, run the supported checks, then review possible matches with the evidence available.
Identity Verification
Investigate connections that may explain suspicious activity. Shared devices, instruments and locations help you ask better questions; they do not establish that every connected customer is the same person.
Identity Verification
Use organisation lists to apply reviewed evidence consistently. Keep the decision to add an entry separate from the rules that decide what a list match does.
Identity Verification
Search an authorised face photo against the eligible faces in your organisation. Use this for investigation and review, and keep it distinct from comparing two photos or proving a login.
Identity Verification
Ask an existing applicant to redo a finished verification, either fully or only for selected steps. Re-verification keeps the verification ID and records a new attempt so your team can explain what changed.
Identity Verification
Compare two face photos when you need a 1:1 similarity verdict. This check is separate from liveness and from searching a customer book.
Identity Verification
Protect a returning-customer journey with a subject-bound face re-authentication workflow. Compare the current live capture with an eligible enrolment or an authorised reference photo, then let your backend decide whether to continue the login.
Identity Verification
Collect a map pin and the address details your team needs. Address Intelligence corroborates available evidence and explains its strength; a customer’s typed address remains their claim.
Identity Verification
Collect the declarations your policy needs, such as source of funds or expected activity. A questionnaire gives you recorded customer answers; it does not independently verify those answers.
Identity Verification
Verify contact access with an email or phone code. Use the workflow step for capture journeys, or the standalone API when your app needs a separate contact check.
Identity Verification
Device Intelligence adds context from the device and network used during capture. Configure the findings your team cares about and use them with other evidence rather than treating every shared device as fraud.
Identity Verification
NFC verification adds authenticated chip evidence from a supported passport or identity card. Set it up in a mobile capture workflow and understand when the result can, and cannot, raise assurance.
Identity Verification
Liveness helps establish that a real person is in front of the camera. Enable it in the workflow customers use, choose a method, and route captures your policy cannot accept.
Identity Verification
Verify a new customer with a published individual workflow. The customer completes the document and selfie journey; your backend receives the outcome and applies your onboarding policy.
Identity Verification
Set up face search in your onboarding workflow, decide what happens when one person uses another account, and check that your app handles the result.
Product Updates
Matching a face to one document is a contained problem. Searching it against every identity a business has verified is not. Why our fraud work is becoming a compute problem, and why Myaza Trust has joined NVIDIA Inception.
Product Updates
You can replace the “Protected by Myaza” footer on every verification screen with your own logo. It costs $0.10 per production verification, and your organisation needs $750 of paid credit the first time a custom logo goes live. After that, anyone on your team can change it at any balance.
Risk & Compliance
Perpetual KYC means refreshing a customer's record when something changes, not re-checking everyone on a calendar. The FATF asks that CDD data be kept up to date, particularly for higher-risk customers; events and risk decide when and how much you ask for.
Risk & Compliance
Wallet screening catches addresses that a sanctions authority has published, matched exactly. It misses unlisted addresses controlled by the same person, funds that passed through intermediaries, and anything published after your last check.
Risk & Compliance
A PEP match means you must confirm the person and classify them, not refuse them. Foreign PEPs always need senior management approval, source of wealth and funds, and enhanced monitoring; domestic PEPs need it only when your risk assessment says the relationship is higher risk.
Risk & Compliance
Most sanctions false positives come from thin customer data, not oversensitive matching. Screen with verified date of birth, nationality and ID numbers, record why each match was cleared so it does not return, and leave fuzzy matching alone.
Risk & Compliance
In June 2025 the FATF revised Recommendation 16: standard originator and beneficiary data above USD/EUR 1,000, a defined start to the payment chain and new checks against misdirected payments. Countries are expected to implement by the end of 2030.
Risk & Compliance
The Travel Rule requires the sending VASP to collect originator and beneficiary information, pass it to the receiving VASP immediately and securely, and make it available to authorities. The hard parts are finding the counterparty, handling self-hosted wallets and jurisdictions that disagree.
Risk & Compliance
The FATF's seventh targeted update, published 16 July 2026, finds most jurisdictions now have Travel Rule laws but few enforce them, and asks VASPs to strengthen wallet screening, unhosted-wallet due diligence and scrutiny of offshore platforms.
Risk & Compliance
On 19 June 2026 the FATF added Bosnia and Herzegovina and Iraq to its grey list and removed Algeria and Namibia. A grey listing is a risk factor to weigh, not an instruction to apply enhanced due diligence or to exit a market.
Identity Verification
People abandon verification at predictable moments: an unexplained start, the camera permission prompt, document capture, the desktop that has no camera, and being asked to redo everything after one failure. Measure abandonment per step, then fix the step, not the whole flow.
Product Updates
Ask for more than one ID when a single ID's weakness is exactly your risk, and choose IDs that come from independent sources. Then set the pass policy (all, at least two, or any one) by asking what you would accept if one check could not confirm.
Identity Verification
A reliable age check uses a date of birth established by an identity check (the government record, the document or its chip), compares it with a per-country limit, and fails closed when no date can be read. A typed birthday proves nothing, and a face gives an estimate with a margin of error.
Identity Verification
Where streets have no numbers, stop matching address strings. Capture a location (a map pin with the applicant's own directions and details), then corroborate it at the level of the area against independent records, and grade how strongly it is supported.
Identity Verification
A proof-of-address document shows that an address was printed on a document, often with a name, at a date. Give it the weight of corroborating evidence, not verification, and set rules for name, recency and document type that fit each market.
Identity Verification
Registration numbers are public, so anyone can type a real company's number. To know the applicant represents the business, verify who they are, check them against the officers the register names, and, where they are not named, ask for evidence of their authority.
