Didit vs GBG greenID: database checks beyond Australia and NZ

Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.

Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.

This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.

The comparison presents Didit as a broader, self-service alternative to GBG greenID for Australian and New Zealand organizations with international onboarding needs, while acknowledging that it is written by Didit. It states that greenID’s terms identify Australia’s Document Verification Service and New Zealand’s NZIICS among its database sources, with pricing and commitments negotiated through customer Order Forms, whereas Didit documents government or authoritative database checks across 45 countries plus a global category and publishes per-module list prices, including $0.33 for full KYC and $0.20 for AML screening. Didit also claims to combine identity verification, KYB, AML screening, transaction monitoring, crypto wallet screening, workflow design, and evidence retrieval in one account, with support for register-photo selfie matching in certain countries. The material contrasts Didit’s transaction-monitoring rules, wallet screening, AI-assisted investigation reports, workflow Copilot, MCP server, test mode, and linked business-owner KYC capabilities with features not documented on GBG’s public pages as of 25 October 2026. It recommends that prospective switchers review greenID contract obligations, map datasets and outcomes, test parallel traffic, and migrate gradually when their terms permit.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.