Overview:
Ballerine is an open-source risk management infrastructure designed for global payment companies, marketplaces, and Fintechs. It automates decision-making for merchants, sellers, and users throughout the customer lifecycle, including account opening (KYC, KYB), underwriting, and transaction monitoring. The system uses a flexible rules and workflow engine, a third-party plugin system, a manual review back office, and document collection frontend flows. It is currently undergoing a major rebuild and is not actively supported in its open-source form.
Core Features:
Back Office: A case management dashboard for manual decision-making on user applications and transactions.
Workflow Engine: Orchestrates and automates different parts of the system to define and run process steps.
KYB Collection Flow: Enables real-time modification of KYC/KYB frontend user journeys.
Rule Engine: Allows leveraging various rule types to ensure compliance with a user's risk policy. (Note: This component is still under construction.)
Plugin System: Integrates with third-party vendors, APIs, and databases.
No-Code Builder: A work-in-progress feature intended to allow non-technical users to configure risk rules and workflows.
Use Cases:
Fintechs and payment companies automating merchant and seller approval workflows, including document collection and manual review.
Marketplaces managing user identity verification (KYC/KYB) during account opening.
Risk operations teams reviewing and processing cases through a dedicated back-office dashboard to approve, reject, or request resubmissions.
Developers building adaptive user journeys that change in real-time based on a user's risk profile, with the option to self-host for data ownership.
Why It Matters:
Ballerine positions itself as an open-source alternative that gives organizations control over their risk management processes without being locked into a single vendor's data sources or pricing. Its modular architecture—combining a workflow engine, a plugin system for third-party integrations, and a manual review back office—allows teams to tailor decisioning flows to their specific policies. The ability to self-host keeps sensitive data within a user's own infrastructure, addressing data ownership concerns.
