Cowrie Research

stable-genius

4 min read

Stable Genius

  • Name: Stable Genius
  • URL: https://www.stablegenius.co/
  • Category: stablecoin merchant-settlement company / POS-and-checkout operator / bank-payout and webhook-truth control plane
  • Tags: ethereum-ecosystem
  • Summary: Stable Genius belongs in companies/ because the durable dependency is not only a payment-intent API or a QR-code checkout flow. It is a named operator that decides which merchants get onboarded, how KYC/KYB and bank-link approval work, when proxy contracts get deployed, how fee splits and payout schedules are packaged, and which webhook and settlement events merchants treat as operational truth. The useful question is not just how do I accept USDC? but which company controls merchant admission, conversion-to-bank workflow, payout cadence, and the company-run lifecycle shell around those flows?
  • What it does:
    • Onboards merchants through dashboard-based account creation, KYC/KYB, bank-account linking, and deployment of a non-custodial proxy contract that becomes the payment address
    • Operates payment-intent APIs that return payment addresses and EIP-681 QR payloads for POS, app, and online-checkout flows
    • Packages automatic or manual settlement workflow that converts USDC into USD bank payouts while preserving emergency withdrawal paths from the merchant’s onchain proxy contract
    • Exposes merchant, balance, transaction, and settlement state through a private-beta REST API with bearer-token auth, version pinning, pagination, and rate limits
    • Publishes signed webhook events for payment confirmation and settlement lifecycle updates, making Stable Genius part of the merchant’s operational truth layer rather than just a passive QR generator
    • Supports multi-merchant platform integrations where one integrator can process payments for several merchants through a shared API surface
  • Key claims:
    • The docs homepage says Stable Genius enables stablecoin payments with one API call to create a payment and one webhook when it's confirmed, while the merchant gets USD in their bank account, which is unusually direct evidence that the company shell matters as much as the API surface
    • The official site says funds go directly to a wallet only the merchant can access and that Stable Genius never holds, touches, or transfers the merchant’s money, which clarifies the product posture but does not remove the company-run onboarding, bank-link, payout, and webhook boundary
    • The merchant docs say onboarding includes KYC/KYB, Plaid or manual bank linking, and deployment of an onchain proxy contract, which makes merchant admission and account setup explicit operator-controlled choke points
    • The how-it-works and settlement docs say payment intents return EIP-681 QR payloads, confirmation triggers a payment_intent.confirmed webhook, the default payout schedule is weekly Monday 8am EST, and ACH settlement usually lands 1–3 business days after withdrawal initiation, which makes the live operational workflow much more specific than a generic USDC checkout label
    • The merchant docs say the default fee rate is 1% and that fee splitting happens onchain through the merchant proxy contract, which is a useful boundary map: onchain fee visibility exists, but the company still defines the default commercial workflow
    • The webhook-security docs specify X-StableGenius-Signature and X-StableGenius-Timestamp headers, HMAC-SHA256 verification, constant-time comparison, and a 5-minute replay window, which matters because merchants may end up treating Stable Genius webhook events as payment and settlement truth
    • The API overview describes a private-beta API at https://api.stablegenius.co/v1 with sandbox and production keys, reinforcing that access and production usage still sit behind company-issued credentials
  • Whitepaper: No classic standalone company whitepaper is the point here. The clearest primary materials are the official site, docs corpus, merchant and settlement guides, API overview, and webhook-security pages; the broader source bundle remains ../whitepapers/stable-genius-primary-sources-2026-05-02.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • There is not a particularly useful standalone Stable Genius protocol boundary doing the analytical work.
  • The meaningful surface is the named operator that admits merchants, deploys the proxy-contract workflow, links the bank account, schedules cash-out, signs the webhooks, and decides how the easiest production path works.
  • That is why this note belongs in companies/: the practical dependency is a company-run merchant-settlement shell rather than a neutral settlement primitive.

Control surface

  • Practical authority sits in merchant onboarding, KYC/KYB approval, bank-link approval, proxy-contract deployment workflow, default fee configuration, payout cadence, ACH conversion path, API-key issuance, and webhook publication.

  • The sticky dependency is operational memory: once a merchant or platform hardens around Stable Genius payment intents, proxy contracts, bank-linked settlement, and signed lifecycle callbacks, the real lock-in is to the company-run payout and reconciliation shell rather than only to USDC or EIP-681.

  • Read Stable Genius as a company-operated merchant-settlement and payout control plane, not as a neutral payment rail.

  • Last reviewed: 2026-08-10 UTC

Graph View

Backlinks