Integrations
Payment providers, banks, your existing accounting and your own systems. What works today is marked green — what is built but still waiting on a third-party contract, we say plainly.
Recurring revenue from several sources in one set of books.
Any number of accounts, including fees, payouts and failed payments.
Swiss provider. Transactions and subscriptions via signed webhooks.
Swiss provider. Transactions and subscription lifecycle via signed webhooks.
The Swiss payment route straight from Fynaro — also as a safety net for declined cards.
Movements in, payments out.
Upload the statement from any Swiss bank; payments are matched automatically.
Payment runs as a file for e-banking. Format produced, not yet validated with a bank.
Direct account connectivity to the major banks. Adapter built, SIX participation contract pending.
Fetch statements automatically and submit payments directly. Requires a bank contract.
Getting in, getting out, working together.
bexio, Abacus and Banana are detected automatically; other systems via generic CSV — with AI-assisted account mapping and rollback.
Journal as CSV, Banana format and an audit-ready deferral schedule.
A dedicated login instead of shipping data — without consuming a user seat.
UBL per EN-16931 is produced. Fynaro is not a certified Peppol access point.
For everything you want to automate yourself.
Programmatic access with your own keys and per-key permissions.
Signed events (HMAC-SHA256) for Zapier, Make or your own endpoints.
AI assistants reach your financial data through the Model Context Protocol.
Use your own Anthropic key — or switch AI off entirely.
“Ready to connect” means the code is built and tested, but operation depends on a third-party contract (SIX, a bank, a Peppol provider). We would rather label that than leave it vague.
Tell us which system you want to connect. Via the API and webhooks, much is already possible today.