Solarisbank 中断历史

1. 2026年8月15日 UTC 05:26investigating

   我们目前注意到,在往来的SEPA即时交易中,内部拒收的情况有所增加。 这个问题与我们的一个服务提供者有关。 合作伙伴影响/客户影响: 为离开的SEPA 即时转让 - > 合作伙伴将注意到受影响的SEPA即时交易的结算出现延误 如果长期出现错误信息,建议合作伙伴告知客户,作为替代办法,可以进行正常的SEPA信贷转账。 免责声明:客户的实际影响可能有所不同,这取决于每个合作伙伴实施Solaris SE API服务的情况. 已受影响的终点 : POST /v1/ 账户/{账户 id}/ 交易/sepa instant credit ters API 参考文献:欲进一步了解受影响的终点/s,请阅读以下公共文献: SEPA 即时信用转账(POST):https://docs.solarisgroup.com/api-reference/dignal-banking/sepa-ters/#tag/SEPA-即时信用转账(SEPA-Instant-Credit-ters/paths/~1v1~1counts~1%7Baccount id%7D~1 transactionactions~1sepa instant credit ters/post Webhook Eventures (Instant SEPA 失败): https://docs.solarisgroup.com/api- reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit trant failed/post 互联网档案馆的存檔,存档日期2013-12-02. 我们为这次停电可能造成的不便道歉。 如有问题或问题,请联系我们,在@solarisgroup.com发送电子邮件,或通过我们的专用售票平台.

2. 2026年8月15日 UTC 07:03investigating

   我们正在继续调查这一问题.

3. 2026年8月15日 UTC 09:43identified

   问题已经确定

4. 2026年8月15日 UTC 10:38identified

   我们正在继续就这一问题开展工作.

5. 2026年8月15日 UTC 10:47identified

   供应商问题与数据中心断电影响网站的连接。 https://status.core-backbone.com/ 页面存档备份,存于互联网档案馆

6. 2026年8月15日 UTC 11:09identified

   为了防止任何进一步交易被拖延,已停止了SEPA即时交易。 建议合作伙伴向客户通报改为正常的SEPA信贷转账.

7. 2026年8月15日 UTC 14:34identified

   固定到位,已恢复了即将离任的SPA即时交易服务.

8. 2026年8月15日 UTC 14:53monitoring

   进出SEPA即时交易服务已经恢复。 我们目前正在监测所有进出交易,以确保全面服务稳定。 我们为这次停电可能造成的不便道歉。 如有问题或问题,请联系我们,在@solarisgroup.com发送电子邮件,或通过我们的专用售票平台.

9. 2026年8月18日 UTC 08:15resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月5日 UTC 17:35monitoring

   We would like to inform you that we have experienced 5XXs API error messages to be returned on multiple API endpoints to our Partners between 18:38 CEST - 19:12 CEST 05.08.2026. In the mean time we are monitoring relevant service to ensure that it's operating within normal levels. Partner Impact: • Partners who initiated calls to Solaris endpoints during outage time would have experienced errors. Customer Impact: • Customers might experienced error messages while attempting different actions on partners side which dependancy on Solaris end-points. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2026年8月5日 UTC 19:37resolved

   The issue was fully resolved. We would like to inform you that we have experienced 5XXs API error messages to be returned on multiple API endpoints to our Partners between 18:38 CEST - 19:12 CEST 05.08.2026. In the mean time we are monitoring relevant service to ensure that it's operating within normal levels. Partner Impact: • Partners who initiated calls to Solaris endpoints during outage time would have experienced errors. Customer Impact: • Customers might experienced error messages while attempting different actions on partners side which dependancy on Solaris end-points. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

1. 2026年7月26日 UTC 13:23investigating

   目前,我们发现,在往来的SEPA即时交易中,拒收额有所增加。 这个问题与我们的提供方有关,他们一直致力于解决这个问题。 合作伙伴影响/客户影响: 为离开的SEPA 即时转让 - > 合作伙伴将注意到受影响的SEPA即时交易的结算出现延误 如果长期出现错误信息,建议合作伙伴告知客户,作为替代办法,可以进行正常的SEPA信贷转账。 免责声明:客户的实际影响可能有所不同,这取决于每个合作伙伴实施Solaris SE API服务的情况. 已受影响的终点 : POST /v1/ 账户/{账户 id}/ 交易/sepa instant credit ters API 参考文献:欲进一步了解受影响的终点/s,请阅读以下公共文献: SEPA 即时信用转账(POST):https://docs.solarisgroup.com/api-reference/dignal-banking/sepa-ters/#tag/SEPA-即时信用转账(SEPA-Instant-Credit-ters/paths/~1v1~1counts~1%7Baccount id%7D~1 transactionactions~1sepa instant credit ters/post Webhook Eventures (Instant SEPA 失败): https://docs.solarisgroup.com/api- reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit trant failed/post 互联网档案馆的存檔,存档日期2013-12-02. 我们为这次停电可能造成的不便道歉。 如有问题或问题,请联系我们,在@solarisgroup.com发送电子邮件,或通过我们的专用售票平台.

