Your ops team gets a configurable, auditable case platform. Your engineers get an SDK. Launch new operations in days - with the controls regulators expect, from day one.
Admin panels, KYC queues, dispute trackers - internal tools nobody planned for, rebuilt at every stage of growth while the roadmap waits.
Handoffs in Slack, evidence in sheets, status in someone’s head. Fine at a thousand customers - fatal at a hundred thousand.
Licensing and audits ask for maker-checker, audit trails and access control - controls that are expensive to retrofit and impossible to fake.
Without queues, SLAs and routing rules, operations scale linearly with hiring - and every departure takes process knowledge with it.
Ops configures workflows in the console. Engineering extends the platform through an SDK and connects systems through one integration layer - nobody builds another admin panel.
Everything an operation needs is configuration - versioned with draft, activate, archive and history. Ops iterates in the admin console; engineering stays on the roadmap.
Stages, transitions, role gates, approval gates, decision gateways and API calls - a state machine you can see, not a config file you decode.
Case data captured through a form builder with sections, field types and validation - no React sprint for every new checklist.
Decision tables score and route cases - readable by your risk team, versioned, simulated before they go live, explainable afterwards.
SLA policies on the case or a single stage, calendar-aware. Breaches surface in queues before they become complaints.
A screening hit, a dispute, an escalation - it lands in the right team’s queue, SLA armed.
IntakeRole gates, maker-checker, timers - the state machine you drew.
In workflowDecision tables score and route - every rule versioned and explainable.
RoutedEvery action seals into a hash-chained audit log, verifiable on demand.
Sealed ✓One timeline holds it all: transitions, approvals, comments, documents, integration calls - who, what, when, in order.
Screening-hit triage, document review and EDD approval chains - so growth campaigns don’t drown compliance in manual review.
Alert queues with decision-table triage and SLA-bound response - measurable, auditable, and staffed by queue instead of by heroics.
Network deadlines as timers, maker-checker on decisions, evidence attached to the case record - not scattered across tools.
Customer 360 pulls live data from your systems into one view, so tier-2 support works a case - not five browser tabs.
If you can draw it as stages and rules, Wahid can run it - this week, not next quarter.
$ pnpm create-module disputes ✔ module scaffolded · sdk ^1.x // src/index.ts export default defineModule({ id: 'disputes', views: [{ id: 'queue', permission: 'DISPUTES.VIEW' }], routes: [{ path: '/disputes', page: DisputesQueue }], });
REST-first, with the delivery guarantees ops platforms usually skip. Connect your ledger, processors and KYC vendors once - reuse them from every workflow.
OAuth2 client credentials, API keys, HMAC, bearer and basic - plus mTLS when a bank partner demands it, and SOAP for the legacy corner cases.
HMAC-verified inbound webhooks open or advance cases; outbound calls gate workflow transitions or fire-and-forget notify.
Outbox with retries and dead-letter, idempotency keys on every call, circuit breakers and explicit timeouts - at-least-once, receiver-dedupable.
A blocking call that fails rolls the transition back cleanly. A timeout is an explicit unknown-outcome, never a silent success.
The controls a license application asks about are the platform’s foundation - not a roadmap item you promise the regulator.
A single-tenant deployment in your cloud account - or on-premise when a bank partnership or regulator requires it. Your data never leaves your estate.
OIDC-native with Keycloak: SSO against the IdP you already run, just-in-time provisioning, roles and teams synced from groups.
Begin with one case type and one team. Add workflows, modules and integrations as operations grow - on the same platform, without migrations.
Predictable platform pricing per deployment - no per-seat meter punishing you for growing the ops team.
Financial software still runs on systems written decades ago and patched ever since. We build the frontier alternative: platforms that are configurable, auditable and AI-ready from day one - built in the GCC, for the institutions the region’s standards are written for.
Our engineers work alongside yours - from the first workshop through production. Consulting and embedded engineering with deep banking-domain context.
Wahid, the back office - available today. SafeConnect, open-banking consent management - in active development on the same platform.
Bring one workflow you run in spreadsheets today - we’ll show it configured and running in Wahid, queues to audit trail.
Two hours with your ops and engineering leads - we map one real process end to end.
Your case types, rules and SLAs live in Wahid - reviewed with the team that will run them.
Wire your stack through the integration layer, deploy single-tenant in your cloud, go live.