Overview
The daily spending limit update process involves the following steps:- Fetch EIP-712 Typed Data - Get the EIP-712 typed data for wallet signing
- Sign and Submit - Sign the EIP-712 data and submit the update
- Monitor Update - Wait for the delay relay to process the change and check the new limit
- The signing wallet must be one of the Gnosis Pay Safe signers (EOA or smart contract wallet)
- For smart contract wallets, signatures are verified using ERC-1271 standard
- Updates are processed after a 3-minute delay as transactions are going through the Gnosis Pay delay relay
Daily Limit Update Process
1
Fetch EIP-712 Typed Data for Signing
Get the EIP-712 typed data that needs to be signed by the user’s wallet:The response contains EIP-712 typed data with
cURL
domain
, types
, primaryType
, and message
fields that need to be signed by the user’s wallet using the EIP-712 standard.2
Sign and Submit EIP-712 Data
Safe Activation Required: This step only works when the Gnosis Pay Safe account has been fully activated and its modules are deployed. If you receive an error during submission, ensure that the Safe account activation process has been completed first.For more information about Safe account setup and module deployment, see the Safe Management API documentation.
Wallet Requirements:
- The wallet must be a signer of the Gnosis Pay Safe account
- For EOA wallets: Standard EIP-712 signature is used
- For smart contract wallets: ERC-1271 signature verification is used, and you must include the
smartWalletAddress
field in the request body
cURL
3
Monitor the Transaction Execution
The daily limit change is processed through a delay relay mechanism that executes after 3 minutes.You can monitor the transaction status using the delay-relay monitoring endpoint
or by checking your Safe’s transaction history.Additionally, you can also poll the following endpoint to check when the new limit becomes active:
cURL