# United Kingdom: GBP

## Supported payment rails

| Rail | Description | Settlement | Limit |
|  --- | --- | --- | --- |
| `FPS` | Faster Payments Service. 24/7/365 availability. | Instant | £1,000,000 |
| `CHAPS` | Clearing House Automated Payment System. Business days only. Cut-off ~5:00 PM GMT/BST (bank-dependent). | Same-day | No limit |


Routing order: `FPS` is used when the beneficiary account is FPS-addressable and the amount is at or below £1,000,000; otherwise `CHAPS` applies.

For details on rail selection, see [Payment rail reference](/products/payments-direct-2/api-docs/integration-resources/payment-rail-reference).

## Beneficiary identity

When creating a beneficiary identity for GBP payments, provide the following fields. See [Create and manage identities](/products/payments-direct-2/api-docs/developer-guides/create-and-manage-identities) for the API workflow.

The required fields depend on whether the beneficiary is a **business** or an **individual**.

### Business beneficiary

Applies to **B2B**, **B2B2B**, and **C2B2B** use cases. Submit a `business` identity.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `businessName` | Required | STRING | 1–140 characters. |
| `address.streetAddress` | Required | ARRAY of STRING | Each item 1–70 characters. |
| `address.city` | Required | STRING | 1–140 characters. |
| `address.stateOrProvince` | Required | STRING | 1–140 characters. |
| `address.postalCode` | Required | STRING | 3–15 characters. |
| `address.country` | Required | STRING | Two-letter ISO 3166-1 alpha-2 country code. |


### Individual beneficiary

Applies to **B2C**, **B2B2C**, and **C2B2C** use cases. Submit an `individual` identity.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `firstName` | Required | STRING | 1–140 characters. |
| `lastName` | Required | STRING | 1–140 characters. |
| `dateOfBirth` | Required | DATE | ISO 8601 date (YYYY-MM-DD). |
| `address.streetAddress` | Required | ARRAY of STRING | Each item 1–70 characters. |
| `address.city` | Required | STRING | 1–140 characters. |
| `address.stateOrProvince` | Required | STRING | 1–140 characters. |
| `address.postalCode` | Required | STRING | 3–15 characters. |
| `address.country` | Required | STRING | Two-letter ISO 3166-1 alpha-2 country code. |


## Beneficiary financial instrument

When creating a financial instrument for GBP payouts, set `financialInstrumentType: GB_FPS` and `currency: GBP`. Provide the following fields in the `gbFps` payment rail object. See [Create and manage financial instruments](/products/payments-direct-2/api-docs/developer-guides/create-and-manage-financial-instruments) for the API workflow.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `bankName` | Required | STRING | 2–140 characters. |
| `sortCode` | Required | STRING | Exactly 6 digits. |
| `accountNumber` | Required | STRING | Exactly 8 digits. |


## Originator identity

When creating an originator identity for GBP payments, provide the following fields. The required fields depend on whether the originator is a **business** or an **individual**.

### Business originator

Applies to **B2B**, **B2B2B**, **B2B2C**, and **B2C** use cases. Submit a `business` identity.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `businessName` | Required | STRING | 1–140 characters. |
| `address.streetAddress` | Required | ARRAY of STRING | Each item 1–70 characters. |
| `address.city` | Required | STRING | 1–140 characters. |
| `address.stateOrProvince` | Required | STRING | 1–140 characters. |
| `address.postalCode` | Required | STRING | 3–15 characters. |
| `address.country` | Required | STRING | Two-letter ISO 3166-1 alpha-2 country code. |
| `registration` | Required | ARRAY of OBJECT | Each item: `number` (3–35 characters) and `type` (one of `INCORPORATION_CERTIFICATE`, `TAX_ID`). At least one registration entry is required. |


### Individual originator

Applies to **C2B2B** and **C2B2C** use cases. Submit an `individual` identity.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `firstName` | Required | STRING | 1–140 characters. |
| `lastName` | Required | STRING | 1–140 characters. |
| `dateOfBirth` | Required | DATE | ISO 8601 date (YYYY-MM-DD). |
| `address.streetAddress` | Required | ARRAY of STRING | Each item 1–70 characters. |
| `address.city` | Required | STRING | 1–140 characters. |
| `address.stateOrProvince` | Required | STRING | 1–140 characters. |
| `address.postalCode` | Required | STRING | 3–15 characters. |
| `address.country` | Required | STRING | Two-letter ISO 3166-1 alpha-2 country code. |


## Transaction fields

When creating a payment, provide the following fields. See [Create a payment](/products/payments-direct-2/api-docs/developer-guides/create-a-payment) for the API workflow.

| Field  | Required | Type | Constraints  |
|  --- | --- | --- | --- |
| `purposeCode` | Required | ENUM | 4–5 characters. See [Purpose of payment codes](#purpose-of-payment-codes) below. |
| `paymentMemo` | Optional | STRING | 0–16 characters. Pattern: `^[\w\/-?:(). '+\s]+$` |


### Purpose of payment codes

| Code | Description |
|  --- | --- |
| `ADCS` | Fees for advisory or consulting service |
| `BEXP` | Business expense payment |
| `BLDM` | Building maintenance payment |
| `COMC` | Commercial payment |
| `DBTC` | Debit transfer |
| `EDUC` | Education |
| `FEES` | Fee payment |
| `GIFT` | Gift payment |
| `GDSV` | Goods and services payment |
| `HREC` | Housing rent collection |
| `INSC` | Insurance claim settlement |
| `INSU` | Insurance payment |
| `INVS` | Investment settlement |
| `LOAR` | Loan repayment |
| `MDCS` | Medical service payment |
| `PCOM` | Residential property purchase |
| `RENT` | Property rental payment |
| `SALA` | Payment of salary |
| `SERV` | Service payment |
| `SUPP` | Supplier payment |
| `TAXS` | Tax settlement |


## Verifying requirements for your scenario

For the exact fields required for your specific use case and payment rail, use the [Payload Schema Utility](/products/payments-direct-2/api-docs/integration-resources/payload-schema-utility).