Start with the payment workflow that slows your team down.
Collect from a client, pay a group, get contractors ready, or fix a reconciliation problem. Gruv helps your team gather the right information, complete the checks, run the payment step, and follow what happens next.
Start here
Pick the job
- Collect a client payment
- Prepare a payout batch
- Get contractors ready
- Review payment mismatches
Build the path
Fit Gruv to the work
- Who pays and receives
- Markets and currencies
- Checks and approvals
- How your team connects
Choose a starting point
Four jobs. One clearer way to run them
Each path solves a different problem. Start with the one closest to the work on your desk today.
Collect a client payment
Plan the invoice, checks, checkout, and payment follow-up as one billing journey. Keep refunds and disputes connected to the same work.
Explore Merchant of RecordPrepare a payout batch
Create a draft batch, catch row-level problems, move it through approval, and export the result after processing.
Explore mass payoutsGet contractors ready
Clarify who does what, collect the information the engagement needs, and make the path to a start or payment decision easier to follow.
Explore Agent of RecordReview payment mismatches
Compare payment records, find missing or mismatched entries, and give possible matches a clear place for review.
Explore reconciliationAcross Gruv
Five familiar steps keep the work moving
The details change by workflow. The basic rhythm stays familiar, so your team knows what to look for next.
- 01
Bring in the source
That might be an invoice, a payout file, a contractor engagement, or two sets of payment records.
- 02
Check what is missing
Find the missing fields, documents, decisions, or approvals before the work moves forward.
- 03
Run the next action
Share the payment link, approve the payout batch, decide whether an engagement is ready, or start reviewing matches.
- 04
See what needs attention
Keep the current state and the problem that needs attention close to the work itself.
- 05
Finish with a clear outcome
See what was completed, what still needs attention, and what your team should do next.
What to bring
Four details make the first conversation useful.
A short description is enough. These four details help the team understand what you are trying to change.
The outcome
What should be easier when the workflow is working?
The money movement
Which countries, currencies, parties, and payment methods are involved?
The decisions
Who reviews exceptions, approves the next step, or answers questions?
The connection
Which systems or files does your team use today?
Frequently Asked Questions
Do I need to know which Gruv product I need?+
Can we start with one market or one workflow?+
Do we need an API integration to begin?+
Can Gruv connect to our existing systems?+
How does pricing work?+
Ready to talk through the workflow?
Tell us who pays, who gets paid, and what needs to happen in between.
