Account movement
HG.Cash will send this webhook whenever money moves in or out of one of your accounts. The request body contains the movement details.
Use this to keep your internal balances and ledgers in sync with HG.Cash.
Documentation Index
Fetch the complete documentation index at: https://docs.hg.cash/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
HMAC-SHA256 signature of the raw JSON body. Format: sha256=<hex>.
When you configure a webhook signing secret in account settings, HG.Cash includes
this header on every webhook POST. Verify the signature in your endpoint to ensure the request is authentic.
Body
Payload sent to your webhook endpoint whenever money moves in or out of one of your HG.Cash accounts.
Headers: When you configure a webhook signing secret in account settings, HG.Cash sends the header X-HG-Webhook-Signature: sha256=<hex> where the value is HMAC-SHA256 of the raw JSON body using your secret. Verify this to ensure the request is authentic.
Notes:
- Numeric values (like
amount, CBU/CUIT) are sent as strings to preserve precision and formatting. dateis a local date-time and must be interpreted usingtimezone.
Internal movement ID
Provider- or bank-level external identifier for the movement
Movement amount as a decimal string
ISO 4217 currency code
^[A-Z]{3}$Movement direction relative to your account
Inbound, Outbound Current status of the movement
Type of movement (for example inbound or outbound)
HG.Cash account ID associated with the movement
Movement local date-time in the provided timezone
IANA timezone identifier used to interpret date
Name of the sender
Name of the recipient
Sender CBU (22-digit). Sent as string.
^\d{22}$Recipient CBU (22-digit). Sent as string.
^\d{22}$Sender CUIT/CUIL (11-digit). Sent as string.
^\d{11}$Recipient CUIT/CUIL (11-digit). Sent as string.
^\d{11}$Coelsa transaction code

