Webhooks
Know the moment something changes.
DATAMASON Ledger sends signed events when a transaction matches, an exception opens or a run completes, so your systems can react without polling.
Event catalogue
Six events to start.
| Event | Sent when |
|---|---|
| transaction.ingested | A transaction was received and normalized |
| transaction.matched | A transaction was matched to its counterparts |
| exception.opened | A difference needs review |
| exception.resolved | An exception was resolved and recorded |
| settlement.confirmed | A settlement batch was received in the bank |
| reconciliation.completed | A reconciliation run finished |
Payload
Signed, small and explicit.
Each event carries an id, a type and the data needed to act, signed so you can verify it came from DATAMASON Ledger.
{
"id": "evt_6Q2M8Z",
"type": "transaction.matched",
"created": "2026-09-14T10:42:13+05:30",
"data": {
"transaction_id": "txn_48291",
"match_id": "mch_Q8D1TA",
"rule": "exact_amount_ref",
"invoice": "INV-1024"
}
}Delivery
Verify signatures. Expect retries.
- Verify the signature header against your endpoint secret
- Respond with a 2xx quickly; do heavy work asynchronously
- Retries use backoff, so handlers must be idempotent
- Use the event id to de-duplicate
// t = timestamp, v1 = HMAC-SHA256(secret, t + "." + body)
const expected = hmac(secret, t + "." + rawBody);
if (!timingSafeEqual(expected, v1)) return 400;
if (now - t > 300) return 400; // replay windowMake every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.