fitgap

Cyclos

Features
Ease of use
Ease of management
Quality of support
Affordability
Market presence
Take the quiz to check if Cyclos and its alternatives fit your requirements.
Pricing from
€1 one-time
Free Trial unavailable
Free version
User corporate size
Small
Medium
Large
User industry
-

What is Cyclos

Cyclos is a web-based banking and payment platform used to operate digital payment services such as e-wallets, community currencies, and member-to-member transfers. It is typically used by organizations that run their own payment ecosystem, including financial institutions, cooperatives, marketplaces, and community currency operators. The platform combines account management, transaction processing, fees, limits, and role-based administration, and it can be deployed as a hosted service or on-premises depending on the edition. Cyclos also provides APIs and configurable workflows to integrate with external systems and tailor products for specific payment schemes.

pros

Configurable payment scheme engine

Cyclos supports multiple account types, transaction types, fees, limits, and authorization rules, which helps organizations model different payment products in one system. Administrators can configure roles, permissions, and operational workflows without rebuilding core logic. This is useful for closed-loop payment networks and community/alternative currency programs where rules differ from standard card processing. The configurability is a practical differentiator versus tools focused mainly on invoicing or SMB payment acceptance.

Multi-channel user access

The platform provides web access and typically supports mobile access patterns for end users and administrators, enabling self-service for balances, transfers, and statements. It includes member management and back-office functions for customer support and operations teams. This suits deployments where both consumers and agents/merchants interact with the same payment network. It reduces reliance on separate portals for different user groups.

Integration and deployment options

Cyclos offers APIs to integrate with external applications, identity systems, and other financial infrastructure. Organizations can choose deployment models (commonly including hosted and on-premises options depending on licensing/edition), which can align with regulatory or data residency requirements. This flexibility supports use cases such as integrating payments into a broader platform or running a standalone digital banking service. It also helps when migrating from legacy systems or connecting to existing accounting/ERP environments.

cons

Not a general-purpose PSP

Cyclos is designed to run a payment network or digital banking environment rather than act as a simple plug-in payment gateway for standard card acquiring. Organizations that only need basic online payment acceptance may find it heavier than necessary. Additional providers may still be required for card processing, bank transfers, or local payment rails depending on the country. This can increase integration scope compared with turnkey payment acceptance tools.

Implementation can be complex

Because the product is highly configurable, initial setup typically requires careful design of transaction types, fees, limits, and operational roles. Deployments often involve integration work, data migration, and security/compliance configuration. Teams without payments operations experience may need vendor or partner support to reach production. Time-to-launch can be longer than lightweight payment or invoicing products.

Limited out-of-box accounting depth

While Cyclos provides transaction records, statements, and operational reporting, it is not a full accounting system with complete general-ledger functionality for all enterprise finance needs. Many organizations still integrate it with dedicated accounting/ERP software for statutory reporting and complex financial consolidation. Reconciliation and reporting requirements can drive additional customization or external tooling. Buyers evaluating it under “accounting & finance software” should validate finance workflows end-to-end.

Plan & Pricing

Plan Price Key features & notes
Free €0 initial / €0 yearly Up to 300 users and turnover < €100,000; downloadable free Cyclos 4 PRO evaluation/community service.
Social license €1 initial / €0 yearly For non-profit/social-mission organisations (0–20,000 users, turnover < €200,000); application required; may require proof of charitable status.
Small (S) €500 initial / €1,000 yearly For 300–2,000 users, turnover < €300,000; allows up to 3 countries by default; hosting package available (see notes).
Medium (M) €3,000 initial / €3,000 yearly For 2,000–5,000 users, turnover < €1,000,000; includes 5 hours free setup support; allows up to 6 countries by default; negotiable lower prices for MFIs.
Large (L) Prices to be negotiated For 5,000–1,000,000 users, turnover < €60,000,000; allows up to 12 countries by default; access to mobile app source code negotiable; prices negotiated with sales.
X Large (XL) Prices to be negotiated For >1,000,000 users and turnover > €60,000,000; enterprise terms and pricing negotiated with sales.

Notes:

  • One-time (perpetual) license option: price = (5 × yearly fee) + initial fee (per price list).
  • Hosting package (offered by Cyclos/STRO) for Small and Medium licenses: €125 per month (dedicated server, backups); additional support purchasable (see support rates).
  • Support/consultancy: standard consultancy/support tariff €100 per hour for medium/large licensees; medium/large/xlarge include 5 hours free setup support (per price list & support pages).

Seller details

STRO
Utrecht, Netherlands
2001
Private
https://www.cyclos.org/
https://www.linkedin.com/company/stro

Tools by STRO

Cyclos

Popular categories

All categories