Institutional · Pre-Execution Compliance
🔒 Patent-pending technology

The Guardian SDK

The gap this closes

MAS-regulated institutions are deploying AI agents to autonomously execute financial transactions. No standard compliance layer exists between an AI agent's instruction and the payment rail. Existing compliance tools were designed for humans at keyboards — they cannot intercept, assess, and approve or hold an AI-generated instruction at machine speed, before any money moves.

Pre-execution compliance infrastructure for MAS-regulated banks, digital banks, and financial institutions deploying agentic AI. Guardian SGSV compliance checks before every transaction fires — automatically, at speed, with a permanent record of every decision.

How It Works

Every transaction follows the same path — from AI instruction to compliance decision to permanent record.

Step 1
AI agent fires an instruction
An AI agent generates a transaction instruction — FX settlement, payment routing, or investment execution. It reaches the Guardian SDK integration point.
Step 2
Guardian SDK intercepts
The instruction is intercepted before it touches your payment rail. No transaction proceeds without passing through the compliance engine first.
Step 3
Guardian SGSV runs a full assessment
Guardian SGSV performs a complete compliance assessment against your institution's own policy configuration. Decision issued in milliseconds.
Step 4
Decision: CLEARED or HELD
✓ CLEARED
Transaction proceeds immediately.
⚠ HELD
Queued for compliance review.
Step 5
Permanent audit record written
Every decision is written to an immutable audit log. Tamper-proof. 7-year retention. Exportable. Regulator-ready at any time.
Illustrative sandbox environment — sample data shown for concept demonstration only. Not live transaction data or a production compliance metric.
Guardian SGSV Compliance Dashboard — Sandbox
Guardian SGSV — pre-execution validator
Seven-gate sequential validator — deterministic pre-execution compliance
Straight-Through Rate
96.4%
ALLOW, no escalation
Escalated to Sentry
3.0%
of total volume
Hard Blocked
0.6%
fail-closed
System Uptime
99.98%
rolling 30 days
MAS Regulated
FEAT Aligned
AML/CFT
MAS TRM
AWS Singapore
PDPA
FAST Compatible
SWIFT Compatible
PayNow
TLS 1.3
AES-256
ISO 27001
SFA Member
MAS Regulated
FEAT Aligned
AML/CFT
MAS TRM
AWS Singapore
PDPA
FAST Compatible
SWIFT Compatible
PayNow
TLS 1.3
AES-256
ISO 27001
SFA Member
Why Guardian SDK

Not an In-House Build. Not a Generic Tool.

Two alternatives exist. Neither solves the problem in the time the regulatory obligation requires.

Generic compliance tools weren't built for this
Transaction monitoring systems and sanctions screening engines were designed for human-initiated transactions. They cannot intercept an AI agent's instruction before it reaches the payment rail.
Building in-house takes longer than your obligations allow
A purpose-built pre-execution compliance engine requires compliance architecture expertise, MAS regulatory alignment, and production-grade millisecond latency. Most institutions estimate 12–24 months for an in-house build.
Guardian SDK is purpose-built and available now
Guardian SGSV was designed from the ground up for one specific problem: running a complete compliance assessment on an AI agent's transaction instruction before any money moves. Patent-pending, MAS-aligned, available today.
MAS Examination

When MAS asks for your AI transaction records

Without Guardian SDK
No system exists between the AI agent and the payment rail to generate a per-transaction compliance record. The institution cannot produce what MAS is requesting — because the records were never created at the point of execution.
With Guardian SDK
Every AI-initiated transaction has a timestamped compliance record — decision, reason code, data evaluated, and outcome — generated at the point of execution. The institution exports the archive and the examiner's request is answered in minutes.
Regulatory Context

The MAS Requirements Guardian SDK Addresses

MAS FEAT — Accountability
Explainability & Audit
What MAS requires
AI systems used in financial decisions must be explainable. Institutions must demonstrate that AI-driven decisions were made for identifiable, auditable reasons.
How Guardian SDK satisfies it
Guardian SGSV issues every compliance decision with full context and reason code. Every decision is logged with the rule applied, the data evaluated, and the outcome.
MAS AML/CFT Notice
Transaction Record-Keeping
What MAS requires
Financial institutions must conduct AML/CFT checks on transactions and maintain complete, retrievable records — including the compliance assessment that preceded each transaction.
How Guardian SDK satisfies it
Guardian SDK intercepts and assesses every transaction before execution. Every decision is written to an immutable 7-year audit log — exportable for MAS examination at any time.
MAS TRM Guidelines
AI System Controls
What MAS requires
AI systems in production financial environments must have robust controls, defined escalation paths, and full audit capability for AI-influenced decisions.
How Guardian SDK satisfies it
The Guardian SDK sits between the AI and the payment rail, enforcing your institution's own compliance policy and providing a complete audit trail for every AI-influenced transaction.

Built for Institutions. Engineered for Scale.

Complete Pre-Execution Coverage
Every AI-generated transaction instruction passes through Guardian SGSV before it reaches your payment infrastructure.
Millisecond Clearance
Compliant transactions are cleared and released in under 100ms. No latency impact on transaction throughput.
Three Integration Paths
REST API, native SDK (Python, Java, Node.js), or API gateway proxy for legacy environments.
Compliance Hold Queue
Non-compliant instructions are held with full context for your compliance team. Every action recorded and timestamped.
7-Year Immutable Audit Records
Every transaction generates a tamper-proof compliance record retained for seven years. Exportable on demand.

Three Institutional Tiers

Enquire below to discuss the right tier for your institution.

Guardian Standard

For Tier-1 international banks and major payment network operators. Full Guardian SGSV compliance, configurable to institutional policy. 99.9% uptime SLA.

Enquire →
Guardian Enterprise

For global custodians and major banking groups requiring higher volume, active-active resilience, and dedicated account management. 99.99% uptime SLA.

Enquire →
Guardian Global

For global payment networks operating across multiple regulatory jurisdictions with bespoke compliance architecture requirements.

Enquire →
Complete the picture

Guardian SDK handles compliance before execution.
Sidian Sentry handles everything after.

Together they provide full-spectrum coverage — no gap between pre-execution validation and post-execution monitoring.

What Getting Started Looks Like

Most institutions complete their initial integration within two weeks.

Typical Integration Timeline
Days 1–3
MSA and DPA signed. Sandbox credentials provisioned immediately.
Week 2
Integration engineering begins. REST API, native SDK, or API gateway proxy.
Weeks 3–4
Compliance team onboarding. Policy configuration and hold queue setup.
Go-live
Guardian SGSV in production. Every AI-generated transaction assessed before it fires.
Founding Partner Programme — Now Open
Sidian is currently onboarding its first institutional partners. Access includes sandbox credentials, integration documentation, and direct engineering support.
Enquire about access →
MAS AIDA Grant Applicant
Active engagement with MAS on AI governance for financial services
OCBC Emerging Enterprise Award
Submitted and currently under review
Singapore FinTech Association
Member

Enquire About The Guardian SDK

Tell us about your institution and compliance requirements.

Select…
Select…

Or email info@sidian.sg directly.