SEPA CT Instant Frequently Asked Questions have been provided here and arranged based on various areas.

General Queries

SEPA instant payment is a new EU-wide transfer scheme introduced in November 2017. It allows customer based in the EU area to transfer money instantly (within 10 seconds) to any third party bank account in the SEPA area.

The recipient’s account will generally be credited within 1 to 2 seconds of the transfer being initiated and accepted. The maximum time permitted as per the scheme is 10 seconds.

You may send instant transfers and also receive instant transfers, using the Origix IP solution

Arkea is a participant in the SEPA instant payment scheme.

It will not be possible to send an Instant transfer. Should Instant transfers be important to your business, we would suggest you register with Sentenial/Arkea for SEPA instant payments

SEPA instant payments will cost slightly more than a traditional money transfer.

Yes, Origix IP allows you to receive money instantly into your bank account

It is possible to send money instantly to a bank account provided the destination account is with a bank that participates in the SEPA instant payment scheme.

The usefulness of the scheme is limited at present, however as more and more banks join the scheme, it will rapidly become more widely available and eventually instant will become the default transfer type.


The number of participating banks is growing each month as the transfer becomes more popular.

You need to obtain the BIC of the recipient bank and then refer to the list of participating bank BICs, published by EPC.

All EU countries may participate in the scheme, along with EEA countries.

Note: It is not currently possible to suspend a mandate via the API but this can be done via the Nuapay user interface.

At present it is not mandatory for banks to provide SEPA Instant transfers.

The scheme operates Euro transfers only. It is generally not possible to make a SEPA instant payment to non-Euro bank accounts.

Your transfer request will be rejected at the point of entry and you will be advised to make the transfer using normal transfer method.

At present the only way to create instant transfers is via the REST API. A user interface option will be provided in a later release.

At present the only way to create transfers is via the REST API. A file gateway option is planned for a later release.


Your transfer request will be rejected and you will receive a message to this effect.

Please contact ABS for information on how to transfer funds to your ABS account.

The sending of transfer notifications to recipients is an optional service that the recipient’s bank may or may not provide.

Origix IP will inform you of the outcome of the transfer. See the Webhooks section.

When Origix IP receives confirmation that the payee bank has received the funds, Origix IP will inform you via an automatic Webhook notification. You should receive the notification within 10 seconds.

A transfer may be recalled. If you wish to recall a transfer, you should contact the ABS support desk to initiate the recall. A recall is not guaranteed to be successful and may take up to 10 days to retrieve an answer from the payee’s bank.

For transfers initiated via API, 4 eyes is not recommended, as this dilutes the STP nature of the transfer.

Transfer requests must be digitally signed and encrypted using the secure credential provided by Origix IP.

An API is provided that will return the status of a transfer, together with all the transfer details - See the Retrieve Instant Payment service.

The common reasons for failure are

  • Lack of funds in the payer's account.
  • The payee’s bank is not a participant in the SEPA instant payment scheme.
  • The payee’s account is not a valid account.

You may send the transfer as a normal transfer, and the recipient will receives the money the following day

Failed Payments

Recalls operate in a similar manner to the existing SEPA credit transfer recall. Recalls are not instant.

Recall requests are sent to the CSM in an ISO20022 CAMT.056 message format, via the EBICS messaging protocol. The request will be forwarded to the beneficiary bank.

The beneficiary bank has 10 days in which to respond to the CSM.

The response from the beneficiary bank may be positive or negative. A positive response will result in the funds being returned. A pacs.004 message will be sent to the originating bank, and funds will then be credited to the customer account. In the case of a negative response, the originating bank will receive a CAMT.029 explaining why the funds cannot be returned.

There are two ways in which an Affiliates can be notified of failed transfer:

  • If the transfer fails validation on the Sentenial platform (lack of funds, or unreachable beneficiary BIC) the API response will inform the affiliate of the failed transfer, together with a reason code.
  • If the transfer fails in RT1 (timeout) or in the beneficiary bank (account not found), the affiliate will be informed via a Webhook. Affiliates may also call the Retrieve Instant Payment API to get the latest status of a transfer.


Sentenial will issue Affiliates with credentials (Certificates/PKI key pai & API key) to enable them access the SEPA Instant APIs and receive and unencrypt webhook content.

RT1 will issue certificates/PKI key pair to Sentenial. Sentenial will sign transfers with their private key before submitting transfer to RT1 via EBICS channel