Identity Verification Service Events

The following events deliver updates on the verification status or decision of a customer profile within the Identity Verification Service (IVS). These are sent to you in the Account Events webhook, which is part of the Events API. You must be subscribed to IVS events to receive these events.

Event wrapper

Each event is enclosed in this wrapper:

{
 "detail": {
  "data": {
   "<event_name>": {<event_body>}
   }
  },
  "metadata": {
   "detail_id": "<UUID>",
   "detail_timestamp": "<YYYY-MM-DDThh:mm:ss.ssssss>",
  }
 }
}

Where:

<event_name> — Name of the event, including version number at the end.
<event_body> — Fields in the event, as documented in the tables below.
<UUID> — Unique identifier for the detail contents, meaning the unique ID for the event message.
<YYYY-MM-DDThh:mm:ss.ssssss> — Timestamp for when the event was generated and sent.

`ivs_customer_status.v1`

The status or decision of a customer profile has changed. The change was caused by document verification, sanction alerts, or manual review.

Code — n/a
Event trigger — Galileo calculates a new status or decision for a customer profile (consumer or business).
Processes — These processes contain the event trigger:
- Identity Verification Service

Event body

Field name	Type	Required	Description
`ivsProfileId`	string	X	Provider-generated identifier for the IVS profile. Use this ID to reference the account's status in other API endpoints. Example: `”243693”`
`customerId`	string	X	Galileo-generated ID for the customer undergoing verification. Use this to correlate this event back to the specific entity record in your system. Example: `”890123”`
`customerName`	string	X	The name of the customer (consumer or business). Example: `”Your Customer”`
`statusChangeTs`	string	X	Timestamp for when the status changed in Galileo system time. Format: `YYYY-MM-DD hh:mm:ss MST`
`statusCode`	string	X	The new status of the customer. See status codes for valid values. Example: `”COMPLETE”`
`decisionCode`	string		The decision made on this customer. See decision codes for valid values. Example: `”ACCEPT“`
`transientState`	Boolean		Whether the customer profile verification is currently in progress.

Status codes

Code	Description
`COMPLETE`	The customer verification process is completed.
`REFERRED`	Application is pending manual review.
`AWAITING_RESPONSE`	Application requires customer action.
`IN_PROGRESS`	Application requires customer action.

Decision codes

Code	Description
`ACCEPT`	The customer application was verified and accepted.
`DECLINE`	The customer application failed verification and was declined.
`CLOSE`	The customer application was closed.

Example payload

{
 "detail": {
  "data": {
   "ivs_customer_status.v1": {
        "ivsProfileId": "222",
        "customerId": "101",
        "customerName": "John Doe",
        "statusChangeTs": "2021-06-30 21:39:14 MST",
        "statusCode": "COMPLETE",
        "decisionCode": "ACCEPT",
        "transientState": true
      }
   }
  },
  "metadata": {
   "detail_id": "20ed3369-552a-197f-df4c-6971d65fe999",
   "detail_timestamp": "2026-05-29T15:56:00.060756"
  }
 }
}

`ivs_journey_result.v1`

A decision has been made on an application verification within a customer's profile in IVS.

Code — n/a
Event trigger — Galileo provides a total rule score and risk level decision on a customer profile.
Processes — These processes contain the event trigger:
- Identity Verification Service

Event body

