Skip to main content

Dashboard

  1. Open Checkouts in the sidebar (/app/checkouts).
  2. Review the stats row and recent sessions on the overview.
  3. In Create checkout, choose country, account (optional—HG.Cash picks an eligible operative account if omitted), amount, and success URL.
  4. Click Create checkout. Copy the checkout link from the success panel and send it to your payer.
Use Validate or Reconcile (top right) when you need those flows.

Country notes (dashboard)

API

POST /api/v1/checkouts with Bearer token. Minimum body:
Optional: accountId, cancelUrl, webhookUrl, metadata, idempotencyKey, locale, and payer (country-specific). For BR, CL, and BO, if you pass an explicit accountId that is Bloqueada or Cerrada, the API returns 403 with code: ACCOUNT_NOT_OPERATIVE. When accountId is omitted, HG.Cash selects an eligible Operativa account.

Argentina (AR)

  • Response includes accountDisplay (alias, CVU/CBU, holder).
  • Payer completes name, amount, and 8-digit DNI on the hosted page.
  • Completion when an inbound transfer matches amount + DNI on the assigned account.

Brazil (BR)

  • payer.name, payer.document (CPF or CNPJ — digits only or formatted), and payer.email required on create.
  • Response may include qrCode and pixCopiaECola.

Chile (CL)

  • paymentMethodId and customer required — see Chile cash-in for payment method listing.

Example (Brazil)

Response includes checkoutUrl — send that URL to the payer. PIX fields (qrCode, pixCopiaECola) may also be returned on create.

Example (Argentina)

Response includes checkoutUrl — send that URL to the payer.