Pillar 03 · Built by Orokii
Stablecoin wallets for apps that aren't supposed to be a bank.
A Go SDK for non-custodial stablecoin wallets — built for the creator economy, gaming, gig payouts, and e-commerce. Four chains in production. Your end users hold the keys. Orokii stays out of the regulated chain.
Where the market is
Plenty of wallet SDKs for crypto-native apps. Fewer for apps that aren't.
Established
Privy, Magic, Web3Auth, Dynamic, Turnkey. Well-funded, strong on DeFi UX, social-login embedded wallets. Mostly built for crypto-first audiences.
Underserved
Non-crypto-native apps — creators, games, gig platforms, e-commerce — that want stablecoin rails without becoming a bank, and that need compliance plumbing pre-wired.
Where we sit
A Go SDK with the bundled identity + AML cross-sell via KoraStratum. Non-custodial-only by design so neither you nor we end up in the regulated chain unintentionally.
What's included
Production chain code. Compliance hooks. Operational telemetry.
Multi-chain support
Polygon, Ethereum, TRON, and Stellar out of the box — about 3.6k LOC of chain code in production today across Stratum, Sikama, and LuckyCat. Polygon is the practical default for stablecoin throughput.
Production · 4 chains live
Non-custodial key handling
KMS envelope encryption patterns from the Orokii blockchain stack. Customer or end-user holds the keys — Orokii never has access. Crosses MSB triggers stay out of scope by design.
Production patterns
Deposit detection and sweeping
Per-chain listeners detect inbound deposits and surface them to the application layer in near real time. Sweep logic for moving funds to operational wallets is configurable per chain.
Production
Stablecoin onramp adapters
Plug-in adapters for fiat-to-stablecoin onramp (when the customer needs it). The customer brings its own onramp provider relationship; the SDK normalizes the integration.
Adapter pattern · per-partner
Compliance hooks
Optional KYC integration via Kora IDV cross-sell. Optional sanctions screening on counterparty addresses via Kora Compliance. Both off by default; on when your domain needs them.
Optional · cross-sell
Operational telemetry
Structured logs and metrics for transaction status, wallet balances, and sweep operations. Drop into your existing observability stack.
Production
Who we work with
Apps that want stablecoin rails without becoming a payments company.
Creator-economy platforms
Royalty and revenue-share payouts to creators in stablecoins. Bypass the legacy ACH-only payout latency and the per-payout fee structure.
Gaming and metaverse apps
In-app stablecoin balances tied to gameplay, marketplaces, and out-of-game cashout. Non-custodial keeps the platform off the MSB hook.
Gig-economy payout platforms
Domestic same-day payouts in stablecoin. (Cross-border B2B payouts cross into regulated territory — out of scope for this SDK.)
How we work together
You ship the app. We ship the SDK.
You bring
- Your application and identity stack
- Your end-users (whose keys they themselves control)
- Your fiat onramp or offramp provider relationship (Bridge, MoonPay, Transak, or other)
- Your hosting — the SDK runs in your service
- Compliance posture appropriate to your jurisdiction (Orokii is not in the regulated chain)
We bring
- The Go SDK — chain integrations, KMS-envelope patterns, deposit listeners, sweepers
- Reference integration sample app
- Production-tested code from the Stratum / Sikama / LuckyCat wallet stack
- Optional Kora IDV and Kora Compliance cross-sell when KYC or sanctions matter to your domain
- Versioned SDK releases with security patching
Commercial model
Per-deployment license. No per-transaction fees.
Starter
$25k
per year · one chain · standard support
Single-chain deployment. Email support, business-hours SLA. Ideal for pilots and early-stage apps.
Growth
$75k
per year · multi-chain · priority support
Multi-chain, faster patch cadence, priority support. The common shape for production apps with real volume.
Scale
Custom
multi-chain · 24/7 on-call · custom adapters
24/7 on-call coverage, custom chain or onramp adapters, joint roadmap input. Talk to us.
Deliberately no per-transaction fees — transaction-based pricing can characterize Orokii as a payments participant, which we structurally avoid. License-only model keeps the relationship clean.
Frequently asked
What partners ask before signing.
Why non-custodial only?
Custodial wallet operation triggers Money Services Business registration in most US states and similar regimes elsewhere. Operating a custodial wallet for customers would make Orokii a regulated party in your business — the exact thing we are structurally avoiding. The SDK is non-custodial because that lets us ship pure software without becoming part of your regulatory chain.
Can we add custodial mode later?
For your own platform, yes — you can build a custodial layer on top of the SDK. Orokii will not operate custody on your behalf, regardless of structure. The SDK and our managed services intentionally stop at the non-custodial line.
Why not use Privy, Magic, Web3Auth, Dynamic, or Turnkey?
For consumer-crypto-native onboarding (social login, embedded wallets for DeFi UX), the named SDKs are well-funded and have developer mindshare. The Orokii angle is the bundled identity + AML cross-sell via KoraStratum, which the pure key-management SDKs do not offer. Pick Orokii when you need compliance plumbing in the same engagement.
What about Solana? Bitcoin?
Not in the production chain set today. Adding Solana is a tractable port of the existing patterns — scope it in the engagement. Bitcoin is structurally different (UTXO model, no native stablecoins) and is not on our near-term roadmap.
What are the SLAs?
The SDK is a versioned library — SLAs apply to the support contract, not the library binary. Standard tier: response within one business day. Higher tiers available for production-critical integrations. Discussed during scoping.
Where does the SDK actually live?
In your service. The library imports into your Go application; the runtime is yours. There is no Orokii-hosted control plane for this product, and no customer data ever crosses Orokii infrastructure.
Ready to evaluate?
A 30-minute scoping call covers your domain, your chain preference, your onramp provider, and rough integration timeline. No deck, no sales process.