Q1 2026 product roundup

Q1 2026 is done and it feels like one of the busiest at Griffin, ever. We shipped a few "quality of life" features whilst we're full speed ahead on some big bets for the year. But before we get ahead of ourselves, here's our roundup for Q1 2026!

Accrued interest is now visible in the API and app

You can now view accrued interest on any Griffin bank account both via the API and directly in the Griffin app. Show your customers how much interest they've earned so far in the current period by pulling the data from the API and surfacing it in your product.

To retrieve it, make a GET request to the account URL. The response will now include an accrued-interest object alongside the account balance. In the app, you'll find the figure in the account overview tab next to the balance.

Read the full release note →

You can now freeze and block bank accounts via the app or API

You can now apply restrictions to any bank account within your organisation via the API or the app. Two restriction types are available:

• Freeze‍—‌prevents outbound payments while allowing inbound payments to continue
• Block‍—‌prevents both inbound and outbound payments

Restrictions can be applied at any point in an account's lifecycle, updated as circumstances change, and lifted when no longer needed. Each restriction requires a reason code, legal status, and a note for context.

Read the full release note →

Savings account payouts now arrive an hour earlier

From 9 February 2026, we moved the withdrawal payout window for savings accounts from 5:00pm to 4:00pm (UK time). It might sound like a small change, but for fintechs whose customers rely on same-day access to their money, an hour can make a meaningful difference‍—‌especially when you're up against end-of-business cut-offs.

Here's how the updated schedule works:

• Requests made before 12:00pm on a working day → paid out from 4:00pm the same day
• Requests made after 12:00pm on a working day → paid out from 4:00pm the next working day
• Requests made on weekends or public holidays → paid out from 4:00pm the next working day

If you display payout times anywhere in your product, customer comms, or help docs, make sure those references reflect the new 4:00pm time.

Read the full release note →

Laying the groundwork for overseas payments

In February, we updated how we represent debtor and creditor information in payment API responses. This is a foundational change to support receiving overseas payments‍—‌something that's been on the roadmap and is actively in development.

The short version of what's changing in the API:

Account identification

• account-number becomes optional (still populated for all domestic payments)
• iban and bban introduced as optional fields
• other-account-identification introduced as a catch-all for schemes we can't yet process
• account-number-code deprecated

Bank identification

• bank-id becomes optional
• sort-code introduced as an optional field for UK domestic accounts
• bic introduced as an optional field
• other-institution-identification introduced for schemes we can't yet process
• bank-id-code deprecated

If your integration relies on account-number or bank-id being present, please get in touch so we can help you handle the transition. We'll continue populating both fields for domestic payments throughout this change‍—‌you'll only need to handle missing values to receive payments from non-UK accounts.

Outbound overseas payments support is coming soon.

Read the full release note →

That's "it". C'est ça. You can check out our product roadmap, jump into our sandbox to explore the API for free, or join our Slack community to keep up with the latest.