AgentPay Market
Docs

Account

Addresses and Wallet connections

Choose the right address and understand what each connection permits.

Which address belongs where?

  • Safe account address: holds purchase funds. Its address alone does not prove control.
  • Safe owner address: administers the Safe. It is not the Safe account address.
  • Wallet execution address: the local Session Key address used as the Policy delegate. Read it from Wallet; do not substitute the owner address.

Set up local Wallet

Open Settings → Wallet → Wallet setup for installation and configuration. Market Wallet connections are separate from local Wallet setup and payment authorization.

Connect your local Wallet

From the User folder, run ./run market connect. Sign in, choose a nickname such as Work PC, and confirm the account and Safe. This connects Orders under that Wallet’s Policy without another Safe owner signature. Each computer keeps its own key; Market does not synchronize keys. Copied keys using the same Policy represent one authorization, regardless of nickname.

Manage these connections in Settings → Wallet. They show spending and allow Order support only under that Wallet’s Policy. They grant no spending or receipt-confirmation permission. An existing connection can support its Orders after spending expiry; revocation blocks new requests through it. New Policies do not automatically inherit access to old Orders.

Purchase restrictions

A restriction on your Buyer Safe prevents new Orders through every Wallet using that Safe. It does not freeze funds, revoke your spending permission or stop support for existing Orders. Disconnecting or renaming a Wallet does not remove it. Contact support if you need it reviewed. After removal, normal Policy and service checks still apply. Status may take a few seconds to refresh.

Unlink or stop payments?

Unlink asks for confirmation and removes the selected Market association. Removing one connection stops its grant of website access. Other verified connections may still provide access to the same Orders. Submitted cases and requests already authorized may continue; local Wallet/API credentials and on-chain Policies remain active.

To stop new authorized payments, follow Revoke Safe spending authorization. To create spending permission, use User and Wallet setup.