Fystack is now ISO/IEC 27001:2022 certified.
NON-CUSTODIAL MPC WALLET

Wallets Your Users Truly Own

A shared-custody MPC model where the user, your backend, and a trusted co-signer each hold a key share. No single party — not even you — can move funds alone.

2-OF-3 THRESHOLD SIGNING
SHARE 1

User Device

Mobile / Browser

SHARE 2

Your Backend

Any cloud or on-prem

SHARE 3

Trusted Co-Signer

Fystack / TEE enclave

Signing Ceremony

Any 2 of 3 shares required — no single party can sign alone

User approves on device
Backend applies policy check
Co-signer attests
Threshold met — transaction signed

No share ever leaves its device. No single party — not even Fystack — can move funds alone.

How it works

True MPC — no seed phrases, no single points of failure

01

Distributed key generation

An MPC ceremony creates three key shares simultaneously. No full private key ever exists in one place — not during generation, not in storage, not during signing.

02

User approves on device

The mobile share is bound to the user's device and unlocked with biometrics or a passcode. The user must consent to every signature.

03

Threshold signing

Any two of the three shares collaborate to produce a valid signature. No share ever leaves its host — they exchange only MPC protocol messages.

04

Refresh & recover

Shares can be rotated (proactive refresh) or regenerated if a device is lost, without ever reconstructing the private key.

Why it matters

The security of self-custody with the UX of a fintech app

True user sovereignty

Users hold a share on their own device. Without their approval, funds cannot move — even if your infrastructure is fully compromised.

No single point of failure

Losing one share doesn't lose the wallet. Compromising one party doesn't compromise the funds. Threshold cryptography by design.

Social & device recovery

Recover access when a user loses their phone with proactive share refresh, no seed phrase, no broken self-custody UX.

Deploy anywhere

Backend share runs on any cloud, on-prem, or edge. Mobile share runs on iOS, Android, or web. Co-signer runs with Fystack, a TEE, or your HSM.

Drop-in SDKs

Native iOS, Android, and JavaScript SDKs handle share storage, MPC protocol messages, and signing — your app just calls sign().

Policy & compliance aware

The backend share enforces spending limits, approval workflows, and AML screening before participating in signing.

SDKs

Native SDKs for every mobile platform

Ship MPC signing on the platforms your users already live on. Each SDK handles share storage, device binding, and protocol messaging — your app just calls sign().

iOS SDK

iOS

Swift / SwiftUI

Android SDK

Android

Kotlin / Java

React Native SDK

React Native

iOS & Android

Flutter SDK

Flutter

Dart

Use cases

Where shared-custody wins

Consumer crypto wallets

Ship a Web3 wallet in your app where users can't lock themselves out and you can't unilaterally move their funds.

Neobanks & fintechs

Offer self-custodial stablecoin accounts with compliance controls, KYC-gated flows, and fraud protection on the backend share.

Embedded Web3 experiences

Add signing to games, social apps, and marketplaces without onboarding users to seed phrases or external wallets.

Institutional co-custody

Let a trader hold one share, the firm hold another, and a compliance provider hold the third — enforcing dual control by cryptography.

Ship a non-custodial wallet your users trust

Talk to our team about integrating Fystack's MPC SDKs into your mobile app, backend, and co-signer infrastructure.

Contact Us
Join our community