'%20/%3e%3c/svg%3e){kind=small}
Preview
Separation of duties
Audited
Three gates between a request and a payment.
Every payout on Payouts.com passes through three separate, audited stages — Approval, Authorization, and Execution — each with its own permissions. The person who approves can't also be the one who authorizes, so separation of duties ("four eyes") is enforced by the system, not by trust.
Up to date
payouts
authorized
Submitted
authorized
Approvals
How the three gates work
Every payout moves through three separate, audited stages — each with its own permissions and its own controls.
Gate 1 — Approval
An approval decision engine decides whether a payout needs human review, using per-currency thresholds and a source whitelist. Everything else routes into multi-step approval workflows.
Policy routing
Preview
Incoming payout
$8,200
MManager≤ $10k
Routed
DDirector$10k – $50k
Routed
CCFO> $50k
Routed
Auto-routed today1,284
Gate 2 — Authorization
Auto-authorization rules clear matching payouts in the priority order you set, while moving money requires the account owner's passcode at the OTP/2FA gate — recorded separately from who approved.
Dual control
2-of-2
AR
JK
Step-up OTP
Awaiting approvals
Gate 3 — Execution
The execution service pushes each payment to the chosen rail, with batch execution and optional execution workflows — and every approval, authorization, and release is captured in an immutable, exportable audit trail.
Audit trail
Logged entries482,109
Why Approvals
Why three gates matter
Splitting approval, authorization, and execution into separate permissions with separate audit trails is how Payouts.com prevents both fraud and honest mistakes.
Approval gate
0 released
PR-8842$48,200
PR-8845$6,120
PR-8849$2,940
PR-8851$19,400
Awaiting approval
What you get
Safe by default, reviewed at scale.
An approval decision engine auto-approves only what's safe — within per-currency thresholds and a source whitelist — while everything else flows into multi-step workflows, queues, delays, and Supreme Judge AI review.
Per-currency thresholds
Separate auto-approve limits for USD, EUR, and GBP, plus a fallback for everything else.
Source whitelist
Only listed sources — API, batch, UI, and AP invoices — can auto-approve; everything else routes to a human.
Approval SLA · preview
-38% vs target
2.4h
avg approvePending34
Approved · 24h1,902
Within SLA96%
Avg time-to-approve · 7d2.4h
Controls at a glance
Every payout, under policy
100%payouts under policy
2approvers on demand
0unlogged releases
60%faster sign-off
'%20d='m0%200%2018%2011h65%2065%2065%2065%2066L51%2039h65%2065%2065%2065L18%2066h65%2065%2065%2065%2066L51%2094h65%2065%2065%2065L18%20121h65%2065%2065%2065%2066L51%20149h65%2065%2065%2065L18%20177h65%2065%2065%2065%2066L51%20205h65%2065%2065%2065L18%20232h65%2065%2065%2065%2066z'/%3e%3c/svg%3e)
'%20transform='translate(-20)scale(.72249)'%3e%3cpath%20fill='%23fff'%20d='M0%200h1063v708.7H0z'/%3e%3cpath%20fill='%23df0000'%20d='M0%200h1063v354.3H0z'/%3e%3cpath%20fill='%23fff'%20d='M245.2%2059.4a124.6%20124.6%200%200%200%201.1%20243.9%20126.9%20126.9%200%201%201-1.1-243.9'/%3e%3cpath%20fill='%23fff'%20d='m202%20162.4-18.9-13.8%2023.5-.2%207.2-22.3%207.5%2022.3h23.4l-18.8%2014%207.2%2022.3L214%20171l-19%2013.8zm26%2076.9-19-13.8%2023.5-.2%207.3-22.3%207.4%2022.2h23.5l-19%2014%207.3%2022.3-19-13.6-19%2013.8zm86.3-.6-19-13.8%2023.4-.2%207.3-22.3%207.4%2022.3H357l-18.9%2014%207.3%2022.3-19.1-13.7-19%2013.8zm25.7-76.2-19-13.8%2023.5-.2%207.2-22.3%207.5%2022.2h23.4l-18.8%2014%207.2%2022.3-19.1-13.6-19%2013.8zM271.7%20112l-19-13.8%2023.5-.2%207.3-22.3%207.4%2022.3h23.5l-19%2014%207.3%2022.2-19-13.6-19%2013.8z'/%3e%3c/g%3e%3c/svg%3e)
'%20transform='translate(-128)scale(.72249)'%3e%3cpath%20fill='%23fff'%20d='M0%200h1063v708.7H0z'/%3e%3ccircle%20cx='523.1'%20cy='344.1'%20r='194.9'%20fill='%23bc002d'%20transform='translate(-59.7%20-34.5)scale(1.1302)'/%3e%3c/g%3e%3c/svg%3e)
+33 more
OTP / 2FA gate
Authorizing money or switching on auto-pay rules requires the account owner's one-time passcode.
Approval audit trail
Every settings change is captured with who, what, before, and after.
Why teams switch
Safe enough for AI agents
Separate permissions and audit trails are also what make it safe to let AI agents and APIs create payouts: trusted, low-risk paths flow straight through, while anything outside the rules stops for a human.
Policy approval ladder · preview
Routing $24,800
M
MakerSubmits request
Approved
Mg
Manager> $5,000
Approved
Fin
Finance> $25,000
Approved
CFO
CFO> $75,000
Approved
SLA timer
00:00
time-to-authorize
Audit trail
Approved today486
FAQ
The three gates, answered
Everything you need to know about the three gates — approval, authorization, and execution — and how they keep payouts safe.
Still have questions?
What are the three gates?
Approval, Authorization, and Execution. Each is a separate stage with its own permissions and audit trail, enforcing separation of duties so one person can't both approve and release a payment.
How does auto-approval stay safe?
Auto-approval is limited by per-currency thresholds and a source whitelist — only listed sources can auto-approve, and anything above a threshold or outside the whitelist goes to a human reviewer.
What requires an OTP?
Authorizing money movement and switching on auto-pay rules require the account owner's one-time passcode at the authorization gate.
What is straight-through processing?
It's an exemption that lets fully trusted sources bypass the gates, so routine, low-risk payouts can flow without manual review while everything else is still controlled.
Is Payouts secure and compliant?
Yes. Payouts is SOC 2 Type II. Funds are safeguarded with tier-1 partner banks in each region. SSO/SAML, role-based access, audit logs, and approval policies are built in.
Control every payout,
end to end
Approval, authorization, and execution — three audited gates with separate permissions, so one person can't both approve and release a payment.