Changelog

September 23, 2025

User Validation

• Cross-partner validation: Once a user is validated with one partner, their validation status is now recognized across all partner websites.

Verification Configuration

• Partners can now choose which types of verifications are presented to users.
• The email verification fallback option can be disabled if not required.

UI Enhancements

• Added three new configurable color options for cancel and error buttons:
• button.backgroundFailure
• button.foregroundFailure
• button.foregroundCallToActionFailure

Standard Implementation (formerly Old Implementation)

The previous implementation page has been renamed and enhanced as Standard Implementation.

Updates to the Standard Implementation SDK include:

• Simplified payload validation:
• Payload integrity checks are no longer required.
• Use eventMessage.data.isPayloadValid to directly verify payload validity.
• Removed the local payload validation script.
• New optional parameters:
• paramList.verificationTypeList: Specify which verification types to display.
• paramList.verificationTypeDefault: Define the default selected verification type in Go.cam.
• paramList.useEmailAsFallbackVerification: Enable or disable email fallback as a verification method.
• Additional UI customization: Three new configurable colors for cancel and error states (see UI Enhancements).

Hosted Implementation (New)

A new implementation option, Hosted Implementation, is now available. It differs from the Standard Implementation as follows:

• Frontend-only (JavaScript) implementation.
• Provides a simplified iframe overlay logic.
• Can be set up with a single JavaScript file added to the document body (Automatic Implementation).
• Automatically manages:
• • Website content blurring until age verification is complete.
  • Local device cookies to track verified users.
• Offers two modes:
• • Automatic implementation: Handles most logic automatically.
  • Controlled implementation: Allows partners to define custom actions on verification success or failure.
• Domain-based restrictions:
• • Each domain must be validated before it can be configured.
  • Implementation and data postback are bound to specific domain names.
  • Two access keys are provided per domain: one for development, one for production.
• Configuration binding: All settings (colors, verification types, advanced liveness, email fallback, etc.) are stored per domain.
• Simplified verification logic compared to the Standard Implementation.

Statistics Filtering

• Statistics can now be filtered by domain name.
• Hosted and Standard implementations can be separated in reports for improved visibility.

Bug fixes

Various small bug fixes.