igrantio-business-wallet-portallisted

# iGrant.io business wallet portal (umbrella) ## When to use A customer organisation wants its **own** business wallet portal - their branding, their pages, only holder functions (receive, hold, present, notifications) - on the iGrant.io OWS APIs. This skill is the route map: it does not duplicate any contract; it tells you which skill to open for each part and in which order. For a single missing fact (a path, an enum, a payload), go straight to `igrantio-api-holder`. ## 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. ## 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. 1. **Environment** - demo or staging? _Default demo (`https://demo-api.igrant.io`); a switch later is a configuration change._ 2. **API key** - do you have the OWS API key for that environment? If not, request it from [support@igrant.io](mailto:support@igra