XKOVA Docs
Docs / Integrations and Orchestration / Wallet Providers

Wallet Providers

Members hold wallets, and those wallets come from a wallet vendor. XKOVA places every vendor behind one wallet provider interface, so the product code that creates a wallet, reads a balance, or asks a member to sign does not change when the vendor does. The same interface spans non-custodial and custodial models.

The wallet provider interface

A wallet provider is the vendor that creates and holds member wallets. XKOVA does not bind to one. Each vendor sits behind a stable wallet provider interface, and the orchestration layer above it, payments, escrow, treasury, and signing, calls that one interface. This is the model from Integrations and Orchestration applied to wallets: the vendor is an adapter, swapped without touching the product surface.

The wallet vendor surface is configured per tenant on a case by case basis and is not a self-serve API yet. Wallet vendor selection, custodial or non-custodial, is set up with you during onboarding rather than chosen through a public endpoint. Treat the model below as how the platform is wired, not as a configuration you flip on your own today.

Custodial and non-custodial

The interface spans two custody models, and the model is a property of the wallet rather than a different product.

ModelWho controls the key
Non-custodialThe member. They sign in their own wallet; no one else can move their funds.
CustodialA custodian holds keys on the member's behalf under the institution's controls.

XKOVA's money movement is non-custodial by construction: the owner signs an instruction, the XKOVA Relayer submits it and pays gas, and the chain settles. The member's key signs; XKOVA never holds it. See Non-custodial Model for the mechanics and Wallets and Balances for the member wallet surface.

Example vendors

The wallet interface is vendor-agnostic by design, so a provider can be swapped without changing the product surface above it. The Thirdweb in-app wallet is the provider available today; further vendors such as Turnkey and Fireblocks are planned against the same interface. The non-custodial signing model holds regardless of vendor: the member signs typed data in their own wallet and the relayer submits the signed instruction. The vendor determines how the member's wallet is provisioned and how signing is presented, not whether the move is non-custodial.

Related