Subscriptions, Referrals and Channel Commissions
Monetise a creator-led or signal product with tiered subscriptions, on-chain payment verification, referral rewards, and a channel-partner commission system — without rebuilding the back office for any of them.
Who this is for
| Persona | Typical inbound |
|---|---|
| Signal or alpha service | ”We want a subscription model with influencer commissions baked in.” |
| Creator-led product | ”Tiered subscriptions with a referral programme our power users can actually share.” |
| Information or research platform | ”Trial codes for distribution, paid conversion, and commission tracking on every conversion.” |
| Internal cross-product team | ”Can we extend this stack to a new product line under the same organisation?” |
Not a fit if you need a turnkey card-based SaaS subscription product (Stripe and Paddle do that better), arbitrary lifecycle hooks for a product that does not map to our tier model, or a fully self-service public API surface today.
What you can ship today
The capability is delivered as a custom-deployed module — currently powering our own subscription products and selected partner integrations. The full stack covers:
| Capability | What it includes |
|---|---|
| Subscription lifecycle | User profile, current subscription state, pricing (with optional personalised pricing), on-chain payment verification, tier upgrade pricing, and tier upgrade execution. |
| Tier model | Two tiers today (a standard “pro” tier and a higher “alpha” tier) with an upgrade-cost endpoint between them. Custom tier names and pricing are scoped per partnership. |
| Trial codes | Batch generation, redemption, and revocation. Useful for paid distribution and KOL seeding. |
| Referral rewards | Validate a referral code, query reward summary and detailed breakdown, and claim accumulated rewards. Each user can set a custom alias for their own referral code. |
| Channel-partner commissions | A two-level structure where channel partners onboard their own KOL roster. Subscribers bind to a channel partner via a referral code; the channel partner earns commissions on attributed subscriptions. |
| Administration surface | List users, change a user’s referral role, grant subscriptions, manage trial codes, and manage channel partners and their KOLs. |
How it works
The end-user experience is wallet-signed — a subscriber connects a wallet, signs a session token, and the subscription system uses that token to attribute the user across pricing, referral, payment verification, and commission events. The on-chain payment is verified against an internal payment record before the subscription is activated.
1. Subscriber visits your product, connects a wallet, signs a session token.
2. Your frontend reads pricing for the user
(optionally with a referral code applied for trial eligibility).
3. Subscriber pays on-chain.
4. Backend verifies the on-chain payment, activates the subscription,
credits the referring user (and their channel partner, if any) with
commission accrual.
5. Subscriber can later upgrade tier; the upgrade-cost endpoint computes
the prorated delta and the upgrade endpoint executes it.
6. Channel-partner commission summary and detailed referral breakdown
are queryable at any time.For channel partners onboarding KOLs, an administrative workflow binds a KOL wallet to a channel partner, sets the KOL’s alias and configuration, and optionally grants the KOL an Alpha subscription. The commission attribution then flows through every subscriber bound to that KOL.
Custody model
Subscriptions are paid in crypto. The payment lifecycle is custodial — settled subscription payments and accrued referral and commission balances sit in a KryptoGO-managed account associated with your organisation, with claim flows that send funds to the recipient’s wallet on request. See Custody Options for the full custody catalogue.
Compliance posture
Subscription payments inherit our regulated posture: Taiwan VASP registration, ISO 27001 and ISO 27701 certifications, SOC 2 Type II examined controls, Cure53 audit. Address-level AML risk scoring runs on inbound subscription payments based on configurable per-organisation policy. See Compliance and Certifications for the full picture.
Typical integration timeline
| Phase | Bucket |
|---|---|
| Subscription lifecycle wired into your existing product, with the standard tier model and on-chain payment | One to three months |
| Referral programme and channel-partner commissions added on top | One to three months |
| Custom tier names, pricing model variants, or tailored commission rules | Three to six months |
Timelines assume your product already has a wallet-signed authentication pattern. Adding wallet sign-in for the first time is typically a few additional weeks.
Current scope
- The full stack is in production today inside our own analytics product and is exercised at scale on subscriber, referral, and commission flows.
- The standard tier model is “pro” and “alpha” with a defined upgrade path. Custom tier names, prices, and rules are scoped per partnership.
- A self-service administration dashboard is not part of the standard package — partners typically operate via direct API access or via a custom-built operator surface. A more general administration surface is in design.
- Server-to-server integration without a wallet sign-in is in early access. Talk to us about your authentication model during scoping.
- Region eligibility for subscription payments is confirmed per partnership.
Talk to us
The fastest way to scope a subscription, referral, and channel-partner integration is a 45-minute discovery call. Reach our partnerships team via the address on www.kryptogo.tw .
Where to go next
- On-chain analytics and signals — the analytics surface that subscription products are typically paired with.
- Transaction webhooks — the signed callback contract for payment lifecycle events.
- Accept crypto payments — the underlying payment platform.
- Custody Options — how subscription balances are held and claimed.