galanthus documentation

galanthus gives applications one way to read accounts, retrieve transactions, and run payment workflows across banks and financial providers. It is available as a native library and as gln, a command-line tool designed for automation. FinTS 3.0 / 4.1, EBICS, Revolut, and Wise sit behind that shared product surface.

See the galanthus product page for 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

How galanthus maps FinTS 3.0 and 4.1 to shared account, payment, and approval workflows, including statement formats, capability discovery, and duplicate-submission protection.

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 run in CI, which remain manual-only, and why MemorySanitizer requires a separately instrumented dependency environment.

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 is commercially licensed rather than published as an open-source product. Premium-tier licensees receive the full source tree under the commercial source-available, non-redistributable licence after commercial terms are agreed. See procurement.