Copperx

  • Name: Copperx
  • URL: https://copperx.io/
  • Category: stablecoin and crypto payments infrastructure / non-custodial checkout and invoicing control plane / developer-first payment gateway
  • Summary: Copperx is a non-custodial crypto payment gateway for businesses and developers. The substance is not the checkout widget. It is the hosted workflow layer around sessions, invoices, subscriptions, webhooks, chain support, and settlement into merchant-controlled wallets.
  • What it does:
    • Lets businesses accept crypto payments directly into their own wallets instead of holding merchant funds in Copperx custody
    • Supports one-time checkout flows, subscriptions, invoices, and recurring invoices through hosted flows and APIs
    • Exposes webhook events so merchants can automate provisioning, billing, reminders, renewals, and other backend actions
    • Provides API-key-based developer access for custom integrations and a dashboard for account, branding, promo-code, and payment configuration
    • Offers no-code or low-code surfaces such as payment links plus integrations for WooCommerce, Zapier, Stripe, BigCommerce, and Magento
    • Supports multiple chains and tokens, with docs and FAQ naming networks such as Solana, Ethereum, Polygon, BNB Smart Chain, Tron, Base, Optimism, and Arbitrum
    • Includes test-mode guidance and API endpoints for creating, retrieving, listing, auto-recovering, and partially completing checkout sessions
  • Key claims:
    • The docs introduction describes Copperx as “a modern, non-custodial crypto payment gateway designed for developers and businesses” and says it accepts payments directly into the merchant’s own wallet while Copperx “never holds custody”
    • The use-cases page positions Copperx for SaaS subscriptions, ecommerce, digital services, donations, event ticketing, developer APIs, and invoicing, which suggests a broad business-payments platform rather than a single checkout button
    • The FAQ says merchants can accept payments across multiple networks including Solana, Ethereum, Polygon, BNB Smart Chain, Tron, Optimism, and Arbitrum; it also highlights instant wallet withdrawals, refund management, tax and promo-code support, payer-paid processing fees, and one-time plus recurring payments
    • The key-concepts page defines Copperx around non-custodial wallet settlement, checkout, invoicing, subscriptions, webhooks, test mode, and supported chains/tokens, reinforcing the control-plane reading
    • The checkout-session reference exposes concrete API operations for session creation, retrieval, listing, auto-recovery by transaction hash, and partial-checkout completion, which is stronger evidence of a real payment API surface than the marketing site alone
    • The authentication page says all API requests require bearer-token authentication managed through the Copperx dashboard
    • The docs llms.txt enumerates a product surface spanning setup, payment configuration, invoices, subscriptions, webhooks, APIs, payment links, and multiple platform integrations
  • Whitepaper: No canonical standalone Copperx whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, llms.txt, FAQ and concept pages, plus the linked API reference and the main site; see ../whitepapers/copperx-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

Control surface

  • Practical authority sits in API-key issuance, supported chains and tokens, checkout-session state, subscription and invoice lifecycle, webhook delivery, refund policy, and dashboard defaults.

  • Non-custodial is real here, but it does not remove operator dependence. The sticky layer is the hosted state machine around merchant billing and settlement.

  • Read Copperx as payment orchestration infrastructure, not as a base settlement rail.

  • Last reviewed: 2026-05-25 UTC