Skip to main content

​
Who this section is for

Partners and backends can receive HTTPS callbacks from HG.Cash. HG.Cash sends POST requests with JSON when ledger transactions change or transaction requests (such as outbound / cash-out transfers) transition state. Optionally verify deliveries with HMAC-SHA256. Work with HG.Cash onboarding for URLs, signing secrets, and sandbox vs production endpoints.

​
Guides in this section

  • Checkouts — Hosted payment pages for Argentina, Brazil, Chile, Bolivia, and Colombia (create, validate, reconcile in the dashboard and via POST /api/v1/checkouts).
  • API IP allowlist — Optional IPv4 CIDR allowlist for your user API token. An empty list allows any IP. When HG.Cash enforces the list, non-matching requests return 403 Forbidden.
  • Receiving webhooks — Default callback URL & signing secret, X-HG-Webhook-Signature, JSON body (type: ledger transaction vs request for transaction requests), and automatic retry policy.
  • Delivery history and health monitoring — Dashboard delivery logs per transaction or transfer, manual retry, daily health checks, auto-disable on repeated failures, and email alerts.