SEPA Transfers

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

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 a European Union (EU) initiative launched in 2008 that aims to facilitate international bank transfers among the participating countries. SEPA is composed of 36 countries: the 27 EU member states, the United Kingdom, Iceland, Norway, Liechtenstein, Switzerland, Monaco, and San Marino.

Banks in the participating countries use a dedicated payment system that enables seamless cross-border transfers within SEPA in Euros for the same cost and time as domestic transfers.

Prerequisites for Testing

Before testing SEPA transfers in the Sandbox environment, ensure your test account has a sufficient balance.

Note: You cannot self-fund Sandbox accounts via API. If your balance is 0, contact your Partner Manager to request a manual top-up.

Types of SEPA payment schemes

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

• SEPA Direct Debit (SDD), including:
  • SEPA Direct Debit Core
  • SEPA Direct Debit B2B
• SEPA Credit Transfer (SCT)
• SEPA Instant Credit Transfer

Select the links to learn more about how Solaris has implemented each scheme.

SEPA Credit Transfer (SCT) Recall

An SCT Recall occurs when a user 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 This is a manual support process and is not handled via the Solaris API.

To initiate a recall:

1. Identify the Transaction: Locate the specific transfer details (Transaction ID, Amount, Beneficiary).
2. Contact Support: Submit a recall request through Solaris Partner Care.
3. 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 and the specific details required to open a request.

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, which is 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.