Skip to main content
Gruv.ai logo

Sending payouts

How do I create a payment request?

Select a payable talent and project, add service lines, review currencies and fees, then submit the payment request.

Updated July 18, 2026

The current one-person flow creates a payment request for a talent. It does not directly execute a payout. You enter the payment details, create a draft, review totals and context, and submit the request. Any later approval, funding, or payout action remains separate.

Before you create the request

  • Confirm the active team. If Gruv asks you to choose one, make that selection before entering payment details.
  • The talent must appear as payable. If they are still invited or need payout setup, use Inviting a talent and resolve that status first.
  • Have a project and category ready. The form requires both before it can create a draft.
  • Know the transaction currency, the currency the talent should receive, and who covers the service fee.

Create the payment draft

  1. Open Create payment.
  2. Select Talent (Beneficiary). A talent that is not payable remains disabled and shows its current readiness label.
  3. Select the project, category, optional subcategory, payout currency, transaction currency, and service-fee payer.
  4. Add at least one service line with a description, quantity, unit, and unit price. Use additional lines when the request covers more than one service or milestone.
  5. Choose Review payment request. Gruv creates a draft and opens Review & send.

Review and submit

Check the amount charged to the client, the amount shown for the talent, currencies, fees, and service lines. You can add notes and upload supporting attachments. Wait for uploads to finish before submitting. If live totals are unavailable, the page can show the entered draft values; review them carefully before continuing.

Choose Submit payment request only when the review is correct. The result is a submitted transaction request and may provide links for payment or document details. Submission is not the same as clicking Approve or Execute on a Payment Run.

Need to prepare multiple beneficiary rows from a file? Use Payment Runs instead. A Payment Run has its own beneficiary IDs, CSV fields, processing states, approval actions, and execution permissions.

Was this article helpful?

Related articles

Still need help?

Tell us what you are trying to do, what you can see, and where the workflow stopped. We will route the question to the right person and follow up.

Contact Gruv