Meld® IDOne account

For project teams

Connect your product to Meld® ID

This page shows the technical contract separately from the user-facing portal: client_id, redirect_uri, secret, IP allowlist, and OAuth flow.

01

Client ID

Each project gets its own client identifier.

02

Client secret

Secrets can be rotated from the admin area.

03

Redirect URIs

Callback URLs are registered ahead of time and matched exactly.

04

IP allowlist

Server-to-server requests can be limited to known addresses.

01

Connection contract

Every project gets its own rules and does not disturb the others.

Identifiers

The project gets a client_id, while the user keeps one identity.

Redirects

Allowed redirect_uri values are set ahead of time and are not guessed.

Secret

The client secret is stored separately and can be reissued.

IP limits

The integration can be limited to specific IP addresses.

02

What data can be requested

Each project asks only for the scopes it needs, and Meld® ID returns only the claims the user approved.

openid

Confirms identity and is needed for the basic login flow.

email

Returns the confirmed email and its verification status.

profile

Broad profile scope. It covers profile.basic, profile.contact, profile.address, and profile.billing.

profile.basic

First name, last name, display name, birth date, and language.

profile.contact

Phone number for contact and verification.

profile.address

Home or delivery address without payment data.

profile.billing

Billing name, company, and tax details. No cards are transferred.

03

OAuth flow

First authorization, then code, then token exchange, then the project’s local session.

01

1. Authorize

The user opens Meld® ID and approves the project login.

02

2. Confirm

After consent, Meld® ID issues an authorization code for the registered redirect_uri.

03

3. Token

The project exchanges the code for an access token and receives userinfo.

04

Security

We check redirects, secrets, and IP allowlists without guesswork.

01

Exact redirect_uri

The match must be exact, with no arbitrary variations.

02

client_secret checks

The server verifies the secret separately from the browser login.

03

Request audit

The admin area shows who goes where and where the chain breaks.