2. 2026年7月26日 UTC 17:57resolved

   即将离任和即将到来的SEPA即时交易问题已完全解决。 合伙人/客户影响: SEPA即时转账:在该事件中,合作伙伴在结算受影响的SEPA即时交易时可能遇到延误。 免责声明:客户的实际影响可能因每个合伙人具体实施Solaris API服务而异. 已受影响的终点 : POST /v1/ 账户/{账户 id}/ 交易/sepa instant credit ters API 参考文档 : 为进一步了解受影响的终点,请审查下列公开文件: SEPA 即时信用转账(POST):https://docs.solarisgroup.com/api-reference/dignal-banking/sepa-ters/#tag/SEPA-即时信用转账(SEPA-Instant-Credit-ters/paths/~1v1~1counts~1%7Baccount id%7D~1 transactionactions~1sepa instant credit ters/post Webhook Eventures (Instant SEPA 失败): https://docs.solarisgroup.com/api- reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit trant failed/post 互联网档案馆的存檔,存档日期2013-12-02. 我们为这次停电可能造成的不便道歉。 如有问题或问题,请联系我们,在@solarisgroup.com发送电子邮件,或通过我们的专用售票平台.

自动翻译自官方事件更新。

1. 2026年6月18日 UTC 15:41identified

   Dear Partners, We are experiencing a delay in card delivery. Partner & Customer Impact: • Customers might experience 2-3 days delays with physical Visa cards deliveries. Impacted Services: • Physical Visa Card Production Disclaimer: Actual customer impact experience may vary, depending on each Partner's implementation of Solaris API services. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2026年6月19日 UTC 15:34monitoring

   A fix has been implemented and we are monitoring the results.

3. 2026年6月24日 UTC 09:26resolved

   All impact phyiscal cards were produced and shipped to couriers. We apologize for any inconveniences this delay 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.

1. 2026年6月9日 UTC 13:47investigating

   We are currently observing an decraese in outgoing & incoming SEPA Instant transactions clearance rates since ~ 15:34 CEST. There is no technical issue detected on Solaris side yet it's suspected issue is related to external source. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would observe increase in declined for outgoing SEPA instant transactions with code AB08. Indicating offline creditors banks. For Incoming SEPA Instant transfers -> Partners would notice decrease in volume of incoming SEPA Instant transactions. In case of persistent error messages, Partners are advised to inform Customers of possibility of performing the usual SEPA Credit Transfer as an alternative. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. Relevant Doc: Webhook Events (Instant SEPA Failed): 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. 2026年6月9日 UTC 14:59resolved

   The issue impacting incoming and outgoing SEPA Instant transactions has been fully resolved, and services are operating at normal levels.

1. 2026年5月24日 UTC 21:22identified

   We are experiencing 5XXs API error messages to be returned on multiple API endpoints to our Partners starting 23:00 CEST. The issue has been mitigated as of 23:17 CEST. Partner Impact: • Partners/Customers attempting to process transactions would have experienced delays 5XXs errors while calling the below API Endpoints: • GET /v1/persons/{person_id)/accounts/{account_id} • GET /v1/accounts/{account_id)/balance • GET /v1/persons/{person_id)/accounts Customer Impact: Customers might experienced error messages while attempting to retrieve transaction information and while fetching account balance Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. API Reference Documentation: Partners/Customers attempting to use the services associated to the endpoints would have been presented with either generic error messages or specific to each Partner's implementation of the endpoint/s. We will share more details on the error after further investigation is performed. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2026年5月24日 UTC 22:41resolved

   The incident identified to be impacting multiple API endpoints intermittently between 23:00 CEST and 23:17 CEST on 24.05.2026, resulting in elevated API error rates has been resolved. Services have been monitored in order to ensure that all operations are running within normal service levels. Partner/Customer Impact Resolution: 5XX API error messages are no longer returned from multiple API endpoints across all services and customers will no longer receive error messages in the partner mobile or web applications. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. The incident has been resolved. No further updates would be provided 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.

