Skip to content
Home/
Standards
Last updated

Standards

Solaris adheres to specific international standards to ensure data consistency, security, and regulatory compliance.

Corporate security standards

Solaris maintains the highest levels of enterprise security and operational resilience. We are officially certified and compliant with the following frameworks:

  • CRR Banking License: Solaris operates with a full German commercial banking license.
  • ISO/IEC 27001: Solaris is certified for information security management, ensuring systematic risk management.
  • PCI DSS 4.0: Solaris is fully certified under the Payment Card Industry Data Security Standard version 4.0.
  • DORA: Solaris complies with the EU-wide Digital Operational Resilience Act.
  • GDPR: Solaris is fully compliant with European data protection regulations.

For official documentation and due diligence verification, visit the Solaris Licenses & security page ↗.

API data formats

The following standards apply specifically to data formatting within API requests and responses.

StandardDescriptionReferenceExample
Country CodesISO 3166-1 alpha-2WikipediaDE, FR, ES
Currency CodesISO 4217WikipediaEUR
State CodesISO 3166-2 (Germany)WikipediaBE (Berlin)
Dates & TimesISO 8601Wikipedia2023-12-31T23:59:59Z
Phone NumbersE.164Wikipedia+491701234567

Character encoding

The Solaris API uses UTF-8 encoding.

KYC Restriction

For all fields related to Customer Data (Names, Addresses), Solaris only accepts UTF-8 Latin characters. Submitting other character sets (e.g., Cyrillic, Kanji) will cause the KYC flow to fail.

The Money object

Solaris does not use floating-point numbers for financial amounts. Instead, all monetary values (amount, balance, fee, charge) use a structured Money Object.

Properties

PropertyTypeDescription
valueintegerThe amount in the smallest unit (e.g., Cents).
unitstringThe unit of currency. Currently only cents.
currencystringThe currency code. Currently only EUR.
precisioninteger(Optional) The decimal precision of the value.

Example

To represent €10.00, you send a value of 1000 cents.

{
  "amount": {
    "value": 1000,
    "unit": "cents",
    "currency": "EUR",
    "precision": 2
  }
}

SEPA character set

The European Payments Council (EPC) limits the characters allowed in SEPA transactions (EPC217-08). Solaris enforces this restricted set on the following fields:

  • Credit Transfers: recipient_name, end_to_end_id, description.
  • Direct Debits: end_to_end_id, description, mandate.reference, mandate.debtor_name.

Allowed characters

a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
/ - ? : ( ) . , ' +

Formatting rules

  1. No leading spaces.
  2. Slashes (/):
    • Cannot start or end with a slash.
    • Cannot contain double slashes (//).
  3. Extended Characters: Solaris automatically converts extended Latin characters (e.g., ö $\rightarrow$ o:) according to EPC guidelines.

Escaping and length

Solaris must escape specific characters internally. This affects the character count limit.

CharacterEscaped AsCount Impact
' (Single Quote)'Counts as 6 characters

Merchant Category Codes (MCC)

Solaris uses standard Merchant Category Codes for transaction classification.

Return codes

Return codes for SEPA R-transactions (Refunds, Returns, Rejects) follow the EPC173-14 standard.

Previous page
Next page