Gnosis Pay primary sources — 2026-05-02

Project status in this pass

• No canonical standalone Gnosis Pay whitepaper or litepaper surfaced.
• The clearest current sources of truth were the official site, docs corpus, account-architecture and onboarding guides, the on/off-ramp integration docs, the OpenAPI-linked API intro, the public GitHub organization, and the @gnosispay/account-kit README.
• The materials consistently frame Gnosis Pay as self-custodial stablecoin card and wallet infrastructure rather than as a simple consumer card or exchange add-on.

Primary-source snapshots

1) Homepage

• URL: https://gnosispay.com/
• Key excerpt:
  • The homepage markets Gnosis Pay as white-label infrastructure to “ship stablecoin card programs in minutes.”
  • It highlights instant card issuance, fiat rails, multi-currency accounts, self-custody through Safe smart accounts, and global merchant acceptance.
  • It also claims local rails such as IBANs, Pix, and US account numbers, plus integrated KYC/AML and compliance positioning.

2) Docs introduction

• URL: https://docs.gnosispay.com/
• Key excerpt:
  • The docs intro says Gnosis Pay is built to help developers and businesses offer card issuance, management, and user experiences through APIs.
  • It frames Gnosis Card as a stablecoin-based Visa debit card and emphasizes self-custody, DeFi protocol integration, cashback, and ramp integrations.
  • This immediately suggests a broader infrastructure layer than a standalone card product.

3) Account architecture

• URL: https://docs.gnosispay.com/account
• Key excerpt:
  • The account docs say every user gets a Gnosis Pay Safe smart-contract wallet on Gnosis Chain and that funds are never held by Gnosis Pay or any third party.
  • They distinguish SIWE-authenticated wallets used for login/API sessions from Safe owners used for ultimate control.
  • They also describe Zodiac-based Roles and Delay modules, including delegated spending rules and a three-minute delay on non-card transactions.

4) Onboarding flow

• URL: https://docs.gnosispay.com/onboarding-flow
• Key excerpt:
  • The onboarding guide walks partners through email signup, terms acceptance, Sumsub KYC, source-of-funds questionnaires, OTP phone verification, Safe deployment, deployment-status checks, and then card issuance.
  • It says country-based currency setup can map UK users to GBPe, Brazil users to USDCe, and other users to EURe by default.
  • The guide also points developers to the open-source Gnosis Pay UI as a reference implementation.

5) API reference intro

• URL: https://docs.gnosispay.com/api-reference/intro
• Key excerpt:
  • The API intro says Gnosis Pay offers an HTTP JSON API backed by an OpenAPI specification at https://api.gnosispay.com/api-docs/spec.json.
  • It also says most endpoints require JWT authentication obtained via Sign-In with Ethereum.
  • This confirms the platform is meant to be integrated as programmable backend infrastructure rather than consumed only through a hosted app.

6) On/off-ramp integrations

• URL: https://docs.gnosispay.com/on-off-ramps/index
• Key excerpt:
  • The on/off-ramp docs describe fiat-to-stablecoin integrations including EUR to EURe via Monerium, USD to USDCe via Noah, and BRL to BRLA via Avenia.
  • They say Gnosis Pay can facilitate KYC sharing through Sumsub, but partners still need direct contractual/API relationships with those providers.
  • This is a strong clue that Gnosis Pay is packaging wallet, card, compliance, and local-rail coordination into one stack.

7) Public GitHub organization

• URL: https://github.com/gnosispay
• Key excerpt:
  • The public GitHub org exposes a docs repo, a UI starter, a SIWE demo app, and account-kit, which is described as containing functions to read and write on-chain Gnosis Pay accounts.
  • The repo mix indicates the company is publishing real developer infrastructure and not only consumer-facing marketing.

8) Account Kit README

• URL: https://raw.githubusercontent.com/gnosispay/account-kit/main/README.md
• Key excerpt:
  • The README says the SDK generates relay-ready transaction payloads for account creation, direct transfer, account setup, queued execution, allowance changes, delegated spend flows, and account integrity queries.
  • It explicitly describes upgrading a 1/1 Safe into a Gnosis Pay account and uses EIP-712 signing and Zodiac module semantics throughout.
  • This makes the self-custodial, programmable-account architecture unusually concrete.

9) UI starter README

• URL: https://raw.githubusercontent.com/gnosispay/ui/main/README.md
• Key excerpt:
  • The UI starter README references partner registration, public secure-elements endpoints, the Gnosis Pay API base URL, and local commands for generating API types.
  • Even though it is brief, it reinforces that Gnosis Pay expects partner teams to build on top of its hosted infrastructure.

Working conclusion

Gnosis Pay is best cataloged as a self-custodial stablecoin card-and-wallet control plane. The decisive evidence in this pass was the repeated combination of Safe smart accounts, Zodiac module-based spending controls, SIWE-authenticated API flows, partner-oriented onboarding and KYC orchestration, local fiat/ramp integrations, and open-source tooling for onchain account operations and UI bootstrapping.