Flowker is Lerian’s workflow orchestration platform for financial operations. It automates the steps that happen before, during, and after a transaction — anti-fraud checks, manual approvals, payment routing, customer onboarding, and more. Instead of building custom logic for each approval flow or validation step, you define workflows once and Flowker executes them consistently, with full audit trails and real-time visibility.Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Why use Flowker?
Financial operations involve multiple steps, approvals, and external checks. Managing these manually leads to errors, delays, and compliance gaps. Flowker centralizes this orchestration so every step stays tracked, auditable, and repeatable. For the full business case, see Why Flowker?.
Core concepts
At its core, Flowker works with two concepts:
- Workflows: The overall process — a sequence of steps that define what happens for a given operation (e.g., “process a Pix payment” or “onboard a new customer”). Workflows can branch and recover from failures automatically.
- Tasks: The individual steps within a workflow — such as checking a fraud score, waiting for a manager’s approval, calling an external service, or posting to the ledger.
What makes Flowker different?
Purpose-built for the financial domain
Unlike generic workflow tools, Flowker is modeled specifically for the transactional ecosystem. Its architecture reflects the operational and regulatory realities of banking, payments, Pix, and financial orchestration.Pre-ledger validation
Flowker enforces all validations before any posting reaches the ledger. This prevents inconsistent states, operational errors, and compliance violations — ensuring that only valid, authorized, and well-formed transactions are ever recorded.Bounded contexts by design
The platform is structured around clear bounded contexts, separating concerns such as onboarding, payments, settlement, risk, and reconciliation. This segmentation improves scalability, governance, and domain clarity across complex financial operations.Integrations with APIs, Webhooks, SDKs, and Pre-built Connectors
Flowker connects seamlessly with any external system — banking cores, fraud engines, PSPs, ERPs, or third-party APIs. As long as input/output expectations are defined, Flowker can orchestrate, transform, enrich, and route data across your ecosystem.Full audit trails
Every step inside a workflow generates detailed audit logs that can be queried, reviewed, and exported. This provides traceability and compliance-grade visibility across the entire orchestration lifecycle.End-to-end observability
Native support for distributed tracing, metrics, and structured logging, enabling real-time monitoring across workflows and external interactions.Enterprise-grade security
API Key authentication for all endpoints. Encrypted data channels via HTTPS.Developer-first experience
Flowker includes OpenAPI definitions, reusable templates, and a local development environment with Docker — enabling teams to build, test, and deploy flows with confidence and speed.Key features
Workflow orchestration
- Run tasks sequentially.
- Apply conditional logic based on HTTP status codes and response fields.
- Persist workflow state for auditing and recovery.
- Manage versions with full lifecycle control, including draft, activation, deactivation, and clone-based iteration.
Integration and connectivity
- Send HTTP requests (POST, GET, PUT).
- Receive and process webhooks from external systems.
- Connect to multiple financial service providers.
DSL engine
- Define workflows with a .
- Validate workflow definitions before deployment.
- Transform data between steps and reuse templates for faster setup.
- Reusable workflow templates for faster setup and consistency across environments.
Authentication and security
- API Key authentication (X-API-Key header) for all endpoints.
- Full audit trail with structured logs and encryption at rest.
Observability
Flowker includes built-in observability powered by OpenTelemetry, Jaeger, Prometheus, and Grafana. You can trace each workflow execution, monitor metrics, and review detailed logs for debugging and compliance.Common use cases
Anti-fraud operations
- Send transaction and account data to external fraud prevention services.
- Collect and process responses from multiple providers, and apply configurable rules to decide whether to proceed.
- Every step is logged and stored for auditing.
Manual approvals
- Pause a workflow until a person validates the operation.
- You can support multiple approval levels, send notifications, and integrate with approval systems.
- Once approved or rejected, the workflow continues or stops automatically.
Payment orchestration
- Coordinate multi-step payment flows that span multiple providers or rails.
- Flowker handles retries, reconciliation with your ledger, and automatic recovery from failures.
Customer onboarding
- Automate KYC and AML processes, integrate with credit bureaus and validation services, and set up conditional onboarding rules based on risk profiles.
API architecture
Flowker’s API is divided into three main categories: Authoring, Runtime, and Administrative. Each category has a clear purpose to help developers build, execute, and manage workflows.
- Authoring routes: create, update, and manage workflow definitions, versions, and templates.
- Runtime routes: start, monitor, and control workflow executions in real time.
- Administrative routes: manage tenants, API keys, providers, and system health.
Current status
Flowker is in active development. For additional information about specific integrations or implementation details, contact us.