Accept Google Wallet ID in your onboarding flow: integration guide
Blog post from Didit
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.
Didit supports Google Wallet ID verification through either a hosted workflow, which includes document capture as a fallback, or a standalone API for custom websites and Android apps. The service is available in the United States, United Kingdom, Brazil, Singapore, and Taiwan, and requires developers to configure the requesting origin; each production application must also be registered with Google once, while sandbox testing needs no registration and uses simulated credentials. In the standalone integration, the backend starts the request, the user approves sharing through a wallet prompt, and the backend submits the response for verification; the hosted flow manages these screens and can offer document capture when wallet verification is cancelled, expires, or fails. Didit checks credential signatures and returns identity attributes and a verification outcome through its API or webhook, but an account should be approved only after the backend confirms a completed, verified result. Completed wallet checks are billed, while incomplete attempts are not, and any document fallback is charged separately.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Vector Search | 1 | 1,251 | 223 | 92 | -37% |
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.