The Wallet Experience Is Changing—And That’s a Good Thing
Not long ago, creating a wallet meant choosing between clunky browser extensions, fragmented mobile apps, or writing down a 24-word seed phrase on a piece of paper you were bound to lose.
If you're building a modern Web3 product today, that simply won't cut it. Users expect onboarding to be instant, seamless, and secure. Enterprises want compliance, control, and user lifecycle visibility. And developers—well, we want all of the above, without having to duct-tape six libraries together.
That’s why we’ve come to appreciate the flexibility and structure of KS Wallet, part of the Kalp Studio ecosystem. It’s not just a wallet—it’s a wallet system. And in this guide, we’ll show you how to create and connect a wallet across 2 access points:
- Kalp Studio Console
- Embedded Wallet (for dApps)
While all of these work well, we’ll focus more on embedded and custodial experiences—because that’s where most teams are struggling to find the right balance between user experience and backend control.
Prerequisites
Kalp Studio is a decentralised infrastructure platform designed to build, manage, and scale blockchain applications and networks. It serves as a comprehensive ecosystem for developers, offering a wide range of tools and services that simplify the complexities of blockchain technology, making it more accessible and efficient.
Explore it here: https://www.kalp.studio
What’s Different About Wallets in 2025?
Let’s be honest: the wallet UX has held Web3 back. It’s too fragmented for users, too inconsistent for developers, and too risky for enterprise teams to fully trust.
But a few things have shifted:
- Wallets are no longer “just an app”—they’re part of your product’s backend architecture.
- Custodial and embedded flows are gaining traction, especially for real-world use cases.
- Platforms like Kalp Studio now offer wallets as modular components: secure, API-driven, and adaptable to different use cases.
KS Wallet supports self-custody, custodial, and MPC models. This guide focuses primarily on Custodial Wallets and how to get started with them.
Custodial Wallets: Built for Enterprise-Grade Use Cases
KS Wallet’s custodial model gives platforms full control over wallet creation, key storage, and transaction signing—without exposing sensitive details to the frontend.
This is especially powerful when:
- You’re building a SaaS platform
- Your users are non-technical or new to crypto
- You need audit logs, recovery workflows, and KYC integration
How to Use Kalp Studio Console to Create Your Custodial Wallet
1. Log in to Kalp Studio Console
Sign in to your Kalp Studio account and navigate to the Console Dashboard.
https://console.kalp.studio
2. Access the KS Wallet Product
From the list of available products (e.g., Instant Deployer, KS Storage), locate KS Wallet, then click Explore.
3. Initiate Wallet Creation
Click on the "+ Create New Wallet" button.
4. Select Wallet Type — Custodial
You'll be prompted to choose between Self‑Custody, Custodial, or MPC. Select Custodial Wallet and click Continue.
5. Choose Blockchain and Network
Use the dropdown menus to select your target blockchain (e.g., Kalp DLT) and the correct network (Mainnet or Testnet).
6. Pick a Wallet Provider
Choose Kalp Studio as your provider.
7. Complete Wallet Setup
After selecting the provider, click on Continue. When finished, you'll receive a confirmation message and details including the wallet’s public address, and often a small token credit (like “1 GINI”).
8. Verify Wallet Creation
Navigate to the Wallets list in the sidebar. You should now see the newly created custodial wallet with its address and balance.
Why This Matters to You
Whether you're a startup or an enterprise, your wallet setup will affect:
- User conversion rates
- Compliance and audits
- Recovery and support workflows
- Dev time and maintenance overhead
With KS Wallet, you don’t need to choose one rigid model. You can mix and match based on:
- Your user base
- Your security needs
- The maturity of your product
Embedding KS Wallet in Your dApp — Step-by-Step
Embedded Wallets allow you to create and connect wallets inside your dApp—no extensions, downloads, or seed phrases required.
If you’ve ever seen a user bounce off your signup flow because of wallet setup friction, you’ll understand why this matters.
How It Works
The KS Embedded Wallet works by generating a self-custody or custodial wallet in the backend, linked to a user’s device or session. You can configure:
- Wallet type (self-custody or custodial)
- Storage method (session, local storage, backend)
- Key recovery options (e.g., email verification or MPC fallback)
Configuration Steps
1. Sign In to Kalp Studio Console
Log in to your account. You'll land on the main dashboard.
2. Access the KS Wallet Product
Select KS Wallet and click Explore.
3. Navigate to Embedded Wallet Configuration
In the sidebar, click "Embedded Wallet" to open the configuration interface.
4. Explore the Embedded Wallet Panel
You’ll see:
- Module intro
- Left-side customisation options
- Live preview pane
- “View Docs” button for advanced info
5. Configure Social Login Options
- Open the Login Options dropdown
- Select login methods (Google, email, phone, etc.)
6. Customise Theme Appearance
- Use the Theme Color tool to set modal/button background and text color
- The live preview updates automatically
7. Preview the User Experience
Toggle between Modal, Button, and Code views to simulate different UI states.
8. Apply and Save Your Configuration
Click Apply Changes and wait for a success notification.
9. Generate and Retrieve the API Key
Go to Open API in the sidebar to copy your API Auth Key for embedding.
10. Integrate the Wallet into Your App
- Embed the widget snippet and API key in your front-end
- Use React or JS code from the “Code” preview tab
- Test it by authenticating, viewing balances, and triggering on-chain actions
Why Embedded Wallets Matter
Embedded wallets bring major advantages:
- Frictionless onboarding: no extensions or external apps
- Brand-consistent UX: full interface control
- Backend control: support for custodial/MPC setups
- Developer efficiency: everything is configured on one platform
What You Can Do Next
Once set up, you can:
- Manage wallet states with Kalp Wallet APIs
- Build claim/transfer flows
- Add security layers like MPC or verified recovery
Before we Conclude
Wallets aren’t just UI elements anymore—they’re part of your backend strategy. And if you want to build scalable, secure, user-friendly blockchain applications, your wallet layer has to work with you, not against you.
KS Wallet gives you the flexibility to build wallets the way your product works.
Start with embedded or custodial flows to onboard users fast. And do it all from one integrated platform: Kalp Studio.
In the upcoming articles, we will explore two other major KALP STUDIO products: The KALP Instant Deployer and the API Gateway. Until then, stay tuned!