ClearBank

SEPA Credit Transfer UK

SEPA Credit Transfer UK

Our SEPA Credit Transfer UK (SCT UK) service lets you receive euro payments from any SEPA participant bank via the SEPA Credit Transfer (SCT) scheme. To get started with SCT UK, you'll need a euro account under a ClearBank UK BIC. This will be set up for you as part of your onboarding process.

If you're interested in using this new service, please contact your Client Director.

Availability and hours

SCT UK is available Monday to Friday from 07:00 to 14:30 UK time, and is subject to scheme holidays.

The scheme holidays applicable to SCT UK are listed below:

  • New Year's Day
  • Good Friday
  • Easter Monday
  • Labour Day
  • Christmas Day
  • Boxing Day / Christmas Holiday

Exact dates can be found on the ECB's website.

Inbound payments

When you receive an SCT payment, you'll be notified via webhook. To receive webhooks, you'll need to subscribe to them first using the ClearBank Portal.

Our SCT UK service has two dedicated inbound payment webhooks:

  • Payments.CrossBorder.InboundPaymentCompleted - Cross-border Inbound Payment Completed webhook - This webhook contains detailed ISO 20022 compliant payment information of any inbound SCT payments.
  • CustomerAccounts.TransactionCompleted - Customer Account Transaction Completed webhook - This webhook contains the minimum information necessary to reconcile a payment.

Note: if you are subscribed to our inbound Multi-Currency Payments service webhooks, Payments.Mccy.TransactionCreated and Payments.Mccy.TransactionSettled, these will also notify you of any inbound SCT payments. All of these webhooks' TransactionId field will have the same UUID whenever they refer to the same payment, so you can use this field in your idempotency logic to prevent double counting of inbound SCT payments.

Simulation endpoints

Simulate an inbound payment

post/payments/cross-border/v2/inbound/payments

This endpoint is available in the simulation environment only. You can call this endpoint to simulate an inbound SCT payment. After submitting a valid request, you'll receive a Payments.Mccy.InboundPaymentCompleted webhook and a CustomerAccounts.TransactionCompleted webhook. If you are also subscribed to our Multi-currency Payments webhooks, Payments.Mccy.TransactionCreated and Payments.Mccy.TransactionSettled, you will also receive these.

Parameters

  • Authorization string, header, Required

    Your API token, retrieved from the ClearBank Portal.

  • DigitalSignature string, header, Required

    Signed hash of the body of the request. The hash is signed by your private key.

  • X-Request-Id string, header, Required

    A unique identifier for the request; valid for 24 hours, max length 83.

Request Payload (application/json)

  • interbankSettlementAmount object, Required

  • paymentIdentification object, Required

  • creditorAccount object, Required

  • remittanceInformation object, Required

request

{
"interbankSettlementAmount": {
"amount": 1234.56,
"currency": "EUR"
},
"paymentIdentification": {
"endToEndIdentification": "E2E1234567890"
},
"creditorAccount": {
"iban": "GB13CBAB2233441234567"
},
"remittanceInformation": {
"unstructured": [
"myRemittanceInformation-111-ABC"
],
"structured": [
{
"reference": "MY-structured-REM-INFO"
}
]
}
}
Code copied

Response (application/json)

  • 202 Accepted
  • 409 Conflict
  • 422 Unprocessable Content
  • 500 Internal Server Error
  • 503 Service Unavailable

Conflict

{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}
Code copied

Unprocessable Content

{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}
Code copied

Associated Webhooks