Not a gateway — an orchestrator.
A central hub between your business and many banks and payment providers. Thynqora routes every payment to the best provider, fails over when one won't play, enforces approval, and posts it to a ledger — money-in and money-out, end to end.
Every payment, the same disciplined route.
From a signed request to a ledger entry, each stage is explicit and each state transition is an event you can audit.
Tenancy & validation
The tenant and its zone are resolved from a signed token, and the request is validated before anything else runs.
Risk & compliance screening
Every payment is screened before a single provider is considered — nothing routes until it clears.
Routing & failover
Eligible providers are scored on success, speed and cost, and arranged into a failover chain.
Maker-checker approval
Amount-banded four-eyes mandates are frozen onto the payment; the maker can never sign their own.
Connector execution
The chosen connector executes the payment; on failure it fails over to the next provider in the chain.
Ledger posting
On confirmed success, a double-entry ledger posting records the movement — reconciled against the statement later.
Pick the best provider — and prove why.
Choose an optimization profile and the engine scores every eligible provider, builds a failover chain, and stores the full decision. No black box.
Optimization profiles · success / speed / cost
| Provider | Succ | Speed | Cost | Score | Rank |
|---|---|---|---|---|---|
| Provider A | 0.98 | 0.72 | 0.40 | 0.86 | chosen |
| Provider B | 0.95 | 0.90 | 0.55 | 0.85 | failover 1 |
| Provider C | 0.90 | 0.60 | 0.95 | 0.82 | failover 2 |
decision stored · concentration caps applied · provider override available
An orchestrator, not a black box.
Smart Routing
Score every eligible provider on success rate, speed and cost, then build a failover chain. Four optimization profiles plus custom, versioned per tenant.
Explainable Decisions
Every routing decision is decomposed and stored — see exactly why a provider was chosen or skipped.
Optional ML Assist
A model predicts success probability and latency per candidate — and stays silent until it has enough data to be trusted.
Connector SDK & Failover
A pluggable connector model with a catalogue spanning banks, e-money, card acquirers, payout networks and digital assets. Failover moves between providers, never between accounts at one bank.
Maker-Checker Approval
Amount-banded four-eyes mandates with quorum. The maker never signs their own payment, and nobody signs twice.
Rules Engine
Versioned, tenant-scoped rules with dry-run and draft/publish. Pin, exclude or prefer a connector, force approval, or block a payment.
Ledger & Reconciliation
Double-entry ledger on confirmed success, plus statement reconciliation with five named break types and a matcher that refuses to guess.
Collections (Money-In)
Incoming payments are attributed by virtual account or payer reference — never guessed — and returned when they can't be placed.
Treasury & FX
FX quotes with per-pair margins and a held-quote flow, plus treasury positions, exposures and limits.
Multi-Zone & Multi-Tenant
One deployment per jurisdiction, a database per tenant, and automatic tenant isolation enforced by architecture — not hand-written filters.
Enterprise Security
OIDC + PKCE + RS256, per-permission RBAC, idempotency proven under concurrency, and BYOK AES-256-GCM credential sealing.
Operations Portal
Dashboards, payments with full failover history, a collections / exceptions queue, SLA-driven cases, approvals and a visual routing-rule builder — white-labelled.
Connector catalogue
One integration. Many ways to move money.
A pluggable connector catalogue of 30+ providers across five categories and multiple regions. Each connector declares its capabilities and credentials; routing and failover work the same regardless of who's underneath. New providers plug into the same SDK.
Controls that hold up to audit.
Stop hard-wiring one bank.
See a payment routed, failed over and recovered — with the decision and the ledger entry to match.