A staged payment can outlive the authority that created it.
Founders need delegated payment preparation, while access removal must immediately change what Command can execute.
Who you’d be doing this for
“I removed our contractor in the morning, then saw their old payment waiting for approval after lunch.”
Faraji Abebe · Finance Manager
Manages payment permissions for a growing startup that uses Command to prepare vendor payments.
What is at stake
A staged payment can remain available after a finance admin removes the requester’s access. You must weigh delegated payment speed against proof that authority is current at approval.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- delegated payment speed vs current authority
- customer clarity vs control rigor
- narrow release scope vs reusable governance evidence
Why Mercury
Command stages customer-directed payments inside a business banking workflow where partner-bank obligations depend on clear authority and logging.
Written with these in mind
Not your kind of problem? 27 more at Mercury, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.