• Pricings

  • Research

    KYC Audit After Zero-Knowledge KYC: What Still Gets Checked

    November 20, 2026

    8 mins read

    A KYC audit still asks what was checked, from which source and when, even after zero-knowledge KYC. What changes and how to make the flow audit-ready.

    Orochi Network banner: What a KYC Audit Still Checks, Zero-knowledge KYC changes what you hold, not what the auditor asks, with a privacy lock and records icon
    A KYC audit checks that a firm knew who its customers were, kept the evidence and can show it on request. Zero-knowledge KYC lets a firm accept "this customer passed KYC" without holding the passport and the selfie. It does not remove the audit. A regulator or an internal auditor still asks what was checked, from which source, when, and who can show the evidence today.
    The record side of KYC is back in the news. The Travel Rule makes firms pass sender and receiver details along with a transfer, and the Recordkeeping Rule makes them keep those details. On 9 November 2026 the US Financial Crimes Enforcement Network (FinCEN) and the Federal Reserve Board withdrew a 2020 proposal that would have cut the threshold of both rules for cross-border transfers from $3,000 to $250, and would have clarified that they apply to crypto (convertible virtual currency). Commenters had argued that a lower threshold would raise the liability of firms "required to maintain personally identifiable information" (Federal Register, 91 FR 70824). The $3,000 rules stay, and so does the tension: firms must keep records, and every copy of identity data they keep is a risk.

    What zero-knowledge KYC changes and what it does not

    In a zero-knowledge KYC flow, a trusted party checks the customer's documents once. The customer, or a registry, then gives other firms a Zero-Knowledge Proof (ZKP) that the customer's credential meets a statement, such as "passed KYC with provider X" or "is not on the sanctions list", without the documents. A ZKP is a small piece of cryptographic data that anyone can check with a public key; it shows the statement holds without showing the data behind it. Our guide to zero-knowledge KYC for financial institutions covers how the flow works.
    What changes is what the relying firm holds: an answer and a proof instead of a file. What does not change is who answers to the regulator. The Financial Action Task Force (FATF), which sets the global anti-money laundering standards, is clear in its 2020 Guidance on Digital Identity that when a firm relies on someone else's checks, "the ultimate regulatory responsibility for CDD measures remains with the regulated entity" (para 95). The audit questions follow the firm, not the documents.

    What a KYC audit still checks

    The FATF guidance and the Travel Rule give the list. It does not depend on how the customer was onboarded.
    • Customer due diligence (CDD) evidence. Proof that the firm identified the customer and checked that identity against a reliable source, at the risk level the customer carries.
    • The record behind each check. FATF says its record-keeping standard, Recommendation 11, applies to digital records too, including the type of evidence, its source and the date and time of the check (para 43).
    • Reliance on a third party. A firm that relies on another firm's KYC must get the needed information immediately and be able to get copies of the evidence on request without delay (paras 94 to 96).
    • Ongoing due diligence. Under FATF Recommendation 10, the customer's status has to be kept current. A KYC result from two years ago is not evidence about today.
    • Travel Rule data. The Travel Rule in crypto works as in banking: on qualifying transfers, the sending firm passes originator and beneficiary (sender and receiver) information to the next firm in the chain, and both keep a record of it.

    How the audit answers change

    The table puts the same audit questions to a firm that holds the documents and to a firm that holds only a zero-knowledge KYC result.
    Audit questionFirm holds the documentsFirm holds a zero-knowledge KYC resultWhat is missing without a record
    What was checked?The file: ID, address, screening resultsA yes or no answer and the policy it was checked againstWhich checks ran and under which policy version
    From which source, and when?Document details and timestampsThe issuer of the credential and the time of the proofEvidence type, source, date and time (FATF para 43)
    Can you show the evidence on request?Pull the fileAsk the KYC provider or credential issuerCopies "without delay" depend on a third party's systems (paras 94 to 96)
    Is the customer still valid today?Re-check the documentsCheck the credential's statusWhether the answer was current when the account acted
    What went out with a transfer?Originator and beneficiary dataThe same required data, plus fewer extra copies for parties that only need a yes or noA record of what was sent, to whom, and when
    Every row has the same gap. The zero-knowledge flow gives a good answer to "is this customer verified?" but the audit asks a second question: show me the record that answer came from, as it was at the time.

    A verified flag is not evidence

    A credential or a proof shows that someone checked something. It does not show that the record behind the check was kept as claimed. The W3C standard for digital credentials says it plainly: "Verifiability of a credential does not imply the truth of claims encoded therein" (W3C, Verifiable Credentials Data Model v2.0, May 2025). Our post on how banks check verifiable credentials covers the issuer, holder and verifier roles.
    For an auditor, the weak point is the link between the answer and the stored record. If the KYC provider's database can change after the fact, a "passed" result from March cannot be tied to what the record said in March. If the link is checkable, the firm can show which record version each answer came from, and that nobody edited it later. That is the part of the evidence a proof can carry without moving personal data.
    Flow of an audit-ready zero-knowledge KYC record, from record update and proof to the auditor's own check Each yes or no answer points to a record version an auditor can check without seeing the customer's data.

    How to make a zero-knowledge KYC flow audit-ready

    Six steps, in order. Each one depends on the step before it.
    1. Map each answer to the rule it serves. List every yes or no the flow produces (identity verified, sanctions clear, accredited, Travel Rule data sent) and the rule behind it. The auditor will test against that map, so it comes first.
    2. Keep the evidence trail at the source. The documents stay with the KYC provider or credential issuer, with evidence type, source, date and time recorded. The reliance contract states how fast the firm gets copies on request.
    3. Give every record update a proof. Each time the KYC status record is written or changed, a ZKP is generated and a commitment to the new record state is published, for example on a blockchain. A commitment is a short fingerprint of the whole record: anyone can hold it, nobody can read the record from it, and any later edit gives a different fingerprint. Edits after the fact now show up.
    4. Link each decision to a record version. The onboarding or transfer decision stores which proof and which committed state it relied on. The firm can now answer "what did you know at the time?" with a version, not a story.
    5. Treat status changes as new versions. Periodic review, revocation and new sanctions hits create a new committed state. An answer based on an old state fails the check, so stale KYC shows up before the auditor finds it.
    6. Give the auditor a check path. The auditor checks the proofs against the published commitments on their own, without access to personally identifiable information (PII). When the audit needs the documents, the firm gets them from the source through the reliance arrangement in step 2.
    None of this makes a firm compliant on its own. It gives the auditor evidence they can check rather than accept, next to the audit work they already do.

    Where zkDatabase fits

    zkDatabase is a verifiable database powered by Zero-Knowledge Proofs, and decentralized identity and private KYC is one of the use cases it is built for. It generates a proof for every insert and update to a KYC status record, so an auditor can check that the record behind each yes or no answer was stored and processed as claimed and was not changed later. The verifying firm checks the proof without needing to hold the PII.
    Three mechanisms map to the audit-ready steps. A membership proof lets a customer show they are in the set of valid credentials without revealing which credential they hold or any personal data. Revocation publishes a new committed set, so a proof against the old set no longer passes. For Travel Rule flows, selective disclosure lets a party that only needs the compliance answer get it without a copy of the personal data; the data the rule requires still goes to the counterparty firm. The proof covers how the record was stored and processed. Whether a document was genuine stays with the KYC provider's checks, as it does today.
    For the wider view of how proofs fit regulatory work, see our guide to Zero-Knowledge Proof compliance. For one KYC result reused across firms, see reusable KYC.

    Plan an audit-ready KYC flow

    Talk to our team about proving your KYC records to auditors without moving customer data.