igrantio-qr-codelisted

Wallet QR code panel for EUDI Wallet (EUDIW) and European Business Wallet (EUBW) flows on the iGrant.io Organisation Wallet Suite, at the exact look of the iGrant.io demonstrators and the OWS passwordless-login page: a 240 px credential-offer or presentation-request QR at error-correction level H in a bordered, rounded 12 px frame, the logo on a white disc in the centre, the small refresh pill that mints a new exchange, the bordered white "Open in EUDI Wallet" button at QR width, a transaction-code box, the wallet hint, and the initialising / refreshing / scanned / error states. Use whenever an issuer or verifier frontend renders a wallet QR.
L3-iGrant/skills · ★ 1 · Code & Development · score 75

Install: claude install-skill L3-iGrant/skills

# iGrant.io wallet QR panel ## When to use Any time a frontend renders a wallet QR: the issuance `credentialOffer` or the verification `vpTokenQrCode` URI. This skill is the single QR pattern for `igrantio-issuer-frontend` and `igrantio-verifier-frontend`; both vendor it. Use it instead of a hand-rolled QR component, so every QR code a user meets looks the same as in the iGrant.io demonstrators and the OWS passwordless-login page. For the bare URI-to-image helper only, `igrantio-frontend-client` ships a minimal `QrCode`. ## Prerequisites - An **iGrant.io Organisation Wallet Suite (OWS) API key**. Get it from [support@igrant.io](mailto:support@igrant.io). Keep it on the server, in an environment variable or a secret manager. The browser never sees it. - The **OWS environment** the key belongs to. The default is **demo** (`https://demo-api.igrant.io`). Use **staging** (`https://staging-api.igrant.io`) only when the integrator asks for it. A key works only in its own environment. - A tenant backend that mints the exchange (`igrantio-issuer-backend` or `igrantio-verifier-backend`). The panel never calls OWS itself. - A logo image for the disc in the centre of the code (PNG or SVG, square). ## Ask the integrator first Ask one question at a time. Wait for the answer. Give the recommended default with each question. Look up facts in the project (framework, environment variables, an existing backend) instead of asking for them. Record the answers before you write code.