PageSourceSearch

https://console.sift.com/js/202-b0609fb4f0b03553bf68.js

js sift.com collected 2026-10-01 08:42:44 UTC 7,134 bytes, 1 lines download raw bytes

1"use strict";(this.webpackChunk=this.webpackChunk||[]).push([[202],{70202:(e,t,o)=>{o.r(t),o.d(t,{default:()=>n});var i=o(85376);const n={displayName:"Jumio",category:"ID Verification",className:"jumioSolutionTemplate",cardLabel:"Connect with Jumio to dynamically verify the identity of your customers.",solutionTagline:"Connect with Jumio to dynamically verify the identity of your customers.",solutionDescription:"Jumio is the Next-Gen KYC solution which allows you to establish trust from day one. With Sift, dynamically employ Jumio’s identity verification services to serve a friction-free verification experience and to simplify KYC and AML compliance. A Jumio account is required to activate. Visit https://jumio.com for more information.",previewImages:[],keyFeatures:[{title:"Low-Code Integration",icon:"code",body:"Sift’s Workflows plugs right into Jumio and serves the verification UI with a low code integration"},{title:"Step-Up Authentication",icon:"shield-check",body:"Use Workflow Criteria to manage your business logic and serve additional friction when needed"},{title:"Cost Savings",icon:"coins",body:"Leverage the Sift score to reduce the number of verification calls ran by blocking fraudsters right off the bat"}],sharedData:[{sourceLogo:i.i,sinkLogo:"jumio_connector",type:"Sift Reference",description:"Sift will provide a Workflow Run ID as a reference to Jumio when a verification is triggered."},{sourceLogo:"jumio_connector",sinkLogo:i.i,type:"Verification Outcome",description:"Sift will be able to access the verification outcome and any decline reasons, if applicable. Sift does not consume any PII with this integration."}],pricing:"Jumio is free to connect with Sift when you have an existing Jumio account. Visit https://jumio.com for more information.",requirements:[{title:"Key Information",icon:"account-needed",body:"You will need to provide API Credentials from Jumio."},{title:"Low-Code Integration",icon:"account-needed",body:"You’ll need to set up a webhook to consume the verification outcome from Jumio."},{title:"Jumio Account",icon:"account-needed",body:"Make sure you have an active account with Jumio to get started."}],integrationSteps:'#### How to Install\n  The Jumio App leverages Sift Workflows in order to determine when to trigger an ID Verification. The following steps will enable the integration between the two services:\n  \n  #### Integration Details\n  Your application will need to send a [synchronous event to Sift](https://developers.sift.com/docs/python/workflows-api/overview). When the Workflow Criteria for a route is fulfilled, a Sift redirect URL will be returned in a workflow_statuses array as shown below. The client of your application will need to make a POST request to that URL using [a beacon key](https://developers.sift.com/docs/python/apis-overview/core-topics/authentication), resulting in a redirect to the Jumio verification flow.\n  \n  ```json\n     {\n      "score_response": {\n        ...\n        "workflow_statuses": [\n          ...\n          "history": [\n            {\n              "app": "identity_verification",\n              "name": "jumio",\n              "state": "running",\n              "outputs": {\n                "redirect_url": "https://console.sift.com/v1/idv/jumio/accounts/..."\n               },\n              "config": {\n                "provider": "jumio"\n              }\n            },\n      ...\n  ```\n  \n  ###\n  Your application will also need a webhook endpoint to consume the verification outcome. This should indicate whether the user should proceed or not in the application’s flow. A sample payload is as follows:\n  \n  ```json\n    {\n      "workflow_run_id": 5suzrz37cqgqe2,\n      "idv_response": { \n        "jumioIdScanReference": 1a23cz3er4afewa,\n        "verificationStatus": "DENIED_FRAUD", \n        "rejectReason": "MANIPULATED_DOCUMENT", \n        "similarity": "NO_MATCH",\n        "validity": "FALSE",\n        "reason": "SELFIE_MANIPULATED"\n      }\n      "service_name": "jumio"\n     }\n```\n  \n  ### Note: For full details about the idv_response object fields and values, please reference Jumio’s [callback documentation](https://github.com/Jumio/implementation-guides/blob/master/netverify/callback.md).\n\n  \n  #### Jumio Application Settings\n  After the Integration Setup has been completed, you may move forward with the setup within the Jumio portal. \n  \n  1. Log into [Jumio](https://customer-portal.netverify.com/#/login).\n  2. Navigate to your Ap
1plication Settings via the cog icon.\n  3. Specify your client’s customization settings. \n  4. Ensure you fill out the Success URL and Error URL, which should be handled by your application. The Callback URL can be left blank.\n  5. Feel free to leave the authtoken blank.\n  6. Navigate to the Redirect Tab and specify your redirect settings.\n  \n#### App Setup with Sift\n  For this part of the setup, you will need to generate API Credentials within Jumio and enter them into Sift. \n\n  1. Begin this setup by pressing Enable located in the upper right hand corner of this page, resulting in the displaying of a modal window. Here, you will need to provide both your API Credentials and a Webhook URL. \n  \n  2. Within the Jumio portal on the [API Credentials tab](https://customer-portal.netverify.com/app/#/settings/identity-verification/api-credentials/api-users), generate a new API Token and Secret. Enable all permissions and enter your password to validate. Enter these values into the modal in Sift.\n  \n  3. Next, specify what type of ID Verification experience you would like to use.\n  \n  4. After the credentials have been entered, the Webhook URL of where the verification webhook should be received should be entered into the modal upon setup as follows:\n  \n    ![](/image/connect/solutions/jumio_connector/instructions/cons_ver.png)\n\n\n### Note: Note: Because Sift is not allowed to process PII, Sift will provide a limited version of the verification response. If more information is required, please query the [Retrieval API](https://github.com/Jumio/implementation-guides/blob/master/netverify/netverify-retrieval-api.md).\n\n  5. Lastly, navigate to Workflows, and specify the route where you’d like to use Jumio.\n\n  ![](/image/connect/solutions/jumio_connector/instructions/wf_setup.png)\n',faq:[{title:"Do I need a Jumio account to connect with Sift?",body:"Yes, a Jumio account is required. Visit https://jumio.com for more information."},{title:"What data can I send to Sift with a Jumio connector?",body:"The Jumio connector enables verification outcome data to be sent to Sift. This includes the verification status, reject reason, and ID type."},{title:"How does the connector work?",body:"The Jumio connector leverages an integration from Sift to Jumio which is triggered by a Workflow. When the corresponding Workflow criteria is fulfilled, Sift calls the Jumio service. When the verification is complete, Sift will consume the verification outcome, and send the result to your application."}],troubleshooting:[],requiredAuthFields:[],requiredConfigFields:[]}}}]);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.