Approve, sign and send a payment
Before you start
Section titled “Before you start”- To approve, the payment’s tier names you, directly or through a group you’re in.
- To propose, sign or execute, you have View outgoing transfers, plus Propose bill payments (for a payment to someone else) or Propose internal transfers (for a transfer between your own accounts). (Who can use it)
- To propose, your wallet is an owner or delegate of the paying Safe. To sign, it’s an owner. Have it ready to connect.
- Mezzanine records each step under the Full name in your profile, or your email if you haven’t set one.
Part A: Approve the payment
Section titled “Part A: Approve the payment”- In the sidebar, click Requires Action.You see the list of items waiting on you. A payment needing approvals shows a count such as 1 of 2.
- Click the payment.Its details open on the right: Amount, To, From, Execution, and the Process so far.
- Check the amount, the recipient and anything under Flags or Documents. Open Details to see the full account details.
- Click Approve.A window opens titled Add a document (recommended).
- Attach an invoice or link and click Save and continue, or click Continue without one.The window changes to Approve this payment? and shows You are approving, for example
$14,200.00 to Phil Quan
, with the account it goes to and the account it comes from beneath. No money moves until the payment is executed. - Click Approve.If more approvals are needed, you see
Your approval is recorded — 1 of 2. Waiting on the last one.
and the payment leaves your list. If yours was the last, you see “…approved, ready to execute from Safe name.” and the payment stays open, now showing Propose.
Wallet not verified? If the destination wallet hasn’t passed wallet verification, a warning appears in the Approve this payment? window, and again when you propose, sign or execute. Tick
I understand this wallet isn’t verified for this payment and want to proceed.to continue. The exception is logged. If you have Start wallet verification, you can click Send a test transaction or mark it as verified in the warning instead (Verify a wallet with a test transaction, Verify a wallet manually).Not paid from a Safe? If Execution reads
Executed outside Mezzanine, there’s nothing to sign. Someone the Off-site accounts execution policy names pays it from that account, then clicks Mark executed, optionally adds a document, and confirmsMark this payment as executed?. If the policy needs more than one confirmation, each of them does this. That’s the end of it.
Part B: Propose the Safe transaction
Section titled “Part B: Propose the Safe transaction”- With the payment open, click Propose.A window opens titled Propose transaction, showing the amount, recipient, Proposer, Wallet and Role.
- If it says
Connect a wallet to propose this payment.
, click Connect wallet and choose your wallet.The window shows your wallet and a Role of Safe owner or Safe delegate. - If Role says Not a Safe owner or delegate, click Choose different wallet.A window opens titled Switch to the correct wallet, listing the Safe’s signers and proposers. Click Connect beside a wallet you hold.
- If the button reads Switch to network, click it and approve the network change in your wallet.
- Click Propose transaction, then approve the signature request in your wallet.You see
Transaction proposed. The Safe’s signers can now sign it.
The payment now shows Sign, or Execute if one signature is enough.
Already sent from the Safe in another app? If someone paid it straight from the Safe before anyone proposed it here, don’t propose it. Click Mark executed beside Propose instead and confirm
Mark this payment as executed?. This is open to someone the Off-site accounts execution policy names, and only until a transaction is proposed from Mezzanine.
Part C: Sign (each Safe owner)
Section titled “Part C: Sign (each Safe owner)”Every owner who signs does this. If you proposed as an owner, your signature is already in.
- In the sidebar, click Requires Action, then click the payment.The row shows a count such as 1 of 2 signatures.
- Click Sign.A window opens titled Sign transaction, showing Signer, Wallet, Role and Signatures.
- If your wallet isn’t connected or isn’t an owner, use Connect wallet or Choose different wallet as in Part B.
- Click Sign transaction, then approve the signature in your wallet.You see
Signature added to the Safe transaction.
The row shows You’ve signed.
More signers needed? The Safe decides how many signatures are required, not Mezzanine. The other owners see the payment in their own Requires Action list. To send one of them the payment directly, open it, click More actions (…) → Share, and send them the copied link.
You hold two owner wallets? Signatures count per wallet. Switch to the second wallet and sign again.
Part D: Execute
Section titled “Part D: Execute”Once the signatures are in, the row shows Ready to execute.
- Click the payment, then click Execute.Mezzanine checks the Safe’s queue. If nothing is ahead of this transaction, a window offers Add a document (recommended).
- Click Save and continue or Continue without one.A window opens titled Execute transaction, showing Executor and Signatures.
- Click Execute transaction.You see
Waiting for on-chain confirmation…
, thenTransaction confirmed on-chain.
Click View on block explorer to see it, or Close.
You’re done. The payment moves to History in Move Money as Complete. To read its activity, open Requires Action → History, select the payment and open Changes below Process.
Prefer the payments list? Every step is also on Move Money. Open the payment from Requires Action and use the same buttons in its details.
If something goes wrong
Section titled “If something goes wrong”| You see | Why | What to do |
|---|---|---|
| Approve is greyed out | The payment’s tier doesn’t name you, or the approvals it still needs are for others. | Click Policy beside Process to see who it needs, and ask one of them |
| Propose, Sign or Execute is greyed out | You don’t hold the propose permission for this kind of payment | Ask an admin for Propose bill payments or Propose internal transfers. Clicking the button names the missing permission and lets you request it |
Only an owner or delegate of the paying Safe can propose this payment. Choose a different wallet.or Only an owner of the paying Safe can sign this payment. Choose a different wallet. |
The connected wallet can’t act for this Safe | Click Choose different wallet and connect an owner wallet, or ask a teammate who holds one |
You have already signed this transaction |
This wallet’s signature is already counted | Wait for the other owners |
Connect a wallet to propose this payment.or Connect a wallet to sign this payment. |
No wallet is connected | Click Connect wallet, choose your wallet and try again |
Your sign-in can’t be confirmed. Reload the page and try again. |
Mezzanine couldn’t confirm who’s signed in | Reload the page and try again. If it keeps happening, sign out and back in |
This payment’s paying account can’t be read. Reload the page and try again. |
The page can’t read the paying Safe’s details, often because it’s an older version of Mezzanine | Reload the page and try again. If it keeps happening, contact support |
This payment’s recipient has no valid wallet address, so it can’t be proposed. Send it back to edit the payment. |
The recipient has no wallet address the Safe can pay, for example a bank account | Click More actions (…) → Send back to edit, then change the recipient or the paying account |
| Transaction not executable | Other transactions are queued ahead of this one in the Safe | Execute or reject them in the Safe first. How the Safe queue works explains the order |
The destination address didn’t pass sanctions screening, so nothing was sent. Don’t send funds to it. |
The recipient address is on a sanctions list | Stop. Don’t pay this address. Raise it with whoever handles compliance |
The transaction reverted on-chain. |
The transaction failed on the blockchain. Nothing moved | Check it on the block explorer. The payment ends as Failed; create a new one if it should still go out |
Transaction broadcast. On-chain confirmation is pending. |
The blockchain hasn’t confirmed it yet | Close the window. The payment completes on its own |
This payment moved on — refreshed. |
Someone else acted on it first | Read the updated payment and carry on from its new step |
That didn’t go through. Nothing was recorded — try again. |
The action failed | Try again. If it keeps happening, contact support |