Skip to content
Last updated

Developer Help Center

Follow these triage steps to resolve integration issues quickly.

System status

Before debugging your code, verify if the Solaris platform is operating normally.

View System Status Page ↗

Tip

Subscribe to updates on the Status Page to receive immediate notifications about maintenance windows or incidents.

Environments

Ensure your configuration matches the correct environment URLs.

EnvironmentBase API URLAuthentication URL
Sandboxhttps://api.solaris-sandbox.dehttps://auth.solaris-sandbox.de
Productionhttps://api.solarisbank.dehttps://auth.solarisbank.de
How to top up Sandbox accounts

Solaris does not provide a public simulation endpoint to trigger inbound payments or top up account balances programmatically.

To fund your Sandbox accounts, contact your Partner Manager. They will assist you with the necessary manual steps.

Troubleshooting

Common HTTP error codes and their solutions.

401 Unauthorized
Authentication failed.
  • IP Allowlist: The firewall may block your request. Ensure your Production IP addresses are allowlisted by the Onboarding Team.
  • Wrong Environment: Check the table above. Ensure you are not using a Sandbox token on the Production URL.
  • Token Expiry: Bearer tokens are valid for 1 hour. Ensure your system refreshes the token automatically.
403 Forbidden
Access denied.
  • Missing Permission: Your Partner account lacks the specific role or permission to access this endpoint.
  • Action: Contact your Partner Manager to request access.
429 Too Many Requests
Rate limit exceeded.
  • Concurrency Limit: You are allowed a maximum of 255 concurrent API calls. Exceeding this will block new requests.
  • SMS Limit: You are limited to 60 SMS messages per recipient per hour.
Timeouts (Idle Connections)
Connection dropped.
  • Idle Timeout: The API drops connections that are idle for more than 150 seconds.
  • Action: If you receive a timeout, verify if the action was completed on the Solaris side before retrying to avoid duplicate transactions.
Webhook Failures
Notification delivery failed.
  • Timeout: Your endpoint must respond with a 200-299 status code. Solaris treats any other response code as a failure and retries the notification.
  • Retries: We use exponential backoff. If your system is down, we retry delivery for up to 7 days.

Contact support

Select the correct channel based on your integration stage.

Integration Phase

Contact: The Onboarding Team. When: You are integrating Solaris products or testing in Sandbox.

Live Operations

Contact: The Incident Management Team. When: You are live in Production and experiencing a critical bug, outage, or payment failure.

Commercial Requests

For new feature requests or commercial topics (e.g., resolving 403 Forbidden errors), contact your Partner Manager.

Technical issue template

Include these details in your ticket to speed up resolution.

1. Environment: (Sandbox / Production)
2. Affected Endpoint: (e.g., POST /v1/persons)
3. Error ID: (The "id" field found inside the JSON error response body)
4. Timestamp (UTC): YYYY-MM-DD HH:MM
5. Error Message: (Copy the full JSON error body)
6. Description: (Briefly describe what you expected vs. what happened)

Report fraud

If you suspect a fraudulent transaction or a compromised account, do not email Support.

Report Fraud Immediately ↗

Security and compliance

Official documentation for due diligence and legal verification.

Banking Licenses

View our CRR licenses and regulatory status.

Security Standards

Information Security & Data Protection policies.

Whistleblowing

Report a compliance concern anonymously.