Shared payload contracts
Engineering, finance, and ops agree on payload shape and field assumptions before build starts.
Developer resources
Validate the integration path before the rollout starts.
Use payload builders, webhook tests, integration patterns, and readiness evidence to align engineering, finance, and operations before production work begins.
Payload recordsWebhook testsClose exportsRollout handoff
docs.gruv.apppayoutscreate-payout
Search docs⌘K
POST/v1/payouts
Create a payout. Returns a payout object once routing and approvals clear.
Run in sandbox
POST /v1/payoutsAuthorization: Bearer sk_live_••••{"amount": 14200,"currency": "USD","payee": "py_29ax8c2v","rail": "ach_same_day","idempotency_key": "rollout-may-001"}
200 OKpayout.created
id"po_29ax8c2v"
status"approved"
settled_at"2026-05-15T14:22Z"
provider_ref"stripe_treas_8a91"
Tested in sandbox
Webhook payout.released
Idempotent retries
Capabilities
From request to release with the same record
Webhooks rehearsed before launch
Replay events, inspect responses, and prove retry behavior before the first production call.
Close fields mapped early
Provider references, status history, and ERP fields locked before scope freezes so finance signs off ahead of build.
Trust artifacts surfaced early
Coverage, controls, and data-handling docs attached during scoping so procurement and security move with the build.
Examples that match how money moves
Payload examples ship with finance context
Every request shape carries counterparty, amount, currency, references, and the close output finance teams need on the same record.
Webhook docs walk through the failure path
Retries, failed payouts, held records, and the support actions that resolve them are documented alongside the success path.
Export fields documented before rollout
Provider references, status history, fees, exception reasons, and ERP fields are mapped before scope freezes so finance signs off early.
Integration readiness
What engineering should validate before launch
01
Map
Request and response fields
02
Replay
Webhook states and retries
03
Export
Finance close fields
04
Review
Trust and rollout packet
Capabilities
Tools and artifacts you can use today
API payload builder
Explore request and response shapes with typed fields so engineering can plan implementation against data that resembles the workflow.
Webhook simulator
Replay representative events, inspect responses, and rehearse retry paths before the first production call or support escalation.
Integration patterns
Pick the API, webhook, file, or hybrid pattern that fits the stack, finance handoff, and team bandwidth you actually have.
Implementation examples
Review request and response examples for common payout, virtual-account, collection, and reporting workflows during evaluation.
Trust and coverage pack
Security posture, regional coverage, residency, data-handling, and audit-ready artifacts for procurement and security reviews.
Close-fields reference
Provider references, status history, fees, and exception reasons mapped to ERP fields before rollout scope freezes.
How it works
Validate one event contract before adding every system
Deeper resources
Where to go next
Links into the product surfaces and evaluation materials most developer teams open next.
Integrations
APIs, webhooks, files, ERP and HRIS connectors.
Payouts
Compliance-gated payout runs with audit trails.
Virtual accounts
Dedicated receiving details and auto-reconciliation.
Trust and coverage
Security posture, regions, and audit-ready artifacts.
Case studies & proof
Stories, redacted samples, and evaluation artifacts.
Pricing
Plans and enterprise modules for scaled rollouts.
Frequently Asked Questions
What stacks do you integrate with?+
Common conversations include ERPs, HRIS, identity providers, product databases, payout providers, earnings networks, and finance data warehouses. Many integrations run as APIs or webhooks, with file imports available as a fallback for quicker rollout reviews.
Is there a sandbox environment?+
Evaluation can start with the API payload builder and webhook simulator. For signed-in sandbox credentials, talk to an engineer so the environment, data shape, and workflow scope match what you need to validate.
How do I test webhooks locally?+
The webhook simulator can replay representative events to an endpoint you configure, including local URLs via a tunnel. It should be used to rehearse retries, failure states, support actions, and downstream finance handling before production traffic.
Where are the OpenAPI specs and code samples?+
Endpoint schemas, request and response shapes, and representative examples are available through the payload builder. Full OpenAPI spec downloads and implementation review can be scoped during evaluation.
How long does a typical integration take?+
Teams that start with file imports or a narrower payout flow usually move faster than teams trying to connect every system at once. Deeper API, SSO, and multi-system syncs should usually follow once the first workflow and exception path are validated.
What should we validate before engineering starts?+
Validate the request fields, webhook states, retry behavior, finance export fields, owner map, trust packet, and first rollout boundary. That keeps the build from becoming a moving target.
Ready to review the integration path?
Talk to an engineer to scope endpoints, events, export fields, and rollout, or open the payload builder to test request shapes right now.
Many teams start with a narrow launch in weeks; timelines depend on scope and integrations.