SDK Distribution
What we publish openly, what we deliver through partnership, and how to procure each.
SDKs available on the public npm registry
These are installable directly with npm, pnpm, or yarn. Documentation for each is on the linked surface.
| SDK | Purpose | Documentation |
|---|---|---|
@kryptogo/kryptogokit-sdk-react | Embedded React widget for accepting stablecoin payments. Provides a hook (usePayment) and provider components for wallet connection. Includes multi-chain wallet connectors (WalletConnect, MetaMask, Phantom, Tron wallets). | Crypto Payment docs |
@kryptogo/auth | Framework-agnostic OAuth 2.0 client library for “Sign in with KryptoGO” and partner-initiated user provisioning. Works inside any web stack (React, Vue, Angular, vanilla JavaScript). | Get Started |
If you can npm install it, it is in this row. Everything below is delivered through a partnership conversation.
SDKs delivered through partnership
These are not on the public npm registry. They are delivered to partners as pre-built packages alongside an integration agreement, sample apps, and dedicated support.
| SDK | Purpose | Delivery |
|---|---|---|
| Mobile Wallet SDK (Flutter module distributed as native iOS and Android packages) | Embedded into a partner’s native iOS and Android apps via a method-channel bridge. Provides 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. | iOS xcframework via CocoaPods (iOS 14.0+, arm64). Android AAR via Gradle (API 21+, Kotlin 1.8+). Sample apps in Swift / SwiftUI and Kotlin / Compose are provided. |
| Single-page checkout app | A complete hosted checkout app that a partner can deploy under their own domain or use under our domain. | Source-available under partnership terms; deployment guidance provided. |
| Studio control panel | The merchant-facing operations console. Used by the partner’s operations and compliance teams. | Hosted by KryptoGO; partner accounts provisioned during onboarding. White-labelled domain support is available on request. |
If your integration depends on any of these, schedule a partnership conversation and we will scope delivery alongside the rest of the integration.
Documentation surfaces
| Surface | Audience | Link |
|---|---|---|
| Public capability docs (this site) | Prospective partners scoping an integration | The directory you are reading |
| Public API and SDK reference | Engineers integrating against the published SDKs | API Reference and Crypto Payment docs |
| Partner integration documentation | Engineers under an active partnership, with access to non-public SDKs and sample apps | Provided alongside SDK delivery |
| Compliance trust portal | Compliance and procurement teams | trust.kryptogo.com |
| Marketing | General audience | www.kryptogo.tw |
Versioning and release cadence
The publicly-published SDKs follow semantic versioning. Breaking changes are infrequent and accompanied by a migration note in the changelog. Patch and minor releases happen as needed; we do not impose a fixed cadence.
For partnership-delivered SDKs, releases are coordinated with the partner integrating them. We do not push changes that would break a deployed partner integration without prior coordination.
Where to go next
- API Surface — for the capability-level endpoint inventory.
- Architecture Overview — for how the SDKs fit into the wider system.
- For npm package documentation, browse the Crypto Payment docs.
- For partnership SDK delivery, contact our partnerships team via the address on www.kryptogo.tw .