Platform Partners

INVO Network supports non-gaming platform partners — video, microdrama, social, creator, and other digital experiences — that want to use INVO as their payment rail and ledger. This page is a high-level overview for partner teams. The technical onboarding contracts are negotiated individually.

Who is this for?

Companies running consumer apps that want a turnkey way to:

  • • Sell a branded in-app currency to their users with real money
  • • Have users spend that currency on items, unlocks, or subscriptions inside the platform
  • • Let users move balances across the broader INVO Network
  • • Cash out the platform's earned revenue to their bank account

Platform status is now self-serve: any KYC-verified developer can claim it for an active game from the Platform & Keys page in the developer dashboard (see below). Negotiated fee splits and custom contracts still start with the contact at the bottom of this page.

Self-serve setup — Platform & Keys

Everything below is done from the Platform & Keys page in the developer dashboard — sign in at console.invo.network (or dev.console.invo.network for sandbox), open the user menu in the top-right corner, and choose Platform & Keys.

  1. 1

    Claim platform status

    Pick your game, then under Platform status choose Video platform, Creator platform, or Social platform and apply. The change is instant — no approval queue. Two requirements: your developer account must be identity-verified (KYC) and the game must be live or testing. Platform tenants are reachable as a transfer destination from every game on the network, so every claim is audited. Choosing Standard game reverts it.

  2. 2

    Get your SDK secret key

    The SDK secret key card lets you reveal and copy your ivsdk_… key, and rotate it at any time. Rotation has a 7-day grace window — the old key keeps working while you cut your integration over. See Partner Credentials & Key Handling for the handling rules.

  3. 3

    Web platforms: turn on passkey step-up

    Under Passkey step-up, submit the domain your sign-in pages run on and prove you control it with a DNS TXT record — the config goes live the moment verification passes. Full walkthrough on Platform Step-Up (WebAuthn / Passkeys).

  4. 4

    Configure your webhook

    The console links straight to the dashboard's Webhooks page for your game — endpoint URL, event selection, signing secret, and delivery history live there. Contract details: Receiving Webhooks.

What Partners Get

Branded currency