1. 2026年5月19日 UTC 10:42identified

   We are currently observing an increase in outgoing rejected and decrease incoming SEPA Instant transactions volumes; Issues started since ~ 10:30 CEST. There is no technical issue detected on Solaris side yet it's suspected issue is related to external source. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice increase in declined for outgoing SEPA instant transactions with code AB08. Indicating offline creditors banks. For Incoming SEPA Instant tranfer -> Parnters would notice decrease in volume of incoming 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. Relevant Doc: Webhook Events (Instant SEPA Failed): 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. 2026年5月19日 UTC 12:06identified

   A number of other banks encountering delays in processing SEPA instants Payements, and we are closely monitoring this issue.

3. 2026年5月19日 UTC 14:06resolved

   The rejections involve participants Banks connected to RT1. We would like to confirm that, following monitoring, the outage has been resolved.

1. 2026年5月19日 UTC 08:00investigating

   A partial outage for Multiple Cards services have been identified for creating Cards and associated Card Lifecycle Status changes. Partner Impact: • POST /v1/cards/{id}/virtual_card_requests is returning increased 5xx errors • POST /v1/cards/{card_id}/block returning increased 5xx errors • POST /v1/cards/{card_id}/unblock returning increased 5xx errors (not an exhaustive list) Customer Impact: • Customers attempting to perform card lifecycle operations or obtaining card CVC details may be presented with a generic error message intermittently, in the mobile or web applications • Customers attempting to create cards will be presented with 5XXs errors • Customers will be unable to Block and Unblock cards Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solaris SE API services. Impacted endpoints: • POST /v1/cards/{id}/virtual_card_requests • POST /v1/cards/{card_id}/block • POST /v1/cards/{card_id}/unblock (not an exhaustive list) API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards/#tag/Cards-servicing/paths/~1v1~1cards~1{id}~1virtual_card_requests/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. 2026年5月19日 UTC 08:53identified

   A partial outage for Multiple Cards services have been identified for creating cards and associated card lifecycle status changes related to cards processing provider. Partner Impact: Anticipated failures related to all cards creation & servicing end-points. Customer Impact: Anticipated failures related to all cards servcing operations. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards 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.

3. 2026年5月19日 UTC 09:01monitoring

   All affected cards services should be fully recovered and operational within normal levels by 10:20 CEST.

4. 2026年5月19日 UTC 12:54resolved

   We would like to confirm that, following extensive monitoring, the outage has been fully resolved. A partial outage for Multiple cards services have been identified for creating cards and associated card lifecycle status changes related to cards processing provider. Partner Impact: Anticipated failures related to all cards creation & servicing end-points. Customer Impact: Anticipated failures related to all cards servcing operations. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/digital-banking/cards 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.

1. 2026年5月5日 UTC 21:45investigating

   Due to an active outage on the Top Level Domain (.de) provider Denic, it is anticipated that partners may experience service disruption related to the reachability of Solaris API endpoints in the production environment (api.solarisbank.de). We will keep you informed as we continue to monitor the provider updates. API Reference Documentation: To understand more about the impacted endpoints please read the following public documentation: • https://docs.solarisgroup.com/api-reference/ 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. 2026年5月6日 UTC 07:28resolved

   We are pleased to confirm that provider issue was resolved by 12:20; Service operating within normal levels.

1. 2026年4月18日 UTC 20:42investigating

   We encountered an ongoing issue with Incoming & Outgoing SEPA Instant transactions, resulting in unsuccessful transactions. Partner / Customer Impact: Incoming & Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted Incoming & Outgoing SEPA Instant transactions. Alternative Actions: In the event of lingering external error messages, Partners are advised to inform customers of the possibility of initiating a standard 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 inconvenience this outage may have caused. Should you have any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

2. 2026年4月18日 UTC 22:10monitoring

   The issue impacting Incoming & Outgoing SEPA Instant transactions has been mitigated. Service stability has returned to normal levels, and our engineering team is monitoring the system closely to ensure continued performance. Partner / Customer Impact: Incoming & Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted Incoming & Outgoing SEPA Instant transactions. 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 inconvenience this outage may have caused. Should you have any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

3. 2026年4月19日 UTC 08:36resolved

   The issue impacting Incoming & Outgoing SEPA Instant transactions was fully resolved at 05:34 CEST, 19/04/2026 .

