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)

CountryExtra fields on create
AROptional payer name and DNI; payer can also enter them on the hosted page
BRPayer email required
CLCreate via API only for now (payment method + customer payload)

​
API

POST /api/v1/checkouts with Bearer token. Minimum body: 
{
  "country": "AR",
  "amount": "1500.00",
  "successUrl": "https://merchant.example/success"
}
Optional: accountId, cancelUrl, webhookUrl, metadata, idempotencyKey, locale, and payer (country-specific).

​
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.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 (Argentina)

curl -X POST https://hg.cash/api/v1/checkouts \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "country": "AR",
    "amount": "1500.00",
    "successUrl": "https://merchant.example/success",
    "cancelUrl": "https://merchant.example/cancel",
    "webhookUrl": "https://merchant.example/hooks/checkout",
    "metadata": { "orderId": "ORD-42" }
  }'
Response includes checkoutUrl — send that URL to the payer.