Service Disruption Notice: Physical Visa Card Production Delayed
A fix has been implemented and we are monitoring the results.
Home
/
Status
/
Service
Embedded-Finance-Plattform für individuelle Banking-Produkte.
Source
auto
Category
Payments
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 15m ago
8
Components
0
Active incidents
1
Maintenance
12.5%
90d uptime
Service Disruption Notice: Physical Visa Card Production Delayed
Jun 18, 3:41 PM
Normalized official status-page data for incidents, maintenance, components, and history.
12.5%
Known uptime
16 known history days
8
Components tracked
0 outage, 0 degraded
51
Incidents indexed
0 active right now
50
Maintenance windows
1 active or scheduled
Components with the most recent status-page events.
Cards
Operational
Digital Banking
Operational
Other
Operational
Authentication
Operational
B2C Banking
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
2
operational days
0
degraded days
7
outage days
7
maintenance days
74
unknown days
Latest outages and degradations detected from the official status page.
A fix has been implemented and we are monitoring the results.
The issue impacting incoming and outgoing SEPA Instant transactions has been fully resolved, and services are operating at normal levels.
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 incidents@solarisgroup.com or through our dedicated ticketing platform.
The rejections involve participants Banks connected to RT1. We would like to confirm that, following monitoring, the outage has been resolved.
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 incidents@solarisbank.de or through our dedicated ticketing platform.
We are pleased to confirm that provider issue was resolved by 12:20; Service operating within normal levels.
The issue impacting Incoming & Outgoing SEPA Instant transactions was fully resolved at 05:34 CEST, 19/04/2026 .
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 incidents@solarisbank.de or through our dedicated ticketing platform.
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 incidents@solarisgroup.com or through our dedicated ticketing platform.
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 incidents@solarisgroup.com or through our dedicated ticketing platform.
Scheduled and completed maintenance windows are separated from incidents.
A Planned Maintenance for Solaris API Services has been scheduled on 28th of June 2026 between 22:00 - 23:59 CET. The maintenance will be performed on Production environments in order to apply infrastructure changes that will improve the efficiency of our services. Expected Partner Impact: • All Solaris API services will experience a downtime between 2-5 minutes and degraded performance (high response times or intermittent 5xx errors) between 10-15 minutes during the maintenance window. Expected Customer Impact: • Customers trying to initiate new processes based on our API services (ex: new Onboardings, Authorizations, etc.) may be presented with a generic error message or experience slowness in the associated mobile or Web applications 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 planned maintenance may cause. Regular scheduled maintenance activities are required in order to maintain a high standard for the quality of services offered by Solaris. In case of any questions or concerns, please contact us by sending an email at incidents@solarisbank.de or through our dedicated ticketing platform.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Solarisbank status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.solarisgroup.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 8 of 8 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Authentication Displays the health of our Authentication product | Operational | Component | Not recorded |
B2C Banking | Operational | Component | Not recorded |
Cards Displays the health of our Cards product | Operational | Component | 6/19/2026 |
Digital Banking Displays the health of our Digital Banking product | Operational | Component | 6/20/2026 |
Identification Displays the health of our Identity products. | Operational | Component | Not recorded |
Lending Displays the health of our Lending product | Operational | Component | Not recorded |
Payments Displays the health of our Payments product | Operational | Component | Not recorded |
Other Displays the health of any other product / service affected. | Operational | Component | 6/20/2026 |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Solarisbank is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.