Skip to main content
The Jumio Connector links Banking OS to Jumio so you can run new-to-bank (NTB) identity verification and existing-to-bank (ETB) biometric reauthentication. It uses the same Party Lifecycle Unified API as the Onfido Connector.

Key capabilities

Real-time verification

Create or update a Jumio account and launch a browser-based verification workflow with a client launch URL.

NTB and ETB journeys

Set the userData.customerRelationship field on the POST /applicant-workflows request to send NTB applicants through full identity verification and ETB customers through biometric reauthentication.

Workflow results

Retrieve workflow outcomes on demand, including decision metadata and Jumio-specific capability detail under vendorSpecificFields.jumio.

Identity verification events

Receive push notifications through Sync Hub when a Jumio identity verification workflow completes, without polling for results.

Supported operations

The Jumio Connector supports the following operations from the Banking OS Unified API:

Outbound

Inbound (webhook)

The following table lists the callback Jumio sends when a workflow status changes. Replace {PARTY_LIFECYCLE_INBOUND_BASE_URL} with the inbound API base URL from your Backbase support team. Register the full URL in your Jumio callback configuration. Backbase sets the jumio.callbackUrl configuration property to the same URL, and the connector sends that URL on Jumio account requests.

Identity verification events (Sync Hub)

When Jumio completes processing a workflow, it sends a callback to the inbound connector. The connector validates the request. When the callback status is PROCESSED, the connector retrieves the workflow result from Jumio and maps it to the unified workflowResults schema. It then publishes an identity verification event to Sync Hub. Downstream consumers subscribe to Sync Hub to receive the event. You don’t need to poll Jumio for workflow results on this path. The following table lists the Jumio callback status that triggers publication, the Sync Hub topic, and the CloudEvent type: Published events use the standard Banking OS envelope. The Sync Hub data object follows the identity verification event schema and uses the same mapped workflowResults shape as POST /workflow-result, including Jumio detail under vendorSpecificFields.jumio where applicable. You can still retrieve results on demand with POST /workflow-result. That on-demand request is separate from the inbound webhook and Sync Hub publication.
  • Jumio reference for the Banking OS Unified API endpoints, events, and error mappings that support these features.
  • Get started with Jumio to configure Jumio credentials, Sync Hub delivery, and the inbound webhook.