1. 2026年4月14日 UTC 18:30investigating

   We are currently observing an increase in outgoing rejected SEPA Instant transactions; issues started since 18:00 CEST. We are investigating the issue and focusing on service recovery. 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: SEPA Instant Credit Transfers (POST): 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 Webhook Events (Instant SEPA Failed): 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. 2026年4月14日 UTC 19:50investigating

   We are still observing a limited number of rejected outgoing SEPA Instant transactions. This affected transactions are being rejected by the scheme for some banks. We continue to monitor the situation closely and will provide further updates as soon as more information becomes available. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant transactions before being rejected. 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: SEPA Instant Credit Transfers (POST): 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 Webhook Events (Instant SEPA Failed): 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 cause. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

3. 2026年4月15日 UTC 07:30monitoring

   We continue to monitor the situation closely and will provide further updates as soon as more information becomes available. Partner Impact/Customer Impact: For Outgoing SEPA Instant transfers -> Partners would notice a delay in the settlement of the impacted Outgoing SEPA instant transactions before being rejected. 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: SEPA Instant Credit Transfers (POST): 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 Webhook Events (Instant SEPA Failed): 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 cause. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

4. 2026年4月15日 UTC 10:47resolved

   The issue with outgoing SEPA Instant transactions was fully resolved at 22:30 CET on 14/04/2026. Solaris can confirm that its internal systems and relevant providers remained fully operational. The transaction rejections were attributed to an operational malfunction in the external scheme of correspondent banks. Partner / Customer Impact: Outgoing SEPA Instant Transfers: During the incident, Partners may have experienced delays in the settlement of impacted outgoing SEPA Instant transactions before they were rejected by the scheme. Alternative Actions: In the event of any lingering external error messages, Partners are advised to inform customers of the possibility of initiating a standard SEPA Credit Transfer as an alternative. Disclaimer: Actual customer impact may vary depending on each Partner's specific implementation of Solaris API services. Impacted Endpoints: POST /v1/accounts/{account_id}/transactions/sepa_instant_credit_transfers API Reference Documentation: To understand more about the impacted endpoints, please review the following public documentation: SEPA Instant Credit Transfers (POST): 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 Webhook Events (Instant SEPA Failed): 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.

1. 2026年3月9日 UTC 14:16identified

   Issue Summary: We have identified an issue affecting Scheduled Transfers initiated with the debtor name exceeding the character limit supported by the underlying service. The failures are specifically related to debtor names exceeding the 70-character limit supported by the SEPA scheme. Resolution & Action Required: Customer Impact: Affected customers might notice that Standing orders weren't executed on time and to ensure successful processing, partners and customers are advised to manually re-submit or retry any affected transactions associated with unexecuted scheduled orders. Partner Impact - This issue specifically affects transactions involving sole proprietors or businesses with extended legal names (over 70 characters). By identifying this as a SEPA scheme limitation, partners can verify that customers with standard name lengths remain unaffected. Legacy endpoints are not impacted by this issue. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer#api-reference-documentation API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2026年3月9日 UTC 16:23resolved

   We have successfully deployed a fix to resolve the issues affecting Scheduled Transfers initiated with the debtor name exceeding the character limit supported by the underlying service.The failures were specifically related to debtor names exceeding the 70-character limit supported by the SEPA scheme. Resolution & Action Required: Customer Impact: Affected customers might notice that Standing orders weren't executed on time and to ensure successful processing, partners and customers are advised to manually re-submit or retry any affected transactions associated with unexecuted scheduled orders. Partner Impact - This issue specifically affects transactions involving sole proprietors or businesses with extended legal names (over 70 characters). By identifying this as a SEPA scheme limitation, partners can verify that customers with standard name lengths remain unaffected. Legacy endpoints are not impacted by this issue. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted endpoints: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer#api-reference-documentation API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/guides/digital-banking/sepa-transfers/scheduled-transfer In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

1. 2025年12月22日 UTC 15:58resolved

   We would like to inform you of a recent issue affecting the VideoIdent flow via our service provider IDnow . This is not a service outage but requires a partner action to ensure optimal user experience. Our service provider, IDnow, has notified us of an issue regarding their Android SDK that causes reduced image quality, specifically a green tinge, on certain Android versions and devices. To address this, IDnow has released a fix for the issue and updated the VideoIdent app in the Google Play Store. Partner Action Required : It is strongly recommended that all partners using the Android SDK update to the latest version to ensure image clarity. https://github.com/idnow/de.idnow.android/releases End users connecting to these services via the standalone app must also ensure they are using the latest version of the VideoIdent app from the Google Play Store. Impact : End users on certain Android devices may experience degraded image quality (green tint) during the VideoIdent process. This may impact the visual verification steps required for a successful identification. Disclaimer: -This issue specifically affects the Android SDK on certain device configurations. -The iOS SDK is not affected. -VideoIdent and eSign Web flows are not affected. -AutoIdent and all other products from our service provider remain unaffected. If you have any questions or require support, please contact us at [email protected] or through our dedicated ticketing platform.

