Skip to main content
Gruv.ai logo
How Gruv works

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 Record

Prepare a payout batch

Create a draft batch, catch row-level problems, move it through approval, and export the result after processing.

Explore mass payouts

Get 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 Record

Review payment mismatches

Compare payment records, find missing or mismatched entries, and give possible matches a clear place for review.

Explore reconciliation

Across 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.

  1. 01

    Bring in the source

    That might be an invoice, a payout file, a contractor engagement, or two sets of payment records.

  2. 02

    Check what is missing

    Find the missing fields, documents, decisions, or approvals before the work moves forward.

  3. 03

    Run the next action

    Share the payment link, approve the payout batch, decide whether an engagement is ready, or start reviewing matches.

  4. 04

    See what needs attention

    Keep the current state and the problem that needs attention close to the work itself.

  5. 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?+
No. Start with the job you need to get done: collect a client payment, pay a group, get contractors ready, or review payment mismatches. Gruv can help identify the closest starting point.
Can we start with one market or one workflow?+
Yes. A focused first use case makes it easier to confirm the parties, money movement, checks, and connection method. You can discuss additional markets or workflows after that path is clear.
Do we need an API integration to begin?+
Not necessarily. Depending on the workflow, the starting point may be in-product work, a file exchange, or an API or webhook connection. Gruv will confirm the option available for your setup.
Can Gruv connect to our existing systems?+
Start with the file, API, webhook, or accounting connection your workflow needs. Bring the system names to the first conversation so the team can confirm the best available connection method.
How does pricing work?+
Use the fee planning calculator for a simple scenario. Current Gruv pricing comes from a quote based on the service, markets, payment flow, and connection method you need.

Ready to talk through the workflow?

Tell us who pays, who gets paid, and what needs to happen in between.