For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterOpenAPI SpecStatus
OverviewInquiriesTransactionsRelaysAPI ReferenceChangelog
OverviewInquiriesTransactionsRelaysAPI ReferenceChangelog
  • Overview
    • Relay Overview
    • Getting Started
  • Widget
    • Usage
  • Integration Methods
    • Server SDK
  • References
    • Relay Widget SDK
    • Server SDK
    • Gateway Service
    • API
    • Schemas
LogoLogo
Help CenterOpenAPI SpecStatus
On this page
  • 1. Widget
  • 2. Server-side integration
Overview

Getting Started

Was this page helpful?
Previous

Widget

Next
Built with

Integrating Relay requires two components working together:

  1. Widget — collects and verifies the end user’s identity, creating the verification inquiry
  2. Server-side integration — retrieves the claim result from the completed inquiry

1. Widget

Embed Persona’s Widget in your frontend to handle the user-facing verification flow. The Widget creates the inquiry and runs the user through the configured verification steps.

Widget usage →

2. Server-side integration

Once the Widget completes a verification, your server retrieves the claim result. Choose the integration method that best fits your stack:

MethodBest for
Server SDKTypeScript/Node.js backends. Easiest to integrate — handles all cryptography out of the box
Edge WorkerTeams whose backend isn’t TypeScript but whose stack includes Cloudflare or Vercel — second fastest to spin up
Relay Gateway ServiceBackends without the right language support for blind RSA or OHTTP — offloads all cryptography to a self-hosted service
APITeams who want full control and are willing to implement the Privacy Pass cryptography themselves — works with any language or runtime