How kyc0 compares KYC vendors

01 / Evidence ladder

Evidence standards for KYC research

Country requirement summaries rely on Level A. Feature and public-price facts rely on Level B. We do not convert a vendor’s accuracy claim into an editorial fact.

02 / Comparisons

How a KYC vendor comparison is built

1. Define the buyer scenario: sector, markets, product, volume, customer types, fraud exposure, and operations team.
2. Set an evidence cutoff date and record the exact official pages checked.
3. Normalize scope: identity verification, KYB, screening, monitoring, case work, and orchestration are evaluated separately.
4. Record public pricing without filling private fields from third-party estimates.
5. Separate qualifying facts from fit judgments and state the conditions behind each judgment.
6. Specify a buyer-run test whose outcome could overturn the desk recommendation.
7. Send factual corrections through the correction process; vendors do not approve conclusions.

Default decision dimensions

• Regulatory and evidence fit for the buyer’s jurisdictions
• Completion and decision quality for the actual document and device mix
• Fraud controls, reason codes, and escalation paths
• Workflow, case, audit, retention, and deletion operations
• Developer integration, failure handling, and change management
• Commercial terms and effective cost per approved customer
• Support, incident response, portability, and exit risk

03 / Pricing protocol

KYC price snapshots need a date and denominator

A public price is transcribed from the vendor’s current official page and stored with the plan name, currency, unit definition, minimum commitment, visible inclusions, and check date. We avoid scraped reseller tables when the vendor is the better source.

Quote comparisons use total vendor charges plus internal manual-review labor. The preferred denominator is an approved customer, not an API call. Taxes, fraud losses, implementation, unused prepaid volume, and overage rules remain separate unless the input supports them.

04 / Country requirements

Country KYC research starts with scope

“KYC requirements in a country” is too broad to be a legal answer. Each page identifies the covered entity or sector, the primary instrument, trigger events, identity data, verification standard, beneficial-owner treatment, ongoing duties, records, and live transition rules.

Every substantive rule links to the legislation or regulator. We label inference and implementation advice separately from legal summary. Country pages are information, not legal advice.

05 / Freshness

When KYC research is reviewed again

• A new act, rule, amendment, regulator notice, implementation date, or formal guidance update.
• A vendor price, plan, ownership, product name, material capability, or documentation change.
• A correction with enough evidence to alter a factual statement or fit judgment.
• A scheduled source check: high-change comparison and transition pages first, then stable pages.

The visible review date means the cited source set was checked. It does not guarantee that no unpublished contract, local interpretation, or later event exists.

06 / Revenue

Partner revenue does not set KYC rankings

kyc0 may earn a fee from clearly marked referral links. Commercial availability does not determine inclusion, order, fit judgment, or criticism. A vendor can be recommended without a commercial relationship, and a partner can receive a negative conclusion.

Sponsored placement is not inserted into comparison rankings. Any paid placement would be labeled as advertising and kept outside the editorial table.

07 / Corrections

Corrections require a source and effective date

Send corrections to research@kyc0.com with the page URL, disputed sentence, primary source, and effective date. We correct material errors and update the review date when the source set is rechecked. Disagreement with a stated fit judgment is considered, but does not by itself establish a factual error.