Jira

The Jira integration creates issues in your Jira Cloud project when Verilock events require team action. Issues are created with configurable types, priorities, and labels for easy triage.

Prerequisites

Jira Cloud instance (Data Center is not supported)
Project admin permissions
Verilock Business or Enterprise plan

Setup

Generate an API Token

Go to id.atlassian.com/manage-profile/security/api-tokens and click Create API token. Name it Verilock Integration and copy the token.

Identify Your Project Key

In Jira, open your target project. The project key appears in the URL and issue prefixes (e.g., COMP for COMP-123). You will need this in the next step.

Configure in Verilock

Go to Dashboard > Settings > Integrations > Jira and enter:

Jira URL: https://your-domain.atlassian.net
Email: The email associated with your Atlassian account
API Token: The token from step 1
Project Key: Your project key (e.g., COMP)

Configure Issue Types

Map Verilock events to Jira issue types:

Event Category	Issue Type
AML events	Task
Session events	Story
Transaction events	Bug

You can use any issue type available in your project, including custom types. Verilock validates the type against your project schema on save.

Test Connection

Click Create Test Issue to verify the integration. A test issue will appear in your Jira project.

Event-to-Issue Mapping

Verilock Event	Priority	Labels	Summary
`aml.match_found`	Highest	`compliance`, `aml`	AML Match Found -
`aml.monitoring.match`	Highest	`compliance`, `monitoring`	Continuous Monitoring Match -
`transaction.blocked`	High	`fraud`, `blocked`	Transaction Blocked -
`transaction.flagged`	High	`fraud`, `review`	Transaction Flagged -
`session.declined`	Medium	`kyc`, `declined`	Session Declined -
`face.duplicate_found`	High	`kyc`, `duplicate`	Duplicate Face Detected -
`session.expired`	Low	`kyc`, `expired`	Session Expired -

Issue Description

Each Jira issue includes a structured description with event details:

{
  "fields": {
    "project": { "key": "COMP" },
    "summary": "AML Match Found - aml_x7k9m2p4",
    "issuetype": { "name": "Task" },
    "priority": { "name": "Highest" },
    "labels": ["compliance", "aml", "verilock"],
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [
            { "type": "text", "text": "Screening ID: aml_x7k9m2p4\nApplicant: Jean Dupont\nMatch Type: PEP\nMatch Score: 92%\nRisk Level: High" }
          ]
        }
      ]
    }
  }
}

Custom Fields

You can map Verilock data to Jira custom fields from the dashboard. Common mappings include:

Verilock Field	Jira Custom Field
`risk_score`	Risk Score (number)
`session_id`	Verilock Session ID (text)
`applicant.email`	Applicant Email (text)
`decision`	Verification Decision (select)

Custom field mappings require the fields to exist in your Jira project before configuration. Create them in Project Settings > Fields first.

Troubleshooting

401 Unauthorized

Verify your email and API token are correct. Ensure the Atlassian account has access to the target project.

Issue type not found

The configured issue type must exist in your project’s issue type scheme. Check Project Settings > Issue Types for available types.

Labels not appearing

Jira auto-creates labels on first use. If labels are not visible, check that the labels field is available on your issue type’s screen scheme.

Getting Started

Integrations

Reference

AML Screening

Transaction Monitoring

Verification Enhancements

Data & Compliance

Decentralized Identity

Prerequisites

Setup

Event-to-Issue Mapping

Issue Description

Custom Fields

Troubleshooting

​Prerequisites

​Setup

​Event-to-Issue Mapping

​Issue Description

​Custom Fields

​Troubleshooting

Prerequisites

Setup

Event-to-Issue Mapping

Issue Description

Custom Fields

Troubleshooting