Troubleshooting

The usual problems, and what to do about them. If yours isn’t here, use Send feedback in the app or write to hello@payclose.app.

The sign-in email doesn’t arrive

• Look in the spam or junk folder: the sender is new to your mailbox. Sign-in emails come from login@mail.payclose.app.
• Check the address on the “Check your email” page. If it’s wrong, select Use a different address.
• Wait a minute before asking again. More than a few requests a minute get “Too many requests. Wait a minute and try again.”
• One address can get 10 sign-in links a day. After that, Payclose says “Too many sign-in links for this address today. Use the latest link we sent, or try again tomorrow.” Daily limits reset at midnight UTC.
• Still nothing? Write to hello@payclose.app from that address.

The link expired or was already used

A sign-in link works for 15 minutes after it’s sent, and only once. Select Request a new link on the page that says so, or go back to run.payclose.app and send yourself a new one.

The link signs in the browser that opens it. If you asked for it on your computer but opened it on your phone, you’re signed in on the phone: request another one on the computer.

The security check doesn’t load or pass

The sign-in page runs a Cloudflare check before it sends a link.

• “The security check could not load. Check your connection or allow challenges.cloudflare.com in your content blocker, then reload the page.”
• “The security check did not pass. Complete it again, then send the link.”
• On a shared office network, the day’s new accounts can run out: “Too many new accounts from this network today. Try again tomorrow, or ask a colleague to invite you.” Invitations don’t count toward that limit.

The wallet doesn’t connect

Payclose connects to the wallet extension in your browser, such as MetaMask or Rabby. It doesn’t connect to phone wallets by QR code.

• “No wallet extension was found in this browser”: install your wallet’s extension in this browser. For a Safe payout, you can use the CSV Airdrop file instead.
• “The wallet could not connect. Unlock the extension and try again.”
• “The wallet already has a request open. Open the wallet extension and answer it, then try again.”

Several wallet extensions: pick the one to use

With more than one wallet extension installed, such as MetaMask and Rabby, Connect wallet opens Choose a wallet: select the one that holds the account you need. This browser remembers your choice and lists it first next time, marked Last used, so switching to another wallet is one click. Cancel connects nothing.

An older extension may not show up in that list. When none of your extensions does, Payclose talks to whichever wallet holds the browser’s default place, and another extension can take it: its window opens instead of the one you expect, or the account you expect isn’t there. In the other extension’s settings, turn off its option to act as the default wallet, or turn that extension off while you pay, then reload Payclose.

The wallet is on the wrong network or account

• Network. Payclose offers Switch to Base, or whichever network the payout is on. If your wallet doesn’t know the network yet, Payclose says it “is not in your wallet yet. Add the network in the wallet first, then switch to it and try again.”
• Safe owner. “This wallet is not an owner of the Safe.” Payclose lists the owners: switch to one of them in the extension.
• Regular wallet. “This payout pays from 0x…, and the wallet is connected as 0x….” Switch to the payout’s account in the extension; the page follows.
• Halfway through a payment. If the wallet moves to another network between two transactions, Payclose stops before the next one: switch back, then select Continue.

“Too many requests”

Some actions have a limit per person per minute. Creating payouts, wallets, organizations and invitations, sending for approval, Check now and recording transactions share about 10 a minute; reading a payout’s review or its Safe batch, about 30. Wait a minute and try again.

There are daily limits too, which reset at midnight UTC:

What	Limit
Sign-in links to one email address	10 a day
New accounts from one network	10 a day
Organizations one person creates	3 a day
Invitations from one organization	20 a day
Feedback messages from one person	10 a day

If Payclose has sent all the email it can for the day, it says so: try again tomorrow, or write to hello@payclose.app.

A payout nobody can approve

Send for approval stays off, or a payout waits with “nobody is left to approve it”. Invite an approver in Settings → Members, or lower Approvals required in Settings → Organization. An invited approver counts once they’ve signed in. A payout that was already waiting doesn’t become approved when the rule is lowered: if nobody is left to approve it, reopen it and send it again. See when nobody can approve.

A passkey doesn’t work

• “No passkey yet: without one you cannot approve payouts.” Add one in Settings → Security.
• “For your first passkey, sign in again: the link is valid for a fresh session.” Your sign-in is more than 10 minutes old. Select Sign in again, sign in with a new link, and add the passkey right away.
• “The passkey signature could not be verified.” Try again; if it keeps failing, add a passkey for this device in Settings → Security and use that one.
• A passkey that lives on another device, such as your phone or a security key, works when that device is at hand. Otherwise, add one for this device.

An address can’t be paid yet

A line marked Address not usable, with a Usable from date on the address, is in the 24-hour pause after its approval: send the payout for approval once it has passed. Address not approved means the address waits for an owner or approver other than the person who proposed it. See Recipients and address changes.

“This payout changed a moment ago”

Someone else changed the payout while you were acting on it, and Payclose now shows it as it is. Check what changed, then do it again if it still makes sense.