Skip to main content
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

1

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.
2

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.
3

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)
4

Configure Issue Types

Map Verilock events to Jira issue types:
Event CategoryIssue Type
AML eventsTask
Session eventsStory
Transaction eventsBug
You can use any issue type available in your project, including custom types. Verilock validates the type against your project schema on save.
5

Test Connection

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

​
Event-to-Issue Mapping

Verilock EventPriorityLabelsSummary
aml.match_foundHighestcompliance, amlAML Match Found -
aml.monitoring.matchHighestcompliance, monitoringContinuous Monitoring Match -
transaction.blockedHighfraud, blockedTransaction Blocked -
transaction.flaggedHighfraud, reviewTransaction Flagged -
session.declinedMediumkyc, declinedSession Declined -
face.duplicate_foundHighkyc, duplicateDuplicate Face Detected -
session.expiredLowkyc, expiredSession 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 FieldJira Custom Field
risk_scoreRisk Score (number)
session_idVerilock Session ID (text)
applicant.emailApplicant Email (text)
decisionVerification Decision (select)
Custom field mappings require the fields to exist in your Jira project before configuration. Create them in Project Settings > Fields first.

​
Troubleshooting

Verify your email and API token are correct. Ensure the Atlassian account has access to the target project.
The configured issue type must exist in your project’s issue type scheme. Check Project Settings > Issue Types for available types.
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.