Product scope
Marqib helps compliance teams review unusual trades and money movements, see the supporting records, and document a decision. Here is the scope of the pilot build.
Scope and release labels reviewed: 27 October 2026
Decision-time evidence versions, new data-quality and delivery controls, and mandatory re-review of changed case proposals are developed and awaiting release to the live demo. These features are labelled separately below.
Start with the records your firm already holds.
Ten built-in monitoring and screening rules cover selected patterns such as linked-account trades, repeated near-threshold deposits, rapid fund movement and activity beyond the declared profile. Detection depends on the required data being loaded.
Screen client and payment-counterparty names against UN, OFAC, EU and UK lists. UAE and MASAK lists use uploads. A potential match goes to review; it is not an identity confirmation.
See why an alert was raised and inspect records and linked accounts. An analyst proposes an outcome for a different MLRO to review. MLROs can also decide directly. A shared link alone is not proof of wrongdoing.
Record holds on pending withdrawals and return allow, review or hold through the decision API. Your payment system must apply that response; the case record alone does not stop a bank transfer.
Preview threshold changes on loaded history, build rules in a structured form and approve versions. Sample completed cases and review workload and outcome reports.
Load customer, trade, payment and optional activity files by CSV or scheduled file pull. The interface is in English, Arabic and Turkish; recorded evidence stays in its original language.
Use named roles, authenticator-app verification and OpenID Connect sign-in. Optional model drafting checks evidence references; a reviewer checks factual accuracy and sensitive text.
Local validation records cover these additions. Cloud release and final verification remain pending.
See data issues, assigned or unassigned reviews and proposals relevant to your role in one entry point. Open overdue work first, review the evidence and continue through the existing case workflow. You cannot approve your own proposal. Developed; awaiting live demo release.
Each proposal and final decision saves a separate evidence version. Later customer or transaction edits do not replace it. Download the JSON, verify its SHA-256 or print it in English, Arabic or Turkish. goAML and MASAK submission files are outside this version archive.
Find payments requiring review by client and reason, and see recent upload outcomes. Optionally compare manual standard CSV uploads with separately declared source counts and payment totals by currency/status. Differences stop the upload. A match does not prove newly inserted records or bank reconciliation. Historical FX is unavailable; non-USD payments pause USD monetary rules. For manual deliveries, save the source period, UTC deadline and expected controls before upload. Missing and late recorded acceptances stay visible; identical accepted files reuse their original receipt.
Changed case proposals must be reviewed again before approval or return.
The connection or draft is implemented; customer-specific acceptance comes next.
MT5 Web API, cTrader, Praxis Cashier and B2Core adapters. Available fields and permissions differ by account; some data still needs file exports.
Import or receive findings from supported providers under your own licence. PEP and adverse-media data come from your provider. Marqib does not supply a global PEP database or its own blockchain intelligence.
Prepare case content and export drafts. Local schema, indicator codes and sector-specific fields require verification. An authorised person submits through the authority’s system; filing receipts are not automatically reconciled.
A container package and installation guide are prepared. Your IT team validates the region, backups, restore process, security settings and operating environment before live use.
These are priorities for development, not features available for purchase today.
Verify missing or late files, source-to-record differences across recurring feeds, and historical exchange-rate sources. Manual periods/deadlines and CSV count/total checks are developed and awaiting live release. Automated feed/bank reconciliation and FX conversion remain planned.
Track source-of-funds questions, requested documents, due dates and periodic customer or company reviews in the same workspace.
Follow money across linked accounts and counterparties, with time-aware fan-in, fan-out and possible mule-network patterns.
Try a proposed rule on future incoming activity without creating operational cases or restricting payments, then review its results before approval.
Add versioned country and sector packs, validated exports, recorded submissions, authority receipts and corrections linked to the approved draft.
Add official submission archives, investigation holds that suspend deletion, stronger sign-in options and recorded backup-and-restore exercises.
These need additional data, specialist providers or a separate business decision.
Market-price context, full order replay, cross-instrument patterns and communications linked to an investigation.
Refund, chargeback, merchant and device patterns beyond the current deposit-and-withdrawal model.
Exchange and validate originator and beneficiary information through a licensed provider, with country-specific handling of missing data.
It highlights patterns and supports investigation. A match, risk score or shared account detail is a reason to review the records; the firm makes the decision.
It helps draft text from selected records. Reference checks do not prove a sentence is true, and token replacement does not anonymise every free-text detail. Human review remains necessary.
Priorities are shaped by pilot needs and validation results. We will mark a feature available after its scope and acceptance checks are complete; no date is promised on this page.
Agree a bounded pilot: your data sources, required rules, reporting jurisdiction and measurable acceptance criteria. Start with representative history and named reviewers.
In the data controls developed for the next release, original currency labels are preserved. Monetary thresholds are in USD; historical FX conversion is not available. Non-USD, invalid or unknown-status records make the affected client’s monetary checks incomplete. These controls await live release; their results are not a clearance.
A pilot starts with an agreed use case, data sources and acceptance criteria.