23 docs tagged with "payments"

Bacs is the UK payment scheme behind Direct Credits and Direct Debits. Griffin supports Bacs payments so your customers can pay their bills or receive credits. To send money, use Faster Payments.

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.

Credit Payment Recovery (CPR) is an industry procedure to bring consistency in the recovery method for Faster Payments (FPS) and settled Bacs payments (the Bacs recall pre-settlement process remains unchanged).

This guide will walk you through what happens when an organisation collects a Direct Debit from one of your accounts, and what you see over the API at each step. 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 working with Direct Debit mandates on your accounts: listing them, fetching one, cancelling one, and handling the cases where an expected mandate never appears. For the concepts behind mandates and the parties involved, see Direct Debits on Griffin accounts.

A Direct Debit lets an organisation collect money from a bank account with the account holder's ongoing authority, the standard UK mechanism for bills, subscriptions, and repayments. On Griffin, Direct Debits work in one direction: organisations your customers have authorised can collect from Griffin accounts. You cannot use Griffin to collect Direct Debits from accounts at other banks; see the Bacs overview for what is and isn't supported.

Whilst Griffin does not currently accept payments from overseas, it is possible for payments that have originated overseas to credit Griffin via the Faster Payment infrastructure. In such a scenario, the payment has been sent from overseas to a UK participant of Faster Payments before being sent onwards to Griffin as a Faster Payment. However, this is still considered a single payment, with the debtor bank being the overseas bank, and the creditor bank being Griffin.

Unfortunately, economic crime is prevalent in today’s financial system. Both you and we have a responsibility to ensure end customers are protected, and Griffin has a number of controls in place to reduce the risk to you and your customers.

Payees provide a way to store a payee name (account-holder) against UK payment details - an account number (account-number) and a sort code (bank-id) - and to easily reference these when making a payment.

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.

Given the large volumes of payments that flow each day it is natural that errors occur. See below for various scenarios and how you should manage them.

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.

Making a payment is a multistep process. There are several resources that you will need to interact with throughout its processing lifecycle which are described below.

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

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

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.

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:

Typically outward instant payments are sent immediately after they have been submitted, and received in the creditor's account shortly after that. Withdrawal schedules and regular outage periods introduce a delay between payment submission and the payment being sent.