Payclose @paycloseapp

@MetaMask For payouts we'd draw the line here: let the agent prepare the batch, never approve it. Whoever proposes a payout, human or agent, shouldn't be the one who signs off on a new address.

@base Money in is getting easy. Money out is the next half: once revenue lands in USDC on Base, a team pays its contractors from the same wallet every month. That side needs approvals and a list of known addresses, not just a fast transfer.

@tether Happy 12th. Built for traders, and quietly it became payroll too: lots of teams pay contractors in USDT every month now. Sending is the easy part. Knowing that every address on the list is still the right one is where the work is.

@realScamSniffer For teams that pay the same people every month, the fix is process, not eyesight: pay only from a list of approved addresses, and send any new address through its own approval with a waiting period. Then nobody copies an address from the history at the moment of sending.

@safeLabs_ @safe Curious how the policy controls handle recurring payouts. In a monthly contractor batch the amounts rarely change, but now and then one address does. Can a policy treat an address the Safe has never paid differently from the ones it has paid before?

The riskiest message in a contractor payout: "new wallet, pay me here." With address confirmation on, the recipient confirms an address with a signature from that wallet, and a change also needs one from the wallet paid now. A chat message alone can't redirect a payment.

@safe Payroll is the workflow we'd test first: today every contractor's monthly amount from a team Safe is public to anyone who knows the address. The open question for us is reconciliation: will owners still get a per-transfer record to match against what was approved?

@realScamSniffer Same first 3 and last 6 characters as the real one, which is exactly the part people check by eye. For an address you pay every month, copy it from your own records (last month's payout, a saved contact), never from the transaction history, and compare it in full.

New in Payclose: a proof file for every approved payout. It holds the exact lines, each approver's passkey signature over them, and the transactions that paid them. Anyone can check one in the browser, nothing uploaded, no need to trust us: payclose.app/verify?utm_sou…

@Lisk the group chat is also where "new wallet, use this one" shows up. whatever the stack, that's the one message that should need a second approver and a waiting period before money moves

@TweetBySoft propose and explain, never decide. we ended up with the same rule for humans: whoever prepares a payout can't approve it. how does Ledgerly handle a contractor changing their payout address mid-month? that's where most of the risk sits for us

@RhiderShark @Americanfort_io agree, it's a design thing. what's worked for us on recurring payouts: check a new address against every address you've paid before, not just the last one, and show the middle chars. anything new waits a day and needs a second person to approve. boring but it catches this