One platform for every banking operation.
Wahid unifies case management, workflow and integrations in a single, auditable back office - configurable per bank. Extendable to any use case.
A case type is four things, composed.
Draw the process. Define the data. Declare the rules. Set the clock. Wahid composes them into a case type - and every case runs it.
Configured, versioned, ready to run.
Intake to sealed, in one flow.
- 01A case arrivesIntake from any channel lands in the right team's queue, SLA armed.
- 02The workflow takes overRole gates, maker–checker, timers — the state machine you drew.
- 03Routed by ruleDecision tables score and route — every rule versioned and explainable.
- 04Sealed for goodEvery action seals into a hash-chained audit log, verifiable on demand.
Everything a back office needs, in one place.
Case management, end to end
Queues and team routing, SLA timers on business calendars, row-level visibility - and one timeline that records everything.
A workflow engine you can see
Design on a canvas: stages, transitions, role gates, approval gates, decision gateways and integration API calls. Versioned, with history and restore.
Access to the widget
Default-deny RBAC gates modules, tabs and widgets. One matrix of who sees what.
Customer 360
Profile, accounts, cards and loans bound to your core over mTLS - no data duplication.
Modules, two ways
Extend the platfrom for your specific usecase using UI based module builder or full React modules on the SDK.
A record you can hand a regulator.
Every action chains to the last with sealed hashes. Verify integrity on demand and hand regulators evidence, not exports.
- Hash-chained, concurrency-safe sealing
- On-demand chain verification
- Customer-access auditing
One integration layer. Every system, every module.
Wahid Core sits between your bank's systems and the modules your teams work in — orchestrating REST/SOAP over mTLS, an outbox with retries and circuit breakers, with every call permission-gated.
Default-deny RBAC
Permissions gate every module, tab and widget - with segregation of duties.
Tamper-evident audit
A hash-chained system of record, verifiable from day one.
On Premise
Runs on your infrastructure - your data never leaves your estate.
OIDC-native identity
Keycloak out of the box - JIT provisioning, role sync, teams from IdP groups.
Months, not years without losing control.
Configuration over code where it's safe. Modules over forks where it's not.
Time to market
- Workflows, forms, rules and SLAs are configuration
- New use cases without a release
- Per-bank modules ship without forking the platform
Control
- On-Premise, on your infrastructure
- Tamper-evident audit from day one
- Default-deny RBAC to the widget level
See Wahid in action.
A guided walkthrough with your use case in mind.