Skip to content

E4-F6: Blacklist Validation at Checkout

Epic: E4: Ticket Purchase Flow

Size: S (Small)

Problem / Outcome

Block purchase if any ticket holder is blacklisted.

Scope

In-Scope:

  • Real-time OIB check against blacklist for all ticket holders
  • MUP referral message on block
  • All-or-nothing validation

Out-of-Scope:

  • Partial blocking (all or nothing)

Acceptance Criteria

  • AC1: Given blacklisted OIB, when checkout submitted, then purchase blocked with MUP message
  • AC2: Blacklist check occurs for ALL ticket holders, not just primary buyer
  • AC3: Block message: "HNS is prevented from selling a ticket to this person pursuant to applicable law. For all information regarding this restriction, please contact MUP."

Data Model Impact

No new tables required.

Validation against Blacklist table:
- Check each ticket holder OIB
- Log blocked attempts to ViolationLog

Permissions/Roles

  • Internal service call

How to Verify

npm test -- --grep "blacklist checkout"

Expected: Blacklisted OIB blocks purchase with correct message.

Dependencies

Implementation Tasks

See E4: Ticket Purchase Tasks

Doc References

Last Updated: January 2026