Real-time Identity Verification: Web Push Notifications

Optimize User ExperienceImplement web push notifications to provide immediate feedback on identity verification status, reducing user anxiety and improving conversion rates.

Technical ImplementationUnderstand the core components of web push notifications, including Service Workers, Push API, and Notification API, for effective integration.

Leverage WebhooksUtilize Didit's robust webhook system to trigger push notifications based on real-time verification status changes, ensuring accuracy and timeliness.

Didit's AdvantageDidit's modular, AI-native platform with its developer-first API makes integrating real-time identity verification status updates via web push notifications straightforward and efficient, enhanced by Free Core KYC.

In today's fast-paced digital world, user expectations for instant feedback are higher than ever. When a user submits their identity for verification, the waiting period can be a source of anxiety and lead to drop-offs. Imagine waiting for a crucial account to be activated or a transaction to clear, only to be left in the dark about its progress. This is where web push notifications become a game-changer for identity verification workflows. By providing real-time updates, businesses can significantly enhance user experience, reduce churn, and build trust.

The Power of Real-time Communication in KYC

Identity verification, often a critical step in Know Your Customer (KYC) processes, can sometimes take time. Whether it's due to document review, liveness checks, or AML screening, users appreciate transparency. Web push notifications offer a direct and unobtrusive channel to communicate the status of their verification. Instead of requiring users to constantly check an app or email, a push notification can instantly inform them:

• That their documents have been received.
• If their liveness check was successful or requires a retry.
• When their identity has been successfully verified (Approved).
• If additional information is needed (Resubmitted).
• If verification has been declined.
• When the status is "In Review" and awaiting a compliance team's decision.

This proactive communication reduces uncertainty, minimizes support inquiries, and keeps users engaged throughout the onboarding journey. For businesses utilizing Didit's ID Verification, Passive & Active Liveness, and AML Screening & Monitoring, integrating real-time feedback is a natural extension of a seamless user experience.

Understanding Web Push Notification Architecture

To implement web push notifications, you'll typically need three core components:

1. Service Worker: A JavaScript file that runs in the background, separate from the main browser thread. It intercepts network requests, manages caching, and, crucially for push notifications, listens for push events from the server.
2. Push API: This API, exposed to the Service Worker, allows your web application to subscribe to push services provided by the browser vendor (e.g., Google's FCM, Mozilla's autopush). It handles the secure delivery of messages to the user's device even when the browser is closed.
3. Notification API: This API is used by the Service Worker to display notifications to the user once a push message is received. It controls the title, body, icon, and actions associated with the notification.

On your backend, you'll need a server-side component capable of sending push messages to the appropriate push service endpoints. This component will be triggered by events, such as a change in a user's verification status received via a webhook.

Integrating with Didit's Real-time Status Updates

Didit's platform is built with a developer-first approach, offering clean APIs and robust webhooks that make real-time integrations seamless. Every verification session in Didit moves through distinct statuses: "Not Started", "In Progress", "Approved", "Declined", "In Review", "Resubmitted", "Expired", "Abandoned", and "Kyc Expired". These statuses are critical for triggering your web push notifications.

Here's a high-level workflow for integrating Didit with web push notifications:

1. User Initiates Verification: When a user starts an identity verification flow using Didit's Verification Links or API, a session is created.
2. Subscribe to Push Notifications: On your frontend, when the user opts in, subscribe them to web push notifications. This generates a unique PushSubscription object containing endpoint URL and encryption keys. Store this subscription object securely in your database, associated with the user's ID.
3. Configure Didit Webhooks: In your Didit Business Console, set up a webhook URL that points to an endpoint on your backend server. Didit will send real-time updates to this endpoint whenever a verification session's status changes.
4. Backend Processes Webhook: When your backend receives a webhook notification from Didit (e.g., a status change to "Approved" or "Declined" for a specific session_id), it retrieves the corresponding user's PushSubscription from your database.
5. Send Push Message: Your backend then uses a push library (e.g., web-push for Node.js) to send a push message to the browser's push service using the stored subscription data. The payload of this message can include the new verification status and any relevant details.
6. Service Worker Displays Notification: The user's browser receives the push message, and the Service Worker displays a notification using the Notification API, informing the user of the update.

This robust integration ensures that your users are always in the loop, transforming a potentially anxious waiting period into a positive and transparent experience. For scenarios requiring re-verification, Didit's "Resubmitted" status can trigger a push notification prompting the user to retake specific steps, streamlining the process.

Best Practices for User Experience

• Clear Opt-in: Always obtain explicit user consent before sending push notifications. Explain the value proposition clearly.
• Concise Messaging: Keep notification messages short, clear, and actionable. "Your identity has been verified!" is more effective than a lengthy paragraph.
• Provide Context: Include a link in the notification that directs users to a relevant page on your site where they can take action or view more details.
• Frequency Control: Avoid overwhelming users with too many notifications. Only send updates for significant status changes.
• Localization: If you operate globally, ensure your notifications are localized for different languages and regions.

How Didit Helps

Didit is the AI-native, developer-first identity platform designed to make identity verification seamless and efficient. Our modular architecture and clean APIs are perfectly suited for integrating real-time communication channels like web push notifications. With Didit's extensive range of products, including ID Verification (OCR, MRZ, barcodes), Passive & Active Liveness, and AML Screening & Monitoring, businesses can build comprehensive verification workflows. Our robust webhook system ensures that your backend receives immediate notifications of status changes, enabling you to trigger web push notifications with precision. Didit's Free Core KYC offering, combined with no setup fees and a pay-per-successful-check model, makes it an accessible and powerful solution for businesses of all sizes looking to enhance their user experience through real-time identity verification updates.

Ready to Get Started?

Ready to see Didit in action? Get a free demo today.

Start verifying identities for free with Didit's free tier.