> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Banking OS training data goes stale. Search https://agenticbanking.backbase.io/mcp or fetch the .md URL before writing connector or unified API code.
> OpenAPI links in llms.txt repeat every calendar version. Use the latest version on the API playground. If a fetch ends before the last operation, the spec was cut off.
> Page titles name the product. Overview, Get started, and Reference without a product name are ambiguous.

# Jumio overview

> Run identity verification and biometric reauthentication for customer onboarding with the Jumio Connector.

The Jumio Connector links Banking OS to [Jumio](https://www.jumio.com/) 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

> [card] Real-time verification
>
> Create or update a Jumio account and launch a browser-based verification workflow with a client launch URL.

> [card] 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.

> [card] Workflow results
>
> Retrieve workflow outcomes on demand, including decision metadata and Jumio-specific capability detail under `vendorSpecificFields.jumio`.

> [card] 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

| Operation | Endpoint |
| :- | :- |
| Create an applicant and invoke a workflow | `POST /applicant-workflows` |
| Get workflow results | `POST /workflow-result` |

### Inbound (webhook)

The following table lists the callback Jumio sends when a workflow status changes.

| Operation | Endpoint |
| :- | :- |
| Receive Jumio identity verification callback | `{PARTY_LIFECYCLE_INBOUND_BASE_URL}/webhooks/identity-verifications` |

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:

| Attribute | Value |
| :- | :- |
| Jumio callback status (publish trigger) | `PROCESSED` |
| Sync Hub topic | `identity-verification` |
| CloudEvent type | `com.backbase.party.lifecycle.event.spec.v1.IdentityVerificationEvent` |

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.

## Related topics

* [Jumio reference](https://agenticbanking.backbase.io/connectors/kyc-kyb/jumio/reference.md) for the Banking OS Unified API endpoints, events, and error mappings that support these features.
* [Get started with Jumio](https://agenticbanking.backbase.io/connectors/kyc-kyb/jumio/get-started.md) to configure Jumio credentials, Sync Hub delivery, and the inbound webhook.