Field name	Type	Required	Description
`journeyVerificationUid`	string	X	Unique ID of an application associated with the journey verification. Example: `"243693"`
`entityId`	string	X	Galileo-generated ID for the entity undergoing verification. Use this to correlate this event back to the specific entity record in your system. Example: `"890123"`
`journeyId`	integer	X	ID of the journey that processed the application verification. Example: `"26689"`
`journeyName`	string	X	Name of the underlying risk vendor or internal logic path used. Example: `"IDVerse"`
`customerName`	string		Full legal name of the customer (consumer or business) undergoing verification. Example: `"Acme Corp"`
`totalRuleScore`	integer		Aggregate numerical score calculated across all rulesets. This total is used to determine if the journey passes, fails, or requires manual review. Example: `"60"`
`totalRiskLevel`	string		Categorical risk rating determined by the `totalRuleScore`. Example: `"IDVerse - Document Match"`
`journeyType`	object		Journey verification object.
`journeyType.journeyTypeId`	integer		Identifier for the journey category. Example: `5`
`journeyType.journeyTypeLabel`	string		Plain-text description of `journeyType.journeyTypeId`. Example: `"KYC"`
`journeyStartTs`	string		Timestamp for when this journey was created in Galileo system time. Format: `YYYY-MM-DD hh:mm:ss MST`
`journeyEndTs`	string		Timestamp for when this journey ended in Galileo system time Format: `YYYY-MM-DD hh:mm:ss MST`
`journeyStatus`	object	X	Status of the journey verification object.
`journeyStatus.statusLabel`	string		Name of the status. Example: `"Cleared"`
`journeyStatus.isActive`	Boolean		Whether the journey is still processing the application.
`journeyStatus.statusDesc`	string		Detailed explanation of the status. Example: `"The application was marked as clear"`.
`journeyStatus.statusCode`	string		Identifier for the journey status. See `journeyStatus` codes for valid values. Example: `"STACLR"`
`auditReference`	string		Unique ID for tracking this specific identity verification check. Example: `"AU357977324"`
`rulesetOutcomes`	object		Array of outcome objects for every ruleset executed during the journey.
`rulesetOutcomes.rulesetId`	integer		Unique ID for the specific collection of rules. Example: `51565`
`rulesetOutcomes.rulesetScore`	integer		Sum of all individual `ruleScore` values within this specific set. Example: `60`
`rulesetOutcomes.riskLevel`	string		Risk classification assigned to this specific ruleset outcome. Example: `"IDVerse - Document Match"`
`rulesetOutcomes.rulesetOutcomeStatus`	string		Result of applying the rule set. Same value as `journeyStatus.statusCode`. Example: `"STACLR"`
`rulesetOutcomes.rulesetLabel`	string		Display name of the rule set. Example: `"IDVerse Ruleset v3"`
`rulesetOutcomes.ruleOutcomeDetails`	array		Granular results of every individual Boolean check or score-based rule.
`rulesetOutcomes.ruleOutcome.ruleOutcome`	Boolean		Returns `true` if the rule’s specific condition passed.
`rulesetOutcomes.ruleOutcome.ruleScore`	integer		Incremental score applied by this rule to the cumulative ruleset result. Example: `10`
`rulesetOutcomes.ruleOutcome.ruleId`	integer		Reference number for the individual rule. Example: `348609`
`rulesetOutcomes.ruleOutcome.ruleOutcomeDesc`	string		Explanation of what this specific rule was checking for and the result. Example: `"IDVerse - Extracted Last Name Matching Application (Applicant)"`
`rulesetOutcomes.ruleOutcome.ruleName`	string		Display name of the rule. Example: `"IDVerse - Extracted Last Name Matching Application (Applicant)"`
`rulesetOutcomes.ruleOutcome.appIds`	string		Application IDs associated with this rule. Example: `"1000110"`
`rulesetOutcomes.ruleOutcome.rulesetId`	integer		Unique identifier for the parent rule set. Example: `51565`
`rulesetOutcomes.ruleOutcome.rulesetName`	string		Display name of the parent rule set. Example: `"IDVerse Ruleset v3"`
`links`	array		Collection of links associated with the journey for follow-up actions.
`links.linkType`	object		Object containing the details of the specific action link.
`links.linkType.rel`	string		Describes how the link relates to the current journey. Example: `"testvalue"`
`links.linkType.href`	string		Target URL for executing the required follow-up action. Example: `"https://target-url.com"`

`journeyStatus` codes

This table shows the possible statusCode values and their corresponding statusLabel.

`statusCode`	`statusLabel`	Description
`STARCLR`	Cleared	The application cleared the verification process and is approved after initially being referred for manual review or submitting additional documentation.
`STACLS`	Closed	The application is closed without a final approval or decline, typically because the customer abandoned the application or the referral was manually closed.
`STACOM`	Complete	The automated application successfully completed all required checks and a final decision has been made on the application.
`STADEC`	Declined	The verification failed and resulted in a decline, typically because the customer abandoned the application or the journey expired.
`STEPUP`	Awaiting customer response	The verification process requires additional action from the customer, such as submitting an ID document or answering knowledge-based questions before it can proceed.
`REFQUE`	Referred	The customer's application triggered a risk threshold and was routed to a queue for manual review by a compliance officer.
`PRGASC`	In-Progress Asynchronous Journey	The verification process is actively running in the background and waiting for delayed responses from third-party data sources.

Example payload

