Softwr

Automation Integration · head to head

Flowable vs Paymentology

Flowable logo

Flowable

Automation Integration

Apache 2.0 BPMN, CMMN and DMN engine from the team that originally built Activiti

From
Free
Free plan
Yes
Paymentology logo

Paymentology

APIs

Cloud issuer processing across emerging and developed markets

From
On request
Free plan
No

The short version

  • Flowable is free; Paymentology prices on request.
  • Only Flowable lists BPMN 2.0 engine; only Paymentology lists global issuer processing.
  • Where Flowable falls short: enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives.
  • Prices and features on this page were last checked on 20 November 2026.

How do Flowable and Paymentology differ?

Flowable and Paymentology differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Flowable and Paymentology actually diverge.

Attributes where Flowable and Paymentology differ
AttributeFlowablePaymentology
Starting priceFreeOn request
Free tierYesNo
PlatformsLinux, Windows, Self-hosted, WebWeb, API
CategoryAutomation IntegrationAPIs
Founded20162014

Identical on both: pricing model (Quote).

Which features does each one have?

They share no listed features; 8 appear only for Flowable and 8 only for Paymentology. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Flowable

  • BPMN 2.0 engine
  • CMMN case management
  • DMN decision tables
  • Spring Boot integration
  • Modelling studio
  • Task and case application
  • REST APIs
  • History and audit

Only in Paymentology

  • Global issuer processing
  • Real time transaction data
  • Virtual and physical issuance
  • Tokenisation
  • Multi currency and multi product
  • Card controls
  • Programme management tools
  • Fraud and risk integration

What is each one used for?

Paymentology is most often brought in for A mobile money operator adding a card product on top of an existing wallet base. The jobs each tool is most often brought in to do.

Flowable

  • An insurer automating claims handling where each case follows a different path and BPMN alone cannot express itnot Paymentology
  • A bank embedding process orchestration inside an existing Spring Boot estate rather than buying a separate platformnot Paymentology
  • A team leaving Activiti or jBPM that wants the same API family with active commercial maintenancenot Paymentology
  • A regulated organisation needing complete process history and decision table audit trails for supervisorsnot Paymentology

Paymentology

  • A neobank launching cards in an African or South East Asian market where hosted United States processors have no certificationnot Flowable
  • A mobile money operator adding a card product on top of an existing wallet basenot Flowable
  • A bank consolidating several regional card processors onto one platformnot Flowable
  • A fintech expanding an existing card programme into the Gulf without re platformingnot Flowable

Where do Flowable and Paymentology fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Flowable

  • The open source engine is genuinely usable but ships without the modelling studio, work application and admin console, so an open source deployment means building your own user interfaces before anyone can use it
  • It expects Java engineering capacity; teams looking for a business-user low-code automation tool will find the modelling and deployment cycle far too technical
  • Enterprise pricing is not published and is quoted per deployment, leaving buyers without a benchmark against Camunda or IBM alternatives
  • The Activiti fork left three engines with related APIs and overlapping documentation in circulation, and search results routinely return advice for the wrong one
  • Flowable AG is a small Swiss company relative to its competitors, so the partner network, training market and pool of engineers with production experience are all limited outside Europe

Paymentology

  • Paymentology processes but does not hold issuing licences, so every market still needs your own licence or a sponsor bank, which is usually the slowest and most expensive part of a launch
  • Fees include per active card charges and monthly minimums, so a portfolio with many dormant cards pays for plastic that generates no interchange
  • Certification, settlement and scheme relationships differ by country, so a multi market rollout is a series of separate projects rather than one integration
  • As a processor it sits between your product and the networks, meaning outages and scheme mandate changes reach your cardholders through a party you do not control
  • Documentation and developer self service are weaker than the United States hosted processors, so early integration depends heavily on Paymentology implementation staff

How much do Flowable and Paymentology cost?

Flowable is free to use; Paymentology is priced on request. Plan by plan below, from each vendor's own pricing page.

Flowable

Free
  • Flowable Open SourceFree
    • Apache 2.0 licensed BPMN, CMMN and DMN engines
    • Embeddable Java library or standalone apps
    • No modelling studio or enterprise applications
  • Flowable EnterpriseOn request
    • Modelling studio, work application and admin console
    • Connectors, forms and advanced identity management
    • Support with SLA and version maintenance

Paymentology

On request
  • Paymentology processingOn request
    • Quoted per programme and per market
    • Typically per transaction and per active card fees plus a monthly minimum
    • Issuing licence or sponsor bank required in each market and not provided

Which should you pick?

Choose Flowable if

  • You need bpmn 2.0 engine.
  • You want to start without paying.
  • You work on Linux, Windows, Self-hosted, Web.
  • You also want cmmn case management.

Choose Paymentology if

  • You need global issuer processing.
  • You work on Web, API.
  • You also want real time transaction data.

Questions people ask

Is Flowable or Paymentology better?
Neither clearly leads. Flowable starts at Free and Paymentology at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Flowable or Paymentology?
Flowable has a free tier; the other does not. Paid plans start at Free for Flowable and On request for Paymentology.
Does Flowable or Paymentology run on more platforms?
Flowable runs on Linux, Windows, Self-hosted, Web. Paymentology runs on Web, API.
Can I use Flowable for free?
Yes. Flowable has a free tier, so you can try it without paying. Paymentology starts at On request.
What is Flowable best used for?
Flowable is most often used for an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it, a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform, a team leaving activiti or jbpm that wants the same api family with active commercial maintenance, a regulated organisation needing complete process history and decision table audit trails for supervisors. Of those, an insurer automating claims handling where each case follows a different path and bpmn alone cannot express it and a bank embedding process orchestration inside an existing spring boot estate rather than buying a separate platform are not what Paymentology is typically brought in for.
What can Flowable do that Paymentology cannot?
Flowable covers BPMN 2.0 engine, CMMN case management, DMN decision tables, Spring Boot integration. Paymentology covers Global issuer processing, Real time transaction data, Virtual and physical issuance, Tokenisation.

Answered from the vendors’ own pages

Flowable: Is Flowable open source?

Yes, the BPMN, CMMN and DMN engines are Apache 2.0. The modelling studio and enterprise applications are commercial.

Paymentology: Does Paymentology provide the BIN and licence?

No. You need your own issuing licence or a sponsor bank in each market; Paymentology processes the transactions.

Flowable: How does it relate to Activiti and jBPM?

The same core developers built jBPM, then Activiti, then forked Activiti in 2016 to create Flowable.

Paymentology: What is the actual pricing model?

Per transaction and per active card, with a monthly minimum. Dormant cards still cost, so model your activation rate.

Flowable: What does Flowable Enterprise cost?

Nothing is published. It is quoted per deployment by the vendor.

Paymentology: Why choose it over a United States issuer processor?

Network certification and live programmes in markets where those processors do not operate, which decides feasibility rather than preference.

Flowable: Why choose it over Camunda?

CMMN case management is a first-class engine, which matters when work is exception-driven rather than a fixed sequence.

Share

Related pages

Other head to heads