---
title: "Faster payments"
metaTitle: "Faster payments"
order: 1
showPageMenu: true
---

import EndpointBlock from "src/components/endpoint-block"
import WebhookPlaceholder from 'src/components/webhook-placeholder'
import Callout from 'src/components/callout'
import ExternalLink from 'src/components/external-link';

## Faster Payments overview

The Faster Payment System (FPS) is the most frequently used and fastest payment rail in the UK. It is instant or near-instant, and operates all hours of all days. All ClearBank UK GBP accounts support inbound and outbound Faster Payments.

You can initiate a Faster Payment using the [POST /v3/Payments/FPS](#send-faster-payments) endpoint, and receive confirmation of settlement from the [Transaction Settled webhook](#transaction-settled-webhook). You can send Faster Payments individually or in bulk with a single request.

Key aspects of FPS include:

* A payment limit of £1,000,000 on inbound and outbound payments.
* No cut-off times or operational holidays: Faster Payments settle near instantly 24 hours a day, 365 days a year.

## Features and functionality

### Validation requirements

Every Faster Payment is validated against these rules:

| Element     | Type   | Validation | Description  |
|-------------|--------|------------|--------------|
| `name`      | string | maxLength: 140<br /> minLength: 1 <br /> pattern: `^[a-zA-Z0-9\/\-?:().,’+\s#=!"%&*<>;{@\r\n]*$` | **Also known as Account Holder Name** <br /> This the creditor's name.<br /> If max length exceeds 35 characters, this will be truncated before sending to scheme.                                   |
| `reference` | string | maxLength: 35 <br /> minLength: 0 <br /> pattern: `^[a-zA-Z0-9\/\-?:().,’+\s#=!"%&*<>;{@\r\n]*$` | **Also known as the Payment Reference** <br /> This is the payment reference under remittance information. If the max length exceeds 18 characters, this will be truncated before sending to scheme. |

Pattern: Alphanumeric (uppercase and lowercase) and special characters*****.<br />
*****Special characters: **/** (forward slash), **-** (hyphen), **?** (question mark), **:** (colon), **(** (left parenthesis), **)** (right parenthesis), **.** (full stop), **,** (comma), **’** (right single quote), **+** (plus sign), &nbsp; (blank space), **#** (hash), **=** (equals), **!** (exclamation mark), **”** (right double quote), **%** (percentage), **&** (ampersand), ***** (asterisk), **<** (less than), **>** (greater than), **;** (semicolon), **{** (left curly bracket), **@** (commercial at), **CrLf** (carriage return line feed).

This endpoint uses the endToEndIdentification field as a duplicate check to ensure the request is idempotent.   

#### Abusive message filtering

To protect payment recipients from harm and abuse, outbound payments are subject to screening to check for profanities.

The screening checks the `Reference` string of the `RemittanceInformation` object. If any term in this string matches a term on the profanity list, it will be removed and the field will be blank when the payment reaches the beneficiary.

References will be removed if they match terms found in (but not limited to) the Pay.UK profanities list that can be found on the Reference Documents page of the Knowledge Centre. This can be accessed by signing in to the <ExternalLink href="../api/getting-started">ClearBank Portal</ExternalLink>.

The result of the screening can be found in the `SupplementaryData` object of the Transaction Settled webhook as follows:

| Abusive message screening result    | Supplementary Data value      |
|--------------------------------------|-------------------------------|
| Pass (no match)                      | `AbusiveMessageScreeningResult:Pass` |
| Fail (match)                         | `AbusiveMessageScreeningResult:Fail`<br /> `AbusiveMessageScreeningIdentifiers:paymentInstruction.creditTransfer.remittanceInformation.structured.creditorReferenceInformation.reference` |

### APP Scam protection and internal transfers

In line with legislation to prevent Authorised Push Payment (APP) scams, payments sent via the Faster Payments scheme may be in scope for APP scam reimbursement, allowing for the recovery of 50% of any consumer reimbursement (up to the claim limit) from the receiving Payment Service Provider (PSP). Further details are available on <ExternalLink href="https://www.wearepay.uk/appr-policy/">Pay.UK's website</ExternalLink>.

Only payments sent via scheme are in scope of APP scam reimbursement, however, when you initiate a payment and we identify that the recipient account is held by a ClearBank client, the payment method is updated to internal transfer by default.

To ensure you have control over the payment method and, by extension, your level of liability for reimbursement claims, the [POST /v3/payments/fps endpoint](#send-faster-payments) contains a **enforceSendToScheme** Boolean field.

- When set to **true**: the payment will be processed (and billed for) as a Faster Payment regardless of whether it is eligible to be processed as an internal transfer. 
- When set to **false** or not included: there will be no change to the existing behaviour.

<Callout colour="blue"><p>Note that if the <strong>enforceSendToScheme</strong> field is included in your payload but left blank, the request will fail and a 400 Bad Request response will be received.</p>
</Callout>

### Forward-dated and standing order payments

The `paymentTypeCode` field of the [POST /v3/payments/fps endpoint](#send-faster-payments) allows you to specify the type of payment using the following three-letter codes:

- `SIP` - Single immediate payment
- `SOP` - Standing order payment
- `FDP` - Forward-dated payment

This is an optional field. If not provided, the payment type will default to `SIP`.

<Callout colour="blue"><p>We do not warehouse payment instructions or standing order mandates. While the <strong>paymentTypeCode</strong> allows you to specify the type of payment, it is your responsibility to arrange to call the <strong>POST /v3/payments/fps</strong> endpoint on the required date and time.</p>

<p>You are responsible for ensuring you have an SOP mandate in place for any account that you send SOPs from.</p>
</Callout>

A bulk payment can contain a combination of SIPs, SOPs and FDPs. While SIPs and FDPs can be initiated at any time, **SOPs can only be sent Monday to Friday, excluding bank holidays, between 00:01 and 06:00am UK time**.

If a single or bulk SOP is initiated outside of the supported days/times, the request will not be accepted and a `400 Bad Request` response will be returned:

![Message flow diagram showing a single or bulk SOP payment sent outside of supported hours and returning a 400 Bad Request response](/assets/images/diagrams/uk/faster-payments/sop-payment.svg "SOP sent outside of supported hours")

If a bulk payment containing a combination of SIPs, SOPs and FDPs is initiated outside of the supported days/times, the SIPs and FDPs will be accepted and the SOPs will be rejected:

![Message flow diagram showing abulk payment containing SIPs, SOPs and FDPs sent outside of supported hours, a 202 Accepted response is returned, the SIPs and FDPs are accepted for processing and the SOPs are rejected](/assets/images/diagrams/uk/faster-payments/bulk-sop-payment.svg "Bulk payment containing SIPs, SOPs and FDPs sent outside of supported hours")

While a `202 Accepted` response will be returned if the provided payment details are valid, the payment `Response` for the SOPs will show as `Rejected`. **You will not receive a Transaction Rejected Webhook for SOPs sent outside of supported days/times**.

### Payment returns

Our Faster Payments service supports payment returns up to 90 days after clearing. You may sometimes need to return a Faster Payment, for example if:

- The beneficiary's name does not match that of the details of the account holder.
- The beneficiary's account has been closed or transferred.
- The beneficiary is deceased.

To return a single Faster Payment, you can use the [POST /v3/payments/fps/return](#return-a-faster-payment) endpoint.

ClearBank does not permit the return of Faster Payments over **90 calendar days old** or payments that are **temporarily ineligible for return** (for example, if the transaction has not yet settled or been reflected as settled throughout our system). If a return cannot be completed (including after retry attempts), you'll receive a **'400 - Bad Request'** response.

To return a payment older than 90 days, or a payment you cannot send through the return endpoint, make a normal outbound payment instead.

Faster Payments are dated against UTC from their clearing timestamp, which is given in the [Transaction Settled](#transaction-settled-webhook) webhook's `TimestampCreated` field. Held transactions can still age, so a payment held for over 90 days - identifiable from the same field in the [Transaction Held webhook](#inbound-transaction-held-webhook) - will also be invalid for return.

### Send Faster Payments Originating Overseas

Faster Payments Originating Overseas (FPOOs) must be sent using our dedicated endpoint: [POST /v2/payments/fps/singlepayment](#send-a-faster-payment-originated-overseas).

## Endpoints and webhooks

<EndpointBlock
type="post"
title="Send Faster Payments"
endpoints={[
  {
    path: "/v3/payments/fps",
    version: "3.0.FPS-payment",
    webhooks: [
      'transaction-settled-webhook-v6',
      'payment-message-assessment-failed-webhook-v1',
      'payment-message-validation-failed-webhook-v1',
      'transaction-rejected-v2'
    ]
  }
]}
/>

<WebhookPlaceholder render='transaction-settled-webhook-v6' />

#### Faster Payments Transaction Settled webhook error codes

| Error code                       | Description                                                                                | Recommended action                                                   | Retry Policy      |
|----------------------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------|-------------------|
| **AC03**                             | Beneficiary Sort Code/Account Number unknown                                               | Verify beneficiary account details and resubmit                      | Review then retry |
| **AC06**                             | Beneficiary Account stopped                                                                | Contact beneficiary to confirm account status or provide alternative | Review then retry |
| **AC07**                             | Beneficiary Account closed                                                                 | Contact beneficiary for updated account details                      | Review then retry |
| **AC09**                             | Account is not in currency quoted                                                          | Confirm currency requirements and resend in supported currency       | Review then retry |
| **AG01**                             | Terms and Conditions of Account do not permit crediting of these funds                     | Contact beneficiary for alternative payment method or account        | Do not retry      |
| **BE08**                             | Error stems from participant error or unavailability                                       | Please retry payment; if it continues to fail, wait and then retry   | Retry             |
| **CB_AccountHoldersBankrupt**        | Payment cannot be applied because of Beneficiary sensitivities – e.g. possible bankruptcy  | Do not retry; escalate and seek legal/compliance guidance            | Do not retry      |
| **CB_AccountNameAndNumberMismatch**  | The payment has been rejected by the receiving bank because the beneficiary account name does not match the beneficiary account number | Validate account name against account number (e.g. via CoP) before retrying | Review then retry |
| **CB_AccountSwitched**               | Account transferred                                                                        | Use account switching data (e.g. CASS redirection) or request updated details. Follow account switching/redirection guidance or obtain updated details  | Do not retry |
| **CB_InitiatingPartyActionRequired** | Sending FPS Institution action required                                                    | Review payment details and format and retry. If payment fails again, contact ClearBank | Review then retry |
| **CB_PaymentBeneficiaryNameMissing** | The payment has been rejected by the receiving bank as the beneficiary name is not present | Include beneficiary name and retry                                   | Review then retry |
| **CB_PaymentReferenceIncorrect**     | The payment has been rejected by the receiving bank due to reference information field being incorrect | Correct the reference format/content and resubmit        | Review then retry |
| **CB_PaymentReferenceMissing**       | The payment has been rejected by the receiving bank because the receiving account cannot be identified without a Payee Reference | Ensure mandatory payment reference is included and retry | Review then retry |
| **MD09** | Beneficiary deceased | Do not retry; contact beneficiary organisation or sender for next steps | Do not retry |
| **MS03** | Reasons not specified by end agent | Retry or contact beneficiary bank for clarification | Retry |
| **PY01** | The payment has been rejected due to an unknown sort code/account number | Reconfirm sort code and account number before resubmission | Review then retry |

<WebhookPlaceholder render='payment-message-assessment-failed-webhook-v1' />
<WebhookPlaceholder render='payment-message-validation-failed-webhook-v1' />
<WebhookPlaceholder render='transaction-rejected-v2' />
<WebhookPlaceholder render='inbound-held-transaction-v1' />
<WebhookPlaceholder render='outbound-held-transaction-v1' />

<EndpointBlock
type="post"
title="Return a Faster Payment"
endpoints={[
  {
    path: "/v3/payments/fps/return",
    version: "3.0.FPS-payment",
    webhooks: [
      'transaction-settled-webhook-v6'
    ]
  }
]}
/>

<EndpointBlock
  type="post"
  title="Send a Faster Payment Originated Overseas"
  endpoints={[
  {
    path: "/v2/payments/fps/singlepayment",
    version: "2.0.FPS-POO",
    webhooks: [
      'transaction-settled-webhook-v6',
      'payment-message-assessment-failed-webhook-v1',
      'payment-message-validation-failed-webhook-v1',
      'transaction-rejected-v2'
    ]
  }
]}
/>