Transaction Monitoring

Screen every payment through a pipeline you control.

Each pay-in and pay-out runs through an ordered set of compliance checks — every one configurable per tenant. The engine clears or holds; a human always makes the final reject.

The Decision Pipeline

Seven checks, in order.

A failing check never aborts the run — it's recorded and the pipeline continues. All-pass clears the payment; any fail or flag holds it for review.

CHECK 01

Banned / Blacklist

Match any value against your per-tenant blacklists. Blacklist types bind to a data point — country, currency, IBAN, anything you configure — and a hit is a hard fail.

CHECK 02

Custom Rules

Operator-based rules authored in plain language: equals, not-equals, contains, greater-than. Combine them per module without writing code.

CHECK 03

Velocity

Cap rapid or repeated activity. Group by any field, measure by count or amount, over any rolling window (minutes to months), with optional multi-condition filters.

CHECK 04

Sanctions & PEP

Screen customer and beneficiary names against sanctions and PEP lists through your chosen, per-tenant screening provider. A hit flags for human disposition.

CHECK 05

Fraud Scorecard

A deterministic, explainable score on amount thresholds, round-number structuring hints, high-risk geography and missing beneficiary data. Flags above your threshold.

CHECK 06

Transaction Ring

A payer→payee money-flow graph that surfaces mule and ring patterns — fan-in, fan-out, circular flows, reciprocal pairs and shared accounts. Off by default, fully tunable.

CHECK 07

Risk Assessment

Weighted per-data-point scores summed and mapped onto the risk bands you define. A high band flags the payment for review.

CLEAR

Every enabled check passed — the payment proceeds.

HOLD

A check failed or flagged — routed to the review queue. The system never auto-rejects.

No-Code Configuration

Owned by compliance, not engineering.

Data points, the checks that run, rules and risk bands are all configured from the console — and simulated before they go live.

Schema Manager

Define the data points every payment carries and which checks each feeds. Creating a data point provisions its storage automatically.

Service Rules

Choose exactly which checks run for each payment module — pay-in and pay-out are configured independently.

Rule Simulation

Enter sample pay-in / pay-out values and see which rules match and what the decision would be — nothing is saved until you're ready.

Risk Bands

Set the score ranges the risk-assessment check maps a payment onto, from low through critical.

Two ways to ingest

Send payments however you already do.

Post a fixed-shape payment to the pay-in / pay-out endpoints, or use schema-driven ingestion where the request fields are generated from your configured data points. Every value is validated against its data-point rules before the pipeline runs.

  • Fixed-shape pay-in / pay-out API
  • Schema-driven dynamic ingestion
  • Evaluate (dry-run) or submit & record
  • Per-field validation on every value

POST /api/v1/compliance/engine/payin

{
  "amount": 48920,
  "currency": "CHF",
  "beneficiary_iban": "CH93•••",
  "party_id": "cust_8842",
  "evaluate": true
}

→ decision

{
  "status": "HOLD",
  "checks": [
    { "velocity": "FLAG" },
    { "sanctions": "PASS" },
    { "risk_band": "high" }
  ]
}
The Reviewer Workflow

Held cases, worked to a decision.

thynqora.app / compliance-queue — Pay-in LIVE
ReferenceAmountChecksStatusCreated
PMT-8842$48,920VSRHOLD2m ago
PMT-8841$1,204✓CLEAR3m ago
PMT-8838$12,500BHOLD6m ago
PMT-8834$860✓CLEAR9m ago
PMT-8829$27,300FRHOLD12m ago
V VelocityS SanctionsR Risk bandB BlacklistF Fraud✓ Cleared

Compliance Queue

Every recorded pay-in / pay-out decision — pending, held, cleared or rejected — with dynamic columns generated from your configured fields.

Case Locking

Reviewers lock a case while they work it, with a timed lease and admin force-release, so two people never decide the same payment.

Documents & Activity

Attach evidence, read the full per-check breakdown, and follow an immutable activity trail on every case.

Decision Webhooks

When a reviewer clears or rejects a case, a webhook fires to your endpoint with the full payment and check breakdown.

Configure it against your own flows.

Bring a sample of your transactions and we'll show the pipeline holding the right ones.