You name the currency (e.g., your platform's "Stars," "Tokens," "Credits"). The network rate is fixed at 1 USD = 10 units; the brand is yours.

Hosted checkout

Card data never crosses your servers. Partners are SAQ-A scope. We handle PCI, 3DS, and the dispute lifecycle end-to-end.

Cross-tenant transfers

Your users can move balances between your platform and other tenants on the network. Two flows: self-transfers (same human, two tenants) and player-to-player sends (gifting by phone). SMS PIN on send, claim on receive, settlement happens server-side; you receive an authoritative webhook on every completion.

Outbound webhooks

HMAC-signed deliveries for every state change — purchases, refunds, transfers, payout status. Replay-safe and dedupable on event id.

Transparent revenue split

The default network fee is 10% on each item-purchase transaction (90% to the partner). Per-partner overrides are negotiated as part of the agreement and applied to your tenant configuration.

Programmatic payouts

Request a payout of your accrued revenue at any time via API. We dispatch the bill internally, ACH the funds to your bank, and notify your webhook on every status transition.

Web step-up (passkeys)

Web platforms verify high-value transfers and sends in-browser with a WebAuthn passkey — phishing-resistant, hardware-bound, and user-verified — instead of an SMS code. Hosted on your own origin. Platform Step-Up →

Cross-tenant transfers & sends

Once your partner tenant is provisioned, your users can move their branded-currency balance to and from any other live tenant on the network — same REST API gaming-tier developers use.

Self-transfer

A user moves their own balance from your platform to a destination tenant where they're also a user. Three calls: initiate-transfer → verify-sms (sender PIN) → destination tenant calls claim-transfer with the claim code.

Transfer API docs →

Player-to-player send

Phone-based gifting. Recipient may not exist on Invo yet — they get an SMS with a claim code. Three calls: initiate-send → verify-sms (sender PIN) → recipient tenant calls claim-currency.

Send API docs →

Verify in-browser with passkeys (web platforms)

Web platforms don't have to send an SMS PIN to verify a transfer or send. Once your relying-party domain is configured, users approve a high-value action with a WebAuthn passkey (Touch ID / Windows Hello / a security key) bound to the specific transaction — phishing-resistant and hardware-backed. It's additive: SMS stays as the fallback, and the rest of the lifecycle is unchanged. See Platform Step-Up (WebAuthn / Passkeys).

How transfer fees work for partners

User always pays a 10% network fee on the transfer amount. Default split:

  • • 3.5% to the source tenant
  • • 3.5% to the destination tenant
  • • 3% to Invo (network fee)

Your tenant has a transfer_fee_percentage setting (default 3.5%) that governs your kickback. A negotiated rate above 3.5% is absorbed from Invo's 3% slice — the user-paid total stays at exactly 10%, and the destination tenant's kickback is unaffected. Read the actual numbers from fee_breakdown in the API response and fee_total in the webhook payload — don't recompute client-side.

Transfer policy on your tenant

Three flags Invo admin sets on your tenant during onboarding:

  • • allows_outgoing_transfers — your users can send out
  • • allows_incoming_transfers — other tenants' users can send in
  • • universal_transfers — 'yes' to allow any active tenant; 'no' to whitelist specific ones via linked_game_ids[]

Always call POST /api/transfers/available-destinations first to discover which destinations are reachable from your tenant before showing options to the user — don't hardcode destination ids.

How Partner Integration Works

  1. 1

    Kickoff & agreement

    Initial scoping call, ToS and revenue split agreed, designated technical contact identified on each side.

  2. 2

    Sandbox provisioning

    Register your game in the sandbox dashboard, claim platform status on the Platform & Keys page, and copy your sandbox SDK key from the same page. Configure your webhook receiver URL on the dashboard's Webhooks page — the signing secret is shown once on creation. INVO stands up your branded currency.

  3. 3

    Build against sandbox

    Your engineering team integrates against the same REST API documented elsewhere on this site. Hosted checkout, item purchase, and webhook handling are the same contracts that gaming-tier developers use.

  4. 4

    Soak window

    Run real flows in sandbox for a typical 2–4 week QA window before flipping to production. Reconciliation diffs should match your internal ledger nightly.

  5. 5

    Production cutover

    Repeat the same self-serve setup on the production console (Platform & Keys for the SDK key, Webhooks page for the signing secret). Swap your base URL, run a small live transaction set, and you're live.

Partner Payouts

As your users top up and spend, your tenant accrues revenue (the default 90% partner share on every item purchase, plus any custom rate negotiated in your agreement). You can request a payout at any time:

What you send

  • • Amount in USD (must be ≤ current owed balance)
  • • Contact email for status updates
  • • Destination ACH bank details (sent on each request)
  • • Idempotency key so retries don't double-pay

What happens next

  • • INVO admin reviews the request
  • • On approval, an internal bill is created and ACH'd
  • • Your webhook receives payout.status_changed events at every transition (requested → approved → processing → completed)
  • • Your owed balance decrements by the paid amount

Account numbers are encrypted at rest; only the last four digits ever appear in API responses or webhook payloads.

What's the same as the gaming-tier API

Partners use the same REST API that gaming-tier developers use:

  • Same auth. Single X-Game-Secret-Key header on every server-to-server call.
  • Same hosted checkout. Mint a session, open the URL, listen for the webhook.
  • Same item-purchase flow. POST /api/item-purchases/purchase-item with idempotency-keyed bodies.
  • Same balance reads. Single, batch, and streaming reconciliation endpoints.
  • Same webhook envelope. HMAC signature, retry policy, idempotency on event id.

The technical pages on this site (Authentication, Currency Purchase, Item Purchase, Player Balance) all apply directly. What's different for partners is the business agreement, the branded-currency setup, and the payout flow described above.

Talk to us

Partner onboarding starts with a conversation. Tell us what you're building, the volume you expect, and what shape you'd want the integration to take.

partners@invo.network