Standards

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

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

General formats

Character encoding

The Solaris API uses UTF-8 encoding.

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

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.

Merchant Category Codes (MCC)

Solaris uses standard Merchant Category Codes for transaction classification.

• Visa Merchant Data Standards
• Mastercard MCC Reference

Return codes

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