Solaris incident

Intermittent Errors for Outgoing SEPA Instant Transactions

Notice Resolved View vendor source →

Solaris experienced a notice incident on November 19, 2025 affecting Digital Banking and Other, lasting 1h 45m. The incident has been resolved; the full update timeline is below.

Started
Nov 19, 2025, 05:15 PM UTC
Resolved
Nov 19, 2025, 07:01 PM UTC
Duration
1h 45m
Detected by Pingoru
Nov 19, 2025, 05:15 PM UTC

Affected components

Digital BankingOther

Update timeline

  1. investigating Nov 19, 2025, 05:15 PM UTC

    Due to an unplanned partial outage at our service provider, a short latency spike has impacted a limited number of outgoing SEPA Instant transactions between 16:50 CET and 17:20 CET. The systems and services are currently stable and the impact is no longer visible, however we are working together with our Instant Payment provider and are closely monitoring the situation. Partner Impact/Customer Impact: • For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant transactions • In case of persistent error messages, Partners are advised to inform Customers of possibility of doing a normal SEPA Credit Transfer as an alternative Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted Endpoints: • POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1accounts~1%7Baccount_id%7D~1transactions~1sepa_instant_credit_transfers/post • https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant_sepa_credit_transfer_failed/post We apologize for any inconveniences this outage may have caused. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

  2. resolved Nov 19, 2025, 07:01 PM UTC

    This incident has been resolved.