Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Historique des pannes de Solarisbank

    53 Solarisbank incidents · avril 2024 — official updates, affected components, duration and resolution details.

    Retour au statut actuel

    Arrêt – Opérations instantanées SEPA

    Début 15 août 2026 à 05:26 UTC · 3d 2h

    IssuesIncident mineur
    Composants affectés
    Digital Banking
    1. 15 août 2026 à 05:26 UTCinvestigating

      Nous observons actuellement une augmentation des rejets internes dans les transactions SEPA instantanées sortantes et entrantes. La question est liée à l'un de nos fournisseurs de services. Impact partenaire/client Impact : Pour le SEPA sortant Transferts instantanés -> Les partenaires remarqueraient un retard dans le règlement des opérations instantanées de l'EPS sortantes. En cas de messages d'erreur persistants, les partenaires sont invités à informer les clients de la possibilité d'effectuer un virement SEPA normal comme alternative Avertissement: L'impact client réel peut varier, en fonction de la mise en œuvre par chaque partenaire des services API Solaris SE. Points finals touchés: POST /v1/comptes/{account id}/transactions/sepa instant crédit transferts Documentation de référence de l'API : Pour en savoir plus sur le ou les paramètres touchés, veuillez consulter la documentation publique suivante : Transferts de crédits instantanés SEPA (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1comptes~1%7Compte id%7D~1transactions~1sepa instant credit transfers/post Webhook Events (Echec du SEPA): https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post Nous nous excusons pour les inconvénients que cette panne peut avoir causés. Pour toute question ou préoccupation, veuillez nous contacter en envoyant un e-mail à [email protected] ou via notre plateforme de billetterie dédiée.

    2. 15 août 2026 à 07:03 UTCinvestigating

      Nous continuons d'enquêter sur cette question.

    3. 15 août 2026 à 09:43 UTCidentified

      Le problème a été identifié

    4. 15 août 2026 à 10:38 UTCidentified

      Nous continuons de travailler sur cette question.

    5. 15 août 2026 à 10:47 UTCidentified

      Le problème du fournisseur lié à une panne de centre de données impactant la connectivité au site. https://status.core-backbone.com/

    6. 15 août 2026 à 11:09 UTCidentified

      Afin d'éviter que d'autres transactions ne soient retardées, les transactions instantanées SEPA ont été arrêtées. Il est conseillé aux partenaires d'informer les clients du changement à un transfert de crédit SEPA normal.

    7. 15 août 2026 à 14:34 UTCidentified

      La solution est en place, et le service de transactions instantanées SEPA sortant a été restauré.

    8. 15 août 2026 à 14:53 UTCmonitoring

      Le service de transactions instantanées SEPA entrant et sortant a été restauré. Nous surveillons actuellement toutes les transactions entrantes et sortantes afin d'assurer la stabilité du service. Nous nous excusons pour les inconvénients que cette panne peut avoir causés. Pour toute question ou préoccupation, veuillez nous contacter en envoyant un e-mail à [email protected] ou via notre plateforme de billetterie dédiée.

    9. 18 août 2026 à 08:15 UTCresolved

      Cet incident a été résolu.

    Traduit automatiquement depuis la mise à jour officielle de l'incident.

    TAUX ÉLÉVÉS D'ERREUR SUR LES ENDPOINTES DE L'API MULTIPLE

    Début 5 août 2026 à 17:35 UTC · 2h 2m

    Pending
    Composants affectés
    Digital BankingCardsIdentificationPayments
    1. 5 août 2026 à 17:35 UTCmonitoring

      Nous tenons à vous informer que nous avons expérimenté des messages d'erreur API 5XXs à retourner sur plusieurs paramètres API à nos partenaires entre 18:38 CEST - 19:12 CEST 05.08.2026. En attendant, nous surveillons le service pertinent pour nous assurer qu'il fonctionne à l'intérieur des niveaux normaux. Impact des partenaires : • Les partenaires qui ont lancé des appels aux paramètres de Solaris pendant la panne auraient connu des erreurs. Impact client : • Les clients pourraient avoir des messages d'erreur en essayant différentes actions du côté des partenaires qui dépendent des points d'arrivée Solaris. Avertissement: L'impact client réel peut varier, en fonction de la mise en œuvre par chaque partenaire des services API Solaris SE. Documentation de référence de l'API : Les partenaires/clients qui tentent d'utiliser les services associés aux paramètres auraient été présentés avec des messages d'erreur génériques ou spécifiques à la mise en œuvre du ou des paramètres par chaque partenaire. Nous partagerons plus de détails sur l'erreur après une enquête plus approfondie. Pour toute question ou préoccupation, veuillez nous contacter en envoyant un e-mail à [email protected] ou via notre plateforme de billetterie dédiée.

    2. 5 août 2026 à 19: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.

    Traduit automatiquement depuis la mise à jour officielle de l'incident.

    Sortie partielle – Transactions instantanées SEPA

    Début 26 juillet 2026 à 13:23 UTC · 4h 33m

    IssuesIncident mineur
    Composants affectés
    Digital Banking
    1. 26 juillet 2026 à 13:23 UTCinvestigating

      Nous observons actuellement une augmentation des refus dans les transactions SEPA instantanées sortantes et entrantes. Le problème est lié à notre fournisseur et ils ont été engagés pour résoudre le problème. Impact partenaire/client Impact : Pour le SEPA sortant Transferts instantanés -> Les partenaires remarqueraient un retard dans le règlement des opérations instantanées de l'EPS sortantes. En cas de messages d'erreur persistants, les partenaires sont invités à informer les clients de la possibilité d'effectuer un virement SEPA normal comme alternative Avertissement: L'impact client réel peut varier, en fonction de la mise en œuvre par chaque partenaire des services API Solaris SE. Points finals touchés: POST /v1/comptes/{account id}/transactions/sepa instant crédit transferts Documentation de référence de l'API : Pour en savoir plus sur le ou les paramètres touchés, veuillez consulter la documentation publique suivante : Transferts de crédits instantanés SEPA (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1comptes~1%7Compte id%7D~1transactions~1sepa instant credit transfers/post Webhook Events (Echec du SEPA): https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post Nous nous excusons pour les inconvénients que cette panne peut avoir causés. Pour toute question ou préoccupation, veuillez nous contacter en envoyant un e-mail à [email protected] ou via notre plateforme de billetterie dédiée.

    2. 26 juillet 2026 à 17:57 UTCresolved

      Le problème avec les transactions SEPA instantanées sortantes et entrantes a été entièrement résolu. Partenaire / Impact client : Transferts instantanés sortants SEPA : Au cours de l'incident, les partenaires ont peut-être connu des retards dans le règlement des transactions instantanées sortantes SEPA. Avertissement: L'impact client réel peut varier en fonction de l'implémentation spécifique de chaque partenaire des services API Solaris. Points finals touchés: POST /v1/comptes/{account id}/transactions/sepa instant crédit transferts Documentation de référence de l'API : Pour en savoir plus sur les paramètres touchés, veuillez consulter la documentation publique suivante : Transferts de crédits instantanés SEPA (POST): https://docs.solarisgroup.com/api-reference/digital-banking/sepa-transfers/#tag/SEPA-Instant-Credit-Transfers/paths/~1v1~1comptes~1%7Compte id%7D~1transactions~1sepa instant credit transfers/post Webhook Events (Echec du SEPA): https://docs.solarisgroup.com/api-reference/onboarding/webhooks/#tag/Webhook-events/paths/instant sepa credit transfer failed/post Nous nous excusons pour les inconvénients que cette panne peut avoir causés. Pour toute question ou préoccupation, veuillez nous contacter en envoyant un e-mail à [email protected] ou via notre plateforme de billetterie dédiée.

    Traduit automatiquement depuis la mise à jour officielle de l'incident.

    Service Disruption Notice: Physical Visa Card Production Delayed

    Début 18 juin 2026 à 15:41 UTC · 5d 17h

    Pending
    Composants affectés
    Cards
    1. 18 juin 2026 à 15: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. 19 juin 2026 à 15:34 UTCmonitoring

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

    3. 24 juin 2026 à 09: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.

    Partial Outage – SEPA Instant Transactions

    Début 9 juin 2026 à 13:47 UTC · 1h 12m

    Pending
    Composants affectés
    Digital Banking
    1. 9 juin 2026 à 13: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. 9 juin 2026 à 14:59 UTCresolved

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

    ELEVATED ERROR RATES ON MULTIPLE ACCOUNTS API ENDPOINTS

    Début 24 mai 2026 à 21:22 UTC · 1h 20m

    Pending
    Composants affectés
    Digital Banking
    1. 24 mai 2026 à 21: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. 24 mai 2026 à 22: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.

    Partial Outage – SEPA Instant Transactions

    Début 19 mai 2026 à 10:42 UTC · 3h 23m

    OutageIncident majeur
    Composants affectés
    Digital Banking
    1. 19 mai 2026 à 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. 19 mai 2026 à 12:06 UTCidentified

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

    3. 19 mai 2026 à 14:06 UTCresolved

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

    Partial Outage for Multiple Cards API Services

    Début 19 mai 2026 à 08:00 UTC · 4h 54m

    OutageIncident majeur
    Composants affectés
    Cards
    1. 19 mai 2026 à 08: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. 19 mai 2026 à 08: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. 19 mai 2026 à 09:01 UTCmonitoring

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

    4. 19 mai 2026 à 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.

    solarisbank.de | Domain Registrar Outage (.de TLD)

    Début 5 mai 2026 à 21:45 UTC · 9h 43m

    Pending
    Composants affectés
    Digital BankingCardsAuthenticationB2C BankingIdentificationLendingPaymentsOther
    1. 5 mai 2026 à 21: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. 6 mai 2026 à 07:28 UTCresolved

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

    Unplanned Partial Outage For Incoming and Outgoing SEPA Instant Transfers

    Début 18 avril 2026 à 20:42 UTC · 11h 53m

    Pending
    Composants affectés
    Digital Banking
    1. 18 avril 2026 à 20: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. 18 avril 2026 à 22: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. 19 avril 2026 à 08:36 UTCresolved

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

    Partial Outage – SEPA Instant Transactions

    Début 14 avril 2026 à 18:30 UTC · 16h 17m

    Pending
    Composants affectés
    Digital Banking
    1. 14 avril 2026 à 18: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. 14 avril 2026 à 19: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. 15 avril 2026 à 07: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. 15 avril 2026 à 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.

    Issue with Scheduled Transfers (Character Limit)

    Début 9 mars 2026 à 14:16 UTC · 2h 7m

    Pending
    Composants affectés
    Digital Banking
    1. 9 mars 2026 à 14: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. 9 mars 2026 à 16: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.

    Identification Service - IDnow Videoident SDK - Android Upgrade Required

    Début 22 décembre 2025 à 15:58 UTC · 0m

    Pending
    Composants affectés
    Identification
    1. 22 décembre 2025 à 15: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.

    Unplanned Service Disruption - Verification of payee

    Début 5 décembre 2025 à 09:50 UTC · 25m

    Pending
    Composants affectés
    Payments
    1. 5 décembre 2025 à 09: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. 5 décembre 2025 à 10:15 UTCresolved

      This incident has been resolved.

    Unplanned IDNOW Partial Outage - Identity Service

    Début 3 décembre 2025 à 14:57 UTC · 2h 10m

    Pending
    Composants affectés
    Identification
    1. 3 décembre 2025 à 14: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. 3 décembre 2025 à 17:08 UTCresolved

      This incident has been resolved.

    Unplanned Outage for Card Transaction Services

    Début 2 décembre 2025 à 11:37 UTC · 1h 35m

    Pending
    Composants affectés
    Cards
    1. 2 décembre 2025 à 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. 2 décembre 2025 à 13:12 UTCresolved

      This incident has been resolved.

    Service Disruption in SANDBOX Environment

    Début 21 novembre 2025 à 09:11 UTC · 0m

    Pending
    Composants affectés
    Digital BankingB2C BankingIdentificationPaymentsOther
    1. 21 novembre 2025 à 09: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.

    Intermittent Errors for Outgoing SEPA Instant Transactions

    Début 19 novembre 2025 à 17:15 UTC · 1h 46m

    Pending
    Composants affectés
    Digital BankingOther
    1. 19 novembre 2025 à 17: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. 19 novembre 2025 à 19:01 UTCresolved

      This incident has been resolved.

    BKYC Provider Services Outage

    Début 18 novembre 2025 à 13:11 UTC · 3h 11m

    Pending
    Composants affectés
    Identification
    1. 18 novembre 2025 à 13: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. 18 novembre 2025 à 16: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.

    BKYC Provider Services Outage

    Début 17 novembre 2025 à 05:26 UTC · 5h 21m

    Pending
    Composants affectés
    Identification
    1. 17 novembre 2025 à 05: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. 17 novembre 2025 à 06:02 UTCinvestigating

      We are continuing to investigate this issue.

    3. 17 novembre 2025 à 08: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. 17 novembre 2025 à 10:47 UTCresolved

      This incident has been resolved.