API Verify Reliance

Additional customer data requirements for 01 February 2026

We need additional information from your customers by 01 February 2026.

September 11, 2025

API Security

Webhook signature validation is now available

You can now verify that webhook events are genuinely from Griffin using HTTP message signatures. This adds an extra layer of security to protect...

June 18, 2025

API

The Griffin MCP server

We’re releasing our Model Context Protocol (MCP) server in beta. You can find it here on Github . The server gives your AI agents an easy way to interact...

May 29, 2025

App Payments

We've added new payments roles to give you more control over approvals

Previously, we had a single role for all Payments related actions in the app. After feedback on needing approvals, we’ve now split this role into three...

May 23, 2025

API Payments

Internal book transfers are now included as a payment scheme in the API

What’s changing? We’re separating out Book transfers and Faster Payments (FPS) in our API payment schemes. From 1st July 2025, you’ll need to specify which...

April 30, 2025

Verify

Onboard individuals resident outside of the UK

You can now onboard individuals resident in the following countries and regions outside of the UK: European Union United Arab Emirates Hong Kong Australia...

April 23, 2025

Embedded bank accounts

Embedded bank accounts are now available in beta

Introducing a new type of bank account We’ve introduced a new type of bank account: embedded bank accounts! Our embedded bank accounts are all-purpose. They...

April 8, 2025

API Verify Reliance

Update specific customer information without triggering a full verification

You can now update specific information (claims data) without having to trigger a full rerun of the verification process.

January 23, 2025

Security

Message signing now mandatory for API requests

Message signing is now required for all API requests in our live environment. Any unsigned requests will fail.

January 15, 2025

API App

Changes to the occupation field in our individual onboarding workflow

If you are using our API for onboarding, the occupation field in the employment claim is now optional.

November 12, 2024