Skip to content
Free guide: How to use AI in compliance

Certificate of Insurance Verification

Certificate of insurance verification that checks the state record, not just the PDF

A certificate of insurance says what a vendor had on the day the broker issued it. Zyphe reads the ACORD 25, checks the named insured is really your vendor, works out whether the state requires workers' compensation for that trade and workforce, and in Florida confirms the policy or exemption on the state's own record. Each credential comes back with one status, its source and its expiry date, so your platform can decide whether the vendor works.

Certificate of Insurance Verification verification

What is certificate of insurance verification?

Certificate of insurance (COI) verification is checking that the insurance a vendor or contractor claims is real, current and theirs. It goes beyond collecting the certificate: the named insured must match the business, the policy must be in date, and for workers' compensation the coverage should be confirmed with the state, because a certificate can be outdated, cancelled after issue, or made out to another company.

Trusted by those who trust no one.

āltitude
Protocol Labs
ETHDENVER
EBSI
Filecoin
XEurope
Bondex
Supra
Yescoin
Twotixx

4.9/5 from 9 customer reviews

  • “Zyphe has completely transformed how we handle KYC data, allowing us to seamlessly share identity information with other financial participants while ensuring that users retain full control over their personal data.”
    Milo Guastamacchia · 5/5 Yooro CEO and Co-Founder
  • “Zyphe has made a big difference in how we approach attendee verification and data security. With decentralized storage for greater privacy, AI-driven identity verification for global check-ins, and audit-ready KYC, we have managed to reduce how much PII we need to handle while having a better user experience. It is easier for us to comply with regulations like GDPR and CCPA.”
    Kelvin Rolf · 5/5 Twotixx CEO and Co-Founder
  • “As a non-custodial wallet, we require every user to complete KYC while also integrating with multiple regulated partners, each with their own compliance requirements. Zyphe gave us a centralized way to collect and manage user identity data while securely sharing it with our partners, significantly reducing friction throughout the onboarding journey.”
    Gonzalo del Cerro · 5/5 Vesseo Head of Product
  • “The KYB feature stands out with a good UI and a lot of information like UBO and financials. I also appreciate that their compliance features offset efforts from my compliance team, which is very helpful.”
    Sam M. · 5/5 Executive, small business
  • “I like the ease of use and the security that Zyphe provides. It has a clean user interface on both the admin and user side. The integrated one-click KYC feature makes the whole experience super fast. The initial setup was easy because they set up everything for me.”
    Fausto D. · 5/5 Owner, mid-market business
  • “The availability of the staff and the ease of integration.”
    Alessandro R. · 5/5 CEO, small business
  • “I use Zyphe's KYC service and agentic compliance service. My users can be verified in a seamless way, and we use their AI agents to support our compliance team. Zyphe was integrated in no time, just the time to open an account and install their SDK.”
    Stefano D. · 5/5 CTO, small business
  • “I think Zyphe is fantastic because of its user interface, which is really good when onboarding documentation. I also appreciate how it enables us to share KYC checks externally. And honestly, the support team is amazing.”
    Ignacio P. · 4.5/5 Small business
  • “I like that Zyphe provides an end-to-end solution for KYC, KYB, and AML case files, integrating seamlessly into our existing stack with documented audit trails for each decision. Additionally, I appreciate the excellent customer support that prompted us to switch from Onfido. The initial setup of Zyphe was super easy, which was a big plus.”
    Gunja G. · 4.5/5 Senior Loan Processor, mid-market business

Two credentials, checked the way an auditor would

General liability comes from the certificate. Workers' compensation starts from the state's rule and ends at the state's record wherever that record can be searched.

ACORD 25 read and matched

The certificate is read field by field. The named insured is compared with your vendor's legal name, ignoring case, punctuation and legal form, so a certificate made out to another business is caught instead of filed.

Workers' comp rule by state

Whether a policy is required depends on the state, the trade, the business form, the employees and the working owners. Zyphe applies the rule first, so a vendor below the threshold is not blocked for a policy the law does not ask for.

Confirmed at the source in Florida

Florida's Proof of Coverage and Exemption records are searched by business name and FEIN. The state record decides over the certificate: a policy cancelled after the PDF was issued shows as lapsed.

One status your platform can act on

Each credential returns a status, the source it was checked against, when, and when it expires, with typed reasons. Only Confirmed at the source and Not required let a vendor work unattended.

How certificate of insurance verification works

Add the certificate to a KYB flow so every vendor is checked as part of onboarding, or run a single check from the dashboard.

