Gnosis Pay

• Name: Gnosis Pay
• URL: https://gnosispay.com/
• Category: stablecoin card-and-wallet control plane / self-custodial spending infrastructure / smart-account payments network
• Tags: ethereum-ecosystem
• Summary: Gnosis Pay is the clearest self-custodial card-and-wallet control plane in this slice. The card is not the point. The point is the Safe-based account stack, delegated spend controls, SIWE sessioning, fiat-rail attachments, and partner APIs that keep meaningful account state visible onchain. Keep this note on that product and account surface; the named operator, issuer, KYC, and partner-composition boundary now lives in gnosis-pay.
• What it does:
  • Lets partners onboard users with SIWE authentication, email registration, terms acceptance, KYC, source-of-funds questionnaires, phone verification, and Safe deployment before card issuance
  • Creates a Safe smart account for each user on Gnosis Chain and uses Zodiac-based Roles and Delay modules to enforce spending limits and transaction controls while preserving user ownership
  • Issues virtual and physical Visa cards through API flows so stablecoin balances can be spent at traditional merchants
  • Exposes account-management endpoints for balances, daily spending limits, withdrawals, authenticated-wallet linking, card lifecycle events, and cashback configuration
  • Supports local fiat connectivity and ramp flows through integrated partners such as Monerium for EUR/IBAN, Noah for USD, and Avenia for BRL, with KYC-sharing support
  • Publishes an OpenAPI-documented HTTP JSON API plus open-source integration assets including a UI starter and the @gnosispay/account-kit SDK for onchain account creation, setup, spending, limit updates, and integrity checks
• Key claims:
  • The official positioning is white-label stablecoin card infrastructure where users keep funds in Safe smart accounts instead of handing balances to a conventional card-program custodian
  • The account docs say each user gets a Safe on Gnosis Chain, with Roles and Delay modules enforcing delegated spend and a queue on non-card actions, which is the real architectural reason this note matters
  • The onboarding flow is heavy and explicit — signup, terms, KYC, source-of-funds checks, phone verification, Safe deployment, configuration checks, then card ordering — which makes the compliance and issuer wrapper impossible to miss
  • The API surface is straightforward: HTTP JSON, OpenAPI docs, JWT auth from SIWE, plus open-source account-kit and UI helpers for account creation, setup, limit changes, and delegated-spend actions
  • The fiat side is still operator-run. Monerium, Noah, and Avenia attach EUR, USD, and BRL paths to the stack, with KYC-sharing and partner-relationship requirements deciding who actually gets those routes
• Whitepaper: No canonical standalone Gnosis Pay whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, docs corpus, OpenAPI/API intro, account and onboarding docs, on/off-ramp documentation, public GitHub org, and the @gnosispay/account-kit README; see ../whitepapers/gnosis-pay-primary-sources-2026-05-02.md.
• Sources:
  • https://gnosispay.com/
  • https://docs.gnosispay.com/
  • https://docs.gnosispay.com/llms.txt
  • https://docs.gnosispay.com/account
  • https://docs.gnosispay.com/onboarding-flow
  • https://docs.gnosispay.com/api-reference/intro
  • https://docs.gnosispay.com/on-off-ramps/index
  • https://github.com/gnosispay
  • https://raw.githubusercontent.com/gnosispay/account-kit/main/README.md
  • https://raw.githubusercontent.com/gnosispay/ui/main/README.md

Internal linkages

• Company / operator boundary for onboarding, issuer packaging, partner composition, and compliance workflow: gnosis-pay.
• Core account substrate: safe.
• Best same-slice contrast: rain.

Protocol / company boundary

• Keep this note on the product shell: Safe-based account mechanics, delegated spend controls, card-ordering flow, account APIs, and the user-visible self-custodial card narrative.
• Use gnosis-pay for the named operator boundary around partner onboarding, issuer relationships, terms acceptance, Sumsub KYC, source-of-funds workflow, and ramp-partner composition.
• That split matters because how does Gnosis Pay's account stack work? and which company controls the legal/compliance and issuer shell around it? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in Safe deployment, delegated spend modules, spending-limit policy, card-ordering and account APIs, and how fiat ramps and local-currency paths attach to the account stack.

• The thicker operator shell around onboarding approval, issuer packaging, KYC sharing, and partner composition now points upward to gnosis-pay.

• That makes this note the clearest account-first anchor in this card-and-wallet slice without flattening the company boundary into the product narrative.

• Last reviewed: 2026-08-08 UTC