Account management

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

This guide explains how to manage customer accounts, retrieve balances, and handle account statements using the Solaris API.

Prerequisites

Before managing accounts, you must have successfully onboarded a customer:

• Onboard a Person
• Onboard a Business

Account balance

The account balance is not a single number but a set of values representing different financial states.

Real-time balances

These values reflect the current state of the account and are returned in the GET Account response.

Dispositions

A Disposition is a booking that has been agreed upon but has a valuta_date (value date) in the future.

• These are returned in the bookings list but are not yet applied to the balance.
• They become effective (affecting interest and balance) only when the valuta_date is reached.

Statement balances

These values are specific to Account Statements and represent snapshots in time.

Overdrafts and Limits

If your solution includes Overdrafts, the Account Limit determines the maximum allowed negative balance.

• Overdraft Facility: The approved credit line (e.g., €500).
• Impact: This amount is added to the available_balance, allowing the customer to spend more than their balance.

Balance calculation example

Scenario: An account has a limit (overdraft) of €100.00.

Retrieve balance

• GET Retrieve balance for an account
• GET Retrieve average daily balance - Useful for calculating interest or service fees.

Bookings

A Booking represents a finalized movement of funds (e.g., a SEPA transfer or a settled card transaction).

• Impact: Bookings update the balance.
• Tracing Transactions:
  • transaction_id: The ID of the original transaction that created this booking.
  • return_transaction_id: Used for R-Transactions (Refunds, Returns, Rejects). It exposes the ID of the original transaction that is being returned or refunded.
• Value Date (valuta_date): The date used for interest calculation. This may differ from the booking_date (e.g., for backdated interest or correction bookings).

• GET Retrieve bookings

Reservations

A Reservation is a temporary restriction of funds. It blocks a specific amount for a pending transaction that has not yet been booked (settled). Common examples include card authorizations at a point of sale.

Reservation lifecycle

Reservations persist until a specific event resolves them:

1. Resolution (Settlement): The reservation remains active until the merchant or system captures the payment. Once captured, the reservation is removed, and a Booking is created for the final amount.
2. Expiration: If the transaction is not captured within the timeframe defined by the card scheme, the reservation automatically expires, and the funds are released back to the available_balance.

• GET Retrieve reservations

Account statements

Solaris provides two types of statements. You must understand the legal distinction between them.

1. Statement of Account (Rechnungsabschluss)

According to § 355 HGB, banks are legally required to regularly issue a statement that contains information about all bookings, interest, fees, and costs.

• Legal Status: Legally Binding.
• Frequency: Quarterly.
• Content: Closing balance, fees, interest, and mandatory legal disclaimers.
• Requirement: You must generate this and provide it to the customer.

Overdraft Information: If the account has an overdraft, the statement must also include:

• overdraft_facility: The granted limit.
• overdraft_rate: The interest rate applied.
• interest_accrued: The actual interest charged for the period.

Generating the statement: Call the endpoint to generate the data, then render it into a PDF using your own template. You must include the mandatory disclaimer text provided in the API response.

The following text is an example of the disclaimer structure. You must use the exact string returned by the API at the time of generation.

Sehr geehrte Kundin, sehr geehrter Kunde,

bitte prüfen Sie die Buchungen, Berechnungen und den Abschlusssaldo im beiliegenden Kontoauszug, der zugleich einen Rechnungsabschluss darstellt. Rechnungsabschlüsse gelten als genehmigt, sofern Sie innerhalb von sechs Wochen nach Zugang keine Einwendungen erheben. Einwendungen gegen Rechnungsabschlüsse müssen der solarisBank schriftlich oder in Textform (z.B. an support@solarisbank.de) zugehen. Im Falle der Einwendung in Textform genügt zur Fristwahrung die rechtzeitige Absendung. Der angegebene Kontostand berücksichtigt nicht die Wertstellung der einzelnen Buchungen. Dies bedeutet, dass der genannte Betrag nicht dem für die Zinsrechnung maßgeblichen Kontostand entsprechen muss und bei Verfügungen möglicherweise Zinsen für die Inanspruchnahme einer eingeräumten oder geduldeten Kontoüberziehung anfallen können. Gutschriften aus eingereichten Lastschriften und anderen Einzugspapieren erfolgen unter dem Vorbehalt der Einlösung. Guthaben sind als Einlagen nach Maßgabe des Einlagensicherungsgesetzes entschädigungsfähig. Nähere Informationen können dem Informationsbogen für den Einleger entnommen werden, den Sie gemeinsam mit unseren für den Geschäftsverkehr mit Ihnen geltenden Allgemeinen Geschäftsbedingungen und besonderen Bedingungen unter www.solarisbank.de/partner einsehen können.

Mit freundlichen Grüßen

Ihre solarisBank

---

Clearance of account is considered accepted if you do not raise any objection within six weeks after receipt. Objections regarding account statements have to be submitted to solarisBank in written or text form (e.g. to service@solarisbank.de). In case of objection in text form, it is sufficient to ensure its timely dispatch.

• POST Create statement of account

Recipient Data Logic: The API provides a recipient_information object to print on the statement. The content changes based on the customer type:

2. Bank Statement (Kontoauszug)

According to Article 248 §§ 3, 7, 10 EGBGB, banks are legally required to provide information about every booking to the customer at least once a month.

• Legal Status: Informational only (Not legally binding).

• Frequency: On-demand (typically monthly).

• Content: List of bookings within a specific date range.

• POST Create bank statement

3. Fee Summary Statement

• Frequency: Annual.

• Content: Summary of all fees charged to the account.

• Delivery: Automatically uploaded to the customer's Postbox.

• POST Request fee summary

Account blocking

Solaris may block an account for compliance or security reasons (e.g., suspicious activity, missing tax data).

Monitoring blocks

Subscribe to the ACCOUNT_BLOCK webhook. When received, call GET Retrieve Account to inspect the locking_status and locking_reason.

Locking statuses

Appendix I: Booking types

The booking_type field explains the business context of a transaction.

Appendix II: Reservation types

Reservations affect the available_balance but have not yet been booked to the ledger.

Appendix III: Account blocking details

When an account is blocked, the locking_status defines what is blocked, and locking_reason explains why.

Locking Reasons