31 docs tagged with "developer guide"

Our platform supports two levels of API authentication.

This guide will show you how to close a bank account via the API. It covers all types of bank accounts.

Confirmation of Payee (CoP) is a payee checking service that helps prevent UK domestic payments from being sent to the wrong account. It does this by making sure the payee account details provided match the details held by their provider.

A payee stores the details of someone you want to send money to - this could be an individual, joint account holders, or a business. Similar to saving a contact, once you've saved someone as a payee, you can easily make future payments to them without re-entering their information.

An event occurs when the state of an API resource changes. For example, a transaction-created event occurs whenever funds are deposited or withdrawn from a Griffin bank account.

When you encounter an error, we’ll try to give you as much detail as possible about what went wrong and how you can fix it.

Welcome to the Griffin API! This guide will take you through creating an API key and introduce some concepts you need to get started.

We’ve released our Model Context Protocol (MCP) server in beta. You can find it on Github.

This guide will show you how to invite new users to your organisation.

Pooled safeguarding or client money accounts are used to hold money on behalf of multiple customers, also known as members of the pool. You are responsible for making sure membership of the pooled account is accurate and up-to-date.

There are four steps to onboarding a company with Verify.

There are four steps to onboarding a sole trader with Verify.

There are four steps to onboarding an individual with Verify.

A client money account is for managing your customers' funds. Only firms regulated under CASS (the FCA's Client Assets Sourcebook) can open client money accounts. You can choose to open a dedicated account for each of your customers, or a pooled account for holding funds from multiple customers. Learn more about bank accounts.

A safeguarding account is for managing your customers funds. Only firms regulated as Electronic money institutions (EMIs) and payments institutions (PIs) in the UK can open safeguarding accounts. You can choose to open a dedicated account for each of your customers, or a pooled account for holding funds from multiple customers. Learn more about bank accounts.

A savings account enables you to offer savings products to your customers. Learn more about savings accounts.

An embedded account enables you to offer a real bank account to your customers. Learn more about embedded accounts.

An operational account is a bank account for managing your organisation's own funds. Learn more about bank accounts.

In outsourcing we do not complete third party checks on the data sent to our system, this is done by you. We are validating that required data exists and that the customer is not out of appetite for industry, jurisdiction or risk profile purposes.

In order to provide you with greater control over payments from your bank accounts, we have split responsibilities for making and approving payments into two separate roles; Request payments and Approve payments. Learn more about roles and memberships.

Our guides aim to explain relevant domain concepts, introduce the API entities that you will be using to construct payment flows, and provide examples to help you get up and running quickly with your payments integration.

This guide will walk you through receiving a book transfer to one of your accounts. Payment processing is a multi-step process which requires interacting with several resource types. Learn about payments, transactions, submissions and admissions here

This guide will walk you through receiving a payment to one of your accounts. Payment processing is a multi-step process which requires interacting with several resource types. Learn about payments, transactions, submissions and admissions here

Griffin automatically receives payments on your behalf. We recommend creating a webhook to receive notifications of new inbound payments and track their status through admissions.

Reliance is for use by regulated firms only, onboarding via Reliance is only available by API.

This guide walks you through making a payment between two Griffin accounts that you control. Payment processing is a multi-step process which requires interacting with several resource types. Learn about payments, transactions, submissions and admissions here

This guide will walk you through making a payment to a UK bank account. Payment processing is a multi-step process which requires interacting with several resource types. Learn about payments, transactions, submissions and admissions here

This guide provides an overview of the process of sending and tracking a payment to completion, regardless of the scheme it's sent over. To learn how to submit a payment for a specific scheme, see our scheme-specific guides:

Message signatures allow us to verify that API requests come from a valid source and ensure the integrity of each request.

This guide explains how to verify that the events you receive through webhooks are genuinely from Griffin using HTTP message signatures.

Overview