Requires Action

Requires Action is the list of everything in your organization that is waiting on you: payments to approve, sign or send, and requests from teammates for access. You decide each one from the same screen, without hunting through the payments list.

It’s the first row in the sidebar, Requires Action. The number beside it is how many items are waiting on you.

Why use it

Money that needs several people to move it stalls when nobody knows it’s their turn. Requires Action shows each person only what they can act on now:

A payment waiting for approvals under your organization’s approval policy.
An approved payment that needs its Safe transaction proposed, signed or executed.
A payment made outside Mezzanine, such as a bank transfer, that someone has to confirm was paid.
A teammate asking for a permission, or for access to a single company file.

You see what is being asked, who asked, and what has already happened, before you decide.

How it works

Someone publishes a payment. It needs as many approvals as its approval policy asks for. Drafts never appear here.
Approvers click Authorize. Each person’s approval counts once. When the last one is in, the payment moves to execution.
If the money comes from a Safe, someone proposes the transaction. This creates the Safe transaction. A proposer who is a Safe owner signs it at the same time.
The Safe’s owners sign it until the Safe’s own threshold is met.
Someone executes it. Mezzanine sends the signed transaction on-chain, and the payment completes when it’s confirmed.

If the money comes from an account Mezzanine doesn’t send from, step 3 onwards is replaced by one step: whoever pays it there clicks Mark as executed.

For the click-by-click version, see Approve, sign and send a payment.

Using the page

The list

Tabs across the top narrow the list: All, Send Money and Permissions, each with a count, and History. The search box finds items by title, type or who sent it.

Each row shows the item’s title, what kind of item it is, and where it came from, such as Initiated by Jordan Chu · 2 hours ago or Auto-generated by the Recurring Payments app. A flag or document icon means someone has attached one. Hover the flag to read the concern.

The pill on the right says what the item is waiting for:

You see	What it means	What to do
1 of 2	The payment has 1 of the 2 approvals its policy needs	Open it and click Authorize or Reject
Awaiting proposal	Approved, paid from a Safe, and nobody has created the Safe transaction yet	Click Propose
1 of 2 signatures or Awaiting signatures	The Safe transaction exists and needs more owner signatures	If you’re an owner who hasn’t signed, click Sign
Ready to execute	The Safe transaction has all the signatures it needs	Click Execute
Awaiting confirmation	The transaction has been sent and is waiting for the blockchain	Nothing. It clears on its own
Awaiting completion	The payment is made outside Mezzanine and nobody has confirmed it yet	Pay it where the money is held, then click Mark as executed
Confirmed on-chain or Failed on-chain	The transaction has landed. The row leaves the list when the payment updates	Nothing

You’ve signed under the pill means your signature is in. The row stays so you can execute it once the other signatures arrive.

When nothing is waiting, you see All clear, nothing needs your attention.

The detail panel

Click a row to open it on the right. For a payment you see:

Amount, To, From and Execution. Execution says how the money will move, such as Executed from Treasury Safe or Executed outside Mezzanine.
A warning if something is wrong, such as Incomplete payment when a required field is empty.
Details, which opens the full sending and receiving account details and the transaction fields.
Flags and Documents attached to the payment.
Process: what has already happened and what still has to.

The buttons at the bottom:

Button	What it does
Authorize	Records your approval. You’re offered Add a document (recommended) first, then asked to confirm Authorize this payment?
Reject	Ends the payment. Rejection is final — the payment cannot be authorized afterwards. You can give a reason, which is kept for the audit trail
Propose, Sign, Execute	The next Safe step. Each opens a window that uses your connected wallet
Mark as executed	Confirms a payment made outside Mezzanine was paid
Mark as failed	Records that a payment made outside Mezzanine wasn’t paid. This is final
Add flag	Adds a note every reviewer sees. It does not block or approve anything on its own. Up to 90 characters
Add document	Attaches a file or link to the payment’s record
More actions (…)	Share copies a link to the payment. Send back to edit returns it to Drafts. Edit details opens its form

When a decision takes a payment out of your list, the next item opens. A payment you’ve fully approved stays open if it moves to execution, in case you’re the one to propose or sign it.

Permission and document requests

A permission request shows who asked, the permission and what it allows. Under Grant via, choose Direct grant to give only what was asked for, or a group. Joining the group grants everything the group holds, not only this permission. Then click Grant or Deny.

A document request is One-off access to a single file, not the whole series. It’s decided the same way.

History

Everything decided in your organization that you can see, newest first. Filter by kind (Send Money, Permissions, Document access) or by outcome (Approved, Rejected), or search by title, outcome, type or who decided. Click a row to see who decided, when and why. Nothing here can be changed.

Approval policies and Safe signers

Two separate rules decide how many people must act on a payment.

Approval policies set how many approvals a payment needs. They’re set in Send Money → Actions → Settings, under Approval Policies. Each has a minimum and maximum amount and a Required Approvals count. Approve Payments starts with three:

Policy	Amount	Approvals
Tier 1: Daily Operations (Up to $5K)	$0 to $5,000	1
Tier 2: Standard (Up to $50K)	$5,001 to $50,000	2
Tier 3: High-Value (Over $50K)	$50,001 and up	3

The Safe’s threshold sets how many owner signatures the Safe transaction needs. Mezzanine reads it from the Safe itself, so if the Safe’s owners change it, the new number applies. To propose you need a wallet that is an owner or delegate of the Safe. To sign you need an owner wallet.

Good to know

Drafts aren’t listed. A draft is its author’s until they publish it from Send Money.
Once you approve, the payment leaves your list while it waits on the others. It comes back if it reaches execution and you can propose, sign or execute it.
Signatures are per wallet. If you hold two owner wallets on the same Safe, you can sign with each.
You can reject or send back a Safe payment only until its transaction is proposed. After that, the outcome on-chain decides. If the transaction is cancelled in the Safe, the payment ends as rejected.
Earlier Safe transactions go first. If other transactions are queued ahead of this one in the Safe, Execute shows Transaction not executable until they are executed or rejected.
Every destination is screened against sanctions lists when the transaction is proposed and executed. A flagged address stops the payment with Destination address failed OFAC screening; transaction not sent.
With Wallet Verification Mode on, an unverified destination shows a warning such as Destination wallet not verified. You must tick I understand this wallet isn’t verified for this payment and want to proceed. before you can continue, and the exception is logged. See Wallet Verification.
If a decision fails, you see That didn’t go through. Nothing was recorded — try again. If someone else acted first, you see This payment moved on — refreshed.

Who can use it

Everyone in your organization can open Requires Action. What appears depends on what you’re allowed to decide.

To…	You need
See payments here	View outgoing transfers
Approve, reject, propose, sign, execute or mark a payment	Propose bill payments for payments to others, or Propose internal transfers for transfers between your own accounts
Propose a Safe transaction	A connected wallet that is an owner or delegate of the paying Safe
Sign a Safe transaction	A connected wallet that is an owner of the paying Safe
Decide permission requests	Membership of the Admin or Owner group
Decide document access requests	Admin or Owner, or Manage company files

If you lack the propose permission for a payment, its decision buttons are greyed out. Add flag, Add document and the More actions items still show, and clicking one tells you which permission is missing and lets you request it.