Solarisbank 장애 기록

1. 2026년 8월 15일 AM 5:26 UTCinvestigating

   현재 SEPA Instant Transaction을 도입하고 들어오는 내부 거부를 관찰하고 있습니다. 문제는 우리의 서비스 제공자 중 하나에 연결됩니다. 파트너 충격/고객 충격: 나가는 SEPA 즉시 전송 -> 파트너는 영향을받은 SEPA 즉시 거래의 합의에 지연을 알 수 있습니다. 지속적인 오류 메시지의 경우, 파트너는 정상적인 SEPA 신용 전송을 대안으로 수행 할 수있는 가능성을 알려줍니다. 면책 조항: 실제 고객 영향은 Solaris SE API 서비스의 각 파트너의 구현에 따라 다를 수 있습니다. 충격적인 내구시간: POST /v1/accounts/{account id}/transaction/sepa instant credit transfers API Reference Documentation: 영향 받은 endpoint/s에 대해 더 알고 싶으신가요? SEPA 즉시 신용 전송 (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1account~1%7Baccount id%7D~1transactions~1sepa instant credit transfers/post Webhook 이벤트 (Instant SEPA 실패) : https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post 우리는 어떤 불편을 끼쳐 드려 죄송합니다. 궁금한 사항이나 우려 사항이 있으시면 [email protected]으로 이메일을 보내거나 전용 티켓 플랫폼을 통해 문의하십시오.

2. 2026년 8월 15일 AM 7:03 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 8월 15일 AM 9:43 UTCidentified

   문제는 확인되었습니다

4. 2026년 8월 15일 AM 10:38 UTCidentified

   우리는이 문제에 계속됩니다.

5. 2026년 8월 15일 AM 10:47 UTCidentified

   데이터 센터 아웃리지에 연결된 공급자 발행은 사이트에 연결됩니다. https://status.core-backbone.com/

6. 2026년 8월 15일 AM 11:09 UTCidentified

   지연된 거래에서 더 많은 거래를 방지하기 위해 SEPA Instant Transaction이 중단되었습니다. 파트너는 정상적인 SEPA 신용 전송에 변화를 알리는 것이 좋습니다.

7. 2026년 8월 15일 PM 2:34 UTCidentified

   수정은 장소에 있으며 SEPA Instant 거래 서비스는 복원되었습니다.

8. 2026년 8월 15일 PM 2:53 UTCmonitoring

   SEPA Instant 거래 서비스는 복원되었습니다. 우리는 현재 모든 들어오고 나가는 거래를 모니터링하여 전체 서비스 안정성을 보장합니다. 우리는 어떤 불편을 끼쳐 드려 죄송합니다. 궁금한 사항이나 우려 사항이 있으시면 [email protected]으로 이메일을 보내거나 전용 티켓 플랫폼을 통해 문의하십시오.

9. 2026년 8월 18일 AM 8:15 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 5일 PM 5:35 UTCmonitoring

   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일 PM 7:37 UTCresolved

   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일 PM 1:23 UTCinvestigating

   SEPA Instant 거래가 진행되고 있습니다. 문제는 우리의 공급자에 연결되고 그들은 문제점을 고치기 위하여 관여되었습니다. 파트너 충격/고객 충격: 나가는 SEPA 즉시 전송 -> 파트너는 영향을받은 SEPA 즉시 거래의 합의에 지연을 알 수 있습니다. 지속적인 오류 메시지의 경우, 파트너는 정상적인 SEPA 신용 전송을 대안으로 수행 할 수있는 가능성을 알려줍니다. 면책 조항: 실제 고객 영향은 Solaris SE API 서비스의 각 파트너의 구현에 따라 다를 수 있습니다. 충격적인 내구시간: POST /v1/accounts/{account id}/transaction/sepa instant credit transfers API Reference Documentation: 영향 받은 endpoint/s에 대해 더 알고 싶으신가요? SEPA 즉시 신용 전송 (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1account~1%7Baccount id%7D~1transactions~1sepa instant credit transfers/post Webhook 이벤트 (Instant SEPA 실패) : https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post 우리는 어떤 불편을 끼쳐 드려 죄송합니다. 궁금한 사항이나 우려 사항이 있으시면 [email protected]으로 이메일을 보내거나 전용 티켓 플랫폼을 통해 문의하십시오.

2. 2026년 7월 26일 PM 5:57 UTCresolved

   SEPA Instant 거래가 완전히 해결되었습니다. 파트너/고객 충격: Outgoing SEPA Instant Transfers : 사건 중, 파트너는 SEPA Instant Transaction에 영향을 미치는 출현 지연을 경험할 수 있습니다. 면책 조항: 실제 고객 영향은 Solaris API 서비스의 각 파트너의 특정 구현에 따라 다를 수 있습니다. 충격적인 내구시간: POST /v1/accounts/{account id}/transaction/sepa instant credit transfers API 참고 문서: 영향 받은 엔드포인트에 대해 더 알고 싶으시다면 다음의 공개 문서를 검토하십시오: SEPA 즉시 신용 전송 (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1account~1%7Baccount id%7D~1transactions~1sepa instant credit transfers/post Webhook 이벤트 (Instant SEPA 실패) : https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post 우리는 어떤 불편을 끼쳐 드려 죄송합니다. 궁금한 사항이나 우려 사항이 있으시면 [email protected]으로 이메일을 보내거나 전용 티켓 플랫폼을 통해 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 18일 PM 3:41 UTCidentified

   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일 PM 3:34 UTCmonitoring

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

3. 2026년 6월 24일 AM 9:26 UTCresolved

   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일 PM 1:47 UTCinvestigating

   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일 PM 2:59 UTCresolved

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

1. 2026년 5월 24일 PM 9:22 UTCidentified

   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일 PM 10:41 UTCresolved

   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일 AM 10:42 UTCidentified

   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일 PM 12:06 UTCidentified

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

3. 2026년 5월 19일 PM 2:06 UTCresolved

   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일 AM 8:00 UTCinvestigating

   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일 AM 8:53 UTCidentified

   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일 AM 9:01 UTCmonitoring

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

4. 2026년 5월 19일 PM 12:54 UTCresolved

   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일 PM 9:45 UTCinvestigating

   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일 AM 7:28 UTCresolved

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

1. 2026년 4월 18일 PM 8:42 UTCinvestigating

   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일 PM 10:10 UTCmonitoring

   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일 AM 8:36 UTCresolved

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

1. 2026년 4월 14일 PM 6:30 UTCinvestigating

   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일 PM 7:50 UTCinvestigating

   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일 AM 7:30 UTCmonitoring

   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일 AM 10:47 UTCresolved

   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일 PM 2:16 UTCidentified

   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일 PM 4:23 UTCresolved

   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일 PM 3:58 UTCresolved

   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일 AM 9:50 UTCmonitoring

   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일 AM 10:15 UTCresolved

   This incident has been resolved.

1. 2025년 12월 3일 PM 2:57 UTCidentified

   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일 PM 5:08 UTCresolved

   This incident has been resolved.

1. 2025년 12월 2일 AM 11:37 UTCmonitoring

   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일 PM 1:12 UTCresolved

   This incident has been resolved.

1. 2025년 11월 21일 AM 9:11 UTCresolved

   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일 PM 5:15 UTCinvestigating

   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일 PM 7:01 UTCresolved

   This incident has been resolved.

1. 2025년 11월 18일 PM 1:11 UTCinvestigating

   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일 PM 4:21 UTCresolved

   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일 AM 5:26 UTCinvestigating

   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일 AM 6:02 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 11월 17일 AM 8:38 UTCmonitoring

   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일 AM 10:47 UTCresolved

   This incident has been resolved.