Integrations and source ownership

• Transcoding service. The real rendition outcome is recorded on the asset and its run steps, with the provider’s receipt.

• Video player and analytics feed. Playback events arrive with a source record identifier and entitlement reference, and become sessions.

• Subscription and entitlement system. Subscriber entitlements are checked against plan codes and effective dates.

• Payment provider and delivery network. Settlements and invoices supply the confirmed amounts for reconciliation.

• Identity provider. Map people to user accounts; disabling a sign-in must remove access here too.

Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated playback event must not create a second session, and a repeated settlement must not be reconciled twice. Queue rejected records with their source identifier and a visible reason. Each source is captured as a snapshot with coverage and freshness, using a reviewed mapping.

Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.