Developer Help Center- Copy for LLMCopy page as Markdown for LLMs
- View as Markdown
Open this page as Markdown - Open in ChatGPTGet insights from ChatGPT
- Open in ClaudeGet insights from Claude
- Connect to CursorInstall MCP server on Cursor
- Connect to VS CodeInstall MCP server on VS Code
- Copy for LLMCopy page as Markdown for LLMs
- View as MarkdownOpen this page as Markdown
- Open in ChatGPTGet insights from ChatGPT
- Open in ClaudeGet insights from Claude
- Connect to CursorInstall MCP server on Cursor
- Connect to VS CodeInstall MCP server on VS Code
Follow these triage steps to resolve integration issues quickly.
Before debugging your code, verify if the Solaris platform is operating normally.
Subscribe to updates on the Status Page to receive immediate notifications about maintenance windows or incidents.
Ensure your configuration matches the correct environment URLs.
| Environment | Base API URL | Authentication URL |
|---|---|---|
| Sandbox | https://api.solaris-sandbox.de | https://auth.solaris-sandbox.de |
| Production | https://api.solarisbank.de | https://auth.solarisbank.de |
The Sandbox environment is isolated and does not connect to real payment networks (SWIFT, SEPA).
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.
- 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.
- Missing Permission: Your Partner account lacks the specific role or permission to access this endpoint.
- Action: Contact your Partner Manager to request access.
- 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.
- 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.
- Timeout: Your endpoint must respond with a
200-299status 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.
Refer to our official documentation for due diligence, audits, or legal verification:
- Banking Licenses: View our Licenses (CRR)
- Security Standards: Information Security & Data Protection
- Whistleblowing: Report a compliance concern
Contact: The Onboarding Team. When: You are integrating Solaris products or testing in Sandbox.
Contact: The Incident Management Team. When: You are live in Production and experiencing a critical bug, outage, or payment failure.
For new feature requests or commercial topics (e.g., 403 Errors), contact your Partner Manager.
Include the following 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)If you suspect a fraudulent transaction or a compromised account, do not email Support.