A Gnosis Pay user can have multiple authenticated wallets attached to their account.
Authenticated wallets are used to sign in via SIWE and to start new API sessions.
1

Get a JWT token for the session

Follow the authentication flow to obtain a JWT token for the Gnosis Pay user.
2

Add a new wallet address

Make a POST call to this endpoint with the address to add.
curl --request POST \
  --url https://api.gnosispay.com/api/v1/eoa-accounts \
  --header "Authorization: Bearer <token>" \
  --header "Content-Type: application/json" \
  --data '{
    "address": "0x1234567890abcdef1234567890abcdef12345678"
  }'
3

Verify that the wallet was added

Call the list accounts endpoint.
The new address should appear in the response.
curl --request GET \
  --url https://api.gnosispay.com/api/v1/eoa-accounts \
  --header "Authorization: Bearer <token>"
  • Adding an authenticated wallet only links it to a Gnosis Pay user for login and API sessions.
  • An authenticated wallet is not automatically a Safe owner.
  • Only Safe owners (EOAs or smart wallets added to the Safe) can interact with the Delay Module or execute on-chain actions.
  • Authenticated wallets can use the API (e.g. place card orders, fetch user info) but cannot control funds unless also added as Safe owners.