Gnosis Pay’s on-chain infrastructure is built on top of the Safe protocol, providing a secure and programmable foundation for digital payments. Each user receives a unique Safe account that acts as their on-chain wallet, with additional modules that enable spending limits, time delays, and delegated spending capabilities.Documentation Index
Fetch the complete documentation index at: https://gnosispay-feat-v2-auth-module.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Architecture Overview
The Gnosis Pay Safe consists of a core Safe account with three main modules:- Core Safe Account: The base Safe wallet that holds funds and processes transactions
- Delay Module: Controls transaction timing and provides security delays
- Roles Module: Manages spending permissions and allowance limits
V2 Architecture Changes
Gnosis Pay V2 maintains the same Safe wallet structure with delay and roles modules, but implements key behavioral improvements:Instant Withdrawals
Withdrawals from the Gnosis Pay Safe reduce the spendable balance immediately to avoid double spending and then sync with the on-chain balance. During this process, the card is not blocked from operations.Multi-Currency Support
The Roles module now supports multi-token configurations so that users can spend different currencies via their spending safe.Module Configurations:
Delay Module Settings
- Transaction delay: 25 hours
- Transaction expiration: 31 hours
Daily Spending Limits
The maximum daily card spend limit is $10K per token. The Roles module enforces a hardcoded on-chain limit of $20K per token, twice the card limit. This buffer exists because card clearing and settlement can take 1–4 days after a transaction, and the higher on-chain limit ensures uninterrupted card operations over that window without requiring any additional user signatures.Account details for authenticated user
To get authenticated user account details, callGET /user/account
- Sandbox
- Production
Account balances for authenticated user
Gnosis Pay V2 provides detailed balance breakdowns to give users complete visibility into their fund status. The authenticated user’s account displays four distinct balance types:| Balance Type | Description | Increases When | Decreases When |
|---|---|---|---|
| Spendable | Amount available for immediate spending via card transactions or withdrawals | • Deposits clear AML analysis • Refunds are processed • Returns of goods are credited | • Card transactions are authorized • Withdrawals are initiated |
| Non-Spendable | Funds that cannot be used for spending. Flagged for review or potential return | • Dependent on AML checks | • Funds are returned to source • Funds are manually released after review |
| Processing Deposits | Incoming deposits currently undergoing AML analysis. Not yet available for spending | • New deposit is received | • AML analysis completes (moves to spendable or non-spendable) |
| Processing Withdrawals | Outgoing withdrawals currently being processed. Deducted from spendable but not yet settled on-chain | • Withdrawal is initiated | • Withdrawal settles on-chain |
Get Account Balances
To request the account balance of the user, callGET /user/balances/v2
- Sandbox
- Production
Each currency maintains its own separate balance states. For example, USDC and USDT will each have their own spendable, non-spendable, processing deposits, and processing withdrawals amounts.