Solution Compliance is the protocol, not a feature.

Every other system treats compliance as a gate you pass before or after a transaction — screen, then send. The decision and the settlement are separate systems connected by API calls and hope. Frame makes them one thing: the compliance attestation is part of the settlement itself. If the attestation is missing, invalid, or expired, the transaction doesn't get flagged for review later — it reverts.

Frame custody: None
Compliance: Enforced
Every settlement: Verifiable

One API Complete payment orchestration.

The traditional approach means stitching together five to ten vendors and owning the integration risk yourself. Frame collapses the entire stack behind a single API.

The traditional approach

Integrate 5–10 vendors separately
Piece together KYC, custody, and payments
Build reconciliation yourself
Run manual compliance workflows
Months of development time

With Frame

A single API integration
The complete stack included
An automated reconciliation engine
Built-in AML and sanctions screening
2–4 week implementation

The reality for your team Six to nine months, or a few weeks.

Most platforms spend 6–9 months integrating separate vendors — each with different APIs, SLAs, pricing models, and compliance requirements. Frame consolidates all of it into one integration. Your team codes against one API, manages one relationship, and ships payment capabilities in weeks, not quarters.

KYC: Onfido / Jumio
Custody: Fireblocks / BitGo
Payments: Circle / Paxos
Compliance: Chainalysis / Elliptic
Reconciliation: Build internally

Policy sovereignty Your rules. Your keys. Invisible to us.

Every other compliance vendor sees your rules — the thresholds, the lists, the policy configuration. Frame cannot. Your policies are encrypted with your own key and evaluated inside a hardware-isolated enclave. The only thing that leaves is a signed decision. Your compliance logic never does.

01
You hold the key

Your compliance policy is encrypted with your own KMS key and stored encrypted at rest. Frame never holds the plaintext.
02
The enclave decides

A hardware-isolated enclave (AWS Nitro) decrypts the policy, evaluates it against the transaction, and signs the result. Nothing else can read inside it.
03
Only the decision leaves

The signed attestation is the enclave's only output. Update a sanctions list or a threshold and it takes effect immediately — no vendor deployment, no propagation delay.

Three ways to deploy Issue it, custody it, or verify it.

The three things an institution can do with a stablecoin map to three ways to run Frame — unified by one identity registry and one attestation pipeline underneath.

Issuer

Issue a branded stablecoin where every mint, burn, and transfer is attestation-gated. You hold the reserves and the keys; Frame enforces compliance at the token level.

Custodian

Custody third-party stablecoins — any ERC-20 — with every deposit, withdrawal, and transfer gated by your own policy. Prove sovereign compliance over assets you don't issue.

Compliance Gateway

Keep your existing tokens, chains, and custody. Add provable compliance as an API-first layer — screened and enforced, not just logged.

Capabilities

Solutions

Complete orchestration capabilities

Frame Orchestration operates under comprehensive regulatory frameworks.

Regulatory Compliance

SOC 2 Type II: Certification in progress, scheduled completion Q2 2026
GDPR compliant: EU operations currently operational
PCI DSS standards: Alignment in progress
ISO 27001: Information security certification in progress

Built-In Compliance

Frame is infrastructure, not a bank — it never custodies funds or issues stablecoins
Regulated activities stay with the institution, under its own licences
Compliance enforced on every transaction, not checked after the fact

Integration paths

Choose your implementation model.

Standard API Integration

Best for: SaaS platforms, marketplaces, fintechs
Full orchestration capabilities via REST API
Sandbox access for testing
Complete developer documentation
2–4 week implementation
Production support included

White-Label Integration

Best for: Your brand
Customisable UI components
Co-marketing arrangement
Revenue share available

Developer experience

Frame Orchestration is designed for developers who want powerful capabilities without complex integration.

Developer Tools

REST API and webhooks
OpenAPI 3.0 spec
SDKs for major languages (Node, Python, Java, Go — available at launch)
CLI and dev container for local sandboxing

Typical Integration Timeline

Week 1: Sandbox auth and first call
Week 2: Settlement and reconciliation wired
Week 3: Compliance review and dry-run
Week 4: Production go-live

Compliance & security

Frame Orchestration operates under comprehensive regulatory frameworks.

Regulatory Compliance

SOC 2 Type II: Certification in progress, scheduled completion Q2 2026
GDPR compliant: EU operations currently operational
PCI DSS standards: Alignment in progress
ISO 27001: Information security certification in progress

Built-In Compliance

Frame is infrastructure, not a bank — it never custodies funds or issues stablecoins
Regulated activities stay with the institution, under its own licences
Compliance enforced on every transaction, not checked after the fact

Economics

You capture the spread. Frame charges for the infrastructure.

Where the value stays

You set the price your clients see
You capture the FX spread on every settlement
Frame charges a flat infrastructure cost basis
No custody, so no custody risk priced in

The structural advantage

Routing over the Verus protocol drives transaction cost toward ~$0.01
0% FX spread on protocol-native settlement
Finality in roughly one minute where rails permit
Traditional rails remain available when required

Ready to orchestrate?

Whether you’re a bank adding stablecoin services, a PSP expanding capabilities, or an ERP embedding payments, Frame Orchestration Platform gives you institutional infrastructure with developer-friendly integration.