Service
Payouts
In one line
Send money out on the same platform.
What it is
A lot of restricted-vertical businesses pay out as much as they take in — affiliate commissions, distributor payments, marketplace sellers, contractor settlements. Doing that through a separate tool means a second reconciliation, a second set of credentials and a second vendor who can decide your category is a problem.
Payouts on the platform draw from the same balance your acceptance settles into, with the same dashboard and the same audit trail. Speed depends on the rail and the receiving bank; your options are set out per program rather than promised on a marketing page.
Capabilities
What you get, specifically.
Batch and one-off payouts
Upload a file, call the API, or send one payment from the dashboard. All three land in the same ledger.
Recipient onboarding
Recipients verify their own bank details through a hosted flow, so you are not storing account numbers you do not need.
Approval workflows
Maker-checker on payouts above a threshold you set. The person who creates a payout is not the person who releases it.
Reconciliation
Every payout reconciles to the settlement it was funded from. No separate statement to marry up.
Specification
The detail.
- Rails
- ACH; faster rails where available on your program
- Recipient types
- Bank account
- Payout speed
- Set at underwriting
- Per-payout cost
- Set at underwriting
Rows reading set at underwriting are not omissions. Those figures are decided per merchant against your vertical, volume and history, and you will see all of them in writing before you sign.
Tell us what you sell.
Before anything sensitive changes hands, we will tell you whether we can underwrite your vertical, roughly what the terms look like, and what underwriting will ask you for.