Skip to content

TASK: Establish payment instruction lifecycle foundation #161

Closed
3 of 3 issues completed
Closed

Description

@ramioooz

Parent: #98

Objective

Create the payment-service foundation that can later participate in the internal-transfer workflow without coupling it to external payment rails.

Scope

  • Define a transport-neutral payment instruction lifecycle and correlation identifiers.
  • Model idempotent command acceptance and terminal outcomes.
  • Keep provider adapters, real payment rails, Kafka publication, and transaction saga orchestration deferred to their planned stories.
  • Add focused unit tests and documentation of the boundary.

Acceptance Criteria

  • Repeated requests with the same idempotency key are deterministic.
  • Illegal lifecycle transitions are rejected.
  • No card, bank, provider, or credential data is committed.
  • The implementation is reviewable as a non-draft PR and links this task and parent story.
  • Maven verification passes.

Activity

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

    @ramioooz
    MemberAuthor

    Completed by merged Payment Service PRs #2, #3, #4, and #5. Lifecycle, HTTP resource, idempotency, authorization, and contract work is complete. Configuration task #162 remains under the bootstrap story #98.

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