galanthus documentation

galanthus is a banking integration library and CLI (gln) for commercial embedding. It supports FinTS 3.0, FinTS 4.1, and EBICS through shared business commands, and it integrates with Revolut and Wise through plugin-backed provider surfaces.

See the galanthus product page for the Verified against snapshot and the commercial model.

Contents

Quickstart

Build-and-run guide for the gln CLI against a real bank endpoint. Covers: building the CLI, initialising a profile, running profile bootstrap, issuing a first read-only command (accounts list, balances list), and the EBICS variant including TLS pinning and bank-key verification.

CLI reference

Per-command reference for gln: every leaf command has its own page (Synopsis, Options, Description, Requirements, Status and exit codes, Result keys, Examples, Notes, See also). Quick links: profile init, profile bootstrap, profile auth login revolut, profile auth login wise, accounts list, balances list, transactions list, transfers sepa, tan resume. The same exit-code contract applies across all commands (0 success, 1 failure or rejected, 10 TAN or continuation input required, 11 command succeeded but explicit follow-up is still required, 130 interrupted), and the troubleshooting page covers cross-cutting failure modes.

Library reference

C ABI for embedding galanthus into a host process. Audience: C and C++ embedders linking the shared library directly, plus FFI binding authors (Python ctypes, Go cgo, Rust bindgen, C# P/Invoke, and similar). Quick links: Getting started, Conventions, Backend handles, Backend results, Accounts, balances, and transactions, Transfers, Direct debits, TAN and resume, Payloads, and the ABI function index for the per-function reference.

Architecture reference

Module layout, dialog model, TAN and resume flow, storage model, and parser architecture. The library is library-first: the client layer owns typed operations, interruptions, continuation tokens, and persistence wiring; the gln CLI is one adapter over the API rather than a separate application stack. FinTS 3.0, FinTS 4.1, and EBICS sit behind shared business workflows rather than separate public command trees.

Protocol support

FinTS 3.0 and FinTS 4.1

Current coverage matrix: which business transactions are implemented for each FinTS version, TAN-mode support, statement formats (CAMT preferred, MT940 fallback), and the idempotency / anti-duplication approach used for FinTS 4.1 transfers.

EBICS

Library and CLI integration notes for EBICS onboarding, key lifecycle, bank-key verification, TLS certificate pinning, PAIN payload generation, and supported read/submission operations.

Neobank integrations (Revolut, Wise)

Plugin model for Revolut and Wise provider APIs. The sub-page covers the plugin trust boundary, profile/auth setup, provider-specific CLI entry points, library entry points, and capability checks.

C ABI

C ABI surface for embedders and FFI bindings (Python, Rust, Go, C#, ...). The full per-page reference, including conventions, payload shapes, and the per-function index, is published under Library reference.

Sanitiser policy

Which sanitisers are routinely run and the CI versus manual split. Address-, Undefined-Behaviour-, Thread-, and Memory-Sanitizer coverage across the test and live-suite surfaces.

Live-test plan

Staged manual live-test plan and galanthus-live-suite usage. Describes how the library is exercised end-to-end against real bank endpoints and the staging discipline applied when bringing a new bank or a new FinTS / EBICS version online.

Test reports

Dated live-test reports against real bank endpoints. Each report records the endpoint, the test date, the FinTS / EBICS version, and the exercised commands. Reports are referenced from the product page's Verified against section and published under /reports/galanthus/.

Changelog

Release-by-release changelog for galanthus.

Evaluation path

The Quickstart shows gln making a read-only call against a real FinTS endpoint. The Library reference covers embedding galanthus through its C ABI from C, C++, or any FFI host. The Architecture reference covers module layout, dialog model, and storage.

Commercial evaluation proceeds via procurement; evaluation-licence requests use the subject line [Product evaluation] galanthus.

Source repository

galanthus does not have a public source repository at launch. Premium-tier licensees receive the full source tree under the commercial source-available, non-redistributable licence after commercial terms are agreed. See procurement.