Ensure all required fields are filled (admin name, email, password, organisation name, sector, location). Your password must be 8-20 characters. If your email is already registered, try logging in or use a different email.

After account creation you can log in anytime to continue onboarding. The system will redirect you to the next incomplete step (wallet connection, verification, or Code of Conduct signing).

Your Business Wallet Address is available in your DISP portal under Digital Wallet (OpenID4VC) > Base Configuration. Copy the full URL and paste it in the Data Marketplace.

Verify that the Business Wallet Address is correct and that your DISP account is active. Ensure your browser allows redirects. If the issue persists, contact your DISP provider.

Ensure your organisation's Legal PID credential is properly issued in your DISP wallet. Check that the credential has not expired. Try clearing your browser cache and attempting verification again.

After requesting the Software Statement, check your DISP portal under Digital Wallet (OpenID4VC) > Wallet Unit (Holder). You need to click 'Click to get the credential issued' and then Accept. The statement will then appear in both the DISP and the Data Marketplace.

There are two OAuth 2.0 clients to configure: 1. Data Marketplace OAuth 2.0 Client: Created in the Data Marketplace, its Client ID and Secret are pasted into your DISP portal (Data Marketplace > Base Configurations). 2. Organisation OAuth 2.0 Client: Created in your DISP portal, its Client ID and Secret are pasted into the Data Marketplace (Developer APIs > Organisation OAuth 2.0 Client).

After publishing a DDA from your DISP, it appears as Unlisted in the Data Marketplace. You need to click 'Request Review' to submit it for governance review. The Review Committee will then approve or reject it.

After the DDA is approved, you still need to click 'List' to make it discoverable on the public discovery page. Only listed DDAs are visible to other organisations.

Ensure your access token has not expired. Verify that the requested API endpoint and HTTP method match those authorised in the Data Agreement linked to the DDA. Check that your DISP's Authorisation Endpoint is correctly configured.