The single application through which a member holds, moves and participates across the SWSS ecosystem — one verified identity, one portfolio, and every product settling on the same layer rather than a separate account per product.
A first session in the SWSS Unified App follows a fixed order. Each step depends on the one before it, and skipping ahead is not possible, the application will return a member to the earliest step they have not completed.
What to Have Ready
| You will need | Why |
|---|---|
| An email address you control | Confirmation is sent to it, and it becomes the address the Foundation uses to reach you |
| A device you trust | Your session and your signing capability are established on it. Treat it as you would the device you bank on |
| Government-issued identity documents | Required for verification. An individual verifies through KYC; an institution verifies through KYB. See Identity Verification |
| For an institution: entity documentation | Registration details and evidence of authority to act for the entity |
The Order of a First Session
- Open the application. The SWSS Unified App is at app.swss.io.
- Sign in through SWSS IVL. Identity is IVL's, and the application asks it rather than maintaining its own. See Signing In with SWSS IVL.
- Confirm your email address. A confirmation is sent to the address you signed in with.
- Review and sign the onboarding terms. Consent is recorded as a signature rather than as a checkbox, so what you agreed to and when is verifiable afterwards by you as well as by the Foundation.
- Complete identity verification. KYC for an individual, KYB for an institution, both through IVL.
- Arrive at your dashboard. From here the rest of the application is open to you, subject to what your verification tier permits.
An account can be created and explored before verification is complete. Operations that are regulated, those that move value or settle a DEED-1 record, require verification first. This is a property of the protocol rather than a setting in the application: verified status operates at the consensus layer, which is why it cannot be granted by an interface. See Compliance at the Protocol Level.
If Something Does Not Complete
Each step reports its own state, and an incomplete step is shown as incomplete rather than skipped silently. A verification that requires review is not a failure: institutional verification in particular involves checks that are not instantaneous. Where a step remains blocked, the support channel inside the application is the route to a person; it carries your account context, which an email does not.
