Skip to Content

White-Label Crypto Wallet

Give your users a wallet inside your app, branded as yours, without operating wallet infrastructure or taking on key custody you do not need to.

Who this is for

PersonaTypical inbound
Consumer fintech”We want our users to hold and send crypto without us building wallet infrastructure.”
Neobank or exchange”We need a wallet experience inside our app for our existing customer base.”
Web3 product needing custody”Can our users’ assets sit with you instead of the user holding their own seed?”
Merchant operations team”We need to track an externally-held wallet alongside our managed treasury.”

Not a fit if you need pure user-held self-custody (use External / user-owned instead with our Payment SDK), Bitcoin in custodial treasury today (on roadmap), or a server-side automated treasury with no human approval step (the multi-signature workflow is intentional).

What you can ship today

Three distinct surfaces, often used together:

SurfaceWhat it is
Mobile Wallet SDKEmbedded into your native iOS and Android apps via a method-channel bridge. Per-user wallet provisioning, multi-chain send and receive, in-app swap, fiat on-ramp, optional in-app DApp browser. White-label theming and six-language localisation built in.
Asset Pro custodial backendOperated by KryptoGO on your behalf. Programmatically create transfers from your treasury to a customer wallet via the Studio API. Transfers go through a Maker → Approver → Signer multi-signature workflow. Per-operator daily transfer limits. Comprehensive audit trail.
External-wallet trackingTrack addresses your organisation does not custody — a vendor’s payout address, an exchange wallet — alongside your managed treasury inside Studio.

For consumer fintechs adding crypto for their existing user base, the most common combination is Mobile Wallet SDK for end-user wallets and Asset Pro for the merchant treasury that powers settlement.

Custody model

This use case spans three of the four custody models in Custody Options:

  • End-user wallets use embedded self-custody (Shamir’s-Secret-Sharing shares split across the user’s device, your cloud, and KryptoGO’s cloud).
  • Your treasury uses the custodial model (Asset Pro, with multi-sig).
  • External wallets that you need visibility into but not control over use external custody.

Pick the combination that matches your business model. Most consumer fintechs use all three.

How it works

For end-user wallets, the Mobile Wallet SDK provisions a fresh wallet the first time the user touches a crypto feature in your app. Your existing authentication system signs a JSON Web Token; the SDK exchanges it for a KryptoGO session and provisions the wallet, splitting the seed into three Shamir shares. From the user’s perspective, no signup, no seed phrase, no extra step — just a wallet view branded with your theme. See Solutions: Consumer Fintech Bolt-On for the full walkthrough.

For your treasury, your operations team uses Studio to set daily transfer limits per operator, designate Maker, Approver, and Signer roles, and process transfers under that workflow. Programmatic transfers call our Studio API with an API key.

// minimal Asset Pro transfer const response = await axios.post( 'https://wallet.kryptogo.app/v1/studio/api/asset_pro/transfer', { chain_id: 'arb', contract_address: '0xff970a61a04b1ca14834a43f5de4533ebddb5cc8', amount: '0.01', wallet_address: '0x3fE5aC82B997255b8226abb6aEfd91f405fe2e8e', }, { headers: { 'X-STUDIO-API-KEY': 'your-studio-api-key', 'Content-Type': 'application/json', }, }, );

Submitted transfers enter the multi-sig workflow. They settle on-chain only after an Approver and a Signer have signed off, in line with your configured policy.

Compliance posture

End-user wallets inherit our regulated posture: Taiwan VASP registration, ISO 27001 and ISO 27701 certifications, SOC 2 Type II examined controls, Cure53 audit. Treasury operations under Asset Pro inherit the same posture, plus the multi-signature workflow that finance and compliance teams require for institutional sign-off. See Compliance & Certifications for the full picture.

Chains supported today

SurfaceChains
Mobile Wallet SDK send / receiveEthereum, Arbitrum, Optimism, Base, Polygon, KCC, Ronin, Oasys, Solana, Bitcoin, Tron
Asset Pro custodial treasuryEthereum, Arbitrum, Optimism, Base, Polygon, BNB Smart Chain, Tron
Solana in custodial treasuryOn roadmap
Bitcoin in custodial treasuryOn roadmap

Token coverage on Asset Pro is currently focused on stablecoins (USDC, USDT) and a small set of major assets. Additional asset and chain coverage is added on partnership request.

Typical integration timeline

PhaseBucket
Mobile Wallet SDK integration into iOS and Android appsOne to three months
Asset Pro treasury setup, multi-sig roles, daily limitsOne to three months
External-wallet tracking for vendor and counter-party visibilityUnder one month

For a worked walkthrough applied to a specific archetype, see Solutions: Consumer Fintech Bolt-On.

Current scope

  • White-label theming and over-the-air-updated localisation across six languages (English, Traditional Chinese, Simplified Chinese, Japanese, Korean, Vietnamese) is included.
  • The Mobile SDK supports per-project deployment configurations, so a partner can ship a wallet branded entirely as their own.
  • Stripe-powered fiat on-ramp is integrated. Geographic coverage depends on Stripe’s footprint in your target market.
  • Solana and Bitcoin in custodial treasury are on the roadmap. End-user Mobile Wallet SDK already supports both.
  • A fully white-labelled reseller portal — where you operate a merchant-facing Studio under your own brand for your own sub-merchants — is in design. Talk to us if this is critical to your scenario.

Talk to us

The fastest way to scope a white-label wallet integration is a 45-minute discovery call. Reach our partnerships team via the address on www.kryptogo.tw .

Where to go next

Last updated on