Skip to main content
Gruv.ai logo
Hosted card checkout

Know when the customer needs to act

Open one configured hosted checkout for an eligible invoice. Follow the provider-reported result without treating capture as money received at your bank.

Review checkout setupFollow the payment status

INV-724 · Website translation

USD 480

Action required
Checkout
Configured hosted provider
This customer step
Complete authentication
Current result
Waiting for provider update

The customer completes this step in the provider checkout. The next payment status still comes from that provider.

One session. Three useful outcomes

Gruv starts checkout for an eligible invoice. The configured provider then controls which card methods appear and whether this customer must complete another authorization step.

  1. 01

    Eligible invoice

    INV-724 · USD 480

    The invoice amount and currency are passed into one checkout session.

  2. 02

    Hosted checkout

    One configured provider

    The provider presents the available card methods and owns the customer authorization step.

  3. 03

    Provider status

    One recorded outcome

    A signed provider event reports action required, failed or captured for the attempt.

Alternative results

Action required

For this example, the customer completes authentication in the hosted checkout. That step does not promise capture.

Failed

Gruv records the failed provider status. This attempt is not rerouted through another gateway.

Captured

Gruv updates the payment record and invoice status from the captured provider result.

What should we do with a failed attempt?

Review the provider failure result with the customer or provider support before another attempt. Gruv does not retry the customer's card or select another gateway here.

Why does this example show only one provider?

Checkout resolves one configured provider and creates one hosted session. It does not compare gateways by card, price or approval rate. Confirm provider and program availability before launch.

INV-724 · Payment attempt

USD 480

Captured
Provider event
Captured
Event received
10 Sep 2026 · 14:06 UTC
Gruv payment record
Captured
Invoice
Payment received
Merchant bank
Confirm separately

Record the payment, then confirm bank receipt

For INV-724, a captured USD 480 payment updates the Gruv payment record and invoice status. Check the provider settlement record and bank receipt separately before treating the proceeds as received at your bank or available for payout.

Why separate capture from bank settlement?

Capture confirms the provider-reported payment result and lets Gruv update its internal record. Use provider settlement and bank records to confirm that the money reached your bank.

What if the invoice is disputed later?

Keep the invoice dispute and the provider card chargeback as separate workflows. Gruv can record an invoice dispute and its resolution here; this path does not submit chargeback evidence or an outcome to the card provider.

More in Payouts

Explore more in Payouts

Universal connectors

Bring approved payment records into Gruv with the references needed for finance review.

Payout automation

Keep received-payment records separate from the configured workflow that executes payouts.

Vendor portal

Give payees their own bank-detail and payout-status view outside the customer checkout.

Frequently Asked Questions

Who handles the customer authentication step?+
The configured provider hosts the checkout and any required customer step. Confirm the provider, available methods, markets, merchant category and authentication policy for your approved program.
Does a failed attempt move to another gateway?+
No. This checkout creates one session with one configured provider. Gruv records the failed provider status; the reviewed path does not reroute the card attempt through another gateway.
Does captured mean the money reached our bank?+
No. Capture updates the internal payment and invoice record. Confirm external bank settlement with the configured provider before treating the proceeds as received at your bank or available for payout.
Does the invoice dispute record submit a card chargeback response?+
No. The invoice dispute record keeps its own case and resolution. Confirm the card-provider response, evidence and deadline process for your acquiring program.

Review your hosted checkout setup

Bring the invoice flow, provider program and markets you need to support. We will review the checkout and payment-status path with you.

Review checkout setup