APIs · head to head
Paymentology vs Split

Paymentology
APIs
Cloud issuer processing across emerging and developed markets
- From
- On request
- Free plan
- No

Split
Testing
Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME
- From
- On request
- Free plan
- No
The short version
- Only Paymentology lists global issuer processing; only Split lists feature flags with targeting.
- Prices and features on this page were last checked on 20 November 2026.
How do Paymentology and Split differ?
Paymentology and Split differ on platforms and category (APIs against Testing). Only the attributes on which Paymentology and Split actually diverge.
| Attribute | Paymentology | Split |
|---|---|---|
| Platforms | Web, API | Web, API, iOS, Android, Windows |
| Category | APIs | Testing |
Identical on both: starting price (On request), pricing model (Quote), free tier (No).
Not yet recorded: founded for Split.
Which features does each one have?
They share no listed features; 8 appear only for Paymentology and 8 only for Split. 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 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
Only in Split
- Feature flags with targeting
- Metrics impact engine
- Guardrail metrics
- Statistical significance testing
- Event ingestion
- SDKs and streaming updates
- Audit and approvals
- Harness platform 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.
Paymentology
- A neobank launching cards in an African or South East Asian market where hosted United States processors have no certificationnot Split
- A mobile money operator adding a card product on top of an existing wallet basenot Split
- A bank consolidating several regional card processors onto one platformnot Split
- A fintech expanding an existing card programme into the Gulf without re platformingnot Split
Split
- A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Paymentology
- Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Paymentology
- Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Paymentology
- A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Paymentology
Where do Paymentology and Split fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Split
- Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
- Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
- The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
- Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
- As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product
How much do Paymentology and Split cost?
Paymentology is priced on request; Split is priced on request. Plan by plan below, from each vendor's own pricing page.
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
Split
On request- Harness FreeFree
- Harness Open Source and community support
- Intended for individuals and small teams
- Feature management capability limited at this tier
- Harness EssentialsOn request
- Bundled DevOps modules including CI, CD, IaC and security testing
- Standard support
- Pricing requires contacting sales
- Harness EnterpriseOn request
- Mix and match from 15 or more modules including Feature Management and Experimentation
- Premier support with a dedicated account manager
- Higher pipeline concurrency and organisation limits
Which should you pick?
Choose Paymentology if
- You need global issuer processing.
- You work on Web, API.
- You also want real time transaction data.
Choose Split if
- You need feature flags with targeting.
- You work on Web, API, iOS, Android, Windows.
- You also want metrics impact engine.
Questions people ask
- Is Paymentology or Split better?
- Neither clearly leads. Paymentology starts at On request and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Paymentology or Split?
- Paymentology starts at On request and Split at On request.
- Does Paymentology or Split run on more platforms?
- Paymentology runs on Web, API. Split runs on Web, API, iOS, Android, Windows.
- What is Paymentology best used for?
- Paymentology is most often used for a neobank launching cards in an african or south east asian market where hosted united states processors have no certification, a mobile money operator adding a card product on top of an existing wallet base, a bank consolidating several regional card processors onto one platform, a fintech expanding an existing card programme into the gulf without re platforming. Of those, a neobank launching cards in an african or south east asian market where hosted united states processors have no certification and a mobile money operator adding a card product on top of an existing wallet base are not what Split is typically brought in for.
- What can Paymentology do that Split cannot?
- Paymentology covers Global issuer processing, Real time transaction data, Virtual and physical issuance, Tokenisation. Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.
Answered from the vendors’ own pages
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.
Split: Is Split still called Split?
It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.
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.
Split: Can I buy just feature flags?
Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.
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.
Split: What does it do that a plain flag service does not?
It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.
Split: Do we need a lot of traffic?
Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.
Related pages
More on Paymentology
Other head to heads
- Paymentology vs Marqeta
- Paymentology vs Enfuce
- Paymentology vs Highnote
- Paymentology vs i2c
- Paymentology vs Thredd
- Paymentology vs Lithic
- Paymentology vs Episode Six
- Paymentology vs Tribe Payments
- Paymentology vs Fintech Farm
- Paymentology vs Unit
- Paymentology vs Synctera
- Paymentology vs Weavr
- Paymentology vs Solaris
- Paymentology vs Token.io
- Paymentology vs Treasury Prime
- Paymentology vs Trustly
- Paymentology vs WSO2 API Manager
- Paymentology vs Brite Payments
- Paymentology vs GrowthBook
- Paymentology vs Kameleoon
- Paymentology vs Eppo
- Paymentology vs Katalon
- Paymentology vs Selenium
- Paymentology vs Sauce Labs
- Paymentology vs TestRail
- Paymentology vs Applitools
- Paymentology vs CloudBees Smart Tests
- Paymentology vs QA Wolf
- Paymentology vs CircleCI
- Paymentology vs BrowserStack
- Paymentology vs BugHerd
- Paymentology vs SoapUI
- Paymentology vs Playwright
- Paymentology vs GitHub Actions
- Paymentology vs Cypress
- Paymentology vs Appium
- Split vs Marqeta
- Split vs Enfuce
- Split vs Highnote
- Split vs i2c
- Split vs Thredd
- Split vs Lithic
- Split vs Episode Six
- Split vs Tribe Payments
- Split vs Fintech Farm
- Split vs Unit
- Split vs Synctera
- Split vs Weavr
- Split vs Solaris
- Split vs Token.io
- Split vs Treasury Prime
- Split vs Trustly
- Split vs WSO2 API Manager
- Split vs Brite Payments
- Split vs GrowthBook
- Split vs Kameleoon
- Split vs Eppo
- Split vs Katalon
- Split vs Selenium
- Split vs Sauce Labs
- Split vs TestRail
- Split vs Applitools
- Split vs CloudBees Smart Tests
- Split vs QA Wolf
- Split vs CircleCI
- Split vs BrowserStack
- Split vs BugHerd
- Split vs SoapUI
- Split vs Playwright
- Split vs GitHub Actions
- Split vs Cypress
- Split vs Appium
