Capture payout inputs from the systems you already use
- Launch with imports, then expand into APIs and webhooks
- Map partner, payee, and payout fields once instead of every cycle
- Keep one shared record across sources, teams, and payout runs
For marketplaces, platforms, and finance teams
Run payout batches that finance can close.
Bring payee readiness, approvals, rail routing, return recovery, and reconciliation exports into one payout run that teams can operate with confidence.
Payee readinessApproval controlsRail routingReturn recovery
Explore the stack
The core parts of a modern payouts platform
Gruv brings together integrations, payee onboarding, payout execution, approval rules, and audit visibility so teams do not have to stitch the flow together across separate tools.
APIs, imports, and embedded flows
Overview
APIs
Bulk imports
Embedded flows
In one system
Global payout orchestration
Overview
Local and cross-border
FX visibility
Statuses and retries
In one system
Payee onboarding and tax capture
Overview
Profiles and methods
Tax forms
Review states
In one system
Approvals, controls, and audit trail
Overview
Approval chains
Policy rules
Audit records
In one system
Features
The building blocks behind modern payout programs
Everything teams usually end up stitching together across forms, support queues, finance tools, and payout providers can live in one connected workflow.
Payout automation and scheduling
Automate recurring runs, threshold-based releases, approval routing, and exception handling so every payout cycle is easier to operate.
Payout release policy×
Authorization is:Required
Threshold:$1,000.00 USD
Tax, compliance, and document collection
Keep W-8, W-9, and other program-specific documents tied to the payee record so reviews, holds, and reporting are easier to manage.
W8
Verified
Tax ID
Country of Residence
Flexible payout methods
Offer the payout methods your program supports while keeping recipient preferences, payout status, and reconciliation fields in one workflow.
PayPal
Wise
RevolutBank
APIs, webhooks, and finance syncs
Connect payout operations to your product, ERP, support tooling, and internal workflows through APIs, webhooks, imports, and exports.
Stripe
QuickBooks
XeroHow it works
How modern teams run the full payout flow
Sending money is only one part of the job. Real payout programs also need clean intake, payee onboarding, tax collection, approval rules, exception handling, and finance-ready records at the end.
Turn recipient data into payout-ready profiles
- Collect bank details, wallets, and payout preferences in one flow
- Track missing tax details, review steps, and blocked states clearly
- Give ops and support teams a clear picture of what needs action
Release, monitor, and reconcile each payout run
- Set approval chains, policies, and release rules around each program
- Surface exceptions and retry states before they become support escalations
- Pass structured exports, references, and webhook signals downstream
Use Cases
Built for businesses where payouts are part of the product
Affiliate platforms, creator ecosystems, expert networks, ad products, and promotions teams all need the same foundation: clean payee data, controlled releases, and visible status for ops, finance, and support.
Affiliate Marketing
Aggregate partner earnings from multiple networks, automate approvals, and pay affiliates without month-end spreadsheet cleanup.
Ad Networks
Turn campaign and channel data into payout-ready records, then release partner payments with cleaner reconciliation.
Creator Economy
Support creator withdrawals, partner revenue shares, subscription earnings, and brand payouts in one payout workflow.
Influencer Marketing
Convert approved deliverables and campaign performance into payout runs, documents, and status visibility for brands and creators.
Podcasts
Track host, guest, or network revenue splits and pay stakeholders with consistent records and visible status updates.
Gaming & Promotions
Handle prize, reward, rebate, and campaign payouts with review steps, exception handling, and audit trails.
How it works
From rail setup to a closed batch
Five steps shape every payout run: connect rails, set policies, onboard payees, release the batch, and reconcile in finance.
gruv.app › rails › new connection
railsprovidersadd
ValidatingNew rail · Stripe Treasury · ACH
ProviderStripe Treasury
RegionUS · ACH same-day
API keysk_live_xxx
Webhook secretwhsec_2xy
Connection checks4 / 5
DNS resolution
Name match · Treasury LLC
Daily limit · $5M
Sandbox round-trip
Production permissions
Frequently Asked Questions
Which countries, currencies, and payout methods do you support?+
Gruv supports multi-country, multi-currency payout programs across bank rails, digital wallets, cards, and partner ecosystems. Coverage continues to expand by corridor and provider, so the best route mix depends on your launch markets, methods, and payout design.
How do payee onboarding and payout methods work?+
Payees can onboard through self-serve flows, embedded experiences, or bulk imports. Gruv can collect payout details, identity or business details, supporting documents, payout preferences, and tax information while keeping status and exceptions visible to your ops team.
How do you prevent duplicate payments?+
Payout creation is designed to be idempotent so retries do not create duplicate disbursements. Use idempotency keys and batch validation to safely re-run operations when networks, files, or providers are flaky.
Is there an approval workflow?+
Yes. You can configure multi-user approvals, thresholds, release windows, and exception handling so routine payouts move quickly while higher-risk flows pause for review.
What reporting and reconciliation artifacts do you provide?+
You get batch and item-level status, provider references, timestamps, return or failure reasons, exports, and webhook events so finance, support, and ops teams can stay aligned.