1. 2025年12月5日 UTC 09:50monitoring

   Due to an unplanned outage for one of our service providers, Solaris experienced increase response "VERIFICATION_NOT_POSSIBLE" of verification of Payee for Normal SEPA / SEPA instant transactions between 09:50 CET and 10:13 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: • There was no direct impact or errors encountered during incident time however customers received response during above mentioned times that verification isn't possible yet customers were still able to confirm transactions and proceed with transfers. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. Impacted Endpoints: • POST/v1/verifications_of_payee 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/verification-of-payee/paths/~1v1~1verifications_of_payee/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. 2025年12月5日 UTC 10:15resolved

   This incident has been resolved.

1. 2025年12月3日 UTC 14:57identified

   An unplanned partial outage affecting person identification via IDnow services has been identified. We are working together with our vendor to restore the impacted services as soon as possible. Partner Impact: • IDnow identification attempts remain stuck in ‘Pending’ state as observed in WebUI and API Customer Impact: • Customers initiating new IDnow identifications may experience delays or interruptions in completing the process. API Reference Documentation: To understand more about the impacted services, please read the following public documentation: • https://docs.solarisgroup.com/guides/kyc/videoident/#video-identification-via-idnow We apologize for any inconvenience this outage may have caused. In case of any questions or concerns, please contact us by sending an email to [email protected] or through our dedicated ticketing platform.

2. 2025年12月3日 UTC 17:08resolved

   This incident has been resolved.

1. 2025年12月2日 UTC 11:37monitoring

   Summary: We identified an issue earlier today that caused all card transactions to fail between 11:07 CET - 11:58 CET. The service is restored within normal levels, and card transactions are processing normally. Our team is continuing to investigate the root cause to prevent similar issues in the future. All services are functioning normally. No further impact is expected. • Partner & Customer Impact: Partners may receive reports of issues related to failed Card Transactions Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. 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/cards/card-transactions In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2025年12月2日 UTC 13:12resolved

   This incident has been resolved.

1. 2025年11月21日 UTC 09:11resolved

   The unplanned service disruption affecting our Sandbox environment has been resolved. The systems and services are currently stable and the impact is no longer visible. Our engineering teams have corrected the infrastructure configuration issue and verified that all services are operating normally. Partner Impact/Customer Impact: • During the incident, Partners experienced a high rate of 5xx server errors and connection failures when accessing the Sandbox API. • Testing capabilities for Sandbox API services were temporarily blocked or experienced significant instability. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank Sandbox API services. We apologize for any inconveniences this outage may have caused to your testing and development activities. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

1. 2025年11月19日 UTC 17:15investigating

   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. 2025年11月19日 UTC 19:01resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 13:11investigating

   We would like to inform you about an outage related to one of our a third-party providers due to the dependency on the provider. The following services which linked to business KYC service are affected. Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2025年11月18日 UTC 16:21resolved

   A fix has been implemented by provider for an outage related to one of our a third-party providers due to the dependency on the provider. The following services which linked to business KYC service are affected. Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

1. 2025年11月17日 UTC 05:26investigating

   We would like to inform you about an outage related to one of our a third-party providers due to the dependency on the provider. The following services which linked to business KYC service are affected. Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

2. 2025年11月17日 UTC 06:02investigating

   We are continuing to investigate this issue.

3. 2025年11月17日 UTC 08:38monitoring

   A fix has been implemented by provider and we are monitoring the results Expected Partner Impact: API calls for the following commercial registrations endpoints are expected to face failure and return 5xx error messages • GET /v1/commercial_registrations/search_by_name • GET /v1/commercial_registrations/find Expected Customer Impact: There may be minor delays in the business onboarding process. Our BKYC specialists might need to manually retrieve business information from the government’s commercial register during this time. Disclaimer: Actual customer impact may vary, depending on each Partner's implementation of Solarisbank API services. API Reference Documentation: To understand more about the impacted endpoint/s please read the following public documentation: • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1find/get • https://docs.solarisgroup.com/api-reference/onboarding/businesses/#tag/Business-Registrations/paths/~1v1~1commercial_registrations~1search_by_name/get We apologize for any inconveniences this planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solarisbank. In case of any questions or concerns, please contact us by sending an email at [email protected] or through our dedicated ticketing platform.

4. 2025年11月17日 UTC 10:47resolved

   This incident has been resolved.