Skip to content

Reservations + tokenization #48

Description

@2D

POST /v1/reservations creates hold, confirms payment (stub), and issues ReservationToken with QR PNG (use your existing QR WebApi project).

GET /v1/reservations/{id}, POST /cancel, POST /transfer.

Store token_ref column (nullable) for future DLT transaction id.

DoD: Scanning QR calls GET /v1/reservations/{id} and shows status=active; cancel flips to canceled. (Reuses the QR module you already ship.)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions