DATE:
AUTHOR:
The Product team at Griffin
API App Security

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

DATE:
AUTHOR: The Product team at Griffin

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. They can be updated as circumstances change, and lifted when no longer needed. Each restriction requires:

  • a reason code

  • legal status

  • a note for context

You can view restrictions on an account at any time, including filtering for active restrictions only. Each time you apply, update, or lift a restriction, we generate a restriction event, giving you a full audit trail.

For more details, check out the managing restrictions guide.

Why we’ve added this

Account restrictions are a core tool for managing financial crime, responding to customer requests, and meeting regulatory obligations. This capability gives you direct control over account activity without needing to route requests through Griffin which is important in time-sensitive situations. For example, if your transaction monitoring flags an account as a suspected APP fraud perpetrator, you can immediately apply a restriction using the fraud-app-perpetrator reason code.

Will this affect existing integrations?

No, this is a new feature, there is no impact on existing integrations. You can adopt it at your own pace.

Questions?

We're here to help. Just reach out at support@griffin.com or get in touch with your Customer Success manager.


Thanks for reading!

 Read our docs

 Join our Slack community

 Follow us on LinkedIn

Powered by LaunchNotes