Event Notifications & Webhooks

To set up webhooks, contact [email protected] with your designated contact email. You can configure multiple webhook endpoints for different notification types. Ensure your endpoint is accessible via HTTPS.

FrankieOne uses webhooks to send real-time notifications about events in your system, such as a workflow completing or an entity’s risk profile changing. This allows you to build automated, event-driven integrations.

Available Notifications

Workflow Events

Notifications triggered when a workflow execution completes, providing updates on the final status and outcome.

IDV Biometrics Events

Notifications for IDV biometrics events, such as token requests, results retrieval, errors, and expirations.

Entity Events

Notifications related to entity events, such as onboarding, updates, and errors.

Workflow Events

FrankieOne sends notifications to keep you informed about workflow events. These notifications are sent to your configured webhook endpoint.

Notification Function	Description
`WorkflowComplete`	Sent when a workflow execution finishes, providing the final status and outcome.

Workflow Error Events

Notifications related to errors workflow events are sent to your webhook endpoint.

Notification Function	Description
`WorkflowComplete`	Sent when there is an error during workflow execution.

IDV Biometrics Events

Notifications related to IDV biometrics events are sent to your webhook endpoint.

Notification Function	Description
`TOKEN_REQUESTED`	Sent when a token is requested for IDV biometrics.
`ONB_URL_GENERATED`	Sent when an onboarding URL is successfully generated.
`RESULTS_RETRIEVED`	Sent when IDV biometrics results are successfully retrieved.
`OCR_PROCESSED`	Sent when OCR processing is successfully completed.

IDV Biometrics Error Events

Notifications related to errors in IDV biometrics events are sent to your webhook endpoint.

Notification Function	Description
`TOKEN_REQUESTED`	Sent when there is an error during token request for IDV biometrics.
`RESULTS_RETRIEVED`	Sent when there is an error retrieving IDV biometrics results.
`OCR_PROCESSED`	Sent when there is an error during OCR processing.
`ONB_URL_GENERATED`	Sent when there is an error generating the onboarding URL.

Entity Profile Events

FrankieOne sends notifications to keep you informed about entity profile events. These notifications are sent to your configured webhook endpoint.

Notification Function	Description
`EntityProfileUpdated`	Sent when an entity profile is updated, providing the latest information.
`EntityRiskChanged`	Sent when there is a change in the risk status of an entity profile.
`EntityStatusChanged`	Sent when the status of an entity profile changes, such as onboarding or verification.
`EntityAssigneeChanged`	Sent when the assignee of an entity profile changes, indicating a new point of contact.

Webhook Structure

All V2 webhooks share a consistent structure. The payload contains two key fields, notificationType and function, which you should use to determine how to process the event. notificationType: Indicates the nature of the update. For most V2 use cases, this will be EVENT. function: This field specifies the exact event that occurred. The payload for every webhook consists of a base schema of common fields, with additional event-specific fields included depending on the function.

Some webhook function names differ from their V1 counterparts. They also do not follow the same naming conventions. Refer to the tables above for the correct function names.

Base Payload Schema

These fields are present on every webhook notification.

Attribute	Type	Description
version	string	The API version of the webhook event.
notificationType	string	The category of notification (e.g., EVENT, RESULT).
function	string	The specific event that triggered the notification (e.g., WorkflowComplete).
functionResult	string	Indicates if the event was successful (SUCCESS) or not (ERROR, FAILURE).
requestId	string	The unique ID for the API request that initiated the event.
entityId	string	The unique identifier of the entity related to the event.
entityType	string	The type of the entity (e.g., INDIVIDUAL).
entityCustomerReference	string	A reference identifier for the customer, used for linking notifications to your internal records.
serviceName	string	The name of the service profile involved.
message	string	A human-readable summary of the event.
channel	string	The channel source from which the webhook was triggered (e.g., API, WEBHOOK).

Event-Specific Fields

Depending on the function, additional fields will be present in the payload to provide specific context.

Function	Additional Field(s)	Description
WorkflowComplete	workflowExecutionId, workflowName, overallStatus	Provides the final status and identifiers of a completed workflow.
EntityStatusChanged	overallStatus	Provides the new status of the entity profile.
EntityRiskChanged	overallRiskStatus	Provides the new risk level of the entity profile.

