Introducing embedded wallets
We're finally introducing you to MatchID's embedded wallets. Check out the overview section under the security chapter of the docs to get started.
Welcome
MatchID builds user onboarding and embedded wallet infrastructure to enable better products built on crypto rails. This means embedding asset control within applications themselves to enable users, businesses, or machines to use digital assets through seamless product experiences.
Use MatchID's client-side SDKs to authenticate users, provide embedded wallets for them, and prompt wallet usage.
Create an account
Get API keys and start
your integration in our dashboard
Try our user dashboard
Sign-in to our user dashboard to see
MatchID in action
Join our Telegram
Share your innovation
and get support from MatchID
Join our Discord
Stay up to date
with latest releases and have fun
Using MatchID
Broadly, MatchID enables:
- User Onboarding—MatchID helps developers onboard users regardless of their experience with crypto-based systems. This means libraries to authenticate them, help them connect their existing wallets, and provision embedded wallets for them if they don't already have one.
- Wallet Infrastructure—Developers can also directly access MatchID’s bare-metal wallet APIs from our APIs using MatchID API SDK to provision and manage cross-chain wallets for any use case.
Embedded-wallet custody depends on the recovery mode used when the wallet was created. Base-generated recovery accounts are vendor-custodial: the key-share vendor holds enough material to sign without the user. Passcode recovery accounts are co-custodial: the vendor needs the passcode, but holds material that can be tested against passcode guesses offline. In both modes, moving assets to a new user-controlled account is the only way to remove that dependency. These legacy flows use secret sharing; they are not multi-party computation and must not be described as self-custodial.
Explore by SDK
Engineering Principles
At MatchID, we believe technical decisions are moral decisions. Below are the principles that guide our engineering decisions.
Secure
Nothing is more important than your user's security. Current embedded-wallet accounts depend on a third-party key-share vendor. Base-generated recovery is vendor-custodial; passcode recovery is co-custodial and its security depends on passcode strength. Your application does not receive the full private key through the SDK. MatchID does not call these legacy modes self-custodial or MPC.
Flexible
MatchID provides SDK and API access to authentication and wallet capabilities. Applications should request only the user data and wallet actions their product needs, with explicit user authorization for sensitive operations.
Easy to Use
MatchID provides SDK UI components for supported authentication and wallet flows. Check the feature matrix for current support; customization and white-label capabilities vary by surface.
Portable
MatchID supports linking several external-wallet ecosystems and provisioning wallets on documented networks. Chain support differs by login, wallet, and signing feature; verify the feature matrix instead of assuming universal support.
With layers of customizability, MatchID supports a wide range of product experiences.