Payouts to United Kingdom

Review these United Kingdom-specific requirements before initiating GBP payouts. For the general
cross-border payment flow, see
Sending Cross-Border Payments.

Supported configurations

United Kingdom payouts support the following participant types:

• C2C (consumer-to-consumer) — individual customer to individual counterparty
• B2C (business-to-consumer) — business customer to individual counterparty
• B2B (business-to-business) — business customer to business counterparty

Payouts use the FPS (Faster Payments Service) rail with sort code and account number routing.

Trading account requirement

United Kingdom payouts require a USDC_SOL trading account as the source. Other trading account types
(such as USDC or USDC_NPL) are not supported for GBP payouts.

Verify GBP payout availability

Confirm your bank supports GBP payouts for your participant type.

ℹ️

Bank configuration required

Contact Cybrid support to enable GBP payouts and configure the United Kingdom as a supported
corridor for your bank.

GET /api/banks/{bank_guid}
Authorization: Bearer YOUR_TOKEN

Look for entries in supported_payout_symbols where:

• symbol: GBP-USD or GBP-USDC_SOL
• country_code: GB
• participants_type: C2C, B2C, or B2B
• route: bank_account

You can also query prices for the United Kingdom:

GET /api/prices?payout_country_code=GB
Authorization: Bearer YOUR_TOKEN

Identity verification requirements

The platform validates all required KYC fields when you create a plan for GBP payouts.

Originator (Customer)

Individual originator (C2C):

• name.first, name.last
• date_of_birth
• address.street, address.city, address.country_code

Business originator (B2C, B2B):

• name.full
• address.street, address.city, address.country_code
• identification_numbers with one of:
  • tax_identification_number
  • employer_identification_number
  • business_registration_number

Receiver (Counterparty)

Create the counterparty with the
standard required fields
for the appropriate type (individual or business). The counterparty must be in verified state
before you can create the external bank account and plan.

Individual counterparty (C2C, B2C):

• name.first, name.last
• address.country_code

Business counterparty (B2B):

• name.full
• address.country_code

Purpose of transaction

For United Kingdom payouts, purpose_of_transaction is required for all participant types.
All standard purpose values are accepted.

B2B invoice documents

B2B payouts require supporting invoice documents at plan creation time. Include the document
files in the plan request body.

External bank account setup

Send a POST request to /api/external_bank_accounts with the following format.

Uses sort code routing with bank_code_type: SORT_CODE and payment_rail: FPS.

{
  "account_kind": "raw_routing_details",
  "name": "UK beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "SORT_CODE",
    "bank_code": "200000",
    "account_identifier": "12345678",
    "payment_rail": "FPS"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "GBP"
}

ℹ️

Sandbox test values

In sandbox, use sort_code: 200000 and account_number: 12345678. These values are accepted
by the sandbox payer and allow you to exercise all three participant types (C2C, B2C, B2B).

ℹ️

API versioning

Creating external bank accounts with foreign raw routing details requires
Accept-Version: 2025-10-01 or later.

For the full account model and field reference, see
Create Foreign Fiat External Bank Accounts.

Validation rules

• Sort code: Must be exactly 6 digits (for example, 200000)
• Account number: Must be exactly 8 digits (for example, 12345678)
• Payment rail: Must be FPS

Common validation errors

Related resources

• Sending Cross-Border Payments
• Create Foreign Fiat External Bank Accounts
• Creating a Counterparty
• Verifying a Counterparty
• Create Plan API Reference