SEPA Instant Credit Transfer

SEPA Instant Credit Transfer (SCT Inst) is a pan-European payment scheme that enables real-time euro transfers, delivering funds to the recipient within 10 seconds, 24 hours a day, 365 days a year.

You can:

Send an SCT Inst payment
Receive an SCT Inst payment
Recall an SCT Inst payment (integrating with recall payments is required)
Receive and respond to a recall request
Simulate SCT Inst payment scenarios
You are notified of incoming SCT Inst payments via the SEPA Instant Inbound Payment Settled webhook and the Customer Accounts Transaction Completed webhook.

To send an SCT Inst payment, use the POST /v1/payments/sepa-instant endpoint.

The SCT Inst scheme does not have a limit for maximum payment amounts, and ClearBank does not impose one. Instead, our clients are responsible for provisioning and managing transaction limits for their underlying customers in accordance with their own operational and risk requirements.

Transactions must be settled within a normal maximum of 5 seconds, with an upper limit of 10 seconds permitted only in exceptional circumstances, as mandated by SCT Inst 2025 rulebook.

You will receive the SEPA Instant Outbound Payment Created webhook. If 10 seconds pass without settlement, you'll receive the SEPA Instant Outbound Payment Delayed webhook. Once the payment has settled, you will receive the SEPA Instant Outbound Payment Settled webhook and the Customer Accounts Transaction Completed webhook.

A message flow diagram explaining how to send an SCT Inst payment

Send an SCT Inst payment

post/v1/payments/sepa-instant

This endpoint is used to create an outbound SCT Inst payment. No limit for external payments, limit of up to €999,999,999.99 for your internal ClearBank accounts. If you make an error on an internal payment, this can only be corrected with a new payment request: you cannot recall payments made to your own accounts.

Parameters

Authorization string, header, Required
Your API Token, obtained 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)

