gnosis-pay

Gnosis Pay Co Ltd

• Name: Gnosis Pay Co Ltd
• URL: https://gnosispay.com/
• Category: stablecoin card-program company / self-custodial payments operator / issuer-and-compliance orchestration company
• Tags: ethereum-ecosystem
• Summary: Gnosis Pay clears the bar for a company note because the practical control surface is not just a Safe-based self-custodial card exists. A named operator packages partner onboarding, terms acceptance, Sumsub KYC, source-of-funds workflow, Safe deployment, card lifecycle APIs, fiat-rail attachments, and issuer relationships into one production shell. The product note remains useful for the account and card mechanics; this note is for the legal and operating perimeter that decides who gets in, which partners are attached, and what compliance and settlement path downstream apps inherit.
• What it does:
  • Operates the Gnosis Pay card-program and account stack marketed to wallets, neobanks, exchanges, and payment processors as a white-label stablecoin card and fiat-rails platform
  • Packages user registration, partner-specific onboarding, terms acceptance, Sumsub KYC, source-of-funds questions, Safe deployment, and card ordering into one API-facing workflow
  • Exposes account, card, cashback, IBAN, and ramp-integration APIs while keeping the surrounding issuer, compliance, and support shell under one operator boundary
  • Uses Safe smart accounts as the self-custodial account substrate while still running the app-facing session, approval, eligibility, and card-program machinery above that substrate
  • Connects external providers such as Monavate for card issuance, Sumsub for identity verification, and Noah / Monerium / Avenia for local fiat corridors and ramp attachments
• Key claims:
  • The public site now frames Gnosis Pay as white-label infrastructure for instant card issuance, fiat rails, and multi-currency accounts rather than only as a branded wallet card product
  • The homepage footer identifies the operator as Gnosis Pay Co Ltd, UK company number 14919639, and says the debit card is issued by Monavate Limited pursuant to licence by VISA Europe Limited; that is the clearest signal that the useful boundary here is a named operating company plus issuer stack, not only a product surface
  • The site markets one API spanning Safe smart accounts, authorization engine, currency conversion, settlement, reconciliation, KYC/AML, fraud controls, and local fiat integrations, which is exactly the kind of bundled operating shell that belongs in companies/
  • The onboarding docs make the operator role explicit: users are registered with a partner-specific partnerId, must accept Gnosis Pay and partner terms, complete Sumsub KYC, answer source-of-funds questions, and only then can move toward card ordering
  • The terms mapping in the onboarding docs includes general-tos, card-monavate-tos, cashback-tos, and privacy-policy, which shows issuer and partner dependencies are first-class parts of the production workflow rather than background vendors
  • The on/off-ramp docs say wallets or platforms must establish direct contractual relationships with providers like Noah, Monerium, and Avenia, while Gnosis Pay facilitates KYC sharing via Sumsub and requires use of the Sumsub instance for these integrations; that makes Gnosis Pay a routing-and-compliance orchestrator even where it is not the direct fiat counterparty
• Whitepaper: No separate company whitepaper is the point here. The strongest primary materials for this pass were the public site, onboarding docs, ramp docs, and the source capture in ../whitepapers/gnosis-pay-company-primary-sources-2026-08-08.md.
• Sources:
  • https://gnosispay.com/
  • https://docs.gnosispay.com/onboarding-flow
  • https://docs.gnosispay.com/on-off-ramps/index
  • https://docs.gnosispay.com/llms.txt
  • ../whitepapers/gnosis-pay-company-primary-sources-2026-08-08.md

Internal linkages

• Product-layer note: gnosis-pay.
• Core account substrate beneath the company shell: safe.
• Useful same-slice company comparisons: rain, monerium, and crossmint.

Protocol / company boundary

• Keep gnosis-pay focused on the product surface: Safe-based account mechanics, delegated spend controls, account APIs, card ordering, and the user-visible self-custodial card narrative.
• Keep this note focused on Gnosis Pay Co Ltd as the named operator that packages onboarding, legal terms, KYC and source-of-funds workflow, issuer relationships, ramp-partner composition, and the broader settlement/compliance shell around those product APIs.
• That split matters because how does the account-and-card stack work? and which company controls admission, issuer packaging, KYC sharing, and partner composition? are related but not identical questions.

Control surface

• Practical leverage sits in partner admission, partnerId issuance, terms and policy changes, KYC and source-of-funds workflow, card eligibility, issuer attachments, fiat-corridor composition, and which downstream providers a wallet or platform must contract with to make the stack work end to end.

• The Safe account keeps meaningful balance state onchain, but the company still decides who reaches that account shell, which legal and compliance steps become mandatory, what card and IBAN features appear, and which local ramp paths feel native.

• Read Gnosis Pay Co Ltd as the named self-custodial-payments operating shell around the product, not as a neutral card protocol.

• Last reviewed: 2026-08-08 UTC