Financial control

Detect and resolve incomplete casino transaction lifecycles.

Distributed wallet and provider calls can time out or arrive more than once. ALHICA records enough evidence to determine whether an effect completed and to recover according to an approved rule.

  • Duplicate protection
  • Pending and incomplete-cycle detection
  • Audited recovery actions
01

Prevent repeated effects

Each financial operation uses stable business identifiers and persisted idempotency state so transport retries do not become repeated debits or credits.

Provider-specific duplicate responses are normalised without discarding their original evidence.

  • Stable transaction keys
  • Request and response persistence
  • Provider-aware duplicate handling
02

Identify ambiguous outcomes

Timeouts, missing completion events, open cycles and balance differences are surfaced as explicit operational states.

Rules determine which cases can retry automatically and which require authorised review.

  • Incomplete cycle detection
  • Calculated and notified balance comparison
  • Configurable reconcile rules
03

Recover with evidence

A recovery action records the original operation, actor, decision, request and final provider outcome.

Daily and lifetime summaries support reconciliation with studios using the source identifiers required by the relevant integration.

  • Controlled retry and resolution
  • Audit trail
  • Financial exports
Next step

Walk through a timeout and recovery scenario.

We can demonstrate the evidence and controls around a sample transaction lifecycle.

Discuss reconciliation