TypeScript SDK
A production TypeScript / JavaScript SDK covering most of the integration surface: browser, Node, and React Native via WebView. Optional partner-brandable UI components.
Developer platform
Build against the control plane.
One integration covers the whole control plane: accounts, money movement, settlement, reconciliation, policy, and compliance. Versioned APIs, a TypeScript SDK, signed webhooks, a sandbox, and hands-on implementation support. Non-custodial by default. Your data is exportable, and a self-host path is on the roadmap.
The full API reference, OpenAPI spec, and sandbox credentials are shared with partners on engagement. OVAAL is a technology and orchestration platform; regulated services are provided by appropriately authorised customers and third-party providers.
What you build with.
REST API
A versioned REST API with a published OpenAPI specification. Simpler surface area than GraphQL, easier to reason about, tool, and audit.
Webhooks
Signed event delivery with retries and idempotency, so your systems stay in sync with the lifecycle of each instruction.
Sandbox
A sandbox environment to integrate and test against before production, provisioned at the start of an engagement.
Implementation support
A real human on day one. We help scope the integration, review the responsibility split, and work alongside your engineers through to production.
Additional SDKs & self-host
Server-side SDKs beyond TypeScript follow on partner-demand signal; the REST API is feature-complete in the meantime. A self-host path is on the roadmap.
Versioning you can plan around.
- Versioned from day one. The API version is explicit, so an upgrade is never a surprise.
- Deprecation window. A published minimum notice before any breaking change, with both versions running in parallel during the window, you migrate on your own timeline.
- Additive changes (new fields, new capabilities) ship without breaking existing integrations.
- Changelog. Every release is published to partners, so your team always knows what changed and why.
What you can build.
The control plane is addressable as modules. Adopt the ones you need and add the rest later, without re-integrating.
- Accounts & wallets: create and manage programmable accounts for your end-users.
- Money movement & routing: quote, execute, and track deposits, conversions, transfers, and payouts across eligible providers and rails.
- Settlement & reconciliation: follow each instruction from authorisation to receipt as one operational record.
- Policy & automation: define, preview, deploy, and revoke rules that govern who or what can initiate a financial action.
- Risk & compliance: connect KYC, KYB, screening, monitoring, and Travel Rule workflows you operate under your own authorisation.
- Audit & export: export audit-log events and your data for your compliance and finance teams.
Endpoint-level reference, authentication scopes, and event schemas are shared in the full API reference once an engagement is underway, not published openly.
No dead-end.
- Exportable data. Your records (accounts, transaction history, routing and policy configuration, audit logs) export on request as signed data.
- Self-host on the roadmap for partners that need full data residency or air-gapped audit retention. Architecture spec available under NDA.
- Non-custodial by default. End-user funds stay end-user-side and aren't trapped in our infrastructure.
Deliberate scope.
REST + webhooks, not GraphQL
A smaller surface area, better tooling, and an easier audit story. The partners we've scoped have asked for the same.
Gated reference, human on day one
The full API reference, OpenAPI spec, and sandbox credentials are delivered on engagement. It keeps our surface private and puts a person alongside your team from the start.
TypeScript first
The TypeScript SDK covers most of the integration surface. Additional language SDKs follow on partner-demand signal.
Build against OVAAL.
Book an architecture review and we'll map the integration to your stack, agree the responsibility split, and get you sandbox access. Prefer to read first? The integration brief is a one-page PDF covering modules, the responsibility model, and indicative commercials.