Document provider detection

How Certivant matches supporting documents (bank statements, utility bills) against a global gazetteer of banks and utility providers to corroborate document type and flag country or type mismatches in verification results.

When a verification includes a supporting document — a bank statement, a utility bill, an electricity statement, an invoice, or a pay slip — Certivant matches the document's OCR text against a global gazetteer of banks and utility providers. A recognised provider corroborates that the document is what it claims to be; a provider that contradicts the claim is surfaced for review. This runs automatically; there's nothing to call.

What the gazetteer contains

Provider typeSource
Banks (name + SWIFT/BIC)GLEIF (CC0), Wikidata
ElectricityWikidata utility classes, US EIA (Form EIA-860), curated
Telecom · gas · water · ISPWikidata, curated

Provider names are matched fuzzily (OCR-tolerant), and bank SWIFT/BIC codes are matched exactly when they appear in the text. The gazetteer is reference data only — no customer data ever enters it.

How it affects a verification

Detection is a corroborating signal, never a gate. The gazetteer can't be exhaustive, so the load-bearing rule is:

  • Match that agrees → positive signal. A recognised bank on a bank_statement, or a recognised utility on a utility_bill, confirms the document type and contributes a small trust bonus.
  • Match that contradicts → routed to human review (escalate), never an automatic rejection.
  • No match → neutral. A document from a provider we don't list is neither penalised nor rejected.

Signals you may see in results

These codes can appear in the verification's review triggers and fraud signals (visible in the dashboard and in the verification webhook payload):

CodeWhereMeaning
provider_type_mismatchreview triggerA confident provider match of the wrong kind for the slot — e.g. a telecom provider on a document submitted as a bank statement (it's really a phone bill). The verification escalates for review.
provider_country_mismatchreview trigger + fraud signalA recognised provider whose country differs from the applicant's claimed or document country — e.g. a US bank statement for an applicant verifying as Canadian. Escalates for review; never auto-rejects, since a legitimate foreign account is possible.

A confirmed match that agrees with the expected type contributes a positive trust signal instead — you won't see a distinct code for it, but it lifts the trust score.

Tuning

The matcher is deliberately conservative — it requires distinctive, multi-token name matches (or an exact BIC) above a confidence floor, so unrelated text never produces a false provider match. Threshold tuning and gazetteer coverage are managed by the platform operator; if you believe a legitimate document is being flagged, share the (redacted) provider name with your account contact so the curated list can be extended.