Payout operations platform
Payout operations, under control.
Rout turns obligations into approved, ledgered, reconciled payouts — with a record you can hand to your auditor.
Not a bank or a money transmitter · no custody of funds
Payout BatchSelect a payment to inspect its ledger entries and audit trail.
PAY-48213-01 · 184,250.00 USD
What Rout is
A system of record for money you owe — from the first obligation to the last reconciled cent.
Every payment starts as an obligation — what you owe, to whom, and why. Payouts settle obligations, in full or in parts, so nothing is paid twice and nothing is left open.
The person who creates a payout cannot approve it. Policies set thresholds by amount, recipient and rail, and every decision is signed and timestamped.
Each movement posts balanced debits and credits to an append-only ledger. Corrections are new entries, never edits — so the history always reads true.
Rout matches its ledger against provider reports and bank statements, surfaces exceptions with owners, and keeps a complete trail ready for audit.
Controls & compliance
Controls built into the route, not bolted on after.
Every payout passes the same checks, enforced on the server, recorded in the ledger and visible to audit.
Whoever creates a payout can’t approve it. Thresholds by amount, recipient and rail decide when a checker is required.
Server-enforced, role-based permissions, scoped per organization with multi-tenant isolation.
Append-only. Corrections are new entries, never edits.
Retries never double-pay. An unknown provider outcome is resolved before any resend.
Ledger against provider report against bank statement, with every exception owned and tracked.
Every privileged action is attributed to a person and timestamped.
No raw bank or routing numbers and no full tax IDs are stored in Rout — status only.
Rout is not a bank or money transmitter and makes no compliance certification.
Many rails, one control plane
Add rails without adding process — the controls travel with every payout.
Rout doesn’t move money itself; a regulated provider does. Whatever the rail, every payout runs the same obligations, approvals, ledger and reconciliation.
Batch settlement for routine payouts
Same-business-day settlement windows
High-value wire transfers
Instant payments, around the clock
Funds held and moved by your regulated payment provider.
How it works
Three steps. One route.
Collect and verify payee details once. Bank details change only through an approved request.
- Verification via your provider
- Detail changes require approval
- Full recipient history retained
Raise obligations from invoices, contracts or file imports. Batch them into payouts; a second person approves before anything moves.
- Maker ≠ checker, enforced
- Thresholds by amount, recipient and rail
- Every decision timestamped
Approved payouts are released to your regulated provider. Rout posts to the ledger and matches provider and bank records.
- Double-entry on release
- Three-way match
- Exceptions queued with owners
Self-service for payees
Payees set themselves up. Your team approves what changes.
Payees receive an invitation and create their own access to the portal.
Business and contact details are confirmed by the payee, not re-keyed by your team.
Tax information is collected in the portal and tracked as a status in Rout.
Bank details are entered in a hosted flow; Rout never stores the raw numbers.
Bank-detail changes require approval
Full recipient history retained
Bank details are collected in a hosted flow. Rout stores status only.
Built for your stack
One call to create a payment. The controls still apply.
Payments created through the API wait for approval like any other, post to the same ledger and reconcile the same way.
Illustrative sample — not a live endpoint.
POST /v1/paymentsAuthorization: Bearer rk_live_••••••••Idempotency-Key: obl-48213-01{"obligation_id": "OBL-48213","recipient_id": "rcp_cascade_freight","amount": "184250.00","currency": "USD","rail": "fedwire"}// 201 Created// { "id":"PAY-48213-01", "status":"awaiting_approval" }
Where Rout sits
Rout is software — not a bank or money transmitter.
A regulated provider moves money; Rout records, controls, and reconciles.
Holds funds and moves money across payment rails.
RoutRecords obligations, enforces approvals, keeps the ledger and reconciles every payout.
Request access
Payout operations you can prove.
Walk through approvals, ledger and reconciliation with your own payout scenarios.