{
  "detail": {
    "data": {
      "ivs_journey_result.v1": {
        "journeyVerificationUid": "243693",
        "entityId": "890123",
        "journeyId": 26689,
        "journeyName": "3. IDVerse",
        "customerName": "Your Customer",
        "totalRuleScore": 60,
        "totalRiskLevel": "IDVerse - Document Match",
        "journeyType": {
          "journeyTypeId": 5,
          "journeyTypeLabel": "KYC"
        },
        "journeyStartTs": "2025-10-28 09:14:27 MST",
        "journeyEndTs": "2025-10-28 09:14:28 MST",
        "journeyStatus": {
          "statusLabel": "Clear",
          "isActive": true,
          "statusDesc": "The application was marked as clear",
          "statusCode": "STACLR"
        },
        "auditReference": "AU357977324",
        "rulesetOutcomes": [
          {
            "rulesetId": 51565,
            "rulesetScore": 60,
            "riskLevel": "IDVerse - Document Match",
            "rulesetOutcomeStatus": "STACLR",
            "rulesetLabel": "IDVerse Ruleset v3",
            "ruleOutcomeDetails": [
              {
                "ruleOutcome": true,
                "ruleScore": 10,
                "ruleId": 348609,
                "ruleOutcomeDesc": "IDVerse - Extracted Last Name Matching Application (Applicant)",
                "ruleName": "IDVerse - Extracted Last Name Matching Application (Applicant)",
                "appIds": "1000110",
                "rulesetId": 51565,
                "rulesetName": "IDVerse Ruleset v3"
              },
              {
                "ruleOutcome": true,
                "ruleScore": 10,
                "ruleId": 329356,
                "ruleOutcomeDesc": "IDVerse - Extracted DOB Matching Application (Applicant)",
                "ruleName": "IDVerse - Extracted DOB Matching Application (Applicant)",
                "appIds": "1000110",
                "rulesetId": 51565,
                "rulesetName": "IDVerse Ruleset v3"
              },
              {
                "ruleOutcome": true,
                "ruleScore": 10,
                "ruleId": 329348,
                "ruleOutcomeDesc": "IDVerse - Liveness Pass",
                "ruleName": "IDVerse - Liveness Pass",
                "appIds": "1000110",
                "rulesetId": 51565,
                "rulesetName": "IDVerse Ruleset v3"
              }
            ]
          }
        ]
      }
    }
  },
  "metadata": {
    "detail_id": "0b03f753-387c-43a1-1589-0d9f5c3f58a2",
    "detail_timestamp": "2026-05-07T18:00:18.146467"
  }
}

`ivs_document_requested.v1`

An ad-hoc request for documents has been sent to a customer undergoing identity verification.

Code — n/a
Event trigger — IVS requests additional documents from the customer.
Processes — These processes contain the event trigger:
- Identity Verification Service

Event body

Field name	Type	Required	Description
`module`	string	X	A user-defined label assigned to the verification request via the IVS dashboard. Example: `"Info Request"`
`auditReference`	string	X	Unique reference identifier for tracking this specific identity verification check. Example: `"AU356402354"`
`customerName`	string		The full legal name of the customer (consumer or business) undergoing verification. Example: `"Your Customer"`
`entityId`	string	X	Galileo-generated ID for the entity undergoing verification. Use this to correlate this event back to the specific entity record in your system. Example: `"890123"`
`submissionUrl`	string		Target URL for executing the required follow-up action. Example: `"https://verify.provider.com/upload/token-123"`
`documentRequestedTs`	string		Date-time when the document request was sent to the customer in Galileo system time. Format: `YYYY-MM-DD hh:mm:ss MST`
`customerEmail`	string		Email address of the customer where the document request was sent. Example: `"[email protected]"`
`experienceUrls`	array	X	List of links the client can use to customize their customer experience for document upload.
`experienceUrls.actionCode`	string		Code for the action. Example: `”STEPSUBMIT“`
`experienceUrls.href`	string		Reference URL. Example: `”https://pp.trunarrative.cloud/stepup/submit.aspx?token=uuid“`

Example payload

{
  "detail": {
    "data": {
      "ivs_document_request.v1": {
        "module": "Info Request",
        "auditReference": "AU356402354",
        "customerName": "Your Customer",
        "entityId": "890123",
        "submissionUrl": "https://verify.provider.com/upload/token-123",
        "documentRequestedTs": "2025-10-21 12:52:38 MST",
        "customerEmail": "[email protected]",
        "experienceUrls": [
          {
            "actionCode": "STEPSUBMIT",
            "href": "https://pp.trunarrative.cloud/stepup/submit.aspx?token=343aefae-cd1a-4b4f-924d-8b62133d8545"
          },
          {
            "actionCode": "STEPEMBED",
            "href": "https://pp.trunarrative.cloud/stepup/embed.aspx?token=343aefae-cd1a-4b4f-924d-8b62133d8545"
          },
          {
            "actionCode": "GETINFO",
            "href": "https://pp.trunarrative.cloud/stepup_api/rest/applications/v1/awaitingresponse/info/343aefae-cd1a-4b4f-924d-8b62133d8545"
          },
          {
            "actionCode": "POSTINFO",
            "href": "https://pp.trunarrative.cloud/stepup_api/rest/applications/v1/awaitingresponse/info/343aefae-cd1a-4b4f-924d-8b62133d8545"
          }
        ]
      }
    }
  },
  "metadata": {
    "detail_id": "0b03f753-387c-43a1-1589-0d9f5c3f58a2",
    "detail_timestamp": "2026-05-07T18:00:18.146467"
  }
}

`ivs_document_submitted.v1`

A customer undergoing identity verification responded to an information request and submitted documents.

