Skip to content

STORY: Commit account reservations from ledger events #102

Closed
2 of 2 issues completed
Closed

Description

@ramioooz

Type: Story
Epic: Ledger and Financial Posting
Slice: Slice 5 - Internal Transfer
Service: account-service
Priority: P0

Update Account Service so final account balance projection changes are triggered by ledger posting events.

Scope:

  • Consume LedgerPostingCompleted and LedgerPostingFailed events.
  • Commit reserved funds when ledger posting completes.
  • Release reservations when ledger posting fails or expires.
  • Use inbox deduplication, optimistic locking, and idempotency.
  • Keep public balance mutation APIs prohibited.

Definition of Done:

  • Account Service does not accept direct public balance mutation requests.
  • Reservation commit/release behavior is driven by ledger events.
  • Duplicate ledger events are ignored safely.
  • Balance projection changes are traceable to ledger posting ids.

Activity

  1. added theissue type on Aug 2, 2026
  2. ramioooz commented on Aug 30, 2026

    @ramioooz
    MemberAuthor

    Account Service reservation persistence is now available for review in account-service#33. This is the first foundation slice: it persists idempotent reservations, protects available balance with optimistic locking, and adds PostgreSQL constraints. The story remains open until ledger-event consumers commit or release reservations and deduplicate those events in Sprint 3.

  3. self-assigned this
    on Aug 30, 2026
  4. ramioooz commented on Sep 1, 2026

    @ramioooz
    MemberAuthor

    Sprint 3 completion evidence: Account Service PRs #33, #34, #35, and #36 are merged. They implement reservation persistence, ledger-driven commit/release handling, governed ledger-event consumption, and reservation command/fact transport. Child tasks #171 and #183 are complete; remaining transfer orchestration work is tracked under #103.

  5. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Account Service transport integration PR is ready for review: digital-bank-java/account-service#37

    It integrates account-service#34 through #36 on top of #33. Existing verification passed: 27 tests, PostgreSQL/Kafka configuration coverage, and git diff --check.

  6. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    The account-service integration is now consolidated in account-service#38. It replaces the conflicting account-service PRs #27 and #37 and carries the current transport stack plus the Maven quality gate. Review and merge #38 instead of merging #27 and #37 separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions