Skip to content

TASK: Define versioned transfer risk and step-up decision contract #194

Closed

Description

@ramioooz

Parent: STORY: Define transfer risk policy and step-up annotation (#55)
Sprint: Sprint 4 - Secure Customer Access and Step-Up Authorization (#22)
Type: Task

Objective

Define the versioned decision contract that determines whether a transfer is allowed, requires step-up authentication, or is declined. This is a design/documentation task; it does not implement risk thresholds, MFA challenges, or transfer execution.

Scope

  • Define request inputs and response outcomes for transfer-risk evaluation.
  • Define stable reason codes, policy-versioning, correlation, expiry, and assurance requirements.
  • Define security invariants: transfer binding, single use, TTL, replay protection, data minimization, and no raw secrets or OTP values.
  • Define boundaries between Transaction Service, Auth Service, MFA Service, and Ledger Service.
  • Identify future implementation tasks without hard-coding business thresholds.

Acceptance Criteria

  • A versioned contract document exists under organization documentation.
  • The document includes representative JSON examples and explicit ownership boundaries.
  • The contract explains the allowed, step-up, and declined paths.
  • Security, audit, observability, and failure-handling expectations are recorded.
  • The document is linked from the parent Story and project handoff.

Delivery

  • Add the supporting documentation PR and link it here.
  • This task can merge independently; no rollout delay is required.
  • Later implementation PRs must reference this Task and the parent Story.

Activity

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

    @ramioooz
    MemberAuthor

    Implemented in #195.

    The PR adds the versioned transfer-risk and step-up decision contract, ownership boundaries, security invariants, failure handling, audit/observability expectations, and future implementation slices.

    Merge: independent; no waiting period is required. Later implementation PRs should reference this Task and parent Story #55.

  4. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Correction: PR #195 was opened against a remote branch that was subsequently overwritten by an unrelated commit, so it does not contain Task #194's implementation.

    The verified implementation is now in replacement PR #196. PR #195 is being closed as superseded.

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