Skip to content

Trust & Security

Traveln integrations are designed so partners can create branded traveler experiences without exposing sensitive credentials in browser code.

Core Principles

Server-side secrets SSO HMAC secrets and partner API keys belong on partner backend services, not in frontend JavaScript.
Tenant-aware access Traveln resolves the tenant from signed tokens, tenant configuration, approved domains, and integration context.
Approved origins Partner web origins must be approved before loading tenant config or embedding selected Traveln flows.
Backend authorization Specific-chat embeds still rely on Traveln backend ownership checks when the chat is loaded.

Authentication Model

Web integrations use short-lived SSO tokens:

  1. The partner frontend asks the partner backend for a token.
  2. The partner backend verifies the user and signs a Traveln SSO payload.
  3. Traveln verifies the token, creates a session, and routes the user to the requested destination.

This keeps sensitive signing material away from browser code while giving travelers a smooth launch into Traveln-powered flows.

Frame And Embed Safety

Iframe-based flows require approved origins. Traveln validates the parent origin for embed-sensitive flows and applies frame policy only where embedding is expected. Normal Traveln pages remain protected by the standard frame policy.

Public Guidance

  • Use HTTPS for production integrations.
  • Keep SSO signing keys and partner API keys server-side.
  • Use approved partner origins for CDN config and iframe embed flows.
  • Treat private chat UUIDs as identifiers, not authorization. Traveln still authorizes access on the backend.
  • Use the server-to-server Integrations API from backend services, not from browser-side JavaScript.