Somehow it is Q3. I still remember New Year’s eve like it was yesterday, but summer solstice has passed and I am enjoying watching Wimbledon a bit too much as I write this. It’s been a busy Q2 with some major releases. Let’s dive in and go through all the big updates.

We improved payment approvals with new roles

We've split our payments role into three distinct roles to give you more control over payment approvals:

• Request payments‍—‌submit payments that require approval
• Approve payments‍—‌approve payments from others (but not your own)
• Approve own payments‍—‌submit and instantly approve payments

This update makes it easier to implement approval workflows within your organisation. Read our full release note here

We launched the Griffin MCP server for your AI agents

We took a giant leap into the future of AI and banking by releasing our beta MCP server. This gives your AI agents an easy way to interact with the Griffin API through any MCP client, including Claude Desktop and code editors like Cursor. While other banks aren't built for AI interaction, we are. Our MCP server lets agents open accounts, make payments, and analyse transactions‍—‌all while maintaining proper safeguards. The server is currently limited to our sandbox environment. Watch the demo above or linked here.

We improved security with message signatures for webhooks

We've added webhook signature validation to give you extra confidence that webhook events are genuinely from Griffin. You can now verify webhook signatures using our public keys, protecting your systems from potential tampering or spoofed requests. This security enhancement includes signature headers on each webhook, public key retrieval from our API, and automatic key rotation for ongoing security. Read our full release note here.

We made Book transfers available as a payment scheme

We've separated out book transfers and Faster Payments (FPS) in our API payment schemes. Book transfers are payments between two bank accounts within your Griffin organisation. They can go through our ledger without going through an external payment rail.Read our full release note here.

And finally, a big thank you to our customers who joined our research sessions!

Thank you for helping us with our UX research, telling us what works, what doesn’t work and generally what you’d like to see more of in the future. We love building alongside our community. More to come!

So what do you think? Did we have a good quarter or could we do better? Feel free to get in touch at product@griffin.com and let us know.

Remember, you can check out our product roadmap, have a play in our sandbox, and join our community for the latest updates and chatter. See you in Q3 when we should have some very exciting updates for you about payments and more.