Skip to content

TASK: Make transfer workflow acceptance atomic and authorized #169

Closed

Description

@ramioooz

Type: Task
Parent: #165
Epic: Banking Domain Vertical Slice
Sprint: Sprint 3 - Internal Transfers and Event Consistency
Service: transaction-service
Priority: P0

Objective

Make transfer workflow request acceptance atomic and protect the internal endpoint.

Scope

  • Make concurrent identical transfer requests converge to one persisted workflow and deterministic replay response.
  • Distinguish known uniqueness conflicts from unexpected database integrity failures.
  • Add PostgreSQL-backed HTTP integration coverage for uniqueness, rollback, and concurrency behavior.
  • Enforce authentication and authorization for the internal transfer endpoint.

Acceptance Criteria

  • Exactly one workflow and one initial action exists for concurrent identical requests.
  • A changed request with an existing identity returns 409 Conflict.
  • Unexpected persistence failures do not get misreported as client conflicts.
  • Unauthenticated and insufficiently authorized callers receive documented Problem Details.
  • ./mvnw verify and SIT verification pass.

This is the production-hardening follow-up to the internal HTTP foundation task #165.

Activity

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

    @ramioooz
    MemberAuthor

    Completed by merged Transaction Service PR #9. Transfer acceptance authorization and atomic replay behavior are included. The native parent was corrected from payment task #163 to transfer HTTP task #165.

  3. added theissue type on Sep 4, 2026
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