XKOVA Docs
XKOVA Documentation
XKOVA is digital asset management for regulated institutions. Two first-class products, XKOVA SPS (the Stablecoin Payment System) and XKOVA TAMS (the Tokenized Asset Management System), sit on an orchestration layer that plugs into the vendors you already trust. It is non-custodial by construction, API first, and ships with an operator console and member facing apps. This portal is built for both people and AI coding agents.
Two products
Both products run on the same non-custodial pattern: the asset owner signs, the XKOVA Relayer submits, and the chain settles.
XKOVA SPS
The Stablecoin Payment System. Move stablecoin value: payments, escrow and claims, treasury, settlement, and off-ramp.
XKOVA TAMS
The Tokenized Asset Management System. Issue and manage digital assets: programmable tokens, real-world assets, cap tables, distributions, and corporate actions.
On an open orchestration layer
XKOVA owns the orchestration: policy, ledger, audit trail, member identity, and settlement state. Every vendor connection is a swappable adapter, so an institution plugs in the providers it already trusts and is never locked into one stack. Closed competitors bundle wallets, networks, compliance, and ramps from a single provider, so switching means rebuilding.
Core Banking
Symitar, Corelation, Fiserv, and other cores, through the integration gateway.
Screening
BSA and KYT through Chainalysis, TRM, Elliptic, and others.
Identity
KYC and KYB through Persona, Alloy, Onfido, and others.
Conversion and Ramps
Fiat to digital through Coinbase, Paxos, Anchorage, and others.
Wallet Providers
Custodial and non-custodial vendors, configured per tenant.
Browse by area
Quickstart
Make your first authenticated sandbox call and reach a confirmed payment.
Platform Overview
The pillars, the orchestration layer, the non-custodial model, tenants and networks.
API Reference
Every operation, generated from the contract, plus a live try it console.
Developer Guide
Authentication, authorization, idempotency, pagination, errors, rate limits, webhooks.
Built for people and agents
Every page exposes a Copy page for LLM action, and the portal publishes an llms.txt index so AI coding agents can discover and read the documentation directly. The reference is generated from the OpenAPI contract, so it never drifts from the running system.
Try the demos
Two hosted demo surfaces show the same rails from both sides. The Plover operator console is the workspace console signed in to the shared Plover Credit Union demo tenant, where staff manage payments, treasury, and compliance. The Plover member app is the customer facing front end where members hold balances and send money. See Try the Demos for how to enter both from the console.