Forex Compliance Workbench

Compliance teams approve KYC cases and change customer risk rules, and every change needs one person to make it and another to approve it.

• A risk-scoring console: view and change weights under maker-checker rules, browse approved versions, and re-score customers in bulk from CSV.
• KYC review pages with document viewers (image, PDF, video, XML) and identity-match results.
• A customer 360 view with permission-gated PII unmasking, PEP review and one transaction search across three products.
• A per-domain API layer that adds fresh auth and a correlation ID to every request.

Change requests came back as nested before-and-after configs that no reviewer could read. I flattened them into readable change rows, matching risk bands by flag instead of array position, so a checker sees exactly what they are approving.

Also closed a review gap: identity-match results showed only face rows, so a case could pass while its PAN face match failed unseen. All match types now show.