Docs, Wallets
Wallets
Updated
Every payout is paid from one company wallet. Payclose records the wallet’s public address only: it never has its keys and never signs for it.
A Safe or a regular wallet
Payclose pays from two kinds of wallet:
- Safe: a multisig account in Safe{Wallet}. One owner signs the payout’s batch in Payclose with their own wallet, the owners confirm and execute it in Safe{Wallet}, and one transaction pays every line. See Paying from a Safe.
- Regular wallet: an ordinary account in a browser wallet such as MetaMask or Rabby. You pay from Payclose: in one transaction where your wallet can batch transfers, otherwise one transaction per line. See Paying from a regular wallet.
Either way, the payout goes through the same review and approvals first, and it’s checked on-chain afterwards.
How Payclose tells them apart
You don’t pick the kind. When you add a wallet, Payclose reads its address on the network you chose:
- No contract at the address: a Regular wallet. An account upgraded to a smart account (EIP-7702) is a regular wallet too, because its own key still signs.
- A Safe: a Safe. Payclose builds batches for Safe versions 1.3, 1.4 and 1.5.
- Any other contract: not added. The app says “This address is a contract Payclose can’t pay from yet.”
If the network can’t be read at that moment, nothing is added: try again in a minute.
Note. A Safe exists only on the networks it was deployed on. Add a Safe’s address on a network where it isn’t deployed, and there’s no contract there, so Payclose reads it as a regular wallet and says so: “No contract at this address: Payclose treats it as a regular wallet. If it’s a Safe that isn’t deployed on this network yet, deploy it first.” Remove it, deploy the Safe on that network, and add it again.
Add a wallet
Owners add wallets, from the Setup panel on Overview or from Settings → Wallets with Add wallet:
- Pick the Network.
- Paste the Address. The field checks it as you type; “Valid address; the checksum matches.” means it’s well formed.
- Give it a Label if you like, such as “Treasury”.
- Select Add wallet.
The list shows each wallet’s label and kind (Safe or Regular wallet), its network, its address and when it was added. Owners can Rename or Remove a wallet from its row. A wallet that a payout uses can’t be removed: delete the draft payouts that use it first, and payouts that were sent keep it for good.
Everyone in the organization sees the wallets; only owners change them.
Networks and tokens
A payout pays from one wallet, on that wallet’s network, and its recipients need an approved address on the same network. These are the networks the app offers:
| Network | Tokens |
|---|---|
| Ethereum | USDT, USDC |
| Base | USDC |
| Arbitrum One | USDC, USDC.e, USDT |
| Sepolia, Base Sepolia and Arbitrum Sepolia (test networks) | USDC |
On Arbitrum One, USDC (issued natively) and USDC.e (bridged) are different tokens with different contracts: pay in the one your contractor expects. What else to agree with a contractor before the first payment: paying contractors in USDC.
Payclose doesn’t offer USDT on Base. The USDT contract it listed there until October 11, 2026 is a bridged copy of Ethereum USDT, not a token Tether issues, and an exchange may not credit a deposit of it. A line or a default token in it from before that date still shows it, with a note that it’s no longer supported: pick another token for it, such as USDC on Base, before you send the payout. A payout sent for approval with it can’t be approved or paid: reopen it, change the token and send it again. Payouts already paid in it stay on record as they were.
Use a test network to try the whole flow with test USDC before you pay for real.
TRON isn’t available yet: TRON payouts come later.