Extension Integration

Overview

Build browser extensions with Reclaim verification in popup/sidepanel. The SDK handles Chrome Manifest V3 complexity including service workers, offscreen documents, and content script orchestration.

When to Use Extension Integration

Choose this integration approach if you are:

• 🔧 Building a browser extension from scratch or adding to an existing one
• 🎯 Controlling the entire user experience within your extension
• 🔌 Creating popup or side panel interfaces that trigger verification
• 🛠️ Developing productivity tools that need provider data verification

What You'll Build

By following this guide, you'll create a browser extension that can:

• Trigger Reclaim verification flows from extension popups or side panels
• Manage provider authentication tabs automatically
• Generate cryptographic proofs using WebAssembly
• Handle verification completion events
• Securely communicate between extension components

Architecture Overview

Extension integration involves three main components:

Components Explained

Extension Popup/Panel

• Your extension's user interface (HTML/CSS/JS)
• Initiates verification requests
• Displays results and handles user interactions

Background Service Worker

• Chrome Manifest V3 background script
• Coordinates between all components
• Manages extension lifecycle and permissions

Content Script Bridge

• Injected into web pages
• Enables communication with provider pages
• Handles message routing

Offscreen Document

• Hidden document for WebAssembly execution
• Generates cryptographic proofs
• Required for Manifest V3 architecture

Provider Tab

• Automatically opened during verification
• Hosts the provider authentication flow
• Monitored by network interceptor

Integration Steps

The integration process consists of four main steps:

1. Manifest Configuration

Configure your Chrome extension's manifest.json with required permissions, content security policies, and web-accessible resources.

Configure Manifest →

2. Background Initialization

Initialize the SDK in your background service worker to enable offscreen document management and message handling.

Set Up Background →

3. Content Script Loading

Load the SDK's content script bridge to enable communication between your extension and web pages.

Load Content Script →

4. Implement Verification Flow

Use the SDK's API in your popup or panel to trigger verification and handle results.

Implement Usage →

Prerequisites

Before starting, ensure you have:

• ✅ Completed the Installation guide
• ✅ Obtained API credentials from the API Key guide
• ✅ Basic understanding of Chrome extension development
• ✅ Familiarity with JavaScript Promises and async/await
• ✅ A Chrome extension project with Manifest V3

Security Considerations

Content Security Policy

The SDK requires specific CSP settings for WebAssembly execution:

"content_security_policy": {
  "extension_pages": "script-src 'self' 'wasm-unsafe-eval'; object-src 'self';"
}

Permissions

The SDK needs specific permissions:

• offscreen: Create offscreen documents for proof generation
• cookies: Access provider cookies during verification
• <all_urls>: Inject content scripts and intercept network requests

Best Practices

1. Never expose credentials in client code: Use environment variables or secure configuration
2. Validate all user inputs: Before passing to verification flows
3. Handle errors gracefully: Implement proper error boundaries
4. Clear sensitive data: After verification completes
5. Use server-side validation: For production deployments

Browser Compatibility

This integration works with Chromium-based browsers supporting Manifest V3:

Example Extension

For a complete working example, check out our sample extension (link to be added).

Next Steps

Start with manifest configuration:

Configure Your Manifest →