Skip to content

Declarative hooks: add receipt QR and footer variable registry #302

Description

@sridharkalaibala

Parent: #34

Goal

Prepare safe receipt customisation without allowing arbitrary code inside billing.

Scope

Define the allowed variables an app can request for receipt extra lines, QR labels, and footer text.

Acceptance criteria

  • Registry lists variable names, examples, source entity, and privacy risk.
  • It excludes secrets, payment credentials, private customer notes, and raw health/tax documents.
  • A sample config shows one QR line and one footer line.
  • Fallback behavior is defined when a variable is missing.

Out of scope

  • No production credentials, customer records, tax IDs, payment data, or private payloads in the repo or issue comments.
  • Do not claim a live integration is supported until a maintainer accepts the matching fixture and evidence.

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

    area: app platformApp registry, install flow, permissions, extension surfaces, connector runtime contractsarea: integrationsExternal services, optional connectors, import/export contractscommunity editionMust work in the free local/community edition without requiring Posnic ClouddocumentationImprovements or additions to documentationenhancementNew feature or requestgood first issueGood for newcomershelp wantedExtra attention is neededneeds designNeeds design notes or acceptance criteria before code PRssize: smallSmall, focused task suitable for a short PR

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions