Skip to content
Digital Banking
/
/
Overview
Last updated

SEPA Transfers

This section contains all the relevant information about SEPA transfers, including key concepts and the necessary endpoints and webhooks you must integrate into your solution.

What is SEPA?

The Single Euro Payments Area (SEPA) is an international transaction system created by the European Union. It aims to facilitate international bank transfers among the participating countries, making cross-border payments as easy as domestic ones.

Currently, SEPA is composed of 41 member states and territories. Banks in participating countries use a dedicated payment system that enables seamless cross-border transfers in Euros for the same cost and time as domestic transfers.

Non-SEPA Transfers (International)

If you need to receive funds from outside the SEPA zone (e.g., USA, Australia, Asia) or via the SWIFT network, refer to the International Transfers guide.

SEPA Payment Schemes

Within SEPA transfers, the European Payments Council (EPC) has created different SEPA payment schemes to fulfill the diverse needs of consumers and businesses.

Incoming SDD Only

Important constraint: Solaris currently only supports Incoming SEPA Direct Debits. This means external creditors can pull funds from Solaris accounts (if the customer signs a mandate). Solaris does not currently support Outgoing SDD (where your customers act as the creditor collecting funds from external banks).

Explore the active SEPA capabilities available on the Solaris platform:

Verification of Payee (VoP)

Account name-checking service to prevent fraud and misdirected payments.

SEPA Credit Transfer (SCT)

Standard push-based money transfers for one-off payments.

SEPA Instant Credit Transfer

Real-time transfers processed in seconds, available 24/7/365.

SEPA Instant Limits

Configure daily and per-transaction caps for Instant SEPA transfers.

Batch Transfers

Initiate and authorize up to 1,000 SEPA transfers in a single request.

Scheduled Transfers

Set up future-dated, one-off, or recurring SEPA transfers.

Incoming Direct Debit (SDD)

Allow external creditors to pull funds from your customers' accounts.

Exception Handling: Recalls and Returns

SEPA Credit Transfer (SCT) Recall

An SCT Recall occurs when a sender requests the return of a payment made from their account. This typically applies if the payment was a duplicate, technically incorrect, or made by mistake.

Process Overview:

  • Manual Process: This is a manual support process and is not handled via the Solaris API.
  • Identify the Transaction: Locate the specific transfer details (Transaction ID, Amount, Beneficiary).
  • Contact Support: Submit a recall request through Solaris Partner Care.
  • Resolution: The beneficiary bank decides whether to accept or reject the recall request.

Refer to the Solaris Partner Care (customer level processes) documentation for the full end-to-end workflow.

SEPA Returns

A SEPA Return occurs when the beneficiary bank rejects an incoming transfer because it cannot credit the funds to the recipient. Unlike a recall (initiated by the sender), a return is triggered automatically by the receiving bank.

Common Reasons for Returns:

  • Account Closed: The beneficiary account no longer exists.
  • Invalid Details: The provided IBAN or beneficiary name does not match bank records.
  • Deceased Beneficiary: The account holder has passed away, and the account is frozen.

Process Overview: When a return occurs, the beneficiary bank sends the funds back to Solaris. We then credit the original amount back to the sender's account.

Prerequisites for Sandbox Testing

Manual Top-up Required

Before testing SEPA transfers in the Sandbox environment, ensure your test account has a sufficient balance. You cannot self-fund Sandbox accounts via API. If your balance is 0, contact your Partner Manager to request a manual top-up.

Previous page
Next page