Skip to main content
Gruv.ai logo
Money Movement

Send a payment link without losing the invoice trail

Issue the request from the invoice, open hosted checkout, and keep the provider result connected to the record finance needs to reconcile.

Hosted checkoutPayment method scopeProvider statusFinance references
Abstract animated-base freelancer merchant-of-record workflow surface with invoice and withdrawal panels.
Payment link
$4,500.00
Invoice#1024
ClientNorthstar Labs
Expires48 hours
Hosted checkout
Client session active
Card
Bank
Capture synced
Invoice, wallet, and provider ref matched

Built for the work after the pay button

Checkout is only one part of collection. Keep the invoice, request, provider session, current status, and finance handoff connected so a retry or exception has a clear owner.

The request starts with invoice context

  • The checkout descriptor keeps the invoice reference, amount, and currency together
  • The provider and checkout flow remain visible
  • Support and finance can use the same request reference

Repeated clicks reuse one charge record

  • The page derives a stable idempotency key from the link token
  • Intent retries can carry that key to the checkout service
  • The provider result remains the source for the payment outcome

Finance gets a defined handoff

  • Keep invoice and provider references in the collection record
  • Map amount, currency, fees, and status into the enabled export
  • Send mismatches to review instead of assuming the books are closed

Pick the collection model that fits your volume

Start with the invoice and hosted checkout flow. Add event and finance handoffs only after the provider, fields, status rules, and exception owner are clear for your program.

Invoice-linked payment requests

Issue the payment request from an invoice so the checkout opens with the right reference, amount, currency, and account context.

Hosted checkout in your client portal

Open the hosted provider session from your client experience, then bring its current result back to the invoice record.

Status and exception handling

Use provider events and checkout responses to update the collection status, and route mismatches or failures to an owner for review.

Finance-ready references

Carry the invoice and provider references into your finance export or accounting handoff.

How it works

From payment link to closed invoice

Five steps take an invoice-linked request through hosted checkout and into a reviewable finance handoff.

gruv.app › collect › new request
collectrequestsnew

Payment request · inv_4823

Drafting
Invoice refinv_4823
ClientNorthwind Group
Amount$14,200.00
CurrencyUSD
Expiresin 7 days
MethodsCard · Bank transfer
Tokenized linkpreview

Signed token created

tok_2hN8aZ4Q · expires 2026-05-12T18:00Z

Idempotency key set

idem_d4f9

Invoice context attached

Frequently Asked Questions

What stays connected to the payment request?+
The checkout descriptor carries the invoice reference, account, amount, currency, provider, and checkout flow. That gives operations and finance a shared reference for the request and its current result.
How does the result reach finance?+
Keep the invoice reference and provider transaction reference in the collection record, then map the fields into the export or accounting handoff enabled for your program.
What payment methods can my clients use?+
The hosted session determines the methods available for the configured provider, entity, country, and currency. Confirm that scope before sending a live request.
How do payment links stay secure?+
The checkout service returns distinct invalid, expired, and no-longer-payable responses. Intent creation can also carry a stable idempotency key derived from the link token.
Payment captured but the invoice still shows unpaid. What happened?+
Compare the invoice state with the provider transaction reference and current checkout result. Keep the mismatch in review until the provider event and finance record can be reconciled.

Ready to map your invoice-linked collection flow?

Bring the invoice record, provider, payment methods, status events, exception path, and finance fields you need. We will turn them into a focused rollout scope.

Many teams start with a narrow launch in weeks.