Recipients and address changes

Recipients are the people your organization pays, each with a payout address per network. The addresses come from your team: you enter the one the contractor gave you, and Payclose checks it, has someone else approve it, and holds it for 24 hours before the first payment. Or invite the recipient to the recipient portal, and the address comes from them, signed by their own wallet.

Add a recipient

Owners and editors add recipients on Recipients with Add recipient. One form takes the person and their address:

• Name, and Email if you have it. The email is optional; it matches rows when you import a CSV, and the recipient portal invitation goes there.
• Invite to the portal, once you type an email: they get an email invitation to confirm their payout address in the recipient portal. It’s ticked to begin with when your organization requires the recipient’s confirmation, and unticked otherwise.
• Network and Address. The networks are those of your company wallets, so add the wallet first.
• Default token and Default amount. They prefill this recipient’s line in a new payout.

Select Add recipient. Payclose saves the person, proposes the address and runs the checks. If they flag something, the panel stays open with What the checks found, so you read it before anyone approves the address. If you’re the only member of the organization, your own approval counts at once.

With Invite to the portal ticked, Payclose sends the invitation once the recipient and the address are saved, and the message says which email it went to. If it can’t be sent, for example because your organization has sent its 20 invitations for the day, the recipient and the address stay as they are: the panel says why and that you can send it from the recipient’s page with Invite to the portal.

To add an address on another network, or to change one, open the recipient and select Propose new address.

The address checks

While you type, the address field checks two things:

• Format: an EVM address is 0x followed by 40 hex characters.
• Checksum: an address in mixed case carries an EIP-55 checksum. If its pattern of upper and lower case doesn’t match, at least one character is wrong, and the address isn’t accepted: copy it again from the source. An address all in one case has no checksum. It’s accepted and marked No checksum, because a typo in it can’t be caught, so paste it from a trusted source rather than typing it.

When the address is proposed, Payclose compares it with every address on file and every address in your past payouts:

• Look-alike address: it starts and ends like an address you already have, with the same first four and last four characters after 0x, but the middle is different. This is how address poisoning works: an attacker sends a tiny transfer from a similar address so that it shows up in your history, and waits for someone to copy it. Confirm the address with the person directly, not in the chat where it was sent.
• Shared address: another recipient already has this address. Check who owns it.

For example, the new address below is flagged as a look-alike of the one on file: the same start, 022e, the same end, 65de, and a different middle.

on file  0x022E7Bf1A501612f5566b640fA69E3fF2e5b65de
new      0x022e9D4C7B1a3E5F6082c1d4A7B9E3f5c2D865De

The checks are a second pair of eyes, not a guarantee: they can’t tell whether an address really belongs to the person.

Approve a new address

Every new address needs an approval from an owner or an approver who didn’t propose it. In an organization with one member, that member approves their own.

• On Recipients, the address waits in its row as Awaiting approval, with an Approve button for those who may approve it. Tick Needs approval to see only those.
• On the recipient’s page, the proposed address sits under the one it would replace, in groups of four characters, with the groups that differ marked.
• Needs you on Overview shows “Approve Lucía Fernández’s new address” to everyone who can approve it, and the number next to Recipients in the sidebar counts them.

Before you approve, compare the address with what the contractor sent, through a different channel from the one it arrived in.

The 24-hour pause

An approved address can’t be paid until 24 hours after its approval. Until then it shows Usable from with the date, and a payout line that uses it is marked Address not usable, which keeps the payout from being sent for approval. The pause leaves time to catch a change that shouldn’t have happened before any money goes to the new address.

Plan ahead: propose a new address at least a day before you send the payout for approval.

Replace or revoke an address

When a new address is approved on a network where the recipient already has one, it replaces the old one. The old address shows as Replaced, and payouts created after the pause use the new one. A draft still on the old address shows Revoked, replaced by the new one, with Use approved address.

Revoke removes an address without a replacement (owners and editors). Lines that use it show it as not usable until another address is approved.

Address history, on the recipient’s page, lists every address with who proposed, approved, replaced or revoked it and when. Payment history shows their lines in recent payouts.

When an address changes after sending

A payout’s lines are frozen when it’s sent for approval. If one of its addresses is revoked or replaced after that, Payclose won’t let the payout be approved or paid. It shows Address revoked, and an owner or editor selects Reopen and send again, switches the line to the approved address and sends the payout for approval again. If a Safe batch that pays the old address is already waiting in the Safe{Wallet} queue, reject it there.

The recipient portal

The recipient portal lets the people you pay confirm their payout address with a signature from their own wallet, propose a new one the same way, and see what you paid them. An address then comes from the person who owns it, not from a message in a chat.

Invite a recipient

Owners and editors invite a recipient in one of two places:

• When adding them: tick Invite to the portal under Email in the Add recipient form. See Add a recipient.
• Later, on the recipient’s page: Invite to the portal in the Recipient portal panel. The recipient needs an email address; without one the button stays off, with “Add Mei’s email with Edit details first: the invitation goes there.”

When your organization requires the recipient’s confirmation and an address waits for a recipient who isn’t invited yet, nothing moves until the invitation goes out. Invite to the portal is then the main button of the recipient’s page, and the note under the held Approve offers it too. Without an email, the note says to add one with Edit details.

Payclose emails them a sign-in link that works for 7 days, naming your organization. The panel shows Invited on with the date, and Send the invitation again sends a fresh link. Once they sign in with the link, it shows Uses the portal since and the date. If you changed the recipient’s email after inviting them, the link signs them in without linking them: invite them again. The recipient gets no seat in your organization and sees nothing of it but their own addresses and payments.

Invitations to the portal count with invitations to your organization: 20 a day in all.

What the recipient does

In the portal, under Payments to you, the recipient:

• Confirms their payout address: the wallet of that address signs a message that proves they control it. The signature moves no funds and costs nothing.
• Changes it: the new wallet signs, and so does the address you pay now, if there is one. The new address then waits for an owner or approver, and the 24-hour pause applies, as for any proposal.
• Sees the payments you made to them, with their status and a link to each transaction.

Their side is described in the recipient portal for recipients.

What you see

• Confirmed by the recipient on and the date, next to an address the recipient signed for, on their page, in Address history and on Recipients.
• Proposed by the recipient on an address they proposed in the portal. It waits under the address it would replace, with the differing groups marked, and owners and approvers get an email. You can approve it even if you’re the one who invited them: they proposed it, not you.
• Not confirmed by the recipient, in a payout’s checks, on a line whose recipient uses the portal but hasn’t confirmed its address. It’s a warning, not an error: the payout can still be sent.

Require the recipient’s confirmation

In Settings → Organization, owners switch on Require the recipient’s confirmation: a new address can be approved only after its recipient confirms it in the recipient portal with a signature from their own wallet. Until then Approve stays off, and a note under it says who confirms the address: “Mei has to confirm this address before it can be approved.” While Mei isn’t invited, Invite to the portal follows it. Addresses waiting for a confirmation leave Needs you.

A recipient who never uses the portal can’t confirm anything. With the setting on, Add recipient ticks Invite to the portal for you; for recipients you added earlier, invite them from their pages.

Receipts

Email receipts to recipients, also in Settings → Organization: when a payout is reconciled, each recipient with an email gets the amount, the network and a link to the transaction. A recipient without an email gets none.

Archive a recipient

Archive, on the recipient’s page, keeps someone out of new payouts and out of payouts copied from an earlier one. Their addresses and history stay, and Unarchive brings them back.