Send Money

Send Money is where every payment your organization makes is listed, from the first draft to the final result. Use it to see where a payment stands, publish drafts, and move approved payments through to execution.

It’s in the sidebar as Send Money. The page itself is titled Approve Payments, under Payments. The number beside Send Money in the sidebar counts payments in drafts, approval and execution.

Why use it

Each payment goes through the same steps: it’s drafted, approved by the people your policy requires, then executed. Send Money shows every payment in each of those steps in one place, so you can:

• See what’s stuck and at which step.
• Check the record of who approved, signed and executed a payment, for audits and board questions.
• Export your payment history to a CSV file for accounting.

How it works

1. A payment is created as a draft, from Bill Pay, Add Internal Transfer or a recurring schedule. The creator picks an approval Policy.
2. Someone publishes it. It moves to NEEDS APPROVAL.
3. Approvers approve it until the policy’s count is met. It moves to EXECUTION.
4. The money moves. From a Safe, someone proposes the transaction, the Safe’s owners sign it, and someone executes it. From an account Mezzanine doesn’t send from, someone pays it there and marks it completed.
5. It lands in HISTORY as Complete, Rejected or Failed.

Approvers and signers can also do steps 3 and 4 from Requires Action, which lists only what’s waiting on them. See Approve, sign and send a payment.

When to use it

• To publish drafts you or your team have prepared.
• To find a specific payment and see where it is. See Find out why a payment hasn’t gone out.
• At month end, to review what went out and export it.
• To change your approval policies, categories or tags.

Using the page

Tabs and statuses

Each tab holds the payments in one step. The first three show a count.

You see	What it means	What to do
DRAFTS	Saved but not submitted. Nobody has been asked to approve it	Click Publish on the row. It’s greyed out until the payment is complete; hover it to see what’s missing
NEEDS APPROVAL	Waiting for approvals. The Status column shows progress against the policy	Approvers click the check icon, Approve Payment, on the row
EXECUTION	Approved. The money hasn’t moved yet	Use the row’s action, below
HISTORY · Complete	The money moved: confirmed on-chain, or marked completed	Nothing. Use View Block Explorer in the row’s menu to see the transfer
HISTORY · Rejected	Someone rejected it, or its Safe transaction was cancelled	Create a new payment if it should still go out
HISTORY · Failed	The transaction reverted on-chain, or someone marked it failed	Check the reason, then create a new payment if needed

On the EXECUTION tab, the row’s action button changes as the payment moves. Hover it to see its name:

Button	When it shows
Propose transaction	Paid from a Safe, and nobody has created the Safe transaction yet
Sign transaction	The Safe transaction needs more owner signatures
Execute transaction	The Safe transaction has all its signatures
A greyed-out check, Pending on-chain confirmation	The transaction is on its way. It completes on its own
Mark completed and Mark failed	Paid from an account Mezzanine doesn’t send from. Pay it there, then mark the result

The Due Date column shows Overdue once the due date has passed, and Due soon in the 7 days before. These are reminders only. They don’t move the payment.

Finding payments

• Search by recipient, destination, funding entity, funding source, asset or tag. It searches the tab you’re on.
• Filter from any column header. The date filter has Overdue, This week and This month shortcuts.
• Change the columns you see. The App column, which shows where a payment was created, is hidden until you turn it on.
• Switch between Table and Kanban. Kanban shows every step side by side as DRAFT, APPROVAL, EXECUTION and COMPLETED. Drag a card one column to the right to open that step’s action, or back to DRAFT to send it back. COMPLETED shows the 25 most recent finished payments.

Click any row to open the payment.

The row menu

The … button on each row, More actions, offers:

• Add Flag: a note for reviewers. A comment is required.
• Reject: ends the payment. A rejected payment can’t be approved afterwards.
• Edit Details: moves the payment back to DRAFTS. Editing moves this payment back to Drafts, and every required approver must approve it again.
• Mark Completed / Mark Failed: close a Safe payment by hand before anyone has proposed its transaction. You must add a comment, because you’re bypassing the Safe.
• Share Details, View Details, and in HISTORY, View Block Explorer.

The Actions menu

Actions, at the top right, has Add Bill Payment, Add Internal Transfer, Export History and Settings. Export History downloads your payment history as a CSV file.

Settings

Actions → Settings opens Approve Payments Settings:

• Payment Categories and Status Tags: the lists people pick from on a payment. Changes save as you make them.
• Approval Policies: for each policy, a Policy Name, Description, Min Amount, Max Amount (blank means No limit), Currency and Required Approvals. Click Save Changes to apply.

New organizations start with three policies: 1 approval up to $5,000, 2 approvals from $5,001 to $50,000, and 3 approvals from $50,001. Raise the counts if you want more eyes on larger payments.

Good to know

• The creator chooses the policy. The Policy field on a payment decides how many approvals it needs. The Policy column on DRAFTS shows it, so check it before you publish.
• A payment can’t be published until it’s complete: recipient and recipient account, funding source and funding source account, description, amount and an approval policy.
• DRAFTS, NEEDS APPROVAL and EXECUTION each list the 50 most recently created payments in that step, and HISTORY the 1,000 most recent. For older payments, use Export History.
• Once a Safe transaction is proposed, you can’t edit, reject or send back the payment. The outcome on-chain decides it.
• Mezzanine reads the Safe’s threshold from the Safe. If the owners change it, the new number applies to transactions still being signed.
• On a phone, the page shows the Kanban board.

Who can use it

The Approve Payments app must be installed from the App Library.

To…	You need the permission
See this page and its payments	View outgoing transfers
Publish, approve, reject, flag, edit, propose, sign, execute or mark payments to others	Propose bill payments
Do the same for transfers between your own accounts	Propose internal transfers
Change categories, tags and approval policies	Propose bill payments or Propose internal transfers
Sign a Safe transaction	An owner wallet of the paying Safe, connected to Mezzanine

Without View outgoing transfers, the page reads You can’t view payments and lets you request access. Without a propose permission, the buttons still show, and clicking one tells you which permission is missing.