You can configure your webhook endpoint to receive all notifications or only specific types, depending on your integration requirements. The notificationType field in the payload identifies the category of each notification.Event-specific fields in the payload are always populated with relevant values based on the event type, ensuring you have the necessary context for processing.

Endpoint Format

FrankieOne appends the requestID to your configured webhook endpoint:

  https://your-domain.com/webhook-endpoint/{requestID}

Payload Examples

{
    "workflowExecutionId": "01JMX7F1Z61K0BP0KWY6MWAQ4J",
    "entityId": "12345678-1234-1234-4321-123487650912",
    "entityType": "INDIVIDUAL",
    "workflowName": "Onboarding",
    "serviceName": "KYC",
    "function": "WorkflowComplete",
    "functionResult": "SUCCESS",
    "notificationType": "EVENT",
    "message": "Entity profile updated",
    "requestId": "01EKVV810DC7NJEC97BAQJZXWR",
    "version": "2.0.0",
    "entityCustomerReference": "customer-ref-12345",
    "overallStatus": "REVIEW",
    "channel": "api"
}

{
    "workflowExecutionId": "01JMX7F1Z61K0BP0KWY6MWAQ4J",
    "entityId": "12345678-1234-1234-4321-123487650912",
    "entityType": "INDIVIDUAL",
    "workflowName": "Onboarding",
    "serviceName": "KYC",
    "function": "EntityRiskChanged",
    "functionResult": "SUCCESS",
    "notificationType": "EVENT",
    "message": "Entity profile updated",
    "requestId": "01EKVV810DC7NJEC97BAQJZXWR",
    "version": "2.0.0",
    "entityCustomerReference": "customer-ref-12345",
    "overallRiskStatus": "LOW",
    "channel": "api"
}

Handling Notifications

Receive the Webhook

Your endpoint should respond with a 200 or 202 HTTP status code to acknowledge receipt. If your endpoint returns a 5xx or 4xx status code (other than 400), the system retries delivery multiple times over a period. A 400 status code stops retries.

Process the Notification Type

Use the notificationType and function fields to determine the appropriate action.

Retrieve Workflow Execution Results

Retrieve workflow execution results anytime post-execution by calling the following API endpoint:

GET Workflow Execution Results

GET /v2/individuals/{entityId}/serviceprofiles/{serviceName}/workflows/{workflowName}/executions/{workflowExecutionId}

Additional Security (JWT Authentication)

FrankieOne supports JSON Web Token (JWT) authentication to enhance the security of webhook notifications. By enabling JWT signing, you can verify the authenticity and integrity of the payloads sent to your webhook endpoint.

Notification payloads are secured through HTTPS and IP whitelisting. You can also enable JSON Web Token (JWT) signing for additional security. Contact support to enable JWT verification for your account.

JWT Structure

{
  "header": {
    "alg": "RS256",
    "typ": "JWT"
  },
  "body": {
    "sub": "[email protected]", // Portal notifications only
    "iat": 1516239022,        // UTC epoch timestamp in seconds
    "iss": "io.frankiefinancial.kycaml"  // Fixed string
  }
}

Security Features

RSA-4096 bit private key encryption
Customer-specific public key for verification
HTTPS with secure algorithms
IP whitelisting

Retry Mechanism

FrankieOne employs a robust retry mechanism to ensure reliable delivery of webhook notifications:

Initial Retry: Immediately after the first failure.
Exponential Backoff: Retries occur at increasing intervals.
Maximum Retries: Up to 50 attempts over 24 hours.

If all retries fail, the message is moved to a Dead Letter Queue (DLQ), and FrankieOne’s support team is notified. Contact support to retrieve messages from the DLQ if necessary.

KYC

​Available Notifications

Workflow Events

IDV Biometrics Events

Entity Events

​Workflow Events

​IDV Biometrics Events

​Entity Profile Events

​Webhook Structure

​Base Payload Schema

​Event-Specific Fields

​Endpoint Format

​Payload Examples

​Handling Notifications

​Additional Security (JWT Authentication)

​Retry Mechanism

Available Notifications

Workflow Events

IDV Biometrics Events

Entity Profile Events

Webhook Structure

Base Payload Schema

Event-Specific Fields

Endpoint Format

Payload Examples

Handling Notifications

Additional Security (JWT Authentication)

Retry Mechanism