Gruv Logo
Merchant of Record

Merchant of Record for paying talent or invoicing clients.

Gruv supports two distinct MoR paths: one for businesses consolidating contractor and agency payments, and one for freelancers managing invoices, collection, and payouts. Start with the path that matches your role.

Business payablesFreelancer invoicingCompliance gatesCollection to payout
I’m paying global talentI’m invoicing clients
A finance and operations team reviewing payout workflows together

What Merchant of Record actually changes.

Merchant of Record is useful when you want more than a payment rail. Depending on the workflow, it can package billing, compliance, payout control, and auditability into one operating model.

Billing and payment collection

Create invoices, payment artifacts, or checkout flows that tie back to the underlying client, work, or vendor relationship.

Compliance and tax gates

Collect required profile, tax, or verification details and hold downstream actions until the workflow is ready to proceed.

Payout control and visibility

Move money out through a structured payout flow with statuses, retries, and exception handling that ops teams can actually follow.

Records finance can use

Keep invoices, beneficiaries, provider references, and export history connected so reconciliation is not rebuilt in spreadsheets later.

Start with the path that matches your role.

The underlying platform can support both sides, but the daily job is different. Businesses usually care about vendor consolidation and payout controls. Freelancers usually care about invoicing, client payment experience, and getting paid without extra admin.

Business path

Pay global talent through one vendor workflow.

Best for finance, AP, procurement, partner ops, and marketplace teams paying freelancers, agencies, or contractor groups.

Reduce vendor sprawl by onboarding Gruv once instead of operationalizing every payee as a separate vendor.
Collect payee details, tax information, and compliance artifacts before release.
Run approval-aware payout operations with explicit statuses and reconciliation exports.
Explore the business workflow

Freelancer path

Invoice clients globally and get paid with less admin.

Best for freelancers, agencies, and solo operators who want clearer invoicing, collection, and payout visibility without stitching together multiple tools.

Send professional invoices or payment links built for cross-border client work.
Give clients a cleaner payment experience and keep payment states visible from collection through payout.
Withdraw funds through supported payout methods once the workflow is cleared to move.
Explore the freelancer workflow

Modules teams often add around MoR.

Many rollouts start with the core MoR workflow, then add receiving, payouts, or batch operations as volume and complexity grow.

Virtual Accounts

Use dedicated receiving details when customers or external platforms pay by bank transfer and you need clearer inbound attribution.

Explore module

Payouts

Add beneficiary management, payout controls, and status tracking when funds need to move out reliably across markets.

Explore module

Mass Payouts

Run batch approvals, imports, and higher-volume payout programs when a simple one-off payout flow is no longer enough.

Explore module

Frequently Asked Questions

What does Merchant of Record mean in practice?+
Merchant of Record is broader than payment processing. In supported Gruv workflows, it can package billing or checkout, compliance gates, payout operations, and record-keeping into one program instead of leaving those steps spread across disconnected tools.
Which MoR page should I start with?+
Start with the Business page if your team is paying freelancers, agencies, or contractor groups. Start with the Freelancer page if you are selling services, invoicing clients, and need a cleaner path from payment collection to withdrawal.
Can businesses and freelancers both use Gruv?+
Yes. Gruv supports both sides of the workflow, but the operating model is different. Businesses usually care about vendor consolidation, approvals, and audit-ready payouts, while freelancers care about invoicing, checkout, and getting paid reliably.
What can Gruv cover inside an MoR workflow?+
Gruv can support client-facing invoices or payment artifacts, payment collection, compliance and tax gates, payout operations, and audit-friendly records inside one MoR workflow. The mix is shaped by your persona, market, payout method, and program configuration.
Can I start with one market, corridor, or workflow first?+
Yes. Many teams start with one region, one payout route, or one business unit, then expand once the workflow and controls are proven. Gruv is well-suited to phased rollouts instead of all-at-once launches.
Can I use Gruv if I already have my own entity?+
Yes. Some customers use Gruv alongside their own entities for selected markets or workflows, while others use it more broadly across the program. The right model is shaped by who is selling, where funds move, and which compliance responsibilities you want packaged into the workflow.
How do payout timing, reviews, and holds work?+
Gruv keeps payout timing, reviews, and hold states explicit so teams are not guessing whether funds are pending, held, available, or paid out. The timeline follows the payout method, market, verification state, and policy checks in the workflow.
Global network background

Ready to see Gruv in action?

Book a demo to scope coverage and rollout, or explore the docs to see how modules fit together.

Book a demoSee pricingRead the docs