The vendor uploads an ACORD 25 in your onboarding flow, with its profile: business name, state, trade, business form, employees and working owners. Your team can also run one from the dashboard.

General liability is taken from the certificate and checked for dates and named insured. The workers' compensation rule for the vendor's state, trade and workforce decides whether a policy is required at all.

Where the state's record can be searched, as in Florida, the policy or the owners' exemptions are confirmed there, and the record overrides the certificate. Anything only a person can decide is marked Needs review, never guessed.

The statuses are written to the case and delivered on the KYB webhook, one entry per credential with its source and expiry date, so your platform can lock or release the vendor's jobs on its own side.

How certificate of insurance verification works visual

The six statuses

Every credential ends in one of six statuses. They are designed so a platform can automate the clear cases and route the rest to a person.

Confirmed at the source
A policy in force on the state's record. The vendor can work.
Not required
Below the state's threshold for the trade and workforce, or, where the only workers the state counts are owners, a recorded exemption in force for each of them. An owner's exemption never removes the cover the vendor's employees need. The vendor can work.
Extracted only
The certificate shows cover in date, but no state record confirmed it.
Expired
Lapsed on the state record or on the certificate.
Missing
No certificate, no line for this cover, not an ACORD 25, or made out to another business.
Needs review
The record shows something only a person can decide, such as an exemption whose owners were not named, or a policy without dates. The vendor does not work unattended meanwhile.

Workers' compensation thresholds by state

The thresholds Zyphe applies today, counting employees and, where the state counts them, working owners. Exemptions for officers and LLC members change the count; Zyphe accepts one only when every working owner is named and holds an exemption in force, of the right type, covering the trade.

Workers' compensation: when a policy is required, and where Zyphe confirms it
StateConstructionOther tradesConfirmed on the state record
Florida1 or more4 or moreYes, Proof of Coverage and Exemption records
Alabama5 or more, except builders of new single-family homes, who need cover at any size5 or moreNot yet, certificate only
Georgia3 or more3 or moreNot yet, certificate only
Tennessee1 or more5 or moreNot yet, certificate only

A summary for orientation, not legal advice. Each state's statute defines who counts and which exemptions apply. Zyphe's rule does not yet treat Alabama new-home building as its own trade, so review those vendors as needing cover.

COI tracking or COI verification?

COI tracking software stores certificates, reminds vendors before they expire and keeps a log. That answers whether you have a certificate on file. It does not answer whether the certificate is true today.

Verification is the step tracking skips: matching the named insured to the vendor, deciding whether the state requires the cover at all, and confirming the policy with the state instead of trusting the PDF. Zyphe does the verification and sends the result to your platform, which can keep using its own tracking or vendor management tool.

Integrate in as little as 15 minutes

curl -X POST https://verify.zyphe.com/v1/login_sessions \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{"auth_type": "email"}'

Frequent Questions

The ACORD 25 is the standard certificate of liability insurance used in the United States. A broker issues it to show the policies a business held on the day it was issued: general liability, auto, umbrella and workers' compensation, with insurers, policy numbers and dates. It is evidence of insurance, not the policy itself, and it does not change if the policy is cancelled afterwards.

Yes. A certificate can be edited, issued to a different business, or describe a policy cancelled after the PDF was produced. That is why Zyphe checks the named insured against your vendor and, for workers' compensation in Florida, confirms the policy on the state's record, which overrides the certificate.

Florida's Division of Workers' Compensation publishes Proof of Coverage and Exemption records that can be searched by business name or FEIN. Zyphe searches both automatically for each Florida vendor, reads the effective and expiration dates, and returns Confirmed at the source only for a policy the record shows in force. How to check Florida proof of coverage

Florida today. For Alabama, Georgia and Tennessee Zyphe applies the state's threshold rule and reads the certificate; their records are next. Outside those four states the certificate is read and matched against your vendor.

Not yet. Broker confirmation and license-board lookups are on the roadmap. Today the sources are the certificate itself and, where available, the state's workers' compensation record.

On the KYB webhook, for checks run inside an onboarding flow, and on the case in the dashboard. A check your team runs from the dashboard can be attached to the vendor's KYB case so the next webhook carries it. Each credential carries its status, the source it was checked against, the date checked, the expiry date and typed reasons your platform can map to its own wording.

KYB verifies that the business exists and who owns it. Insurance verification checks that the same business carries the cover your platform requires before it takes work. They run in the same flow: add the ACORD 25 to a KYB flow and the statuses land on the same case. Explore KYB Software