Taktile
Lets risk teams at banks and fintechs build, test and ship automated credit and fraud decisions without an engineer for every rule change.
Highlights
- Visual, no-code decision-flow builder for analysts to author and edit policy logic
- Native integrations to external data sources (bureaus, KYC/KYB, bank data) via prebuilt connectors
- Deploy and host machine-learning models for credit scoring and fraud signals inside flows
- Built-in A/B testing and shadow/backtesting against historical or live traffic
- Versioning, audit trails, and approval controls for decision governance and compliance
- Real-time decision API to embed approve/decline/review outcomes into onboarding and underwriting
- Monitoring dashboards for decision outcomes, data quality, and policy performance
- Reusable decision components and templates across onboarding, credit, AML, and fraud use cases
External link — opens taktile.com in a new tab. Taktile is a third-party product; we are not affiliated with it.
About Taktile
What it is
Taktile is a decision engine for financial services. Risk teams compose the logic behind credit, fraud and onboarding decisions, test it against historical data, and put it into production without shipping custom code for each change. Founded in 2020 and aimed at fintechs and banks.
Why it's different
The bottleneck it removes is organisational rather than technical. Risk logic changes constantly — a threshold moves, a new signal arrives, a segment behaves differently — and when every change needs an engineering ticket, the risk team ends up running the business on rules that are months out of date. Giving that team the controls, with backtesting so a change can be evaluated before it is live, is the right shape. The caution is the other side of the same coin: these decisions decline people for credit, so they carry explainability and fair-lending obligations, and a no-code interface makes an undocumented change as easy as a considered one. Change control matters more here, not less.
How people use it
It is used for credit decisioning, fraud screening and onboarding checks where the logic is genuinely dynamic. The practice that makes it safe is testing every change against historical decisions before release, and keeping an audit trail of who changed what and why — which a regulator will eventually ask for and which no platform maintains on your behalf.
Written by the n3os team. We are not affiliated with Taktile.
This listing was written from public information, without Taktile’s involvement. If you own it and something here is wrong — or you would rather not be listed at all — email us and we will correct or remove it.
Get the ones worth knowing about
We write one of these for every tool worth the trouble. Get the new ones, plus what we have found genuinely useful lately.
Your address goes to Buttondown, who send the emails on our behalf. One click unsubscribes, and the list is never sold or shared.