Skip to main content
Gruv.ai logo

Provider review

Get the provider list for the workflow you are buying

The relevant provider set depends on the Gruv modules, customer and recipient types, markets, payment methods, deployment, and provider accounts in scope. Use this page to request and review the right named schedule.

Request the current scheduleReview trust and coverage

A schedule that matches your rollout

Provider roles can change with the modules, markets, payment methods, and account structure you choose. Ask Gruv for the current named schedule and terms that apply to your scope.

Review by provider role

Ask which provider handles each part of the workflow

Each rollout can use a different provider mix. Review the named schedule prepared for yours so procurement can focus on the services and data that are actually in scope.

Identity and screening

Used when a program requires identity, business, sanctions, or beneficiary screening workflows.

  • Which provider is enabled for this customer and recipient type?
  • Which fields and documents leave Gruv?
  • Which status, reason, or review result returns?
  • Who owns manual review and deletion requests?

Agreements and tax services

Used only when the rollout includes electronic signature, tax-document, reporting, or filing services.

  • Which agreement or tax workflow is enabled?
  • Which party supplies the document and filing data?
  • Where are signed or filed artifacts retained?
  • Which provider terms and account region apply?

Payment and verification providers

Used for receiving details, account validation, collection, FX, payout execution, returns, and status events where configured.

  • Which provider and account own the intended corridor?
  • Which entity holds or moves funds?
  • What payer, payee, bank, transaction, and error data is shared?
  • Which countries, currencies, and methods are approved?

Hosting and operational services

Used for application hosting, databases, storage, messaging, observability, search, and workflow operations.

  • Which environment and region will hold customer data?
  • Which managed and in-cluster services are in the final architecture?
  • What backup, retention, access, and incident controls apply?
  • Which services receive logs or operational metadata?

Named schedule checklist

Make every provider row answer the same questions

A useful schedule is more than a logo list. It shows why the provider is involved and which part of your rollout makes that involvement necessary.

  • Legal provider name and service category
  • Purpose and enabled Gruv workflow
  • Data subjects and data categories
  • Hosting or processing locations
  • Transfer and contractual mechanism
  • Customer or provider account
  • Activation status and checked date
  • Notice, objection, and replacement terms

A practical procurement path

Turn the provider list into a focused review

  1. 01

    Name the modules and markets

    A billing-only evaluation, a contractor program, and a multi-country payout flow can use different providers and data categories.

  2. 02

    Request the current named schedule

    Ask for the provider list that applies to the proposed workflow, environment, account structure, and launch date.

  3. 03

    Trace data provider by provider

    Record the fields sent, result returned, storage location, retention terms, and support path for each provider.

  4. 04

    Put change terms in the agreement

    Confirm notification, objection, substitution, and termination terms in the DPA or customer agreement.

Need the current provider schedule?

Send the modules, markets, customer and recipient types, payment methods, and deployment context you plan to review. We’ll use that scope to prepare the provider questions for your team.

Contact Gruv