Code — n/a
Event trigger — The customer submitted documents via the submission URL.
Processes — These processes contain the event trigger:
- Identity Verification Service

Event body

Field name	Type	Required	Description
`module`	string	X	A user-defined label assigned to the verification request via the IVS dashboard. Example: `"Document Verification"`
`auditReference`	string	X	Unique reference identifier for tracking this specific identity verification check. Example: `"AU540657"`
`entity_name`	string		The full legal name of the customer (consumer or business) undergoing verification. Example: `"Your Customer"`
`customerName`	string	X	Galileo-generated ID for the entity undergoing verification. Use this to correlate this event back to the specific entity record in your system. Example: `"890123"`
`journeyReference`	string		The alphanumeric string version of the numeric `journeyId`, used for cross-referencing with external vendor systems. Example: `"J1"`
`nextAuditReference`	string		The identifier for the next audit step in the sequence, if applicable. Often matches the current audit reference if no further steps are queued. Example: `"AU540657"`
`documentSubmittedTs`	string	X	Timestamp for when the customer completed the information request and submitted documents in Galileo system time Format: `YYYY-MM-DD hh:mm:ss MST`
`documents`	array		List of documents submitted by the customer.
`documents.docId`	string		UUID for the submitted document. Example: `”93ce6784-c44b-4bd8-b130-69923ff068bb"`
`documents.docType`	string		Type of document submitted. Examples: `"Passport"` or `"Driver License"`
`documents.pages`	array		Contains the individual submitted files.
`documents.pages.filename`	string		Name of the file submitted by the customer. Example: `"passport_front.jpg"`

Example payload

{
  "detail": {
    "data": {
      "ivs_document_submitted.v1": {
        "module": "Document Verification",
        "auditReference": "AU540657",
        "customerName": "Your Customer",
        "entityId": "890123",
        "journeyReference": "J1",
        "nextAuditReference": "AU540657",
        "documentSubmittedTs": "2026-06-23 02:59:48 UTC",
        "documents": [
          {
            "docId": "93ce6784-c44b-4bd8-b130-69923ff068bb",
            "docType": "Passport",
            "pages": [
              {
                "fileName": "passport_front.jpg"
              }
            ]
          },
          {
            "docId": "eaed3c23-3360-4def-84e5-305b3c3bf39b",
            "docType": "Passport",
            "pages": [
              {
                "fileName": "passport_back.jpg"
              }
            ]
          }
        ]
      }
    }
  },
  "metadata": {
    "detail_id": "0b03f753-387c-43a1-1589-0d9f5c3f58a2",
    "detail_timestamp": "2026-05-07T18:00:18.146467"
  }
}

`ivs_referral_status.v1`

An agent makes a decision on a customer’s profile during the manual review process.

Code — n/a
Event trigger — The status of a referral has changed.
Processes — These processes contain the event trigger:
- Identity Verification Service

Event body

Field name	Type	Required	Description
`customerName`	string		The full legal name of the customer (consumer or business) undergoing verification. Example: `"Your customer"`
`referralReference`	string	X	The unique tracking identifier for the manual review case. Example: `"R16659"`
`referralStatus`	string	X	The definitive outcome of the manual review. See Referral status codes for valid values. Example: `"ACCEPT"`
`referralUpdateTs`	string	X	Date-time when this event was created in Galileo system time. Format: `YYYY-MM-DD hh:mm:ss MST`
`entityId`	string	X	Galileo-generated ID for the entity undergoing verification. Use this to correlate this event back to the specific entity record in your system. Example: `"890123"`

Referral status codes

Code	Description
`CLOSED`	The manual review was closed without a decision.
`ACCEPT`	The application was accepted after manual review.
`DECLINE`	The application was declined after manual review.

Example payload

{
  "detail": {
    "data": {
      "ivs_referral_status_change.v1": {
        "customerName": "Your Customer",
        "referralReference": "R16659",
        "referralStatus": "DECLINE",
        "referralUpdateTs": "2020-04-01 02:28:34 MST",
        "entityId": "890123"
      }
    }
  },
  "metadata": {
    "detail_id": "0b03f753-387c-43a1-1589-0d9f5c3f58a2",
    "detail_timestamp": "2026-05-07T18:00:18.146467"
  }
}

Event wrapper

ivs_customer_status.v1

Event body

Status codes

Decision codes

Example payload

ivs_journey_result.v1

Event body

journeyStatus codes

Example payload

ivs_document_requested.v1

Event body

Example payload

ivs_document_submitted.v1

Event body

Example payload

ivs_referral_status.v1

Event body

Referral status codes

Example payload

`ivs_customer_status.v1`

`ivs_journey_result.v1`

`journeyStatus` codes

`ivs_document_requested.v1`

`ivs_document_submitted.v1`

`ivs_referral_status.v1`