Skip to content

EPIC: Payment Rail Architecture #31

Closed
2 of 2 issues completed
Closed

Description

@ramioooz

Type: Epic
Epic: Payment Rail Architecture
Slice: Slice 5 - Internal Transfer
Service: payment-service
Priority: P0

Track this capability for the Digital Bank Java production delivery baseline.

Definition of Done:

  • Scope is implemented or documented for the selected delivery slice.
  • Verification steps are documented and repeatable.
  • API requests are added to the Insomnia collection when an API is introduced.

Activity

  1. added theissue type on Aug 2, 2026
  2. self-assigned this
    on Aug 30, 2026
  3. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Implementation update - 2026-09-06

    The missing Sprint 5 payment-state event slice is now tracked in child story #250: #250

    Payment Service currently has the persisted HTTP instruction lifecycle, but Sprint 5 still requires durable Kafka payment-state events and SIT evidence. The child story is In progress; the sprint remains open until payment orchestration/state events and notification delivery acceptance are complete.

  4. ramioooz commented on Sep 10, 2026

    @ramioooz
    MemberAuthor

    All payment-service lifecycle, authorization, persistence, event publication, and resource-contract descendants are complete and verified in SIT. Closing the parent epic; remaining cloud deployment concerns remain deferred to Sprint 7.

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