FinTech · Compliance-as-a-Service · REST API
🔒 Patent-pending technology

Compliance API
RegOS

The gap this closes

MAS-licensed FinTechs need Guardian SGSV compliance coverage but cannot commit to a full SDK integration. Yet their regulatory obligations under MAS do not pause — leaving a gap between compliance requirements on paper and what is enforced in the transaction flow.

Full Guardian SGSV compliance delivered via a single REST API endpoint. No SDK. No infrastructure changes. For MAS-licensed FinTechs, payment institutions, and Wealthtech platforms.

How It Works

One API call. Full Guardian SGSV compliance. Permanent audit record.

Step 1
Transaction initiated in your platform
Your MAS-licensed platform initiates a payment or transaction through your existing flow. No changes to your core architecture required.
Step 2
Single HTTPS POST to RegOS endpoint
Before the transaction executes, your system sends one HTTPS POST request to the RegOS API. That is the entire integration.
Step 3
Guardian SGSV runs compliance assessment
Guardian SGSV performs a full compliance assessment — MAS AML/CFT-aligned, calibrated to your licensed product scope and risk appetite.
Step 4
Decision returned in milliseconds
✓ CLEARED
Transaction proceeds.
⚠ HELD
Queued for review.
Step 5
Audit record written automatically
An immutable compliance record is written for every API call — timestamped, cryptographically hashed, retained for seven years.
Example API Request & Response
POST https://api.sidian.sg/v1/compliance/check
Content-Type: application/json
X-API-Key: your_api_key
 
{
"transaction_id": "TXN-88421",
"amount": 142000,
"currency": "SGD",
"counterparty": "DBSSSGSG",
"type": "FX_SETTLEMENT"
}
 
// Response (< 100ms)
{
"decision": "CLEARED",
"audit_ref": "AUD-2026-088421",
"timestamp": "2026-06-18T09:14:22Z"
}
Illustrative sandbox environment — sample data shown for concept demonstration only. Not live transaction data or a production compliance metric.
Guardian SGSV Compliance Dashboard — Sandbox
Compliance API — RegOS
ML-AML typology detection with explainability required for MAS FEAT
Typology Flag Rate
2.1%
of requests scored
Avg Model Confidence
76.4%
on flagged decisions
Explainability Coverage
100%
rationale generated per flag
Validated Precision
0.88
vs. labeled typology set
MAS Examination

When MAS asks for your AI transaction records

Without Compliance API — RegOS
Compliance checks ran in batch without generating a per-transaction record at the point of execution. The platform cannot produce a transaction-level audit trail.
With Compliance API — RegOS
Every API call generated a timestamped compliance record at the point of execution. Export the complete archive for the requested period in minutes.
Regulatory Context

The MAS Requirements RegOS Addresses

MAS Payment Services Act (PSA)
Transaction-Level Compliance
What MAS requires
MAS-licensed payment institutions must conduct AML/CFT checks at the transaction level for every transaction, regardless of whether the instruction was generated by a human or an AI system.
How RegOS satisfies it
The Compliance API — RegOS delivers full Guardian SGSV compliance coverage for every API call — returned in milliseconds, with a permanent audit record written automatically.
MAS FEAT Principles
Explainability & Accountability
What MAS requires
FinTechs using AI in payment routing or investment execution are subject to MAS FEAT requirements. AI-driven financial decisions must be explainable.
How RegOS satisfies it
Every RegOS compliance decision is explainable: the decision, reason code, and full context are returned in the API response and written to an immutable audit record.

Compliance in One API Call.

Full Guardian SGSV Compliance Coverage
The same compliance engine that powers the institutional Guardian SDK — delivered via REST. MAS AML/CFT Notice-aligned rules, configurable to your licensed product scope.
Multi-Jurisdiction Rule Packs
Singapore primary jurisdiction with corridor market coverage for key ASEAN and international payment routes. Custom rule packs available.
Automatic Audit Record — Per Transaction
Every API call generates a timestamped compliance record retained for seven years. Exportable for regulatory reporting and MAS examination on demand.
Singapore Data Residency
All compliance processing hosted on AWS ap-southeast-1. Your customer transaction data never leaves Singapore. TLS 1.3 in transit, AES-256 at rest.

Four Deployment Tiers

Enquire below to discuss the right tier for your platform and transaction volumes.

RegOS Developer
Up to 1,000 calls/month

For development, integration testing, and proof-of-concept deployments. Full API functionality at development volumes.

Enquire →
RegOS Production
Up to 50,000 calls/month

For MAS-licensed payment institutions and FinTechs in live production. Full compliance coverage, SLA-backed uptime, and monthly audit export.

Enquire →
RegOS Scale
Up to 500,000 calls/month

For established FinTechs and Wealthtech platforms with significant transaction volumes. Dedicated throughput and priority support.

Enquire →
RegOS Enterprise
Unlimited — custom SLA

For large-scale FinTech platforms requiring custom volume, jurisdiction packs, or bespoke compliance logic.

Enquire →

Enquire About Compliance API — RegOS

Tell us about your platform and compliance requirements.

Select…
Select…

Or email info@sidian.sg directly.