amount number, Required
Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency (EUR).
Minimum
0
creditor object, Required
creditorAgent object
debtor object, Required
endToEndId string, Required
Unique identification, as assigned by the originating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Minimum length
1
Maximum length
35
Pattern
^[0-9a-zA-Z/\-\?:\.,'\+ ]+$
reference string
Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system.
Minimum length
1
Maximum length
140
ultimateCreditor object
ultimateDebtor object

request

{
  "amount": 10,
  "creditor": {
    "name": "John Doe",
    "accountIban": "DE75512108001245126199",
    "postalAddress": {
      "streetName": "Morissette Union",
      "buildingNumber": "99",
      "townName": "Sipesville",
      "postCode": "RV7 4IS",
      "countrySubdivision": "Buckinghamshire",
      "country": "GB"
    },
    "identification": {
      "organisationIdentification": {
        "bic": "CLRBNL2AXXX"
      }
    }
  },
  "creditorAgent": {
    "bic": "CLRBNL2AXXX"
  },
  "debtor": {
    "name": "John Doe",
    "accountIban": "NL73ABNA0529451824",
    "postalAddress": {
      "streetName": "Morissette Union",
      "buildingNumber": "99",
      "townName": "Sipesville",
      "postCode": "RV7 4IS",
      "countrySubdivision": "Buckinghamshire",
      "country": "GB"
    },
    "identification": {
      "organisationIdentification": {
        "bic": "CLRBNL2AXXX",
        "lei": "724500EAW1MTCM9M1X68",
        "genericIdentification": {
          "id": "string",
          "schemeName": {
            "item": "string",
            "itemElementName": 0
          },
          "issuer": "string"
        }
      }
    }
  },
  "endToEndId": "0947eaf6-2b51-496b-afba-969a0a712d1",
  "reference": "INV-00002 2020-01-21",
  "ultimateCreditor": {
    "name": "John Doe",
    "identification": {
      "organisationIdentification": {
        "bic": "CLRBNL2AXXX"
      }
    }
  },
  "ultimateDebtor": {
    "name": "John Doe",
    "identification": {
      "organisationIdentification": {
        "bic": "CLRBNL2AXXX",
        "lei": "724500EAW1MTCM9M1X68",
        "genericIdentification": {
          "id": "string",
          "schemeName": {
            "item": "string",
            "itemElementName": 0
          },
          "issuer": "string"
        }
      }
    }
  }
}

Code copied

Response (application/json)

202 Accepted
400 Bad Request

Accepted

{
  "paymentId": "1fd63af1-83e2-3a8a-1014-3daa0e1c5f28"
}

Code copied

Bad Request

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

Code copied

Associated Webhooks

SEPA Instant Outbound Payment Created webhook
SEPA Instant Outbound Payment Settled webhook
SEPA Instant Outbound Payment Cancelled webhook
Customer Accounts Transaction Completed webhook
SEPA Instant Outbound Payment Delayed webhook

This webhook confirms an SCT Inst outbound payment has been created.

Request body

{
    "Type":"Sepa.Instant.Outbound.Payment.Created",
    "Version":1,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`TransactionId`	Required Unique identifier as assigned by ClearBank. Type: `string` Format: `uuid`
`PaymentId`	Required Unique identifier for payment assigned by ClearBank. This will match the paymentId returned in the 202 response when you initiated the payment. Type: `string` Format: `uuid`
`TimestampCreated`	Required Date and time transaction was created, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalPaymentProperties`	Optional Type: `object` `Key` Type: `null` or `string` Pattern: `[^\n]` `Value` Type: `null` or `string` Pattern: `[^\n]`

Example SEPA Instant Outbound Payment Created webhook request body

{
  "Type": "Sepa.Instant.Outbound.Payment.Created",
  "Version": 1,
  "Payload": {
    "TransactionId": "872237b4-c981-a835-8d6b-0e3d704a661c",
    "PaymentId": "872237b4-c981-a835-8d6b-0e3d704a661c",
    "TimestampCreated": "2025-01-22T12:54:42.1408507Z",
    "EndToEndId": "sMLnipYzjNSrxp4QUA1Tqi0Xo8uHnLRYJaS",
    "AdditionalPaymentProperties": null
  },
  "Nonce": 1839160681
}

Example webhook response

{
    "Nonce": 1839160681
}

This webhook confirms an outbound SCT Inst payment has settled.

Request body

{
    "Type":"Sepa.Instant.Outbound.Payment.Settled",
    "Version":1,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`TransactionId`	Required Unique identifier as assigned by ClearBank. Type: `string` Format: `uuid`
`PaymentId`	Required Unique identifier for payment assigned by ClearBank. This will match the paymentId returned in the 202 response when you initiated the payment. Type: `string` Format: `uuid`
`TimestampCreated`	Required Date and time transaction was created, in UTC. Type: `string` Format: `date-time`
`TimestampSubmitted`	Required Date and time transaction was sent to scheme, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalPaymentProperties`	Optional Type: `object` `Key` Type: `null` or `string` Pattern: `[^\n]` `Value` Type: `null` or `string` Pattern: `[^\n]`

Example SEPA Instant Outbound Payment Settled webhook request body

{
   "Type":"Sepa.Instant.Outbound.Payment.Settled",
   "Version":1,
   "Payload":{
      "TransactionId":"24d683a7-ae69-3035-c748-94827ddcbf92",
      "PaymentId":"24d683a7-ae69-3035-c748-94827ddcbf92",
      "TimestampCreated":"2024-10-11T13:34:59.682719Z",
      "TimestampSubmitted":"2024-10-11T13:35:01.9941075Z",
      "EndToEndId":"5g3qDxv7BCF3sgYy6hJmomi7GqlAc8jstHs",
      "AdditionalPaymentProperties":[
         {
            "Key":"InterBankSettlementDate",
            "Value":"2024-10-11"
         }
      ]
   },
   "Nonce": 1630803960
}

Example webhook response

{
    "Nonce": 1630803960
}

This webhook confirms an SCT Inst outbound payment has been cancelled.

Request body

{
    "Type":"Sepa.Instant.Outbound.Payment.Cancelled",
    "Version":1,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`TransactionId`	Required Unique identifier as assigned by ClearBank. Type: `string` Format: `uuid`
`PaymentId`	Required Unique identifier for the payment, assigned by ClearBank. This will match the paymentId returned in the 202 response when you initiated the payment. Type: `string` Format: `uuid`
`TimestampCreated`	Required Date and time the transaction was created, in UTC. Type: `string` Format: `date-time`
`TimestampSubmitted`	Required Date and time the transaction was sent to scheme, in UTC. Type: `string` Format: `date-time`
`CancellationCode`	Required The cancellation code for the reason the outbound payment was cancelled. Type: `string` Pattern: `[^\n]`
`CancellationReason`	Required Reason the outbound payment was cancelled. Type: `string` Pattern: `[^\n]`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalPaymentProperties`	Optional Type: `object` `Key` Type: `null` or `string` Pattern: `[^\n]` `Value` Type: `null` or `string` Pattern: `[^\n]`

Example SEPA Instant Outbound Payment Cancelled webhook request body

{
  "Type": "Sepa.Instant.Outbound.Payment.Cancelled",
  "Version": 1,
  "Payload": {
    "TransactionId": "a6c26de0-8aae-79d9-eef7-208dfd072632",
    "PaymentId": "a6c26de0-8aae-79d9-eef7-208dfd072632",
    "TimestampCreated": "2025-01-22T12:54:15.5337199Z",
    "TimestampSubmitted": "2025-01-22T12:54:20.5337358Z",
    "CancellationCode": "AC04",
    "CancellationReason": "Closed Account Number",
    "EndToEndId": "dTQC8O0EoyMBvxURbgghRrJMWBTtwCT78GU",
    "AdditionalPaymentProperties": null
  },
  "Nonce": 1355726072
}

Example webhook response

{
    "Nonce": 1355726072
}

Outbound payments may be cancelled due to internal validation failure (the payment did not pass our internal validation rules) or external validation failure (the payment did not pass SEPA scheme or beneficiary bank validation rules). Cancelled payments return a reason code which is reflected in the CancellationCode field of the SEPA Instant Outbound Payment Cancelled webhook. The cancellation codes include, but are not limited to:

Reason code	Description	Internal validation failure	External validation failure
AB05	Timeout Creditor Agent		X
AB08	Offline Creditor Agent		X
AB09	Error Creditor Agent		X
AB10	Error Instructed Agent		X
AB15	Account Is Held Suspense Account / Account Is Repair Suspense Account	X
AC01	Account identifier invalid or incorrect	X	X
AC04	Account Not Active / Closed	X	X
AC06	Blocked Account	X	X
AG01	Transaction Forbidden		X
AG10	Agent Suspended		X
AG11	Creditor Agent Suspended		X
AM03	EUR Currency Not Enabled	X
AM04	Insufficient Funds	X	X
AM05	Duplication		X
BE01	Account Does Not Belong To Institution	X
BE04	Missing Creditor Address		X
CB01	Unknown Error	X	X
CB02	A valid creditor agent BIC cannot be derived from the supplied IBAN	X
CB05	Payment delayed		X
CNOR	Creditor Bank Is Not Registered	X	X
DNOR	Debtor Bank Is Not Registered		X
MD07	End Customer Deceased		X
MS02	Not Specified Reason Customer Generated		X
MS03	Payment failed screening, re-send via SCT		X
RC01	Bank Identifier Incorrect		X
RC05	Invalid BIC Identifier	X
RR03	Missing Creditor’s Name Or Address		X
RR04	Regulatory Reason		X
TM01	Invalid Cut Off Time		X

This webhook notifies you if an SCT Inst outbound payment has not settled within 10 seconds of receiving the payment request. After receiving this webhook, you can still expect to receive a payment settled or payment cancelled webhook - there is no need to retry the payment.

Request body

{
    "Type":"Sepa.Instant.Outbound.Payment.Delayed",
    "Version":1,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`TransactionId`	Optional Unique identifier as assigned by ClearBank. If the transaction later settles, the TransactionId will differ from the original payment. If it is cancelled, it will remain the same. Type: `string` Format: `uuid`
`PaymentId`	Required Unique identifier for payment assigned by ClearBank. This will match the paymentId returned in the 202 response when you initiated the payment. Type: `string` Format: `uuid`
`TimestampCreated`	Optional Date and time the transaction was created, if known, in UTC. Type: `string` Format: `date-time`
`TimestampReceived`	Required Date and time your API request for this payment was received, in UTC. Type: `string` Format: `date-time`
`TimestampSubmitted`	Optional Date and time the transaction was sent to scheme, if known, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalPaymentProperties`	Optional Type: `object` `Key` Type: `null` or `string` Pattern: `[^\n]` `Value` Type: `null` or `string` Pattern: `[^\n]`

Example SEPA Instant Outbound Payment Delayed webhook request body

{
  "Type": "Sepa.Instant.Outbound.Payment.Delayed",
  "Version": 1,
  "Payload": {
    "TransactionId": "2a4cfec4-3285-5028-81c8-452c71a21e39",
    "PaymentId": "c98ef592-fb52-54ac-b49d-54c10bfde8bf",
    "TimestampCreated": "2025-01-21T12:53:15.5312199Z",
    "TimestampReceived": "2025-01-21T12:54:15.3837149Z",
    "TimestampSubmitted": "2025-01-21T12:54:20.5367358Z",
    "EndToEndId": "bzuImc97ohDbzvPNgtfME8zysCOdRQrel52",
    "AdditionalPaymentProperties": null 
  }, 
  "Nonce": 5800496862
}

Example webhook response

{
    "Nonce": 5800496862
}

This webhook confirms a transaction has completed.

Request body

{
    "Type": "CustomerAccounts.TransactionCompleted",
    "Version": 1,
    "Payload": {...},
    "Nonce":
}

Customer Accounts Transaction Completed webhook payload

Element	Description
`TransactionId`	Required Unique identification, assigned by ClearBank, to unambiguously identify the transaction. Type: `string`
`EndToEndIdentification`	Required The end-to-end identification can be used for reconciliation or to link tasks relating to the transaction. Type: `string`
`CreatedDateTime`	Required The date time in which the transaction was created in ClearBank's system. Type: `string`
`CompletedDateTime`	Required The date time on which the amount of money ceases to be available or becomes available to the account in ClearBank's system. Type: `string`
`ClearingChannel`	Required The clearing channel to be used to process the transaction. Type: `string`
`DebitCreditCode`	Required Movement of transaction. Type: `string`
`Amount`	Required Amount of money to be moved between the debtor and creditor. Type: `decimal`
`Currency`	Required Unit of currency is explicit and compliant with ISO 4217. Type: `string`
`RemittanceInformation`	Required Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system. Unstructured data or flattened version of the structured data. Type: `string`
`CreditorAccount`	Required Unambiguous identification of the account of the debtor to which a debit entry is posted. Type: `object` `AccountId` Represents the account ID used within ClearBank's systems. Type: `string` `IBAN` The IBAN for the account. Type: `string` Max. Length: `34` `BBAN` The BBAN for the account. Type: `string` Max. Length: `30` `Descriptor` Represents an arbitrary account descriptor. Type: `string`
`DebtorAccount`	Required Unambiguous identification of the account of the creditor to which a credit entry is posted. Type: `object` `AccountId` Represents the account ID used within ClearBank's systems. Type: `string` `IBAN` The IBAN for the account. Type: `string` Max. Length: `34` `BBAN` The BBAN for the account. Type: `string` Max. Length: `30` `Descriptor` Represents an arbitrary account descriptor. Type: `string`

Example Customer Accounts Transaction Completed webhook request body for inbound SCT Inst payment

{
   "Type":"CustomerAccounts.TransactionCompleted",
   "Version":1,
   "Payload":{
      "TransactionId":"e05bfe3b-3187-28b1-340d-57d57a8739fa",
      "EndToEndIdentification":"12345678",
      "CreatedDateTime":"2025-02-10T12:52:43.7433333Z",
      "CompletedDateTime":"2025-02-10T12:52:43.7666667Z",
      "ClearingChannel":"SEPA-Instant",
      "DebitCreditCode":"Credit",
      "Amount":1000.0,
      "Currency":"EUR",
      "RemittanceInformation":"e05bfe3b-3187-28b1-340d-57d57a8739fa",
      "DebtorAccount":{
         "AccountId":null,
         "Iban":"GB68INST20182441739477",
         "Bban":null,
         "Descriptor":null
      },
      "CreditorAccount":{
         "AccountId":"5602a737-675f-4c85-bbc1-d5d4b4478e64",
         "Iban":"NL25CLRB0066110527",
         "Bban":null,
         "Descriptor":null
      }
   },
   "Nonce":263934935
}

Example webhook response

{
    "Nonce": 263934935
}

Example Customer Accounts Transaction Completed webhook request body for outbound SCT Inst payment

{
   "Type":"CustomerAccounts.TransactionCompleted",
   "Version":1,
   "Payload":{
      "TransactionId":"8fa1ceea-e592-480c-26fa-1fd040c89df1",
      "EndToEndIdentification":"0947eaf6-2b51-496b-afba-969a0a72f38",
      "CreatedDateTime":"2025-02-10T15:54:09.97Z",
      "CompletedDateTime":"2025-02-10T15:54:14.29Z",
      "ClearingChannel":"SEPA-Instant",
      "DebitCreditCode":"Debit",
      "Amount":100.0,
      "Currency":"EUR",
      "RemittanceInformation":"testing instant",
      "DebtorAccount":{
         "AccountId":"5602a737-675f-4c85-bbc1-d5d4b4478e64",
         "Iban":"NL25CLRB0066110527",
         "Bban":null,
         "Descriptor":null
      },
      "CreditorAccount":{
         "AccountId":null,
         "Iban":"DE25370502991000122343",
         "Bban":null,
         "Descriptor":null
      }
   },
   "Nonce":1778087803
}

Example webhook response

{
    "Nonce": 1778087803
}

When you call our endpoints in simulation, any IBANs you provide are validated. To support your testing, the below tables list valid and invalid IBANs for your use:

Valid IBAN	Country
NL73ABNA0529451824	Netherlands
FR7630006000011234567890189	France
GB33BUKB20201555555555	UK
DE75512108001245126199	Germany
DK9520000123456789	Denmark
IE07BOFI900017556967	Ireland
PT88003506514393326125714	Portugal
ES7921000813610123456789	Spain
AT483200000012345864	Austria

Invalid IBAN	Country
GB20FMFX42731695687653	UK
NL51IKXV1050288017	Netherlands
BE66173933352443	Belgium
LT089128849492191749	Lithuania

Receipt of an SCT Inst payment can be confirmed by subscribing to the SEPA Instant Inbound Payment Settled webhook.

This webhook confirms an inbound SCT Inst payment has settled.

Request body

{
    "Type":"Sepa.Instant.Inbound.Payment.Settled",
    "Version":1,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`TransactionId`	Required Unique identifier as assigned by ClearBank. Type: `string` Format: `uuid`
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid`
`DebtorName`	Required The name used to identify the legal owner of the account from which to debit funds. Type: `string` Max. Length: `140` Min. Length: `1` Pattern: `[^\n]{1,140}`
`DebtorAccount`	Required International Bank Account Number associated with the debtor to which a debit entry will be made as a result of the transaction. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `[^\n]{1,35}`
`CreditorName`	Required The name used to identify the legal owner of the account from which to credit funds. Type: `string` Max. Length: `140` Min. Length: `1` Pattern: `[^\n]{1,140}`
`CreditorAccount`	Required International Bank Account Number associated with the account to which a credit entry will be posted as a result of the payment transaction. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `[^\n]{1,35}`
`InstructedAmount`	Required Instructed payment amount in euros, for example 12.51 would indicate €12.51. Type: `number` Format: `decimal`
`SchemePaymentMethod`	Required Payment scheme used to submit the transaction. This will always be INST, which indicates SCT Inst. Type: `string`
`TimestampCreated`	Required Date and time transaction was created, in UTC. Type: `string` Format: `date-time`
`TimestampSubmitted`	Required Date and time transaction was sent to scheme, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalPaymentProperties`	Optional Type: `object` `Key` Type: `null` or `string` Pattern: `[^\n]` `Value` Type: `null` or `string` Pattern: `[^\n]`
`TransactionReference`	Optional Provides contextual information about the payment. For outbound SCT Inst transactions, this will match the information supplied in the Reference field. For inbound SCT Inst transactions, this provides unstructured remittance information; structured information if unstructured is not provided; otherwise NOTPROVIDED. Type: `string` Max. Length: `143` Min. Length: `1`

Example SEPA Instant Inbound Payment Settled webhook request body

{
  "Type": "Sepa.Instant.Inbound.Payment.Settled",
  "Version": 1,
  "Payload": {
    "TransactionId": "8d3d36fe-272c-fc03-44dc-d76c950867e4",
    "PaymentId": "8d3d36fe-272c-fc03-44dc-d76c950867e4",
    "DebtorName": "Thelma Block",
    "DebtorAccount": "GB68INST20182441739477",
    "CreditorName": "Shawna Kautzer",
    "CreditorAccount": "NL37CLRB0126383492",
    "InstructedAmount": 3.35,
    "SchemePaymentMethod": "INST",
    "TimestampCreated": "2025-01-22T12:55:12.1941864Z",
    "TimestampSubmitted": "2025-01-22T12:55:12.1941864Z",
    "EndToEndId": "ec1GSkA8YCLzPYod96O7ROildNHeeHnuwgO",
    "AdditionalPaymentProperties": [
      {
        "Key": "CreditorAgentBic",
        "Value": "RZKTAT2K288"
      }
    ],
    "TransactionReference": "InvoiceReference00189900567844320"
  },
  "Nonce": 1225137631
}

Example webhook response

{
    "Nonce": 1225137631
}

You can send SCT Inst recall requests using the POST /v1/payments/sepa-instant/{paymentId}/recall endpoint. You will receive confirmation via the SEPA Instant Recall Payment Created webhook, and a response via either the SEPA Instant Recall Payment Settled or SEPA Instant Recall Request Rejected webhooks.

Recall requests remain valid for a maximum of 15 business days. If after 15 business days the receiving party has not responded, the recall request is automatically rejected and the SEPA Instant Recall Request Rejected webhook is sent.

A message flow diagram explaining a successful SCT Inst recall which results in receiving a SEPA Instant Recall Payment Settled webhook

A message flow diagram explaining a rejected SCT Inst recall which results in receiving a SEPA Instant Recall Request Rejected webhook

If the receiving party rejects the recall request, a rejection code will be provided and populated in the RejectionCode field of the SEPA Instant Recall Request Rejected webhook. The recall rejection codes include, but are not limited to:

Reason Code	Description
AC04	Closed Account Number
AM04	Insufficient Funds
ARDT	The Transaction Has Already Been Returned
ARJT	Already rejected original SCT (SEPA Credit Transfer)
CUST	Requested By Customer
LEGL	Legal Decision
NOAS	No Answer From Customer
NOOR	No Original Transaction Received
RNPR	Original credit transfer was received but is not processable
RR04	Regulatory reason

External code sets can be downloaded from iso20022.org

Recall an SCT Inst payment

post/v1/payments/sepa-instant/{paymentId}/recall

This endpoint is used to create a recall request for an outbound payment.

Parameters

paymentId string, path, Required
Authorization string, header, Required
Your API Token, obtained 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)

originalInstructedAmount number, Required
Amount of money moved between the debtor and creditor (EUR).
Minimum
0
reasonCodeForRecall string, Required
Value must be one of "DUPL, FRAD, TECH, CUST, AC03, AM09". DUPL = Duplicate, FRAD = Fraud, TECH = Technical problem, AC03 = Invalid creditor number, CUST = Requested by customer, AM09 = Wrong amount
Minimum length
1
additionalInformation string
Can only be used for "FRAD, CUST, AC03, AM09". Further details on the cancellation request reason.
Maximum length
105
originalInstructedDate string, Required
Original date of transaction.
Pattern
YYYY-MM-DD

request

{
  "originalInstructedAmount": "1000",
  "reasonCodeForRecall": "DUPL",
  "additionalInformation": "Lorem ipsum",
  "originalInstructedDate": "2024-08-23"
}

Code copied

Response (application/json)

202 Accepted
400 Bad Request
409 Conflict

Bad Request

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

Code copied

Conflict

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

Code copied

Associated Webhooks

SEPA Instant Recall Payment Created webhook
SEPA Instant Recall Payment Settled webhook
SEPA Instant Recall Payment Cancelled webhook
Customer Accounts Transaction Completed webhook

This webhook confirms an outbound or inbound SCT Inst payment related to a recall request has settled.

Request body

{
    "Type":"Sepa.Instant.RecallPayment.Settled",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`RecallTransactionId`	Required Unique identifier of the recall transaction as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`TotalReturnedAmount`	Required The amount of money returned in euros, with the direction of payment indicated by the sign. For example 12.51 would indicate €12.51 has been credited to your account and -12.51 would indicate that €12.51 has been debited from your account. Type: `number` Format: `decimal`
`TimestampSettled`	Required Date and time the recall was requested, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`

Example SEPA Instant Recall Payment Settled request body

{
  "Type": "Sepa.Instant.RecallPayment.Settled",
  "Version": 2,
  "Payload": {
    "PaymentId": "4f268644-49b1-29f7-238a-d5ee8ea014eb",
    "RecallTransactionId": "c8634f01290904468afeabb417f5ceb0",
    "OriginalTransactionId": "4f26864449b129f7238ad5ee8ea014eb",
    "TotalReturnedAmount": 3.28,
    "TimestampSettled": "2025-01-22T12:55:40.8714037Z",
    "EndToEndId": "mtsHGw83TX9DSvhHD3XDXIHHb3HSqING0T9"
  },
  "Nonce": 445427771
}

Example webhook response

{
    "Nonce": 445427771
}

This webhook confirms an outgoing SCT Inst recall request has been rejected.

Request body

{
    "Type":"Sepa.Instant.RecallRequest.Rejected",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`RejectionCode`	Required Specifies the reason for the rejection of the recall. Reject codes include, but are not limited to: AC04, AM04, ARDT, ARJT, CUST, LEGL, NOAS, NOOR, RNPR, RR04. External code sets can be downloaded from iso20022.org. Type: `string`
`TimestampRejected`	Required Date and time the recall was rejected, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalInformation`	Optional Additional information provided by the initiating party about the rejection. Type: `array` or `null` Type: `string` Pattern: `[^\n]`

Example SEPA Instant Recall Request Rejected request body

{
  "Type": "Sepa.Instant.RecallRequest.Rejected",
  "Version": 2,
  "Payload": {
    "PaymentId": "1734d2ad-9353-49d0-9abe-be7ba966a2a2",
    "OriginalTransactionId": "c496d6a7-fc9b-438b-b03c-22e4ba15d2a1",
    "RejectionCode": "AC03",
    "TimestampRejected": "2025-01-22T12:54:05.1118861Z",
    "EndToEndId": "CKDIbhOhfZVGN6YJ5KgsST9H77IbOViXhhs",
    "AdditionalInformation": [
      "Some Reason"
    ]
  },
  "Nonce": 1106159678
}

Example webhook response

{
    "Nonce": 1106159678
}

Recalls can be requested using the following reason codes:

Reason	Description	Time limit to send recall request
DUPL	Duplicate sending	10 business days
TECH	Technical problems resulting in an erroneous SCT Inst Transaction	10 business days
FRAD	Fraudulent originated SCT Inst Instruction	13 months
AC03	Wrong account number in original transfer	13 months
AM09	Wrong amount in original transfer	13 months
CUST	Requested by customer	13 months

If you receive a recall request, you will be notified via the SEPA Instant Recall Request Received webhook. You can review the details of the request by referring to the OriginalTransactionId for details of the original payment received and ReasonCode for the reason the sending party is requesting the recall (see Recall reason codes)

To respond to the recall request, use the POST /v1/payments/sepa-instant/{paymentId}/recall-response endpoint. Set the approve boolean true to accept the request or false to reject it.

Following your approval of a recall request, the amount of the original payment is ring-fenced and returned to the sending party. You can be notified of the status of the status of the return payment via the SEPA Instant Recall Payment Created webhook, SEPA Instant Recall Payment Settled webhook, and SEPA Instant Recall Payment Cancelled webhook.

Recall requests should be responded to within 15 business days. If after 15 business days you do not accept or reject the recall, ClearBank will automatically reject the request.

A message flow diagram explaining receiving a recall request, being notified via the SEPA Instant Recall Request Received webhook and responding with 'approve' set to 'false' with a valid 'rejectionCode' using the POST /v1/payments/sepa-instant/{paymentId}/recall-response endpoint

This webhook confirms an inbound SCT Inst recall request has been received.

Request body

{
    "Type":"Sepa.Instant.RecallRequest.Received",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`ReasonCode`	Required The reason code used to recall the payment. This can be DUPL, FRAD, TECH, CUST, AC03 or AM09. Type: `string` Pattern: `[^\n]`
`TimestampCreated`	Required Date and time the recall was requested, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`
`AdditionalInformation`	Optional Additional information provided by the initiating party about the recall. Type: `array` or `null` Type: `string` Pattern: `[^\n]`

Example SEPA Instant Recall Request Received request body

{
  "Type": "Sepa.Instant.RecallRequest.Received",
  "Version": 2,
  "Payload": {
    "PaymentId": "86a5fcb3-6be3-4bf9-9e8c-dab5b1c39bc4",
    "OriginalTransactionId": "aa4f5da6-15b7-45ec-abf1-c72d58041ec3",
    "ReasonCode": "AC03",
    "TimestampCreated": "2025-01-22T12:54:32.8690907Z",
    "EndToEndId": "QtXXMAu18XRVubaXBSFoLdi14e5uSMzr85p",
    "AdditionalInformation": [
      "Some Reason"
    ]
  },
  "Nonce": 1885237896
}

Example webhook response

{
    "Nonce": 1885237896
}

Respond to an SCT Inst recall request

post/v1/payments/sepa-instant/{paymentId}/recall-response

This endpoint is used to accept or reject an incoming SEPA ICT recall request.

Parameters

paymentId string, path, Required
Authorization string, header, Required
Your API Token, obtained 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)

approve boolean, Required
To accept a recall, set the value to true. To reject a recall, set the value to false. If set to false, rejectionCode is required.
rejectionCode string
Value must be one of "AC04, NOOR, AM04, ARDT, NOAS, LEGL, CUST". AC04 = Closed account, NOOR = No Original Transaction Received, AM04 = insufficient funds, ARDT = The transaction has already been returned, NOAS = No answer from customer, LEGL = Legal decision, CUST = Requested by customer. Rejection codes should only be set when rejecting the recall. In order to reject a recall, please set the the value of the Approve field to false.

request

{
  "approve": "false",
  "rejectionCode": "AM04"
}

Code copied

Response (application/json)

202 Accepted
400 Bad Request
409 Conflict

Bad Request

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

Code copied

Conflict

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

Code copied

Associated Webhooks

SEPA Instant Recall Request Received webhook
SEPA Instant Recall Payment Created webhook
SEPA Instant Recall Payment Settled webhook

This webhook confirms an inbound SCT Inst recall payment has been created.

Request body

{
    "Type":"Sepa.Instant.RecallPayment.Created",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`RecallTransactionId`	Required Unique identifier of the recall transaction as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`TotalReturnedAmount`	Required The amount of money returned in euros. For example, -12.51 would indicate that €12.51 has been debited from your account. Type: `number` Format: `decimal`
`TimestampSettled`	Required Date and time the recall was requested, in UTC. Type: `string` Format: `date-time`
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`

Example SEPA Instant Recall Payment Created webhook request body

{
  "Type": "Sepa.Instant.RecallPayment.Created",
  "Version": 2,
  "Payload": {
    "RecallTransactionId": "fcb6963b5e9d4b3b943b1551bdc9b398",
    "OriginalTransactionId": "2e4880ab-21a3-43d1-95a1-b6c5426cd6e4",
    "TotalReturnedAmount": 100,
    "TimestampCreated": "2025-01-22T12:54:39.9844016Z",
    "PaymentId": "c7c4402a-56a6-4382-a31a-0ca32099ca4f",
    "EndToEndId": "8ufIvXRF6gDpWcFnLl4GruLZLQsAGCzFa4F"
  },
  "Nonce": 2068152292
}

Example webhook response

{
    "Nonce": 2068152292
}

This webhook confirms an outbound or inbound SCT Inst payment related to a recall request has settled.

Request body

{
    "Type":"Sepa.Instant.RecallPayment.Settled",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`PaymentId`	Required Unique identifier for payment as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`RecallTransactionId`	Required Unique identifier of the recall transaction as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`TotalReturnedAmount`	Required The amount of money returned in euros, with the direction of payment indicated by the sign. For example 12.51 would indicate €12.51 has been credited to your account and -12.51 would indicate that €12.51 has been debited from your account. Type: `number` Format: `decimal`
`TimestampSettled`	Required Date and time the recall was requested, in UTC. Type: `string` Format: `date-time`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`

Example SEPA Instant Recall Payment Settled request body

{
  "Type": "Sepa.Instant.RecallPayment.Settled",
  "Version": 2,
  "Payload": {
    "PaymentId": "4f268644-49b1-29f7-238a-d5ee8ea014eb",
    "RecallTransactionId": "c8634f01290904468afeabb417f5ceb0",
    "OriginalTransactionId": "4f26864449b129f7238ad5ee8ea014eb",
    "TotalReturnedAmount": 3.28,
    "TimestampSettled": "2025-01-22T12:55:40.8714037Z",
    "EndToEndId": "mtsHGw83TX9DSvhHD3XDXIHHb3HSqING0T9"
  },
  "Nonce": 445427771
}

Example webhook response

{
    "Nonce": 445427771
}

The following diagram outlines the process following the unlikely event that there is an issue with the pacs.004 payment that is sent following your approval of an inbound recall request.

A message flow diagram explaining responding to a recall request with 'approve' followed by the pacs.004 payment being rejected at RT1 resulting in receiving a SEPA Instant Recall Payment Cancelled webhook

Following a rejected pacs.004 and receipt of the SEPA Instant Recall Payment Cancelled webhook, the ring-fence is removed from the recall amount and you must re-initiate the recall response using the POST /v1/payments/sepa-instant/{paymentId}/recall-response endpoint.

This webhook confirms an outgoing SCT Inst recall payment has been cancelled.

Request body

{
    "Type":"Sepa.Instant.RecallPayment.Cancelled",
    "Version":2,
    "Payload": {...},
    "Nonce":
}

Payload

Element	Description
`PaymentId`	Required Unique identifier for payment assigned by ClearBank. For recalls of outbound payments this will match the paymentId returned in the 202 response when you initiated the original payment. For recalls of inbound payments this will match the paymentId in the Inbound Payment Settled webhook. Type: `string` Format: `uuid`
`RecallTransactionId`	Required Unique identifier of the recall transaction as assigned by ClearBank. Type: `string` Format: `uuid` Max. Length: `36` Min. Length: `1`
`OriginalTransactionId`	Required Unique identifier of the original payment transaction, as assigned by ClearBank, to unambiguously identify the transaction. This identifier is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `36` Min. Length: `1` Pattern: `[^\n]{1,36}`
`TimestampCancelled`	Required Date and time transaction was cancelled, in UTC. Type: `string` Format: `date-time`
`CancellationCode`	Required Cancellation code. Type: `string` Pattern: `[^\n]`
`CancellationReason`	Required Reason SCT Inst recall payment was cancelled. Type: `string` Pattern: `[^\n]`
`EndToEndId`	Required Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. Type: `string` Max. Length: `35` Min. Length: `1` Pattern: `^[^\n]{1,35}$`

Example SEPA Instant Recall Payment Cancelled webhook request body

{
  "Type": "Sepa.Instant.RecallPayment.Cancelled",
  "Version": 2,
  "Payload": {
    "PaymentId": "160b3baf-1d92-1b2a-3826-b022363d865a",
    "RecallTransactionId": "7509f28206a317cfc9ca7ab71f3e8286",
    "OriginalTransactionId": "160b3baf1d921b2a3826b022363d865a",
    "TimestampCancelled": "2025-01-22T12:56:00.3080782Z",
    "CancellationCode": "CB01",
    "CancellationReason": "Unknown error",
    "EndToEndId": "6jff6aBJ1B76Zoy3rvMT5MzImos14R5WbdC"
  },
  "Nonce": 643704746
}

Example webhook response

{
     "Nonce": 643704746
}

To test the SEPA Instant Outbound Payment Delayed webhook, you can provide one of the following values in the reference field of a Send SCT Inst Payment request:

Reference field value	Simulated behavior
`--DelayPayment--`	Delays the payment by 10 seconds, then proceeds as normal - validation still applies.
`--CancelDelayedPayment--`	Delays the payment by 10 seconds, then cancels the payment with cancellation code `CB05`.

Simulate an inbound SCT Inst payment

post/v1/sepa-instant-emulator/inbound-payment

Generates an inbound SCT Inst payment for testing purposes in our simulation environment for testing purposes.

Parameters

Authorization string, header, Required
Your API Token, obtained 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)

PaymentId string, Required
Unique identification, as assigned by the original first instructing agent, to unambiguously identify the transaction.
Minimum length
1
Maximum length
35
Pattern
^[0-9a-zA-Z/\-\?:\.,'\+ ]+$
EndToEndId string, Required
Unique identification, as assigned by the originating party, to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain.
Minimum length
1
Maximum length
35
Pattern
^[0-9a-zA-Z/\-\?:\.,'\+ ]+$
Reference string
Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system
Amount number
Amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency (EUR).
Minimum
0
Maximum
100000
Debtor object, Required
UltimateDebtor object
Creditor object, Required
UltimateCreditor object

request

{
  "PaymentId": "0947eaf62b51496bafba969a0a712d12",
  "EndToEndId": "0947eaf62b51496bafba969a0a712d12",
  "Reference": "INV-00002 2020-01-21",
  "Amount": "10.00",
  "Debtor": {
    "Name": "John Doe",
    "AccountIban": "NL45INGB4887467303",
    "AgentBic": "CLRBNL2AXXX",
    "OrganisationBic": "CLRBNL2AXXX",
    "PostalAddress": {
      "StreetName": "Morissette Union",
      "BuildingNumber": "99",
      "TownName": "Sipesville",
      "PostCode": "RV7 4IS",
      "CountrySubdivision": "Buckinghamshire",
      "Country": "GB"
    }
  },
  "UltimateDebtor": {
    "Name": "John Doe",
    "OrganisationBic": "CLRBNL2AXXX"
  },
  "Creditor": {
    "Name": "John Doe",
    "AccountIban": "NL01CLRB0123456789",
    "AgentBic": "CLRBNL2AXXX",
    "OrganisationBic": "CLRBNL2AXXX",
    "PostalAddress": {
      "StreetName": "Morissette Union",
      "BuildingNumber": "99",
      "TownName": "Sipesville",
      "PostCode": "RV7 4IS",
      "CountrySubdivision": "Buckinghamshire",
      "Country": "GB"
    }
  },
  "UltimateCreditor": {
    "Name": "John Doe",
    "OrganisationBic": "CLRBNL2AXXX"
  }
}

Code copied

Response (application/json)

202 Accepted
400 Bad Request
404 Not Found

Bad Request

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "errors": {
    "property1": [
      "string"
    ],
    "property2": [
      "string"
    ]
  },
  "property1": null,
  "property2": null
}

Code copied

Not Found

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

Code copied

Associated Webhooks

SEPA Instant Inbound Payment Settled webhook

Simulate an inbound SCT Inst recall request

post/v2/sepa-instant-emulator/inbound-payment/recall

Generates an inbound SCT Inst recall request in our simulation environment for testing purposes.

Parameters

Authorization string, header, Required
Your API Token, obtained 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)

Reference string
Information supplied to enable the matching of an entry with the items that the transfer is intended to settle, such as commercial invoices in an accounts' receivable system
ReasonForRecall string, Required
The reason code used to recall the payment.
Enum array
DUPL, FRAD, TECH, CUST, AC03, AM09
Amount number, Required
Amount of money moved between the debtor and creditor (EUR).
Minimum
0
Maximum
100000
PaymentId string, Required
Original payment ID used in the inbound payment to be recalled.
Minimum length
1
Maximum length
35
Pattern
^[0-9a-zA-Z/\-\?:\.,'\+ ]+$
EndToEndId string, Required
Original endToEndId used in the inbound payment to be recalled.
Minimum length
1
Maximum length
35
Pattern
^[0-9a-zA-Z/\-\?:\.,'\+ ]+$

request

{
  "Reference": "INV-00002 2020-01-21",
  "ReasonForRecall": "DUPL",
  "Amount": "1000",
  "PaymentId": "0947eaf62b51496bafba969a0a712d12",
  "EndToEndId": "0947eaf62b51496bafba969a0a712d12"
}

Code copied

Response (application/json)

202 Accepted
400 Bad Request
404 Not Found
500 Server Error

Bad Request

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "errors": {
    "property1": [
      "string"
    ],
    "property2": [
      "string"
    ]
  },
  "property1": null,
  "property2": null
}

Code copied

Not Found

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

Code copied

Server Error

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

Code copied

Associated Webhooks

SEPA Instant Recall Request Received webhook

SEPA Instant Credit Transfer