Skip to main content

​
What you’ll accomplish

Checkouts let you collect payments through a hosted payment page without building your own transfer or PIX UI. You create a session, share a checkoutUrl with the payer, and HG.Cash confirms payment automatically—or flags it for manual review when needed. In the HG.cash dashboard (Checkouts in the sidebar), you can:
  • See stats (created, completed, conversion, money collected) and recent sessions
  • Create new checkouts and copy the payer link
  • Validate receipts when auto-match did not complete (Argentina)
  • Reconcile inbound bank movements to a pending checkout when matching failed
You can also integrate entirely via the REST API (POST /api/v1/checkouts and related endpoints). Interactive schemas live under API reference → Checkouts.

​
Overview by country

Payers do not log in to HG.cash on the public page. Your backend (or dashboard) uses the same Bearer API token as other v1 endpoints.

​
Checkout statuses

​
Webhooks

When a checkout changes state, HG.Cash can send a CHECKOUT webhook (checkout.completed, checkout.awaiting_manual_review, or checkout.rejected). Configure a per-checkout webhookUrl on create or your user default URL. See Receiving webhooks for HMAC signing.

​
Guides in this section

​
Before you begin

  • Access to Checkouts in the dashboard (enabled per user; contact HG.cash if you do not see it)
  • An operative receiving account for the country (ARS + Urbana for AR, BRL PIX platform for BR, CL PayRetailers for CL, BOB for BO). Bloqueada or Cerrada accounts cannot be used for BR, CL, or BO checkouts and return 403 with ACCOUNT_NOT_OPERATIVE.
  • successUrl on every create — where the payer is redirected after success
  • Optional webhook signing secret in account settings