How do I prepare Continue with SeleID for a web app?

List the HTTPS callback URLs you control. Keep each callback specific to its environment. Where the published integration supports it, use state to bind the response to the request and validate tokens on the server. If a callback is rejected, compare its scheme, host, path and trailing slash with the registered value.

If a callback is rejected, compare its scheme, host, path and trailing slash with the registered value. List the HTTPS callback URLs you control. If you need help, include the product you were using and the step that failed. Keep passwords, one-time codes and secret keys private.

Prepare your web app by identifying its exact callback URL, separating development from production and planning how your server will handle a returned sign-in response. Check the SeleID documentation and roadmap for customer sign-in access before attempting to register a public integration or promising it to users.