IDCloud Portal
The IDCloud Portal is the console where you operate IDCloud after integration: track your customers' identity verification journeys, check each result, and configure how the experience looks for them.
It's the tool for the team that lives with the product every day — fraud prevention, operations, support, product. Nothing here requires technical knowledge.
Access: portal.id.unico.app
Before using any guide
You need a Portal user. Access is created by your account administrator. If you don't have one yet, that's who you talk to.
What you see depends on your permission. Each guide states, in its "Before you start" section, which access profile it requires. If a tab doesn't show up for you, that's a permission issue — not a bug, and not something that needs a technical ticket.
Staging and Production are independent. Each Portal configures its own environment. Configuring in Staging never affects Production — you need to repeat it in the Production Portal.
What you can configure depends on your integration version. Some options only exist in certain Web Journey versions and integration models (iFrame, Redirect, SDK). Each guide calls this out in its own step-by-step, so you don't need to know your version up front to start reading.
Settings
The Settings screen brings together three tabs, each with its own guide. It's the area fully covered at this point.
Journey Customization →
Settings → Customization tab
Apply your brand's visual identity to the verification journey: logo, background color, button colors and shape, and text color. The screen shows a real-time preview, on mobile and desktop, before you publish.
The guide covers the full step-by-step, what each field does, the logo file limits, what's configurable in each Web Journey version, and how to register the allowed domains when the integration is by iFrame.
Use when: the journey needs to feel like a continuation of your product, not a third-party screen.
Webhook →
Settings → Webhook tab
Configure where IDCloud notifies your system when a journey changes state, how it authenticates against your API, and what happens when it doesn't respond.
The guide covers the four authentication types and their fields, the retry and throughput configuration, and how to actually test that the notification arrived.
Use when: you want to receive the verification result automatically, without your system having to poll.
QR Code →
Settings → QR Code tab
Enable QR Code display in the journey, so your customer can start on desktop and continue on mobile.
The guide covers how the toggle behaves — it applies the change immediately, with no save button — and how to validate it on a real journey.
Use when: part of your customers start the process on desktop and capture works better on mobile.
Where to start
If you're launching the product now, this is the order that avoids rework:
- Journey Customization, before your first real customer goes through the flow. Changing the color later is easy — having your first customers see a screen without your brand can't be undone.
- Webhook, so your system receives results without having to poll. Configure and test in Staging before repeating in Production.
- QR Code, if your users start the journey on desktop.
If you already operate the product and came to solve something specific, go straight to the tab's guide — each one starts by saying what it does and what permission it requires.