Integration

AgeGO offers two integration paths, depending on the level of control and flexibility you need.

• Overlay (client-side): A drop-in JavaScript snippet that renders an overlay on top of your pages and masks content until verification is complete. Fastest to launch, minimal or no backend work.
• S2S (server-to-server): A backend workflow where your server decides who and when to send to AgeGO for verification and handles callbacks. Requires development effort but offers maximum flexibility.

How It Works

At a high level, both integration paths follow the same logical flow, with differences in how verification is triggered.

1

A visitor requests a page on your site.

2

Your site triggers AgeGO:

• Overlay: the JavaScript snippet displays the verification overlay directly on the page.
• S2S: your server redirects selected users to AgeGO for verification.

3

AgeGO performs the configured verification checks (for example: Selfie, Credit Card, SMS).

4

Your site receives the verification result via redirect or callback and:

• grants access, or
• denies access, depending on the result.

Choose Your Integration Path

When a site is created in the AgeGO Admin Panel, site owners are presented with three integration options under Integrate AgeGO with your website:

Modal Integration (JavaScript Snippet)

Recommended for most websites.

• Add one JavaScript snippet.
• AgeGO opens as an overlay.
• No backend setup required.
• Automatic handling of user interface and verification flow.
• Ideal for publishers, platforms, and most online services.

→ Open Modal Integration Guide

Server-to-Server (S2S)

Recommended for platforms needing deeper control.

• Backend-driven sequence.
• You manage redirects and session validation.
• Works well for mobile apps, regulated industries, and custom flows.
• Requires handling callbacks and checking verification status.

→ Open S2S Integration Guide