Portal roadmap
This page separates what the portal does now from what may come later. Something listed under Later is not available until it appears under What the portal does now.
What the portal does now
- Public pages need no account. What Wasp is, the integration choices, security guidance, support and the legal notices are open to anyone, and so are the Checkout SDK assets.
- Registration is open and self-service. Anyone may create an account at /portal/register and verify their email. Registering gives you an identity and the guidance every registered developer can read. It attaches you to no merchant and grants nothing else.
- You ask for access from the portal. You request access to your merchant from your portal home page. An administrator for that merchant approves it, and chooses your access in the same step.
- Two API references. The Merchant API reference and the Wasp API reference are read in the portal, and each can be downloaded as the exact YAML file. Each is opened by its own access. See the API reference overview.
- Every page is checked. Each page declares the access it needs, and the portal checks it on every request rather than by hiding links. Search only matches pages you are allowed to read.
- Administrators manage access in the portal. They approve requests, attach developers to a merchant and choose each developer's access.
- The portal shows your merchant's details. Once you are attached, it shows your Merchant ID, Aggregator ID, payment methods, checkout domains and whether an outcome callback URL is set, and fills them into the guides.
- Sandbox credentials come from Stratsol. Ask through Support.
The portal does not record what you read.
The kinds of access
Registration and merchant attachment grant nothing on their own; access is a deliberate grant.
| Access | Requires | What it opens |
|---|---|---|
| Public | Nothing | What Wasp is, the integration choices, security, support, legal |
| Registered | An account | The guidance for choosing and preparing an integration, and how to request access |
| Merchant API reference | Merchant API reference access | The implementation guides, runnable examples and the Merchant API reference |
| Wasp API reference | Wasp API reference access | The Wasp API reference: the broader Wasp contract, including the administration operations Stratsol runs |
| User administration | User administration access | Administering developers: access requests, merchant attachment and access |
These are not levels. Each access opens only what it names, and holding one never implies another. What you read will never affect what you are granted. See the Privacy notice.
Later
Capabilities that need a provisioned relationship, and are not committed to a date:
- Self-service sandbox credential issuance and rotation.
- Checkout Web Domains, editable in the portal.
- Apple Pay domain verification status.
- Outcome callback URL configuration.
- Transaction search, status and redacted logs.
- Production access requests and go-live tracking.
- Aggregator views across a merchant portfolio.
What will not be here
Some things belong in an operational system rather than a developer portal, and are called out so nobody waits for them: raw payment credentials, decrypted card data, another merchant's data, and internal routing or risk configuration are never exposed through this portal at any tier. See the Visibility model.